Version: (using Devel) Compiler: gcc-4.4.2 OS: Linux Installed from: Compiled sources Double-clicking an extender applet's title bar in order to minimize it freezes the plasma panel. The extender is minimized nonetheless, and stays responsive (e.g. I can restore it again and work with it). The panel does not accept any input. Double-clicking a minimized extender restores it and does NOT freeze the panel. Also, using the top-left icon (single click) works fine for both minimize and restore. I've attached gdb during the freeze and got the following backtrace: Thread 2 (Thread 0x7f70d22d6710 (LWP 9841)): #0 0x00007f70ef64d6dc in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0 #1 0x00007f70ef8db06b in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib64/qt4/libQtCore.so.4 #2 0x00007f70ebee613c in QHostInfoAgent::run() () from /usr/lib64/qt4/libQtNetwork.so.4 #3 0x00007f70ef8da0a5 in QThreadPrivate::start(void*) () from /usr/lib64/qt4/libQtCore.so.4 #4 0x00007f70ef648b24 in start_thread () from /lib/libpthread.so.0 #5 0x00007f70f228675d in clone () from /lib/libc.so.6 #6 0x0000000000000000 in ?? () Thread 1 (Thread 0x7f70f2965780 (LWP 9840)): #0 0x00007f70f227cf33 in poll () from /lib/libc.so.6 #1 0x00007f70e8604cac in g_main_context_iterate () from /usr/lib/libglib-2.0.so.0 #2 0x00007f70e8604ff0 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #3 0x00007f70ef9f5873 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/qt4/libQtCore.so.4 #4 0x00007f70eed2d81e in QGuiEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/qt4/libQtGui.so.4 #5 0x00007f70ef9caec2 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/qt4/libQtCore.so.4 #6 0x00007f70ef9cb294 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/qt4/libQtCore.so.4 #7 0x00007f70ef9cef6b in QCoreApplication::exec() () from /usr/lib64/qt4/libQtCore.so.4 #8 0x00007f70f255140a in kdemain (argc=<value optimized out>, argv=<value optimized out>) at /var/tmp/portage/kde-base/plasma-workspace-9999/work/plasma-workspace-9999/plasma/desktop/shell/main.cpp:112 #9 0x00007f70f21c1bdd in __libc_start_main () from /lib/libc.so.6 #10 0x0000000000400709 in _start ()
*** Bug 214966 has been marked as a duplicate of this bug. ***
- What are your KDE and Qt versions (svn revision/branch and git revision...) - The backtrace looks like a normal "QEventLoop waiting for something to happen" , that means... "idle". It could be some kind of weird focus problem...
KDE is r1052953 Qt is kde-qt.git cd8595e I can reproduce this on two computers at least. Note, I'm using focus-follows-mouse, so maybe that's needed for reproducing this...
I have a two panel setup, and double-clicking the notification title made the bottom panel (did not have the systray, for the record) become unresponsive. The rest of plasma-desktop was fine and interactable. I'm downgrading this from a crash, because it's really not a crash.
I think I have experienced this issue, but after the update to: kde-qt master commit 747ff8e6ef6f5a1163dfa75bc9ac4755ce7083d1 (the last one, which includes the fix for bug 210146 and some other related ones) I can't reproduce the issue.... - Could anyone else check this ? Here using: Qt: 4.6.0 (kde-qt master commit 747ff8e6ef6f5a1163dfa75bc9ac4755ce7083d1 Date: Tue Dec 15 11:58:13 2009 +0100) KDE Development Platform: 4.3.82 (KDE 4.3.82 (KDE 4.4 >= 20091211)) kdelibs svn rev. 1063229 / kdebase svn rev. 1063229 on ArchLinux i686 - Kernel 2.6.31.6
Fixed for me in beta2. (No Qt upgrade since beta1)