Xfdesktop crashes when Ctrl+R. This happens when a file is removed in the desktop moving it to the trash, removing with delete key or removing ~/Desktop/file and Ctrl+R (to update the changes) is pressed. It crashes too when ctrl+R is pressed without changes in the desktop. I'm not using gamin, fam, and the problem appears with dbus and without it running. This is the error that I get when I press ctrl+R: bash-3.00$ xfdesktop (xfdesktop:2986): GLib-GObject-WARNING **: invalid uninstantiatable type `<invalid>' in cast to `GObject' (xfdesktop:2986): GLib-GObject-WARNING **: instance of invalid non-instantiatable type `(null)' (xfdesktop:2986): GLib-GObject-CRITICAL **: g_signal_handlers_disconnect_matched: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed (xfdesktop:2986): GLib-GObject-WARNING **: invalid uninstantiatable type `(null)' in cast to `GObject' (xfdesktop:2986): GLib-GObject-CRITICAL **: g_object_set_data: assertion `G_IS_OBJECT (object)' failed (xfdesktop:2986): GLib-GObject-WARNING **: invalid uninstantiatable type `(null)' in cast to `GObject' Segmentation fault bash-3.00$
(In reply to comment #0) I think is the same bug that this one here: http://bugzilla.xfce.org/show_bug.cgi?id=2271
*** This bug has been marked as a duplicate of bug 2271 ***
Created attachment 820 fixes the warnings This clears the icons before they are removed from the hash, otherwise for each 'regular' icon on the desktop these 5 lines of warnings are written I think this is not really a duplicate of the dbus/trash patch (xfdesktop:16232): GLib-GObject-WARNING **: invalid unclassed pointer in cast to `GObject' (xfdesktop:16232): GLib-GObject-WARNING **: instance with invalid (NULL) class pointer (xfdesktop:16232): GLib-GObject-CRITICAL **: g_signal_handlers_disconnect_matched: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed (xfdesktop:16232): GLib-GObject-WARNING **: invalid unclassed pointer in cast to `GObject' (xfdesktop:16232): GLib-GObject-CRITICAL **: g_object_set_data: assertion `G_IS_OBJECT (object)' failed
This patch seems to fix the warnings I had previously.
Yeah, this is a bit different. I can repro this on my setup now (well, I see the warnings, but I don't get a crash). I'll apply this later today...
*** Bug 2422 has been marked as a duplicate of this bug. ***
Slightly different fix, but either way this should be OK now.
gah, mark resolved.