Main character syndrome.

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?

every time I got lost in the ship builder, I’d spend an hour on some crazy design, be a piece away from saving it, and the game would just lock up and stop responding to input. Only ever happened in ship builder. I lost like 4 hours to that flippin’ bug!

I found Fallout 4 had good gameplay, but the main questline didn’t connect with me at all. I’m currently playing through Starfield at the moment, have like 220 hours playtime, I honestly wish I wasn’t finding it so boring but it’s easily the most bland Bethesda game I’ve ever played.

The story writing seems kinda half-arsed, but my main issue with Starfield is in the environments. Every location feels the same, and the planets are all just barren deserts with a random base and two caves plopped on it. At least Fallout 4’s environment felt hand-crafted, and not just like they rolled three dice.

What part of it do you connect with most?

Now try Starfield.

You’ll find it so shallow that Fallout 4 seems like the Mariana Trench.

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.

Yeah, this is probably what OP noticed.

Adwaita Sans is a tweaked version of Inter (the main change was to make lowercase I and L look less similar, IIRC) and then Adwaita Mono is basically Iosevka tweaked to match with Inter.

I use Tauon Music Box on Linux, I think it’s pretty decent, but it is kinda playlist focused.

Maybe Linux just isn’t for you, and that’s okay. Go use Windows or Mac and enjoy your “just works” setup and lack of involuntary learning.

I don’t think you could go wrong for a tenner, I loved that game from start to finish. I watched all of the DoubleFine PsychOdyssey dev diary about making it afterward too, very enjoyable.

I think with a self-hosted mastodon instance, the main downside is poorer discovery across the fediverse as a whole.

When you scale up to the thousands of users something like mastodon.social has, it’s not really an issue because other users have already established connections between instances by following or replying… but if your instance only has a single user, you only see and share posts with the instances you’ve directly interacted with, and it can be really isolating. You have to already know what external accounts you want to follow, because your instance is initially blind to them.

I feel like more instance connections leads to way larger amounts of data consumption too. I follow 120, and am followed by 12… my instance is currently using 24.1 GB for Media Storage.

What I feel would be acceptable:

If you’re proud of your Framework laptop and want to brag about it, we’ll give you some swag for free that you can show off with when you’re out and about!

What this looked like to me:

If you’re attending a conference we’d be paid to attend, but can’t go to, will you show off your Framework laptop to attendees in an effort to convince them to buy one from us too, and we’ll send you some stickers?

The issue isn’t even what they’re asking for, but how their asking it.

When I last had an everyday carry USB stick (5+ years ago) I found I never actually used it for anything.

I had Ventoy and some practical ISOs, and PortableApps with a bunch of useful software (firefox, foobar2000, GIMP, notepad++…) for when I was using someone else’s Windows PC.

…think I stored like two word documents on it, ever.

did you find any solution for this?

I think we Fedora users just have to wait for RPMFusion to roll out the updated driver. Not entirely sure if they only use Stable branch drivers or not though. I’m used to Arch where it would just be in the AUR within the hour…

I’ve been refreshing half the uBlue repos a lot today in the hopes there’s some commits showing they’re rolling the drivers out for Bluefin quickly 😂

• For what I assume is a security precaution, SysRq is disabled by default in Fedora, and you need to go enable it if you want to be able to recover when shit like this happens - the link shows how, and explains what each letter does.
• It’s honestly hard to say what caused it, but you could check your system logs and see what looks suspicious around the time of the crash. journalctl, dmesg and your steam logs (in ~/.steam/steam/logs usually) could be worth a look, or worth showing someone else at least if you aren’t sure whats going on in there.
• I’d avoid actively trying to cause it, but if it happens again you handled it exactly how I’d try handle it. Having SysRq enabled would let r-e-i-s-u-b handle it more gracefully than a forced shutdown at least!

Regardless of what distro you do end up using, the Arch Wiki is a great bookmark to have. The info is like 90% relevant to Linux in general, and at worst you might need to figure out what a file path or package might have changed to in the likes of Ubuntu or Fedora.

and a Nvidia 2080ti

Do you know which Nvidia driver you’re using currently?

There’s an established open-source Nouveau driver that Ubuntu & Mint probably defaulted to, a bleeding-edge open-source NVK driver that is still very early in it’s development, and a proprietary Nvidia driver that Nobara probably tried, as it’s kinda what you’d want for gaming.

The other question would be if you’re using Wayland or X11 underneath your desktop environment?

It should be listed in Settings > System > System Details, under the heading “Windowing System” if you’re using GNOME.

Wayland has better multi-monitor support than X11, but the proprietary Nvidia driver has a few teething problems with Wayland at the moment - a new 555 beta driver update should be coming this week with proper fixes for the sync/screen-tearing issues people have been experiencing.