I definitely mis-read that as IKEA on first glance.

There’s a “US Gov protecting fossils” joke in there somewhere but I don’t really want to kick that hornets nest.

They were limiting their own production to raise demand and keep the price high, but then realized their competitors were benefiting from selling at those higher prices… so now they’re going to raise their own production and try undercut competitors on prices. They have the capacity to out-produce their competition, so they can afford to sell for slightly less than competitors if they want to, hence the "long and shallow” price war quote.

They are against low prices, but if anyone is buying low they want to be the one selling it.

I’ve had no issues with Dash to Dock, this looks more like an ArcMenu issue to me based on your screenshot.

In the description for ArcMenu they say:

Requires GMenu package:

• Depending on your distro you may need to install ‘gir1.2-gmenu-3.0’, ‘gnome-menus’, or ‘libgnome-menu-3-0’

Have you got that dependency covered?

What other extensions do you have installed? What versions of Ubuntu and GNOME are you using?

I’m not doing this for approval.

Okay. Go away and do it then.

My monitors.xml has two <configuration> blocks, with the only real difference being that one has <layoutmode>physical</layoutmode> and the second has <layoutmode>logical</layoutmode>. I don’t really think that’d be the issue here though, because if the dummy plug is listed as disabled it shouldn’t be trying to use it anyway…?

I think you’re right in reporting it to the GDM repo, at a minimum someone there will know where to point you towards figuring this out. Maybe the GNOME Mutter repo might be a related stop for this too, seeing that’s the part generating the monitors.xml…

The things that are supposed to be simple are always the bits that suck the most!

Yeah, seems like it should just be working…

You’ve probably already got this covered, but when you created your user monitors.xml config, did you have the dummy plug connected and disabled?

Maybe the config:

• has it included as a monitor and enabled as part of the screen layout
• or possibly doesn’t include it at all, and then GDM just assumes it can/should use it as a new option?

When you copy over your monitor config, are you correcting the ownership/permissions?

The little scriptlet I made to combat a previous nvidia/wayland multi-monitor headache boils down to:

sudo cp $HOME/.config/monitors.xml /var/lib/gdm/.config/
sudo chown gdm:gdm /var/lib/gdm/.config/monitors.xml

Maybe double check if GDM is ignoring wayland as well, I’ve definitely had that happen in the past too.