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 393631 - crash in Sound: Open the program Sistema...
crash in Sound: Open the program Sistema...
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-01-06 18:58 UTC by nomail
Modified: 2007-01-18 12:07 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description nomail 2007-01-06 18:58:08 UTC 
Version: 2.16.2

What were you doing when the application crashed?
Open the program
Sistematic


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

Memory status: size: 21712896 vsize: 0 resident: 21712896 share: 0 rss: 11489280 rss_rlim: 0
CPU usage: start_time: 1168109864 rtime: 0 utime: 41 stime: 0 cutime:33 cstime: 0 timeout: 8 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)
`system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols.
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1226000720 (LWP 5393)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 99955

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






Comment 1


Christian Kirbach





          2007-01-06 18:59:38 UTC
        



unique

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-18 12:07:19 UTC
        



Thanks for the bug report. This bug has been fixed. The fix will be available in GNOME 2.16.3.
Please feel free to report any further bugs you find.


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