From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: [ISSUE] pulseeffects: remove ConsoleKit2 as dependency?
Date: Sun, 06 Oct 2019 17:45:40 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-15183@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1028 bytes --]
New issue by b1scu1t on void-packages repository
https://github.com/void-linux/void-packages/issues/15183
Description:
### System
* xuname:
` Void 5.2.17_1 x86_64 GenuineIntel notuptodate rrrmFFFFF`
* package:
`pulseeffects-3.2.3_3`
### Expected behavior
Install and use pulseeffects without the ConsoleKit2 dependency.
### Actual behavior
ConsoleKit2 is roped in with the `pulseeffects` package, although `pulseaudio` doesn't need it, and apparently neither does `pulseeffects` according to a Reddit post [here](https://www.reddit.com/r/voidlinux/comments/c954df/pulseeffects_without_consolekit2/).
### Steps to reproduce the behavior
sudo xbps-install -S pulseeffects
To add to this, I had adopted `elogind` as a session manager, given that ConsoleKit2 was being dropped. With ConsoleKit2 being roped in, it automatically starts as a daemon with elogind; I don't think two session managers should run simultaneously.
I've also manually killed the daemon, and `pulseeffects` functions without it.
next reply other threads:[~2019-10-06 15:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-06 15:45 voidlinux-github [this message]
2019-10-08 22:26 ` voidlinux-github
2019-10-09 22:39 ` voidlinux-github
2019-10-09 22:39 ` voidlinux-github
2020-02-25 10:23 ` [ISSUE] [CLOSED] " xtraeme
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-15183@inbox.vuxu.org \
--to=voidlinux-github@inbox.vuxu.org \
--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).