Created attachment 170225 [details] Screen-shot showing issue. SUMMARY Disks & Devices showing non-removable devices when set to display only removable. STEPS TO REPRODUCE 1. Set Disks & Devices to show removable devices only. 2. Insert removable device. 3. Open Disks & Devices OBSERVED RESULT All non-removable devices are shown as well as the inserted removable device. See attached screen-shot. EXPECTED RESULT Only the removable device is shown SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20240605 KDE Plasma Version: 6.0.5 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.1 Kernel Version: 6.9.3-1-default (64-bit) Graphics Platform: X11
I can't reproduce this issue on my system. Some questions for you: 1. How exactly are those devices physically connected? 2. Does the issue reproduce on Wayland? 3. Does the issue reproduce in a new clean user account? 4. Did this work in the past and break with the update to Plasma 6, or 6.0.5, or some other specific version? Thanks!
(In reply to Nate Graham from comment #1) > I can't reproduce this issue on my system. Some questions for you: > 1. How exactly are those devices physically connected? SATA > 2. Does the issue reproduce on Wayland? Unfortunately Wayland doesn't play nicely on this system - black screen + cursor > 3. Does the issue reproduce in a new clean user account? Yes > 4. Did this work in the past and break with the update to Plasma 6, or > 6.0.5, or some other specific version? Working fine prior to the Tumbleweed update 20240523 -> 20240605 (20240524 and 20240531 skipped, so unable to be exact on which update may have caused this.) Updates included that may be relevant: plasma6-* 6.0.4 -> 6.0.5 kde gear 24.04.8 -> 24.05.0 kernel 6.9.1 -> 6.9.3
I think we can discount the kernel, after booting to the previous 6.9.1 version the issue still exists.
How did you set the mounting for this device? As in, do you have fstab config you could share, or was it set up automatically during install? Also, is it a new device, or has it been there since installation of the system? Something clearly wants to think that this device is removable, just trying to figure out now if it's outside or inside Plasma, so that's why I am asking. :)
This is a dual-boot setup with the choice of boot made by bios, not grub. Physically there are 2 ssd drives: sda and sdb, and 1 hdd: sdc (all connected by SATA directly to the motherboard). paul@Orion-15:~$ sudo lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS sda 8:0 1 55.9G 0 disk ├─sda1 8:1 1 48G 0 part / └─sda2 8:2 1 4G 0 part [SWAP] sdb 8:16 1 119.2G 0 disk └─sdb1 8:17 1 112G 0 part /home sdc 8:32 1 232.9G 0 disk ├─sdc1 8:33 1 32G 0 part ├─sdc2 8:34 1 192G 0 part └─sdc3 8:35 1 8.9G 0 part sr0 11:0 1 1024M 0 rom paul@Orion-15:~$ This is fstab used when booting from the ssd drives: UUID=2511d4d8-0425-4e80-bd14-86798396bdfb / ext4 noatime,acl,user_xattr 1 1 UUID=08a4ff75-8318-40cf-b78b-b7049064dfb5 swap swap defaults 0 0 UUID=801838af-06ff-405e-a6c3-194ba5878291 /home ext4 relatime,acl,user_xattr 1 2 This is fstab used when booting from the hdd drive: UUID=ea5c2b1b-ac33-497d-b286-2c06a23623a2 / ext4 noatime,acl,user_xattr 1 1 UUID=8595c8af-adce-47f8-b9e4-9f46348154ac swap swap defaults 0 0 UUID=20d5bdae-6c44-4c27-be89-9c9e91e9233f /home ext4 relatime,acl,user_xattr 1 2 The system is not new and has worked fine with this setup for several years. As I wrote in comment #2, the issue first arose following the Tumbleweed update 20240523 -> 20240605
Follow up... I noticed on the above lsblk output the removable flag (RM) is shown as "1" and also: paul@Orion-15:~> cat /sys/class/block/sda/removable 1 paul@Orion-15:~> cat /sys/class/block/sdb/removable 1 paul@Orion-15:~> cat /sys/class/block/sdc/removable 1 paul@Orion-15:~> is showing these devices as "removable" However, there have been *no* changes made to the hardware or bios configuration of this machine. If I now boot this machine using a Leap 15.5 live USB and then issue the lsblk command the 3 non removable drives (sda, sdb, and sdc) are shown with the correct removable flag, ie "0", non-removable. linux@localhost:~> sudo lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS loop0 7:0 0 814.1M 1 loop /run/overlay/squashfs_container loop1 7:1 0 4.8G 1 loop /run/overlay/rootfsbase sda 8:0 0 55.9G 0 disk ├─sda1 8:1 0 48G 0 part └─sda2 8:2 0 4G 0 part sdb 8:16 0 119.2G 0 disk └─sdb1 8:17 0 112G 0 part sdc 8:32 0 232.9G 0 disk ├─sdc1 8:33 0 32G 0 part ├─sdc2 8:34 0 192G 0 part └─sdc3 8:35 0 8.9G 0 part sdd 8:48 1 57.7G 0 disk ├─sdd1 8:49 1 927.5M 0 part /run/overlay/live ├─sdd2 8:50 1 20M 0 part └─sdd3 8:51 1 56.8G 0 part /run/overlay/overlayfs sr0 11:0 1 1024M 0 rom linux@localhost:~> So it would seem the "bug" lies not with "Disks & Devices" - question now is, where or what? :(
To me this looks like issue you should ask from openSUSE. You could ask them if theres any changes to disk handling between the updates you mentioned. I am setting this as resolved downstream, since I don't think we can do anything about it. However, if you do spot that this might be caused by KDE applications after all, feel free to report in here and open the bug again!
OK - Thanks. - I don't believe this to be a KDE issue. I'll raise an openSUSE bug report.