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 573397 - crash in Evolution Mail and Calendar: I have one exchange acco...
crash in Evolution Mail and Calendar: I have one exchange acco...
Status: RESOLVED DUPLICATE of bug 573124
Product: evolution
Classification: Applications
Component: BugBuddyBugs
2.24.x (obsolete)
Other All
: High critical
: ---
Assigned To: Evolution Triage Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2009-02-27 13:55 UTC by Nik Lam
Modified: 2009-02-27 14:49 UTC
See Also:
GNOME target: ---
GNOME version: 2.23/2.24


Description Nik Lam 2009-02-27 13:55:43 UTC 
What were you doing when the application crashed?
I have one exchange account and two IMAP accounts configured. I had just contracted the directory tree on my exchange account and expanded the directory tree on one of my IMAP accounts and clicked on the Inbox of that account. I then went to quit evolution and it appeared to hang.


Distribution: Fedora release 10 (Cambridge)
Gnome Release: 2.24.3 2009-01-16 (Red Hat, Inc)
BugBuddy Version: 2.24.2

System: Linux 2.6.27.15-170.2.24.fc10.x86_64 #1 SMP Wed Feb 11 23:14:31 EST 2009 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10503000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 515506176 vsize: 515506176 resident: 28602368 share: 12185600 rss: 28602368 rss_rlim: 18446744073709551615
CPU usage: start_time: 1235735070 rtime: 203 utime: 164 stime: 39 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 0x7f49367397e0 (LWP 13439)]
[New Thread 0x7f4931a53950 (LWP 13440)]
0x00000033bfc0ec2f in waitpid () from /lib64/libpthread.so.0

+ Trace 212960

Thread 1 (Thread 0x7f49367397e0 (LWP 13439))

  • #0 waitpid
    from /lib64/libpthread.so.0
  • #1 g_spawn_sync
    from /lib64/libglib-2.0.so.0
  • #2 g_spawn_command_line_sync
    from /lib64/libglib-2.0.so.0
  • #3 ??
    from /usr/lib64/gtk-2.0/modules/libgnomebreakpad.so
  • #4 ??
    from /usr/lib64/gtk-2.0/modules/libgnomebreakpad.so
  • #5 <signal handler called>
  • #6 g_str_hash
    from /lib64/libglib-2.0.so.0
  • #7 g_hash_table_lookup
    from /lib64/libglib-2.0.so.0
  • #8 message_removed
    at mail-stub-exchange.c line 405
  • #9 sync_deletions
    at mail-stub-exchange.c line 1193
  • #10 connection_handler
    at mail-stub.c line 168
  • #11 g_main_context_dispatch
    from /lib64/libglib-2.0.so.0
  • #12 ??
    from /lib64/libglib-2.0.so.0
  • #13 g_main_loop_run
    from /lib64/libglib-2.0.so.0
  • #14 bonobo_main
    from /usr/lib64/libbonobo-2.so.0
  • #15 main
    at main.c line 278 


----------- .xsession-errors (1129173 sec old) ---------------------
 :: file th-title-selector.c: line 965 (ts_title_cell_data_func): should not be reached
 :: ThJobProgressDialog: finalize
 :: ThJobConfigDialog: finalize
 :: ThTitleSelector: finalize
 :: ThDevicePool: finalize
 :: ThDiscDrivePool: finalize
 :: ThDiscDrive: finalize
 :: ThDiscDrive: finalize
 :: ThJob: finalize (0xa04c4c8)
 :: ThAppWindow: finalize
(gnome-keyring-daemon-wrapper:5865): EggSMClient-WARNING **: Received XSMP SaveYourself message in state save-yourself-done: client or server error
gnome-screensaver: Fatal IO error 104 (Connection reset by peer) on X server :0.0.
gnome-settings-daemon: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
Window manager warning: Fatal IO error 11 (Resource temporarily unavailable) on display ':0.0'.
--------------------------------------------------
Comment 1 palfrey 2009-02-27 14:49:20 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 573124 ***