GNOME Bugzilla – Bug 119979
Invalid gconf keys and crash
Last modified: 2004-12-22 21:47:04 UTC
On startup I get this error: An error occurred while loading or saving configuration information for gnome-volume-control. Some of your configuration settings may not work properly. Bad key or directory name: "/apps/gnome-volume-control/OSS-ESS_Solo-1-1/Vol ": ` ' is an invalid character in key/directory names Bad key or directory name: "/apps/gnome-volume-control/OSS-ESS_Solo-1-1/Pcm ": ` ' is an invalid character in key/directory names Bad key or directory name: "/apps/gnome-volume-control/OSS-ESS_Solo-1-1/Spkr ": ` ' is an invalid character in key/directory names Bad key or directory name: "/apps/gnome-volume-control/OSS-ESS_Solo-1-1/Line ": ` ' is an invalid character in key/directory names Bad key or directory name: "/apps/gnome-volume-control/OSS-ESS_Solo-1-1/Mic ": ` ' is an invalid character in key/directory names Bad key or directory name: "/apps/gnome-volume-control/OSS-ESS_Solo-1-1/CD ": ` ' is an invalid character in key/directory names Bad key or directory name: "/apps/gnome-volume-control/OSS-ESS_Solo-1-1/Pcm2 ": ` ' is an invalid character in key/directory names Looks like gmix should strip the spaces at the end before building the key (sed probably). The labels appear identically (including spaces) in linux/soundcard.h. When trying to run sed manually to create the device_labels_linux.h I get the error: sed: file device_labels_linux.sed line 16: Extra characters after command The same happens with the ALSA sed script, only in line 19. Maybe my sed is just too old? It's version 3.02. Then when I quit, volume-control really goes down the drain, crashing hard. I'm not sure whether the crash is realted to the invalid gconf keys. Backtrace was generated from '/opt/gnome2/bin/gnome-volume-control' [New Thread 1024 (LWP 11045)] 0x40a83289 in wait4 () from /lib/libc.so.6
+ Trace 39610
Thread 1 (Thread 1024 (LWP 11045))
I also get some funny messages on the command line: Warning: This version of the Gnome Volume Control was compiled with OSS version 3.8.2, and your system is running version 3.8.16. Warning: This version of the Gnome Volume Control was compiled with OSS version 3.8.2, and your system is running version 0.0.1. (gnome-volume-control:29476): Gtk-WARNING **: gtkmessagedialog.c:270:gtk_message_dialog_get_property(): invalid property id 1 for "message-type" of type `GParamEnum' in `GtkMessageDialog' ** (gnome-volume-control:29476): WARNING **: Error says Bad key or directory name: "/apps/gnome-volume-control/OSS-ESS_Solo-1-1/Vol /title": ` ' is an invalid character in key/directory names (gnome_segv:29485): Gtk-WARNING **: gtkmessagedialog.c:270:gtk_message_dialog_get_property(): invalid property id 1 for "message-type" of type `GParamEnum' in `GtkMessageDialog' Where does it get that OSS version number from? It shouldn't use OSS in the first place, but as configure seems to look for the ALSA headers at <sys/asoundlib.h> and they really are at <alsa/asoundlib.h>... but that's probably a different story. All this is with gnome-media 2.3.7.
This bug was caused by fixing the internationalized labels on the mixer. Apparently those are used for the GConf keys also. A better solution is needed, and definately before 2.4.0 :)
Make sure the keys are written and read from GConf using the C locale?
This should be fixed in the current release (2.3.8). The keys are changed back to their previous names - and the user title is now used for display. The user title and the name have been split.
*** Bug 123912 has been marked as a duplicate of this bug. ***