From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8a4) Gecko/20040927 Description of problem: I've been using KDE since RH9 and one thing is really annoying - when automatic hide function is turned on, kicker tends to freeze for few seconds (especially after closing Mozilla from mozilla.org). Is't the same bug as https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=79685 (I didn't know whether to reopen it or not :/ ) Version-Release number of selected component (if applicable): kdebase-3.3.1-4.1 How reproducible: Sometimes Steps to Reproduce: 1. The same as in bug #79685 Additional info: I remeber that the only version which was unaffected by this bug was KDE 3.2 beta from KDE's ftp (packages from 3rd party, not from RedHat).
it's strange. i tried to reproduce this problem with your instruction. But it works for me. Could you please try with a new created user? perhaps there're some old config files on your home, which caused this problem!
CLosing as workforme
Sorry for no response, but I was trying to find out how to reproduce this bug. I created new account and everything was all right so I decided to remove ~/.kde on my old account. This bug disappeared! I was happy one whole day till the X server crash... bug #121403 The problem reappeared :/ I also tested it on the newly created accounts - after X server crash, kicker randomly freezes. For example run /usr/local/mozilla/mozilla, go to http://www.mozilla.org/releases/mozilla1.8a5/changelog.html copy some text and move mouse to the apropriate screen edge (depends on your configuration) - kicker does not show immediately. You have to wait 3-4 seconds. Another example - run Mozilla (I use gtk build from mozilla.org), surf the web few minutes and close the browser - kicker freezes for 5-7 seconds. Maybe it's problem with sesion saver? I don't know. Removing ~/.kde/share/config/session/* does not help :(
Created attachment 107347 [details] My configuration.
I cannot reproduce this bug any more on my FC4 box :-) I read somhere that kicker from KDE 3.4.x release had major overhaul so they coud have fixed this bug, too.