Bug 243697 - Apply button in "KMail options" dialog hangs UI.
Summary: Apply button in "KMail options" dialog hangs UI.
Status: RESOLVED WORKSFORME
Alias: None
Product: kmail2
Classification: Applications
Component: config dialog (show other bugs)
Version: 2.0.90
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords: akonadi-ports-regression, investigated, triaged
Depends on:
Blocks:
 
Reported: 2010-07-05 22:15 UTC by Alejandro Nova
Modified: 2018-10-21 04:48 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alejandro Nova 2010-07-05 22:15:53 UTC
Version:           2.0 beta1 (using Devel) 
OS:                Linux

When I hit "Apply" button in the KWin Options dialog, instead of OK button, the interface locks up and I have to kill KMail.

Reproducible: Always

Steps to Reproduce:
1. Open KMail 2.
2. Select Preferences | Configure KMail...
3. Change something.
4. Press Apply.

You get a consistent hang, and you have to kill the program.

Actual Results:  
Settings applied, hang.

Expected Results:  
Settings applied, and the capability to press "OK" button after "Apply", to get out of the dialog. KMail2 is usable normally.
Comment 1 Thomas McGuire 2010-07-06 13:22:27 UTC
I can not reproduce this.
Can you maybe attach GDB to the hanging KMail and get a backtrace?

Quoting http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports#How_to_create_useful_crash_reports:

"In case you want to attach to an existing process, run the following command in the shell: 
$ gdb someKDEapp pid

where pid is the process ID of the process you want to attach to. Once attached, and the process is in an infinite loop, after using the 'backtrace' command again a useful backtrace will appear. You can use 'continue' command to let the application run again and press Ctrl+C in gdb to be able to again enter commands."
Comment 2 Tobias Koenig 2010-12-12 13:33:38 UTC
Hej Alejandro,

any news on this issue? Can you still reproduce it with a current version (4.6beta)?

Ciao,
Tobias
Comment 3 Andrew Crouthamel 2018-09-20 22:02:36 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 4 Andrew Crouthamel 2018-10-21 04:48:34 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!