GNOME Bugzilla – Bug 462922
crash in Tasks:
Last modified: 2007-10-07 18:49:01 UTC
Version: 2.10 What were you doing when the application crashed? Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.22.1-33.fc7 #1 SMP Mon Jul 23 17:33:07 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: nuoveXT-1.6 Memory status: size: 127311872 vsize: 127311872 resident: 40427520 share: 30826496 rss: 40427520 rss_rlim: 4294967295 CPU usage: start_time: 1186087837 rtime: 137 utime: 121 stime: 16 cutime:2 cstime: 9 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 -1208998176 (LWP 4694)] [New Thread -1245803632 (LWP 4735)] [New Thread -1224819824 (LWP 4731)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 152413
Thread 1 (Thread -1208998176 (LWP 4694))
----------- .xsession-errors --------------------- QApplication::postEvent: Unexpected null receiver QApplication::postEvent: Unexpected null receiver QApplication::postEvent: Unexpected null receiver QApplication::postEvent: Unexpected null receiver CalDAV Eplugin starting up ... evolution-shell-Message: Killing old version of evolution-data-server... ** (evolution:4694): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:4694): DEBUG: mailto URL program: evolution QApplication::postEvent: Unexpected null receiver 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 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x4200020 --------------------------------------------------
Thanks for taking the time to report this bug. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks in advance!
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 364700 ***