Red Hat Bugzilla – Bug 682474
qt 1:4.7.1-17.fc14 causes kmail composer lockup
Last modified: 2011-06-03 13:33:42 EDT
Description of problem:
qt 1:4.7.1-17.fc14 appears to cause kmail to lockup when you are trying to compose an email. The result is that I cannot send email.
Version-Release number of selected component (if applicable):
every time, though the timing of lockup is variable.
Steps to Reproduce:
1. start kmail
2. create a new email
3. spend some time composing an email, or just attempt to send the email
kmail locks up and does not respond to mouse clicks. When the cursor passes over the text edit area for the email being composed, it vanishes.
I expected to be able to create and send email.
I was able to work around this with Kevin_Kofler's help. I downgraded qt (and its subpackages, and qt-sqlite) to 4.7.1-7 using http://kojipkgs.fedoraproject.org/packages/qt/4.7.1/7.fc14/i686/qt-4.7.1-7.fc14.i686.rpm and related files.
After logging out of KDE and back in, I could once again compose email messages.
The lockup would occur after I'd been typing for a while, and possibly alt-tabbing to other applications while I was composing an email. Sometimes I could finish typing the email (such as by making a very short test message), and then hitting Ctrl-Enter to send the message would trigger the lockup. Since the test message I was doing was to an address for which I had encryption configured, the next step was for kmail to prompt for my passphrase. Therefore I don't think anything in the network or transport side of things plays a part in this bug.
When kmail locked up, I would click on the [X] to close it, and would shortly be prompted to terminate the non-responding application.
On my currently working system:
$ rpm -qa | grep -e "qt.*-4.7.1"
This is a Dell XPS M1330 laptop.
If I can do anything to assist in debugging this, email me at firstname.lastname@example.org, or look for me as retracile on freenode.
I suspect that it's the QTextBrowser regression fixes which caused yet another regression. (Grrr, I wonder if we should just revert the whole thing to the 4.7.0 code before the "performance optimization" which broke everything, with patch on top of patch fixing regressions and causing more. :-( ) We're going to have a 4.7.2 build to test soon, but I'm not sure it'll help. The patches in 4.7.1-17 are from what has since become 4.7.2.
Is this still a problem or reproducible with latest updates?
I have been on qt-4.7.2-8.fc14.i686 since Apr 23, 2011, and have not been having this problem any more.