The only thing I see they did wrong was to disclose the vulnerability before waiting for a comment from the software company.
xinayder
joined 2 years ago
My only issue with the latest update is that the app doesn't start minimized by default. Otherwise, I really like the program!
I had a similar issue with my laptop, where Arch wouldn't be recognized as a bootable system on my NVMe drive unless I disabled RST with Optane on the BIOS, setting it to AHCI mode.
I do remember seeing a similar issue a while ago as well, but I don't remember if the user managed to fix it.
I could suggest removing the Windows drive, installing Arch and checking if everything works, then plugging the Windows drive back in. Windows loves to delete non-Windoes bootloaders from every drive it can.
The same issue happens to me when opening links from any app on Wayland. For example, every time I click a link on a Discord chat, I have to manually click on the Firefox window because the focus is not automatic.
I run Wayland and it's definitely worse than X11, but it's getting better day by day. I always struggle with Wayland and I literally did nothing different than installing KDE Wayland. For example, ever since I moved to Wayland, Firefox will randomly freeze and crash when I'm using my PC - this happens at least once per gaming session.
Also, Wayland is still not feature complete and assuming it's the system fault for poor compatibility is wrong.
Just give arewewaylandyet.com a read.
I'd recommend Forgejo/Gitea as others have mentioned or https://sourcehut.org (instance available at https://sr.ht/)
Which changes, care to elaborate?
This is something being sold in favor of passkeys but I can't ser how "more secure" it is for me.
I use Bitwarden, the domain name matching works exactly like passkey's. How more secure a passkey is, if it has 0 changes to this domain name detection?
Did you use SDL_VIDEODRIVER or SDL_VIDEO_DRIVER? The former one is the old parameter and the latter works. I am using it right now on a Wayland session.
There's a GitHub issue tracking this bug. It seems like SDL3 was finally released and Valve "forgot" to compile SDL3 with Wayland support.
If you're using Wayland, you can add a startup parameter to force the game to use X11 and it will work.
This issue is also affecting Dota 2.
I stopped reading when I read "Electron".
I used Heroic a few times and it's absolute garbage because it runs Electron.
They said they will offer these 2 versions side-by-side, but mark my words, a few months/years they will go with the Electron version and kill the GTK version.
I tried changing the graphics settings on my mid-range PC and they barely make any difference. You can tune FSR to the max but I don't think there will be much notable difference in performance.