GNOME Bugzilla – Bug 493979
crash in Volume Control: changing the PCM setting
Last modified: 2007-12-19 14:02:45 UTC
Version: 2.18.0 What were you doing when the application crashed? changing the PCM setting Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.22.4-65.fc7 #1 SMP Tue Aug 21 22:36:56 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Bluecurve Icon Theme: Bluecurve Memory status: size: 55078912 vsize: 55078912 resident: 11542528 share: 8679424 rss: 11542528 rss_rlim: 4294967295 CPU usage: start_time: 1194312627 rtime: 72 utime: 61 stime: 11 cutime:2 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/gnome-volume-control' (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 -1208260896 (LWP 4386)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 175595
Thread 1 (Thread -1208260896 (LWP 4386))
----------- .xsession-errors (9 sec old) --------------------- fixme:wintab32:WTOverlap (0xc00, 0): stub fixme:wintab32:WTOverlap (0xc04, 0): stub fixme:wintab32:WTOverlap (0xc08, 0): stub fixme:wintab32:WTOverlap (0xc00, 1): stub fixme:wintab32:WTOverlap (0xc04, 1): stub fixme:wintab32:WTOverlap (0xc08, 1): stub fixme:wintab32:WTOverlap (0xc00, 0): stub fixme:wintab32:WTOverlap (0xc04, 0): stub fixme:wintab32:WTOverlap (0xc08, 0): stub Initializing nautilus-search-tool extension (gnome-about-me:4345): about-me-properties-WARNING **: e_book_get_self: there was no self contact UID stored in gconf (gnome-volume-control:4386): GLib-GObject-CRITICAL **: g_object_ref: assertion `object->ref_count > 0' failed --------------------------------------------------
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 471133 ***