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 387699 - crash in Sound: start gnome-sound-proper...
crash in Sound: start gnome-sound-proper...
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-19 22:56 UTC by emerg.reanimator
Modified: 2006-12-23 04:02 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description emerg.reanimator 2006-12-19 22:56:22 UTC
Version: 2.16.2

What were you doing when the application crashed?
start gnome-sound-properties


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

Memory status: size: 102780928 vsize: 102780928 resident: 12988416 share: 9592832 rss: 12988416 rss_rlim: -1
CPU usage: start_time: 1166568864 rtime: 17 utime: 16 stime: 1 cutime:0 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 47774238455584 (LWP 26871)]
0x00002b734d5e9925 in waitpid () from /lib/libpthread.so.0

Thread 1 (Thread 47774238455584 (LWP 26871))

  • #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 Sebastien Bacher 2006-12-19 23:08:50 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 emerg.reanimator 2006-12-21 11:05:13 UTC
Here is new callstak trace. I have rebuilded gnome with debug support
(CFLAGS = -g -O2 -pipe -march=k8 -mtune=k8" in make.conf). I added "threads" keyword in USE flags, but I have experience the problem without this keyword also. So now I am able to attach to target with gdb. Does trace contains enough info to find a clue? If not don't hesitate to contact me.

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 47159517370144 (LWP 2579)]
0x00002ae42d211925 in __libc_waitpid (pid=2585, stat_loc=0x7fff81df052c, 
    options=0) at waitpid.c:32
	in waitpid.c

Thread 1 (Thread 47159517370144 (LWP 2579))

  • #0 __libc_waitpid
    at waitpid.c line 32
  • #1 libgnomeui_segv_handle
    at gnome-ui-init.c line 870
  • #2 <signal handler called>
  • #3 main
    at sound-properties-capplet.c line 478

Comment 3 André Klapper 2006-12-23 04:02:26 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 ***