Alan McKinnon wrote: > On 26/05/2013 13:03, Dale wrote: >> Alan McKinnon wrote: >>> On 26/05/2013 11:51, Dale wrote: >>> >>>> What package provides the kicker thingy? I think in KDE3 it was called >>>> kicker but it appears to have changed to something else. Is that >>>> krunner that has it now? >>> Maybe it's time you used the "thingy" suffix a little less and the real >>> names of things a little more :-) >>> >>> What thing are you asking about? The panel that is usually at the bottom >>> and holds the plasma widgets? Or the thin popup you get with Alt-F2? >>> >>> The panel is called plasma-desktop and comes from kde-base/plasma-workspace >>> The popup is krunner and comes from kde-base/krunner >>> >>> I doubt very much it's a real bug as such in either KDE app (although >>> the fix might go in there). It looks much more to me like a side-effect >>> of IO blocking - two or more apps are trying to get something done and >>> unexpectedly are not getting answers, so they hang around waiting in the >>> doorway and get get in the way of everything else. And just for fun, >>> video drivers are also trying to get in on the act as they have to deal >>> with mouse pointer repaints... >>> >>> Debugging this one is going to be fun (for peculiar definitions of fun) >>> >>> >> The thingy is the thing at the bottom where I can switch desktops, click >> the K menu and where my clock is. I think it was called Kicker in >> KDE3. KDE4 seems to have changed it but not sure what the new name is. > It's a plasma widget called a panel, the only useful thing it does is to > be a container for other widgets that do useful stuff. > > The panel is started by plasma-desktop as one of the standard widgets it > manages. The idea is to give you stuff on the screen that looks more or > less like a familiar desktop. Plasma can do other things and give you > completely different layouts; like for instance not giving you a panel > at all. This would be useful on a phone with small screen > > The whole thing is heavily event based and has to react to a bucket load > of system events being generated such as what the mouse is doing. > There's a fantastic number of ways this could go wrong, some might be > plasma's fault, some might be faults that happen to plasma
I'll try to remember to call it a panel thingy then. ROFL >> I hope they fix this thing soon. If they remove the driver from the >> tree, I'm in a bit of a pickle. > No, you won't be. You have the ebuild right now, copy it to your overlay > and "remove" becomes something that will not happen > > > Last time I did that, it didn't work out well. Actually, it just plain didn't work. May as well tell it like it is. ;-) I'll save a copy just in case. Cross that bridge when I get there I guess. Dale :-) :-) -- I am only responsible for what I said ... Not for what you understood or how you interpreted my words!
