GNOME Bugzilla – Bug 451923
crash in Deskbar: just starting up the com...
Last modified: 2007-06-28 23:32:15 UTC
What were you doing when the application crashed? just starting up the computer Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.2 2007-05-28 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.20-2925.11.fc7xen #1 SMP Mon Jun 11 16:18:59 EDT 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Permissive Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Tango 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 (16 sec old) --------------------- Using Sqlite version 3.3.13 Loading prepared queries... File loaded in 3,000000 ms initialising the indexer Opening index /home/matej/.Tracker/databases/Files Bucket count (max is 524288) is 294908 and Record Count is 191330 preferred bucket count is 191330 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 Nemohu otevřít soubor desktop /usr/share/applications/gnome-commander.desktop pro spouštěč na panelu : není souborem ani adresářem Identity added: /home/matej/.ssh/id_dsa (/home/matej/.ssh/id_dsa) Identity added: /home/matej/.ssh/identity (matej@komensky) -------------------------------------------------- Traceback (most recent call last):
+ Trace 144351
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)
self._named_service = conn.activate_name_owner(bus_name)
self.start_service_by_name(bus_name)
'su', (bus_name, flags)))
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. *** This bug has been marked as a duplicate of 445960 ***