Bug 188144

Summary: Fails to store sever identification, so it asks each time
Product: [Unmaintained] kdelibs Reporter: Dieter Ernst <DREbs_lnx>
Component: generalAssignee: kdelibs bugs <kdelibs-bugs>
Status: RESOLVED WORKSFORME    
Severity: normal CC: cfeck
Priority: NOR    
Version: 4.2   
Target Milestone: ---   
Platform: openSUSE   
OS: Unspecified   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: first dialog that shows up
second message, through which I select to store the certificate permanently

Description Dieter Ernst 2009-03-26 09:42:40 UTC
Version:            (using KDE 4.1.4)
Installed from:    SuSE RPMs

Each time K-Mail downloads my E-Mails from the server, it displays the invalid/expired certificate message. I select to accept the certificate and store it permanently, yet the message display again the next time. This did not happen before, and the same installation for other users on my PC do not show this problem. My guess is, that storing the certificate fails because of a permission problem in my local file system. Not knowing where k-Mail tryes to store the certificates, I cannot help it.

What should I do?
Comment 1 Dieter Ernst 2009-03-26 09:47:20 UTC
Created attachment 32401 [details]
first dialog that shows up
Comment 2 Dieter Ernst 2009-03-26 09:48:36 UTC
Created attachment 32402 [details]
second message, through which I select to store the certificate permanently
Comment 3 Dieter Ernst 2010-10-06 11:37:50 UTC
For different reasons I changed to thunderbird as e-mail client, so I did not follow up the bug anymore.
Comment 4 Christoph Feck 2010-10-06 12:54:13 UTC
... which doesn't mean it is fixed.
Comment 5 Andrew Crouthamel 2018-11-05 03:12:21 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 6 Andrew Crouthamel 2018-11-17 05:02:25 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 7 Justin Zobel 2022-12-18 08:18:08 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-01-02 05:25:53 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-01-17 05:17:20 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!