autorandr
autorandr copied to clipboard
xorg-server 1.20.6 will break script
I have recently patched xorg-server with newest patches and after that autorandr stopped working. Xorg-server truncated devices names from e.g. HDMI-1-1 to HMDI-1. After that all exisitng configuration files and actual autorandr script is broken.
Failed to load profiles (line 394):
Failed to find an EDID for output `eDP-1' in setup file, required as `eDP-1' is not off in config file. (line 394)
It would be nice to consider change in parsing these names to be less restrictive or compatible with multiple versions of device naming.
I would like to add something which might be related. I am on a Thinkpad W530. This device offers the following modes in BIOS:
- intel only (nvidia disabled) with only VGA port enabled
- NVIDIA only with additional digital outputs
- optimus for the bbswitch and so on solutions
In each of this mode, xrandr reports different names for both the LVDS and the external outputs. Maybe it's a good idea to implement aliases like:
DP DP-1 DP-1-1
VGA VGA-1 VGA-1-1
LVDS LVDS-1 LVDS-1-1
so that autorandr treats all outputs with the names DP-1 and DP-1-1 as the same device with the alias DP
What heuristic would you suggest?
There's users connecting monitors to more than a single display-port (DP), and DP also supports daisy-chaining. So systems with DP1-1-8 or the like do exist. (See also)
I was not thinking about any automation / heuristic. More like giving the user the option to define aliases in his config.
But that wouldn't solve the original issue. It'd help in your case though. (Do you actually frequently change this configuration in your BIOS, or is this more of an academical question?) What behaviour would you expect if xrandr reports both a device and its alias to exist?
Is there any proper explanation about those naming schemes? It feels like the outputs are renamed every time I restart X. Its a little bit like the new non-persistent network device names. Why can't my VGA port always be VGA-1 and my laptop panel LVDS-1. There is no other panel and there will never be.... I know, this does not really belong here, but I would like to understand.
But that wouldn't solve the original issue.
Do not agree. @JDuchniewicz could define the alias HDMI-1 HDMI-1-1 and his autorandr should be immune against this weird renaming...
Is there any proper explanation about those naming schemes?
The only I'm aware of is the Kernel doc linked above. I tried to find one, too, to give a better response than I gave above. If we'd know the exact rules, then coming up with code to automate the aliasing (properly, without breaking other users' workflows) would be possible.
Do not agree. @JDuchniewicz could define the alias HDMI-1 HDMI-1-1 and his autorandr should be immune against this weird renaming...
I don't think he's interested in being able to switch back and forth between different xorg versions. The issue was about autorandr automatically updating the configuration from the old to the new names. If you have to manually define aliases for a one-off change, then you could just as well rename the old names and be done with it..
Ok, then I apologize for contributing non helpful things. For me it seems like this could solve some more general problems. Still I don't understand at all why my computer renames outputs based on what driver or X version I am using. This does not make any sense to me and I tried to work around this. I am sure, you will find a proper solution for the OP problem.