[SOLVED] Lost all UI, unusable state
 

Already started here, but I thought this could derail the patch thread (even I think it is related to one of the patches; possibly).


Dumb Jolla (or me ;))!

I updated device to latest äkaälöülëiöäkä version 1.1.4.29. All fine. Had all patches disabled.
Updated all available SW/patches after successful upgrade.
Then a few days later I decided to activate the patches again. Did it all-in-one step. Went through all installed patches and tried to apply (some did not work but that was/is known).
Restarted lipstick and ...
BAM
An empty screen (with just the wallpaper) looked at me.
Nothing works, no apps, no up-down-side swiping, no notification screen. The display stays empty all the time. Only the lock when swiping from top works (shows the lock icon). Furthermore the coderus lockscreen on power button works with displaying selections (and selected app -torch- starts but wothout screen). That's it.

Unfortunately it seems that the upgrade changed the root password? As I cannot ssh into the device (do I have to use root or or user or what account?). Even it worked I had no idea what to check else disabling ausmt.

Any hints?

--
already tried
ssh user@jolla.mydomain
ssh root@jolla.mydomain

also recovery mode seems to be brokem :eek:
when holding vol+ and power button it "cries"/vibrates a few seconds ;)
when holding vol- and power button it powers up the Jolla logo and the white LED is on, but it does not go any further. I have to pull battery, nothing else works!
(battery was quite down, charging now)

Re: Lost all UI, unusable state
 

first of all root password is not set on jolla by default, nemo password is set in developermode settings. and of course nobody is changing your passwords.

Then check Jolla Care article about using Recovery Mode: https://jolla.zendesk.com/hc/en-us/a...Recovery-Mode-

Best option will be ssh via wifi to device and reinstalling homescreen packages. Using recovery for this a much harder.

Re: Lost all UI, unusable state
 

Was going to edit my first post, as I just realized that (what coderus mentioned above).
recovery mode: just read the article to the end and remembered about using putty/telnet (forgot that on-Jolla-screen is only logo)
nemo is the user to connect with ssh (checked: working)

Going to fix soon...

Was there not a post of you (coderus) where you explained how to disable all patches from command line?
Do you know which packages by name I should try. In which order?
TIA

Re: Lost all UI, unusable state
 

Solved! :)

It was enough to do
pkcon install lipstick-jolla-home-qt5
from ssh console (log in as nemo) and after devel-su.

Found the hint from coderus post. this one should really be made sticky / wikified!
big THANK you (the Jolla would not be fun at all without you around! ;))

Why would that one be more problematic using recovery mode?


--
ofc need to check which patch is still working or which one was the culprit. later .....

--
needed to do the full command linked above as two patches did not want to uninstall (Battery StatusBar on Lockscreen and Eventsview controls patch with settings)

Re: [SOLVED] Lost all UI, unusable state
 

@peterleinchen, so you just slammed in a bunch of patches, all/some probably not updated to be used with Äijänpäivänjärvi?

No wonder you got into a bit of trouble :D

In every release the QML's change so that patches just don't apply, you have to manually edit the bits that don't match. Else you'll get into fair lot of trouble...
I myself don't even use any patch manager, I just review the bits manually before applying anything.

Re: Lost all UI, unusable state
 

I guess you'd have to chroot into the Sailfish OS to re-install the damaged packages?

Re: [SOLVED] Lost all UI, unusable state
 

Installing packages in chroot is not a problem, getting internet working in chroot is harder.

Re: [SOLVED] Lost all UI, unusable state
 

Isnt it as simple as

Before chroot'ing .....

Re: [SOLVED] Lost all UI, unusable state
 

I 'guess' a patch can only be applied when the original bits match! So if there was no change in original files between the revisions, there should not be a problem (it might but ...), right?
I think I fetched just all patches I had and tried to aplly. Some did. Some not (as earlier with other OS revisions). No prob so far.

I think the one to blame is zetas 'voice call notification'.
But only in confunction with some other applied patch. As I tried once more one-by-one and that one crashed my UI. But when applying only that one everything seems fine.

So I will leave that out and apply all other once more.
Remark: I do not have a SIM in that device (so I really do not need that one ;)).

Re: [SOLVED] Lost all UI, unusable state
 

When patching multiple files, patches may apply cleanly to some and not ot others, so you end up in situation where couple of QML's are patched and couple are not... -> bang :p

Re: [SOLVED] Lost all UI, unusable state
 

Hmm?
Do you talk about different files affected with ONE patch?
Then I assume patchmanager to be so intelligent to notice that and say 'cannot apply'.
Otherwise: different files affected with different patches. I do not see how that could cause a BANG :confused:

Re: [SOLVED] Lost all UI, unusable state
 

Cannot happen.
One single mismatch even in a set of *.qml's to patch prevents patchmanager from applying anything.

But you can always check whats wrong with

Re: [SOLVED] Lost all UI, unusable state
 

It can't happen because of patchmanager. It can happen because of installing some applications patching something in per-installation scripts automatically, like phonehook or some schturman applications.

anyway we can not get real reason now. the only way to get real reason is getting logs of lipstick when it crashed to load.

Re: [SOLVED] Lost all UI, unusable state
 

How to?

Where located?
And still useful after restarting lots of times?

Re: [SOLVED] Lost all UI, unusable state
 

Lipstick is known to be buggy. I got a lipstick restart numerous times, triggered simply by using the phone normally. Half of the times the restart wiped my desktop wallpaper (I got just a black background instead), but none of the restarts were as catastrophic as peterleinchen describes. And, like it or not, it always happened after installing some patch or another. I even went as far as uninstalling Patchmanaver but Jolla is pretty much unusable without some patches so I put it back on. Haven't had lipstick crashing on me for a while and if/when it happens again, I know what to do so no big deal.

All this has been reported by me and a (small) number of people more than once. No solution has been found or, as far as I am aware, even investigated. All you get back from Jolla is the usual silence. The only one who bothered to reply at all was coderus, with his usual, "works for me, problem is your device".

The fact that it affects only some of us suggests some edge condition. I have not been able to identify a specific patch that triggers it. It is as if the trigger was the mere fact that some QML files have been altered, it does not matter which one.

Re: [SOLVED] Lost all UI, unusable state
 

journalctl -a /usr/bin/lipstick

Re: [SOLVED] Lost all UI, unusable state
 

Unfortunately journalctl holds only info of a few hours (ca. 11.05. 20:00 - 11.05. 23:30).
So I need to provoke the crash once more and dump the journal ...