smb4k in feisty hangs during session startup, waiting for DCop response
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
smb4k |
Fix Committed
|
Medium
|
Unassigned | ||
smb4k (Ubuntu) |
Fix Released
|
Medium
|
Rich Johnson |
Bug Description
Binary package hint: smb4k
During login to my KDE session I have smb4k restarted automatically by the session support. During that time I am prompted that 'DCOPServer' wants to access the KDE wallet, and for my password.
This access is really due to smb4k; I have verified that no other software started in the session asks for wallet access.
Anyway, smb4k hangs waiting for the response from a DCOP call during this time, and fails to mount any of my shares.
I captured a backtrace with a reasonable level of debug information; the hang is in the X ICE library, waiting for a DCOP response:
#0 0xb7fd1410 in __kernel_vsyscall ()
#1 0x4125f163 in __read_nocancel () from /lib/tls/
#2 0x433141ce in _kde_IceTransSo
buf=0x80eab40 "\002\001", size=8)
at /build/
#3 0x43313e7f in _kde_IceTransRead (ciptr=0x80eaa50, buf=0x80eab40 "\002\001",
size=8) at /build/
#4 0x4330dcff in _kde_IceRead (iceConn=0x80ea9d8, nbytes=8,
ptr=0x80eab40 "\002\001")
at /build/
#5 0x433124ef in KDE_IceProcessM
replyReadyR
at /build/
#6 0x432fdc49 in DCOPClient:
remObjId=
replyStruct
at /build/
#7 0x432fdf2d in DCOPClient:
remObjId=
replyType=
minor_opcode=2) at /build/
#8 0x43302977 in DCOPClient::call (this=0x80e9690, remApp=@0xbfc6c1f4,
remObjId=
replyType=
at /build/
#9 0x43305866 in DCOPRef:
args=
at /build/
#10 0x4330597e in DCOPRef:
args=
at /build/
#11 0x4388cd4f in KWallet:
ot=
at /build/
#12 0x43ccdb77 in Smb4KPasswordHa
from /usr/lib/
#13 0x43ccec58 in Smb4KPasswordHa
#14 0x43cc5de3 in Smb4KMounter::mount () from /usr/lib/
#15 0x43cca5b9 in Smb4KMounter::init () from /usr/lib/
#16 0x43cca939 in Smb4KMounter:
#17 0x4970bf00 in QObject:
#18 0x4970c878 in QObject:
#19 0x49a99fa2 in QTimer::timeout () from /usr/lib/
#20 0x49733ade in QTimer::event () from /usr/lib/
#21 0x496a2fa8 in QApplication:
#22 0x496a4dd7 in QApplication:
#23 0x434ece82 in KApplication:
event=
#24 0x496357a9 in QApplication:
#25 0x496959f3 in QEventLoop:
#26 0x4964a2e5 in QEventLoop:
#27 0x496bd67e in QEventLoop:
#28 0x496bd48e in QEventLoop::exec () from /usr/lib/
#29 0x496a4b51 in QApplication::exec () from /usr/lib/
#30 0x08054c6f in ?? ()
#31 0xbfc6cdf4 in ?? ()
#32 0x08055e80 in ?? ()
#33 0x00000000 in ?? ()
Changed in smb4k: | |
status: | Confirmed → Fix Committed |
status: | Confirmed → Fix Committed |
One other thing: if I kill smb4k and restart it within the session a Wallet query from 'smb4k' is shown; the entire process then completes successfully and works as expected.