maemo.org - Talk - [SOLVED] Lost all UI, unusable state

maemo.org - Talk (https://talk.maemo.org/index.php)

- SailfishOS (https://talk.maemo.org/forumdisplay.php?f=52)

- - [SOLVED] Lost all UI, unusable state (https://talk.maemo.org/showthread.php?t=95475)

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

Quote:

Originally Posted by juiceme (Post 1469866)

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

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

Code:

patch --dry-run -p 1 -d / -i /usr/share/patchmanager/patches/your_problematic_patch/unified_diff.patch

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

Quote:

Originally Posted by coderus (Post 1469892)

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

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

Quote:

Originally Posted by peterleinchen (Post 1469900)

How to?

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

journalctl -a /usr/bin/lipstick

Quote:

Originally Posted by coderus (Post 1469892)

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

Quote:

Originally Posted by coderus (Post 1469916)

journalctl -a /usr/bin/lipstick

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 ...