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 528564 - crash in Evolution Mail and Calendar: reading an e-mail I thou...
crash in Evolution Mail and Calendar: reading an e-mail I thou...
Status: RESOLVED DUPLICATE of bug 532844
Product: Evolution Exchange
Classification: Deprecated
Component: Connector
2.22.x
Other All
: High critical
: ---
Assigned To: Connector Maintainer
Ximian Connector QA
: 473870 528577 528583 528623 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2008-04-17 13:12 UTC by dan.mcdonald
Modified: 2008-07-10 03:31 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description dan.mcdonald 2008-04-17 13:12:09 UTC 
What were you doing when the application crashed?
reading an e-mail I thought I had already deleted.


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: 80375808 vsize: 80375808 resident: 19116032 share: 9580544 rss: 19116032 rss_rlim: 4294967295
CPU usage: start_time: 1208437422 rtime: 186 utime: 166 stime: 20 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 -1242265312 (LWP 9365)]
[New Thread -1245377648 (LWP 9366)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 195456

Thread 1 (Thread -1242265312 (LWP 9365))

  • #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 (597 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 
*** Bug 528577 has been marked as a duplicate of this bug. ***
Comment 2 Pedro Villavicencio 2008-04-18 00:20:22 UTC 
*** Bug 528583 has been marked as a duplicate of this bug. ***
Comment 3 Pedro Villavicencio 2008-04-18 00:21:03 UTC 
*** Bug 528623 has been marked as a duplicate of this bug. ***
Comment 4 Akhil Laddha 2008-04-24 12:19:20 UTC 
*** Bug 473870 has been marked as a duplicate of this bug. ***
Comment 5 Paul Smith 2008-07-09 19:45:21 UTC 
This bug is a duplicate of bug #532844
Comment 6 Akhil Laddha 2008-07-10 03:31:07 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 532844 ***