When using kde and gdm-2.20.* apon clicking the logout button from kmenu, you no longer get the "turn off" or "restart" buttons. After some investigation I found that the socket has changed paths, and this should be modified in the ebuild, either to one specific location of at least creating a symlink to it. Path changed from /tmp/.gdm_socket to /var/run/gdm_socket . Reproducible: Always Steps to Reproduce: 1.run any kde version in portage 2. use gdm 2.20.0 or 2.20.1 3. login to kde and select kmenu logout Actual Results: Only the "End Current Session" and "cancel" appears. Expected Results: To have 4 Buttons, 1.End Current Session 2.Turn off Computer 3.Restart Computer 4.Cancel A simple symlink does work ln -s /var/run/gdm_socket /tmp/.gdm_socket I did find a ubuntu bug about It when searching , thats how I figure out it was the socket. https://bugs.launchpad.net/ubuntu/+source/kdebase/+bug/64695
simply put stable kde and stable gdm are fine (kde knows where the gdm socket is) but ~arch kde does not know where ~arch gdm socket is.
Created attachment 134988 [details, diff] Fix to be applied to ksmserver (kdebase) to fix this. I've hit this too, and as it is annoying (and I clean my /tmp dir automatically) I've created the above fix. It will check for the new place to exist (with a stat call) and in that case have the logic connect there instead instead of the /tmp place. The code I added does not do further checks on the file, so in the case where a hacker were to influence the socket in the new location the existing security of ksmserver on attacks at /tmp would have to handle it. (In short, this patch might have security issues, but I don't know. I do know it works)
Created attachment 134991 [details, diff] There were some typo's in the previous one. Sorry for the inconvenience.
Thanks, Paul! I've taken a slightly different patch from upstream's SVN but your help here is really appreciated. This issue is fixed in 3.5.8-r1 of both kdebase and ksmserver. Fixed in CVS.
*** Bug 199983 has been marked as a duplicate of this bug. ***
stable kde and stable gdm are not fine, I run both x86 and amd64 on 2 different machine both of which are running the stable version kde 3.5.7 and gnome 2.20, both have the problem and you patch is for kde 3.5.8, so what can I do to fix my 2 boxes?
(In reply to comment #6) > for kde 3.5.8, so what can I do to fix my 2 boxes? Update.
I removed the old /tmp/.gdm_socket and created a link instead: ln -s /var/run/gdm_socket /tmp/.gdm_socket Works for me.
I have updated, I now have emerge kde 3.5.8 and all works properly.
