qt5-qtsysteminfo is deprecated and intentionally removed from SFOS 4.6
1 Like
A quick update. Of course with having external repos disabled and of course not being allowed entry into aliendalvik et al with ssu register, this is the kind of thing that zypper dup
Loading repository data...
Reading installed packages...
Warning: You are about to do a distribution upgrade with all enabled repositories. Make sure these repositories are compatible before you continue. See 'man zypper' for more information about this command.
Computing distribution upgrade...
Problem: This request will break your system!
the to be installed jolla-settings-accounts-extensions-3rd-party-all-0.4.79-1.12.1.jolla.aarch64 conflicts with 'buteo-sync-plugins-social-vk' provided by the installed buteo-sync-plugins-social-vk-0.4.24-1.17.1.jolla.aarch64
Solution 1: Following actions will be done:
keep obsolete jolla-settings-accounts-extensions-3rd-party-all-0.4.71-1.11.1.jolla.aarch64
keep obsolete jolla-settings-accounts-extensions-0.4.71-1.11.1.jolla.aarch64
Solution 2: Following actions will be done:
ignore the warning of a broken system (requires:feature-jolla)
deinstallation of jolla-settings-accounts-extensions-3rd-party-all-0.4.71-1.11.1.jolla.aarch64
deinstallation of feature-jolla-0.1.8-1.5.7.jolla.noarch
Solution 3: deinstallation of buteo-sync-plugins-social-vk-0.4.24-1.17.1.jolla.aarch64
I looked behind door number three; I don’t know what buteo-sync-plugins-social-vk-0.4.24-1.17.1.jolla.aarch64 is, or why I should care, but it was a horrible ruse!
The following 4 packages are going to be REMOVED:
buteo-sync-plugins-social-vk eventsview-extensions-vk-posts jolla-gallery-extensions-vk jolla-settings-accounts-extensions-vk
For some reason “vk” sounds vaguely familiary, but looking at rpm -qi I get repos such as https://bitbucket.org/jolla/ui-jolla-gallery-extensions which are either very strictly Jolla-internal or totally dead.
There’s also gonna be 61 packages to allegedly downgrade, but I suspect this is zypper having a Linux moment because of eg. in the case of jolla-gallery-extensions-dropbox from the downgrade list:
Loading repository data...
Reading installed packages...
'jolla-gallery-extensions-dropbox' is already installed.
No update candidate for 'jolla-gallery-extensions-dropbox-0.2.14-1.2.1.jolla.aarch64'. The highest available version is already installed.
Resolving package dependencies...
Nothing to do.
Let’s see where I end up once I’ve executed this plan and got the actually bootable firmwarez onto the machine I’m currently on.
All of these mistake exit 106 (socket error? dbus again? wtf?) for politeness but RPM is the only one that actively smears something that’s not chocolate all over itself. I’m not going to uninstall RPM and hope it works out, but instead hope it works out some other way.
Forcing installation of 'rpm-4.16.1.3+git14-1.12.1.jolla.aarch64' from repository 'jolla'.
Resolving package dependencies...
The following package is going to be reinstalled:
rpm
1 package to reinstall.
Overall download size: 626.8 KiB. Already cached: 0 B. After the operation, 2.4 MiB will be freed.
Continue? [y/n/v/...? shows all options] (y): y
Retrieving: rpm-4.16.1.3+git14-1.12.1.jolla.aarch64 (jolla) (1/1), 626.8 KiB
Retrieving: rpm-4.16.1.3+git14-1.12.1.jolla.aarch64.rpm ....................................................................[done (407.8 KiB/s)]
Checking for file conflicts: .............................................................................................................[done]
warning: /home/.zypp-cache/packages/jolla/oss/aarch64/rpm-4.16.1.3+git14-1.12.1.jolla.aarch64.rpm: Header V3 RSA/SHA256 Signature, key ID 47394f
23: NOKEY
/sbin/ldconfig: relative path `1' used to build cache
warning: %postun(rpm-4.16.1.3+git14-1.12.1.jolla.aarch64) scriptlet failed, exit status 1
(1/1) Installing: rpm-4.16.1.3+git14-1.12.1.jolla.aarch64 ................................................................................[done]
Running post-transaction scripts .........................................................................................................[done]
Maybe postun is an uninstallation thing for the existing version, or something, but because I can invoke zypper download and rpm -qlp /home/.zypp-cache/packages/jolla/oss/aarch64/rpm-4.16.1.3+git14-1.12.1.jolla.aarch64.rpm I’ll defer caring until a later date, hopefully so much later I’ll end up forgetting about it.
This at least makes sense, the changelog makes mention of:
### jolla-settings-accounts
- Updated : 0.4.71-1.11.1.jolla -- 0.4.79-1.12.1.jolla
- Binaries removed : jolla-settings-accounts-extensions-vk
I completely forgot about all the changelog stuff. Thanks for that!
I got the bootloader back in, from 4.5.0.25, and after giving my security code, I get a black screen. The power button toggles the cyan LED, but nothing else visible.
The “No apps running” message is gone, but it kinda sucks that all the screen is.
What’s in the firmware? Some kernel stuff that this cannot boot unless the official Sailfish updater flashed something in there, and now my phone is still bricked until images are released? Or is there something else I’m still missing out on?
Any way to debug a Sailfish now that it’s semi-running?
1 Like
It is nice to see this new update, but I didn’t see any informations about the bug about the problem of roaming for mobile internet connection like this one. Has any one try to see if there is an improvement about it ?
1 Like
Hallo das Update lief Problemlos nur ist nun das Wetter in der Ereignisansicht weg nicht schön. Vg Jan
1 Like
Exactly the same thing is happening on mine, although the only thing I did was install the packages in the cache and remove harbour-callrecorder. It definitely connects to the internet, because I’m receiving email notifications. And now I actually managed to log into it with the file manager on my computer! But what to do next?
Hmm, while I was trying to SSH to it, the connection broke and doesn’t want to reestablish. Maybe it’s active for the first 30 seconds after boot and then something else blocks it? But it looks like we’re getting somewhere, at least. I’ll see if I can get in again after another reboot.
I have no idea. My USB mode is usually “Charging only” so no luck with accessing it as an MTP device. Likewise it won’t respond to any pings, though it’s not “Destination Host Unreachable” either.
Removing and reinserting the USB cable does chime. So I wondered if this could be something as silly as the brightness turned to sub-zero and no way to brighten it up, but trying to call the phone goes straight to voicemail.
So it’s not entirely alive either. Sigh.
Anyone?
Would you mind to post in English, as this is an international forum.
Good news! … I hope.
I’m about to be torn between this and certain obligations not related to this, so I’m not sure about my usefulness beyond the ability to reboot my phone without the aid of a volume button.
Oh yeah, and of course it’s gonna be voicemail. It never asked (at least visibly) for a PIN. It’s black after the first security code.
A reboot restores the connection! Assuming you have developer mode enabled, you can connect to your phone over WiFi immediately after it boots, then start running whatever programs necessary. I’m running version --dup right now, let’s see if it keeps going before the connection breaks again.
Hello the update ran smoothly only the weather in the event view away not nice. VG Jan
PS. That’s nice that’s an English forum so the understanding I use also the translation tools that you should try sometimes.
OMG! I’m uncharacteristically giddy about everything 
Remembering what my ssh login password is, so I don’t have to re-do the rescue boot firmware circus just to change it and everything that follows
It’s interesting to me that version --dup wanted to install 24 packages, but it must be a replacement for ssu register somehow, because I was seeing aliendalvik-related things in the list.
Then I showed the missus how bad my phone sucks because it won’t display anything after the initial security code. What followed was the sound of me getting egg on my face. The phone did show the next (IMO redundant) security code entry, and pin, albeit all with a wrong ambience.
Edit: this is glorious! Changing the ambience worked, calling the phone sounded the right ringtone, and launching the most picky Android app I’ve encountered (S-Mobiili) launched just fine.
Thanks to everyone on the forum here!
Hope these demented ramblings of mine help someone else out there.
Actually, hope more no one else encounters these issues.
And while we’re hoping: hope Jolla gets rid of “hey, so many packages look like they might be broken we’re gonna overload your brain and then die during the installation!”
Which may be unfair, maybe the script failure in callrecorder was something no one can predict, but some kind of rollback mechanism would be sweet even if user-driven downgrades weren’t officially supported…
7 Likes
version --dup had to still update quite a lot of packages. Now I’ll reboot, fingers crossed!
[root@Xperia10II-DualSIM defaultuser]# version --dup
REFRESHING CACHE AND DOWNLOADING PACKAGES
Finished transaction (status=1, runtime=84182ms)
UPGRADING SYSTEM
Finished transaction (status=1, runtime=63054ms)
FINISHING
Download (2 packages)
- harbour-audiocut;1.5.0-1;noarch;store
- harbour-papocchio;1.3.5-1;aarch64;store
Install (61 packages)
- connman-configs-sailfish;0.11.13-1.10.1.jolla;noarch;jolla
- droid-config-xqau52-bluez5;0.1.36.1-1.10.1.jolla;aarch64;adaptation0
- droid-config-xqau52-policy-settings;0.1.36.1-1.10.1.jolla;aarch64;adaptation0
- droid-config-xqau52-pulseaudio-settings;0.1.36.1-1.10.1.jolla;aarch64;adaptation0
- droid-config-xqau52-sailfish;0.1.36.1-1.10.1.jolla;noarch;adaptation0
- droid-config-xqau52;0.1.36.1-1.10.1.jolla;aarch64;adaptation0
- droid-hal-version-xqau52;1.0.0-1.4.12.jolla;aarch64;adaptation0
- harbour-audiocut;1.5.0-1;noarch;store
- harbour-fernschreiber;0.17-13;aarch64;store
- harbour-kodimote;2.2.4-1;aarch64;openrepos-ade
- harbour-papocchio;1.3.5-1;aarch64;store
- harbour-passviewer;1.6-1;aarch64;store
- jolla-calculator;1.0.10-1.5.1.jolla;aarch64;apps
- jolla-calendar;1.1.15-1.11.1.jolla;aarch64;apps
- jolla-common-configurations;0.11.13-1.10.1.jolla;noarch;jolla
- jolla-email-settings;1.1.43-1.12.1.jolla;aarch64;apps
- jolla-email;1.1.43-1.12.1.jolla;aarch64;apps
- jolla-handwriting;0.1.7-1.3.3.jolla;aarch64;xt9
- jolla-mediaplayer;1.3.13-1.7.1.jolla;aarch64;apps
- jolla-notes-settings;1.0.24-1.6.2.jolla;aarch64;apps
- jolla-notes;1.0.24-1.6.2.jolla;aarch64;apps
- jolla-xt9-cp;0.2.15-1.4.2.jolla;aarch64;xt9
- jolla-xt9;0.5.22-1.6.3.jolla;aarch64;xt9
- libjollamediaplayer;1.3.13-1.7.1.jolla;aarch64;apps
- mce-plugin-libhybris;1.14.5-1.3.1.jolla;aarch64;adaptation0
- mtp-vendor-configuration-sailfish;0.11.13-1.10.1.jolla;noarch;jolla
- ngfd-settings-sailfish;0.11.13-1.10.1.jolla;noarch;jolla
- ofono-modem-switcher-plugin;1.0.2-1.1.3.jolla;aarch64;adaptation0
- patterns-sailfish-applications;1.1.32-1.14.1.jolla;noarch;jolla
- patterns-sailfish-cellular-apps;1.1.32-1.14.1.jolla;noarch;jolla
- patterns-sailfish-consumer-generic;1.1.32-1.14.1.jolla;noarch;jolla
- patterns-sailfish-core-device;1.1.32-1.14.1.jolla;noarch;jolla
- patterns-sailfish-core;1.1.32-1.14.1.jolla;noarch;jolla
- patterns-sailfish-customer-content-default;1.1.32-1.14.1.jolla;noarch;jolla
- patterns-sailfish-device-adaptation-pdx201;0.1.36.1-1.10.1.jolla;aarch64;adaptation0
- patterns-sailfish-device-configuration-common-xqau52;0.1.36.1-1.10.1.jolla;aarch64;adaptation0
- patterns-sailfish-device-configuration-xqau52;0.1.36.1-1.10.1.jolla;aarch64;adaptation0
- patterns-sailfish-mw;1.1.32-1.14.1.jolla;noarch;jolla
- patterns-sailfish-ui;1.1.32-1.14.1.jolla;noarch;jolla
- pulseaudio-modules-droid-hidl;1.5.0-1.3.5.jolla;aarch64;adaptation0
- pulseaudio-modules-droid-jb2q-common;14.2.102-1.5.1.jolla;aarch64;adaptation0
- pulseaudio-modules-droid-jb2q;14.2.102-1.5.1.jolla;aarch64;adaptation0
- qt5-qpa-hwcomposer-plugin;5.6.2.24-1.4.2.jolla;aarch64;adaptation0
- sailfish-audiorecorder;0.1.9-1.4.1.jolla;aarch64;apps
- sailfish-components-calendar-qt5;1.1.15-1.11.1.jolla;aarch64;apps
- sailfish-content-ambiences-default-about;1.0.12-1.2.5.jolla;noarch;jolla
- sailfish-content-ambiences-default-airy;1.0.12-1.2.5.jolla;noarch;jolla
- sailfish-content-ambiences-default-community;1.0.12-1.2.5.jolla;noarch;jolla
- sailfish-content-ambiences-default-default-ambience;1.0.12-1.2.5.jolla;noarch;jolla
- sailfish-content-ambiences-default-favorites;1.0.12-1.2.5.jolla;noarch;jolla
- sailfish-content-ambiences-default-flow;1.0.12-1.2.5.jolla;noarch;jolla
- sailfish-content-ambiences-default-glacial;1.0.12-1.2.5.jolla;noarch;jolla
- sailfish-content-ambiences-default-party;1.0.12-1.2.5.jolla;noarch;jolla
- sailfish-content-ambiences-default-rolling;1.0.12-1.2.5.jolla;noarch;jolla
- sailfish-content-ambiences-default-sailing;1.0.12-1.2.5.jolla;noarch;jolla
- sailfish-content-ambiences-default-silent;1.0.12-1.2.5.jolla;noarch;jolla
- sailfish-content-ambiences-default-work;1.0.12-1.2.5.jolla;noarch;jolla
- sailfish-content-ambiences-default;1.0.12-1.2.5.jolla;noarch;jolla
- sailfish-office;1.6.8-1.8.3.jolla;aarch64;apps
- sailfish-utilities;0.1.21-1.8.1.jolla;aarch64;apps
- sailfish-weather;1.0.16-1.9.1.jolla;aarch64;apps
REBOOT NOW unless you need to investigate update
issues or know what you are doing (or both).
All bugs encountered until reboot are features.
YES! YES! YES!
A very short summary if anyone else is (still) stuck in the same situation, doesn’t feel like going through the backup-reflash-restore backup route, and had already enabled developer mode prior to updating. If you don’t know how to do some or all of these things, I think all information is in the posts above (starting at post 124) and it’s best if you read them through first.
- open recovery mode (install it via flashboot first, depending on your device)
- use the shell, not ssh
- mount /home according to the instructions here
- remove all traces of harbour-callrecorder and osm-scout-server
- install all of the packages in /home/.pk-zypp-dist-upgrade-cache (it’s a bit of trial and error which ones you need to install first, but you can always upgrade all of the packages in a specific directory at the same time)
- you can install all packages in a directory with this command:
find -name \*rpm | xargs rpm -Uvh - (reinstall the normal boot mode with flashboot, depending on your device)
- reboot the phone normally, at this point it should no longer show the white screens with “No apps running” but stay completely black
- connect your phone to a charger - if you hear the bell, you know you’re on the right track (or if you hear an email notification or whatever native Sailfish notification that only needs Wi-Fi)
- immediately ssh into your phone, run “ssu re 4.6.0.11” and “version --dup” (if you have it installed, temporarily disable the chum repo first, otherwise you’ll get some errors)
- run “reboot”
Your phone should now reboot into a fully working 4.6.0.11 installation, only the ambience will have been reset to a default ambience.
8 Likes
Da gibt es eine Anleitung hier im Forum wie es über das Terminal wiederhergestellt werden kann. Bei mir hat das auch geklappt.
Unfortunately 4.6.0: Android 11 Display » Dark theme built-in scheduler doesn't work, why? has not improved, yet. Still curious why App Support can’t use the timing mechanisms there.