Bug 268965 - kdesu silently hangs and never exits when there's a stale lock left behind.
Summary: kdesu silently hangs and never exits when there's a stale lock left behind.
Status: RESOLVED DUPLICATE of bug 208979
Alias: None
Product: kdesu
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Slackware Linux
: NOR normal
Target Milestone: ---
Assignee: kdesu bugs tracker
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-03-20 16:01 UTC by I'm anonymous. Delete me.
Modified: 2011-04-09 11:35 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description I'm anonymous. Delete me. 2011-03-20 16:01:44 UTC 
Version:           1.0 (using KDE 4.5.5) 
OS:                Linux

kdesu started to hang a while ago.
Since it just silently hung, I didn't know what was happening.
kdesu never made a password dialog, and it just hung forever.
After a significant amount of search, I was reminded that strace could be useful.
"strace kdesu foobar" hung at the line, connect(9, {sa_family=AF_FILE, path="/tmp/ksocket-$USER/kdesud_:0"...}, XX.

So I googled the line, and I found http://forums.gentoo.org/viewtopic-p-5716721.html?sid=1253a2f9945bd29f678456722ac62c2c.

The solution was to remove the lock file, /tmp/ksocket-$USER/kdesud_:0.

I think kdesu at least has to notify a user of a stale lock so that one can remove it and make kdesu work again.
Or kdesu can be modified never to leave a stale lock.

Since I don't know how to create a stale lock file, I don't know how to reproduce it, but it seems certainly reproducible.

Reproducible: Sometimes
Comment 1 Oswald Buddenhagen 2011-04-09 11:35:03 UTC 

*** This bug has been marked as a duplicate of bug 208979 ***