We have moved to a new Sailfish OS Forum. Please start new discussions there.

Revision history [back]

click to hide/show revision 1
initial version

posted 2016-12-03 00:20:58 +0200

Update to 2.0.5 - inconsistencies pkcon vs version vs store updates vs system update

Updated Jolla1 from 2.0.4, but faced a set of problems, here's the sequence:

  1. Jolla store shows no updates for my apps. It doesn't display HereWeGo (despite installed a while ago with store app!)
  2. terminal => pkcon refresh, then pkcon update =>all up to date.
  3. update via gui(settings) to 2.0.5 => failed, needed to reboot. Some loops here, with failed installs, re-download, upgrade failure, reboot. Nothing helpfull ( for me) in logs.
  4. pkcon refresh, then pkcon update =>all up to date.
  5. version --dup => gets and install updates for sailfish maps and ytplayer. Reboot, hardlock with red led => battery remmoval reboot.
  6. update via gui(settings) to 2.0.5 => starts, reboots after cca 30s
  7. still 2.0.4. system --dup => starts what seems to be the upgrade => many packages after, reboot .
  8. finally 2.0.5. terminal => pkcon get-updates => shows many things to update. wtf
  9. version --dup apparently does nothing, no updates - "try later"
  10. pkcon get-updates => shows all up to date. wtf 2 (nothing seemed installed between 8 and 10)

I ended up by upgrading, but not exactly smooth.

I really find this unelegant as compared to dpkg & apt in debian ( never faced similar issues with debian packages).

All in one: which app/servicecentralises the packages, system versions, etc? there are few applications, each seems to have its idea about who's to update and who not (version, pkcon/zyper, jolla store) - yet some parts overlap in mysterious ways.

Things can be kept together with "version" & pkcon/zyppr (although unclear who does what). But Jolla Store application seems pretty useless/broken, never shows anything to update, HereWeGo just disappeared at some point.

Or am I doing something wrong?

Update to 2.0.5 - inconsistencies pkcon vs version vs store updates vs system update

[Edited for readability] Updated Jolla1 from 2.0.4, but faced a set of problems, here's the sequence: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:

  1. 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.
  2. 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?

Sequence of the upgrade

  1. Check if all up to date: updates for my apps in Jolla store shows no updates for my apps. It doesn't display store. HereWeGo not listed at all (despite installed a while ago with store Store app!)
  2. terminal => pkcon refresh, pkcon refresh, then pkcon update pkcon update =>all up to date.
  3. update via gui(settings) to 2.0.5 => failed, failed with a generic GUI message (no details), needed to reboot. Some loops here, with failed installs, Tried once or twice, re-download, upgrade failure, reboot. Nothing helpfull ( for me) special spotted in logs.
  4. pkcon refresh, pkcon refresh, then pkcon update =>all pkcon update again => all up to date.
  5. version --dup date (expectedly).
  6. version --dup => gets and install updates for sailfish maps and ytplayer. Reboot, hardlock with red led => battery remmoval reboot.
  7. removal.
  8. new attempt to update via gui(settings) to 2.0.5 => starts, reboots after cca 30s
  9. still 2.0.4. system --dup version --dup => starts what seems to be the upgrade => many packages after, reboot .reboot.
  10. finally 2.0.5. terminal => pkcon get-updates => shows many things to update. wtf
  11. version --dup wtf
  12. version --dup apparently does nothing, no updates - "try later"
  13. pkcon get-updates nothing ( "no updates, try later" etc message)
  14. pkcon get-updates => shows all up to date. wtf 2 (nothing seemed installed between 8 and 10)

I ended up by upgrading, but not exactly smooth.

I really find this unelegant as compared to dpkg & apt in debian ( never faced similar issues with debian packages).

All in one: which app/servicecentralises the packages, system versions, etc? there are few applications, each seems to have its idea about who's to update and who not (version, pkcon/zyper, jolla store) - yet some parts overlap in mysterious ways.

Things can be kept together with "version" & pkcon/zyppr (although unclear who does what). But Jolla Store application seems pretty useless/broken, never shows anything to update, HereWeGo just disappeared at some point.

Or am I doing something wrong?

Update to 2.0.5 - inconsistencies pkcon vs version vs store updates vs system update

[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:

  1. 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.
  2. 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

  1. 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!)
  2. terminal => pkcon refresh, then pkcon update =>all up to date.
  3. 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.
  4. pkcon refresh, then pkcon update again => all up to date (expectedly).
  5. version --dup => gets and install updates for sailfish maps and ytplayer. Reboot, hardlock with red led => battery removal.
  6. new attempt to update via gui(settings) => starts, reboots after cca 30s
  7. still 2.0.4. version --dup => starts what seems to be the upgrade => many packages after, reboot.
  8. finally 2.0.5. terminal => pkcon get-updates => shows many things to update. wtf
  9. version --dup apparently does nothing ( "no updates, try later" etc message)
  10. pkcon get-updates => shows all up to date. wtf 2 (nothing seemed installed between 8 and 10)