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 370054 - crash in Sound: Lauching Sound config
crash in Sound: Lauching Sound config
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-03 15:31 UTC by emmanuel.cecchet
Modified: 2007-03-16 22:13 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description emmanuel.cecchet 2006-11-03 15:31:41 UTC 
Version: 2.16.0

What were you doing when the application crashed?
Lauching Sound config


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: 26460160 vsize: 0 resident: 26460160 share: 0 rss: 10719232 rss_rlim: 0
CPU usage: start_time: 1162567872 rtime: 0 utime: 15 stime: 0 cutime:14 cstime: 0 timeout: 1 it_real_value: 0 frequency: 2

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 -1208833824 (LWP 14442)]
(no debugging symbols found)
0x00a6e402 in __kernel_vsyscall ()

+ Trace 82385

Thread 1 (Thread -1208833824 (LWP 14442))

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


Sebastien Bacher





          2006-12-17 22:58:53 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-03-16 22:13:40 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 ***