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 528577 - crash in Evolution Mail and Calendar: starting evolution with ...
crash in Evolution Mail and Calendar: starting evolution with ...
Status: RESOLVED DUPLICATE of bug 528564
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-04-17 13:55 UTC by dan.mcdonald
Modified: 2008-04-18 00:19 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description dan.mcdonald 2008-04-17 13:55:04 UTC
What were you doing when the application crashed?
starting evolution with the active message viewed being one that was deleted already.


Distribution: Unknown
Gnome Release: 2.22.0 2008-03-26 (Mandriva)
BugBuddy Version: 2.22.0

System: Linux 2.6.24.4-desktop-1mnb #1 SMP Thu Mar 27 14:34:39 CET 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Ia Ora Blue
Icon Theme: gnome

Memory status: size: 86147072 vsize: 86147072 resident: 17784832 share: 9535488 rss: 17784832 rss_rlim: 4294967295
CPU usage: start_time: 1208440427 rtime: 62 utime: 52 stime: 10 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/lib/evolution-exchange-storage'

Using host libthread_db library "/lib/i686/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1241573088 (LWP 10336)]
[New Thread -1255150704 (LWP 10371)]
[New Thread -1244685424 (LWP 10337)]
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1241573088 (LWP 10336))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/i686/libpthread.so.0
  • #2 g_spawn_sync
    from /usr/lib/libglib-2.0.so.0
  • #3 g_spawn_command_line_sync
    from /usr/lib/libglib-2.0.so.0
  • #4 POA_GNOME_Evolution_Component__fini
    at Evolution-skels.c line 506
  • #5 POA_GNOME_Evolution_Component__fini
    at Evolution-skels.c line 506
  • #6 google_breakpad::ExceptionHandler::InternalWriteMinidump
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #7 google_breakpad::ExceptionHandler::HandleException
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #8 <signal handler called>
  • #9 get_message
    at mail-stub-exchange.c line 2447
  • #10 connection_handler
    at mail-stub.c line 271
  • #11 POA_GNOME_Evolution_Component__fini
    at Evolution-skels.c line 506
  • #12 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #13 POA_GNOME_Evolution_Component__fini
    at Evolution-skels.c line 506
  • #14 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #15 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #16 main
    at main.c line 238
  • #17 __libc_start_main
    from /lib/i686/libc.so.6
  • #18 _start
  • #0 __kernel_vsyscall


----------- .xsession-errors (3130 sec old) ---------------------
(evolution:8613): libecal-WARNING **: e-cal.c:318: Unexpected response
(evolution:8613): libecal-WARNING **: e-cal.c:318: Unexpected response
(evolution:8613): libecal-WARNING **: e-cal.c:318: Unexpected response
(evolution:8613): libecal-WARNING **: e-cal.c:318: Unexpected response
(evolution:8613): libecal-WARNING **: e-cal.c:318: Unexpected response
(evolution:8613): libecal-WARNING **: e-cal.c:318: Unexpected response
(evolution:8613): libecal-WARNING **: e-cal.c:318: Unexpected response
(evolution:8613): libecal-WARNING **: e-cal.c:318: Unexpected response
--------------------------------------------------
Comment 1 Pedro Villavicencio 2008-04-18 00:19:44 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


*** This bug has been marked as a duplicate of 528564 ***