Red Hat Bugzilla – Bug 1473183
[abrt] gnome-settings-daemon: real_assign_crtcs(): gsd-xrandr killed by signal 11
Last modified: 2018-05-29 08:07:20 EDT
Description of problem:
I think you will not be easily able to reproduce the problem because I did the same scenario many times but this was the first time something crashed.
But still here is the step-by-step:
1. I woke up my laptop from sleep
2. I connected it to external display using HDMI
3. I pressed Fn+F4 shortcut (on Acer Aspire 5740G means switch between display layouts: only internal, only external, side by side and mirrored)
4. It did not work and only internal display was active so I tried to press the shortcut repeatedly
5. I disconnected and again connected HDMI (you know the old "turn it off and on again" method)
6. I pressed Fn+F4 again and now it finally switched to side-by-side layout with both internal and external display
7. Then this error reporting window appeared
I guess that the stack trace will be the most useful for you.
And maybe it may be useful information for you that I currently try to use Wayland. It did not ever happen with X11.
Version-Release number of selected component:
runlevel: N 5
Thread no. 1 (10 frames)
#0 real_assign_crtcs at gnome-rr-config.c:941
#1 crtc_assignment_new at gnome-rr-config.c:1068
#2 gnome_rr_config_apply_helper at gnome-rr-config.c:628
#3 gnome_rr_config_apply at gnome-rr-config.c:650
#4 apply_configuration at gsd-xrandr-manager.c:350
#5 handle_fn_f7 at gsd-xrandr-manager.c:1010
#6 gsd_xrandr_manager_2_video_mode_switch at gsd-xrandr-manager.c:367
#7 handle_method_call_xrandr_2 at gsd-xrandr-manager.c:1370
#8 handle_method_call at gsd-xrandr-manager.c:1399
#9 call_in_idle_cb at gdbusconnection.c:4850
Potential duplicate: bug 1352316
Created attachment 1301576 [details]
Created attachment 1301577 [details]
Created attachment 1301578 [details]
Created attachment 1301579 [details]
Created attachment 1301580 [details]
Created attachment 1301581 [details]
Created attachment 1301582 [details]
Created attachment 1301583 [details]
Created attachment 1301584 [details]
Created attachment 1301585 [details]
Created attachment 1301586 [details]
Created attachment 1301587 [details]
*** Bug 1473394 has been marked as a duplicate of this bug. ***
This message is a reminder that Fedora 26 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 26. 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 26 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 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26
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.