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 669601 - evolution crashes when publishing calendar
evolution crashes when publishing calendar
Status: RESOLVED DUPLICATE of bug 664370
Product: evolution
Classification: Applications
Component: Calendar
3.2.x (obsolete)
Other Linux
: Normal critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2012-02-07 19:53 UTC by Bastien Durel
Modified: 2015-04-29 15:34 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
bt full of core file (1.80 KB, text/plain)
2012-02-07 19:53 UTC, Bastien Durel 		Details

Description Bastien Durel 2012-02-07 19:53:16 UTC 
Created attachment 207018 [details]
bt full of core file

Hello,

I have an old, big, calendar in ical, that I used to publish on my webdav webserver.
Now it crashes evolution with a sigsegv -- see backtrace attached -- even if I use another method to publish it.
Evo is crashing at startup if calendar is set to auto-publish (and evo not stating offline)

I imported the calendar file to another computer, with a test account, I got same crash. with an smaller (but real-life) calendar I got the same result. With an almost-empty, created from scratch one, I got no crash.

The file is sent to the webserver, but it's corrupted (size on disk is 2578902 on my computer, 2731472)

I'm using Debian, evolution version 3.2.2-1

I'll be happy to send more information if needed, but I prefer not to send my calendar and core file in public.
Comment 1 André Klapper 2012-02-07 20:13:28 UTC 
"thread apply all bt" is also welcome. :)
Posting your stacktrace inline so the traceparser can pick it up:

+ Trace 229620

  • #0 pvl_head
    from /usr/lib/libical.so.0
  • #1 icalcomponent_free
    from /usr/lib/libical.so.0
  • #2 icalcomponent_free
    from /usr/lib/libical.so.0
  • #3 write_calendar
    at publish-format-ical.c line 131
  • #4 publish_calendar_as_ical
    at publish-format-ical.c line 151
  • #5 publish_online
    at publish-calendar.c line 225
  • #6 publish
    at publish-calendar.c line 461
  • #7 publish
    at publish-calendar.c line 444
  • #8 publish_urls
    at publish-calendar.c line 930
  • #9 ??
    from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  • #10 start_thread
    from /lib/x86_64-linux-gnu/libpthread.so.0
  • #11 clone
    from /lib/x86_64-linux-gnu/libc.so.6
  • #12 ?? 






Comment 2


Bastien Durel





          2012-02-07 20:17:48 UTC
        






+
Trace
    229621






Thread 6
          (Thread 0x7f5853dfb700 (LWP 10729))


    

  • 
#0
read

    
                from
                /lib/x86_64-linux-gnu/libc.so.6

    

    • 

  • 
#1
??

    
                from
                /lib/x86_64-linux-gnu/libglib-2.0.so.0

    

    • 

  • 
#2
??

    
                from
                /lib/x86_64-linux-gnu/libglib-2.0.so.0

    

    • 

  • 
#3
start_thread

    
                from
                /lib/x86_64-linux-gnu/libpthread.so.0

    

    • 

  • 
#4
clone

    
                from
                /lib/x86_64-linux-gnu/libc.so.6

    

    • 

  • 
#5
??

    • 



Thread 2
          (Thread 0x7f58545fc700 (LWP 10728))


    

  • 
#0
__pthread_mutex_unlock_usercnt

    
                from
                /lib/x86_64-linux-gnu/libpthread.so.0

    

    • 

  • 
#1
g_main_context_prepare

    
                from
                /lib/x86_64-linux-gnu/libglib-2.0.so.0

    

    • 

  • 
#2
??

    
                from
                /lib/x86_64-linux-gnu/libglib-2.0.so.0

    

    • 

  • 
#3
g_main_loop_run

    
                from
                /lib/x86_64-linux-gnu/libglib-2.0.so.0

    

    • 

  • 
#4
??

    
                from
                /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0

    

    • 

  • 
#5
??

    
                from
                /lib/x86_64-linux-gnu/libglib-2.0.so.0

    

    • 

  • 
#6
start_thread

    
                from
                /lib/x86_64-linux-gnu/libpthread.so.0

    

    • 

  • 
#7
clone

    
                from
                /lib/x86_64-linux-gnu/libc.so.6

    

    • 

  • 
#8
??

    • 



Thread 1
          (Thread 0x7f58400e2700 (LWP 10759))


    

  • 
#0
pvl_head

    
                from
                /usr/lib/libical.so.0

    

    • 

  • 
#1
icalcomponent_free

    
                from
                /usr/lib/libical.so.0

    

    • 

  • 
#2
icalcomponent_free

    
                from
                /usr/lib/libical.so.0

    

    • 

  • 
#3
write_calendar

    
                at publish-format-ical.c
                  line
                  131

    

    • 

  • 
#4
publish_calendar_as_ical

    
                at publish-format-ical.c
                  line
                  151

    

    • 

  • 
#5
publish_online

    
                at publish-calendar.c
                  line
                  225

    

    • 

  • 
#6
publish

    
                at publish-calendar.c
                  line
                  461

    

    • 

  • 
#7
publish

    
                at publish-calendar.c
                  line
                  444

    

    • 

  • 
#8
publish_urls

    
                at publish-calendar.c
                  line
                  930

    

    • 

  • 
#9
??

    
                from
                /lib/x86_64-linux-gnu/libglib-2.0.so.0

    

    • 

  • 
#10
start_thread

    
                from
                /lib/x86_64-linux-gnu/libpthread.so.0

    

    • 

  • 
#11
clone

    
                from
                /lib/x86_64-linux-gnu/libc.so.6

    

    • 

  • 
#12
??

    • 













Comment 3


Bastien Durel





          2012-02-07 20:31:14 UTC
        



With glib debug symbols :





+
Trace
    229622






Thread 6
          (Thread 0x7f5853dfb700 (LWP 10729))


    

  • 
#0
read

    
                at ../sysdeps/unix/syscall-template.S
                  line
                  82

    

    • 

  • 
#1
unix_signal_helper_thread

    
                at /tmp/buildd/glib2.0-2.30.2/./glib/gmain.c
                  line
                  4542

    

    • 

  • 
#2
g_thread_create_proxy

    
                at /tmp/buildd/glib2.0-2.30.2/./glib/gthread.c
                  line
                  1962

    

    • 

  • 
#3
start_thread

    
                at pthread_create.c
                  line
                  304

    

    • 

  • 
#4
clone

    
                at ../sysdeps/unix/sysv/linux/x86_64/clone.S
                  line
                  112

    

    • 

  • 
#5
??

    • 













Comment 4


Bastien Durel





          2012-02-07 20:34:03 UTC
        



try to give all threads :





+
Trace
    229623






Thread 6
          (Thread 0x7f5853dfb700 (LWP 10729))


    

  • 
#0
read

    
                at ../sysdeps/unix/syscall-template.S
                  line
                  82

    

    • 

  • 
#1
unix_signal_helper_thread

    
                at /tmp/buildd/glib2.0-2.30.2/./glib/gmain.c
                  line
                  4542

    

    • 

  • 
#2
g_thread_create_proxy

    
                at /tmp/buildd/glib2.0-2.30.2/./glib/gthread.c
                  line
                  1962

    

    • 

  • 
#3
start_thread

    
                at pthread_create.c
                  line
                  304

    

    • 

  • 
#4
clone

    
                at ../sysdeps/unix/sysv/linux/x86_64/clone.S
                  line
                  112

    

    • 

  • 
#5
??

    • 













Comment 5


Bastien Durel





          2012-02-07 20:40:03 UTC
        



Well ... the expanded trace is missing some infos, but "see full trace don't", sorry for the noise.






Comment 6


Akhil Laddha





          2012-02-08 08:24:45 UTC
        



Similar issue reported in downstream, it has valgrind trace as well.
https://bugzilla.novell.com/show_bug.cgi?id=730514






Comment 7


Milan Crha





          2015-04-29 15:34:11 UTC
        



This had been fixed in 3.2.3, according to bug #664370, thus I mark this as a duplicate of it.

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