Summary: | cannot run xfdesktop | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Miroslav Šulc <fordfrog> |
Component: | Current packages | Assignee: | XFCE Team <xfce> |
Status: | VERIFIED FIXED | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Miroslav Šulc
2010-11-18 09:30:07 UTC
I hit this when I upgraded and has a stale xfconfd running. Did you reboot or anything? sorry, i did not notice your answer. i have the problem still till now, my laptop rebooted many times. xfdesktop-4.7.3 fixes the problem. it still complains that it cannot connect to session manager as "SESSION_MANAGER environment variable not defined" but it runs and displays the desktop. (In reply to comment #3) > xfdesktop-4.7.3 fixes the problem. good. closing then. > it still complains that it cannot connect to > session manager as "SESSION_MANAGER environment variable not defined" but it > runs and displays the desktop. How do you start Xfce ? Does that happen also if you run Xfce from a new user (like from a empty user directory, empty Xfce configs) ? It should definately be set. Please open a new bug for this if it's a problem and it persists. $ echo $SESSION_MANAGER local/unique:@/tmp/.ICE-unix/20461,unix/unique:/tmp/.ICE-unix/20461 i use slim as login screen so i guess it is slim or xdm or what is it that starts xfce. but it has no negative effect on my xfce it seems, unless it is the cause of not being able to shutdown system from xfce anymore, which worked before last big update of xfce which was week or two back iirc. but i did not have time to dig deeper into this issue yet. (In reply to comment #5) > i use slim as login screen so i guess it is slim or xdm or what is it that > starts xfce. but it has no negative effect on my xfce it seems, unless it is > the cause of not being able to shutdown system from xfce anymore, which worked > before last big update of xfce which was week or two back iirc. but i did not > have time to dig deeper into this issue yet. > Oh, I see. Yes, SLIM was broken until 1.3.2-r3 (bug 346037). Still needs to be stabilized. And you still need to edit /etc/pam.d/system-login by hand and remove 'nox11' parameter from 'pam_ck_connector.so' line for either SLIM or XDM to work (bug 342345). Otherwise ConsoleKit session is never initialized properly, and xfce4-session would propably fail one way or another... samuli, thanks for the hints. i have latest slim as i am on ~amd64 and i changed /etc/pam.d/system-login according to your advice but it seems to have no effect on my system. thinks work still the same, echo $SESSION_MANAGER shows nothing in terminal but xfce seems to work normally, except the shutdown stuff, but i can live with that for now :-) (In reply to comment #7) > samuli, thanks for the hints. i have latest slim as i am on ~amd64 and i > changed /etc/pam.d/system-login according to your advice but it seems to have > no effect on my system. thinks work still the same, echo $SESSION_MANAGER shows > nothing in terminal but xfce seems to work normally, except the shutdown stuff, > but i can live with that for now :-) > Here's some more (propably more suitable for forums or IRC though. Feel free to find me at Freenode if you can't figure it out): Also make sure to launch Xfce with 'exec ck-launch-session startxfce4' from SLIM (or any other). To include the ck-launch-session there. And obviously make sure /etc/init.d/consolekit is running. Then you should see 'active = TRUE' with 'ck-list-sessions' inside X. Also xfce4-session prefers sys-power/upower for those operations, but can also use sudo or hal... so any of those 3 needs to be manually installed. They're runtime-only deps. |