From: lokesh1197 <lokesh1197@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: teams exits if some one on call shares their screen
Date: Sun, 25 Sep 2022 10:14:05 +0200 [thread overview]
Message-ID: <20220925081405.TzdrB9r4Uc0Tc2xvV42xMvfj7uTWkN9uzWvNJFQXhO4@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39131@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1424 bytes --]
New comment by lokesh1197 on void-packages repository
https://github.com/void-linux/void-packages/issues/39131#issuecomment-1257144633
Comment:
Followed it. Still getting the same error. I think I need to get the `proc_util.cc` file somehow but I don't know where to get it from.
Terminal Output:
```
(node:31847) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.
(node:31847) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 ecsSettingsUpdated listeners added to [EventEmitter]. Use emitter.setMaxListeners() to increase limit
(node:31847) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 appInitialized listeners added to [EventEmitter]. Use emitter.setMaxListeners() to increase limit
[31955:0925/133938.319047:FATAL:proc_util.cc(36)] Check failed: . : No such file or directory (2)
Server response:
Server response:
[32036:0925/133941.378786:FATAL:proc_util.cc(36)] Check failed: . : No such file or directory (2)
Server response:
Server response:
[32325:0925/134020.318487:FATAL:proc_util.cc(36)] Check failed: . : No such file or directory (2)
Server response:
Server response:
[32344:0925/134021.246870:FATAL:proc_util.cc(36)] Check failed: . : No such file or directory (2)
Server response:
Server response:
```
next prev parent reply other threads:[~2022-09-25 8:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-06 10:44 [ISSUE] " lokesh1197
2022-09-06 10:46 ` lokesh1197
2022-09-14 12:53 ` Anachron
2022-09-16 15:07 ` lokesh1197
2022-09-17 19:41 ` classabbyamp
2022-09-19 5:26 ` lokesh1197
2022-09-19 5:30 ` lokesh1197
2022-09-21 4:29 ` sgn
2022-09-21 7:58 ` Anachron
2022-09-25 8:14 ` lokesh1197 [this message]
2022-09-25 9:22 ` sgn
2022-09-26 10:21 ` fanyx
2022-10-03 6:44 ` lokesh1197
2022-10-03 10:57 ` classabbyamp
2022-10-03 11:04 ` lokesh1197
2023-03-20 11:50 ` Clos3y
2023-10-13 0:13 ` [ISSUE] [CLOSED] " lokeshmohanty
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220925081405.TzdrB9r4Uc0Tc2xvV42xMvfj7uTWkN9uzWvNJFQXhO4@z \
--to=lokesh1197@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).