| 1 |
Alan McKinnon wrote: |
| 2 |
> On 26/05/2013 13:03, Dale wrote: |
| 3 |
>> Alan McKinnon wrote: |
| 4 |
>>> On 26/05/2013 11:51, Dale wrote: |
| 5 |
>>> |
| 6 |
>>>> What package provides the kicker thingy? I think in KDE3 it was called |
| 7 |
>>>> kicker but it appears to have changed to something else. Is that |
| 8 |
>>>> krunner that has it now? |
| 9 |
>>> Maybe it's time you used the "thingy" suffix a little less and the real |
| 10 |
>>> names of things a little more :-) |
| 11 |
>>> |
| 12 |
>>> What thing are you asking about? The panel that is usually at the bottom |
| 13 |
>>> and holds the plasma widgets? Or the thin popup you get with Alt-F2? |
| 14 |
>>> |
| 15 |
>>> The panel is called plasma-desktop and comes from kde-base/plasma-workspace |
| 16 |
>>> The popup is krunner and comes from kde-base/krunner |
| 17 |
>>> |
| 18 |
>>> I doubt very much it's a real bug as such in either KDE app (although |
| 19 |
>>> the fix might go in there). It looks much more to me like a side-effect |
| 20 |
>>> of IO blocking - two or more apps are trying to get something done and |
| 21 |
>>> unexpectedly are not getting answers, so they hang around waiting in the |
| 22 |
>>> doorway and get get in the way of everything else. And just for fun, |
| 23 |
>>> video drivers are also trying to get in on the act as they have to deal |
| 24 |
>>> with mouse pointer repaints... |
| 25 |
>>> |
| 26 |
>>> Debugging this one is going to be fun (for peculiar definitions of fun) |
| 27 |
>>> |
| 28 |
>>> |
| 29 |
>> The thingy is the thing at the bottom where I can switch desktops, click |
| 30 |
>> the K menu and where my clock is. I think it was called Kicker in |
| 31 |
>> KDE3. KDE4 seems to have changed it but not sure what the new name is. |
| 32 |
> It's a plasma widget called a panel, the only useful thing it does is to |
| 33 |
> be a container for other widgets that do useful stuff. |
| 34 |
> |
| 35 |
> The panel is started by plasma-desktop as one of the standard widgets it |
| 36 |
> manages. The idea is to give you stuff on the screen that looks more or |
| 37 |
> less like a familiar desktop. Plasma can do other things and give you |
| 38 |
> completely different layouts; like for instance not giving you a panel |
| 39 |
> at all. This would be useful on a phone with small screen |
| 40 |
> |
| 41 |
> The whole thing is heavily event based and has to react to a bucket load |
| 42 |
> of system events being generated such as what the mouse is doing. |
| 43 |
> There's a fantastic number of ways this could go wrong, some might be |
| 44 |
> plasma's fault, some might be faults that happen to plasma |
| 45 |
|
| 46 |
|
| 47 |
I'll try to remember to call it a panel thingy then. ROFL |
| 48 |
|
| 49 |
|
| 50 |
>> I hope they fix this thing soon. If they remove the driver from the |
| 51 |
>> tree, I'm in a bit of a pickle. |
| 52 |
> No, you won't be. You have the ebuild right now, copy it to your overlay |
| 53 |
> and "remove" becomes something that will not happen |
| 54 |
> |
| 55 |
> |
| 56 |
> |
| 57 |
|
| 58 |
Last time I did that, it didn't work out well. Actually, it just plain |
| 59 |
didn't work. May as well tell it like it is. ;-) I'll save a copy |
| 60 |
just in case. |
| 61 |
|
| 62 |
Cross that bridge when I get there I guess. |
| 63 |
|
| 64 |
Dale |
| 65 |
|
| 66 |
:-) :-) |
| 67 |
|
| 68 |
-- |
| 69 |
I am only responsible for what I said ... Not for what you understood or how you interpreted my words! |
Archives