GNOME Bugzilla – Bug 443948
crash in Tasks: browsing internet, just ...
Last modified: 2007-09-26 23:13:24 UTC
What were you doing when the application crashed? browsing internet, just running Evolution in the background Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: AquaX Icon Theme: Fedora Memory status: size: 126484480 vsize: 126484480 resident: 31105024 share: 19038208 rss: 31105024 rss_rlim: 4294967295 CPU usage: start_time: 1180965271 rtime: 667 utime: 640 stime: 27 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 -1208330528 (LWP 10822)] [New Thread -1261438064 (LWP 10938)] [New Thread -1259857008 (LWP 10844)] [New Thread -1238865008 (LWP 10841)] [New Thread -1227981936 (LWP 10840)] (no debugging symbols found) 0x00927402 in __kernel_vsyscall ()
+ Trace 138125
Thread 2 (Thread -1261438064 (LWP 10938))
----------- .xsession-errors (148 sec old) --------------------- (evolution:10822): e-data-server-ui-WARNING **: Key file does not have key 'exchange:__wur%5cbohme001;auth_Basic@webmail.wur.nl_' ** (evolution:10822): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:10822): DEBUG: mailto URL program: evolution libnm_glib_nm_state_cb: dbus returned an error. (org.freedesktop.DBus.Error.ServiceUnknown) The name org.freedesktop.NetworkManager was not provided by any .service files (evolution:10822): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0 (evolution:10822): e-data-server-ui-WARNING **: Key file does not have key 'exchange:__wur%5cbohme001;auth_Basic@webmail.wur.nl_' (evolution:10822): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0 (evolution:10822): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 1 ** (evolution:10822): WARNING **: Invalid borders specified for theme pixmap: /home/bohme001/.themes/AquaX/gtk-2.0/entry1.png, borders don't fit within the image --------------------------------------------------
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, libgnome and libgnomeui (as far as those packages are provided by your distribution). More details can be found here: http://live.gnome.org/GettingTraces
(In reply to comment #1) > 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, libgnome and libgnomeui (as far as those packages are provided > by your distribution). More details can be found here: > http://live.gnome.org/GettingTraces > After disabling Mail Nofification (mail-notification-4.0-2.fc7), I've not have a crash anymore. Thanks for you time, maybe betetr to close this Bug.
Unfortunately the stacktrace does not have any hints about the real cause of the crash and does not help in debugging this issue. For some yet unknown reason, such stacktraces are pretty common currently on certain distributions. However, almost all of them do turn out to be filed already, once we managed to gather a useful stacktrace. To do so, simply install the corresponding debugging packages and reproduce the issue, if possible. The resulting stacktrace (see bug-buddy details) will help us to identify and fix the issue. Just in case you ever can reproduce this crash later, please consider installing debugging packages [1] and either reopen this bug report or simply file a new one with the resulting stacktrace. Thanks! Closing this bug report as no further information has been provided.
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 455329 ***