I have been experiencing a problem with my current installation.
In early times of operating systems, this was called, for lack of a better name, rust. The most famous example is:
Taking a new installation of Windows, with nothing running besides a clean install of the operating system. Not making any entries, or accesses. Not performing any tasks not started by the operating system itself, and leaving it to run. After an extended period of time, it would crash.
The phenomenon was considered a cost of doing business, and the solution, at the time, was to not leave the computer running for extended periods of time. This was contrasted by cases where Linux had "up time" readings measured in years. Not days or weeks.
All that aside, I have been experiencing an issue which could be related to Wayland.
On multiple occasions, I have been working on a project. While working for a bit of time, I have gotten up to have a short break with a cup of coffee and a snack. Upon returning to my workstation, the screen had done a "white out" with only the low resolution wastebasket in the corner. The mouse was still active, but right click did not pull up a menu, and left click had no effect.
The availability of mouse and a "stable" screen leads me to believe that X is still running, and by extension Linux OS. I did not do a check externally to see if Samba or SSH were still active.
I solved the issue by doing a hard shutdown (holding the stop button on my Pi5 for 5 seconds). Everything came back when I restarted.
I am running a Pi-5 with a Pimoroni NVMe base and Crucial P3 500G PCM 3.0 drive. It has Bookworm installed, and for the most part has been very satisfactory. I'm just looking for any heads up if there is something that I need to do, or I am sending up a notice of an issue.
Please feel free to contact me for any additional details. I will monitor this thread periodically, but I don't normally come here daily.
Thank you in advance,
Jack
In early times of operating systems, this was called, for lack of a better name, rust. The most famous example is:
Taking a new installation of Windows, with nothing running besides a clean install of the operating system. Not making any entries, or accesses. Not performing any tasks not started by the operating system itself, and leaving it to run. After an extended period of time, it would crash.
The phenomenon was considered a cost of doing business, and the solution, at the time, was to not leave the computer running for extended periods of time. This was contrasted by cases where Linux had "up time" readings measured in years. Not days or weeks.
All that aside, I have been experiencing an issue which could be related to Wayland.
On multiple occasions, I have been working on a project. While working for a bit of time, I have gotten up to have a short break with a cup of coffee and a snack. Upon returning to my workstation, the screen had done a "white out" with only the low resolution wastebasket in the corner. The mouse was still active, but right click did not pull up a menu, and left click had no effect.
The availability of mouse and a "stable" screen leads me to believe that X is still running, and by extension Linux OS. I did not do a check externally to see if Samba or SSH were still active.
I solved the issue by doing a hard shutdown (holding the stop button on my Pi5 for 5 seconds). Everything came back when I restarted.
I am running a Pi-5 with a Pimoroni NVMe base and Crucial P3 500G PCM 3.0 drive. It has Bookworm installed, and for the most part has been very satisfactory. I'm just looking for any heads up if there is something that I need to do, or I am sending up a notice of an issue.
Please feel free to contact me for any additional details. I will monitor this thread periodically, but I don't normally come here daily.
Thank you in advance,
Jack
Statistics: Posted by jachaney — Sun May 25, 2025 9:10 pm