GNOME Bugzilla – Bug 488237
crash in Rhythmbox Music Player: I just edited /etc/dbus-...
Last modified: 2007-10-19 13:56:23 UTC
Version: 0.10.1 What were you doing when the application crashed? I just edited /etc/dbus-1/system.d/hal.conf The second I saved the changes, RhythmBox (and a few other things) crashed. I would guess that it was more of a generic gnome problem or something (or maybe im just not supposed to edit that file..) 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.9-91.fc7 #1 SMP Thu Sep 27 23:10:59 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 332120064 vsize: 332120064 resident: 57241600 share: 35164160 rss: 57241600 rss_rlim: 4294967295 CPU usage: start_time: 1192788406 rtime: 23886 utime: 21497 stime: 2389 cutime:4 cstime: 16 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/rhythmbox' (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 -1208329680 (LWP 3538)] [New Thread -1343239280 (LWP 3898)] [New Thread -1255957616 (LWP 3895)] [New Thread -1310082160 (LWP 3716)] [New Thread -1288709232 (LWP 3588)] [New Thread -1278219376 (LWP 3587)] [New Thread -1241445488 (LWP 3586)] [New Thread -1299199088 (LWP 3585)] [New Thread -1267729520 (LWP 3551)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 171384
Thread 1 (Thread -1208329680 (LWP 3538))
----------- .xsession-errors (7 sec old) --------------------- DeviceAdded, udi=/org/freedesktop/Hal/devices/usb_device_90c_1000_noserial_if0_scsi_host_scsi_device_lun0 DeviceAdded, udi=/org/freedesktop/Hal/devices/usb_devxscreensaver: 22:45:34: 0: unrecognised ClientMessage "_NET_ACTIVE_WINDOW" received xscreensaver: 22:45:34: 0: for window 0x260e7ba (gecko / Firefox-bin) xscreensaver: 22:46:05: 0: unrecognised ClientMessage "_NET_ACTIVE_WINDOW" received xscreensaver: 22:46:05: 0: for window 0x3c00022 (xterm / XTerm) xscreensaver: 22:48:29: 0: unrecognised ClientMessage "_NET_ACTIVE_WINDOW" received xscreensaver: 22:48:29: 0: for window 0x2e00022 (xterm / XTerm) (rhythmbox:3538): Rhythmbox-WARNING **: Client failure: Daemon connection failed RhythmDB-ERROR **: file rhythmdb-property-model.c: line 532 (rhythmdb_property_model_prop_changed_cb): assertion failed: (g_hash_table_remove (propmodel->priv->entries, entry)) aborting... --------------------------------------------------
I managed to crash the dbus daemon by introducing a typo (aka. syntax error) in its config file - hence a bunch of things crashed. I don't know if it is possible to handle something like that more gracefully? If not, this problem can probably be ignored
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 452703 ***