Notify OSD panel is opaque when shown in the installer

Did you choose to "Install Ubuntu" or "Try Ubuntu" at the first screen?

For this bug to occur you need to go straight to 'Install Ubuntu'. Once you're in the live session the notifications appear fine, even when running Ubiquity. I'm trying to get a screenshot but I can't find where the image files are going (they don't end up in ~/Pictures)

When in a live session are you getting unity 3d or unity 2d?

I'm asking because the main difference between ubiquity-dm and unity 3d is that we're using metacity and so don't have compositing.

It's Unity 3D

confirmed with 20120301

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/942572

This bug seems to happen for me both during the Installer and Live Session - but also post installation. I'm not sure if it has anything to do with my graphics setup - I'm on nVidia and using proprietary graphics.

Before yesterday I've installed Ubuntu 12.04 LTS i386 on my ASUS F5N series notebook. First it was ok, as far as I can remember, but after installing nvidia-current it changed and seems the same for mee. I attached a screenshot too.

I've seen this now on a Samsung N310 with Intel Mobile Graphics (945GM I think) and also on the ARM Pandaboard.

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.

So Mirco, what is the best solution here? Should the installer kill notify-osd when switching window-manager? Is that a viable solution?

The best solution for this is indeed to kill and restart notify-osd, when the wm is switched.

Hmm, must be something else.
ubiquity-dm spawns its own X server, then metacity and then at some point we get notify-osd. We never switch window managers nor start anything that can do compositing.

We don't actually have any code in ubiquity spawning notify-osd, the only things we spawn are metacity and gnome-settings-daemon.

Updated screenshot (today's daily): http://www.stgraber.org/download/ubiquitydm-osd.png

It's worth noting that ubiquity-dm spawns a standard metacity without any custom settings, which isn't true of unity-2d that starts it with its building compositor enabled. That might explain why we don't get more report of that from unity-2d users.

I understand that without compositor we can't expect it to become transparent, though maybe something can be done to improve the layout a little?

The Precise Pangolin has reached end of life, so this bug will not be fixed for that release