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 551516 - crash in Evolution Mail and Calendar: Opening Evolution. The ...
crash in Evolution Mail and Calendar: Opening Evolution. The ...
Status: RESOLVED DUPLICATE of bug 527335
Product: evolution
Classification: Applications
Component: BugBuddyBugs
2.22.x (obsolete)
Other All
: High critical
: ---
Assigned To: Evolution Triage Team
Evolution QA team
: 551519 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2008-09-09 14:22 UTC by mattmcadoo
Modified: 2008-09-10 05:35 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description mattmcadoo 2008-09-09 14:22:21 UTC 
What were you doing when the application crashed?
Opening Evolution.  The mail accounts (2 IMAP, 1 Exchange) had been "Offlined" before closing Evolution the night before.  Today, opening, noticed that the message "Resynchronizing with server" stayed at 100%.  Switching between accounts left Evolution in an unresponsive state.  Tried to kill the "Resyning with Server" message via the Red X.  Crash message.


Distribution: Gentoo Base System release 2.0.0
Gnome Release: 2.22.3 2008-07-01 (Gentoo)
BugBuddy Version: 2.22.0

System: Linux 2.6.26-hardened-r1 #2 SMP PREEMPT Thu Sep 4 11:18:04 CDT 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10500000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Unity
Icon Theme: gnome-alternative

Memory status: size: 101261312 vsize: 101261312 resident: 40824832 share: 10768384 rss: 40824832 rss_rlim: 4294967295
CPU usage: start_time: 1220967581 rtime: 182 utime: 169 stime: 13 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

[Thread debugging using libthread_db enabled]
[New Thread 0xb606ca50 (LWP 7609)]
[New Thread 0xb30feb90 (LWP 8104)]
[New Thread 0xb1effb90 (LWP 8100)]
[New Thread 0xb53f8b90 (LWP 8096)]
[New Thread 0xb5c3ab90 (LWP 7610)]
0xb7f9f422 in __kernel_vsyscall ()

+ Trace 206544

Thread 4 (Thread 0xb53f8b90 (LWP 8096))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 IA__g_spawn_sync
    at gspawn.c line 374
  • #3 IA__g_spawn_command_line_sync
    at gspawn.c line 682
  • #4 run_bug_buddy
    at gnome-breakpad.cc line 213
  • #5 check_if_gdb
    at gnome-breakpad.cc line 283
  • #6 google_breakpad::ExceptionHandler::InternalWriteMinidump
    at ../google-breakpad/src/client/linux/handler/exception_handler.cc line 226
  • #7 google_breakpad::ExceptionHandler::HandleException
    at ../google-breakpad/src/client/linux/handler/exception_handler.cc line 197
  • #8 <signal handler called>
  • #9 get_folder_contents_online
    at mail-stub-exchange.c line 698
  • #10 get_folder_contents_online_func
    at mail-stub-exchange.c line 832
  • #11 g_thread_create_proxy
    at gthread.c line 635
  • #12 start_thread
    at pthread_create.c line 297
  • #13 clone
    from /lib/libc.so.6 






Comment 1


Kandepu Prasad





          2008-09-10 05:30:34 UTC
        



*** Bug 551519 has been marked as a duplicate of this bug. ***






Comment 2


Kandepu Prasad





          2008-09-10 05:35:13 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 527335 ***