GNOME Bugzilla – Bug 416834
crash in Sound: test
Last modified: 2007-04-01 13:30:36 UTC
Version: 2.17.92 What were you doing when the application crashed? test Distribution: Fedora release 6.91 (Rawhide) Gnome Release: 2.17.92 2007-02-27 (Red Hat, Inc) BugBuddy Version: 2.17.4 System: Linux 2.6.18-1.2798.fc6 #1 SMP Mon Oct 16 14:54:20 EDT 2006 i686 X Vendor: The X.Org Foundation X Vendor Release: 10299901 Selinux: Permissive Accessibility: Enabled GTK+ Theme: Clearlooks Icon Theme: Echo Memory status: size: 100679680 vsize: 100679680 resident: 17846272 share: 12390400 rss: 17846272 rss_rlim: 4294967295 CPU usage: start_time: 1173547589 rtime: 211 utime: 198 stime: 13 cutime:3 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 -1209088288 (LWP 898)] [New Thread -1269892208 (LWP 909)] [New Thread -1248908400 (LWP 904)] (no debugging symbols found) 0x00b1b402 in __kernel_vsyscall ()
+ Trace 117491
Thread 1 (Thread -1209088288 (LWP 898))
----------- .xsession-errors (23791 sec old) --------------------- ** (nm-applet:1820): WARNING **: <WARN> nma_dbus_init(): org.freedesktop.DBus.Error.NoServer raised: Failed to connect to socket /var/run/dbus/system_bus_socket: Connessione rifiutata ** (nm-applet:1820): WARNING **: <WARN> nma_dbus_init(): org.freedesktop.DBus.Error.NoServer raised: Failed to connect to socket /var/run/dbus/system_bus_socket: Connessione rifiutata --------------------------------------------------
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!
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 413801 ***