After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 123912 - gnome-volume-control crashed upon exit
gnome-volume-control crashed upon exit
Status: RESOLVED DUPLICATE of bug 119979
Product: gnome-media
Classification: Deprecated
Component: gnome-volume-control
unspecified
Other other
: Normal normal
: ---
Assigned To: gnome media maintainers
gnome media maintainers
: 123134 127378 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2003-10-05 20:13 UTC by Vladimir Mencl
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Vladimir Mencl 2003-10-05 20:13:50 UTC
Distribution: Fedora Core release 0.94 (Severn)
Package: gnome-media
Severity: normal
Version: GNOME2.4.0 unspecified
Gnome-Distributor: GNOME.Org
Synopsis: gnome-volume-control crashed upon exit
Bugzilla-Product: gnome-media
Bugzilla-Component: gnome-volume-control [was: gmix]
Bugzilla-Version: unspecified
BugBuddy-GnomeVersion: 2.0 (2.4.0)
Description:
Description of the crash:

When I started gnome-volume-control, it reported:
  An error occurred while loading or saving configuration 
  information for gnome-volume-control. 
  Some of your configuration settings may not work properly.

Then I chose Settings=>Preferences, Reset labels to default values,
Close, Quit

gnome-volume-control crashed

Steps to reproduce the crash:
1. Start gnome-volume-control. Click OK on the error message.
2. Settings => Preferences, Reset labels to default values, Close
3. Quit
4. Crash

Expected Results:
Quit

How often does this happen?
100%

Additional Information:
When I click "Details" in the startup error message, I get these
report:
Bad key or directory name:
 "/apps/gnome-volume-control/OSS-Unknown-1/Vol  ": ` ' is an invalid
character in key/directory names
Bad key or directory name:
 "/apps/gnome-volume-control/OSS-Unknown-1/Pcm  ": ` ' is an invalid
character in key/directory names
Bad key or directory name:
 "/apps/gnome-volume-control/OSS-Unknown-1/Spkr ": ` ' is an invalid
character in key/directory names
Bad key or directory name:
 "/apps/gnome-volume-control/OSS-Unknown-1/Line ": ` ' is an invalid
character in key/directory names
Bad key or directory name:
 "/apps/gnome-volume-control/OSS-Unknown-1/Mic  ": ` ' is an invalid
character in key/directory names
Bad key or directory name:
 "/apps/gnome-volume-control/OSS-Unknown-1/CD   ": ` ' is an invalid
character in key/directory names
Bad key or directory name:
 "/apps/gnome-volume-control/OSS-Unknown-1/Pcm2 ": ` ' is an invalid
character in key/directory names

Note that when I only start gnome-volume-control and I do not select
Preferences and instead Quit immediately, gnome-volume-control freezes.

I copied my whole home directory from a different computer.



Debugging Information:

Backtrace was generated from '/usr/bin/gnome-volume-control'

(no debugging symbols found)...Using host libthread_db library
"/lib/tls/libthread_db.so.1".
(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...[Thread debugging using libthread_db
enabled]
[New Thread -1084751200 (LWP 15137)]
(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...0x0097cc02 in _dl_sysinfo_int80 ()
   from /lib/ld-linux.so.2

Thread 1 (Thread -1084751200 (LWP 15137))

  • #0 _dl_sysinfo_int80
    from /lib/ld-linux.so.2
  • #1 __waitpid_nocancel
    from /lib/tls/libpthread.so.0
  • #2 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 strlen
    from /lib/tls/libc.so.6
  • #5 vfprintf
    from /lib/tls/libc.so.6
  • #6 _IO_stdin_used
  • #7 ??
  • #8 ??
  • #9 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #0 _dl_sysinfo_int80
    from /lib/ld-linux.so.2




------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-10-05 16:13 -------

Reassigning to the default owner of the component, gnome-media-maint@bugzilla.gnome.org.

Comment 1 Ted Gould 2003-10-14 03:15:56 UTC
I can't repoduce this.  Did you run a 2.3.x version of gnome-media? 
That was a problem in those versions.
Comment 2 Vladimir Mencl 2003-10-14 03:21:45 UTC
Yes, I it is gnome-media-2.3.7 (as included in Fedora Core)
Comment 3 Ted Gould 2003-10-14 04:50:15 UTC
Thanks for submitting the bug, but it's already been fixed in 2.3.8. 
Fedora should really upgrade to 2.4.0, there are other fixes in there
also.  Thanks again.

*** This bug has been marked as a duplicate of 119979 ***
Comment 4 Elijah Newren 2003-12-10 05:29:55 UTC
*** Bug 127378 has been marked as a duplicate of this bug. ***
Comment 5 Elijah Newren 2003-12-10 05:31:44 UTC
*** Bug 123134 has been marked as a duplicate of this bug. ***