changing gnome window manager breaks notifications

Bug #349047 reported by Toni Ruottu on 2009-03-26
This bug affects 1 person
Affects Status Importance Assigned to Milestone
notify-osd (Ubuntu)
Mirco Müller
Nominated for Jaunty by radostyle
Nominated for Karmic by radostyle

Bug Description

Binary package hint: notify-osd

I identify myself as a Gnome user, but I use xmonad as the window manager for Gnome as it further increases my productivity. The window manager to be used with Gnome is defined with the environment variable WINDOW_MANAGER. I personally set this variable at the end of my ~/.profile by saying export WINDOW_MANAGER="/usr/bin/xmonad". A piece of software called gnome-wm then looks this variable up at start-up phase and runs the windows manager of my choice, or a default one in case I specified none.

Changing the value of the variable should have no effect on anything, but the window manager that gets started. With Jaunty however, setting the windows manager like this breaks the notification system. While debugging the problem I managed to get both my window manager and notification system working, by 1) unsetting the WINDOW_MANAGER variable 2) logging in with the variable unset 3) killing metacity window manager by hand 4) starting xmonad by hand.

Changed in notify-osd (Ubuntu):
assignee: nobody → macslow
importance: Undecided → Low
Daniel T Chen (crimsun) wrote :

Confirmed in both xmonad and awesome.

Changed in notify-osd (Ubuntu):
status: New → Confirmed
Toni Ruottu (toni-ruottu) wrote :

Choosing Metacity explicitly by adding the following line to ~/.profile does not seem to break notifications.
export WINDOW_MANAGER="/usr/bin/metacity"

radostyle (mr--jon) wrote :

I also have this problem using xmonad with gnome and can conrm the workaround. Thank you Toni for sharing the workaround.

Changed in notify-osd (Ubuntu):
status: Confirmed → Triaged
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers