GNOME Bugzilla – Bug 542464
crash in Gimmie: pressed "Linux".
Last modified: 2008-07-13 21:16:07 UTC
What were you doing when the application crashed? pressed "Linux". Distribution: Ubuntu 8.04 (hardy) Gnome Release: 2.22.2 2008-06-03 (Ubuntu) BugBuddy Version: 2.22.0 System: Linux 2.6.24-19-generic #1 SMP Wed Jun 18 14:43:41 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Enabled GTK+ Theme: Clearlooks Icon Theme: Crux Memory status: size: 0 vsize: 0 resident: 0 share: 0 rss: 0 rss_rlim: 0 CPU usage: start_time: 0 rtime: 0 utime: 0 stime: 0 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0 ----------- .xsession-errors (30 sec old) --------------------- evolution-alarm-notify-Message: Fri Jul 11 00:00:00 2008 evolution-alarm-notify-Message: Thu Jul 10 18:57:44 2008 /usr/bin/compiz.real (video) - Warn: No 8 bit GLX pixmap format, disabling YV12 image format I/O warning : failed to load external entity "/home/matthew/.compiz/session/default0" Starting gtk-window-decorator PID TTY TIME CMD sys:1: Warning: value "((GaProtocol) 2)" of type `GaProtocol' is invalid or out of range for property `flags' of type `GaProtocol' sys:1: Warning: g_hash_table_unref: assertion `hash_table != NULL' failed (evolution:11823): GLib-GObject-WARNING **: IA__g_object_weak_unref: couldn't find weak ref 0xb644f030(0x85e40f0) sys:1: Warning: value "((GaProtocol) 2)" of type `GaProtocol' is invalid or out of range for property `flags' of type `GaProtocol' sys:1: Warning: g_hash_table_unref: assertion `hash_table != NULL' failed Unable to open desktop file /home/matthew/Desktop/Zussaweb.desktop for panel launcher: No such file or directory -------------------------------------------------- Gimmie Version: 0.2.8 Traceback (most recent call last):
+ Trace 202519
self.item.handle_drag_data_received(selection, target_type)
uri_list.append(gnomevfs.URI(uri))
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 429536 ***