Bugzilla – Bug 221604
Notification popup messages are displayed on the wrong screen when using dual screens
Last modified: 2008-03-26 21:25:41 UTC
Banshee is displaying it's popup messages on the wrong screen in a dual monitor environment. See attached screenshot.
Created attachment 105579 [details] Screenshot
Aaron, since we're playing with these popup messages in another bug, would you mind having a look at this one as well?
This is probably a bug in the notification daemon. When Banshee sends the notification it sends the tray icon information which the daemon should then use to position the popup accordingly.
Still an issue... JPR: Added you to CC as I think you know who should be assigned instead of Aaron.
Rodney, is the screen taken into account when positioning the bubble?
I don't know. As part of the specification that was written for our notifications, they are all to pop up in the bottom right, as a stack. The theme used in the screenshot is the standard theme, and not the bubble theme, which I changed the drawing code in, however. I also didn't change any actual positioning code. I just made it so that the positioning requested over dbus is ignored, and we always use the stack, as per the specification. I don't think the specification takes multi-head into account though. I'm not sure what the right way to "solve" this is at the moment.
Ping...
Not sure what to do about this or to whom it should be assigned. It's not a Banshee bug given Rodney's comment, but Rodney is no longer in a position to address this anymore AFAIK. Adjusting summary as it shouldn't be specific to Banshee. Banshee sends positioning information and the notify theme/daemon should use it accordingly.
Ping?
Need to be moved back into the general pool.
Although I see this as a bug and not RFE, moving to 11.0.
Since this came up on planetsuse... There is a bug in the libnotify bugtracker about this. http://trac.galago-project.org/ticket/5 contains two patches which fix the issue.
Changing this to an RFE
*** This bug has been marked as a duplicate of bug 179855 ***