GNOME Bugzilla – Bug 447981
crash in Tasks: start evolution (Email)
Last modified: 2007-06-15 23:08:00 UTC
What were you doing when the application crashed? start evolution (Email) Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.0 2007-03-23 (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: Clearlooks Icon Theme: Fedora Memory status: size: 96436224 vsize: 96436224 resident: 22454272 share: 14049280 rss: 22454272 rss_rlim: 4294967295 CPU usage: start_time: 1181933335 rtime: 91 utime: 78 stime: 13 cutime:0 cstime: 1 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1208592672 (LWP 3232)] (no debugging symbols found) 0x00498402 in __kernel_vsyscall ()
+ Trace 141274
Thread 1 (Thread -1208592672 (LWP 3232))
----------- .xsession-errors --------------------- p.run() File "/usr/bin/puplet", line 355, in run self._getOnDbus() File "/usr/bin/puplet", line 229, in _getOnDbus "/Updatesd") File "/usr/lib/python2.5/site-packages/dbus/_dbus.py", line 410, in get_object follow_name_owner_changes=follow_name_owner_changes) File "/usr/lib/python2.5/site-packages/dbus/proxies.py", line 230, in __init__ _dbus_bindings.UInt32(0)) File "/usr/lib/python2.5/site-packages/dbus/proxies.py", line 169, in __call__ reply_message = self._connection.send_message_with_reply_and_block(message, timeout) dbus.DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The name edu.duke.linux.yum was not provided by any .service files CalDAV Eplugin starting up ... ** (evolution:3232): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:3232): DEBUG: mailto URL program: evolution --------------------------------------------------
bug gone when I change my timezone from "Asia/Makassar" to "Asia/Singapore" which is the same (GMT +8)..
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 425129 ***