GNOME Bugzilla – Bug 496641
crash in Tasks: opening the app
Last modified: 2007-11-14 10:55:09 UTC
Version: 2.10 What were you doing when the application crashed? opening the app 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.9-91.fc7 #1 SMP Thu Sep 27 23:10:59 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Permissive Accessibility: Disabled GTK+ Theme: Crux Icon Theme: Crux Memory status: size: 114356224 vsize: 114356224 resident: 36589568 share: 26021888 rss: 36589568 rss_rlim: 4294967295 CPU usage: start_time: 1195013950 rtime: 123 utime: 111 stime: 12 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 -1209010464 (LWP 4411)] [New Thread -1240470640 (LWP 4431)] [New Thread -1217709168 (LWP 4428)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 177582
Thread 1 (Thread -1209010464 (LWP 4411))
----------- .xsession-errors (6 sec old) --------------------- report junk?? [BULK] $59.95 Price for 50mg x 10 pills report junk?? [BULK] Viagra 50mg x 10 pills buy now (gnome-terminal:3123): Vte-WARNING **: No handler for control sequence `device-control-string' defined. (gnome-terminal:3123): Vte-WARNING **: No handler for control sequence `device-control-string' defined. report junk?? CLAIM YOUR 1 FREE BOTTLE EnlargePENIS PILL FROM THIS SITE tne CalDAV Eplugin starting up ... ** (evolution:4411): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:4411): 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. 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 ***