smb4k in feisty hangs during session startup, waiting for DCop response

[Daniel Pittman]

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/i686/cmov/libpthread.so.0
#2 0x433141ce in _kde_IceTransSocketRead (ciptr=0x80eaa50,
    buf=0x80eab40 "\002\001", size=8)
    at /build/buildd/kdelibs-3.5.6/./dcop/KDE-ICE/Xtranssock.c:1710
#3 0x43313e7f in _kde_IceTransRead (ciptr=0x80eaa50, buf=0x80eab40 "\002\001",
    size=8) at /build/buildd/kdelibs-3.5.6/./dcop/KDE-ICE/Xtrans.c:845
#4 0x4330dcff in _kde_IceRead (iceConn=0x80ea9d8, nbytes=8,
    ptr=0x80eab40 "\002\001")
    at /build/buildd/kdelibs-3.5.6/./dcop/KDE-ICE/misc.c:249
#5 0x433124ef in KDE_IceProcessMessages (iceConn=0x80ea9d8, replyWait=0xbfc6bf58,
    replyReadyRet=0xbfc6bfa8)
    at /build/buildd/kdelibs-3.5.6/./dcop/KDE-ICE/process.c:153
#6 0x432fdc49 in DCOPClient::callInternal (this=0x80e9690, remApp=@0xbfc6c1f4,
    remObjId=@0xbfc6c1fc, remFun=@0xbfc6c0e4, data=@0xbfc6c258,
    replyStruct=0xbfc6c004, useEventLoop=false, timeout=-1, minor_opcode=2)
    at /build/buildd/kdelibs-3.5.6/./dcop/dcopclient.cpp:1931
#7 0x432fdf2d in DCOPClient::callInternal (this=0x80e9690, remApp=@0xbfc6c1f4,
    remObjId=@0xbfc6c1fc, remFun=@0xbfc6c0e4, data=@0xbfc6c258,
    replyType=@0xbfc6c250, replyData=@0xbfc6c248, useEventLoop=false, timeout=-1,
    minor_opcode=2) at /build/buildd/kdelibs-3.5.6/./dcop/dcopclient.cpp:1821
#8 0x43302977 in DCOPClient::call (this=0x80e9690, remApp=@0xbfc6c1f4,
    remObjId=@0xbfc6c1fc, remFun=@0xbfc6c0e4, data=@0xbfc6c258,
    replyType=@0xbfc6c250, replyData=@0xbfc6c248, useEventLoop=false, timeout=-1)
    at /build/buildd/kdelibs-3.5.6/./dcop/dcopclient.cpp:1765
#9 0x43305866 in DCOPRef::callInternal (this=0xbfc6c1f4, fun=@0xbfc6c2a0,
    args=@0xbfc6c260, data=@0xbfc6c258, useEventLoop=NoEventLoop, timeout=-1)
    at /build/buildd/kdelibs-3.5.6/./dcop/dcopref.cpp:77
#10 0x4330597e in DCOPRef::callInternal (this=0xbfc6c1f4, fun=@0xbfc6c2a0,
    args=@0xbfc6c260, data=@0xbfc6c258)
    at /build/buildd/kdelibs-3.5.6/./dcop/dcopref.cpp:52
#11 0x4388cd4f in KWallet::Wallet::openWallet (name=@0xbfc6c328, w=0,
    ot=KWallet::Wallet::Synchronous)
    at /build/buildd/kdelibs-3.5.6/./dcop/dcopref.h:523
#12 0x43ccdb77 in Smb4KPasswordHandler::open_close_wallet ()
   from /usr/lib/libsmb4kcore.so.1
#13 0x43ccec58 in Smb4KPasswordHandler::readAuth () from /usr/lib/libsmb4kcore.so.1
#14 0x43cc5de3 in Smb4KMounter::mount () from /usr/lib/libsmb4kcore.so.1
#15 0x43cca5b9 in Smb4KMounter::init () from /usr/lib/libsmb4kcore.so.1
#16 0x43cca939 in Smb4KMounter::qt_invoke () from /usr/lib/libsmb4kcore.so.1
#17 0x4970bf00 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#18 0x4970c878 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#19 0x49a99fa2 in QTimer::timeout () from /usr/lib/libqt-mt.so.3
#20 0x49733ade in QTimer::event () from /usr/lib/libqt-mt.so.3
#21 0x496a2fa8 in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3
#22 0x496a4dd7 in QApplication::notify () from /usr/lib/libqt-mt.so.3
#23 0x434ece82 in KApplication::notify (this=0xbfc6cdf4, receiver=0x80e72d8,
    event=0xbfc6cb38) at /build/buildd/kdelibs-3.5.6/./kdecore/kapplication.cpp:550
#24 0x496357a9 in QApplication::sendEvent () from /usr/lib/libqt-mt.so.3
#25 0x496959f3 in QEventLoop::activateTimers () from /usr/lib/libqt-mt.so.3
#26 0x4964a2e5 in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3
#27 0x496bd67e in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
#28 0x496bd48e in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
#29 0x496a4b51 in QApplication::exec () from /usr/lib/libqt-mt.so.3
#30 0x08054c6f in ?? ()
#31 0xbfc6cdf4 in ?? ()
#32 0x08055e80 in ?? ()
#33 0x00000000 in ?? ()

[Daniel Pittman (daniel-rimspace)]

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.

[Pierre Buard (pierre-buard)]

I experience the same thing on edgy.

[Rich Johnson (nixternal)]

Marking confirmed due to responses. I will look into this and see if the Smb4k devs have anything new for me. Thanks for the report.

[Rich Johnson (nixternal)]

If you wouldn't mind testing this to see if this issue has been fixed in the newer release I would greatly appreciate it. If this doesn't work, then just remove this one and reinstall the previous version from the repositories. Thanks!

[Pierre Buard (pierre-buard)]

0.8.3 doesn't solve the problem.

[Rich Johnson (nixternal)]

lovely :) I guess it is time to take this upstream then. Thanks for your response.

[Rich Johnson (nixternal)]

until I can figure out how to add the bug for upstream..here is the link for the upstream report.

https://developer.berlios.de/bugs/?func=detailbug&bug_id=11189&group_id=769

[Rich Johnson (nixternal)]

http://developer.berlios.de/bugs/?func=detailbug&bug_id=11189&group_id=769

[Rich Johnson (nixternal)]

Awaiting for Debian Unstable update. Once that is complete, I will go ahead and apply the patch I created to fix this, unless of course Debian decides to apply it before getting it uploaded.

[Rich Johnson (nixternal)]

release 0.8.4 has fixed this issue. Thanks.