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.

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

It’s not gonna stop Google’s internal processes from deciding to pick complete BS results, and you’d definitely be ignoring new genuine content too, but as long as your not looking for results on something time sensitive it would tune out a lot of the AI generated noise out there from the crazy rise in ChatGPT content-farmed articles.

I seen a post on mastodon yesterday that said if you’re using google to search for anything, the trick to getting useful results is to include before:2023 and ignore anything newer because it’s probably just AI generated/prioritized BS.

I don’t think they were entirely wrong in thinking that, tbh.

I tried both Lidarr and Beets before, but their automation tended to pick matches with a “eh, close enough” attitude, so I just decided I’d do it properly myself.

I tag metadata on everything with MusicBrainz Picard, and then store it in a /{Album Artist}/{Album}/{Track} hierarchy.