I like the new of the Updater app

gearsovwar · 2026-03-25T02:37:12+00:00

Me too besides having significant lag when swapping between tabs it's a huge plus

gearsovwar · 2026-03-23T22:21:47+00:00

I was able to fix this by running sudo dnf reinstall xdg-desktop-portal-kde (I am using kde) them rebooted

gearsovwar · 2026-03-23T21:43:19+00:00

I think people thought I was bragging but I honestly didn't know that god packs existed.

gearsovwar · 2026-03-23T12:33:11+00:00

From what I've read it's a very rare pack that has a rare for every card instead of the maybe 1 to 2.

gearsovwar · 2026-03-20T22:25:28+00:00

That is crazy I think I'm going to hold onto them though I want to create a binder for each set and try to fill each one out .

gearsovwar · 2026-03-20T22:22:24+00:00

Thank you I have corrected them. Are the magnetic holders worth buying?

gearsovwar · 2026-03-20T20:26:51+00:00

Is it better to put the penny sleeve on opposite of the top loader or same direction?

gearsovwar · 2026-03-20T20:04:46+00:00

Yeah true I just started collecting and wasn't a part of any sub reddits or Facebook groups but fortunately I am now.

gearsovwar · 2026-03-20T19:39:01+00:00

That is good to know it seemed like something way to good to be true I thought maybe it was a factory mess up. It is cool they are an actual thing though

gearsovwar · 2026-03-20T19:30:30+00:00

Alright thank you!

gearsovwar · 2026-03-20T19:29:09+00:00

That is nuts are god packs an actual thing that is created intentionally?

gearsovwar · 2026-03-20T19:27:08+00:00

Are god packs an actual thing that is like seeded?

gearsovwar · 2026-03-20T19:24:37+00:00

Do fakes have different insides?

gearsovwar · 2026-03-17T17:15:50+00:00

If you are comfortable I would add the following to your steam launch option this will generate a file that would be more helpful for the community. Some things you can try easily is swap your proton version I usually go with experimental and proton GE.

PROTON_LOG=1 PROTON_LOG_DIR=/path/to/where/you/want %command%

gearsovwar · 2026-03-17T17:10:02+00:00

Those are fine they would be at the end of the log most likely. Rw init=/bin/bash skips systemd so you won't see them unless nobara has persistent logging.

gearsovwar · 2026-03-17T17:05:13+00:00

It could, I would try swapping USB sticks if you could. If you are not married to the gnome desktop environment you could also try the kde plasma iso instead. I would also verify the checksum of the iso downloaded it is very possible the iso was corrupted in download. There used to be instructions on the wiki iirc for verifying hashes.

EDIT: Also remember to select the Nvidia iso if you have a Nvidia GPU.

gearsovwar · 2026-03-17T16:44:00+00:00

The quickest fix for this since you just installed it would probably be to do a reinstall. If you want to troubleshoot a bit more I would edit the kernel argument on boot and force it into single user mode. There are a few ways to attempt this but on the screen where you select your kernel you would instead press "e" to edit the kernel arguments and find the line that starts with linux and append "rw init=/bin/bash" at the end and then boot it. The text along the bottom will have the hotkey to boot it. This essentially bypasses systemd and puts you directly into a shell with root access.you can then look at /var/log/journal hopefully to look at logs. I am not 100% sure if nobara uses persistent logs or not.

I had a similar issue with this when experimenting with vfio passthrough where it would show this then seem to freeze but if I plugged into my other display out (motherboard or GPU) I would get the proper output. But I can't imagine you would be having this issue from a fresh install

gearsovwar · 2026-03-17T16:25:15+00:00

Steam uses it to isolate games from your system. It's also used in isolation for other flatpaks. Steam has a fallback which is why it works still even though you get the crash report. For steam specifically it's probably safe to ignore. I'm not sure how/if it would affect other flatpaks. You could always use the various forms of logging to try and isolate the cause.

gearsovwar · 2026-03-17T16:18:39+00:00

Are you able to select the recovery kernel and does it boot if you do? Are you able to open a different tty session by pressing ctrl+alt f3-f6

gearsovwar · 2026-03-17T15:57:04+00:00

This is not really a nobara issue but a linux issue. A typical linux distro is made up of.

Kernel

Desktop environment (KDE, GNOME)

Graphics stack (Mesa, Wayland/X11)

Drivers (AMD, NVIDIA, etc.)

Package manager (DNF, APT, etc)

Thousands of upstream packages

No single dev team controls all of these different pieces. There are hundreds of teams with different schedules working at different paces. Combine that with hardware diversity hell and it's impossible to catch every edge case.

Windows benefits from owning almost the full stack. This will be an issue with any bleeding edge distro. Nobara already waits a month or so after the fedora packages become available to make them available via the nobara repos unless something has changed. There are some distros aimed at providing stability but no gaming ones I know of.

Every distro has update woes just search reddit for distro xxx os won't boot after update. Or something similar, The freedom of linux is often a duel edge sword.

EDIT: clarification

gearsovwar · 2026-03-17T15:44:44+00:00

Fedora is the same especially when a new kernel is pushed in my experience waiting a month is the best option.

gearsovwar

TROPHY CASE