GNOME Bugzilla – Bug 508598
crash in Tasks: Clicked on a folder
Last modified: 2008-01-10 22:39:33 UTC
Version: 2.10 What were you doing when the application crashed? Clicked on a folder 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.12-52.fc7 #1 SMP Tue Dec 18 21:18:02 EST 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Mac4Lin_GTK_v0.3 Icon Theme: OSX_Cursors_v0.2 Memory status: size: 126091264 vsize: 126091264 resident: 39882752 share: 30375936 rss: 39882752 rss_rlim: 4294967295 CPU usage: start_time: 1199994589 rtime: 291 utime: 253 stime: 38 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 -1209137440 (LWP 32120)] [New Thread -1257354352 (LWP 32163)] [New Thread -1246864496 (LWP 32137)] [New Thread -1221727344 (LWP 32136)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 184845
Thread 1 (Thread -1209137440 (LWP 32120))
----------- .xsession-errors (84296 sec old) --------------------- (evolution:19008): e-data-server-ui-CRITICAL **: e_source_combo_box_set_active_uid: assertion `gtk_tree_row_reference_valid (reference)' failed JACK tmpdir identified as [/dev/shm] (evolution:19008): Gdk-CRITICAL **: gdk_window_set_title: assertion `title != NULL' failed JACK tmpdir identified as [/dev/shm] play stio: Can't open input file `/usr/share/gnome/sounds/email.wav': No such file or directory JACK tmpdir identified as [/dev/shm] play stio: Can't open input file `/usr/share/gnome/sounds/email.wav': No such file or directory JACK tmpdir identified as [/dev/shm] JACK tmpdir identified as [/dev/shm] JACK tmpdir identified as [/dev/shm] JACK tmpdir identified as [/dev/shm] JACK tmpdir identified as [/dev/shm] ...Too much output, ignoring rest... --------------------------------------------------
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 ***