Bug 299605 - [4.8.3 regression] Unable to access smb share
Summary: [4.8.3 regression] Unable to access smb share
Status: RESOLVED FIXED
Alias: None
Product: kio
Classification: Frameworks and Libraries
Component: smb (show other bugs)
Version: 4.8
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-05-08 07:20 UTC by karaluh
Modified: 2014-10-07 12:27 UTC (History)
2 users (show)

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 karaluh 2012-05-08 07:20:27 UTC 
As in summary. I had passwords for the shares i'm accessing stored, however I get the pasword prompt now. When I provide correct user and password, the dialog box reappears. 4.8.2 was working fine.

Reproducible: Always
Comment 1 Patrick Peronny 2012-06-26 07:32:24 UTC 
I have the same or a similar problem since kde 4.8.3 from Debian testing repository. Except than I don't have the password prompt, I have directly "access refused".
Tried to delete the kwallet entry for these shares and upgraded smbclient to 3.6.5 but same result no password prompt.
Worked fine before the upgrade (kde 4.7.4).

I have to mount manualy with cifs/fstab if I want to access to something on the network.
Comment 2 Patrick Peronny 2012-06-26 12:04:49 UTC 
(In reply to comment #1)
> I have the same or a similar problem since kde 4.8.3 from Debian testing
> repository. Except than I don't have the password prompt, I have directly
> "access refused".
> Tried to delete the kwallet entry for these shares and upgraded smbclient to
> 3.6.5 but same result no password prompt.
> Worked fine before the upgrade (kde 4.7.4).
> 
> I have to mount manualy with cifs/fstab if I want to access to something on
> the network.

Wrong ticket for me finaly. Now i have the same problem with kio_ftp and kio_fish, sorry.
Comment 3 Dawit Alemayehu 2013-11-19 05:27:18 UTC 
Is this regression still present for you? I cannot personally reproduce the issue in KDE 4.11 or higher.
Comment 4 Patrick Peronny 2014-10-07 09:16:22 UTC 
Sorry for the delay, I didn't see the message (and not sure if it's for me) . Everything works fine since 4.10+ at least.