Description of problem: $ gnome-volume-manager --sm-client-id default5 GnomeUI-CRITICAL **: gnome_client_set_id: assertion `!GNOME_CLIENT_CONNECTED (client)' failed aborting... Version-Release number of selected component (if applicable) 1.5.9-1 How reproducible: always Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: gnome-session-2.13.4-1
Created attachment 123198 [details] gnome-volume-manager backtrace file
*** Bug 177811 has been marked as a duplicate of this bug. ***
Same behaviour here, recent (updated today sat 14th jan) development, before updating (about 2 days ago) there were no such problems Now the described effect happens on both my computers, one with a SB Audigy pci card, other a laptop with intergrated sound (Intel ICH 82801 something), but both with the same gnome-volume-manager
*** Bug 177866 has been marked as a duplicate of this bug. ***
As I was informed we turned on a feature in GNOME for finding critical bugs over the weekend. It has been turned off in recent builds and an update should fix this issue for the user though it does mean there are things that need to be fixed in g-v-m so this bug should stay open.
Is there a separate BZ entry for things caught by this "critical bug finder"? As well as the gnome-volume-manager and mixer_applet2 bugs this seems to find, I also get a similar "empty" dialog box when logging out of gnome ..
I have this problem too. When I manually run gnome-volume-manager when I'm fully loged in it doesn't crash.
The fatal-criticals featture was turned off in gnome-session-2.13.4-2
You fixed this right, John?
Seems to be fixed. Should be out in tomorrows rawhide. If the problem persists please reopen this bug.