GNOME Bugzilla – Bug 476407
crash in Tasks: I think I just left it o...
Last modified: 2007-09-20 16:53:11 UTC
Version: 2.10 What were you doing when the application crashed? I think I just left it open of an extended period (power saving settings kicked in). 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.4-65.fc7 #1 SMP Tue Aug 21 22:36:56 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Mist Icon Theme: Mist Memory status: size: 142610432 vsize: 142610432 resident: 41865216 share: 32002048 rss: 41865216 rss_rlim: 4294967295 CPU usage: start_time: 1189650756 rtime: 83 utime: 75 stime: 8 cutime:3 cstime: 6 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 -1208723744 (LWP 12337)] [New Thread -1257886832 (LWP 12394)] [New Thread -1247003760 (LWP 12373)] [New Thread -1226019952 (LWP 12370)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 162512
Thread 1 (Thread -1208723744 (LWP 12337))
----------- .xsession-errors --------------------- Resource id: 0x4009fb0 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 3 Minor opcode: 0 Resource id: 0x4009e54 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 3 Minor opcode: 0 Resource id: 0x400a3b7 CalDAV Eplugin starting up ... evolution-shell-Message: Killing old version of evolution-data-server... ** (evolution:12337): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:12337): 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 --------------------------------------------------
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 the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers? *** This bug has been marked as a duplicate of 431459 ***