GNOME Bugzilla – Bug 501358
crash in Tasks: Usando wine al parecer n...
Last modified: 2007-12-03 21:59:32 UTC
What were you doing when the application crashed? Usando wine al parecer no me funciona bien 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.23.1-21.fc7 #1 SMP Thu Nov 1 21:09:24 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Bluecurve Icon Theme: nuoveXT.2.2 Memory status: size: 207618048 vsize: 207618048 resident: 26730496 share: 16994304 rss: 26730496 rss_rlim: 4294967295 CPU usage: start_time: 1196714316 rtime: 86 utime: 68 stime: 18 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 -1208863008 (LWP 8993)] [New Thread -1247077488 (LWP 9041)] [New Thread -1269830768 (LWP 9015)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 180624
Thread 1 (Thread -1208863008 (LWP 8993))
----------- .xsession-errors (6 sec old) --------------------- localuser:root being added to access control list SESSION_MANAGER=local/daniel:/tmp/.ICE-unix/8767 ** (gnome-system-monitor:8957): WARNING **: SELinux was found but is not enabled. CalDAV Eplugin starting up ... ** (evolution:8993): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:8993): DEBUG: mailto URL program: evolution (evolution:8993): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0 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. 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 431459 ***