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 380101 - crash in Sound: gnome-menu > startingsou...
crash in Sound: gnome-menu > startingsou...
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: 2006-11-28 11:07 UTC by HZY01222
Modified: 2006-12-08 03:12 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description HZY01222 2006-11-28 11:07:38 UTC 
Version: 2.16.2

What were you doing when the application crashed?
gnome-menu > startingsound


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

Memory status: size: 30162944 vsize: 0 resident: 30162944 share: 0 rss: 13135872 rss_rlim: 0
CPU usage: start_time: 1164711972 rtime: 0 utime: 24 stime: 0 cutime:23 cstime: 0 timeout: 1 it_real_value: 0 frequency: 3

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 6982)]
(no debugging symbols found)
0x40690608 in waitpid () from /lib/libpthread.so.0

+ Trace 89963

Thread 1 (Thread 16384 (LWP 6982))

  • #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


André Klapper





          2006-11-28 16:00:35 UTC
        



Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!







Comment 2


André Klapper





          2006-12-08 03:12:01 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 ***