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 355075 - crash in Evolution: Google Calendar Error
crash in Evolution: Google Calendar Error
Status: RESOLVED DUPLICATE of bug 312348
Product: evolution
Classification: Applications
Component: Calendar
2.8.x (obsolete)
Other Linux
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2006-09-09 08:53 UTC by heyko.oelrichs
Modified: 2006-09-11 15:14 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description heyko.oelrichs 2006-09-09 08:53:29 UTC 
What were you doing when the application crashed?
Ich habe versuch die Google Calender zu öffnen. Vor dem Update lief das einwandfrei jetzt hängt sich Evolution auf sobald ich mehr als zwei "Im Web" Kalender öffne.


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.0 2006-09-04 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 157884416 vsize: 0 resident: 157884416 share: 0 rss: 35500032 rss_rlim: 0
CPU usage: start_time: 1157791080 rtime: 0 utime: 701 stime: 0 cutime:652 cstime: 0 timeout: 49 it_real_value: 0 frequency: 1

Backtrace was generated from '/usr/bin/evolution-2.8'

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1231509840 (LWP 5361)]
[New Thread -1319220320 (LWP 5565)]
[New Thread -1310123104 (LWP 5563)]
[New Thread -1301730400 (LWP 5562)]
[New Thread -1293337696 (LWP 5514)]
[New Thread -1274537056 (LWP 5513)]
[New Thread -1265685600 (LWP 5488)]
[New Thread -1257256032 (LWP 5477)]
[New Thread -1248736352 (LWP 5476)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 71944







Comment 1


André Klapper





          2006-09-11 12:49:02 UTC
        



heyko: for future reference, please write in english. thanks in advance.

Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Can you get us one with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so.






Comment 2


heyko.oelrichs





          2006-09-11 14:14:32 UTC
        






+
Trace
    72120






Thread 1
          (Thread -1208973648 (LWP 6509))


    

  • 
#0
__kernel_vsyscall

    • 

  • 
#1
__waitpid_nocancel

    
                from
                /lib/tls/i686/cmov/libc.so.6

    

    • 

  • 
#2
gnome_gtk_module_info_get

    
                from
                /usr/lib/libgnomeui-2.so.0

    

    • 

  • 
#3
<signal handler called>

    • 

  • 
#4
__kernel_vsyscall

    • 

  • 
#5
*__GI_raise

    
                from
                /lib/tls/i686/cmov/libc.so.6

    

    • 

  • 
#6
*__GI_abort

    
                from
                /lib/tls/i686/cmov/libc.so.6

    

    • 

  • 
#7
g_logv

    
                from
                /usr/lib/libglib-2.0.so.0

    

    • 

  • 
#8
g_log

    
                from
                /usr/lib/libglib-2.0.so.0

    

    • 

  • 
#9
g_assert_warning

    
                from
                /usr/lib/libglib-2.0.so.0

    

    • 

  • 
#10
ORBit_object_peek_connection

    
                from
                /usr/lib/libORBit-2.so.0

    

    • 

  • 
#11
ORBit_object_get_connection

    
                from
                /usr/lib/libORBit-2.so.0

    

    • 

  • 
#12
ORBit_small_invoke_stub

    
                from
                /usr/lib/libORBit-2.so.0

    

    • 

  • 
#13
ORBit_small_invoke_stub_n

    
                from
                /usr/lib/libORBit-2.so.0

    

    • 

  • 
#14
ORBit_c_stub_invoke

    
                from
                /usr/lib/libORBit-2.so.0

    

    • 

  • 
#15
GNOME_Evolution_Calendar_CalView_start

    
                from
                /usr/lib/libecal-1.2.so.7

    

    • 

  • 
#16
e_cal_view_start

    
                from
                /usr/lib/libecal-1.2.so.7

    

    • 

  • 
#17
e_cal_model_copy_component_data

    
                from
                /usr/lib/evolution/2.8/components/libevolution-calendar.so

    

    • 

  • 
#18
e_cal_model_copy_component_data

    
                from
                /usr/lib/evolution/2.8/components/libevolution-calendar.so

    

    • 

  • 
#19
gnome_calendar_discard_view_menus

    
                from
                /usr/lib/evolution/2.8/components/libevolution-calendar.so

    

    • 

  • 
#20
g_cclosure_marshal_VOID

    
                from
                /usr/lib/libgobject-2.0.so.0

    

    • 

  • 
#21
g_closure_invoke

    
                from
                /usr/lib/libgobject-2.0.so.0

    

    • 

  • 
#22
g_signal_chain_from_overridden

    
                from
                /usr/lib/libgobject-2.0.so.0

    

    • 

  • 
#23
g_signal_emit_valist

    
                from
                /usr/lib/libgobject-2.0.so.0

    

    • 

  • 
#24
g_signal_emit

    
                from
                /usr/lib/libgobject-2.0.so.0

    

    • 

  • 
#25
e_cal_free_alarms

    
                from
                /usr/lib/libecal-1.2.so.7

    

    • 

  • 
#26
g_source_is_destroyed

    
                from
                /usr/lib/libglib-2.0.so.0

    

    • 

  • 
#27
g_main_context_dispatch

    
                from
                /usr/lib/libglib-2.0.so.0

    

    • 

  • 
#28
g_main_context_check

    
                from
                /usr/lib/libglib-2.0.so.0

    

    • 

  • 
#29
g_main_loop_run

    
                from
                /usr/lib/libglib-2.0.so.0

    

    • 

  • 
#30
bonobo_main

    
                from
                /usr/lib/libbonobo-2.so.0

    

    • 

  • 
#31
main

    • 

  • 
#0
__kernel_vsyscall

    • 















Comment 3


André Klapper





          2006-09-11 15:14:45 UTC
        



Thanks a lot for the stacktrace! 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 312348 ***