Version-Release number of selected component: arandr-0.1.7.1-3.fc20 Additional info: reporter: libreport-2.2.2 cmdline: /usr/bin/python /usr/bin/arandr executable: /usr/bin/arandr kernel: 3.14.3-200.fc20.x86_64 runlevel: N 5 type: Python uid: 1000 Truncated backtrace: xrandr.py:108:_load_from_commandlineargs:FileLoadError: Not a known mode: 1680x1050 Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/screenlayout/gui.py", line 64, in wrapper return function(*args_out) File "/usr/lib/python2.7/site-packages/screenlayout/gui.py", line 235, in do_open self.filetemplate = self.widget.load_from_file(f) File "/usr/lib/python2.7/site-packages/screenlayout/widget.py", line 88, in load_from_file template = self._xrandr.load_from_string(data) File "/usr/lib/python2.7/site-packages/screenlayout/xrandr.py", line 79, in load_from_string self._load_from_commandlineargs(lines[xrandrlines[0]].strip()) File "/usr/lib/python2.7/site-packages/screenlayout/xrandr.py", line 108, in _load_from_commandlineargs raise FileLoadError("Not a known mode: %s"%p[1]) FileLoadError: Not a known mode: 1680x1050 Local variables in innermost frame: on: 'VGA1' i: 2 commandline: 'xrandr --output DP3 --off --output DP2 --off --output DP1 --off --output HDMI3 --off --output HDMI2 --off --output HDMI1 --off --output LVDS1 --mode 1440x900 --pos 1680x0 --rotate normal --output VGA1 --mode 1680x1050 --pos 0x0 --rotate normal' args: ['--output', 'DP3', '--off', '--output', 'DP2', '--off', '--output', 'DP1', '--off', '--output', 'HDMI3', '--off', '--output', 'HDMI2', '--off', '--output', 'HDMI1', '--off', '--output', 'LVDS1', '--mode', '1440x900', '--pos', '1680x0', '--rotate', 'normal', '--output', 'VGA1', '--mode', '1680x1050', '--pos', '0x0', '--rotate', 'normal'] o: <screenlayout.xrandr.OutputConfiguration object at 0x1ce9610> self: <screenlayout.xrandr.XRandR object at 0x1cdff10> p: ('--mode', '1680x1050') parts: [('--mode', '1680x1050'), ('--pos', '0x0'), ('--rotate', 'normal')] oa: ['--mode', '1680x1050', '--pos', '0x0', '--rotate', 'normal'] os: <Output 'VGA1' (0 modes)> options: {'DP3': ['--off'], 'DP2': ['--off'], 'DP1': ['--off'], 'HDMI3': ['--off'], 'HDMI2': ['--off'], 'HDMI1': ['--off'], 'LVDS1': ['--mode', '1440x900', '--pos', '1680x0', '--rotate', 'normal'], 'VGA1': ['--mode', '1680x1050', '--pos', '0x0', '--rotate', 'normal']} namedmode: <screenlayout.auxiliary.NamedSize object at 0x1ce9310>
Created attachment 903061 [details] File: backtrace
Created attachment 903062 [details] File: environ
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. 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 '20'. 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 20 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 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.