Bug 352911 - kwallet manager crashed if using gpg encryption and gpg key is expired
Summary: kwallet manager crashed if using gpg encryption and gpg key is expired
Status: RESOLVED WORKSFORME
Alias: None
Product: kwalletmanager
Classification: Applications
Component: general (other bugs)
Version First Reported In: unspecified
Platform: Fedora RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: Valentin Rusu
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-09-19 15:51 UTC by Michael Strobel
Modified: 2018-11-30 04:08 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Strobel 2015-09-19 15:51:02 UTC
Hello everyone,

my kwallet which uses gpg encryption crashed with general error since my gpg key was expired. The expiration took place after i created the wallet. Both happens on Fedora 22 and Debian stable (Jessie).

It would be very useful to add a meaningful error message.

Reproducible: Always

Steps to Reproduce:
1. create kwallet with gpg encryption
2. let gpg key expire
3. kwallet crashes on startup

Actual Results:  
general error (1 i think)


I prolonged the gpg key so i can't provide a crash log. If necessary i would change the expiration date back to provoke the error.
Comment 1 Valentin Rusu 2015-09-19 19:26:38 UTC
Can I have the crash log, please?
Comment 2 Andrew Crouthamel 2018-10-31 04:14:26 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 3 Bug Janitor Service 2018-11-15 10:55:56 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 4 Bug Janitor Service 2018-11-30 04:08:07 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!