--pos is not always applied correctly about autorandr HOT 7 OPEN

It's still not working for me without patching xrandr or manually setting crtc. I've submitted the patch here if anyone wants to test it on their system.

from autorandr.

I think I'm running into this issue. I have 2 profiles setup when docked at work, one that uses the built-in monitor of the laptop along with 2 other monitors and another that swaps the built-in monitor out for a display hooked into my hdmi port.

When I load the config using the hdmi, everything has the correct layout. When I load the config with the builtin screen it loads that screen in a weird location that overlaps my other two monitors.

Is there a workaround for this or something I could look into fixing? Or is it a bug with xrandr itself?

from autorandr.

I just tested running the command to switch to the new layout 2x and that seems to work.

from autorandr.

This is a bug in xrandr. I'm using the same workaround - but haven't brought myself to integrating it into autorandr yet, because I don't know how specific the issue is. (What graphics card are you using? If it's not an Intel HD card of the Haswell generation, then we do at least have two affected cards..)

from autorandr.

Another workaround I've found is manually setting the --crtc switch for each output. In my case autorandr (using xrandr) sets the monitors correctly the first time when starting X but if I switch profiles and switch back it doesn't work.

from autorandr.

I've had this issue of overlapping outputs in the past. I have an NVIDIA Quadro 2000M and it occurred on both Arch Linux and FreeBSD.

I've had to use workarounds before but I recently retried using a single invocation of autorandr --change. And now that's working just fine for me.

My machine is a notebook and I have two external monitors connected. I had assumed that the problem was that my video card only supported driving two outputs at the same time. And while I wanted to turn the notebook's display off and only use the two external monitors xrandr (or autorandr) tried to apply the appropriate configuration to all three outputs at the same time, leading to an error. If I configured each output with a separate invocation of xrandr I was able to get to configuration I wanted. But autorandr didn't support that at the time.

But as I said the problem is gone now for me. I don't know if something in xrandr, autorandr or the proprietary NVIDIA driver changed, but I'm glad it's working now out of the box.

Version information for my machine where it's currently working:

$ pkg query %v py27-autorandr
1.3.p1
$ xrandr --version
xrandr program version       1.5.0
Server reports RandR version 1.5
% pkg query %n-%v libX11 libXrandr nvidia-driver xorg-server
libX11-1.6.5,1
libXrandr-1.5.1
nvidia-driver-384.90
xorg-server-1.18.4_6,1
$ freebsd-version
11.1-RELEASE-p6

Maybe it's working for others now as well?

from autorandr.

I've tried the patch from @Quuz in the hope that it would fix my issue, which is basically that autorandr vertical does not work (xrandr --output eDP-1 --mode 1920x1080 --pos 0x0 --output DP-2-2 --mode 2560x1440 --pos 0x1080 fails), but no luck.
It is likely another issue, will have to investigate. It is not related to autorandr really, since it also fails to setup this correctly using arandr.
Linux 4.14.9-1-ARCH, Lenovo X250 (Intel graphics).

from autorandr.