Bug 351219

Summary:	kmail gui freeze apparently loosing time in QTextBlock::textDirection()
Product:	[Applications] kmail2	Reporter:	Diego Ercolani <diego.ercolani>
Component:	composer	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED UNMAINTAINED
Severity:	normal
Priority:	NOR
Version:	4.14.7
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Attachments:	perf data while composing a mail 1/2 perf data while composing a mail 2/2

Description Diego Ercolani 2015-08-12 11:52:19 UTC

kmail-4.14.9-24.2.x86_64
libqt4-4.8.6-4.4.1.x86_64
from openSUSE_13.2

Apparently there is an issue in the kmail GUI that freezes it whenever you click on something with the mouse.

I used "perf -a"  to record what happened while I was trying to compose a new email. I attach the perf.data file so you can analize


Reproducible: Always

Comment 1 Diego Ercolani 2015-08-12 11:59:33 UTC

Created attachment 94001 [details]
perf data while composing a mail 1/2

Comment 2 Diego Ercolani 2015-08-12 12:00:08 UTC

Created attachment 94002 [details]
perf data while composing a mail 2/2

Comment 3 Diego Ercolani 2015-08-13 08:04:58 UTC

As it was impossible for me to use kmail and do normal communication during working time it seem I solved the problem with this workaround:

I exited akonadi (akonadictl stop) and kmail (pkill kmail)

then I removed:

~/.kde4/share/apps/kmail2
~/.kde4/share/config/kmail2rc
~/.kde4/share/config/kmail-migratorrc
~/.kde4/share/config/kmail.eventsrc

really i noticed that under ~/.kde4/share/apps/kmail2/autosave there was a file that probably was a message autosave and was the problem, unfortunately I didn't backup it....

Comment 4 Denis Kurz 2017-06-23 20:00:32 UTC

This bug has never been confirmed for a KDE PIM version that is based on KDE Frameworks (5.x). Those versions differ significantly from the old 4.x series. Therefore, I plan to close it in around two or three months. In the meantime, it is set to WAITINGFORINFO to give reporters the oportunity to check if it is still valid. As soon as someone confirms it for a recent version (at least 5.1, ideally even more recent), I'll gladly reopen it.

Please understand that we lack the manpower to triage bugs reported for versions almost two years beyond their end of life.

Comment 5 Denis Kurz 2018-01-31 16:50:49 UTC

Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.1 aka 15.12, preferably more recent), please open a new one unless it already exists. Thank you for all your input.