Recover Jolla 1 from lipstick start failure [answered]

asked 2020-01-02 20:46:15 +0300

mosen
9271 ●92 ●132 ●145

http://mosushi.de/

Hi all!

My Jolla 1 suffers a total lipstick startup failure after a failed update.

What happend?
I took it from the drawer after ~3years and wanted to set it up for my daughter.
SW version was 2.0.x and the first two updates to 3.1.x succeeded.
I then played around with it to show Jolla 1 to a visiting friend and must have enabled patchmanager2 in the process.
When i now tried to further update to 3.2.1.20 in the evening it failed at ~50% of the installs with some error mentioning to "deactivate all patches".
Great, i am an idiot...
I then deactivated all patches and removed patchmanager in the hope a second update try would fix it.
The second version --dup went through without errors but after reboot i have no lipstick whatsoever.
Since the install is really fleshed out and was fully set up to my needs i am not keen to do reset in recovery mode and loose it all.

What would i need to do to completely reinstall lipstick? Would that even help?

Ssh connection works and if i try to start or restart lipstick manually i get:

[root@Sailfish nemo]# systemctl --user restart lipstick
Job for lipstick.service failed because the control process exited with error code. See "systemctl status lipstick.service" and "journalctl -xe" for details.

systemctl status says:

[root@Sailfish nemo]# systemctl status lipstick.service
● lipstick.service
   Loaded: not-found (Reason: No such file or directory)
   Active: inactive (dead)

journalctl says:

Jan 02 17:58:37 Sailfish systemd[1182]: Starting The lipstick UI...
-- Subject: Unit UNIT has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit UNIT has begun starting up.
Jan 02 17:58:37 Sailfish kernel: handle_bam_mux_cmd: dropping invalid LCID 10 reserved 1 cmd 1 pad 0 ch 10 
len 0
Jan 02 17:58:37 Sailfish kernel: handle_bam_mux_cmd: dropping invalid LCID 11 reserved 1 cmd 1 pad 0 ch 11 
len 0
Jan 02 17:58:38 Sailfish lipstick[1339]: [C] unknown:0 - Failed to create display (No such file or director
y)
Jan 02 17:58:38 Sailfish systemd[1182]: lipstick.service: Main process exited, code=exited, status=1/FAILUR
E
Jan 02 17:58:38 Sailfish systemd[1182]: Failed to start The lipstick UI.
-- Subject: Unit UNIT has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit UNIT has failed.
-- 
-- The result is failed.
Jan 02 17:58:38 Sailfish systemd[1182]: Dependency failed for Application launch booster for Sailfish Brows
er.
-- Subject: Unit UNIT has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit UNIT has failed.
-- 
-- The result is dependency.
Jan 02 17:58:38 Sailfish systemd[1182]: booster-browser.service: Job booster-browser.service/start failed w
ith result 'dependency'.
Jan 02 17:58:38 Sailfish systemd[1182]: Dependency failed for Application launch booster for Silica on QtQu
ick2.
-- Subject: Unit UNIT has failed
-- Defined-By: systemd