GNOME Bugzilla – Bug 432719
crash in Gimmie:
Last modified: 2007-04-26 07:28:44 UTC
What were you doing when the application crashed? Distribution: Ubuntu 7.04 (feisty) Gnome Release: 2.18.1 2007-04-10 (Ubuntu) BugBuddy Version: 2.18.1 System: Linux 2.6.20-15-generic #2 SMP Sun Apr 15 07:36:31 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: Darkilouche Icon Theme: Human 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 (34 sec old) --------------------- Watching directory /home/alex/grafica/temi/Tux_G2_Pack.tar.gz_FILES/Tux G2 - Ecrans de démarrage (total watches = 47) Watching directory /home/alex/documenti/csatlante/RutilTv0.13/lib/src (total watches = 48) Watching directory /home/alex/documenti/csatlante/RutilTv0.13/include/private (total watches = 49) starting indexing... ** (trackerd:5582): CRITICAL **: check_directory: assertion `tracker_is_directory (uri)' failed indexing #1 - /home/alex flushing all words Finished indexing. Waiting for new events... ** Message: Hit unexpected error "Non si trova sullo stesso file system" while doing a file operation. ** Message: Hit unexpected error "Non si trova sullo stesso file system" while doing a file operation. ** Message: Hit unexpected error "Non si trova sullo stesso file system" while doing a file operation. ** Message: Hit unexpected error "Non si trova sullo stesso file system" while doing a file operation. ** Message: Hit unexpected error "Non si trova sullo stesso file system" while doing a file operation. libhal-storage.c 1056 : INFO: called LIBHAL_FREE_DBUS_ERROR but dbusError was not set. -------------------------------------------------- Traceback (most recent call last):
+ Trace 130079
for i in items:
for i in self.get_items_uncached():
yield DriveItem(drive)
raise ValueError, "Cannot find URI to open for drive '%s'" % drive
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 421620 ***