Description of problem: I attempted to import account and mail information into evolution from an evolution backup archive. I tried it several times. This issue doesn't happen very often, but the import of the evolution archive never worked. Version-Release number of selected component: evolution-3.6.1-1.fc18 Additional info: libreport version: 2.0.18 abrt_version: 2.0.18 backtrace_rating: 4 cmdline: evolution crash_function: g_settings_backend_dispatch_signal kernel: 3.6.5-2.fc18.x86_64 truncated backtrace: :Thread no. 1 (10 frames) : #0 g_settings_backend_dispatch_signal at gsettingsbackend.c:340 : #1 g_settings_backend_path_changed at gsettingsbackend.c:496 : #2 dconf_engine_change_notify at dconfsettingsbackend.c:233 : #3 dconf_engine_watch_established at dconf-engine.c:735 : #5 dconf_gdbus_method_call_done at dconf-gdbus-thread.c:230 : #6 g_simple_async_result_complete at gsimpleasyncresult.c:775 : #7 g_dbus_connection_call_done at gdbusconnection.c:5339 : #8 g_simple_async_result_complete at gsimpleasyncresult.c:775 : #9 complete_in_idle_cb at gsimpleasyncresult.c:787 : #13 g_main_context_iteration at gmain.c:3351
Created attachment 638877 [details] File: core_backtrace
Created attachment 638878 [details] File: environ
Created attachment 638879 [details] File: limits
Created attachment 638880 [details] File: backtrace
Created attachment 638881 [details] File: cgroup
Created attachment 638882 [details] File: executable
Created attachment 638883 [details] File: maps
Created attachment 638884 [details] File: dso_list
Created attachment 638885 [details] File: proc_pid_status
Created attachment 638886 [details] File: open_fds
Created attachment 638887 [details] File: var_log_messages
this crash happens very rarely. Out of about maybe twenty import attempts it happened only one time.
Thanks for a bug report. The crashing thread is a DConf dedicated thread, thus I'm moving this there.
*** Bug 951763 has been marked as a duplicate of this bug. ***
The last duplicate is from Fedora 19, thus I'm moving this there.
*** Bug 971183 has been marked as a duplicate of this bug. ***
updated to 3.8.3. started. one of time its crashed.
Started evolution and it crashed. reporter: libreport-2.1.4 backtrace_rating: 3 cmdline: evolution crash_function: g_settings_backend_dispatch_signal executable: /usr/bin/evolution kernel: 3.9.4-300.fc19.x86_64 package: evolution-3.8.3-1.fc19 reason: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV) runlevel: N 5 uid: 1000
Seeing this quite a lot when running evo today
Same here, evolution crashed right after started and abrt shows this bug here, evolution-3.8.3-2.fc19.x86_64.
Clicked on Evolution icon and got a message that it had crashed. I do not knoe how or why or how to reproduce it. reporter: libreport-2.1.6 backtrace_rating: 4 cmdline: evolution crash_function: g_settings_backend_dispatch_signal executable: /usr/bin/evolution kernel: 3.10.6-200.fc19.x86_64 package: evolution-3.8.5-2.fc19 reason: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV) runlevel: N 5 uid: 500
*** Bug 999260 has been marked as a duplicate of this bug. ***
Just a me too with 3.8.5-2fc19.
Filed upstream as https://bugzilla.gnome.org/show_bug.cgi?id=710367
upstream suggests this is an evolution bug after all
(In reply to Milan Bouchet-Valat from comment #24) > Filed upstream as https://bugzilla.gnome.org/show_bug.cgi?id=710367 Thanks. Let's deal with this upstream then, to avoid duplication of the work.
*** Bug 1108509 has been marked as a duplicate of this bug. ***
This has a fix upstream; and it's still causing frequent problems with Evolution (in Fedora 20). Can this be backported (as comments in the upstream bug suggest Ubuntu has done)?
Another user experienced a similar problem: Clicked on a 'mailto' link. reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: evolution --component=mail mailto:?body=Click%20on%20the%20link%20below%20to%20see%20LG%20LB630V%2042%20Inch%20Full%20HD%20Smart%20LED%20TV%20with%20webOS.%20(cat%20no.%202275242)%20EUR469.99%20*%20on%20Argos.ie%0D%0Ahttp%3A%2F%2Fwww.argos.ie%2FProductDisplayTRK019%3FpartNumber%3D2275242%0D%0A%0D%0A%0D%0A*Please%20note%20this%20price%20is%20as%20shown%20on%20Argos.ie%20at%20the%20time%20the%20email%20was%20sent.%20Go%20to%20Argos.ie%20to%20check%20the%20latest%20details%20and%20price. crash_function: g_settings_backend_dispatch_signal executable: /usr/bin/evolution kernel: 3.14.23-100.fc19.x86_64 package: evolution-3.8.5-2.fc19 reason: evolution killed by SIGSEGV runlevel: N 5 type: CCpp uid: 10000
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.