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 391784 - crash in Sound: I tried to run "Sound" u...
crash in Sound: I tried to run "Sound" u...
Status: RESOLVED DUPLICATE of bug 363005
Product: gnome-control-center
Classification: Core
Component: Sound
2.16.x
Other All
: High critical
: ---
Assigned To: Control-Center Maintainers
Control-Center Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-01-02 07:26 UTC by randy
Modified: 2007-01-02 12:53 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description randy 2007-01-02 07:26:36 UTC
Version: 2.16.2

What were you doing when the application crashed?
I tried to run "Sound" under System -> Preferences -> Sound


Distribution: Gentoo Base System version 1.12.6
Gnome Release: 2.16.2 2007-01-01 (Gentoo)
BugBuddy Version: 2.16.0

Memory status: size: 21721088 vsize: 0 resident: 21721088 share: 0 rss: 11415552 rss_rlim: 0
CPU usage: start_time: 1167722737 rtime: 0 utime: 27 stime: 0 cutime:25 cstime: 0 timeout: 2 it_real_value: 0 frequency: 5

Backtrace was generated from '/usr/bin/gnome-sound-properties'

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
`system-supplied DSO at 0xb7fb8000' has disappeared; keeping its symbols.
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1227618640 (LWP 10513)]
0xb7fb8410 in __kernel_vsyscall ()

Thread 1 (Thread -1227618640 (LWP 10513))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 main
  • #0 __kernel_vsyscall

Comment 1 Susana 2007-01-02 12:53:37 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


*** This bug has been marked as a duplicate of 363005 ***