GNOME Bugzilla – Bug 497377
crash in Tasks:
Last modified: 2007-11-16 17:38:15 UTC
Version: 2.10 What were you doing when the application crashed? 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.5-76.fc7 #1 SMP Thu Aug 30 13:47:21 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 111742976 vsize: 111742976 resident: 34861056 share: 26021888 rss: 34861056 rss_rlim: 4294967295 CPU usage: start_time: 1195220745 rtime: 103 utime: 90 stime: 13 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 -1209219360 (LWP 3109)] [New Thread -1261446256 (LWP 3124)] [New Thread -1228481648 (LWP 3114)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 178125
Thread 1 (Thread -1209219360 (LWP 3109))
----------- .xsession-errors (7 sec old) --------------------- JACK tmpdir identified as [/dev/shm] ASSERT: "!name.isEmpty()" in kdirlister.cpp (1555) ASSERT: "!name.isEmpty()" in kdirlister.cpp (1555) X Error: BadAccess (attempt to access private resource denied) 10 Major opcode: 2 Minor opcode: 0 Resource id: 0x2c0000e JACK tmpdir identified as [/dev/shm] WARNING: DCOPReply<>: cast to 'QStringList' error WARNING: DCOPReply<>: cast to 'QString' error CalDAV Eplugin starting up ... ** (evolution:3109): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:3109): 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 431459 ***