https://bugs.kde.org/show_bug.cgi?id=527185
Méven <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |DOWNSTREAM --- Comment #11 from Méven <[email protected]> --- (In reply to Mark from comment #10) > Okay, I'm sailing into very unknown territory now, so I'm just giving you > the output of the commands: > > ❯ udevadm test /sys/class/block/sda3 2>&1 | grep -i -B3 udisks_ignore > > ~ > ❯ udevadm info /dev/sda3 | grep -i part_entry > E: ID_PART_ENTRY_SCHEME=gpt > E: ID_PART_ENTRY_NAME=root > E: ID_PART_ENTRY_UUID=1e48bf56-1865-4e6b-8929-d9e62a073084 > E: ID_PART_ENTRY_TYPE=c12a7328-f81f-11d2-ba4b-00a0c93ec93b > E: ID_PART_ENTRY_NUMBER=3 > E: ID_PART_ENTRY_OFFSET=8392704 > E: ID_PART_ENTRY_SIZE=125824952 > E: ID_PART_ENTRY_DISK=8:0 > > ~ > ❯ grep -n UDISKS_IGNORE /usr/lib/udev/rules.d/80-udisks2.rules > 57:# (e.g. UDISKS_PRESENTATION_HIDE -> UDISKS_IGNORE) > 116:# interface so setting UDISKS_IGNORE at first does not seem to achieve > 121:ENV{ID_PART_ENTRY_SCHEME}=="mac", > ENV{ID_PART_ENTRY_TYPE}=="Apple_Bootstrap", ENV{UDISKS_IGNORE}="1" > 124:ENV{ID_PART_ENTRY_SCHEME}=="gpt", > ENV{ID_PART_ENTRY_TYPE}=="426f6f74-0000-11aa-aa11-00306543ecac", > ENV{UDISKS_IGNORE}="1" > 130: ENV{UDISKS_IGNORE}="1" > 136: ENV{UDISKS_IGNORE}="1" > 142: ENV{UDISKS_IGNORE}="1" > 147: ENV{UDISKS_IGNORE}="1" > 152: ENV{UDISKS_IGNORE}="1" > 155: ENV{UDISKS_IGNORE}="1" > 160: ENV{UDISKS_IGNORE}="1" > 163:ENV{ID_VENDOR}=="Sony", ENV{ID_MODEL}=="PRS*Launcher", > ENV{UDISKS_IGNORE}="1" > 166:KERNEL=="sr*", ENV{ID_VENDOR}=="SanDisk", ENV{ID_MODEL}=="Cruzer", > ENV{ID_FS_LABEL}=="U3_System", ENV{UDISKS_IGNORE}="1" > 169:KERNEL=="sr*", ENV{ID_VENDOR}=="ASMT", ENV{ID_MODEL}=="VirtualCDROM", > ENV{ID_FS_LABEL}=="ASUS_+Speed_ZENDISK*", ENV{UDISKS_IGNORE}="1" > 172:KERNEL=="sr*", ENV{ID_VENDOR}=="Linux", > ENV{ID_MODEL}=="File-CD_Gadget*", ENV{ID_FS_LABEL}=="CDROM*", > ATTRS{manufacturer}=="HMD Global", ENV{UDISKS_IGNORE}="1" > 184:ENV{ID_PART_TABLE_TYPE}=="dos", ENV{ID_PART_ENTRY_TYPE}=="0x0|0x17", > ENV{ID_PART_ENTRY_NUMBER}=="1|2", ENV{ID_FS_TYPE}=="iso9660|udf", > ENV{UDISKS_IGNORE}="0" > 187:KERNEL=="ram*", ENV{UDISKS_IGNORE}="1" > 188:KERNEL=="zram*", ENV{UDISKS_IGNORE}="1" > > ~ > ❯ pacman -Qo /usr/lib/udev/rules.d/80-udisks2.rules > /usr/lib/udev/rules.d/80-udisks2.rules is owned by udisks2 2.11.2-1.1 Thanks, this shows the cause. udevadm reports ID_PART_ENTRY_TYPE=c12a7328-f81f-11d2-ba4b-00a0c93ec93b for sda3. This is the partition type of an EFI System Partition, the same as sda2. The udisks2 rule at line 136 of 80-udisks2.rules hides every partition of this type. So UDisks, Solid and Dolphin all hide your root partition as an ESP. A Linux root partition should have the type 4f68bce3-e8cd-4db1-96e7-fbcaf984b709 (Linux root x86-64). The installer set this type, so please report it to your distribution, CachyOS. To fix the existing installation: sudo sgdisk --typecode=3:4f68bce3-e8cd-4db1-96e7-fbcaf984b709 /dev/sda then sudo partprobe /dev/sda or reboot. The data on the partition does not change. A second partition with the ESP type can also confuse the firmware or the bootloader. I am closing this as a downstream issue. -- You are receiving this mail because: You are watching all bug changes.
