Bug 307961 - kmail2 ceases to repsond (hangs), then after closure, refuses to start
Summary: kmail2 ceases to repsond (hangs), then after closure, refuses to start
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail2
Classification: Applications
Component: general (show other bugs)
Version: 4.8.5
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-10-06 07:48 UTC by Parameshwara Bhat
Modified: 2017-01-07 22:36 UTC (History)
0 users

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Parameshwara Bhat 2012-10-06 07:48:37 UTC
A few times in a work-day, kmail2 for no apparent reasons just freezes. One cannot even highlight and copy from kmail2.The rest of the desktop is fine.

This most of the times I have faced switching from another application to kmail2. But no other application shows this behaviour.

After freezing, I can get the KDE 'Terminator' dialog by clicking on window close cross, kmail disappears.

When I type kmail again in krunner, I can see it bouncing for quite some time and then stop. In the process viewer I can see two instances of kmail .Starting kmail2 from commandline on Konsole, does not output any message other than something like Qdbus started before qcoreapplication.

If I log-out,re login, it will run again.

Reproducible: Always

Steps to Reproduce:
1.I cannot reproduce it as I do not know what triggers it.But this happens by itself a few times in working day.
2.
3.
Comment 1 Denis Kurz 2016-09-24 18:15:56 UTC
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of kmail2 (version 5.0 or later, as part of KDE Applications 15.12 or later), it gets closed in about three months.
Comment 2 Denis Kurz 2017-01-07 22:36:01 UTC
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.