After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 464724 - crash in Evolution: Exiting Evolution (via E...
crash in Evolution: Exiting Evolution (via E...
Status: RESOLVED DUPLICATE of bug 334966
Product: evolution
Classification: Applications
Component: general
2.8.x (obsolete)
Other All
: High critical
: ---
Assigned To: Evolution Shell Maintainers Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-08-08 14:56 UTC by sternn
Modified: 2007-08-19 16:26 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description sternn 2007-08-08 14:56:50 UTC 
What were you doing when the application crashed?
Exiting Evolution (via Exit menu option).  No recent sending or receiving of mail.  No unusual behavior observed prior.


Distribution: Gentoo Base System release 1.12.9
Gnome Release: 2.16.3 2007-06-07 (Gentoo)
BugBuddy Version: 2.16.1

System: Linux 2.6.22-gentoo-r1 #10 SMP PREEMPT Fri Jul 27 11:03:40 CDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 70200000
Selinux: No
Accessibility: Disabled

Memory status: size: 334614528 vsize: 334614528 resident: 54079488 share: 39145472 rss: 54079488 rss_rlim: -1
CPU usage: start_time: 1186544746 rtime: 870 utime: 819 stime: 51 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/evolution-2.8'

(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 47036490136704 (LWP 12166)]
[New Thread 1115969856 (LWP 13485)]
[New Thread 1115703616 (LWP 12177)]
[New Thread 1107310912 (LWP 12175)]
[New Thread 1098918208 (LWP 12174)]
[New Thread 1090525504 (LWP 12172)]
[New Thread 1082132800 (LWP 12170)]
0x00002ac7863cf53e in waitpid () from /lib/libpthread.so.0

+ Trace 153734

Thread 1 (Thread 47036490136704 (LWP 12166))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 ??
    from /usr/lib/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 strcmp
    from /lib/libc.so.6
  • #4 e_shell_window_set_title
  • #5 ??
  • #6 GNOME_Evolution_ShellView_setTitle
    from /usr/lib64/evolution/2.8/libeshell.so.0
  • #7 e_component_view_set_title
    from /usr/lib64/evolution/2.8/libeshell.so.0
  • #8 ??
    from /usr/lib64/evolution/2.8/components/libevolution-mail.so
  • #9 ??
    from /usr/lib/libglib-2.0.so.0
  • #10 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #11 ??
    from /usr/lib/libglib-2.0.so.0
  • #12 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #13 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #14 main
  • #0 waitpid
    from /lib/libpthread.so.0 


----------- .xsession-errors ---------------------
(evolution-2.8:12166): camel-WARNING **: camel_exception_get_id called with NULL parameter.
(evolution-2.8:12166): camel-WARNING **: camel_exception_get_id called with NULL parameter.
(evolution-2.8:12166): camel-WARNING **: camel_exception_get_id called with NULL parameter.
(evolution-2.8:12166): camel-WARNING **: camel_exception_get_id called with NULL parameter.
(evolution-2.8:12166): camel-WARNING **: camel_exception_get_id called with NULL parameter.
ICE default IO error handler doing an exit(), pid = 14121, errno = 0
ICE default IO error handler doing an exit(), pid = 14141, errno = 0
** (bug-buddy:14584): WARNING **: Couldn't load icon for Bonobo Component Browser
** (bug-buddy:14584): WARNING **: Couldn't load icon for Open Folder
--------------------------------------------------
Comment 1 André Klapper 2007-08-19 16:26:21 UTC 
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 334966 ***