Bug 197133 - no turn off or restart buttons in KDE w/ gnome-base/gdm-2.20.x
Bug#: 197133 Product:  Gentoo Linux Version: unspecified Platform: All
OS/Version: Linux Status: CLOSED Severity: normal Priority: P2
Resolution: FIXED Assigned To: kde@gentoo.org Reported By: admin@easyshellz.com
Component: KDE
URL: 
Summary: no turn off or restart buttons in KDE w/ gnome-base/gdm-2.20.x
Keywords:  
Status Whiteboard: 
Opened: 2007-10-26 14:08 0000
Description:   Opened: 2007-10-26 14:08 0000 
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

------- Comment #1 From Dan Coats 2007-10-26 18:09:04 0000 ------- 
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.

------- Comment #2 From Paul de Vrieze 2007-11-02 06:04:10 0000 ------- 
Created an attachment (id=134988) [details]
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)

------- Comment #3 From Paul de Vrieze 2007-11-02 08:42:33 0000 ------- 
Created an attachment (id=134991) [details]
There were some typo's in the previous one. Sorry for the inconvenience.

------- Comment #4 From Wulf Krueger (RETIRED) 2007-11-04 00:24:47 0000 ------- 
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.

------- Comment #5 From Jakub Moc (RETIRED) 2007-11-22 14:36:12 0000 ------- 
*** Bug 199983 has been marked as a duplicate of this bug. ***

------- Comment #6 From Billy DeVincentis 2007-11-23 00:08:09 0000 ------- 
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?

------- Comment #7 From Wulf Krueger (RETIRED) 2007-11-23 00:18:01 0000 ------- 
(In reply to comment #6)
> for  kde  3.5.8,  so  what  can  I  do  to  fix  my  2  boxes?

Update.

------- Comment #8 From Jakub Moc (RETIRED) 2007-11-23 12:11:12 0000 ------- 
*** Bug 199983 has been marked as a duplicate of this bug. ***

------- Comment #9 From Michael Mauch 2007-12-03 18:24:30 0000 ------- 
I removed the old /tmp/.gdm_socket and created a link instead:

  ln -s /var/run/gdm_socket /tmp/.gdm_socket 

Works for me.

------- Comment #10 From Billy DeVincentis 2007-12-03 19:02:16 0000 ------- 
I  have  updated,  I  now  have  emerge  kde  3.5.8  and  all  works  properly.