From: ap4y <ap4y@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: cmus: Starting CMUS without a session bus results in MPRIS error
Date: Wed, 30 Sep 2020 03:12:39 +0200 [thread overview]
Message-ID: <20200930011239.-Dj0-jV4WvHLKDrIFYWdZZZn8VhZg_HcXLZDEwA8xfI@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-20744@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 812 bytes --]
New comment by ap4y on void-packages repository
https://github.com/void-linux/void-packages/issues/20744#issuecomment-701101406
Comment:
In my case I was starting x session via `dbus-launch --sh-syntax --exit-with-session` yet was still getting `mpris` related errors. This one took me a while to figure out, but the problem is that `DBUS_SESSION_BUS_ADDRESS` was not exposed in my environment. I checked what gentoo does to fix this, since my gentoo machine with a similar setup doesn't have this error, and apparently `dbus` package adds [80-dbus](https://gitweb.gentoo.org/repo/gentoo.git/tree/sys-apps/dbus/files/80-dbus) under `/etc/X11/xinit/xinitrc.d` when `X` use flag is enabled. @ericonr I wonder if we should do the same for `dbus-x11` and `dbus-elogind-x11`? I'm happy to send a patch for this.
next prev parent reply other threads:[~2020-09-30 1:12 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-08 6:26 [ISSUE] " flexibeast
2020-04-10 20:47 ` ericonr
2020-04-11 0:34 ` flexibeast
2020-05-06 5:43 ` ericonr
2020-05-11 4:41 ` galmio
2020-05-11 4:42 ` galmio
2020-05-11 4:58 ` flexibeast
2020-05-11 16:06 ` galmio
2020-05-12 11:37 ` flexibeast
2020-08-28 2:05 ` shoober420
2020-08-28 2:05 ` shoober420
2020-09-30 1:12 ` ap4y [this message]
2020-09-30 2:34 ` shoober420
2021-02-28 1:36 ` ericonr
2022-04-16 2:02 ` github-actions
2022-04-30 2:13 ` [ISSUE] [CLOSED] " github-actions
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=20200930011239.-Dj0-jV4WvHLKDrIFYWdZZZn8VhZg_HcXLZDEwA8xfI@z \
--to=ap4y@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).