Thatâs it. And Rime input method engine should be not many users.
1 Like
?
I just did the limbo and checked yaml-cpp.
It was introduced with 4.0, yes.
But it was not a dependency or at least it got not installed for 4.0, 4.1, 4.2, only in 4.3
Ah ok thatâs great, thanks. Weâll add a note about that. Hopefully this means that not many users will run into this on full release. Though I wonder if people previously upgrading with version --dup with your repo enabled might have accidentally pulled in your version instead of the official one.
Very good news if itâs not previously installed. It was added as a build dependency for 4.0.1, but I guess whatever it was used for didnât knock onto a runtime dependency until this latest version. Thanks for verifying.
2 Likes
As @peterleinchen has said, the problematic libyaml-cpp was only installed when I did the latest upgrade. I am probably the worst case scenario, as I had done previous version âdupâs on previous upgrades, and it had not been installed previously.
1 Like
And as my test device got somehow corrupted checking all ssu re and dependencies I had to reset 
And ran into this 3 (three) times with a vanilla reset X and XA2 
Absolutely not.
This lib was only introduced now with 4.0 and your version is older, right?
Thanks.
Yeah, about 3 years ago, Show home:birdzhang:rime / yaml-cpp - SailfishOS Open Build Service
2 Likes
As @dmz pointed out in another post, on the XA2 you may get the message to remove ofono-alien-binder-plugin before updating to 4.3.0.12. I got this message too. My device was updated from 4.1 to 4.2 immediately (5 minutes) before updating to 4.3, so the native packages should have been all valid and unchanged.
I didnât find any solution and decided to ignore the message. Installation had no issues. Device is running on 4.3 now.
Well done up to here!
Just a small typo in url (note missing jolla/armv7hl),
Use e.g.
https://releases.jolla.com/releases/4.3.0.12/jolla/armv7hl/oss/armv7hl/libzypp-17.26.0+git1-1.6.1.jolla.armv7hl.rpm
Something I really really struggled long time ago (and again today )
@vige
thanks for trying to move missed post(s)
but this one belongs way ahead (as you see from time stamp)
here it does not make any sense
My wifes phone (Xperia 10 Dual SIM) hangs on downloading the update:
Remove Packages:
libopusfile
ofono-alien-binder-plugin
What can I do now with this?
Old system is SFOS 4.2.0.21, but updated through many versions since 3.2 or 3.3, username still Nemo and not defaultuser. Do I have to reflash the device?
How is the CLI command to remove theese packages?
edit: found the solution,
[nemo@Sailfish ~]$ devel-su
Password:*****
[root@Sailfish nemo]# pkcon remove libopusfile
[root@Sailfish nemo]# pkcon remove ofono-alien-binder-plugin
exit
reboot
did it. After this, the update worked. Problem is solved.
Is there also a solution for regular users? I just want to make an update.
In my case I should uninstall the packages
harbour-fotokopierer
ofono-alien-binder-plugin
Is there an easier way to remove them?
I donât know what the second one is, but the first one should simply automatically uninstall itself when you install the OS update.
i ignored them an updated regardless.
came through unscathed.
Just logged in to say, that I didnât actually have any problems updating the OS but the 1st manually made boot after the update was quite interesting.
I shut my phone (xperia 10ii) down a day after the update when attending to a concert and when I tried to restart the phone after the concert I got to the 1st screen asking for my passcode. After entering the valid password/pin-code the phone just stuck showing the keyboard for the pin and a spinning wheel. I waited for a short while and then manually rebooted the phone again and the same issue happened again. This time I waited for a longer time but nothing still happened. I then restarted it for the 3rd time, gave a wrong pin on purpose, got an error message for it and then gave the right pin and the phone started normally. Go figure 
1 Like
Just to say this is something I reliably have after every update:
on first boot after the update the first LUKS unlock code is entered but the UI never (and I mean never, hours) appears.
Shutdown / restart for the second time and everything is fine.
X and XA2
1 Like
I also have the same issue on the Xperia X and 10 II, but I think itâs happened more often than only after OS updates. Sometimes it just doesnât unlock anything. You can notice the difference in the spinning wheel, too: when itâs âfakeâ unlocking, it spins smooth and fast and never goes away, and when itâs unlocking for real, it stutters a lot and quickly fades to black for the UI to appear.
After downloading the files for an UI update of my Xperia 10 II (XQ-AU52) (from version 4.2.0) to version 4.3.0, I get a message to remove or reset (âtilbakestillâ) the package âfeature-xt9â because it may create problems during the update.
I run my phone with a very basic setup with no use of Android nor do I have openrepos or anything related installed, and I never work âunder the hoodâ of the phone â so I donât know how to find and remove said file/package.
What should I do now?
Just go ahead? (I have seen others previously got same warning about said package when upgrading to 4.2.0 and then just disregarded it apparently without encountering problems later on.)
Hi there,
in my case, connman.service failed after Update to 4.3.0.12 Suomenlinna
Before update, I removed the packages listed as obstacles, except for âgit-minimalâ and âgittinâ.
However, I later noticed that I forgot to disable the repos âopenrepos-noonienâ and âchumâ .
The update itself went without interruptions, freezes or errors.
But after reboot connman.service failed and no connections are available.
Nov 12 16:03:20 Sailfish systemd[1]: connman.service: Main process exited, code=exited, status=1/FAILURE
Nov 12 16:03:20 Sailfish systemd[1]: connman.service: Failed with result 'exit-code'.
Nov 12 16:03:20 Sailfish systemd[1]: Failed to start Connection service.
Nov 12 16:03:21 Sailfish systemd[1]: connman.service: Service hold-off time over, scheduling restart.
Nov 12 16:03:21 Sailfish systemd[1]: connman.service: Start request repeated too quickly.
Nov 12 16:03:21 Sailfish systemd[1]: connman.service: Failed with result 'exit-code'.
To get a little bit more information in journal, i deactivate the row âStandardOutput=nullâ in connman.service and get this additional output:
Nov 12 16:11:00 Sailfish connmand[31780]: Unknown option --systemd
Unfortunately I couldnât get any information about the connmand option ââsystemdâ so i try to start connmand manual as daemon and without the ââsystemdâ option:
devel-su /usr/sbin/connmand -W nl80211 --nobacktrace --noplugin=wifi
This starts connmand, all connections comes up and everything works as expected, until next reboot.
Maybe someone can help me to find a solution so that connman.service can start connmand again automatically and I donât have to factory-reset or reflash my device.
Additional Information:
Update done with GUI
Device: Xperia X (F5121)
Edit:
Problem solved.
For anyone who comes across this problem:
In my case there was an old version of connman.service in â/etc/systemd/system/â.
Either I created this myself and donât remember it, or this is a holdover from a previous Sailfish version.
However, the connman.service required for this version is located in the directory â/usr/lib/systemd/system/â after deleting the outdated service â/etc/systemd/system/connman.serviceâ and a systemctl daemon-reload, connmand was able to start with systemctl restart connman.service.
My 4.1/4.2 problem with the loss of a wifi connection also killing the mobile data - requiring a restart - remains on 4.3:
2 Likes