Version: unspecified (using KDE 4.7.3) OS: Linux Esc button must be used to close the plasma dashboard if it overlies an auto hide panel. The mouse click over the "x" does not work. Reproducible: Always Steps to Reproduce: Place auto hide panel on top edge. Open dashboard. Try closing dashboard with mouse. Actual Results: Dashboard stays up unless esc button is pushed. Expected Results: Dash board closes with mouse click on "x"
confirmed for 4.8b1. Funny, because most of the panel autohide bugs are gone by now i thought
this only happens with compositing on and is due to the glow proximity detection window .. this needs to be made into a kwin effect. CC'ing Marting since he will need to be consulted on the fix ...
.. and now ACTUALLY cc'ing Martin ;)
if it's in the last pixel, even as a kwin effect wouldn't work yet, is something that x can't really do (being notified about mouse reaching a place without putting a window under it) so would be upstream/wontfix
https://bugs.kde.org/show_bug.cgi?id=288087 Note this behaviour does not occur for me on KDE 4.6.5 [Debian Sid]. On 4 December 2011 04:33, Marco Martin <notmart@gmail.com> wrote: > https://bugs.kde.org/show_bug.cgi?id=288087 > > > Marco Martin <notmart@gmail.com> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > CC| |notmart@gmail.com > > > > > --- Comment #4 from Marco Martin <notmart gmail com> 2011-12-03 18:33:26 --- > if it's in the last pixel, even as a kwin effect wouldn't work yet, is > something that x can't really do (being notified about mouse reaching a place > without putting a window under it) so would be upstream/wontfix > > -- > Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email > ------- You are receiving this mail because: ------- > You reported the bug.
https://bugs.kde.org/show_bug.cgi?id=288087 A work around for a mouse control is to configure another active screen edge to opening/closing the dashboard in kde system settings > work space behavior > screen edges. > > On 4 December 2011 06:42, Bryan Cebuliak <bryan.cebuliak@gmail.com> wrote: >> https://bugs.kde.org/show_bug.cgi?id=288087 >> >> >> >> >> >> --- Comment #5 from Bryan Cebuliak <bryan cebuliak gmail com> 2011-12-03 20:42:36 --- >> https://bugs.kde.org/show_bug.cgi?id=288087 >> Note this behaviour does not occur for me on KDE 4.6.5 [Debian Sid]. >> >> On 4 December 2011 04:33, Marco Martin <notmart@gmail.com> wrote: >>> https://bugs.kde.org/show_bug.cgi?id=288087 >>> >>> >>> Marco Martin <notmart@gmail.com> changed: >>> >>> What |Removed |Added >>> ---------------------------------------------------------------------------- >>> CC| |notmart@gmail.com >>> >>> >>> >>> >>> --- Comment #4 from Marco Martin <notmart gmail com> 2011-12-03 18:33:26 --- >>> if it's in the last pixel, even as a kwin effect wouldn't work yet, is >>> something that x can't really do (being notified about mouse reaching a place >>> without putting a window under it) so would be upstream/wontfix >>> >>> -- >>> Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email >>> ------- You are receiving this mail because: ------- >>> You reported the bug. >> >> -- >> Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email >> ------- You are receiving this mail because: ------- >> You reported the bug.
I think Marco is quite right, so this is a RESOLVED WAYLAND where the compositor can pass the events through.
But is it really in the last pixel? The 'close' marker is well below this last pixel for me. And similar click-through-the-blue-shadow bugs have by now been solved. I get the feeling that the whole set of dashboard bugs, including this one, is related to the z-coordinate and focus of the dashboard.
Oops. This behaviour is in 4.6.5 too with compositing [krender] on. But not with it off. On 4 December 2011 20:26, Thijs <thijs22nospam@gmail.com> wrote: > https://bugs.kde.org/show_bug.cgi?id=288087 > > > > > > --- Comment #8 from Thijs <thijs22nospam gmail com> 2011-12-04 10:26:32 --- > But is it really in the last pixel? The 'close' marker is well below this last > pixel for me. And similar click-through-the-blue-shadow bugs have by now been > solved. I get the feeling that the whole set of dashboard bugs, including this > one, is related to the z-coordinate and focus of the dashboard. > > -- > Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email > ------- You are receiving this mail because: ------- > You reported the bug.
This bug still exists in KDE 4.93
If the user has their panel at the top of the screen then the "Widget Dashboard" icon will not allow an exit. Clicking on it has no effect. It will work if the dashboard has been opened and then the widget dashboard icon is clicked BEFORE anything else on the dashboard. Additionally, if the News widget is open on the dashboard and a link on it is clicked to open in a browser window and the user then clicks the widget dashboard icon it will exit to the desktop. So the problem seems to be related to focus (as Thijs mentioned 2011-12-04 10:26:32 UTC ). It would surely be desirable to be able to configure the dashboard so that the exit icon could be moved to the bottom or the side of the screen - or at least have the bug fixed so that it works regardless of where it is placed.
I can confirm this bug is still reproducible in 4.10.4, but only when panel is at the top edge of the screen in auto-hide mode and the dashboard is in "show desktop" mode. Other scenarios look like working as expected. so this bug has a duplicate in https://bugs.kde.org/show_bug.cgi?id=301915
Hello! This bug report was filed for KDE Plasma 4, which reached end-of-support status in August 2015. KDE Plasma 5's desktop shell has been almost completely rewritten for better performance and usability, so it is likely that this bug is already resolved in Plasma 5. Accordingly, we hope you understand why we must close this bug report. If the issue described here is still present in KDE Plasma 5.12 or later, please feel free to open a new ticket in the "plasmashell" product after reading https://community.kde.org/Get_Involved/Bug_Reporting If you would like to get involved in KDE's bug triaging effort so that future mass bug closes like this are less likely, please read https://community.kde.org/Get_Involved#Bug_Triaging Thanks for your understanding! Nate Graham