From: Nathan Dehnel <ncdehnel@gmail.com>
To: help-guix@gnu.org
Subject: How to grant a program permission to access /run/dbus/system_bus_socket
Date: Thu, 8 Sep 2022 19:00:59 -0500 [thread overview]
Message-ID: <CAEEhgEs6T1ThGF1PZ9a_M2YVHq95K4Qt_GYLMnz3cHYWKg2c+g@mail.gmail.com> (raw)
nathan@guixlaptop ~/guix-configs $ nixGLIntel bitwarden
Fontconfig error: Cannot load default config file: No such file: (null)
(node:27126) DeprecationWarning: file property is deprecated and will
be removed in v5.
(Use `bitwarden --trace-deprecation ...` to show where the warning was created)
Fontconfig error: Cannot load default config file: No such file: (null)
[27126:0908/182240.112106:ERROR:bus.cc(398)] Failed to connect to the
bus: Failed to connect to socket /run/dbus/system_bus_socket:
Permission denied
[27126:0908/182240.112150:ERROR:bus.cc(398)] Failed to connect to the
bus: Failed to connect to socket /run/dbus/system_bus_socket:
Permission denied
[27126:0908/182240.147940:ERROR:platform_font_skia.cc(246)] Could not
find any font: Sans, sans. Falling back to the default
[27126:0908/182240.194552:ERROR:bus.cc(398)] Failed to connect to the
bus: Failed to connect to socket /run/dbus/system_bus_socket:
Permission denied
[27126:0908/182240.194584:ERROR:bus.cc(398)] Failed to connect to the
bus: Failed to connect to socket /run/dbus/system_bus_socket:
Permission denied
[27126:0908/182240.194599:ERROR:bus.cc(398)] Failed to connect to the
bus: Failed to connect to socket /run/dbus/system_bus_socket:
Permission denied
18:23:06.071 › TypeError: Object has been destroyed
at WindowMain.<anonymous>
(/nix/store/sfi1jv9vxlhh6rpxs6dnf6rc5i0ixg2v-bitwarden-2022.8.1/opt/Bitwarden/resources/app.asar/main.js:49732:36)
at Generator.next (<anonymous>)
at /nix/store/sfi1jv9vxlhh6rpxs6dnf6rc5i0ixg2v-bitwarden-2022.8.1/opt/Bitwarden/resources/app.asar/main.js:49546:71
at new Promise (<anonymous>)
at window_main_awaiter
(/nix/store/sfi1jv9vxlhh6rpxs6dnf6rc5i0ixg2v-bitwarden-2022.8.1/opt/Bitwarden/resources/app.asar/main.js:49542:12)
at WindowMain.updateWindowState
(/nix/store/sfi1jv9vxlhh6rpxs6dnf6rc5i0ixg2v-bitwarden-2022.8.1/opt/Bitwarden/resources/app.asar/main.js:49727:16)
at WindowMain.<anonymous>
(/nix/store/sfi1jv9vxlhh6rpxs6dnf6rc5i0ixg2v-bitwarden-2022.8.1/opt/Bitwarden/resources/app.asar/main.js:49681:28)
at Generator.next (<anonymous>)
at /nix/store/sfi1jv9vxlhh6rpxs6dnf6rc5i0ixg2v-bitwarden-2022.8.1/opt/Bitwarden/resources/app.asar/main.js:49546:71
at new Promise (<anonymous>)
Chowning the /run/dbus/system_bus_socket might break something and
would be overwritten anyways. What's the Best Practices™ way to fix
this?
reply other threads:[~2022-09-09 0:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAEEhgEs6T1ThGF1PZ9a_M2YVHq95K4Qt_GYLMnz3cHYWKg2c+g@mail.gmail.com \
--to=ncdehnel@gmail.com \
--cc=help-guix@gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).