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 409848 - crash in Sound: I had been experiencing ...
crash in Sound: I had been experiencing ...
Status: RESOLVED DUPLICATE of bug 378184
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-02-20 02:37 UTC by nconroy181
Modified: 2007-02-20 16:58 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description nconroy181 2007-02-20 02:37:21 UTC 
Version: 2.16.1

What were you doing when the application crashed?
I had been experiencing sound problems - somehow the system was unable to detect the need to use the analog sound settings from my previous boots (go figure!).  I had managed to get most working by manually selecting the analog device.  I was checking out the options for sound capture when BugBuddy surfaced.


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 106635264 vsize: 0 resident: 106635264 share: 0 rss: 17764352 rss_rlim: 0
CPU usage: start_time: 1171934880 rtime: 0 utime: 242 stime: 0 cutime:226 cstime: 0 timeout: 16 it_real_value: 0 frequency: 5

Backtrace was generated from '/usr/bin/gnome-sound-properties'

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1225763152 (LWP 15439)]
[New Thread -1302340704 (LWP 15541)]
[New Thread -1285555296 (LWP 15539)]
[New Thread -1250161760 (LWP 15532)]
[New Thread -1275602016 (LWP 15531)]
[New Thread -1258599520 (LWP 15522)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 112170

Thread 1 (Thread -1225763152 (LWP 15439))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 __kernel_vsyscall
  • #5 raise
    from /lib/tls/i686/cmov/libc.so.6
  • #6 abort
    from /lib/tls/i686/cmov/libc.so.6
  • #7 __libc_message
    from /lib/tls/i686/cmov/libc.so.6
  • #8 free
    from /lib/tls/i686/cmov/libc.so.6
  • #9 g_free
    from /usr/lib/libglib-2.0.so.0
  • #10 gst_gconf_audio_src_get_type
    from /usr/lib/gstreamer-0.10/libgstgconfelements.so
  • #11 gconf_client_get_type
    from /usr/lib/libgconf-2.so.4
  • #12 gconf_listeners_notify
    from /usr/lib/libgconf-2.so.4
  • #13 gconf_client_value_changed
    from /usr/lib/libgconf-2.so.4
  • #14 gconf_client_value_changed
    from /usr/lib/libgconf-2.so.4
  • #15 g_source_is_destroyed
    from /usr/lib/libglib-2.0.so.0
  • #16 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #17 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #18 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #19 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #20 main
  • #0 __kernel_vsyscall 






Comment 1


palfrey





          2007-02-20 15:05:48 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-02-20 16:58:33 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 378184 ***