Summary: | authorization dialog does not remember smb username and pass | ||
---|---|---|---|
Product: | [Unmaintained] kio | Reporter: | illumilore <illumilore> |
Component: | smb | Assignee: | Unassigned bugs mailing-list <unassigned-bugs> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | asturm, cfeck, frank78ac, nate |
Priority: | NOR | Keywords: | triaged |
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | unspecified | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
illumilore
2012-06-26 19:49:00 UTC
Are you indeed using the KSectetsService storage? It had been moved back to playground because of several issues, and until it is ready, it is suggested to use KWallet. My mistake, I had just selected the component that had keyring in the description This is not a kwallet-related problem, in my opinion. Not Dolphin-related either. Oops, kio/smb might be more accurate. Does this still happen with more modern versions of all relates software (KDE Plasma 5, KDE Frameworks, KWallet, KIO, libsmbclient, etc)? *** Bug 341593 has been marked as a duplicate of this bug. *** Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! Never seen this with Frameworks 5. My username and password are remembered just fine for password-protected SMB shares. Calling it fixed in the absence of new information from the bug submitter. |