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 387812 - crash in Sound:
crash in Sound:
Status: RESOLVED DUPLICATE of bug 384931
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-20 07:23 UTC by Simon Matthews
Modified: 2006-12-20 11:40 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description Simon Matthews 2006-12-20 07:23:18 UTC 
Version: 2.16.2

What were you doing when the application crashed?



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

Memory status: size: 102387712 vsize: 102387712 resident: 13082624 share: 9572352 rss: 13082624 rss_rlim: -1
CPU usage: start_time: 1166599393 rtime: 21 utime: 20 stime: 1 cutime:1 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 "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 47621078065424 (LWP 16397)]
0x00002b4fa445d925 in waitpid () from /lib/libpthread.so.0

+ Trace 95613

Thread 1 (Thread 47621078065424 (LWP 16397))

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






Comment 1


Susana





          2006-12-20 11:40:56 UTC
        



Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


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