GNOME Bugzilla – Bug 504443
crash in Tasks: intentar manda un correo...
Last modified: 2007-12-19 16:03:05 UTC
Version: 2.10 What were you doing when the application crashed? intentar manda un correo electronico a yahoo Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-11-13 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.23.8-34.fc7 #1 SMP Thu Nov 22 23:05:33 EST 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: 127963136 vsize: 127963136 resident: 40001536 share: 32006144 rss: 40001536 rss_rlim: 4294967295 CPU usage: start_time: 1198067818 rtime: 103 utime: 96 stime: 7 cutime:0 cstime: 0 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 -1209030944 (LWP 4435)] [New Thread -1262081136 (LWP 4450)] [New Thread -1225167984 (LWP 4439)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 182337
Thread 1 (Thread -1209030944 (LWP 4435))
----------- .xsession-errors --------------------- Minor opcode: 0 Resource id: 0x1e0bc22 BBDB spinning up... QClipboard::setData: Cannot set X11 selection owner for PRIMARY X Error: BadWindow (invalid Window parameter) 3 Major opcode: 19 Minor opcode: 0 Resource id: 0x1e0006e CalDAV Eplugin starting up ... ** (evolution:4435): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:4435): 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:4435): e-data-server-ui-WARNING **: El archivo de claves no tiene el grupo «Passwords-Mail» --------------------------------------------------
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 467846 ***