If it happens, who would buy it? Amazon, M$? Much good that would do, just shift power from one giant to the next. Maybe if IBM bought it and ran it to the ground after a few years…

It is already using plasma 6 since a few weeks back, or am I miss interpreting something?

Get the token from the cookie instead of the Authorization header

It un-fucked itself thankfully, I haven’t done anything to resolve that issue. But when I ran the update today it went well with several new packages. Which means Nobara or Fedora pushed some changes to packages in the repos.

Yeah I forgot to mention that I’ll not be using dnf manually but rely on nobara-sync. But I must stress that I already did that before this issue, BUT I followed advice on nobaras own website where the solution was to use dnfand I still ended up with this problem. The real issue was still my own though, I should have upgraded to Nobara 38 before trying the workarounds, since 37 isn’t supported any more.

Yeah I kind of realised that the instructions assumed I had already upgraded, will try to keep track of new updates better in the future. So for sake of completion here’s how I solved it in the end:

• Ran upgrade from Nobara 37->38 following their guide: https://nobaraproject.org/docs/upgrade-troubleshooting/how-do-i-upgrade-to-a-new-nobara-version/
• Ran into conflicts: file /usr/lib64/libopenh264.so.2.3.1 conflicts between attempted installs of openh264-2.3.1-2.fc38.x86_64 and noopenh264-0.1.0~openh264_2.3.1-2.fc38.x86_64
• Solved it with exclusion: sudo dnf -v system-upgrade download --releasever=38 --allowerasing --exclude=openh264.x86_64
• Fonts and glitches are gone, got some broken deps instead. So if anyone got a suggestion for that instead let me know. Otherwise I’ll do as it suggest --best --allowerasing' and see what else breaks:

Problem: The operation would result in removing the following protected packages: plasma-desktop
================================================================================
 Package                 Arch   Version         Repository                 Size
================================================================================
Skipping packages with conflicts:
(add '--best --allowerasing' to command line to force their upgrade):
 kde-settings            noarch 38.2-5.fc38     nobara-baseos-38           33 k
 libkworkspace5          x86_64 5.27.8-1.fc38   nobara-baseos-38          115 k
 libkworkspace5          x86_64 5.27.9.1-3.fc38 nobara-baseos-38          115 k
 plasma-workspace-common x86_64 5.27.8-1.fc38   nobara-baseos-38           41 k
 plasma-workspace-common x86_64 5.27.9.1-3.fc38 nobara-baseos-38           40 k
 plasma-workspace-libs   x86_64 5.27.8-1.fc38   nobara-baseos-38          2.2 M
 plasma-workspace-libs   x86_64 5.27.9.1-3.fc38 nobara-baseos-38          2.2 M
 plasma-workspace-wayland
                         x86_64 5.27.8-1.fc38   nobara-baseos-38           70 k
 plasma-workspace-wayland
                         x86_64 5.27.9.1-3.fc38 nobara-baseos-38           70 k
Skipping packages with broken dependencies:
 kde-settings-plasma     noarch 38.2-5.fc38     nobara-baseos-38           13 k
 plasma-lookandfeel-fedora
                         noarch 5.27.8-1.fc38   nobara-baseos-38          403 k
 plasma-workspace        i686   5.27.8-1.fc38   nobara-baseos-multilib-38  15 M
 plasma-workspace        x86_64 5.27.8-1.fc38   nobara-baseos-38           15 M
 plasma-workspace        i686   5.27.9.1-2.fc38 nobara-baseos-multilib-38  15 M
 plasma-workspace        i686   5.27.9.1-3.fc38 nobara-baseos-multilib-38  15 M
 plasma-workspace        x86_64 5.27.9.1-3.fc38 nobara-baseos-38           15 M
 plasma-workspace-x11    x86_64 5.27.9.1-3.fc38 nobara-baseos-38           68 k
 sddm-breeze             noarch 5.27.9.1-3.fc38 nobara-baseos-38          440 k

Transaction Summary
================================================================================
Skip  18 Packages

That is helpful, I’m not sure what I’m looking for yet though. But another comment lead me into antialiasing and this line in the history seems plausible.
install -y /tmp/zenity/nobara-amdgpu-config/fedora-amdgpu-pro/packages/amdamf-pro-runtime-5.4.3-4.fc37.x86_64.rpm /tmp/zenity/nobara-amdgpu-config/fedora-amdgpu-pro/packages/amd-gpu | 2023-04-25 20:11 | I, O | 11

Undo didn’t work though:

sudo dnf history undo 11
Error: The following problems occurred while running a transaction:
Cannot find rpm nevra “amd-gpu-firmware-20230404-149.fc37.noarch”.

So I made a rollback to my last know stable point: sudo dnf history rollback 2
It didn’t exactly workout either unfortunately:

Transaction history is incomplete, before 73.
ransaction history is incomplete, before 72.
Transaction history is incomplete, after 71.
Transaction history is incomplete, before 61.
Transaction history is incomplete, after 60.
Transaction history is incomplete, before 8.
Transaction history is incomplete, before 7.
Transaction history is incomplete, after 6.
Error: The following problems occurred while running a transaction:
Cannot find rpm nevra “ImageMagick-c+±1:6.9.12.82-1.fc37.x86_64”.
… many lines more about pkgs not found

I’ll do a reboot and see what actually took effect. Atleast I’m learning something, maybe I should do all my upgrades via dnf instead of the manager in the future, easier to know whats going on.

Turning AA off for fonts solved the missing characters, downside it doesn’t look very good. I still have glitchy artefacts in some menus and the package manager doesn’t display any text for buttons which is a bit problematic. Guessing disabling some more AA settings would remove more of the problems. But it doesn’t solve my main problem - why did AA break in the first place

I pretty new to Linux gaming but I love it. Currently playing games directly from Steam and Blizzard games via Bottles. Please help me out with a few questions. What is the use case for gamescope? What is the use case for Heroic? Is it instead of Bottles/Lutris?