Version: (using KDE 4.3.2) Compiler: gcc-4.4.1 OS: Linux Installed from: Fedora RPMs Running Fedora 11 with the updates-testing repository. I updated qt and kdelibs from the repository a few days ago and am now having troubles with all password dialogs. When using three stars per character (System Settings::About Me::Show three bullets for each letter), password prompts are failing in one of two ways: * kopete, kwalletd (kwalletmanager, ksshaskpass, etc): A dialog is popped up. I can enter a password in the box. Three bullets are given per character. But when I click on ok, hit the <Enter> key on the keyboard, or Alt-O to try to make the Open button activate, the dialog doesn't go away. The Open button does visibly depress but simply comes back to the unclicked state and nothing happens. Clicking the Cancel button does close the window but doesn't get me closer to getting the password entered. * kscreenlocker: when I enter my password in the dialog box and hit enter, the dialog tells me that the password was incorrect and goes insensitive. kscreenlocker never removes the dialog from the screen and never gives me a new dialog to put a new password in. I have to log in at a console window and kill kscreenlocker to get back in. Previous (working): kdelibs-4.3.1-3.fc11.i586 qt-4.5.2-3.fc11.i586 Current (non-working): kdelibs-4.3.2-3.fc11.i586 qt-4.5.3-4.fc11.i586 This Debian bug report seems to be the same issue: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=550866 As given in that bug, I was able to workaround the issue by setting the number of bullets shown per character to one instead of three.
Archlinux bug report where the user reported that they had upgraded from qt-4.5.2 to 4.5.3 and the bug started. Downgraded qt to 4.5.2 and the bug stopped: http://bugs.archlinux.org/task/16478?dev=280
I can confirm the bad behavior here with kde-4.3.2 + qt-4.5.3 (kde-qt) combo.
I cannot confirm this with: qt-4.6.0-0.2.beta1.fc12.x86_64 kdelibs-4.3.2-4.fc12.x86_64 Qt bug that got fixed in 4.6.0?
Looks like this is an issue with Qt 4.5.3 specifically.
Still happens to me with: qt-4.6.0-0.2.beta1.fc11.i586 (kde-redhat-unstable) kdelibs-4.3.2-4.fc11.i586 (updates-testing) Perhaps something else that has been updated in F12 is the answer?
Created attachment 37953 [details] fix for qt-4.5.3 glib-event-loop regression Here's the regression we've found that contributes to the problem described here with password dialogs. Patch sent to nokia (no reply yet).
Already known by Nokia and fixed for 4.5.4. (I actually detected this regression before 4.5.3 - yay unittests, but Nokia forgot to backport the fix into the 4.5 branch, unfortunately; they did now) Meanwhile you can revert that one-liner, or apply the fix (git commit 063bded, or in patch format: http://www.davidfaure.fr/2009/qeventdispatcher_glib_fix.diff ) *** This bug has been marked as a duplicate of bug 210171 ***
Than reports that qeventdispatcher_glib_fix.diff doesn't fix the particular 3star echo problem reported here. for posterity, his upstream report is http://bugreports.qt.nokia.com/browse/QTBUG-5197 without comment yet.
And yet reverting the one-liner in qeventdispatcher_glib fixes it? That would be pretty bad then, it means Nokia's fix is incomplete. If that's the case, someone should contact Bradley T. Hughes <bradley.hughes@nokia.com> (btw the git ref I used was wrong, the git commit that is supposed to fix the glib-eventdispatcher regression is d0d0fdb8e46351b4ab8492de31e5363ef6662b57)
Thanks David, we're doing further testing to confirm.
I have added this patch to our Debian packages: - 0078-Fix-regressions-in-qeventloop-qtimer-and-qsocketnoti.patch Fix regressions in qeventloop, qtimer, and qsocketnotifier autotests. http://git.debian.org/?p=pkg-kde/qt4-x11.git;a=blob;f=debian/patches/0078-Fix-regressions-in-qeventloop-qtimer-and-qsocketnoti.patch;h=628f1cf4df6f0639fa22708179915ea7f7d5368d;hb=master
upon further testing, qeventdispatcher_glib_fix.diff is good (for me). false alarm it would seem.
OK, than produced a test case that still fails using qeventdispatcher_glib_fix.diff : kdialog --password "test" + 3star echo = clicking ok does nothing (still stuck)
Sure? I can't see much relation... Anyway, where does one configure 3-star echo?
There's at least 2 of us now that can reproduce it, fairly sure. Try for yourself, systemsettings -> About me, check "Show 3 bullets for each letter", and try kdialog --password "test"
admittedly, this is still almost certainly a qt bug/issue.
SVN commit 1083166 by cfeck: Fix paint recursion in "three bullet" password mode There are other issues related to "three bullet" mode, such as not being able to move cursor or select text. But simple typing and backspace should work without 100% CPU and hangs. Please test if this commit fixes this bug, it will be available with the KDE SC 4.4.0 release. CCBUG: 180482 CCBUG: 186724 CCBUG: 211250 CCBUG: 215380 CCBUG: 224693 M +10 -0 klineedit.cpp WebSVN link: http://websvn.kde.org/?view=rev&revision=1083166
SVN commit 1083167 by cfeck: Fix paint recursion in "three bullet" password mode (backport r1083166) CCBUG: 180482 CCBUG: 186724 CCBUG: 211250 CCBUG: 215380 CCBUG: 224693 M +10 -0 klineedit.cpp WebSVN link: http://websvn.kde.org/?view=rev&revision=1083167
Assuming the bug is fixed, since there was no further feedback. Please reopen if you see this issue with KDE SC 4.4.x.