Summary: | Plasma-desktop menu weird behavior where it shows up constantly | ||
---|---|---|---|
Product: | [Unmaintained] plasma4 | Reporter: | chosunsk |
Component: | general | Assignee: | Plasma Bugs List <plasma-bugs-null> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | andresbajotierra, asraniel, notmart |
Priority: | NOR | ||
Version First Reported In: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: |
Pic 1: Behavior when widgets are locked
Pic 2: Behavior when widgets are unlocked Pic 3: Temporary solution: Zoom out from the desktop and close the plasma-desktop menu Pic 4: Bug on top, panel on the bottom |
Description
chosunsk
2009-09-03 03:42:00 UTC
This bug was not present in KDE 4.3.0 Created attachment 36645 [details]
Pic 1: Behavior when widgets are locked
Created attachment 36646 [details]
Pic 2: Behavior when widgets are unlocked
Created attachment 36647 [details]
Pic 3: Temporary solution: Zoom out from the desktop and close the plasma-desktop menu
Isn't that that qt bug that got fixed in qt? It is bug 200802 probably. - Can you confirm that this doesn't happen in a panel in the bottom edge ? (or clicking the cashew in the upper-right corner of the Desktop) Thanks It occurs when the menu panel is at the bottom (see attached pic 4). Also, when I reported this bug, I had the cashew on the right side of my screen, not on the left where it first appeared. Created attachment 36680 [details]
Pic 4: Bug on top, panel on the bottom
- To which panel(or desktop) is that menu associated with ? I have five activites with each having four virtual desktops. Strangely, when zooming out, the bug happens to occur on the fourth activity when going left to right, up to down. Also, the fourth one activity happens to show up as the first one on my activity bar, and it is the one I log into. Could this be a sorting bug? AFAIK, there is no way to sort the activities in any order. the toolbox works in a different way now, this bug simply can't happen anymore |