This problem started just after installing box64 from pi-apps. I uninstalled it and the problem persisted. Oddly enough, startplasma-x11 loads a desktop just fine, as does starting any other session not involving wayland, but I have to stop the blinking cursor with a ctrl-alt-f2 and log in first. Wayland refuses to run, however, without the external drive attached. External drive is ext4, has no system files, no real relation to the system at all, it's just a media drive.
Its entry in fstab is:If it is attached, plasma-wayland loads normally,; if is is not, plasma-wayland sits and blinks until I drop it to console.
I have a vague memory of doing something with it some time ago, writing its uuid somewhere else. I checked in crontab and I checked in the mounted devices section of KDE's system manager, no entries. Where else would the system be looking to mount the stupid thing?
Its entry in fstab is:
Code:
UUID=b9cd6ebd-d189-4f82-92ce-fd09f2348bf1 /media/pi/MS2T ext4 auto,nofail,noatime,rw,user 0 0I have a vague memory of doing something with it some time ago, writing its uuid somewhere else. I checked in crontab and I checked in the mounted devices section of KDE's system manager, no entries. Where else would the system be looking to mount the stupid thing?
Statistics: Posted by StevenDJaques — Fri May 02, 2025 3:24 am