[Bug 268965] New: kdesu silently hangs and never exits when there's a stale lock left behind.
crockabiscuit at yahoo.com
crockabiscuit at yahoo.com
Sun Mar 20 15:01:44 GMT 2011
https://bugs.kde.org/show_bug.cgi?id=268965
Summary: kdesu silently hangs and never exits when there's a
stale lock left behind.
Product: kde
Version: 1.0
Platform: Slackware Packages
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: general
AssignedTo: unassigned-bugs at kde.org
ReportedBy: crockabiscuit at yahoo.com
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
--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the Unassigned-bugs
mailing list