Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#43590 - [ksshaskpass] Does not check if kwallet is already open
Attached to Project:
Arch Linux
Opened by abc (Xiflite) - Tuesday, 27 January 2015, 19:40 GMT
Last edited by Antonio Rojas (arojas) - Sunday, 20 September 2015, 09:02 GMT
Opened by abc (Xiflite) - Tuesday, 27 January 2015, 19:40 GMT
Last edited by Antonio Rojas (arojas) - Sunday, 20 September 2015, 09:02 GMT
|
DetailsDescription:
- have a kwallet timeout of 10 minutes - try for example to add multiple ssh-keys which are protected with a pass stored in kwallet - note, that you have to enter your kwallet passphrase every time though the wallet is still open Additional info: 5.2.0-1 Steps to reproduce: Try to access something with ksshaskpass multiple times within you kwallet timeout |
This task depends upon
Closed by Antonio Rojas (arojas)
Sunday, 20 September 2015, 09:02 GMT
Reason for closing: Upstream
Additional comments about closing: https://bugs.kde.org/show_bug.cgi?id=343 456
Sunday, 20 September 2015, 09:02 GMT
Reason for closing: Upstream
Additional comments about closing: https://bugs.kde.org/show_bug.cgi?id=343 456
Comment by Andrea Scarpino (BaSh) -
Wednesday, 28 January 2015, 07:50 GMT
- Field changed: Category (Packages: Extra → Upstream Bugs)
Please report upstream.
Comment by Antonio Rojas (arojas) -
Saturday, 19 September 2015, 22:50 GMT
What's the status of this? Did you report it upstream?
Comment by abc (Xiflite) -
Sunday, 20 September 2015, 08:57 GMT
I do not use KDE anymore since 2 weeks (when this bug still persist). I reported the bug upstream but can't remember of any dev feedback.