A couple on months ago I had a bizarre problem where a piece of window was stuck over LB and would return every time I restarted LB, even after a PC reboot:
I was advised to hold down the left-shift key while restarting LB and that worked.
Last night LB 1.10.0.0 bricked. The laser status would change from “Ready” to “Disconnected” every time you tried to run a job, and stayed in Disconnect. Ruida 6445G on ethernet. Ping to IP# was fine. This is a makerspace with a lot of casual users, I don’t know how it got into this state.
I tried to reboot LB and the PC a dozen times, no luck, then I remembered the left-shift key thing. BOOM ALL FIXED. So that’s twice now we’ve had LB get stuck with some persistent, bizarre error that can only be fixed by holding down the left-shift during a restart. I’ve never seen this in any other software.
Ok, that’s great, the problem is fixed, we’re ok. But what is this left-shift thing doing? Because people are going to be asking me how I fixed it. As a makerspace, we’ve got a lot of users of varying skill levels and they used it unsupervised. If I mention this possible “fix”, it becomes like a viral rumor, users are going to be trying to fix ANY problem by doing this left-shift thing on their own and it won’t be logged or communicated to anyone. This might cause more problems/confusion, I just don’t know what the left-shift thing is doing.
What does the left-shift thing do to make it “clean boot”, exactly, and why isn’t it booting up clean like this all the time? What are the consequences of using the left shift key unnecessarily during restarts?