Bug 210171

Summary: kmail and kwallet password dialogs stopped working
Product: [Unmaintained] kmail Reporter: Dirk Heinrichs <dirk.heinrichs>
Component: generalAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED UPSTREAM    
Severity: normal CC: a.badger, faure, phobosk, rdieter, sjuengling
Priority: NOR    
Version: 1.12.2   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Dirk Heinrichs 2009-10-11 11:49:47 UTC 
Version:           1.12.2 (using 4.3.2 (KDE 4.3.2), Gentoo)
Compiler:          i686-pc-linux-gnu-gcc
OS:                Linux (i686) release 2.6.31.3

Since a few days, whenever a user needs to enter a password in either kmail's or kwallet's password dialog, only "Cancel" button works. Clicking "Ok" has no effect and the dialog stays on the screen.
Comment 1 Dirk Heinrichs 2009-10-11 18:05:27 UTC 
Looks like the problem came from updating QT to 4.5.3. After downgrading back to 4.5.2 everything was back to normal.
Comment 2 David Faure 2009-10-15 16:46:06 UTC 
Just a guess (because I know of one regression in 4.5.3), does
export QT_NO_GLIB=1
(and then restarting kmail from that terminal)
solve the problem?
Comment 3 Sascha Jüngling 2009-10-19 17:06:54 UTC 
This is not only restricted to KMail and kwallet, it also happens for Kopete's password dialogues if you want to log in to your messengers, it happens for Dolphin e.g. when you want to connect to FTP sites, it even happens for using kdesu and entering your root password.

An interesting hint posted by PhobosK on the Gentoo bugtracker for this problem [1]:

Minimize the dialogue after entering the credentials and pressing Return/Ok. It will successfully log in then.

What I also noted: After I hit the Ok button, kwalletd will usually fire up and eat about 60-80% CPU until I kill it. My laptop's fan starts going crazy, that's how I first noticed it.

David: Yes, exporting this var and starting from the same terminal did work.



[1]: http://bugs.gentoo.org/show_bug.cgi?id=288580#c1
Comment 4 David Faure 2009-10-20 23:47:24 UTC 
> David: Yes, exporting this var and starting from the same terminal did work

Then the bug is known and already fixed for Qt-4.5.4.

Meanwhile just apply git commit 063bded, or in patch format: http://www.davidfaure.fr/2009/qeventdispatcher_glib_fix.diff
Comment 5 David Faure 2009-10-29 19:48:16 UTC 
*** Bug 211250 has been marked as a duplicate of this bug. ***
Comment 6 PhobosK 2010-01-15 23:54:14 UTC 
Well the same bug reappears in Qt-4.6.0...