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 388147 - crash in Sound: Attempted to open sound ...
crash in Sound: Attempted to open sound ...
Status: RESOLVED DUPLICATE of bug 368901
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: 2006-12-21 03:29 UTC by jstaelen
Modified: 2006-12-21 13:52 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description jstaelen 2006-12-21 03:29:15 UTC 
Version: 2.16.2

What were you doing when the application crashed?
Attempted to open sound preferences wizard.


Distribution: Slackware Slackware 11.0.0
Gnome Release: 2.16.2 2006-11-22 (Dropline GNOME)
BugBuddy Version: 2.16.0

Memory status: size: 10964992 vsize: 0 resident: 20471808 share: 0 rss: 10964992 rss_rlim: 0
CPU usage: start_time: 1166674974 rtime: 0 utime: 75 stime: 0 cutime:72 cstime: 0 timeout: 3 it_real_value: 0 frequency: 16

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)
[Thread debugging using libthread_db enabled]
[New Thread 16384 (LWP 2073)]
(no debugging symbols found)
0x40690608 in waitpid () from /lib/libpthread.so.0

+ Trace 95861

Thread 1 (Thread 16384 (LWP 2073))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 ??
    from /usr/lib/libgnomeui-2.so.0
  • #2 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 __pthread_sighandler
    from /lib/libpthread.so.0
  • #4 <signal handler called>
  • #5 main
  • #0 waitpid
    from /lib/libpthread.so.0 






Comment 1


Sebastien Bacher





          2006-12-21 13:52:50 UTC
        



Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


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