Changing volume using media keys or custom keyboard shortcuts on second monitor affects gnome desktop theme

[ferrogene]

I'm running Ubuntu Hardy amd64 with compiz enabled for both my laptop and desktop. Both have nVidia graphic card and their own dual monitor setup, i.e., laptop has a second monitor and the desktop has TV connection. Also, both nVidia cards use open source driver(nvidia-glx). The symptom is that if I change the volume using dedicated media keys or custom keyboard shortcuts with the mouse focus on the second monitor, it affects gnome desktop theme, e.g., icon theme and/or window decorator theme depending on monitor. It affects only the icon theme on the primary(first) monitor. But, on the second monitor both icon theme and window decorator are affected. It seems that the icon theme and the gtk theme roll back to the default gnome icon theme and gtk theme (maybe Raleigh), respectively, and then come back to the normal theme. Changing volume shouldn't affect any component of the desktop theme in any way. If I turn off the compiz effect, it simply doesn't happen. It only occurs with compiz effect turned on. It also doesn't happen if I change the volume using volume control on the panel. It only happens with the combination of separate monitor setup + compiz turned on + focus on second monitor. Here is the version info; kernel: 2.6.24-24-generic, nvidia-glx: 1:96.43.05, compiz: 1:0.7.4. Thanks in advance.

[Travis Watkins (amaranth)]

This appears to be a crash in gnome-settings-daemon, nothing to do with compiz. Does the same thing happen if you switch to metacity, enable metacity compositing, and try to change the volume?

To turn on the metacity compositor: gconftool-2 -s '/apps/metacity/general/compositing_manager' --type bool true
To turn it off again: gconftool-2 -s '/apps/metacity/general/compositing_manager' --type bool false

[ferrogene (tachyian)]

Thanks for reply, Travis. I've tested what you said and I think you're right. It has nothing to do with compiz. If I switch to metacity and enable metacity compositing, then the same problem happens. But, if I disable compositing, then everything works perfectly. Can you tell me what possibly causes the crash in gnome-settings-daemon? I think I need to move this bug report to somewhere else and (because this is the first time that I report a bug) I don't know where and how... Sorry.

[Travis Watkins (amaranth)]

Not sure what information will be wanted for gnome-settings-daemon about this crash but I'll reassign the bug and mark it Confirmed until someone looks at it.

[ferrogene (tachyian)]

Thank you, Travis. I appreciate it. I hope someone can fix this 'cause it's a bit annoying even though not serious.

[Chris Coulson (chrisccoulson)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.

[madbiologist (me-again)]

This might be the gnome bug https://bugzilla.gnome.org/show_bug.cgi?id=615853 which has been fixed in gtk2-engines-pixbuf 2.20.1-0ubuntu1