I've lost count the number of times I found a bug in a Linux screensaver. I eagerly await hearing how they're going to make this right. Every Linux distro is shipping this copyright- and license-infringing code. Mint-screensaver and Cinnamon-screensaver, being forks and descendants of Gnome-screensaver, have inherited this license violation and continue to perpetuate it. It turns out, the Gnome-screensaver authors copied large parts of XScreenSaver into their program, removed the BSD license and slapped a GPL license on my code instead - and also removed my name. XScreenSaver was released under the BSD license, one of the oldest and most permissive of the free software licenses. Just to add insult to injury, it has recently come to my attention that not only are Gnome-screensaver, Mint-screensaver and Cinnamon-screensaver buggy and insecure dumpster fires, but they are also in violation of my license and infringing my copyright. This button-mashing actually crashed the machine's screensaver by sheer luck, allowing them onto the desktop, ultimately leading to the discovery of a high priority security vulnerability for the Linux Mint team."īut that's not the only thing bothering Jamie Zawinski: But HotHardware notes that it was discovered when " one Dad let the kids play with the keyboard. ZDNet reports that Linux Mint has issued a patch for Cinnamon that fixes the screensaver bug. These bugs are a shameful embarrassment of design - as opposed to merely bad code. It is unconscionable that someone designing a critical piece of security infrastructure would design the system in such a way that it does not fail safe.Įspecially when I have given them nearly 30 years of prior art demonstrating how to do it right, and a two-decades-old document clearly explaining What Not To Do that coincidentally used this very bug as its illustrative strawman! The real bug here is that the design of the system even permits this class of bug. The point is not that such a bug existed, but that such a bug was even possible. You will recall that in 2004, which is now seventeen years ago, I wrote a document explaining why I made the design trade-offs that I did in XScreenSaver, and in that document I predicted this exact bug as my example of, "this is what will happen if you don't do it this way."Įvery time this bug is re-introduced, someone pipes up and says something like, "So what, it was a bug, they've fixed it." That's really missing the point. Jamie titled his blog post "I told you so, 2021 edition": Solutions to these long-standing issues remain elusive. Long-standing topics like X11, developer interaction, and code licensing all feature. JWZ continues to track issues with screensavers on Linux (since 2004!), and discusses a new bug in cinnamon-screensaver. I'm using a script which automaticly boots into Kweb Browser if you choose the Console Autologin in the raspi-config.Legendary programmer Jamie Zawinski has worked on everything from the earliest releases of the Netscape Navigator browser to XEmacs, Mozilla, and, of course, the XScreenSaver project. I have to mention that i'm using the 7" Raspberry Pi Touchscreen and i'm not booting to the desktop, but to the text console. No screensaver, no screen blanking, no monitor power saving mode.īut my screen still goes idle after a certain time of inactivity. Save with 'Ctrl' + 'x' key, then 'y', then 'enter' So it looks like -profile -desktop -profile s 0 s s dpms 0 0 0 'select all', then right click 'copy', then scroll to bottom with down arrow key, then 'paste' NO SCREEN BLANKING, NO POWERSAVE MODE, NO SCREENLOCK. You just have to enable it is all (or simply disable it all if that is your preference).Ĭlick here to setup lockscreen, put monitor into a true powersave mode, and configure settingsĭISABLE IT ALL. LXDE in Debian/Raspbian has its own ability to setup lockscreen, turn off the monitor, and put it into a true "power save" mode (not screen blanking), etc.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |