Thanks to something that just seems like dependency flood to me, I now have to install a lot of packages I don't really want, such as consolekit. I don't care about seats or sessions, but I care about limiting the unnecessary resources that are used by my machine. Since I cannot purge consolekit anymore, it would be nice if debconf could at least ask me if I wanted to use it in the first place, and prevent the starting of console-kit-daemon in case I don't.
martin f krafft wrote: console-kit-daemon is only started on demand if other applications request it, so maybe you should revisit the apps that need CK. Disabling CK when other services need it doesn't sound a good idea to me. I'm closing this bug as I don't think it makes sense to add a debconf prompt and won't implement it. Michael
also sprach Michael Biebl <biebl@debian.org> [2009.08.30.0146 +0200]: /etc/X11/Xsession.d/90consolekit starts ck-launch-session. Anyway, how do I find out what uses consolekit? What would they need it for?
ck-launch-session is in some loop and causing crazy high loads. I don't care what it does. I don't want it. I tried to remove consolekit and it seems it wants to take Xorg along with it, which is nuts. I have since cleaned up /etc/X11/Xsession.d/ from that crap. Though still I don't understand why I can't just simply remove a optional package without breaking a normal X Debian box.
reopen 544147 thanks This is not resolved by closing the bug. hal and policykit depend on consolekit, but I don't *want* that functionality. I appreciate HAL, and if policykit were implemented right, that would make sense too, but I don't need consolekit. I don't have anyone else sitting on my chair^W seat, and I don't care about XDG sessions. I just want to be able to use X with a minimal window manager and some terminals, and I'd like to avoid the feature creep that freedesktop.org brings.
reassign 544147 dbus forcemerge 544483 544147 thanks martin f krafft wrote: consolekit (or more specifically all dbus activated system services) can be disabled, albeit in a rather hackish way, see my comment at [1] I guess what you want is best handled in #544483, so I'm reassigning and merging those two bugs. Michael [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=544483#42