Created attachment 408553 [details]
Video showing the problem. The start may be a bit flaky.
Description of problem:
When I try to access a remote folder using SMB, KDE shows the password entry dialog even though the correct password was already saved. Confirming the dialog (without changing the login details) works fine, but the same dialog is shown multiple times when trying to access a resource and the user has to confirm the dialog (again, without changing anything) multiple times.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Open the run dialog and type an SMB resource address. For example trying to access the directory "Product Documents" under the share "Documents" on the server "negro" using the username "oded.a", the address would be smb://oded.a@negro/Documents/Product Documents
Need to confirm 5 password dialogs
Dolphin now shows the content of the directory and browsing is possible without more password dialogs popping out
If the password is already saved and it works, KDE should continue without needing any more password confirmations. At worst 1 password confirmation may be justified, but not 5.
Please see attached video. In the video you can see that there is one password confirmation dialog before Dolphin actually starts (you can see its a password dialog started by the desktop because its centered on the desktop. also I have the KWin effect of darkening parents of modal dialogs, which you can see in action later in the vide). Then Dolphin starts and we get two more desktop confirmation dialogs as the path in the Dolphin window gets slowly built, then we get another password confirmation dialog from Dolhin (you can see it is centered on the Dolphin window) and finally another desktop password confirmation dialog.
kio_smb is in kdebase-runtime.
This is a issue which needs to be reported upstream. Please file a report at
Please add upstream report info to this report. We will monitor the upstream
report for a resolution.
Thanks for the report
Fedora Bugzappers volunteer triage team
This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '13'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 13's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 13 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here:
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.