Bug 244903

Summary:	KWallet not saving crash report user name and password
Product:	[Applications] drkonqi	Reporter:	Tim <tim.klassen>
Component:	general	Assignee:	Unassigned bugs mailing-list <unassigned-bugs>
Status:	RESOLVED WORKSFORME
Severity:	normal	CC:	mail, valir
Priority:	NOR	Keywords:	triaged
Version:	unspecified
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Tim 2010-07-16 22:15:27 UTC

Version:           unspecified (using Devel) 
OS:                Linux

When a crash occurs in KDE, and the bug crash reporter runs... there is a point where I am requested for my kde bug user name and password... at which time I have the option checked to save the information in KWallet. However, the next time the bug reporter runs I have to enter the user name and password again (it wasn't saved the in the prior session).

Reproducible: Always

Steps to Reproduce:
1) a kde crash occurs
2) crash (bug) reporter opens
3) a few windows in...at the request of the reporter I enter my password and user name (and make sure the save in Kwallet option is checked)
4)  finish the crash report
5)  repeat #1 and #2
6)  the user name and password should be saved in Kwallet from the previous run, but I have to manually enter the information again because it was not saved.

Actual Results:  
Kwallet does not save user name and password in kde crash reporter.

Expected Results:  
The user name and password should be saved, but isn't... each time I have to manually enter the info.

Comment 1 Tim 2010-07-16 22:18:29 UTC

additional details of the above report:

KDE Platform Version: 4.4.92 (KDE 4.4.92 (KDE 4.5 RC2))
Qt Version: 4.7.0
Operating System: Linux 2.6.32-23-generic x86_64
Distribution: KXStudio 10.04 LTS

Comment 2 Valentin Rusu 2013-09-03 21:07:50 UTC

This is not a kwallet bug AFAICT and perhaps it has already been fixed by now. Reassigning.

Comment 3 Jekyll Wu 2013-09-04 04:06:56 UTC

I haven't personally encounterd such problem, neither did I read similar reports between year 2011 and now. 

Please try some recent releases (4.10.5 or 4.11.1) to see whether the probem still exist.

Comment 4 Andrew Crouthamel 2018-09-24 02:21:33 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 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!

Comment 5 Andrew Crouthamel 2018-10-27 04:22:12 UTC

Dear Bug Submitter,

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!