GNOME Bugzilla – Bug 445762
crash in Tasks: pressed ctrl+w in evolut...
Last modified: 2007-06-12 00:46:24 UTC
What were you doing when the application crashed? pressed ctrl+w in evolution to send it background 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.3194.fc7 #1 SMP Wed May 23 22:47:07 EDT 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: Permissive Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 598298624 vsize: 598298624 resident: 35266560 share: 19398656 rss: 35266560 rss_rlim: 18446744073709551615 CPU usage: start_time: 1181398074 rtime: 382 utime: 341 stime: 41 cutime:374 cstime: 49 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' (no debugging symbols found) Using host libthread_db library "/lib64/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 46912496508512 (LWP 3529)] [New Thread 1147435344 (LWP 3579)] (no debugging symbols found) 0x000000358b40d89f in waitpid () from /lib64/libpthread.so.0
+ Trace 139578
Thread 1 (Thread 46912496508512 (LWP 3529))
----------- .xsession-errors (59 sec old) --------------------- SDL_GL_BLUE_SIZE: 8 SDL_GL_DEPTH_SIZE: 24 SDL_GL_DOUBLEBUFFER: 1 Opened audio at 22050 Hz 16 bit stereo No current table name! (the first time is normal...) Stopping sound...ok. Stopping graphics...ok. CalDAV Eplugin starting up ... ** (evolution:3529): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:3529): 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 (evolution:3529): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0 --------------------------------------------------
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 334966 ***