Correct Top Panel email notification on Screen0

Asked by JayBofMA

I am using Unity-2d and the default Top Panel that is rendered. My setup is a 15" laptop connected to a docking station and a larger external monitor (Screen1) configured with Separate X and Xinerama, First, I do not care that the Top Panel is rendered on both Screen0 and Screen1. But what I see is that the Evolution new email notifications are only updated on Screen1 (I saw some older post that indicated an updated PPA for Evolution included a fix for notifications, but that had no impact here.)

So I would like to see the notification updated correctly on Screen0. If this requires me to restrict the display of the Top Panel to Screen0, then I would need some information on how to accomplish this (toggling Stretch flags in gconf-editor made no change.) Or if there is a way to have the new email notification updated correctly on both Screen0 and Screen1, then I would appreciate any information in that regard as well.

Coincidentally, I see the opposite behavior for Evolution appointment notifications (and I have to run to one now ;-) ). The appointment notification indicator is raised on Screen0, where I would expect, and prefer, to see it. So this may be an indication that the email notification applet is at fault.

Question information

Language:
English Edit question
Status:
Solved
For:
unity-2d Edit question
Assignee:
No assignee Edit question
Solved by:
JayBofMA
Solved:
Last query:
Last reply:
Revision history for this message
Olivier Tilloy (osomon) said :
#1

This inconsistent behaviour of notifications is indeed annoying. However it doesn’t have anything to do with unity-2d’s panel, the notifications’ placement code is completely independent from unity-2d’s code base. I’d suggest to look into bug reports for notify-osd, or maybe specifically for the e-mail notifications applet.

Revision history for this message
JayBofMA (jayburrill) said :
#2

Finally found a Bug which notes this problem. Although not technically Solved, resolution of this Bug #331369 will provide the solution.