From: furryfixer <furryfixer@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: KDE X11 should be started with dbus-run-session
Date: Tue, 12 May 2020 14:11:11 +0200 [thread overview]
Message-ID: <20200512121111.2pnOz0gD5xxz7OWVXzK5wVF6WBZs3Z53tWG5FWB0w44@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-21766@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 602 bytes --]
New comment by furryfixer on void-packages repository
https://github.com/void-linux/void-packages/issues/21766#issuecomment-627303381
Comment:
I was too ignorant to realize the complex name of the dbus-session file is just the machine-id-0.
~/.dbus/session-bus/$(cat /var/lib/dbus/machine-id)-0. Since we know what the filename will be, we could simply (if KDE) source this file at login to set $DBUS_SESSION_BUS_ADDRESS. I leave it to maintainers to ponder whether this is a good idea, and if so, should it happen automatically or be manually done by the user within scripts in the ~/ directory.
next prev parent reply other threads:[~2020-05-12 12:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-08 23:05 [ISSUE] " ProjectMoon
2020-05-10 1:02 ` ericonr
2020-05-10 13:07 ` ProjectMoon
2020-05-10 22:34 ` ericonr
2020-05-11 17:47 ` furryfixer
2020-05-11 18:10 ` Johnnynator
2020-05-11 18:10 ` Johnnynator
2020-05-11 21:04 ` ProjectMoon
2020-05-12 1:06 ` furryfixer
2020-05-12 11:46 ` furryfixer
2020-05-12 12:11 ` furryfixer [this message]
2020-05-20 6:41 ` ericonr
2020-05-20 12:42 ` Johnnynator
2020-05-20 15:02 ` furryfixer
2020-07-17 10:28 ` Johnnynator
2020-07-17 10:28 ` [ISSUE] [CLOSED] " Johnnynator
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=20200512121111.2pnOz0gD5xxz7OWVXzK5wVF6WBZs3Z53tWG5FWB0w44@z \
--to=furryfixer@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).