Issue with 5.1.0.7 Early Acces update

Bug Reports
1

REPRODUCIBILITY: Always
OS VERSION: 5.0.0.77 to 5.1.0.0.7
HARDWARE: X10II
UI LANGUAGE: EN
REGRESSION: NO

DESCRIPTION:

Updated to 5.1.0.77 and I had to force reboot after the update but system does not start. It boots to inactive password keypad and then after 2-3s the screen goes black and that’s all. I see black screen and white diode.

PRECONDITIONS:

Working 5.0.0.77

STEPS TO REPRODUCE:

Update to 5.1.0.7 Early release

EXPECTED RESULT:

Working phone,

ACTUAL RESULT:

Inactive keypad during boot and the black screen.

MODIFICATIONS:

All

ADDITIONAL INFORMATION:

Black screen.

I’m looking for the hints what to disable in recovery mode to successfully boot. So far I have removed anything not from Jolla from /etc/systemd.
Updated to 5.1.0.8 and no change.

2

Why don’t you post in the release thread like everyone else? It’s not like the problem is unknown…

1 Like
3

I have posted but there are 211 posts already and no one is going to read the post from 2 days ago.

4

So what do you mean that this whole new thread adds at all?

5

So what do you mean that your comments adds at all to this issue?

3 Likes
6

That people might be reminded that cluttering up the forum just wastes time and effort.

7

I am the last one that cluttering the forum and you fighting this undoubtedly a problem, are already doing the same and wasting my time and effort.
I believe that this issue is unique and after 2 days of solving I simple need any clue and direction where to search.

2 Likes
8

I have connected keyboard via USB and entered blindly pass code. The phone booted and I saw a SFOS lock sceen after entering pass code the screen then went black again.
Now I can login to system via wifi and ssh.
After restarting of homescreen systemctl --user restart lipstick I can see a login screen again for several seconds and the it goes black again.
Edit: It is getting interesting, as long as I use touch screen e.g. rotate login screen carousel it works. After entering pass code or living it alone for a few seconds the screen goes black.

1 Like
9

Sounds like an incomplete update. Is there any space left on the root partition?

10

A lot:
Filesystem Size Used Available Use% Mounted on /dev/sailfish/root 10.2G 6.6G 3.6G 65% /

11

Have you tried the verify option from sfos-upgrade?

Or looked at some logs?

12

Back in business. I have fixed the issue.
The culprit was pulseaudio that was unable to start due to wrong libgcrypt library in /usr/lib64.
There was libgcrypt.so.20.7.0 file linked to libgcrypt.so.20 and libgcrypt.so.20.7.0 file.
I have removed libgcrypt.so.20.7.0 and relinked libgcrypt.so.20 to libgcrypt.so.20.7.0.
I have no clue where the libgcrypt.so.20.7.0 comes from.
It looks like it was a part of orphaned package:
Information for package libgcrypt20:

Repository     : @System
Name           : libgcrypt20
Version        : 1.12.0-1.2.3.bso
Arch           : aarch64
Vendor         : meego
Installed Size : 1.1 MiB
Installed      : Yes (automatically)
Status         : up-to-date
Source package : libgcrypt-1.12.0-1.2.3.bso.src
Upstream URL   : https://www.gnupg.org/software/libgcrypt/index.html
Summary        : The GNU Crypto Library
Description    : 
    Libgcrypt is a general purpose crypto library based on the code used in
    GnuPG.

most likely fetched from one of testing repositories.

3 Likes