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 354431 - crash in Sound: trying to start sound pr...
crash in Sound: trying to start sound pr...
Status: RESOLVED DUPLICATE of bug 351002
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-09-05 12:33 UTC by thanate
Modified: 2006-09-05 14:55 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description thanate 2006-09-05 12:33:58 UTC
Version: 2.16.0

What were you doing when the application crashed?
trying to start sound preference


Distribution: Debian testing/unstable
Gnome Release: 2.16.0 2006-09-04 (GARNOME)
BugBuddy Version: 2.16.0

Memory status: size: 24403968 vsize: 0 resident: 24403968 share: 0 rss: 13340672 rss_rlim: 0
CPU usage: start_time: 1157459567 rtime: 0 utime: 64 stime: 0 cutime:58 cstime: 0 timeout: 6 it_real_value: 0 frequency: 8

Backtrace was generated from '/home/boat/garnome/bin/gnome-sound-properties'

Using host libthread_db library "/lib/tls/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1226455360 (LWP 15790)]
0xb72401de in __waitpid_nocancel () from /lib/tls/libpthread.so.0

Thread 1 (Thread -1226455360 (LWP 15790))

  • #0 __waitpid_nocancel
    from /lib/tls/libpthread.so.0
  • #1 libgnomeui_segv_handle
    at gnome-ui-init.c line 870
  • #2 <signal handler called>
  • #3 main
    at sound-properties-capplet.c line 478
  • #0 __waitpid_nocancel
    from /lib/tls/libpthread.so.0

Comment 1 Christian Kirbach 2006-09-05 14:55:36 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 351002 ***