Description of problem:
Started firefox.x86_64 46.0.1-4.fc24 and gnome-shell, gnome-software and evolution-alarm-notify crashed
Version-Release number of selected component:
pkg_fingerprint: 73BD E983 81B4 6521
pkg_vendor: Fedora Project
reproducible: Not sure how to reproduce the problem
runlevel: N 5
Thread no. 1 (5 frames)
#0 _g_log_abort at gmessages.c:325
#3 gdk_event_source_check at gdkeventsource.c:92
#4 g_main_context_check at gmain.c:3681
#6 g_main_context_iteration at gmain.c:3901
#7 g_application_run at gapplication.c:2381
Created attachment 1161150 [details]
Created attachment 1161151 [details]
Created attachment 1161153 [details]
Created attachment 1161154 [details]
Created attachment 1161155 [details]
Created attachment 1161156 [details]
Created attachment 1161157 [details]
Created attachment 1161158 [details]
Created attachment 1161159 [details]
Created attachment 1161160 [details]
Created attachment 1161161 [details]
Created attachment 1161162 [details]
Thanks for a bug report. This crashed in gdk (it's part of gtk+), claiming:
> Error reading events from display: Broken pipe
I guess from it that there happened something with the display, maybe when you run gnome-shell, then it restarted it or anything, like when you've switched from X11 to Wayland or vice versa, when the evolution-alarm-notify was still running. Could it be it? In any case, there is nothing from the evolution code in the crashing backtrace, except of the main() itself, and the other threads are also idle, thus I'm moving this to gtk+ for further investigation.
*** Bug 1349087 has been marked as a duplicate of this bug. ***
*** Bug 1379445 has been marked as a duplicate of this bug. ***
*** Bug 1387780 has been marked as a duplicate of this bug. ***
*** Bug 1398841 has been marked as a duplicate of this bug. ***
This happened to me when switching to an external display, which matches your suspicions.
*** Bug 1402213 has been marked as a duplicate of this bug. ***
Similar problem has been detected:
when your computer posts and does not display anything unplug all the power connectors and peripherals from the motherboard and re-connect them after a fiew minuts happened thismorning so i left it doing mem test for a couple of hours and then i schacked the temperature and evrythings running whell but i boot fedora live disk and all these errors
pkg_fingerprint: 4089 D8F2 FDB1 9C98
pkg_vendor: Fedora Project
reason: evolution-alarm-notify killed by SIGTRAP
runlevel: N 5
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. 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 25 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 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 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.