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 428447 - crash in Sound: I went to system -
crash in Sound: I went to system -
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-11 00:21 UTC by kurt.s.hayes
Modified: 2007-04-11 18:50 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description kurt.s.hayes 2007-04-11 00:21:41 UTC 
Version: 2.16.0

What were you doing when the application crashed?
I went to system -> preferences -> sound


Distribution: Red Hat Enterprise Linux Server release 5 (Tikanga)
Gnome Release: 2.16.0 2006-09-04 (Red Hat, Inc)
BugBuddy Version: 2.16.0

Memory status: size: 261787648 vsize: 261787648 resident: 13611008 share: 9625600 rss: 13611008 rss_rlim: -1
CPU usage: start_time: 1176250950 rtime: 7 utime: 7 stime: 0 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/gnome-sound-properties'

(no debugging symbols found)
Using host libthread_db library "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912582774544 (LWP 3843)]
(no debugging symbols found)
0x00002aaaac597895 in waitpid () from /lib64/libpthread.so.0

+ Trace 126728

Thread 1 (Thread 46912582774544 (LWP 3843))

  • #0 waitpid
    from /lib64/libpthread.so.0
  • #1 gnome_gtk_module_info_get
    from /usr/lib64/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 main
  • #0 waitpid
    from /lib64/libpthread.so.0 






Comment 1


palfrey





          2007-04-11 16:14:50 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-11 18:50:54 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 ***