Phillip Berndt

Sorry it took me a while to respond. If this is still an issue: Apparently you have a manually configured mode that is added using xrandr's `--addmode` command. Try doing...

Could you post the `config` file of the `xxxx` profile, please? (Or, alternatively, add a `print(self.options)` before line 233 and post what it prints, in particular for the `pos` key.)

Hm, with your xrandr output, I get the configuration ``` output eDP1 mode 1600x900 pos 0x0 primary rate 60.00 ``` Note the different `mode` and `pos` lines. Obviously something went...

Do I get that right, b-menu generates autorandr profiles?

I'm very reluctant to start a blacklist. Maintaining a list of supplications to blacklist sounds like it won't scale and maintaining a list of blocked displays doesn't cover nested x...

I haven't moved to Wayland yet because it lacks support for Nvidia graphics cards and even if it did support them it still also lacks _many_ features I regularly use....

There's use cases where people don't want to switch on disabled outputs, and for them this creates flickering. That makes this an undesired solution, unfortunately. I personally worked around this...

Curious: What happens if you _only_ enable the output that didn't work using `xrandr --output foo --auto`? What happens if you only `-q`?

> This does not appear to be reflected in the output of xrandr -q --verbose. Couldn't we extract this from the first line (it states effective resolution and physical device...

[I just tried](https://gist.github.com/phillipberndt/32cf4e75a8214f90a8ab). No, that doesn't work, and that it doesn't makes a lot of sense, too, now that I've come to think about it.. What xrandr displays is per-output...