

Overall a fair assessment! 🤝


Overall a fair assessment! 🤝


Very much pro-Wayland in my case.
Just saying that certain CEF/Electron apps (especially those running on older Chromium version) are what is causing certain Wayland specific issues, hence my issue is on the application side (Steam, Spotify etc.), not on Wayland’s side… My bad for the badly worded post which made it seem like the classical “Wayland bad!” posts.
I haven’t touched X11/Xorg in years, nor am I planning on reverting back to it anytime.


Yeah, maybe it was just badly worded by me…
most (if not all) Wayland issues I currently have are related to Chromium, and especially CEF/Electron applications that are based on older Chromium versions. Weren’t trying to say that this is an inherent Wayland issue, considering most of the applications works as expected.


Why have a consistent Wayland experience when each application can run it’s own Electron version with varying degrees of enforced Wayland flags, and/or such an outdated Chromium version Wayland is just jank.
Edit:
Was trying to say that most of these CEF/Electron applications all need their own separate Wayland specific (Chromium) flags to have better Wayland support/integration. And the older Electron applications typically use an older Chromium as base, having even worse Wayland support… Was not trying to make this a “Wayland bad!” kind of post.
TL;DR: Electron applications have wildly varying level of Wayland support/integration, don’t have any Wayland issues other than specific CEF/Electron apps!


Biggs & Wedge!


Ohh, I don’t use their web based application… The compiler is open-source, so I just run it completely offline
Github repo for reference on how to install the compiler/CLI version


Big fan of Typst these days;
Markdown-like syntax, with LaTeX typesetting, great for technical documents at least


From what I’ve read Galaxy allows for downloading specific version of the games.
Might be misremembering, so take it with a pinch of salt
It seems it’s mostly “proper cloud saving” that’s missing relative to Heroic 🤷


Surely they’ll make a native Linux client then, right, right?!
(Meanwhile; shoutout to Heroic)


The mounting the partition with the current Kubuntu install was just to ensure that the data migration was working as-is, i.e. a sanity check.
And the ArchWiki link was more for the general concept of sharing drive between OSes, you can ignore the Windows specifics
Good luck with the setup, it should be doable :)


In general I was thinking; If you keep your steam library to a seperate partition you can easily mount that in the same matter as you would now, making the Steam migration very easy, while making your root and home partition(s) fresh otherwise
I’m not sure about migrating a single game, Steam is keeping a database (VDF-something if I recall correctly) of what you have installed, so it might get a bit confused if it suddenly only finds a single game.
If you have sufficient space on your drive(s) you could:
I think this blog covers the topic
EDIT: ArchWiki on sharing drive with Windows




Any particular reason you’re not on/tested the v590-branch? Of course it might be borked compared to 570, but might be worth a shot?


FYI:
the default, one of AMDVLK and RADV
I think that AMDVLK is shipping RADV per default now, so you might as well use RADV (for gaming, there might be other differences in OpenCL etc.), see Github/AMDVLK for more information;
In a move to streamline development and strengthen our commitment to the open-source community, AMD is unifying its Linux Vulkan driver strategy and has decided to discontinue the AMDVLK open-source project, throwing our full support behind the RADV driver as the officially supported open-source Vulkan driver for Radeon™ graphics adapters.


Why not just grab the previous PKGBUILD version that worked?


Not sure if you have the same problem or not, but I had intermittent jitter spikes (and/or complete package drops) every 60 seconds on my Realtek chipset, ran:
sudo iw dev wlan0 set power_save off
And it’s been stable since (just had to make a udev rule to make it persistent across boot)


amdvlk, any reason you’re not using the MESA driver, RADV?


… I can’t undervolt my card…
People usually use/recommend LACT for undervolting/overlocking on Linux


What is your:
Versions?
Additionally, what does the kernel logs tell you when you get a green screen?
I think that’s what Tauri is trying to do