After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 662405 - Invisible barrier to let the message tray hotspot is missing a pixel
Invisible barrier to let the message tray hotspot is missing a pixel
Status: RESOLVED NOTGNOME
Product: gnome-shell
Classification: Core
Component: message-tray
3.2.x
Other Linux
: Normal normal
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
: 663814 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2011-10-21 17:01 UTC by Amanda Cameron
Modified: 2011-12-17 18:40 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Screen Layout (22.81 KB, image/png)
2011-10-21 17:35 UTC, Amanda Cameron
Details

Description Amanda Cameron 2011-10-21 17:01:49 UTC
The missing pixel is at the very bottom of the screen, so moving the mouse to the bottom, then sliding over causes the mouse to slip through onto the other screen. however if you move the mouse from bottom + 10px over, it will hit the barrier until you move the mouse down.
Comment 1 Rui Matos 2011-10-21 17:16:20 UTC
Can you tell us how your monitors are setup? Which resolusions to they have? How are they aligned?
Comment 2 Amanda Cameron 2011-10-21 17:35:54 UTC
Created attachment 199675 [details]
Screen Layout
Comment 3 Jasper St. Pierre (not reading bugmail) 2011-10-21 18:04:32 UTC
We tested a bit on IRC, and we found that creating a pointer barrier like:

  Main.layoutManager.bottomMonitor
  global.create_pointer_barrier(r(0).x + r(0).width,
                                r(0).y + r(0).height - 1,
                                r(0).x + r(0).width,
                                r(0).y + r(0).height);

didn't stop the pointer. Offsetting in other direction ( y + height, y + height + 1 ) stopped it somewhat, but also stopped triggering the message tray sometimes, and the pointer still got through sometimes. Changing y2 to be y + height + 5 seemed to fix the pointer getting through.
Comment 4 Rui Matos 2011-10-21 20:32:24 UTC
This is actually a bug in the X server which shall be fixed when http://patchwork.freedesktop.org/patch/6785/ lands.

The problem is that the CRTC pointer constraining logic is off by 1 pixel and lets the pointer get 1 pixel further down than it should (and to the right too).
Comment 5 Jasper St. Pierre (not reading bugmail) 2011-11-10 22:50:02 UTC
*** Bug 663814 has been marked as a duplicate of this bug. ***
Comment 6 Rui Matos 2011-12-17 18:40:25 UTC
This should be fixed in X server 1.11.3 so I'm closing this bug.