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 543141 - crash in Evolution Mail and Calendar: going offline
crash in Evolution Mail and Calendar: going offline
Status: RESOLVED DUPLICATE of bug 543185
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-07-15 17:50 UTC by michael
Modified: 2008-07-15 21:52 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description michael 2008-07-15 17:50:27 UTC 
What were you doing when the application crashed?
going offline


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

System: Linux 2.6.24-1-686 #1 SMP Thu May 8 02:16:39 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 82612224 vsize: 82612224 resident: 26812416 share: 9936896 rss: 26812416 rss_rlim: 4294967295
CPU usage: start_time: 1215780680 rtime: 5559 utime: 5335 stime: 224 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

(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 0xb66359a0 (LWP 5745)]
[New Thread 0xb6399b90 (LWP 5746)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 202914

Thread 1 (Thread 0xb66359a0 (LWP 5745))

  • #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 <signal handler called>
  • #6 ??
  • #7 ??
  • #8 ??
  • #0 __kernel_vsyscall 


----------- .xsession-errors (660 sec old) ---------------------
 *** Gnome Registry Session: yes.
 *** Gnome Registry Session: yes.
 *** Gnome Registry Session: yes.
 *** Gnome Registry Session: yes.
 *** Gnome Registry Session: yes.
 *** Gnome Registry Session: yes.
 *** Gnome Registry Session: yes.
 *** Gnome Registry Session: yes.
 *** Gnome Registry Session: yes.
 *** Gnome Registry Session: yes.
 *** Gnome Registry Session: yes.
 *** Gnome Registry Session: yes.
 *** Gnome Registry Session: yes.
Keymap changed! Regrabbing keys...Keymap changed! Regrabbing keys...Keymap changed! Regrabbing keys...Keymap changed! Regrabbing keys...Keymap changed! Regrabbing keys...Keymap changed! Regrabbing key
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Keymap changed! Regrabbing keys...Keymap changed! Regrabbing keys...Keymap changed! Regrabbing keys...Keymap changed! Regrabbing keys...Keymap changed! Regrabbing keys...Keymap changed! Regrabbing key
--------------------------------------------------
Comment 1 Baptiste Mille-Mathias 2008-07-15 17:55:28 UTC 
Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks in advance!
Comment 2 michael 2008-07-15 21:52:41 UTC 

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