Ghoelian

Just fyi, that is not Fedora workstation, thats a Fedora atomic spin, which is an immutable os. Installing packages and updating works a bit different than a normal distro.

The bootloader thing doesn’t happen anymore with UEFI I believe. Each os has its own boot partition now.

All windows can do is make itself the first boot option, which you’d have to reverse in your bios.

+1 for ventoy. With that you can just flash ventoy on it once, then copy iso’s over to the usb drive without reformatting or reflashing anything.

Yeah just wish it would show the verified status in the cli, that’s the only reason I still go to the website

That is also a form of basic auth, you still pass the credentials like “username:password”, optionally base64 encoded but I don’t believe that’s required.

Edit: actually, after looking into it a bit more, it seems like passing credentials in the url will actually cause the browser to send it as an authorization header instead. So in essence it’s doing the same thing.

I think they’re talking about basic Auth, with which you can pass credentials in a URL like this:

https://username:password@website.com

Have you tested if hardware acceleration even works at all? On my Fedora install, whenever I try the latest 545 driver, it just doesn’t work. glxinfo just returns an error, insufficient resources.

535 still works great for me though.

Does this apply to Proton as well, or have they had their own fixes for Vulkan or something? Cause I’ve been playing games on Wayland with Proton just fine for a good while now.

Also, when you choose either of the update or restart/shutdown options, it actually tries to restart, (for me) always boots back into linux because that’s my default. When I’d eventually boot back into Windows, it just continues installing the update I’d long forgotten about.

Pretty happy to be rid of that mess entirely now.

Are you using Wayland with KDE? For me the taskbar freezes if I’m on Wayland and hover over some windows so it shows the preview.

If you’re also using Wayland, try turning off window previews (right-click taskbar->configure->Show small window previews).

Also, as a workaround if this doesn’t fix it for you, you can execute plasmashell --replace and it’ll replace the existing frozen instances instead of starting new ones. If you use krunner (alt+space) it’ll stay in your recent commands as well, so you can easily run it again when it freezes again.

I’m pretty sure KDE’s window manager, kwin, can do all of those things through kwin scripts and window rules, except the pager doesn’t show the details of windows on other desktops, just the outline.

I have a magic trackpad 2 (maybe 3, not sure) and haven’t noticed any lagging issues. I mainly use it wired, but the times I did use it wirelessly I didn’t notice any lag either.

Unfortunately I didn’t have gestures ootb, though that could be a KDE plasma thing, since they have touchpad gestures like two finger scroll and tap to click disabled by default as well.

Setting up gestures using touchegg was easy enough though.

Yup, that’s my coworkers as well. Constantly complaining about how removed windows is, already developing in docker on wsl anyway, but they never want to switch to anything that would solve all their complaints.

Not trying to defend windows or anything, but

Fast boot/reboot times (less than 10 minutes)

What? In my experience, nowadays Linux is probably still a bit faster than windows in boot times, but that’s comparing 20 seconds to like 30 seconds. Nowhere near 10 minutes.

How did you deal with scaling with 2 different resolutions on X? I never managed to get it working quite properly, the closest I got was running some xrandr scale commands on login.

The other sections are different actions that appear in the context menu of the steam desktop icon, so that you can launch steam straight into big picture for example. If you just launch steam, just the [Desktop Entry] section will execute.

While in my experience the answer you replied to works, to get the same behavior as what you got in the terminal, you should edit the exec line to something like steam --forcedesktopscaling=2 %u.

If you use the separate actions, you should edit it there as well, but those won’t have any effect on just launching steam.

Yeah that’s why I don’t use discover to do the actual updating. I just manually run my flatpak updates when discover tells me there are some.

This is why I really like KDE Plasma’s discover. It’s got integrations with apt, snap, Flatpack, and rpm, and that’s only the ones I’ve tried so far.

I don’t really use discover itself to manage my packages, cause for some reason I prefer to do it with the cli tools, but it is a great update notifier.