GNOME Bugzilla – Bug 509069
crash in Tasks: Bug Buddy is asking me t...
Last modified: 2008-02-06 08:38:23 UTC
Version: 2.10 What were you doing when the application crashed? Bug Buddy is asking me to write what I was doing when Tasks suddenly stopped. I had just finished changing my Evolution preferences to load images in messages from my contacts. I switched to an old email with images from one of my contacts and looked at the images (which probably had been displayed before anyway) when Bug Buddy requested I write this. I did not know Tasks was running nor that it had stopped running. Aside from that in the last month this F7 machine has been extremely slow at times. A few times since the last kermel it would not display the login window after my absence and I had to press the reset button to regain the machine. Other times the windows would slowly be redrawn. It has not done this for a week. My FC2 machine has been even slower over the past month and the drive light has stayed lit for days on end. While that is happening the machine is almost unusable it is so slow, taking 3 to 6 minutes to boot and half a minute to draw the background. This machine also has recovered in the past week. The only unusual things I recall doing before this slowness started was listening to music from a local radio station choqfm.ca and upgrading Mozilla on the FC2 machine and trying to install Adobe and Flash to listen to that station. I haven't listened to that station since. This slowness may notbe related to the current problem Task seems to have had as it stopped suddenly and unnoticably a month or more ago and when I reported it as requested I was told it was a problem that already had been reported. I hope this is not wasting your time. If I should read something to better know what to do when Bug Buddy or whatever requests something, then please let me know about where or what reading to seek out. 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: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 148262912 vsize: 148262912 resident: 66105344 share: 41037824 rss: 66105344 rss_rlim: 4294967295 CPU usage: start_time: 1200106003 rtime: 7471 utime: 6762 stime: 709 cutime:40 cstime: 17 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 -1208554768 (LWP 26337)] [New Thread -1291580528 (LWP 1064)] [New Thread -1231037552 (LWP 1063)] [New Thread -1241527408 (LWP 31245)] [New Thread -1272812656 (LWP 26391)] [New Thread -1220027504 (LWP 26354)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 185121
Thread 1 (Thread -1208554768 (LWP 26337))
----------- .xsession-errors (314 sec old) --------------------- (evolution:26337): libebook-WARNING **: invalid escape, passing it through (evolution:26337): libebook-WARNING **: invalid escape, passing it through (evolution:26337): libebook-WARNING **: invalid escape, passing it through (evolution:26337): libebook-WARNING **: invalid escape, passing it through (evolution:26337): e-utils-WARNING **: calling e_icon_factory_get_icon_filename with unknown icon_size value (48) (evolution:26337): e-utils-WARNING **: Cannot resolve symbol 'org_gnome_new_mail_config' in plugin '/usr/lib/evolution/2.10/plugins/liborg-gnome-new-mail-notify.so' (not exported?) (evolution:26337): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x9a4f140' (evolution:26337): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x9a4f260' --------------------------------------------------
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 447591 ***