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 313790 - Evolution crashed while loading calendar data
Evolution crashed while loading calendar data
Status: RESOLVED OBSOLETE
Product: evolution
Classification: Applications
Component: Calendar
2.4.x
Other Linux
: Normal normal
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
evolution[groupwise]
Depends on:
Blocks: 318200
 
 
Reported: 2005-08-18 06:11 UTC by Poornima
Modified: 2013-09-13 00:54 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Poornima 2005-08-18 06:11:28 UTC 



+
Trace
    62511






Thread 1
          (process 10022)


    

  • 
#0
mono_handle_exception

    
                from
                /usr/lib/libmono.so.0

    

    • 

  • 
#1
mono_arch_handle_exception

    
                from
                /usr/lib/libmono.so.0

    

    • 

  • 
#2
mini_init

    
                from
                /usr/lib/libmono.so.0

    

    • 

  • 
#3
<signal handler called>

    • 

  • 
#4
pthread_cond_signal

    
                from
                /lib/tls/libpthread.so.0

    

    • 

  • 
#5
cal_query_cb

    
                at e-cal.c
                  line
                  954

    

    • 

  • 
#6
e_cal_marshal_VOID__INT_POINTER

    
                at e-cal-marshal.c
                  line
                  164

    

    • 

  • 
#7
g_closure_invoke

    
                from
                /opt/gnome/lib/libgobject-2.0.so.0

    

    • 

  • 
#8
g_signal_chain_from_overridden

    
                from
                /opt/gnome/lib/libgobject-2.0.so.0

    

    • 

  • 
#9
g_signal_emit_valist

    
                from
                /opt/gnome/lib/libgobject-2.0.so.0

    

    • 

  • 
#10
g_signal_emit

    
                from
                /opt/gnome/lib/libgobject-2.0.so.0

    

    • 

  • 
#11
impl_notifyQuery

    
                at e-cal-listener.c
                  line
                  638

    

    • 

  • 
#12
_ORBIT_skel_small_GNOME_Evolution_Calendar_CalListener_notifyQuery

    
                at Evolution-DataServer-Calendar-common.c
                  line
                  204

    

    • 

  • 
#13
IOP_profile_dump

    
                from
                /opt/gnome/lib/libORBit-2.so.0

    

    • 

  • 
#14
ORBit_OAObject_invoke

    
                from
                /opt/gnome/lib/libORBit-2.so.0

    

    • 

  • 
#15
ORBit_small_invoke_adaptor

    
                from
                /opt/gnome/lib/libORBit-2.so.0

    

    • 

  • 
#16
ORBit_recv_buffer_return_sys_exception

    
                from
                /opt/gnome/lib/libORBit-2.so.0

    

    • 

  • 
#17
ORBit_recv_buffer_return_sys_exception

    
                from
                /opt/gnome/lib/libORBit-2.so.0

    

    • 

  • 
#18
giop_thread_queue_process

    
                from
                /opt/gnome/lib/libORBit-2.so.0

    

    • 

  • 
#19
giop_init

    
                from
                /opt/gnome/lib/libORBit-2.so.0

    

    • 

  • 
#20
g_thread_pool_push

    
                from
                /opt/gnome/lib/libglib-2.0.so.0

    

    • 

  • 
#21
g_thread_create_full

    
                from
                /opt/gnome/lib/libglib-2.0.so.0

    

    • 

  • 
#22
start_thread

    
                from
                /lib/tls/libpthread.so.0

    

    • 

  • 
#23
clone

    
                from
                /lib/tls/libc.so.6

    

    • 









Not reproducible always so set Severity to 'Normal'.






Comment 1


viren





          2005-09-08 12:26:07 UTC
        



Does this still happen ?






Comment 2


Poornima





          2005-09-12 09:28:28 UTC
        



This is not consistently reproducible bug.






Comment 3


Chenthill P





          2006-01-12 20:58:35 UTC
        



Please reopen if you find it happening. Have not seen this happening for since long time.