Bug 249602 - Dolphin requires username/password multiple times on network shares
Summary: Dolphin requires username/password multiple times on network shares
Status: RESOLVED DUPLICATE of bug 248340
Alias: None
Product: dolphin
Classification: Applications
Component: general (show other bugs)
Version: 16.12.2
Platform: Slackware Linux
: NOR normal
Target Milestone: ---
Assignee: Peter Penz
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-08-31 11:45 UTC by david.martin.it
Modified: 2010-09-12 16:04 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 david.martin.it 2010-08-31 11:45:28 UTC
Version:           unspecified (using KDE 4.5.0) 
OS:                Linux

When I access a network share with Dolphin for the first time, I insert username and password, and then I save the credentials on Kwallet.
Then I close and re-open Dolphin, I go to the network share, and Dolphin ask me for credentials three times. The credentials are already saved in the form, because Dolphin uses the credentials I saved on Kwallet.
I don't understand why Dolphin shows me the form with username and passowrd, I click "ok" and then Dolphin shows me the same form again for three times.
If I use Konqueror, it uses the credentials saved on Kwallet and access automatically the network share.

I am sure that this problem has appeared whit KDE 4.5.

Reproducible: Always

Steps to Reproduce:
1. create a network share (it is placed on a Linux server), samba configured with security = user;
2. access the network share and save credentials on Kwallet;
3. open dolphin and access the network share

Actual Results:  
Dolphin shows me the form in which username and password are already specified, I click "ok" and it shows me the same form two more times.

Expected Results:  
I have installed KDE 4.5 from Slackware packages created by Alien Bob
http://alien.slackbook.org/ktown/4.5.0/
Comment 1 FiNeX 2010-09-12 16:04:35 UTC

*** This bug has been marked as a duplicate of bug 248340 ***