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 507264 - crash in Evolution: sending & receiving.
crash in Evolution: sending & receiving.
Status: RESOLVED DUPLICATE of bug 431459
Product: evolution
Classification: Applications
Component: general
2.10.x (obsolete)
Other All
: High critical
: ---
Assigned To: Evolution Shell Maintainers Team
Evolution QA team
: 507286 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2008-01-04 13:52 UTC by Jack Schneider
Modified: 2008-02-06 09:59 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20



Description Jack Schneider 2008-01-04 13:52:45 UTC
What were you doing when the application crashed?
sending & receiving.


Distribution: Debian lenny/sid
Gnome Release: 2.20.2 2007-11-29 (Debian)
BugBuddy Version: 2.20.1

System: Linux 2.6.22-3-amd64 #1 SMP Sun Nov 4 18:18:09 UTC 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 505266176 vsize: 505266176 resident: 33677312 share: 19632128 rss: 33677312 rss_rlim: 18446744073709551615
CPU usage: start_time: 1199454663 rtime: 1016 utime: 866 stime: 150 cutime:18 cstime: 62 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0x2b10c563a6d0 (LWP 7057)]
[New Thread 0x42804950 (LWP 7117)]
[New Thread 0x42003950 (LWP 7116)]
[New Thread 0x41802950 (LWP 7112)]
[New Thread 0x41001950 (LWP 7084)]
[New Thread 0x40800950 (LWP 7083)]
(no debugging symbols found)
0x00002b10bcf7234f in waitpid () from /lib/libpthread.so.0

Thread 1 (Thread 0x2b10c563a6d0 (LWP 7057))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 g_spawn_sync
    from /usr/lib/libglib-2.0.so.0
  • #2 g_spawn_command_line_sync
    from /usr/lib/libglib-2.0.so.0
  • #3 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #4 <signal handler called>
  • #5 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #6 ??
    from /usr/lib/libglib-2.0.so.0
  • #7 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #8 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #9 main
  • #0 waitpid
    from /lib/libpthread.so.0


----------- .xsession-errors (24 sec old) ---------------------
(evolution-2.10:5392): Gtk-CRITICAL **: gtk_label_set_text: assertion `GTK_IS_LABEL (label)' failed
(evolution-2.10:5392): Gtk-CRITICAL **: gtk_widget_show: assertion `GTK_IS_WIDGET (widget)' failed
/usr/lib/iceweasel/firefox-bin: Symbol `SSL_ImplementedCiphers' has different size in shared object, consider re-linking
evolution-shell-Message: Killing old version of evolution-data-server...
/usr/lib/python2.4/site-packages/apt/__init__.py:18: FutureWarning: apt API not stable yet
  warnings.warn("apt API not stable yet", FutureWarning)
Window manager warning: last_user_time (2224751264) is greater than comparison timestamp (1158449785).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _NE
Window manager warning: 0x3000003 (Software U) appears to be one of the offending windows with a timestamp of 2224751264.  Working around...
current dist not found in meta-release file
evolution-shell-Message: Killing old version of evolution-data-server...
get puck pop://puck@mail.volunteerwireless.net/
Find Items 0
get puck@dp-indexing.com pop://puck%40dp-indexing.com@mail.dp-indexing.com/
Find Items 0
--------------------------------------------------
Comment 1 Akhil Laddha 2008-02-06 09:53:11 UTC
*** Bug 507286 has been marked as a duplicate of this bug. ***
Comment 2 Akhil Laddha 2008-02-06 09:59:51 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 431459 ***