Version-Release number of selected component: evolution-data-server-3.10.4-1.fc20 Additional info: reporter: libreport-2.1.12 backtrace_rating: 4 cmdline: /usr/libexec/evolution-calendar-factory crash_function: magazine_chain_pop_head executable: /usr/libexec/evolution-calendar-factory kernel: 3.13.3-201.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 magazine_chain_pop_head at gslice.c:545 #1 thread_memory_magazine1_alloc at gslice.c:848 #2 g_slice_alloc at gslice.c:1007 #3 g_list_append at glist.c:232 #4 e_cal_backend_add_view at e-cal-backend.c:1236 #5 data_cal_handle_get_view_cb at e-data-cal.c:1320 #6 ffi_call_unix64 at ../src/x86/unix64.S:76 #7 ffi_call at ../src/x86/ffi64.c:522 #8 g_cclosure_marshal_generic at gclosure.c:1454 #11 g_signal_emitv at gsignal.c:3063 Potential duplicate: bug 769523
Created attachment 864393 [details] File: backtrace
Created attachment 864394 [details] File: cgroup
Created attachment 864395 [details] File: core_backtrace
Created attachment 864396 [details] File: dso_list
Created attachment 864397 [details] File: environ
Created attachment 864398 [details] File: exploitable
Created attachment 864399 [details] File: limits
Created attachment 864400 [details] File: maps
Created attachment 864401 [details] File: open_fds
Created attachment 864402 [details] File: proc_pid_status
Created attachment 864403 [details] File: var_log_messages
Thanks for a bug report. I see in the backtrace that this crashed due to memory corruption, something probably tried to access already freed memory. The backtrace hows that it was discovered during creation of a new calendar view, which can be done on various occasions, the most common is when changing displayed time in a Calendar view. The backtrace doesn't show anything more, unfortunately. It'll be helpful, if you could provide any steps how to reproduce the crash, what calendar types (On This Computer, Google, CalDAV,...) you use and basically any detail what you did before the process crashed. Thanks in advance.
(In reply to Milan Crha from comment #12) > Thanks for a bug report. I see in the backtrace that this crashed due to > memory corruption, something probably tried to access already freed memory. > The backtrace hows that it was discovered during creation of a new calendar > view, which can be done on various occasions, the most common is when > changing displayed time in a Calendar view. The backtrace doesn't show > anything more, unfortunately. > > It'll be helpful, if you could provide any steps how to reproduce the crash, > what calendar types (On This Computer, Google, CalDAV,...) you use and > basically any detail what you did before the process crashed. Thanks in > advance. Sorry, but I have no idea what caused the crash. I do have my ownCloud account configured in GNOME, and ownCloud comes with a calendar. That may have something to do with the crash. I never use the ownCloud or GNOME calendars, though.
(In reply to Joshua Escamilla from comment #13) > (In reply to Milan Crha from comment #12) > > Thanks for a bug report. I see in the backtrace that this crashed due to > > memory corruption, something probably tried to access already freed memory. > > The backtrace hows that it was discovered during creation of a new calendar > > view, which can be done on various occasions, the most common is when > > changing displayed time in a Calendar view. The backtrace doesn't show > > anything more, unfortunately. > > > > It'll be helpful, if you could provide any steps how to reproduce the crash, > > what calendar types (On This Computer, Google, CalDAV,...) you use and > > basically any detail what you did before the process crashed. Thanks in > > advance. > > Sorry, but I have no idea what caused the crash. I do have my ownCloud > account configured in GNOME, and ownCloud comes with a calendar. That may > have something to do with the crash. I never use the ownCloud or GNOME > calendars, though. Hi, I have a crash with owncloud. This crash comes while sync beginning (but not anytime !). For information, i use ownCloud on a Raspberry Pi, at home. Can this bug provides of the "time sync" ? (because with overclock at 800Mhz, it's best). Thank's.
Hi Frédéric, I'm not sure I follow. If you are able to reproduce the crash reliably, then I'd like to ask you for a debugging under valgrind, which may give us a hint. If you have updated backtrace with exact evolution-data-server version, then it'll help too.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
Another user experienced a similar problem: I removed the last account from the gnome account settings wizard. Then I tried to add a new account. Nothing happended for a few seconds. Then I got the abrt report about the crashed evolution-data server. reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: /usr/libexec/evolution-calendar-factory crash_function: magazine_chain_pop_head executable: /usr/libexec/evolution-calendar-factory kernel: 3.16.3-200.fc20.x86_64 package: evolution-data-server-3.10.4-5.fc20 reason: evolution-calendar-factory killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: This occurred after I add my google account into Online accounts reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: /usr/libexec/evolution-calendar-factory crash_function: magazine_chain_pop_head executable: /usr/libexec/evolution-calendar-factory kernel: 3.17.3-200.fc20.x86_64 package: evolution-data-server-3.10.4-7.fc20 reason: evolution-calendar-factory killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.