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 427330 - crash in Sound: turning on sound
crash in Sound: turning on sound
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-04-07 17:22 UTC by rod
Modified: 2007-04-08 11:48 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description rod 2007-04-07 17:22:54 UTC 
Version: 2.16.2

What were you doing when the application crashed?
turning on sound


Distribution: Slackware Slackware 11.0.0
Gnome Release: 2.16.3 2007-03-03 (Dropline GNOME)
BugBuddy Version: 2.16.0

Memory status: size: 10969088 vsize: 0 resident: 20312064 share: 0 rss: 10969088 rss_rlim: 0
CPU usage: start_time: 1175966527 rtime: 0 utime: 19 stime: 0 cutime:19 cstime: 0 timeout: 0 it_real_value: 0 frequency: 4

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

+ Trace 125830

Thread 1 (Thread 16384 (LWP 6476))

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


palfrey





          2007-04-07 21:20:07 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


Jens Granseuer





          2007-04-08 11:48:34 UTC
        



Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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