GNOME Bugzilla – Bug 454468
crash in Deskbar:
Last modified: 2007-07-11 17:34:06 UTC
What were you doing when the application crashed? 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.21-1.3228.fc7 #1 SMP Tue Jun 12 15:37:31 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Bluecurve Icon Theme: Bluecurve 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 (941 sec old) --------------------- I/O error : Permission denied I/O error : Permission denied I/O error : Permission denied I/O error : Permission denied I/O error : Permission denied I/O error : Permission denied (evolution:4020): evolution-mail-WARNING **: ignored this junk plugin: not enabled or we have already loaded one (evolution:4020): e-utils-WARNING **: Plugin 'Bogofilter junk plugin' failed to load hook 'org.gnome.evolution.mail.junk:1.0' ** (evolution:4020): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:4020): DEBUG: mailto URL program: evolution libnm_glib_nm_state_cb: dbus returned an error. (org.freedesktop.DBus.Error.ServiceUnknown) The name org.freedesktop.NetworkManager was not provided by any .service files play stio: Can't open input file `/usr/share/gnome/sounds/email.wav': No such file or directory -------------------------------------------------- Traceback (most recent call last):
+ Trace 146264
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 403752 ***
*** Bug 455469 has been marked as a duplicate of this bug. ***
*** Bug 455915 has been marked as a duplicate of this bug. ***