Version: (using KDE 4.3.0) Compiler: gcc version 4.3.2 (Gentoo 4.3.2-r3 p1.6, pie-10.1.5) -march=k8-sse3 -O2 -pipe OS: Linux Installed from: Gentoo Packages When I enter in panel configuration mode and try to add a widget by the button Add Widget, the dialog is showed and close immediately. I just can add Widgets to a panel if I click with the right button, go to panel configuration and choose the option Add Widget.
I can confirm this. I think it is related to focus-follows-mouse - the config panel loses focus for some reason and closes immediately. Note that this leads to problems in various other circumstances as well. Would be better if somehow the config elements could stay open even if there's no focus anymore, I often close it by accident :/
Manuel Nickschas, What KDE version are you using? I have tried to reproduce this bug on KDE 4.3.3 and I couldn't, so I think it maybe already fixed. Can you confirm this?
Trunk as of yesterday, and the issue is still around. I often need dozens of attempts to succeed in keeping the widget open.
I can confirm that Ronan's problem exists in KDE 4.4 Beta 2. Right-click the panel, click `panel options', click `add widgets...' -- and nothing happens. Right-click the panel, click `panel options', click 'panel settings', and *then* click `Add widgets', and Beta 2's funky new add-widget bar appears. I've never seen this bug in any previous version of KDE.
Hi, I'm using KDE SC 4.4 beta 2, too. I can't reproduce this bug, too. I guess it's fixed. I can confirm that if focus follows mouse is activated and there are windows open, it can be very difficult to keep both panel configuration bar and KDE 4.4's "funky new add-widget bar" open, because the windows steal the focus if you just accidentally mouse over them for even a fraction of a second, and then they close. And Markus, I think Ronan's problem was when he tried to open that 'Add widgets' dialog from panel settings (that bar that appears next to the panel) and that he was only able to open it by doing it the way you couldn't. Your bug (I can confirm it too) seems to be a new and different bug for a different bug report. I hope this makes sense.