Github messages for voidlinux
 help / color / mirror / Atom feed
* [ISSUE] pulseeffects: remove ConsoleKit2 as dependency?
@ 2019-10-06 15:45 voidlinux-github
  2019-10-08 22:26 ` voidlinux-github
                   ` (3 more replies)
  0 siblings, 4 replies; 5+ messages in thread
From: voidlinux-github @ 2019-10-06 15:45 UTC (permalink / raw)
  To: ml

[-- 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.

^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2020-02-25 10:23 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-10-06 15:45 [ISSUE] pulseeffects: remove ConsoleKit2 as dependency? voidlinux-github
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

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).