Description of problem: My laptop uses optimus and is wired so one of the external monitor ports is on the nvidia chip. Due to this I have testing packages enabled so I can use nouveau output provider PRIME support. I have 2 external monitors connected, one to VGA via the intel chipset (VGA2), and one to DVI via the NVIDIA chipset (DP-2) . I am also trying to use 2 DisplayLink monitors in addition (DVI-0 and DVI-1). I ran these commands to set up my monitors, and had the crash on the last one: [ben@localhost ~]$ xrandr --output DP-2 --auto --right-of VGA2 [ben@localhost ~]$ xrandr --output DVI-0 --auto --left-of VGA2 [ben@localhost ~]$ xrandr --output DVI-1 --auto --left-of VGA2 [ben@localhost ~]$ xrandr --output LVDS2 --auto --below VGA2 [ben@localhost ~]$ xrandr --output DVI-1 --auto --left-of VGA2 [ben@localhost ~]$ xrandr --output DVI-1 --off [ben@localhost ~]$ xrandr --output DVI-0 --off [ben@localhost ~]$ xrandr --output DVI-1 --auto --left-of VGA2 [ben@localhost ~]$ xrandr --output DVI-0 --auto --right-of DP-2 Floating point exception (core dumped) [ben@localhost ~]$ xrandr --output DVI-0 --auto --right-of DP-2 Floating point exception (core dumped) [ben@localhost ~]$ xrandr --output DVI-0 --off [ben@localhost ~]$ xrandr --output DVI-0 --auto --right-of DP-2 Floating point exception (core dumped) Version-Release number of selected component: xorg-x11-server-utils-7.5-16.fc18 Additional info: backtrace_rating: 4 cmdline: xrandr --output DVI-0 --auto --right-of DP-2 crash_function: preferred_mode executable: /usr/bin/xrandr kernel: 3.8.3-203.fc18.x86_64 uid: 1000 Truncated backtrace: Thread no. 1 (3 frames) #0 preferred_mode at xrandr.c:901 #1 set_output_info at xrandr.c:1172 #2 get_outputs at xrandr.c:1833
Created attachment 713326 [details] File: backtrace
Created attachment 713327 [details] File: cgroup
Created attachment 713328 [details] File: core_backtrace
Created attachment 713329 [details] File: dso_list
Created attachment 713330 [details] File: environ
Created attachment 713331 [details] File: limits
Created attachment 713332 [details] File: maps
Created attachment 713333 [details] File: open_fds
Created attachment 713334 [details] File: proc_pid_status
Created attachment 713335 [details] File: var_log_messages
Additionally, to reach the same display arrangement, the following works: [ben@localhost ~]$ xrandr --output DVI-1 --off [ben@localhost ~]$ xrandr --output DVI-0 --off [ben@localhost ~]$ xrandr --output DP-2 --off [ben@localhost ~]$ xrandr --output DP-2 --off [ben@localhost ~]$ xrandr --output DVI-1 --auto --left-of VGA2 [ben@localhost ~]$ xrandr --output LVDS2 --auto --below VGA2 [ben@localhost ~]$ xrandr --output LVDS2 --auto --below DVI-1 [ben@localhost ~]$ xrandr --output DP-2 --auto --right-of VGA2 [ben@localhost ~]$ xrandr --output DVI-0^C-auto --left-of DP-2 [ben@localhost ~]$ xrandr --output LVDS2 --off [ben@localhost ~]$ xrandr --output DVI-0 --auto --right-of DP-2 [ben@localhost ~]$ xrandr --output LVDS2 --auto --below DVI-1
cleaned up, this works: xrandr --output DVI-1 --off xrandr --output DVI-0 --off xrandr --output DP-2 --off xrandr --output DP-2 --off xrandr --output LVDS2 --off xrandr --output DVI-1 --auto --left-of VGA2 xrandr --output DP-2 --auto --right-of VGA2 xrandr --output DVI-0 --auto --right-of DP-2 xrandr --output LVDS2 --auto --below DVI-1
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. 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 WONTFIX if it remains open with a Fedora 'version' of '18'. 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 prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 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 to Fedora 18's end of life. 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 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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.
Same issue occurs on Fedora 20: 3.13.5-200.fc20.x86_64 #1 SMP Mon Feb 24 16:51:35 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux Please reopen
Package is xorg-x11-server-utils-7.7-2.fc20 xrandr --output eDP1 --auto Floating point exception (core dumped)
Same problem for me. xrandr --output DP-1-2 --auto Floating point exception (core dumped)
sorry, i forgot the configuration: xorg-x11-server-common-1.14.4-11.fc20.x86_64 xorg-x11-server-utils-7.7-6.fc20.x86_64 xorg-x11-server-Xorg-1.14.4-11.fc20.x86_64 Please reopen bug, Adriano
I hit this same issue by just running: xrandr --output VGA1 --auto using xorg-x11-server-utils-7.7-7.fc21.x86_64.
This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. 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 '21'. 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 21 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 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 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.