(tagging @Mister_Magister for this)
Thanks for the new EA, update went smooth and no issues for my Gemini.
I don’t have
libcontentaction-qt5-url-distinction installed so I don’t hink that’s it. I do have mister magisters repository enabled though. Forgot to remove it since I tested his Yottagram.
Hmm first of all it shouldn’t break anything as package wasn’t updated by jolla.
Second of all you shouldn’t remove those packages.
Third, update might be able to downgrade/upgrade it to jolla ones
Fourth, downgrade/upgrade it to jolla ones via zypper
How dare you!
@eson You didn’t need to, that was the problem – it could’ve been automatically updated with some other package using storeman.
I agree with @Mister_Magister, do not try to remove the package. If you want to play safe, “downgrade” to the official version.
OK, thanks… both of you.
I downgraded to
obexd-contentfilter-off-1.1.7-stable.noarch I don’t see any alternative package. So cannot downgrade that. Also I get the warning that it would break my system to remove
Still I get the warning I should remove these three packages.
OS upgrade went fine after downgrade those packages. Thanks again!
Not sure man i don’t use official ports
could you give me a hint, which command do the trick?
with Pkcon or zypper?
See an example for another package here: How to reinstall "original" package version?
Can’t update from 126.96.36.199 to 188.8.131.52 since although suggesting initially that the update is just 30Mb I’m now told that the download (downloaded) needs 500Mb but has only 349Mb currently available!
Not only this but having “successfully” installed 184.108.40.206 I’m being told that I need to uninstall pages of items before I update!!! Surely the change of such a minor version can’t affect so many entries!!!
How do I delete the downloaded update please and can Jolla issue an update that actually works for XA2 users please.
@ninepine: I had a similar issue initially with my XA2 when trying to update to 220.127.116.11
The memory is apparently needed for the installation - not for the download of the update. In my case, it turned out that i messed up with zypper download and downloaded some rpms in the system memory without deletuing the rpms later (thus having too little memory space).
Once I resoved that issue, the warning and hinting to removing 100+ packages disappeared. Further, I learned that in the present case I could ignore the warning.
Thanks but this is a very minor upgrade from. 0.1.45 to 0.1.48 so cannot possibly require 500mb. Maybe somebody from Jolla /Sailfish can fix this error please?
Making sure that the erroneous error messages are also removed please would also help. At the moment it seems that 18.104.22.168 needs some serious work.
I believe Sailfish updates the packages piecemeal rather than a la carte. If it’s suggesting a 500MB download, it’s downloading updates to all individual packages. Someone else can correct me on that.
An OS update is executed using the software code (and the other setup) already in the device. The new update cannot help the installation of itself! The code of the new update will be in effect only after the device restart which is done in the end of the installation.
So, if a phone has 22.214.171.124 in it then the update to 126.96.36.199 is done by running the instructions contained in the code of 188.8.131.52. Hence, if there is a problem in installing 184.108.40.206, that problem is most probably caused by something in the phone now - the changes in 220.127.116.11 do not affect at that point yet.
The download size from 18.104.22.168 to 22.214.171.124 is around 30 MB. Only the modified code packages are replaced.
I’m encountering the same issue on my Jolla Tablet, it isn’t saying it needs to download 500MB, it’s saying the device needs 500MB free space after the 30MB update is downloaded, and prevents the user from installing it.
I even enlarged the root partition on my tablet with several GBs a couple of years ago specifically because the “not enough space on root partition” problem kept showing up with every new release.
Edit: ah, wait a minute, perhaps the enlarged root partition got undone after performing a factory reset.
Edit 2: it did indeed get undone after a factory reset. Here’s a great guide to enlarging the root partition. @ninepine, if you follow this guide, you’ll be able to fix the problem.
Edit 3: well, apparently, by following the guide, my device lock code got changed, and now I can’t do anything with my tablet anymore. Great.
Someone else have problems with dynamic orientation in the last update?
I also have problems with dynamic orientation not working in android apps in 126.96.36.199.
It worked correctly in 188.8.131.52 on my XA2 plus.