Issue when disabling screen in settings (Position of output %s is negative)

Hello everyone,

Since my last update last week end, I have a weird behavior in the display settings. For a bit of context, I have a three screen set up (one internal laptop display and two external one) and I use endeavor OS.

Sometime, I need to disable every display except one (to be sure to have a game in fullscreen on the right screen).

Before the update, I didn’t had to think about the position of the screens according to others. I was able do only keep activate the middle screen without editing screen arrangement (where each screen is depending to each other).

Now, I need to put the screen that I want to keep activate at position 0,0 (so it’s the first screen). If I don’t, the configuration can’t be applied because other screen get a negative position which is not supported according to the error message.

I’m not sure if it’s a KDE plasma so before posting an issue on bugzilla I prefer to ask see if other people encounter the same issue as me.

2 Likes

I have a very similar issue. Trying to remove one of my display is displaying an error message:
”Couldn’t apply display configuration: Position of output HDMI-A-1 is negative, that is not supported” HDMI-A-1 being the monitor I am trying to remove.

1 Like

I am having this exact same issue. Worked just fine until about a week ago. I have almost the exact same setup as well. I have three monitors (two side by side and one below) and if I try to disable the top two I get the message “Couldn’t apply display configuration: Position of output DP-1 is negative, that is not supported”.

I am unable to disable the display no matter what arrangement or priority I put the screens in so I am resorting to unplugging the displays when I need to disable them which is really annoying.

@DropNDrag when you say you put the active one at position 0,0, are you changing the arrangement AND the priority? Just curious how you are getting the enable/disable to work still. I would like to still use that over disconnecting my monitors if I can.

1 Like

I don’t change the priority of the screen. My set up is :

Built-in screen | Monitor 1 (primary) | Monitor 2

When I want to disable ‘Built-in screen’, I specify the following screen configuration :

Monitor 1 (enable) | Monitor 2 (enable) | Built-in screen (disable).

In this case, the relative position of ‘Built-in screen’ is not negative since 0,0 is Monitor 1.

Even if I setup my monitors like that in the screen configuration I still get the error and I am unable to disable any of the screens.

In my case is not possible disable the monitor if is on position 0,0.

I am on Cachyos OS with KDE 6.6.5, I was able to disable my left monitor ( setup at 90 degree) until few weeks ago, now I receive the message :

Couldn’t apply display configuration: Position of output DP-2 is negative, that is not supported

Also some game will launch on the left screen and of course are 90 degree, with some I can change to the windows, move to the primary, enlarge and get the game ok ( need to pretty much do all the time). They maybe looking for position 0,0 and they launch on that monitor.

The workaround for it, is to move the left screen on KDE monitor, on the right side, doing that my center monitor became 0,0 and the games working and I can also disable the screen if I want, this create a small issue ( I need to move the cursor from center to right side and move the windows on the right side too).

I tried xrandr --output DP-1 --primary but is not doing anything in my case.

My monitors are HDMI and I use the HDMI port with HDMI 1.4 and the DP port with a DP-HDMI cable, and I also have a and adapter DP-HDMI, so I tried all the ports, but this is not change the situation.

So my question is: it is a new bug as it was working before?

Any workaround to tell the system when i go on the left side of the screen to go on left even if the config is on the right?

Thank you.

Yes. I added some safety checks in KWin, as the display settings had a bug that in rare cases put screens at insane positions (like -2 billion) that caused rendering errors.

As it turns out, sometimes it also puts disabled screens at more sensible negative positions for good reasons, so the checks had to be relaxed a bit. I’ll email distros to backport that fix.

2 Likes

Thank you, @Zamundaaa , really appreciate.