From: flexibeast <flexibeast@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] cmus: Starting CMUS without a session bus results in MPRIS error
Date: Wed, 08 Apr 2020 08:26:56 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-20744@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 774 bytes --]
New issue by flexibeast on void-packages repository
https://github.com/void-linux/void-packages/issues/20744
Description:
Installing and running `cmus` from the console results in an error message: "an error occured while initializing MPRIS". [This line of the cmus source](https://github.com/cmus/cmus/blob/d1290d50f9f7585c43b9e1326c0d6d1e0b4583f6/mpris.c#L491) suggests that `cmus` requires the presence of a session bus (cf. [the documentation for `sd_bus_default_user`](https://www.freedesktop.org/software/systemd/man/sd_bus_open.html)), and indeed, running `dbus-launch /bin/cmus` results in no error being reported on startup.
How should this be addressed? Should the `cmus` package be modified, or should upstream not be assuming the presence of a session bus?
next reply other threads:[~2020-04-08 6:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-08 6:26 flexibeast [this message]
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
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-20744@inbox.vuxu.org \
--to=flexibeast@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).