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 331573 - EDS - Clicked into Calendar view and got crash
EDS - Clicked into Calendar view and got crash
Status: RESOLVED DUPLICATE of bug 334065
Product: evolution-data-server
Classification: Platform
Component: Calendar
1.6.x (obsolete)
Other All
: Normal major
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2006-02-17 17:29 UTC by David Richards
Modified: 2013-09-14 16:49 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description David Richards 2006-02-17 17:29:00 UTC
Please describe the problem:
This is with 2.5.91, clicked into Calendar view and it sat for a second and
appeared to be bringing down the information and then EDS crashed.  Close if
duplicate.  We need to get these EDS issues resolved...anything that physically
crashes Evo I will mark Major until release.

Backtrace was generated from '/opt/gnome/libexec/evolution-data-server-1.6'

Using host libthread_db library "/lib/tls/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1219766592 (LWP 769)]
[New Thread -1267024976 (LWP 858)]
[Thread debugging using libthread_db enabled]
[New Thread -1219766592 (LWP 769)]
[New Thread -1267024976 (LWP 858)]
[Thread debugging using libthread_db enabled]
[New Thread -1219766592 (LWP 769)]
[New Thread -1267024976 (LWP 858)]
[New Thread -1283810384 (LWP 856)]
[New Thread -1308988496 (LWP 808)]
[New Thread -1224066128 (LWP 771)]
0xffffe410 in ?? ()

Thread 2 (Thread -1267024976 (LWP 858))

  • #0 ??
  • #1 ??
  • #2 ??
  • #3 ??
  • #4 __lll_mutex_lock_wait
    from /lib/tls/libpthread.so.0
  • #5 _L_mutex_lock_33
    from /lib/tls/libpthread.so.0
  • #6 ??
  • #7 ??
  • #8 ??
    from /lib/tls/libc.so.6
  • #9 ??
  • #10 __libc_ptyname1
    from /lib/tls/libc.so.6
  • #11 ??
  • #12 gnome_segv_handler
    at server.c line 97
  • #13 gnome_segv_handler
    at server.c line 97
  • #14 <signal handler called>
  • #15 getenv
    from /lib/tls/libc.so.6
  • #16 tzset_internal
    from /lib/tls/libc.so.6
  • #17 __tz_convert
    from /lib/tls/libc.so.6
  • #18 gmtime
    from /lib/tls/libc.so.6
  • #19 isodate_from_time_t
    at e-cal-time-util.c line 575
  • #20 e_cal_component_gen_uid
    at e-cal-component.c line 432
  • #21 ensure_mandatory_properties
    at e-cal-component.c line 980
  • #22 e_cal_component_set_new_vtype
    at e-cal-component.c line 1064
  • #23 e_gw_item_to_cal_component
    at e-cal-backend-groupwise-utils.c line 838
  • #24 populate_cache
    at e-cal-backend-groupwise.c line 178
  • #25 cache_init
    at e-cal-backend-groupwise.c line 649
  • #26 g_thread_create_full
    from /opt/gnome/lib/libglib-2.0.so.0
  • #27 start_thread
    from /lib/tls/libpthread.so.0
  • #28 clone
    from /lib/tls/libc.so.6


Steps to reproduce:
1. 
2. 
3. 


Actual results:


Expected results:


Does this happen every time?


Other information:
Comment 1 Chenthill P 2006-03-14 04:31:40 UTC

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