Maybe. I'm also keeping open the possibility that I have a hardware issue. Thus far, I've discovered one of the HDMI outputs has distorted sound and the build quality of the USB3 sockets was also questionable (initially way too tight). Some sort of software or disk corruption might also be the culprit. I've not encountered any way of verifying packages, if there's such a thing....something in your config.
No spare microSD cards around here, I fear. I'm also averse to switching them out, and to sticking them into USB adapters. Data has been lost that way.Given that it is easy to do, I would burn a default config to a spare card and validate that a "stock" OS install behaves normally. You can then use this microSD card to compare to your install to try and figure out the differences.
I have been backing up my boot.log.# files in /var/log from before and after the incident (2/2/2024). Maybe I could glean something from them. I could also switch back to Wayland then reboot and examine the new boot.log file, couldn't I? Well, I notice that the actual boot.log file is empty. Surely there would be something I could check after a failed Wayland boot, through the terminal.
Really, I've not done any noodling (installation etc.) for a little while and not just before the issue. I had installed a load of software packages previously (over a week and several boots prior), but nothing terribly out of the ordinary and just about all of it using sudo apt install; no snapping, flatpacking or self-assembly.The most likely suspect is the last thing you did (changed/installed/removed) before it stopped working correctly. However, it could be the interaction of an update with something you changed previously, which is what makes this so much fun. It would be very helpful to know what extra software you have installed, and if there is anything out of the ordinary with your setup (networking wise) and what peripherals you have connected, especially the type and resolution of the monitor.
The most unusual things about my system are that I get internet from a Wi-Fi hotspot (which it would still connect to, I can see), and that the monitor is a 1080p TV. I've had to use a force_hotplug fix to stop Wayland crashing when the screen gets blanked, which apparently occurs due to the TV waggling hotplug on signal loss. That was a while back.
Oh, I also see a rogue zero-byte file in the /home/pi folder whose filename is made up of unusual graphical characters. This has been a feature for quite a while. The file won't delete.
Statistics: Posted by tkonan — Mon Feb 05, 2024 7:29 pm
