Update to 2.0.5 - inconsistencies pkcon vs version vs store updates vs system update
asked 2016-12-03 00:20:58 +0300
[Edited for readability]
Updated Jolla1 from 2.0.4, but faced a set of problems detailed at the end of the post.
The update was performed with version --dup after various GUI failures that left the phone half updated.
I still have two problems:
- Currently the phone works, is updated, but when checking for updates the settings GUI displays "Waiting for connection..." despite being connected (no matter if WLAN or WIFI) , and silently aborts after a while.
- The system displays a "System update/ v2.0.5 available" - but that's the version already running. Is this related to the above point?
Question: How to solve these problems?
Edit 20161207: I was suspecting a problem cache => forced the reload of the cache with zypper ref -f.
version --dup says nothing to update.
zypper dup instead asked to:
- install a new "pattern" (?): jolla-mw
- remove a package: upower
Answered yes, but it did nothing. After reboot, same steps have given the same result.
Sequence of the upgrade
- Check if all up to date: updates for my apps in Jolla store. HereWeGo not listed at all (despite installed a while ago with Store app!)
- terminal =>
pkcon refresh, thenpkcon update=>all up to date. - update via gui(settings) to 2.0.5 => failed with a generic GUI message (no details), needed to reboot. Tried once or twice, re-download, upgrade failure, reboot. Nothing special spotted in logs.
pkcon refresh, thenpkcon updateagain => all up to date (expectedly).version --dup=> gets and install updates for sailfish maps and ytplayer. Reboot, hardlock with red led => battery removal.- new attempt to update via gui(settings) => starts, reboots after cca 30s
- still 2.0.4.
version --dup=> starts what seems to be the upgrade => many packages after, reboot. - finally 2.0.5. terminal => pkcon get-updates => shows many things to update. wtf
version --dupapparently does nothing ( "no updates, try later" etc message)pkcon get-updates=> shows all up to date. wtf 2 (nothing seemed installed between 8 and 10)
Same problem here :-(
lupastro ( 2016-12-07 15:44:47 +0300 )editSilly question, did you set the version with ssu before you version --dup? The version is not set by the upgrade notification you need to set it by hand. Using pkcon or zypper to upgrade can render your device a brick, just so you know. And if all still fails, did you recreate your Jolla Account in Settings-Accounts yet?
chemist ( 2016-12-08 11:26:10 +0300 )edit@chemist I did it -several times-, but nothing changed.
lupastro ( 2016-12-08 17:17:23 +0300 )edit@chemist: I haven't set the version with ssu. The purpose of step 5 above was to make sure that the2.0.4 version was up to date ( I was suspecting some non-updated packages for the upgrade failures)
Indeed that allowed to move a bit further and actually start the upgrade, but crashed and rebooted.
Lucky me, I could log in and version --dup (step 7) did what seemed to be the upgrade continuation.
Yet I think some of the installed packages are actually broken. Go figure which....
Thinking out loud, can I see the timestamp of the package installation? I could see which was installed around the crash and attempt reinstalling it.
rtr2001 ( 2016-12-12 21:17:19 +0300 )editWhat does happen when you actually set the version with ssu? Never (2./4.)! If there are other repos active than Jolla's you might get your device in limbo. What version --dup does without setting newer version with ssu, is just as simple as it rechecks dependencies of the current version and installs those. (8.)+(9.) is normal, that is how it should be and also why you may brick it by (4.). do pkcon refresh, set new version with ssu, version --dup - if there is any single error in pkcon refresh, do not proceed! Reset your Jolla account in Settings-GUI, then try again. If there are still errors, let us know here.
chemist ( 2016-12-13 10:58:24 +0300 )edit