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 512039 - crash in Evolution:
crash in Evolution:
Status: RESOLVED DUPLICATE of bug 431459
Product: evolution
Classification: Applications
Component: BugBuddyBugs
2.10.x (obsolete)
Other All
: High critical
: ---
Assigned To: Evolution Shell Maintainers Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2008-01-25 13:27 UTC by Jack Schneider
Modified: 2008-03-20 15:19 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20



Description Jack Schneider 2008-01-25 13:27:46 UTC
What were you doing when the application crashed?



Distribution: Debian lenny/sid
Gnome Release: 2.20.3 2008-01-12 (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: 512507904 vsize: 512507904 resident: 31944704 share: 19234816 rss: 31944704 rss_rlim: 18446744073709551615
CPU usage: start_time: 1201267612 rtime: 94 utime: 80 stime: 14 cutime:1 cstime: 5 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 0x2b101558b6d0 (LWP 7620)]
[New Thread 0x43005950 (LWP 7666)]
[New Thread 0x42804950 (LWP 7662)]
[New Thread 0x42003950 (LWP 7661)]
[New Thread 0x41802950 (LWP 7660)]
[New Thread 0x41001950 (LWP 7639)]
[New Thread 0x40800950 (LWP 7638)]
(no debugging symbols found)
0x00002b100ccc834f in waitpid () from /lib/libpthread.so.0

Thread 1 (Thread 0x2b101558b6d0 (LWP 7620))

  • #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 (11 sec old) ---------------------
** Message: volume = 0
/usr/lib/iceweasel/firefox-bin: Symbol `SSL_ImplementedCiphers' has different size in shared object, consider re-linking
[NoScript] [NoScript] browserDOMWindow wrapped for external load interception
/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 (271143584) is greater than comparison timestamp (2971405554).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET
Window manager warning: 0x3200003 (Software U) appears to be one of the offending windows with a timestamp of 271143584.  Working around...
current dist not found in meta-release file
/usr/lib/iceweasel/firefox-bin: Symbol `SSL_ImplementedCiphers' has different size in shared object, consider re-linking
[NoScript] [NoScript] browserDOMWindow wrapped for external load interception
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-03-20 15:19:48 UTC
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but
we are happy to tell you that the problem has already been fixed. It should be
solved in the next software version. You may want to check for a software
upgrade.


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