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 389252 - crash in Sound: just trying to open the ...
crash in Sound: just trying to open the ...
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-12-24 16:59 UTC by techno.mayix
Modified: 2007-01-04 05:01 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description techno.mayix 2006-12-24 16:59:05 UTC
Version: 2.16.2

What were you doing when the application crashed?
just trying to open the sound conf option and using rosegarden


Distribution: Gentoo Base System version 1.12.6
Gnome Release: 2.16.2 2006-12-22 (Gentoo)
BugBuddy Version: 2.16.0

Memory status: size: 24592384 vsize: 0 resident: 24592384 share: 0 rss: 15896576 rss_rlim: 0
CPU usage: start_time: 1166957702 rtime: 0 utime: 264 stime: 0 cutime:261 cstime: 0 timeout: 3 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)
`system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols.
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1225439568 (LWP 13864)]
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1225439568 (LWP 13864))

  • #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-25 10:33:56 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 2007-01-04 05:01: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 ***