Summary: | sys-apps/dbus[user-session] prevents login with message "Could not sync environment to dbus." | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Norman Back <gentoo3> |
Component: | Current packages | Assignee: | Freedesktop bugs <freedesktop-bugs> |
Status: | RESOLVED OBSOLETE | ||
Severity: | normal | CC: | chiqui_rupia, mgorny, perfinion, systemd |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | Suggested patch |
Description
Norman Back
2018-01-25 11:44:28 UTC
This issue is now resolved. I had sys-auth/consolekit in the world file. After many searches I eventually found https://forums.gentoo.org/viewtopic-t-1041644-start-0.html After emerge --deselect sys-auth/consolekit emerge --depclean -av removed sys-auth/consolekit I could then reboot and login with user-session enabled. Maybe enabling the use flag user-session should block sys-auth/consolekit when the systemd use flag is enabled. Created attachment 516786 [details, diff]
Suggested patch
Block on consolekit if user-session enabled
I wonder if there's ever any reason to have both systemd and consolekit installed at the same time. I wonder if there's ever any reason to have consolekit at all, given the existence of elogind now. legacy. Just forgot to remove the flag once the switch was over I guess. Note that consolekit is still being developed afaik so there might be a reason as to easily switch from one to another. I'm not sure that pam_systemd does anything useful when not booting with systemd. I've suffer same issue. My fresh install was 4-5 years ago, and upgrading it frequently after two-three weeks. Initially I started with init.d and kde4 and changed to systemd and kde5 when they came stable. In none upgrade -> clean deps, consolekit was been removed. Enabling/disabling consolekit USE make no change in the system, but consolekit package still remain in @world. It need to be uninstalled manually. I think the should be blocked by plasma-workspace ebuild, like attached patch suggest. (In reply to EFI from comment #6) > I've suffer same issue. My fresh install was 4-5 years ago, and upgrading it > frequently after two-three weeks. Initially I started with init.d and kde4 > and changed to systemd and kde5 when they came stable. In none upgrade -> > clean deps, consolekit was been removed. > Enabling/disabling consolekit USE make no change in the system, but > consolekit package still remain in @world. It need to be uninstalled > manually. > > I think the should be blocked by plasma-workspace ebuild, like attached > patch suggest. Thank you. You have succinctly described my experience. The difference is that my first install was in 2004 and my last fresh install was in 2008. My current install was upgraded from a fresh install made between 2004 and 2008. Since the fresh install, I have upgraded kde3 from via kde4 to plasma; migrated from 32 to 64bit and applied upgrades on a regular basis ( between 4 weekly and daily). None of these removed console kit from world, even though I used depclean ( once it had been released) after each upgrade. CCing consolekit maintainer in case of any opinion about whether consolekit should block systemd or not. consolekit is gone. |