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 374264 - crash in Sound: When I click the "system...
crash in Sound: When I click the "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
: 374236 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2006-11-12 13:19 UTC by zwexin
Modified: 2006-12-08 03:13 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description zwexin 2006-11-12 13:19:33 UTC 
Version: 2.16.0

What were you doing when the application crashed?
When I click the "system->preferences->sound", the program has been crashed. My computer is IBM T20. My name is Wayne Zhou.


Distribution: Fedora Core release 6 (Zod)
Gnome Release: 2.16.0 2006-09-04 (Red Hat, Inc)
BugBuddy Version: 2.16.0

Memory status: size: 26308608 vsize: 0 resident: 26308608 share: 0 rss: 11804672 rss_rlim: 0
CPU usage: start_time: 1163337321 rtime: 0 utime: 51 stime: 0 cutime:47 cstime: 0 timeout: 4 it_real_value: 0 frequency: 6

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 -1208776480 (LWP 3743)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 85751

Thread 1 (Thread -1208776480 (LWP 3743))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 main
  • #0 __kernel_vsyscall 






Comment 1


André Klapper





          2006-11-13 10:29:45 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-11-13 10:34:03 UTC
        



*** Bug 374236 has been marked as a duplicate of this bug. ***






Comment 3


zwexin





          2006-11-13 14:22:53 UTC
        



I have installed these debuginfo packages as follow:

glib2-debuginfo-2.12.3-2.fc6.i386.rpm
gtk2-debuginfo-2.10.4-4.fc6.i386.rpm
gnome-vfs2-debuginfo-2.16.0-4.fc6.i386.rpm
gnome-utils-debuginfo-2.16.0-1.fc6.i386.rpm
glibc-debuginfo-common-2.5-3.i386.rpm
glibc-debuginfo-2.5-3.i386.rpm 
libgnomeui-debuginfo-2.16.0-4.fc6.i386.rpm

but the report likes this:

Distribution: Fedora Core release 6 (Zod)
Gnome Release: 2.16.0 2006-09-04 (Red Hat, Inc)
BugBuddy Version: 2.16.0

Memory status: size: 26312704 vsize: 0 resident: 26312704 share: 0 rss: 11571200 rss_rlim: 0
CPU usage: start_time: 1163425679 rtime: 0 utime: 49 stime: 0 cutime:46 cstime: 0 timeout: 3 it_real_value: 0 frequency: 6

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)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208903456 (LWP 2707)]
0x00a27402 in __kernel_vsyscall ()




+
Trace
    86069






Thread 1
          (Thread -1208903456 (LWP 2707))


    

  • 
#0
__kernel_vsyscall

    • 

  • 
#1
__waitpid_nocancel

    
                from
                /lib/libpthread.so.0

    

    • 

  • 
#2
libgnomeui_segv_handle

    
                at gnome-ui-init.c
                  line
                  870

    

    • 

  • 
#3
<signal handler called>

    • 

  • 
#4
main

    • 

  • 
#0
__kernel_vsyscall

    • 








Are there other debuginfo packages that I missed?






Comment 4


André Klapper





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