Bug 78184 - Quick browser hangs erratically
Summary: Quick browser hangs erratically
Status: RESOLVED DUPLICATE of bug 74487
Alias: None
Product: kicker
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: RedHat Enterprise Linux Linux
: NOR normal
Target Milestone: ---
Assignee: John Firebaugh
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-03-22 01:59 UTC by Jason Haar
Modified: 2004-03-31 03:23 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jason Haar 2004-03-22 01:59:33 UTC
Version:            (using KDE KDE 3.2.1)
Installed from:    RedHat RPMs
OS:          Linux

I have been using my own dir tree of objects via a "Quick browser" hanging off the Taskbar for over a year now - basically all the of KDE-v2* releases.

Now that I've upgraded from KDE 3.1.2 to 3.2.1, I find that my old Quick Browser tree doesn't work as well as it used to. All the objects still work, it's just that I find that quite often (5-10 times a day!) I click on the folder on my Taskbar, the initial menu pops up, and I can't click on anything. At that stage I have to either hit ESC a bunch of times - or try to move focus to another app,etc to free up the Quick Browser again. Then I let it disappear and try again. Normally the 2nd or 3rd time later it works as expected.

My Quick Browser list is just a directory full of shortcuts to slogin sessions in xterms - nothing fancy. They do work fine normally, but these "glitches" occur which ruin the experience. I have some subdirs to group the sessions accordingly (Quick Browser kicks ass as a concept!), but basically it's subdirs plus some slogin sessions...

I use "Focus follows mouse", but this is under the KDE Fedora RPM release I got off kde.org. I wonder if the changes made to KDE to do double-click and the like (i.e. the "Redhatifying" of KDE) may be responsible for this bug?

Thanks
Comment 1 John Firebaugh 2004-03-31 03:23:16 UTC

*** This bug has been marked as a duplicate of 74487 ***