GNOME Bugzilla – Bug 477164
crash in Volume Control: listening music
Last modified: 2007-10-03 09:50:06 UTC
Version: 2.18.0 What were you doing when the application crashed? listening music Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:47:07 EDT 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Orange-LiNstaBlackPlastic Icon Theme: Aero-stlxv Memory status: size: 313446400 vsize: 313446400 resident: 21573632 share: 10338304 rss: 21573632 rss_rlim: 18446744073709551615 CPU usage: start_time: 1189850073 rtime: 642 utime: 633 stime: 9 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 "/lib64/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 46912496317936 (LWP 3274)] (no debugging symbols found) 0x000000377a00d865 in waitpid () from /lib64/libpthread.so.0
+ Trace 163073
Thread 1 (Thread 46912496317936 (LWP 3274))
----------- .xsession-errors (68 sec old) --------------------- SELECT TrackId FROM Tracks WHERE Artist LIKE :artist AND Title LIKE :title LIMIT 1' Executing reader on sql ' SELECT TrackId FROM Tracks WHERE Artist LIKE :artist AND Title LIKE :title LIMIT 1' (navigator-bin:3250): Gtk-WARNING **: 無法在 module_path 中找出佈景主題引擎:‘ubuntulooks’, *** e = [Exception... "ServiceManager::GetService returned failure code:" nsresult: "0x80570016 (NS_ERROR_XPC_GS_RETURNED_FAILURE)" location: "JS frame :: chrome://browser/content/utilityOverlay.js *** No preference found for pref.browser.homepage.disable_button.restore_default --------------------------------------------------
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 ***