OS crashed with UT tweak tool
-
I used UT tweak tool to try the desktop mode.
After a little test with desktop mode, I changed back to mobile mode.
Then the OS crashed.
If each time of mode changed, should reboot the device?
I found double changes with tweak tool, only the first click works.
So I had to reinstall ubuntu touch. That's very trouble because of poor web speed.My device: MEIZU mx4
-
The UT tweak tool allows the user to do things that might cause the OS to malfunction, depending on what is tweaked on what device. It would seem that you have stumbled upon one of these things.
This is very much a 'use at your own risk' tool. -
Weird, I've never experienced that. And even now it works just fine with my MX4. What does however crash the system for me is closing UT Tweak tool - even if not entering the password yet. It did miraculously not crash for me just one time in at least 10 attempts I gave it now. And it is not the first time I've noticed this as I've been experiencing that behaviour for at least a few months now (but fortunately I only launch UT Tweak tool very rarely).
-
I don't think this is an issue with UTTT as it simply changes a setting. I rarely switch to desktop mode on my mx4 but I don't remember experiencing that. Maybe you have a lot of apps open when you do it? Or a heavy/big app open? Lomiri isn't exactly stable at the moment. It can crash due to memory or doing many things at once.
-
@zubozrout
Just checked, and no crash of any kind if i close UTTT without entering password. -
@keneda I am unable to get it crash today either :/. But it was constantly crashing for me yesterday evening even after multiple reboots and I've certainly seen these crashes before (in the last few months) too.
-
Now I got this crash again @Keneda. Unity crashed upon closing the UT Tweak tool so was trying to restart itself and before it could load the whole system restarted seeing the bootloader logo. But no more again now.
I am also seeing these kind of logs in the app log:
qt.qpa.mirclient: Attempted to deliver an event to a non-existent window, ignoring.
and:
file:///opt/click.ubuntu.com/ut-tweak-tool.sverzegnassi/0.6.2/qml/main.qml:36: TypeError: Value is null and could not be converted to an object
where the first one could potentially kill Unity I guess but I am seeing both these errors even when it doesn't crash.
When looking at this file
.cache/upstart/unity8.log.1.gz
I can see some more details starting around 19:04:38 when the app was launched, then 19:04:41 when I closed it. Then there is a gap in between 19:04:42.094 and 19:05:29.635 when unity crashed, started loading itself up again after this gap. And then finally at 19:06:27.876 the whole system went down going all the way thorough the bootloader. Here is the log, though I am not sure if anything can actually be useful there to debug this: https://zubozrout.cz/data/logs/ut-tweak-tool-unity-crash.logSeems similar to my phone crashing from time to time but usually at least few times a day upon receiving Telegram messages: https://github.com/ubports/ubuntu-touch/issues/1164 (a long standing issue I seem to be continually getting for ages now).
-
@zubozrout you should report this on UTTT repo
-
@keneda I would, but the qml error might not be significant and the other one is probably not UT Tweak Tool related. I would expect that to be more a Lomiri issue TBH. Nonetheless I am not sure I have enough data for either, at least I don't see them
-
@zubozrout , @keneda,
I reinstalled UT, and the OS crashed another time.
This time the crash looks like I had run some other apps can write system partition while I using the tweak tool.
Then I reinstalled UT, and carefully used the tweak tool. But the OS crash the third time. The reason maybe I didnot use a password for my device while the tweak tool need a password.
And I reinstalled again. But yesterday , the OS crashed the fouth time! I justed picked a long touch on a link for open in another windows with a webber made app(That operation is very usual for a web browser), and the OS crashed.
It looks unusual operations will result conflicts on system partition. Also there is no approved or restart lomiri actions after editting with the tweak tool, that would make the system partition easily hurt.
In this days, the lomiri crahsed many times, most beacuse of the system is over load and the device be in hot. For this situation, I just reboot the device and it is ok.
That is my update information.