Commit #1295d93 does not seem to work for the case it was made for about patchmanager HOT 13 CLOSED

If you interested in parsing journal you can use journalctl -o json-pretty to see available fields with values

from patchmanager.

3.0.62 fixed all problems?

from patchmanager.

yep this is default behaviour now. restarting homescreen and removing all patches if cant load any qml in lipstick or jolla-settings which are major applications of sfos :)

from patchmanager.

check with new build

from patchmanager.

Still no difference, behaviour and PM-log is exactly as before.

journalctl -al _COMM=jolla-settings + _EXE=/usr/sbin/patchmanager + _EXE=/usr/bin/patchmanager-dialog 2>&1 | tee pm3.0.61-journal_shutdown-screen.txt (as root) outputs: pm3.0.61-journal_shutdown-screen.txt

from patchmanager.

BTW, is there a reason for not using an absolute path _COMM=/usr/bin/jolla-settings (instead of _COMM=jolla-settings) in Patchmanager 3 and when extracting from the Systemd journal?

Edit: Yes, because it is the correct syntax, see journalctl -o json-pretty | fgrep _COMM | sort | uniq

from patchmanager.

Thanks for testing, please check new build

from patchmanager.

Thanks for testing, please check new build

I have troubles installing v3.0.61-1.135.1: Storeman was hanging (right after updating some other apps successfully), "updating Patchmanager forever".
Looking at the command line, any pkcon sub-command was hanging, too. Apparently the zypper back-end was hanging.
Will reboot and retry then.

from patchmanager.

Slooow down, you are talking to an old man. ;)

And I have more in store. ;\

from patchmanager.

Well, PM 3.0.62-1.136.1 altered the behaviour WRT this issue slightly:

1. Unchanged: Shutdown screen is applying fine, which seems correct judging from the log.
2. Unchanged: After that, Restarting preloaded services works fine.
3. Unchanged: When entering Settings -> Display, "Could not load page" is displayed ...
4. Different: ... briefly, followed by Lipstick restarting hard and then all Patches are unapplied, Patchmanager's engine unloaded (Load engine entry in Patchmanager's pulley menu) and Patchmanager is in a special failure mode (Resolve failure entry in pulley).

TL;DR: Now additionally crashing Lipstick and ultimately unapplying all Patches. ;\

from patchmanager.

Well, while this technically makes sense (avoiding more severe mishaps, as not starting jolla-settings at all, thus preventing to resolve the situation at the GUI), this is a bit "bastard operator from hell"-style. ;))

Although I believe it now sends an overly strong indication that something went wrong (solely "Could not load page" was sufficient for that, IMO), any other approach would take additional coding efforts and this solution does the job, hence closing as fixed.

from patchmanager.

BTW, the other issues I was able to reproduce with various Patchmanager 3.0.61 releases (e.g. with Lockscreen Analog Clock) are gone with v3.0.62, hence I do not have more in store anymore.

Thank you!

from patchmanager.

thank you

from patchmanager.