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 485627 - crash in Evolution: syncrhonizing using sync...
crash in Evolution: syncrhonizing using sync...
Status: RESOLVED DUPLICATE of bug 488881
Product: evolution
Classification: Applications
Component: BugBuddyBugs
2.10.x (obsolete)
Other All
: High critical
: ---
Assigned To: Evolution Triage Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-10-11 07:00 UTC by Dries.Decock
Modified: 2008-07-03 16:55 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description Dries.Decock 2007-10-11 07:00:50 UTC 
What were you doing when the application crashed?
syncrhonizing using syncevolution


Distribution: Gentoo Base System release 1.12.9
Gnome Release: 2.18.3 2007-09-26 (Gentoo)
BugBuddy Version: 2.18.1

System: Linux 2.6.22-gentoo-r5-20070924 #4 SMP Wed Sep 26 14:53:34 CEST 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: 283357184 vsize: 283357184 resident: 11517952 share: 6569984 rss: 11517952 rss_rlim: 18446744073709551615
CPU usage: start_time: 1192085811 rtime: 14 utime: 14 stime: 0 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/libexec/evolution-data-server-1.10'

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 47708324509600 (LWP 28453)]
[New Thread 1115969856 (LWP 28551)]
[New Thread 1099184448 (LWP 28472)]
[New Thread 1074006336 (LWP 28454)]
0x00002b63f567711a in waitpid () from /lib/libc.so.6

+ Trace 169420

Thread 2 (Thread 1115969856 (LWP 28551))

  • #0 __lll_mutex_lock_wait
    from /lib/libpthread.so.0
  • #1 _L_mutex_lock_51
    from /lib/libpthread.so.0
  • #2 pthread_mutex_lock
    from /lib/libpthread.so.0
  • #3 ??
  • #4 <signal handler called>
  • #5 g_str_hash
    from /usr/lib/libglib-2.0.so.0
  • #6 g_hash_table_lookup
    from /usr/lib/libglib-2.0.so.0
  • #7 e_cal_backend_file_modify_object
    at e-cal-backend-file.c line 1934
  • #8 e_cal_backend_sync_modify_object
    at e-cal-backend-sync.c line 262
  • #9 _e_cal_backend_modify_object
    at e-cal-backend-sync.c line 746
  • #10 ORBit_small_invoke_adaptor
    from /usr/lib/libORBit-2.so.0
  • #11 ??
    from /usr/lib/libORBit-2.so.0
  • #12 ??
    from /usr/lib/libORBit-2.so.0
  • #13 giop_thread_queue_process
    from /usr/lib/libORBit-2.so.0
  • #14 ??
    from /usr/lib/libORBit-2.so.0
  • #15 ??
    from /usr/lib/libglib-2.0.so.0
  • #16 ??
    from /usr/lib/libglib-2.0.so.0
  • #17 start_thread
    from /lib/libpthread.so.0
  • #18 clone
    from /lib/libc.so.6
  • #19 ?? 


----------- .xsession-errors (82 sec old) ---------------------
** (tilda:7406): CRITICAL **: clearlooks_style_draw_box_gap: assertion `height >= -1' failed
** (tilda:7406): CRITICAL **: clearlooks_style_draw_box_gap: assertion `height >= -1' failed
** (tilda:7406): CRITICAL **: clearlooks_style_draw_box_gap: assertion `height >= -1' failed
** (tilda:7406): CRITICAL **: clearlooks_style_draw_box_gap: assertion `height >= -1' failed
** (tilda:7406): CRITICAL **: clearlooks_style_draw_box_gap: assertion `height >= -1' failed
** (tilda:7406): CRITICAL **: clearlooks_style_draw_box_gap: assertion `height >= -1' failed
** (tilda:7406): CRITICAL **: clearlooks_style_draw_box_gap: assertion `height >= -1' failed
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x220000b (tilda)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
--------------------------------------------------
Comment 1 Milan Crha 2008-07-03 16:55:58 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 488881 ***