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 355215 - crash in Sound: click sound
crash in Sound: click sound
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-10 01:45 UTC by thanate_d
Modified: 2006-09-10 14:18 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description thanate_d 2006-09-10 01:45:49 UTC 
Version: 2.16.0

What were you doing when the application crashed?
click sound


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

Memory status: size: 26361856 vsize: 0 resident: 26361856 share: 0 rss: 15196160 rss_rlim: 0
CPU usage: start_time: 1157852720 rtime: 0 utime: 68 stime: 0 cutime:54 cstime: 0 timeout: 14 it_real_value: 0 frequency: 5

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

Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1227213120 (LWP 4055)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 72012

Thread 1 (Thread -1227213120 (LWP 4055))

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






Comment 1


Rob Bradford





          2006-09-10 14:18:34 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 ***