Times fine to take since I’ve got plenty of it between no obvious problems with this solution and X11 still working just fine.
I am actually curious about this stuff though and was tempted to try submit my first proper bug report with this since it’s both simple and a major problem. I’m a developer myself, but I’ve stuck to my lane super hard so it’s difficult to figure out how to actually tinker with linux without the first clue where to start. For stuff like this in future, mind sharing what I should look into for that shell scripting magic you did to get the right variable?
I would still file a bug report. I don’t know if it is crashing, so I can’t recommend whether or not to try and get a backtrace.
It’s hard to do anything without knowing where to start. That’s what makes contributing to any project, so hard. For me it is almost never the language, but just knowing where stuff is. Even reading through the merge request for moving the display functionality out of kscreen. It feels like if you weren’t part of that conversation. You would have no idea which parts of these 3 or 4 different libraries are responsible for controlling which parts of the display.
I was unable to find anything relevant in the code, I can only guess that it must be saving from memory before rebooting. If that is the case and hopefully there isn’t some cached file that I missed somewhere. It should be safe to make the file mutable again. Then reboot and see if all is still well.
Edit: the relevant file for loading, writing, and saving is outputconfigurationstore.cpp. Nothing in there about caching from what I can see. I think it overwrites on exit from memory. Since it loaded up the immutable version, I think it will attempt to write back the corrected version you have now. Should be fine to make it mutable again.
Set it mutable, rebooted, and the video signal is intact. I guess that means it was either cached or something else read it and corrected itself. Probably should have tried a hard shutdown, thinking about it… oops. Oh well. Thank you for solving this for me! You were really quick at hunting that right variable to change.