GNOME Bugzilla – Bug 660497
description bubble from message tray got cut by right of screen
Last modified: 2013-03-02 13:04:25 UTC
I've got a multiscreen setup with the primary monitor on top with a 1920x1080 resolution, and the secondary monitor at the bottom with a 1280x800 resolution and centered wrt to the bigger monitor. In this setup, the message tray is at the bottom of the secondary screen (the bottom one), I don't know if this is expected. When I click in a notification in the message tray, the bubble that pops up isn't fully visible, it goes out of screen. If I change the monitors positions in the display configuration panel, then the bubbles are no longer cut.
Created attachment 197788 [details] screenshot which should make this bug report more understandable :p
What version of gnome-shell are you using?
gnome-shell-3.1.92-1.fc16.x86_64
Can you try the patch in bug #659861, or wait until 3.2.1 (or F16) is released? (Apologies, I thought I pushed that before we branched, and that it would be in 3.1.92)
I tried applying this patch, restarting gnome-shell but it didn't help. However, I'm not confident at all that I applied it correctly (I got this when trying to apply it in /usr/share/gnome-shell) patch -p1 </home/teuf/hack/attachment.cgi\?id\=197287 patching file js/ui/boxpointer.js patching file js/ui/layout.js patch unexpectedly ends in middle of line ) I'll try F16/3.2.1 when this goes out.
(In reply to comment #5) > I tried applying this patch, restarting gnome-shell but it didn't help. > However, I'm not confident at all that I applied it correctly (I got this when > trying to apply it in /usr/share/gnome-shell) > patch -p1 </home/teuf/hack/attachment.cgi\?id\=197287 > patching file js/ui/boxpointer.js > patching file js/ui/layout.js > patch unexpectedly ends in middle of line > ) > > I'll try F16/3.2.1 when this goes out. Yes, it's meant to be applied with 'git am', not 'patch'. You can try stripping the email header and footer off of the attachment.
I diffed what I have in /usr/share/gnome-shell against what is in the package, and it looks like the patch got applied correctly. So it doesn't help with this bug.
*** Bug 660521 has been marked as a duplicate of this bug. ***
Can you try some steps for me? 1. Go into the overview so that the message tray is open 2. Open the looking glass (Alt+F2, 'lg') 3. Click the eyedropper in the top-left, and select the message tray icon in there. 4. Evaluate: Main.layoutManager.findMonitorForActor(r(0)) == Main.layoutManager.bottomMonitor Does it say "true" or "false"?
In the mean time, my gnome-shell got upgraded to 3.2.0. I applied the patch from the other bug again since findMonitorForActor only exists with it and restarted gnome-shell. Then when using the eyedropper, the message tray doesn't appear when I hover over it even though I seem to be able to pick some widgets so I ran your code against 2 of them: an StBin::last-child and a StBoxLayout "summary-mode". With these 2 objects, I get true with the code you gave (I changed the r(0) to the correct value). Let me know if I did something wrong in my tests, I can try again :)
(In reply to comment #10) > Then when using the eyedropper, the message tray doesn't appear when I hover > over it even though I seem to be able to pick some widgets so I ran your code > against 2 of them: an StBin::last-child and a StBoxLayout "summary-mode". With > these 2 objects, I get true with the code you gave (I changed the r(0) to the > correct value). Let me know if I did something wrong in my tests, I can try > again :) The message tray should always be visible in the overview.
(In reply to comment #11) > > The message tray should always be visible in the overview. Ah indeed, but the window key shortcut didn't work in eyedropper mode, and I hadn't tried to click in the upper left corner. I just did that, and rerun your test for the message tray, the icon I get in there (rhythmbox), and the ClutterTexture associated with the icon, and in all cases I get true.
Oh, looking at your screenshot, your sides aren't touching, so I bet that the bottom monitor isn't detected as the bottom monitor. Can you try the patch in bug #660596?
Ah, this patch fixes the issue indeed. Fwiw, you say "Also, yes, by design the message tray should always be on the most bottom monitor, as it would be hard to hit otherwise." in this other bug, to be consistent this should mean that the primary screen has to be the top one, otherwise the top bar gets hard to hit if it's on the bottom monitor.
(In reply to comment #14) > Ah, this patch fixes the issue indeed. > > Fwiw, you say "Also, yes, by design the message tray should always be on the > most bottom monitor, as it would be hard to hit otherwise." in this other bug, > to be consistent this should mean that the primary screen has to be the top > one, otherwise the top bar gets hard to hit if it's on the bottom monitor. Indeed.
The primary monitor is configured in the control panel, and is indicated by showing a little panel on that monitor. So if we put the panel somewhere other than that, we're going to be inconsistent.
i always thought panels were expected to be on the primary monitor. (heck, virtual desktops only work on the primary monitor) the secondary monitor being a 'presentation mode screen' which always holds the same windows on all virtual desktops. under this premise, the notification panel is appearing on the wrong screen. and like dan winship said. having the panel on top is arbitrary too. if it was up to me, the notification panel should be on the primary screen too (or moveable like the top panel). anyway, im glad the bug has been fixed ;)
I haven't seen this issue in a while. Please comment or reopen if you're still seeing it.