GNOME Bugzilla – Bug 438075
crash in Deskbar:
Last modified: 2007-05-13 10:52:04 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: Enabled GTK+ Theme: Clearlooks Icon Theme: nuoveXT-1.6 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 (11 sec old) --------------------- Bucket count (max is 524288) is 196556 and Record Count is 185154 preferred bucket count is 185154 starting database closure for thread main Database closed for thread main starting database closure for thread main Database closed for thread main Checking tracker DB version...Current version is 15 and needed version is 13 GTK Accessibility Module initialized Initialising aMule Checking if there is an instance already running... There seems to be an instance of aMule already running If this is not the case, you may have to remove the file ~/.aMule/muleLock, to allow aMule to run. Attempting to raise current running instance. No se puede abrir el archivo de escritorio /usr/share/applications/listen.desktop para el lanzador del panel: No existe el fichero ó directorio -------------------------------------------------- Traceback (most recent call last):
+ Trace 133919
self.load (f)
mod_instance = getattr (mod, handler) ()
self.tracker = bus.get_object('org.freedesktop.Tracker','/org/freedesktop/tracker')
follow_name_owner_changes=follow_name_owner_changes)
_dbus_bindings.UInt32(0))
reply_message = self._connection.send_message_with_reply_and_block(message, timeout)
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 for tracker. *** This bug has been marked as a duplicate of 403752 ***