| Summary: | if consolekit does not set login-session-id = '' or does not find DBUS session-bus system should not soft lock | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | turtle <turtle> |
| Component: | [OLD] KDE | Assignee: | Gentoo KDE team <kde> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | ||
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
turtle
2011-11-29 19:37:48 UTC
Did you start dbus? Hi thanks dbus is started. ps -C dbus-launch -o pid= 3447 /etc/init.d/dbus status * status: started This is the worst and most interesting problem I have had yet in 8 years of using Gentoo. I now suspect it is due to pam_mount being installed even though I currently do not use it. Anything you want me to do and I'll do it right away. Thanks I guess you have glib-networking installed see bug #365479. Try one of the suggested workarounds in the comments of the mentioned bug or try to upgrade to KDE 4.7.3 (note KDE 4.7.3 is in stabilisation, will hit stable tree soon). (In reply to comment #3) > I guess you have glib-networking installed see bug #365479. Try one of the > suggested workarounds in the comments of the mentioned bug or try to upgrade to > KDE 4.7.3 (note KDE 4.7.3 is in stabilisation, will hit stable tree soon). My issue is this set up is too fragile; any number of things (user mis configurations, bugs in updates, weird combinations of DE of software, python issues etc) will cause applications to not find session bus or cause garbled or incomplete data in the session. Problems in this new fangled dbus *kit stuff should not render a system frozen. This is a bug about redundancy and robustness. For example I am doing a emerge -e system right now that has brought in a python update which broke wicd. If I try to start wicd-cli I get: wicd-cli Traceback (most recent call last): File "/usr/share/wicd/cli/wicd-cli.py", line 19, in <module> import dbus ImportError: No module named dbus But my system does not soft lock. If login-session-id = cant be null openrc should kill anything that will soft lock cause of that and throw a legable error message on the console. Openrc should kill processes depending on session bus *kit stuff in this case. OR Gentoo should provide a way to manually set login-session-id Regarding glib-networking and that other bug; I had done a emerge -C glib-networking and no change. To my surprise it kept getting pulled back in by revdep-rebuild. There is no blocker in glib-networking and that bug 365479 is resolved. The commenter's on that bug cant reproduce the problem. I need KDE apps for work so I uninstalled xfce and recompiled the gimp with -webkit and that keeps it out of my system. And I still experience softlock. This bug 387147 is close to my first problem here is my forums post for more description:http://forums.gentoo.org/viewtopic-t-901458-highlight-.html I also have the problem right after logging in to KDE or Xfce not when calling xfce4-session-logout. But I digress it is not about me, I just feel like the whole JustWorks(tm) thing is too fragile for Gentoo. Please close this bug as a duplicate of bug 387147 and reclassify as testing has determined this is not related to KDE. last comment on robustness aside the bug is upstream: http://sourceforge.net/tracker/?func=detail&aid=3407320&group_id=41452&atid=430593 Original problem of "logging into KDE or xfce causes soft lock of system due to no memory." Top shows nothing in particular eating the memory. dbus kit stuff using pam might be related or it was just a compound problem after an update. emerge -av =pam_mount-2.10 and masking < pam_mount-2.10 will fix the problem. *** This bug has been marked as a duplicate of bug 387147 *** |
