Bug 160536 - Accessing password-protected samba shares sometimes fails
Summary: Accessing password-protected samba shares sometimes fails
Status: RESOLVED FIXED
Alias: None
Product: kdelibs
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: kdelibs bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-04-07 23:33 UTC by Ivo Anjo
Modified: 2009-04-03 16:59 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ivo Anjo 2008-04-07 23:33:07 UTC
Version:            (using KDE 4.0.3)
Installed from:    SuSE RPMs
OS:                Linux

I think this is somewhat related to bug 153982, but happens in a totally different way.

I have a home server with a password-protected samba share; when dolphin connects the first time to the share, it asks for the password and all is ok. If I close dolphin and, to re-open it after some time or if I do too many operations, I get a "Internal Error, Please send full bug report ... Unknown error condition in stat: Resource temporarily unavailable", and I can't connect to that share again without restarting.
Comment 1 Ivo Anjo 2008-04-08 19:31:36 UTC
Ok, so by chance today I discovered some more details on this bug. This seems to be related to bug 155008 , that is, this error occurs when dolphin tries to access passworded samba shares, and kded isn't running (I noticed that whenever I got this error I also lost my global shortcuts like alt+tab and alt+f2).

So this means that basically dolphin gets an internal error when accessing password-protected samba shares and kded isn't running. Starting kded fixes the problem immediately, I don't even have to restart dolphin.

Finally, I've re-tested bug 153982, and while it still happens, it doesn't seem to be related to this one (it happens with kded running), as I thought at first.
Comment 2 Dario Andres 2009-04-03 01:12:05 UTC
Any news on this ? Thanks
Comment 3 Ivo Anjo 2009-04-03 16:59:45 UTC
This seems to be fixed.