GNOME Bugzilla – Bug 486498
crash in Evolution: aprire una e-mail già le...
Last modified: 2007-10-14 13:22:27 UTC
What were you doing when the application crashed? aprire una e-mail già letta Distribution: Debian lenny/sid Gnome Release: 2.18.3 2007-07-03 (Debian) BugBuddy Version: 2.18.1 System: Linux 2.6.22-2-amd64 #1 SMP Thu Aug 30 23:43:59 UTC 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 453066752 vsize: 453066752 resident: 32026624 share: 19136512 rss: 32026624 rss_rlim: 18446744073709551615 CPU usage: start_time: 1192343946 rtime: 85 utime: 69 stime: 16 cutime:0 cstime: 3 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution-2.10' (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 0x2af19fe7e860 (LWP 4792)] [New Thread 0x42003950 (LWP 4848)] [New Thread 0x41802950 (LWP 4847)] [New Thread 0x41001950 (LWP 4823)] [New Thread 0x40800950 (LWP 4822)] (no debugging symbols found) 0x00002af197e6fc7f in waitpid () from /lib/libpthread.so.0
+ Trace 170090
Thread 1 (Thread 0x2af19fe7e860 (LWP 4792))
----------- .xsession-errors (13 sec old) --------------------- (gnome-panel:4726): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -9 and height 24 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 evolution-shell-Message: Killing old version of evolution-data-server... --------------------------------------------------
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 ***