dwam wrote: ↑

Sun Oct 19, 2025 3:56 pm

Olydnad_SWE wrote: ↑

Sun Oct 19, 2025 1:27 pm

I've tested in Raspberry Pi OS with KDE Plasma installed on Trixie with: sudo apt install kde-plasma-desktop and everything works fine.

So I guess it's a bug-like thing with Raspberry Pi OS as it works if you just put KDE on it. I like both Raspberry Pi OS and KDE Plasma as a desktop environment. Luckily, KDE Plasma doesn't come with too many unnecessary programs as I'm minimalist.

I know there are several ways to eject a USB disk. But I want it easy and it should always work in my opinion.

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...

Olydnad_SWE wrote: ↑

Mon Oct 20, 2025 3:45 pm

dwam wrote: ↑

Sun Oct 19, 2025 3:56 pm

Olydnad_SWE wrote: ↑

Sun Oct 19, 2025 1:27 pm

I've tested in Raspberry Pi OS with KDE Plasma installed on Trixie with: sudo apt install kde-plasma-desktop and everything works fine.

So I guess it's a bug-like thing with Raspberry Pi OS as it works if you just put KDE on it. I like both Raspberry Pi OS and KDE Plasma as a desktop environment. Luckily, KDE Plasma doesn't come with too many unnecessary programs as I'm minimalist.

I know there are several ways to eject a USB disk. But I want it easy and it should always work in my opinion.

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.

lsblk
> you see your devices and potential mountpoints
if partitions are mounted do
udisksctl unmount -b /dev/sdXN
now you can eject properly and safely
udisksctl power-off -b /dev/sdX

dwam wrote: ↑

Mon Oct 20, 2025 5:57 pm

Olydnad_SWE wrote: ↑

Mon Oct 20, 2025 3:45 pm

dwam wrote: ↑

Sun Oct 19, 2025 3:56 pm

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: Select all

lsblk
> you see your devices and potential mountpoints
if partitions are mounted do
udisksctl unmount -b /dev/sdXN
now you can eject properly and safely
udisksctl power-off -b /dev/sdX

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

Olydnad_SWE wrote: ↑

Mon Oct 20, 2025 11:37 pm

Thanks for testing. I'll stay on KDE for now, as it works for me. I need to have a stable environment to work with.
I have started to work more and more with Raspberry Pi as they are powerful enough most of the time. What worries me is if I get any update that breaks KDE since it is not supported on Raspberry Pi OS.
And yes, I have backups. The thing is that I don't dare to use them as it doesn't work as it should. But with KDE, it seems to work.
Maybe we should open up a new thread about that?

andrew_pi wrote: ↑

Tue Oct 21, 2025 6:11 am

There is a whole forum section dedicated to Raspberry Pi OS which is actively used to discuss such matter.

dwam wrote: ↑

Tue Oct 21, 2025 7:07 am

andrew_pi wrote: ↑

Tue Oct 21, 2025 6:11 am

There is a whole forum section dedicated to Raspberry Pi OS which is actively used to discuss such matter.

I know
However this issue was initially reported while beta testing pre release Trixie upgrades, then the RC version and finally here again when the final version was released and this thread's title indicates clearly we're here to report issues

andrew_pi wrote: ↑

Tue Oct 21, 2025 3:07 pm

dwam wrote: ↑

Tue Oct 21, 2025 7:07 am

andrew_pi wrote: ↑

Tue Oct 21, 2025 6:11 am

There is a whole forum section dedicated to Raspberry Pi OS which is actively used to discuss such matter.

I know
However this issue was initially reported while beta testing pre release Trixie upgrades, then the RC version and finally here again when the final version was released and this thread's title indicates clearly we're here to report issues

Report issues, yes in the first instance. But to-and-fro exchanges to get to the bottom of the issue deserve their own threads.

andrew_pi wrote: ↑

Thu Oct 02, 2025 9:16 am

First time I've used the network install, took just 3 minutes!

First thing to report is my bluetooth connection to a Jabra desk speaker won't work with A2DP, profiles. I must use one of the headset profiles instead. I was using A2DP previously with Bookworm based Raspberry Pi OS.

Look and feel of the theme is really good to my eyes.

NickJOB wrote: ↑

Tue Oct 28, 2025 1:54 pm

andrew_pi wrote: ↑

Thu Oct 02, 2025 9:16 am

First time I've used the network install, took just 3 minutes!

First thing to report is my bluetooth connection to a Jabra desk speaker won't work with A2DP, profiles. I must use one of the headset profiles instead. I was using A2DP previously with Bookworm based Raspberry Pi OS.

Look and feel of the theme is really good to my eyes.

I also have a problem with this. I have a Jabra Speak2 55 which worked well with Bookworm. Now, with Trixie, I can pair it and right-click select it from the speaker icon, but when I try to right-click select it from the microphone icon I get the message "Failed to connect to Bluetooth device - Could not set device as output" which doesn't sound right at all.

I'm not clear how to change profiles or if there should be some other kind of fix?

Thanks for any advice!

keyboardman wrote: ↑

Mon Nov 10, 2025 1:49 pm

I upgraded from bookworm to trixie on my Pi5 with GNOME. I searched "apt search wayvnc". it gives me this output even though I changed bookworm to trixie in "/etc/apt/sources.list.d/raspi.list"

Code: Select all

wayvnc/testing,now 0.9.1-1+rpt5 arm64 [installed,automatic]
 VNC server for wlroots-based Wayland compositors

As you can see it says "testing" instead of "trixie". lsb_release command tells me "No LSB modules are available."

Should I be concerned?

DirkS wrote: ↑

Mon Nov 10, 2025 2:09 pm

keyboardman wrote: ↑

Mon Nov 10, 2025 1:49 pm

I upgraded from bookworm to trixie on my Pi5 with GNOME. I searched "apt search wayvnc". it gives me this output even though I changed bookworm to trixie in "/etc/apt/sources.list.d/raspi.list"

Code: Select all

wayvnc/testing,now 0.9.1-1+rpt5 arm64 [installed,automatic]
 VNC server for wlroots-based Wayland compositors

As you can see it says "testing" instead of "trixie". lsb_release command tells me "No LSB modules are available."

Should I be concerned?

what does 'apt policy wayvnc' report?

wayvnc:
 Installed: (none)
 Candidate: 0.9.1-1+rpt5
 Version table:
 0.9.1-1+rpt5 500
 500 http://archive.raspberrypi.com/debian trixie/main arm64 Packages
 100 /var/lib/dpkg/status
 0.9.1-1 500
 500 http://deb.debian.org/debian trixie/main arm64 Packages

keyboardman wrote: ↑

Mon Nov 10, 2025 1:49 pm

As you can see it says "testing" instead of "trixie".

lsb_release command tells me "No LSB modules are available."

jojopi wrote: ↑

Mon Nov 10, 2025 2:17 pm

keyboardman wrote: ↑

Mon Nov 10, 2025 1:49 pm

As you can see it says "testing" instead of "trixie".

wayvnc is modified for RPOS, so it comes from RP repo instead of Debian. RP trixie suite is still listed as "testing", rather than "stable", for some reason.

lsb_release command tells me "No LSB modules are available."

Out of interest, where did you get the idea to type that command from? It is baffling irrelevant. I cannot really think of a situation where it would be useful, even archeologically.

keyboardman wrote: ↑

Mon Nov 10, 2025 2:31 pm

I used lsb_release command because I thought it would tell me "testing" or something. I might be wrong, I don't know.

dom wrote: ↑

Mon Nov 10, 2025 2:52 pm

keyboardman wrote: ↑

Mon Nov 10, 2025 2:31 pm

I used lsb_release command because I thought it would tell me "testing" or something. I might be wrong, I don't know.

Might be worth reading this thread.
I think you are expecting lsb_release to behave in a way it doesn't.

Distributor ID:	Debian
Description:	Debian GNU/Linux 13 (trixie)
Release:	13
Codename:	trixie

jojopi wrote: ↑

Mon Nov 10, 2025 2:17 pm

RP trixie suite is still listed as "testing", rather than "stable", for some reason.

Notice: Repository 'http://archive.raspberrypi.com/debian trixie InRelease' changed its 'Suite' value from 'testing' to 'stable'