© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
67d34a1
(Get the code!)
This happens when a compositing window-manager is available/running when notify-osd is started... and later during the session is replaced with something that's no longer compositing windows. Because notify-osd still thinks it's running in a composited environment. Killing and restarting notify-osd, when the switch from a compositing to a non-compositing window-manager happens fixes this issue.
notify-osd used to much more dynamic in its rendering behaviour in the past, but I had to remove some of that for reasons I currently can't remember anymore.
As for the blue color... this seems to be from running notify-osd < 0.9.34. With the latest (0.9.34) release, the background tint is always correct.