kde4 panel when clicked on the left edge it opens widget from the right
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
kdebase-workspace (Ubuntu) |
Invalid
|
Low
|
Unassigned |
Bug Description
Binary package hint: kdebase-workspace
Kubuntu Lucid beta 2
problem with KDE4 panel
I encounter this problem when I want to click K Menu button by moving cursor and clicking the very left-bottom corner of the screen.
When I click (left mouse button) on the left edge of KDE4 panel (left side of K Menu button), it opens the clock widget (which is on the right side). The panel is locked and maximized.
When panel is unlocked, it opens Plasma config menu. I even don't have to click the edge, also placing mouse over the left edge acts like the cursor is over the right edge of the panel. The widget on the right glows as if you placed cursor over it (or the plasma menu widget glows when the panel is unlocked).
You can also create a new panel (eg. at the top), add a widget onto it and then add a separator on the opposite to plasma logo, so that the added widget is pushed near the plasma logo.
Now maximize and lock the panel, then click or move mouse over the left edge (added widget is on the right).
I run Kubuntu beta inside VirtualBox 3.1.6 with guest additions installed, full screen mode (if it may have anything to do with this bug).
Greetings :)
ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: plasma-
ProcVersionSign
Uname: Linux 2.6.32-21-generic i686
Architecture: i386
Date: Tue Apr 20 22:19:36 2010
InstallationMedia: Kubuntu 10.04 "Lucid Lynx" - Beta i386 (20100406.1)
ProcEnviron:
LANGUAGE=
PATH=(custom, no user)
LANG=pl_PL.UTF-8
SHELL=/bin/bash
SourcePackage: kdebase-workspace
Hi there!
Thanks for reporting this bug! Your bug seems to be a problem with the KDE program itself, and not with our KDE packages. While we appreciate your issue, it would be better if it was tracked at https:/ /bugs.kde. org, so that the KDE developers can deal with this speedily and have direct communication with you as the reporter for more effective debugging.
Thanks!