Failed to start Application launch booster for Qt5
asked 2020-05-07 14:15:56 +0300
I did the update to Rokua (3.3.0.16) two days ago. The update got stuck (green led and screen almost black with some backlight). The phone was working fine (didn't check journalctl) after restart. Installed propeller over Storeman (propeller has only one exe file) and was about to add repository for Battery Buddy. Phone got unresponsive. After a restart, there is only the first screen, with the bottom and the top drawer. I removed both added repos just to be sure, but no effects.
Can connect over ssh, calls not possible.
Journal:
eMay 07 12:53:10 Xperia10-DualSIM systemd[5036]: Starting Application launch booster for Qt5...
May 07 12:53:10 Xperia10-DualSIM /usr/libexec/mapplauncherd/booster-qt5[7256]: Daemon: Boot mode set.
May 07 12:53:10 Xperia10-DualSIM booster-qt5[7256]: terminate called after throwing an instance of 'std::runtime_error'
May 07 12:53:10 Xperia10-DualSIM booster-qt5[7256]: what(): SocketManager: Failed to bind to socket (fd=7)
May 07 12:53:10 Xperia10-DualSIM systemd[5036]: booster-qt5.service: Main process exited, code=killed, status=6/ABRT
May 07 12:53:10 Xperia10-DualSIM systemd[5036]: Failed to start Application launch booster for Qt5.
May 07 12:53:10 Xperia10-DualSIM systemd[5036]: Dependency failed for Signal booster-qt5 that boot is over.
May 07 12:53:10 Xperia10-DualSIM systemd[5036]: booster-qt5-signal.service: Job booster-qt5-signal.service/start failed with result 'dependency'.
May 07 12:53:10 Xperia10-DualSIM systemd[5036]: booster-qt5.service: Unit entered failed state.
May 07 12:53:10 Xperia10-DualSIM systemd[5036]: booster-qt5.service: Failed with result 'signal'.
May 07 12:53:11 Xperia10-DualSIM kernel: binder: 4841:4841 transaction failed 29189/-22, size 0-0 line 3024
May 07 12:53:11 Xperia10-DualSIM systemd[5036]: booster-qt5.service: Service hold-off time over, scheduling restart.
May 07 12:53:11 Xperia10-DualSIM systemd[5036]: booster-qt5.service: Start request repeated too quickly.
May 07 12:53:11 Xperia10-DualSIM systemd[5036]: booster-qt5.service: Unit entered failed state.
May 07 12:53:11 Xperia10-DualSIM systemd[5036]: booster-qt5.service: Failed with result 'start-limit'.
Also, I couldn't make a backup as :
Start: /usr/libexec/jolla-notes/notes-vault --action export --name Notes --bin-dir /home/nemo/.local/share/system/privileged/Backups-tmp/units/sailfish_backup_2020-05-07T08-59-36Z/Notes/blobs --dir /home/nemo/.local/share/system/privileged/Backups-tmp/units/sailfish_backup_2020-05-07T08-59-36Z/Notes/data --home-dir /home/nemo
Done: notes-vault [FAILED] Exit code: 127
Standard error was:/usr/libexec/jolla-notes/notes-vault: symbol lookup error: /usr/libexec/jolla-notes/notes-vault: undefined symbol: _ZN5vault4unit6getoptEv
Any hint? Otherwise, I have to reset the phone :(
Note: To be able to backup the phone, I needed to:
/usr/libexec/jolla-notes/notes-vault: symbol lookup error: /usr/libexec/jolla-notes/notes-vault: undefined symbol: _ZN5vault4unit6getoptEv
cd /usr/libexec/jolla-notes/
mv notes-vault notes-vault.orig
touch notes-vault
chmod +x notes-vault
Did a fsck :(
Do I need to revert to Android first?
Jolla Recovery v2.0
tomtom ( 2020-05-07 14:46:58 +0300 )editWelcome to the recovery tool! The available options are: 1) Reset device to factory state 2) Reboot device 3) Shell 4) Perform file system check 5) Run sshd 6) Exit Type the number of the desired action and press [Enter]: 4 /dev/mmcblk0rpmb: read failed after 0 of 4096 at 0: Input/output error 2 logical volume(s) in volume group "sailfish" now active e2fsck 1.45.0 (6-Mar-2019) Pass 1: Checking inodes, blocks, and sizes Pass 2: Checking directory structure Pass 3: Checking directory connectivity Pass 4: Checking reference counts Pass 5: Checking group summary information root: 38172/160000 files (0.4% non-contiguous), 454887/640000 blocks Opening encrypted filesystem, you will be prompted for your security code. Enter passphrase for /dev/sailfish/home: e2fsck 1.45.0 (6-Mar-2019) Pass 1: Checking inodes, blocks, and sizes Pass 2: Checking directory structure Pass 3: Checking directory connectivity Pass 4: Checking reference counts Pass 5: Checking group summary information /dev/mapper/luks-home: 30923/2973696 files (3.0% non-contiguous), 11091667/11887104 blocks /dev/mmcblk0rpmb: read failed after 0 of 4096 at 0: Input/output error 0 logical volume(s) in volume group "sailfish" now active Done Press [Enter] to return to recovery menu...So you have network connectivity? I'd try to repeat the update via
or via sfos-update from openrepos.
Do NOT have any openrepos repos enabled while trying to repeat the update. After installing an application disable them temporarily using
nephros ( 2020-05-07 16:01:06 +0300 )editssu dr <reponame>until you are up and running again.A more general approach of fixing e.g. that jolla-notes problem would be:
lists the package owning that file. Note it down.
Then do a
which lists all the libraries it needs to run. Note them as well and for each of them again do a
rpm -qf <path>.Now you have a list of packages. Reinstall them using
nephros ( 2020-05-07 16:04:41 +0300 )editMany thanks nephros! You saved my day!
It probably happened root had insufficient space when I used the builtin update.
I did 1.) sfos-openrepos wget from openrepos, then rpm -Uhv then run It said that I have probably not enough space 2.) made space du -x -a / > /home/nemo/Documents/filelist.csv then opened in LibreOffice and sorted Found out that app Stellarium, Sailfish Scanner and Android Here WeGo maps eate a lot - removed (rm) 3.) ran sfos-openrepos 4.) rebooted and ran post_sfos-upgrade
Perfect!
Notes: 1.) Backup still don't work Did as you suggested but getting always Package not found e.g. pkcon install glib2-2.62.4+git1-1.5.1.jolla.armv7hl 2.) /dev/mmcblk0rpmb: read failed after 0 of 4096 That was the USB, no ?
tomtom ( 2020-05-07 18:41:49 +0300 )edit