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 300432 - Non func:Invitation tab is missing after sending 340 meetings
Non func:Invitation tab is missing after sending 340 meetings
Status: RESOLVED DUPLICATE of bug 305322
Product: evolution
Classification: Applications
Component: Calendar
2.2.x (obsolete)
Other All
: Normal normal
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2005-04-13 06:12 UTC by Poornima
Modified: 2013-09-10 14:02 UTC
See Also:
GNOME target: ---
GNOME version: 2.5/2.6



Description Poornima 2005-04-13 06:12:37 UTC
Steps to reproduce:
1. Sent meeting with delay of 2 minutes , after every 100 meetings delay was
increased by 1 minute
2. After sending 340 meetings, saw that 'Invitations' tab is missing, recurrence
& scheduling screens are not editable.
3. When this script was running, after 19 hours EDS has crashed.
Attached traces of currently running EDS.
Coredump of crashed eds
Attached gdb traces of evolution, traces at terminal


Stack trace:
EDS traces, which doesnt seem to be useful

Thread 1 (Thread 1095049728 (LWP 1752))

  • #0 pthread_mutex_lock
    from /lib/tls/libpthread.so.0
  • #1 process_callbacks_main_thread
    at e-meeting-store.c line 1000
  • #2 g_idle_dispatch
    from /opt/gnome/lib/libglib-2.0.so.0
  • #3 g_main_context_dispatch
    from /opt/gnome/lib/libglib-2.0.so.0
  • #4 g_main_context_iterate
    from /opt/gnome/lib/libglib-2.0.so.0
  • #5 g_main_loop_run
    from /opt/gnome/lib/libglib-2.0.so.0
  • #6 bonobo_main
    from /opt/gnome/lib/libbonobo-2.so.0
  • #7 main
    at main.c line 610
  • #0 pthread_mutex_lock
    from /lib/tls/libpthread.so.0
  • #0 ??
  • #1 ??
  • #2 ??
  • #3 ??
  • #4 raise
    from /lib/tls/libc.so.6
  • #5 abort
    from /lib/tls/libc.so.6
  • #6 g_logv
    from /opt/gnome/lib/libglib-2.0.so.0
  • #7 g_log
    from /opt/gnome/lib/libglib-2.0.so.0
  • #8 g_thread_create_posix_impl
    from /opt/gnome/lib/libgthread-2.0.so.0
  • #9 g_thread_create_full
    from /opt/gnome/lib/libglib-2.0.so.0
  • #10 g_thread_pool_start_thread
    from /opt/gnome/lib/libglib-2.0.so.0
  • #11 g_thread_pool_push
    from /opt/gnome/lib/libglib-2.0.so.0
  • #12 giop_thread_request_push_key
    from /opt/gnome/lib/libORBit-2.so.0
  • #13 pool_push_request_for_T
    from /opt/gnome/lib/libORBit-2.so.0
  • #14 ORBit_POA_handle_request
    from /opt/gnome/lib/libORBit-2.so.0
  • #15 ORBit_handle_request
    from /opt/gnome/lib/libORBit-2.so.0
  • #16 giop_connection_handle_input
    from /opt/gnome/lib/libORBit-2.so.0
  • #17 link_connection_io_handler
    from /opt/gnome/lib/libORBit-2.so.0
  • #18 link_source_dispatch
    from /opt/gnome/lib/libORBit-2.so.0
  • #19 g_main_context_dispatch
    from /opt/gnome/lib/libglib-2.0.so.0
  • #20 g_main_context_iterate
    from /opt/gnome/lib/libglib-2.0.so.0
  • #21 g_main_loop_run
    from /opt/gnome/lib/libglib-2.0.so.0
  • #22 link_io_thread_fn
    from /opt/gnome/lib/libORBit-2.so.0
  • #23 g_thread_create_proxy
    from /opt/gnome/lib/libglib-2.0.so.0
  • #24 start_thread
    from /lib/tls/libpthread.so.0
  • #25 clone
    from /lib/tls/libc.so.6



Other information:
Comment 1 Chenthill P 2005-04-21 09:04:19 UTC
This happens since EDS has crashed and so the client has to be reloaded. So the
appointment editor should not be opened when the client is not in a loaded state.
Comment 2 Chenthill P 2005-08-04 14:55:18 UTC
Decreasing the severtiy and priority as it occurs only after sending a large
number of meetings and EDS crashes due to addressbook.
Comment 3 Chenthill P 2005-08-22 22:14:23 UTC
Fix for 272191 will fix this too.

*** This bug has been marked as a duplicate of 272191 ***
Comment 4 Chenthill P 2005-08-22 22:16:38 UTC
Its actually a duplicate of 305322
Comment 5 Chenthill P 2005-08-22 22:17:20 UTC

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