! Please note that this is a snapshot of our old Bugzilla server, which is read only since May 29, 2020. Please go to gitlab.xfce.org for our new server !
Button loses highlight when moving cursor on screen edges
Status:
RESOLVED: FIXED
Product:
Xfce4-panel
Component:
General

Comments

Description Mariusz 2017-04-20 01:19:59 CEST
Created attachment 7078 
video showing this issue

Hello. I'm using Whisker Menu 2.1.2 on Xubuntu 17.04 with xfce4-panel 4.12.1

My issue is that Whisker Menu button loses its highlight when I move cursor on the screen edges. I've tested it when the panel was pinned to the top (default in Xubuntu) and to the bottom with 100% length and on fresh user account. It seems that WM should be the first item on the panel to see this issue appear. No matter if it's displayed as an icon or a text. When the highlight is lost clicking on the button is not bringing the menu up. It just makes the highlight appear, nothing more.

I recorded my screen to explain this issue better (I will attach the file also):
https://drive.google.com/open?id=0B8qh4-wxxEZ7ckpic29mdUEyWW8
Comment 1 Mariusz 2017-04-20 01:28:14 CEST
Created attachment 7079 
video showing this issue (ZIP)
Comment 2 Dave Pearson 2017-04-20 10:24:36 CEST
I Can confirm this seems to affect installs on Hardware rather than VM's.
Comment 3 Graeme Gott editbugs 2017-04-20 11:42:02 CEST
This is not a bug in Whisker Menu, as I can recreate this with other plugins (such as the PulseAudio plugin and the DateTime plugin). I also can only recreate it with GTK3 plugins, and for me they do not need to be the first item on the panel. It is most likely a bug in the panel.
Comment 4 Mariusz 2017-04-21 22:43:53 CEST
This may not be related, but I think I should mention it. I can observe very similar behaviour with Plank docked to the left side of my screen, as seen here - https://drive.google.com/open?id=0B8qh4-wxxEZ7b3ZTZ0stb1VvdGM

So maybe not only xfce4-panel is affected by this bug, but all docked (GTK3) windows/objects?
Comment 5 Pasi Lallinaho editbugs 2018-05-07 16:52:07 CEST
I can't reproduce this in Xubuntu 18.04 (panel version 4.12.2). I tried with multiple different panel settings and both left/top positioning.

In case there isn't anything else to work on, the only difference we found out with the original reporter is GPU/graphic drivers; they are using Nvidia, I'm using Intel.
Comment 6 Spass 2018-05-07 23:31:15 CEST
I'm the original poster (new account) and now I know a little bit more about this bug. It's not only Xfce4-panel issue, but I have no idea where it should be moved. I've created a thread on the Xfce official forum and this issue was confirmed by other user using AMD graphics card, so it seems that it's not related to a specific hardware.

Here's the link to the forum: https://forum.xfce.org/viewtopic.php?id=12190
Comment 7 Spass 2018-05-11 14:22:54 CEST
I think you can close this bug report, it's not Xfce specific. It occurs on MATE, KDE and GNOME too. Unfortunately I still have no idea what causes it.

Details here: https://askubuntu.com/questions/1034051/what-causes-an-issue-with-desktop-elements-losing-focus-when-i-move-my-mouse-cur
Comment 8 Spass 2018-10-24 15:48:19 CEST
OK, there's a workaround for this issue. This bug report tells a lot more about it - https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1795135

I put export GDK_CORE_DEVICE_EVENTS=1 to /etc/X11/Xsession.d/56xubuntu-session and my Xfce panel items aren't blinking any more, and that works with Plank too. Tested on Xubuntu 18.04.
Comment 9 Simon Steinbeiss editbugs 2018-10-24 19:24:32 CEST
Fixed in https://git.xfce.org/xfce/xfce4-panel/commit/?id=e56e869

Note that the environment variable is a workaround and that the actual bug is in xorg's xinput2.
Comment 10 xfce 2018-11-04 08:22:36 CET
This started happening to me after upgrading to the newly-released Fedora 29.  I use a panel at the top of the screen and, much of the time, was unable to click on Window Buttons when my mouse was on the top pixel row.  Adding GDK_CORE_DEVICE_EVENTS=1 into my /etc/environment file, then rebooting, fixed it.  Thank you.
Comment 11 Simon Steinbeiss editbugs 2018-11-05 23:05:23 CET
*** Bug 14729 has been marked as a duplicate of this bug. ***

Bug #13509

Reported by:
Mariusz
Reported on: 2017-04-20
Last modified on: 2018-11-05

People

Assignee:
Simon Steinbeiss
CC List:
5 users

Version

Version:
4.12.0

Attachments

video showing this issue (560.82 KB, video/mp4)
2017-04-20 01:19 CEST , Mariusz
no flags
video showing this issue (ZIP) (410.39 KB, application/zip)
2017-04-20 01:28 CEST , Mariusz
no flags

Additional information