Kicker lockup (Re: KDE 3.0.2 reminder)

[Waldo Bastian]

On Tuesday 18 June 2002 10:02 am, Carsten Wolff wrote:
> Hi,
> may I add this one:
> http://bugs.kde.org/db/44/44048.html
> Kicker freeze, wich appears in many cases (personalizer/kcontrol).

Kicker ends up looping on Kicker::configurationChanged --> 
PanelKMenu::configChanged

What happens is that the configurationChanged signal gets connected to 
PanelKMenu::configChanged while handling the configurationChanged signal so 
when Qt checks the next receiver for the signal it notices this freshly 
connected slot and calls PanelKMenu::configChanged and the whole cycle 
repeats itself over and over again.

It's also strange that both PanelKMenu as well as PanelServiceMenu have a 
configChanged slot. I pretty much suspect that PanelKMenu::configChanged gets 
called twice and PanelServiceMenu::configChanged doesn't get called at all.

The following two patches seem to solve the problem. Please review/test.
(Make sure to restart kdeinit after the kpanelmenu patch because kicker seems 
to insist on restarting itself through kdeinit)

Cheers,
Waldo
-- 
bastian at kde.org  |   SuSE Labs KDE Developer  |  bastian at suse.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: kpanelmenu.patch
Type: text/x-diff
Size: 502 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20020618/cb739603/attachment.patch>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: kicker.patch
Type: text/x-diff
Size: 1376 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20020618/cb739603/attachment-0001.patch>