BUILD ID: 126.96.36.199
HARDWARE: XA2 Plus (dual sim)
UI LANGUAGE: English (US)
REGRESSION: (compared to previous public release: Yes, No, ?): ?
Because it seemed fun (and convenient) to me to develop directly on the phone (mainly to play with QML and Common Lisp (
eql from OpenRepos)) I had to install some dependencies required by the qarma.pro file.
One of these dependencies was
qt5-qtgui-devel which has as its own dependency
mesa-llvmpipe-libGLESv2. This last package overwrites the existing
/usr/lib/libGLESv2.so.2.0.0 which lead to this bug report.
(The packages are from the default Jolla repos on a fresh phone, not from OpenRepos or something else!)
STEPS TO REPRODUCE:
- Flash phone with a new installation,
- From the terminal or a remote session install:
devel-su pkcon install mesa-llvmpipe-libGLESv2, or
devel-su pkcon install qt5-qtgui-devel,
- Reboot phone, enter correct security code,
- Observe the infinite spinner.
The telephone shows the normal lock screen.
The telephone keeps showing the decryption unlock screen and the spinner keeps spinning.
The telephone is remotely reachable (if enabled beforehand) and has most services running. The
sailfish-unlock-agent seems stuck:
$ systemctl list-jobs JOB UNIT TYPE STATE 134 sailfish-unlock-agent.service start running
If you installed just
mesa-llvmpipe-libGLESv2 from step 2.1 then putting back the old
libGLESv2.so.2.0.0 fixes everything again on a reboot. If you installed
qt5-qtgui-devel from step 2.2 then there’s more issues (which I haven’t further explored).
I do not think packages installed from the default repos should do this. I do agree one is on his own when installing packages from unsupported repos.