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.

Yeah, the Forgejo documentation was dreadful when I last looked, it really showed its origin as a Gitea replacement for people already using (and understanding) Gitea.

That’s cool. Any reason why you went with a self-hosted GitHub runner over making the full jump to a self-hosted Gitea instance + runner?

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.

All the CDLC for RS2014 work by pretending to be the DLC for “Smashing Pumpkins - Cherub Rock”, because it was given away for free as a preorder. If you get any of the other delisted DLC, you can use Rocksmith Custom Song Toolkit to change the ID to one you own (free or paid, as long as you have a steam license for it) and it should work.

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?

The usual fix from the Jellyfin docs would be to check you file naming conventions, and add the TVDB or TMDB show ID to the folder so that it scrapes it correctly, or use the Identify option like @Rudee mentioned to select a better match from the UI after import.

Both TVDB and TMDB consider Pokémon Journeys to be Season 23 of the original Pokémon show, the OMDB seems to list it as a standalone show though, so you could import and match it against that metadata.

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.

This one is edgy.

Thats great.

I’d still like my Nvidia card to work so I’m happy about this, and when AMD on Linux eventually starts swapping over to explicit sync, I’ll be happy for those users then too.

• Arch Linux announcement
• Ubuntu discourse announcement
• RedHat/Fedora security alert
• Debian security announcement