General discussion • Re: TRIXIE is released! Please comment below!

I have one RPI5 with Trixie (upgrade from Bookworm) and KDE too and I experience the same issues. It's not as often but it's not 100% safe either... at least for me so far...

I got some updates on eject just now. Have you tested if it has anything to do with our problem? I have KDE on it right now, and there it has worked for me. Most curious if it works in Raspberry Pi OS without KDE.

I just tested on 2 RPI5 after todays updates

- on RPI5 with Trixie and KDE : after 3 attempts with 2xnvme/USB3 enclosures and 2xUSB3 drives I had no errors
- on RPI5 with Trixie and PiXEL : more feedback is welcome from more people. So far, here's what I noticed (with same nvme and usb3 drives as with KDE):

- automount feature for nvme in USB3 enclosures is broken. It simply no longer works ! (manual mount with udisksctl works fine) (no they're not ext4 !)
- automount feature for USB2 drives works fine. Eject safely works. Same situation as before.
- automount feature for USB3 drives works fine. Eject with pcmanFM or wfpanel still produce errors... Ejecting manually with udisksctl works fine
- after manual mount of nvme in USB3 enclosures with udisksctl, eject with pcmanFM or wfpanel still produce errors... Ejecting manually with udisksctl works fine

I'd say it's worse with the loss of automount and I could not see any improvement with the safely remove feature...

You can make your tests safely. Even if you have errors like the screencap below, just do :

Code:

lsblk> you see your devices and potential mountpointsif partitions are mounted doudisksctl unmount -b /dev/sdXNnow you can eject properly and safelyudisksctl power-off -b /dev/sdX

Here's the error we experience
eject-error.png

Statistics: Posted by Olydnad_SWE — Mon Oct 20, 2025 11:37 pm