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 554231 - crash in Evolution Mail and Calendar:
crash in Evolution Mail and Calendar:
Status: RESOLVED DUPLICATE of bug 523463
Product: evolution
Classification: Applications
Component: BugBuddyBugs
2.22.x (obsolete)
Other All
: High critical
: ---
Assigned To: Evolution Triage Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2008-09-28 22:10 UTC by g.jackways
Modified: 2009-01-20 04:00 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description g.jackways 2008-09-28 22:10:21 UTC
What were you doing when the application crashed?



Distribution: Debian lenny/sid
Gnome Release: 2.22.3 2008-06-30 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.26-1-amd64 #1 SMP Wed Sep 10 15:31:12 UTC 2008 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10402000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 580788224 vsize: 580788224 resident: 29323264 share: 19726336 rss: 29323264 rss_rlim: 18446744073709551615
CPU usage: start_time: 1222639792 rtime: 109 utime: 99 stime: 10 cutime:0 cstime: 5 timeout: 0 it_real_value: 0 frequency: 100

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

[Thread debugging using libthread_db enabled]
[New Thread 0x7fe12ffe5790 (LWP 4703)]
[New Thread 0x41569950 (LWP 4757)]
[New Thread 0x41d6a950 (LWP 4756)]
[New Thread 0x426bc950 (LWP 4744)]
0x00007fe12b8c25ff in waitpid () from /lib/libpthread.so.0

Thread 1 (Thread 0x7fe12ffe5790 (LWP 4703))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 IA__g_spawn_sync
    at /build/buildd/glib2.0-2.16.5/glib/gspawn.c line 374
  • #2 IA__g_spawn_command_line_sync
    at /build/buildd/glib2.0-2.16.5/glib/gspawn.c line 682
  • #3 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #4 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 <signal handler called>
  • #6 IA__g_main_context_check
    at /build/buildd/glib2.0-2.16.5/glib/gmain.c line 2491
  • #7 g_main_context_iterate
    at /build/buildd/glib2.0-2.16.5/glib/gmain.c line 2642
  • #8 IA__g_main_loop_run
    at /build/buildd/glib2.0-2.16.5/glib/gmain.c line 2853
  • #9 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #10 main
    at main.c line 793
  • #0 waitpid
    from /lib/libpthread.so.0


----------- .xsession-errors (24 sec old) ---------------------
(firefox-bin:4540): Pango-WARNING **: Error loading GPOS table 5503
gtk-gnash: /usr/include/boost/variant/detail/visitation_impl.hpp:203: typename Visitor::result_type boost::detail::variant::visitation_impl(int, int, Visitor&, VPCV, mpl_::true_, NBF, W*, S*) [with W 
Player request channel hang up
Shutting down
Child process exited with status 256
plugin instance destruction
shutting down input chan 0x7f0045cfc700
CalDAV Eplugin starting up ...
evolution-shell-Message: Killing old version of evolution-data-server...
** (evolution:4570): DEBUG: mailto URL command: evolution %s
** (evolution:4570): DEBUG: mailto URL program: evolution
CalDAV Eplugin starting up ...
evolution-shell-Message: Killing old version of evolution-data-server...
** (evolution:4703): DEBUG: mailto URL command: evolution %s
** (evolution:4703): DEBUG: mailto URL program: evolution
--------------------------------------------------
Comment 1 André Klapper 2008-09-28 22:46:19 UTC
What were you doing when the application crashed?

Comment 2 g.jackways 2008-09-28 23:05:04 UTC
Had changed from mail view to contacts view (which took some time). Then tried to change back to mail view. Evolution hung, then crashed.
Comment 3 Akhil Laddha 2009-01-20 04:00:59 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 523463 ***