> > Until this bug is eliminated any device instability while WiFi is enabled > > can be attributed to it. > > > > Well it is slightly worse. Also some device instability even when wifi > is off can be attributed to it if wi-fi was enabled at least once on > this device. Like this example shows, it most probably corrupted memory > of application manager before it saved updated status file with package > info. Any file modified when wi-fi is on can become corrupted. One > random example - whole gconf system configuration is saved as a set of > xml files and contain sensitive data that could bring device to reboot > loop or random reboot when some (system) application reads its settings > from it and becomes confused due to bad data. This configuration is > saved when some device setting changes (like changing brightness or > sound volume level) which happens relatively often. Also installation of > any package over network can corrupt some random bytes when extracting > it so future execution can run faulty code or read bad data even when > wi-fi is not enabled.
Fantastic. I've been having to reflash roughly once a week due to spontaneously occurring reboot loops. Has this bug always been there, or will reverting to an earlier 2007HE help avoid it? -- "Tak does not require that we think of Him, only that we think." --Grag Bashfullsson http://www.gnu.org/philosophy/shouldbefree.html _______________________________________________ maemo-developers mailing list [email protected] https://lists.maemo.org/mailman/listinfo/maemo-developers
