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 531072 - crash in Evolution Mail and Calendar: Trying to connect to exc...
crash in Evolution Mail and Calendar: Trying to connect to exc...
Status: RESOLVED DUPLICATE of bug 451816
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-05-02 14:40 UTC by andrew.phillips
Modified: 2008-05-03 12:35 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description andrew.phillips 2008-05-02 14:40:53 UTC 
What were you doing when the application crashed?
Trying to connect to exchange.


Distribution: Debian lenny/sid
Gnome Release: 2.22.1 2008-04-08 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.22-3-686 #1 SMP Mon Nov 12 08:32:57 UTC 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Smokey-Blue-Dark
Icon Theme: Tango

Memory status: size: 130064384 vsize: 130064384 resident: 53981184 share: 22466560 rss: 53981184 rss_rlim: 4294967295
CPU usage: start_time: 1209739183 rtime: 3443 utime: 3410 stime: 33 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb676e740 (LWP 7154)]
[New Thread 0xb3bffb90 (LWP 7167)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 196684

Thread 1 (Thread 0xb676e740 (LWP 7154))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/i686/cmov/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 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 ??
  • #6 ??
  • #7 ??
  • #8 ??
  • #9 ??
  • #10 ??
    from /usr/lib/libedataserver-1.2.so.9
  • #11 ??
  • #12 ??
  • #13 <signal handler called>
  • #14 e_account_set_string
    from /usr/lib/libedataserver-1.2.so.9
  • #15 exchange_config_listener_authenticate
    from /usr/lib/evolution/2.22/plugins/liborg-gnome-exchange-operations.so
  • #16 exchange_operations_get_exchange_account
    from /usr/lib/evolution/2.22/plugins/liborg-gnome-exchange-operations.so
  • #17 org_gnome_exchange_commit
    from /usr/lib/evolution/2.22/plugins/liborg-gnome-exchange-operations.so
  • #18 ??
    from /usr/lib/evolution/2.22/libeutil.so.0
  • #19 ??
  • #20 ??
  • #21 ??
  • #22 ??
  • #0 __kernel_vsyscall 


----------- .xsession-errors (380 sec old) ---------------------
  (org.freedesktop.DBus.Error.ServiceUnknown) The name org.freedesktop.NetworkManager was not provided by any .service files
(evolution:6625): evolution-mail-WARNING **: Error occurred while existing dialogue active:
Could not connect to Evolution Exchange backend process: Please restart Evolution
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3a00003 (Evince Doc)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
(evolution:6625): evolution-mail-WARNING **: Error occurred while existing dialogue active:
Could not connect to Evolution Exchange backend process: Please restart Evolution
BBDB spinning up...
(evolution:6625): Gdk-WARNING **: GdkWindow is too large to allow the use of shape masks or shape regions.
(evolution:6625): Gdk-WARNING **: GdkWindow is too large to allow the use of shape masks or shape regions.
Making error
--------------------------------------------------
Comment 1 Susana 2008-05-03 12:35:03 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


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