Bug 321354

Summary: Attempts to open the wallet are made even if no proxy password has been entered
Product: [Applications] konversation Reporter: Sergey Zolotarev <szx>
Component: generalAssignee: Konversation Developers <konversation-devel>
Status: RESOLVED WORKSFORME    
Severity: normal CC: hein, peter.simonsson, szx
Priority: NOR    
Version: 1.5-rc1   
Target Milestone: ---   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Sergey Zolotarev 2013-06-19 08:54:49 UTC
When you enable proxy in connection settings Konversation will ask you to enter your KDE Wallet password on startup and additionally when you open settings (Settings -> Configure Konversation), even if you didn't specify a password for the proxy server.

Reproducible: Always




Konversation 1.5-master #4301
KDE Development Platform 4.10.4
Comment 1 Eike Hein 2013-06-27 13:59:56 UTC
I'm not sure there's a way around that since it needs to open the wallet to find out if there's a password in there. Peter?
Comment 2 Peter Simonsson 2013-06-28 20:09:08 UTC
yeah it needs to look if there's a password. A way around that is to check if a username has been specified I guess...
Comment 3 Peter Simonsson 2013-06-28 20:12:46 UTC
Or hmm that is stored in the wallet as well... maybe adding a setting which tells konversation if it should look in the wallet or not. Which is set when something is added to the wallet.
Comment 4 Andrew Crouthamel 2018-11-10 03:22:25 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 5 Andrew Crouthamel 2018-11-21 04:49:01 UTC
Dear Bug Submitter,

This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand.

Thank you for helping us make KDE software even better for everyone!
Comment 6 Sergey Zolotarev 2018-11-21 06:39:36 UTC
Hello,

Unfortunately I can't re-test this bug because I don't have KDE installed anymore, if nobody else has the same issue I wouldn't mind if you close it. Thank you.
Comment 7 Justin Zobel 2023-01-18 02:41:09 UTC
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 8 Bug Janitor Service 2023-02-02 05:00:51 UTC
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
mark the bug 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!
Comment 9 Bug Janitor Service 2023-02-17 03:48:36 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now 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

Thank you for helping us make KDE software even better for everyone!