Editing Unrestricted-system-ui
Warning: You are not logged in.
Your IP address will be recorded in this page's edit history.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 149: | Line 149: | ||
=== Technical details === | === Technical details === | ||
system-ui enters safe mode when it receives SIGSEGV or SIGABRT, it does this by writing two files to /tmp (system-ui-crashed and system-ui-crashed-again), the second file is a workaround to system-ui crashing at startup, if the first file exists when system-ui crashes, the second one will be created. unrestricted-system-ui checks for the second file at startup, if it exists, it restores Nokia's limitation while allowing another applet, the safe mode one, to show. To exit safe mode, the applet deletes both files and kills system-ui to restart it. | system-ui enters safe mode when it receives SIGSEGV or SIGABRT, it does this by writing two files to /tmp (system-ui-crashed and system-ui-crashed-again), the second file is a workaround to system-ui crashing at startup, if the first file exists when system-ui crashes, the second one will be created. unrestricted-system-ui checks for the second file at startup, if it exists, it restores Nokia's limitation while allowing another applet, the safe mode one, to show. To exit safe mode, the applet deletes both files and kills system-ui to restart it. | ||
- |
Learn more about Contributing to the wiki.