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 651456 - Hot corners and message tray issues in dual head mode
Hot corners and message tray issues in dual head mode
Status: RESOLVED DUPLICATE of bug 622655
Product: gnome-shell
Classification: Core
Component: general
3.0.x
Other Linux
: Normal normal
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
Depends on:
Blocks:
 
 
Reported: 2011-05-30 10:45 UTC by sirex
Modified: 2011-05-30 11:01 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Visible shadow of message tray in dual head mode (917.75 KB, image/png)
2011-05-30 10:45 UTC, sirex
Details

Description sirex 2011-05-30 10:45:15 UTC
Created attachment 188873 [details]
Visible shadow of message tray in dual head mode

I have two monitors, one bigger, other smaller. Is there a way, to layout two monitors of different size, that hot corners (top-left and bottom-right) would be accessible?

If secondary monitor is placed at left-middle, then activity hot corner is no more accessible, because mouse move to other screen and does not triggers activities view. Also in some layouts gnome-shell starts to use CPU intensively.

It seems, that only layout, that I attached works correctly.

But with layout (in attachment), I experience other annoyance. It is hard to make message tray appear, because mouse moves to the bottom screen, so I need to be more precise to make message tray appear. Also, in secondary monitor, shadow of message tray is visible as can be seen in attachment.
Comment 1 Florian Müllner 2011-05-30 11:01:47 UTC
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.

You'll need a recent enough XServer / XFixes to work correctly.

The other issue is bug 636963.

*** This bug has been marked as a duplicate of bug 622655 ***