Red Hat Bugzilla – Bug 1279343
[abrt] gnome-shell: get_application_proxy(): gnome-shell killed by SIGSEGV
Last modified: 2016-12-20 10:33:33 EST
Version-Release number of selected component:
runlevel: N 5
Thread no. 1 (10 frames)
#0 get_application_proxy at shell-app.c:922
#1 g_task_return_now at gtask.c:1104
#2 g_task_return at gtask.c:1162
#3 init_second_async_cb at gdbusproxy.c:1805
#4 g_task_return_now at gtask.c:1104
#5 g_task_return at gtask.c:1162
#6 async_init_get_all_cb at gdbusproxy.c:1443
#7 g_task_return_now at gtask.c:1104
#8 g_task_return at gtask.c:1162
#9 g_dbus_connection_call_done at gdbusconnection.c:5702
Created attachment 1091644 [details]
Created attachment 1091645 [details]
Created attachment 1091646 [details]
Created attachment 1091647 [details]
Created attachment 1091648 [details]
Created attachment 1091649 [details]
Created attachment 1091650 [details]
Created attachment 1091651 [details]
Created attachment 1091652 [details]
Created attachment 1091653 [details]
Created attachment 1091654 [details]
Created attachment 1091655 [details]
Any idea what triggered this? I've been seeing these crash reports, but we've been unable to figure out how this could possibly happen.
(In reply to Owen Taylor from comment #13)
> Any idea what triggered this? I've been seeing these crash reports, but
> we've been unable to figure out how this could possibly happen.
IIRC at the time I had just launched gedit, it was blocking on something (a DAVFS share?) and had not shown its main window (and didn’t look like it ever would). I executed `pkill gedit` in a terminal, and Shell crashed.
It’s possible this was caused by an inconsistent state, since I had upgraded to F23 but not yet run `sudo dnf distro-sync`. However, when I did so I don’t recall it touching any relevant packages.
Sorry this isn’t very helpful — that’s all observed. I don’t have a concrete way of reproducing it.
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. 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'
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 23 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 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 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
Thank you for reporting this bug and we are sorry it could not be fixed.