GNOME Bugzilla – Bug 460030
crash in Evolution: First openning after boo...
Last modified: 2007-10-14 15:30:45 UTC
What were you doing when the application crashed? First openning after boot Distribution: Mandriva Linux release 2007.1 (Official) for i586 Gnome Release: 2.18.0 2007-03-15 (Mandriva) BugBuddy Version: 2.18.0 System: Linux 2.6.17-11mdv #1 SMP Tue Feb 13 11:59:10 MST 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks-Olive Icon Theme: Amaranth Memory status: size: 191938560 vsize: 191938560 resident: 24883200 share: 16842752 rss: 24883200 rss_rlim: 4294967295 CPU usage: start_time: 1185310839 rtime: 120 utime: 100 stime: 20 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/i686/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1236941088 (LWP 4535)] [New Thread -1340105824 (LWP 4555)] [New Thread -1348498528 (LWP 4552)] [New Thread -1331713120 (LWP 4550)] [New Thread -1314927712 (LWP 4548)] [New Thread -1289749600 (LWP 4545)] [New Thread -1279755360 (LWP 4544)] (no debugging symbols found) 0xbfffe410 in __kernel_vsyscall ()
+ Trace 150310
Thread 1 (Thread -1236941088 (LWP 4535))
----------- .xsession-errors (14 sec old) --------------------- (gnome-panel:4467): GConf-WARNING **: Directory `/apps/panel/toplevels/top_panel_screen1/screen' was not being monitored by GConfClient 0x80f4958 /usr/share/themes/Clearlooks-Olive/gtk-2.0/gtkrc:44: Clearlooks configuration option "menuitemstyle" is not supported and will be ignored. /usr/share/themes/Clearlooks-Olive/gtk-2.0/gtkrc:45: Clearlooks configuration option "listviewitemstyle" is not supported and will be ignored. /usr/share/themes/Clearlooks-Olive/gtk-2.0/gtkrc:46: Clearlooks configuration option "progressbarstyle" is not supported and will be ignored. (gnome-panel:4467): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -21 and height 24 CalDAV Eplugin starting up ... /usr/share/themes/Clearlooks-Olive/gtk-2.0/gtkrc:44: Clearlooks configuration option "menuitemstyle" is not supported and will be ignored. /usr/share/themes/Clearlooks-Olive/gtk-2.0/gtkrc:45: Clearlooks configuration option "listviewitemstyle" is not supported and will be ignored. /usr/share/themes/Clearlooks-Olive/gtk-2.0/gtkrc:46: Clearlooks configuration option "progressbarstyle" is not supported and will be ignored. ** (evolution:4535): DEBUG: mailto URL command: evolution %s ** (evolution:4535): DEBUG: mailto URL program: evolution /usr/share/themes/Clearlooks-Olive/gtk-2.0/gtkrc:44: Clearlooks configuration option "menuitemstyle" is not supported and will be ignored. /usr/share/themes/Clearlooks-Olive/gtk-2.0/gtkrc:45: Clearlooks configuration option "listviewitemstyle" is not supported and will be ignored. /usr/share/themes/Clearlooks-Olive/gtk-2.0/gtkrc:46: Clearlooks configuration option "progressbarstyle" is not supported and will be ignored. --------------------------------------------------
Thanks for taking the time to report this bug. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Could you please install some debugging packages [1], start the application as normal, and reproduce the crash, if possible? Once bug-buddy pops up, you can find the stacktrace in the Details, now containing way more information. Please copy that stacktrace and paste it as a comment here. Thanks in advance! [1] debugging packages for evolution, evolution-data-server, gtkhtml, gtk, glib, gnome-vfs, pango, libgnome and libgnomeui (as far as those packages are provided by your distribution). More details can be found here: http://live.gnome.org/GettingTraces
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 ***