GNOME Bugzilla – Bug 470190
crash in Tasks: fetching new mail from t...
Last modified: 2007-09-04 18:31:23 UTC
Version: 2.10 What were you doing when the application crashed? fetching new mail from the server. Evolution was running on kde and karamba has to widgets on the fesktop. 420 MB RAM used , 500 RAM on system. 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.4-65.fc7 #1 SMP Tue Aug 21 22:36:56 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Bluecurve Icon Theme: Bluecurve Memory status: size: 136552448 vsize: 136552448 resident: 42045440 share: 34152448 rss: 42045440 rss_rlim: 4294967295 CPU usage: start_time: 1188044745 rtime: 234 utime: 197 stime: 37 cutime:4 cstime: 10 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 -1209162016 (LWP 8026)] [New Thread -1271501936 (LWP 8122)] [New Thread -1292481648 (LWP 8118)] [New Thread -1281991792 (LWP 8117)] [New Thread -1229886576 (LWP 8058)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 157823
Thread 1 (Thread -1209162016 (LWP 8026))
----------- .xsession-errors (613 sec old) --------------------- QObject::connect: No such slot BlueCurve::BlueCurveClient::contextHelp() QObject::connect: (sender name: 'help') QObject::connect: (receiver name: 'unnamed') X Error: BadMatch (invalid parameter attributes) 8 Major opcode: 158 Minor opcode: 6 Resource id: 0x4d g', 'Bayer Leverkusen (14)', '-', 'Karlsruhe (7)'], ['15h30', 'Coming', 'VfB Stuttgart (15)', '-', 'MSV Duisbourg (9)'], ['15h30', 'Coming', 'FC Nuremberg (12)', '-', 'Werder Br\xeame (16)'], ['15h30' [[], [], [], [], [], [], [], [], [], [], [], [], [], [], [], [], [], [], [], [], [], [], [], [], [], [], []] [[], [], [], [], [], [], [], [], [], [], [], [], [], [], [], [], [], [], [], [], [], [], [], [], [], [], []] [['17h10', 'Coming', 'Caen (14)', '-', 'Marseille (13)'], ['20h00', 'Coming', 'Bordeaux (6)', '-', 'Lorient (1)'], ['20h00', 'Coming', 'Monaco (4)', '-', 'Le Mans (1)'], ['20h00', 'Coming', 'Nancy (1) [[], [], [], [], [], [], [], [], [], [], [], [], [], [], [], [], [], [], [], [], [], [], [], [], [], [], []] [[], [], [], [], [], [], [], [], [], [], [], [], [], [], [], [], [], [], [], [], [], [], [], [], [], [], []] [['17h10', 'Coming', 'Caen (14)', '-', 'Marseille (13)'], ['20h00', 'Coming', 'Bordeaux (6)', '-', 'Lorient (1)'], ['20h00', 'Coming', 'Monaco (4)', '-', 'Le Mans (1)'], ['20h00', 'Coming', 'Nancy (1) ...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 the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers? *** This bug has been marked as a duplicate of 467846 ***