Description of problem:
I was executing the outputs test of the Test_Day:2016-11-03_BetterSwitchableGraphicsSupport. Repeatedly inserting/removing the HDMI cable caused this crash.
- Hybrid graphics laptop (Intel + NVIDIA GTX 965M)
- HDMI port is wired to the dGPU.
- Internal monitor is 1920x1080
- External monitor is a Dell U2515H (2560x1440)
- Running "Switchable Test Day live image"
Version-Release number of selected component:
pkg_fingerprint: 4089 D8F2 FDB1 9C98
pkg_vendor: Fedora Project
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:347
#5 handle_fn_f7 at gsd-xrandr-manager.c:1007
#6 gsd_xrandr_manager_2_video_mode_switch at gsd-xrandr-manager.c:364
#7 handle_method_call_xrandr_2 at gsd-xrandr-manager.c:1365
#8 handle_method_call at gsd-xrandr-manager.c:1394
#9 call_in_idle_cb at gdbusconnection.c:4836
Potential duplicate: bug 1044713
Created attachment 1217547 [details]
Created attachment 1217548 [details]
Created attachment 1217549 [details]
Created attachment 1217550 [details]
Created attachment 1217551 [details]
Created attachment 1217552 [details]
Created attachment 1217553 [details]
Created attachment 1217554 [details]
Created attachment 1217555 [details]
Created attachment 1217556 [details]
Created attachment 1217557 [details]
Created attachment 1217558 [details]
Created attachment 1217559 [details]
The above situation had runtime PM disabled (via nouveau.runpm=0). With runtime PM enabled (but acpi_osi="!Windows 2015" due to bug 1354256), this is visible:
33.632330 kernel: nouveau 0000:01:00.0: DRM: resuming kernel object tree...
33.876456 kernel: nouveau 0000:01:00.0: priv: GPC0: 419df4 00000000 (1a40820e)
33.876653 kernel: nouveau 0000:01:00.0: priv: GPC1: 419df4 00000000 (1a40820e)
33.895865 kernel: nouveau 0000:01:00.0: DRM: resuming client object trees...
33.895997 kernel: nouveau 0000:01:00.0: DRM: resuming display...
33.896117 kernel: nouveau 0000:01:00.0: DRM: resuming console...
38.884466 gnome-settings-: gnome_rr_output_list_modes: assertion 'output != NULL' failed
38.885187 kernel: show_signal_msg: 12 callbacks suppressed
38.885214 kernel: gnome-settings-: segfault at 0 ip 00007f6c3631a5bd sp 00007fff808d3650 error 4 in libgnome-desktop-3.so.12.2.0[7f6c362fe000+37000]
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.