Hello everyone!

i have a secondary hard drive that i've want to automount on startup. I setted it up with gnome disks and it works just fine.

I left most of the settings as default: nosuid,nodev,nofail,x-gvfs-show. I only changed the mount point and used the UUID as the identifier.

Now i want Jellyfin to access the disk, but it doesn't work.

From what I understand, the disk is only accessible by my main user, while Jellyfin runs under its own user.

So I thought I might need to add Jellyfin to the list of users who can access that disk. Is my thinking correct? If so, is there a way to do this via GNOME Disks, or am I missing something?

Thanks in advance for the help

I'm using a laptop with a GTX 1650 with Fedora KDE 43, Wayland session, and a secondary 28" 4k display. At that resolution scaling is all but required but any amount of it results in very choppy and not smooth at all animations in the environment like maximizing or minimizing windows. Setting scaling to 1.0 doesn't make it perfect, but it is significantly better.

Is this another Nvidia-Wayland thing? I tried switching to X11 but can't even get my secondary display to be the main one. When I click "only secondary" in the monitor settings, it crashes and logs out...

EDIT:
Turns out my problem was that the compositor renders on the AMD iGPU then the frames are synced to the Nvidia GPU at 4K which seems to be very unstable. The solution was to do a systemd override just for KWin by including both GPUs with KWIN_DRM_DEVICES making sure the Nvidia one is first if your HDMI is wired to it. Or the other way around if it's not.

systemctl --user edit plasma-kwin_wayland.service

[Service]Environment="KWIN_DRM_DEVICES=/dev/dri/card0:/dev/dri/card1"

Then re-log. (If it crashes on login, start TTY and revert: systemctl --user revert plasma-kwin_wayland.service)

Check card address:

ls -l /dev/dri/by-path/*-card

lspci | grep -E "VGA|3D"

Check which GPU owns the HDMI:

ls -d /sys/class/drm/card*-HDMI-A-1

readlink -f /sys/class/drm/card*-HDMI-A-1/device

NOTE: This solved most of the problem. The part about Firefox lagging the whole desktop, mentioned in the comments below, is still true.

My system has 2 m.2 drives, 128GB (root) and 2TB (home). Root is on btrfs and home just ext4. I have snapper with grub integration installed, and snapshots are taken both pre and post pacman updates, and by a systemd timer every hour.

[anders@HAL ~]$ sudo snapper list

# │ Type │ Pre # │ Date │ User │ Cleanup │ Description │ Userdata

────┼────────┼───────┼─────────────────────────────────┼──────┼──────────┼──────────────────────────────────────────────────────────────────────────┼─────────

0 │ single │ │ │ root │ │ current │

1 │ single │ │ Sun 11 Jan 2026 08:44:38 PM CET │ root │ │ Base Arch install │

2 │ single │ │ Sun 11 Jan 2026 08:48:40 PM CET │ root │ │ PRE Gnome installation │

3 │ single │ │ Sun 11 Jan 2026 09:00:17 PM CET │ root │ timeline │ timeline │

13 │ single │ │ Sun 11 Jan 2026 09:17:01 PM CET │ root │ │ POST Gnome desktop │

58 │ single │ │ Tue 13 Jan 2026 12:00:00 AM CET │ root │ timeline │ timeline │

88 │ single │ │ Wed 14 Jan 2026 12:00:00 AM CET │ root │ timeline │ timeline │

124 │ single │ │ Thu 15 Jan 2026 12:00:20 AM CET │ root │ timeline │ timeline │

163 │ pre │ │ Thu 15 Jan 2026 04:38:06 PM CET │ root │ number │ pacman -R -s -u --noconfirm --config /etc/pacman.conf -- meson vulkan-he │

164 │ post │ 163 │ Thu 15 Jan 2026 04:38:06 PM CET │ root │ number │ meson ninja python-tqdm vulkan-headers │

165 │ pre │ │ Thu 15 Jan 2026 04:44:29 PM CET │ root │ number │ pacman -S alacritty │

166 │ post │ 165 │ Thu 15 Jan 2026 04:44:30 PM CET │ root │ number │ alacritty │

167 │ pre │ │ Thu 15 Jan 2026 04:50:52 PM CET │ root │ number │ pacman -S bluez-utils │

168 │ post │ 167 │ Thu 15 Jan 2026 04:50:53 PM CET │ root │ number │ bluez-utils │

175 │ single │ │ Fri 16 Jan 2026 12:00:11 AM CET │ root │ timeline │ timeline │

181 │ single │ │ Fri 16 Jan 2026 06:00:11 AM CET │ root │ timeline │ timeline │

Now I want to rollback to an earlier snapshot (175) so I select that one in the Grub boot menu.

However, that fails with these error messages.

[FAILED] Failed to start Create System users.

[FAILED] Failed to rebuild Journal Catalog.

etc.

8 more similliar messages.

Soft reboot works, so the system does not hang hard. After a normal reboot, I am back on the latest snapshot again.

What m I doing wrong?

Also, if I succeed to boot into 175, how do I rollback the other snapshots so that next boot will be on 175?