BUG : 2.0.4.14 upgrade fails
With "Installation aborted by user", every time. Anyone else experiencing this?
Oct 20 09:42:30 Sailfish statefs[560]: Cellular_interfaces=( CallBarring , CallForwarding , ConnectionManager , MessageManager , MessageWaiting , Phonebook , PushNotification , SimManager , SmartMessaging , SimToolkit , VoiceCallManager , ExtSimInfo , )
Oct 20 09:42:30 Sailfish statefs[560]: Reset cellular network properties
Oct 20 09:42:30 Sailfish statefs[560]: Cellular status Searching -> Disabled
Oct 20 09:42:30 Sailfish statefs[560]: Reset properties
Oct 20 09:42:30 Sailfish store-client[8166]: [D] PackageHandler::slotUpgradeProgress:750 - void PackageHandler::slotUpgradeProgress(int) 10
Oct 20 09:42:30 Sailfish store-client[8166]: [D] Package::DistUpgradeTransactionPkgKit::slotPackage:179 - void Package::DistUpgradeTransactionPkgKit::slotPackage(PackageKit::Transaction::Info, const QString&, const QString&) 10 "harbour-debota;0.50-164;armv7hl;store" "QuickBar"
Oct 20 09:42:30 Sailfish store-client[8166]: [D] DBusConnector::storeCredentials:560 - void DBusConnector::storeCredentials(const QDBusMessage&)
Oct 20 09:42:30 Sailfish store-client[8166]: [D] Package::DistUpgradeTransactionPkgKit::slotTransactionError:158 - void Package::DistUpgradeTransactionPkgKit::slotTransactionError(PackageKit::Transaction::Error, const QString&) 4 "Installation aborted by user
"
Oct 20 09:42:30 Sailfish mce[531]: modules/display.c: mdy_datapipe_packagekit_locked_cb(): packagekit_locked = 0
Oct 20 09:42:30 Sailfish store-client[8166]: [D] Package::DistUpgradeTransactionPkgKit::slotTransactionFinished:119 - void Package::DistUpgradeTransactionPkgKit::slotTransactionFinished(PackageKit::Transaction::Exit, uint) 2 5159
Oct 20 09:42:30 Sailfish store-client[8166]: [D] PackageHandler::slotUpgradeFailure:775 - void PackageHandler::slotUpgradeFailure(const QString&) "Installation aborted by user
"
Oct 20 09:42:30 Sailfish store-client[8166]: [D] expression for onOsUpdateResult:56 - System upgrade failed!
Oct 20 09:42:30 Sailfish store-client[8166]: [D] Package::RepositoryTransactionPkgKit::slotWrappedTransactionFailure:306 - Wrapped transaction failed: "Installation aborted by user
"
Oct 20 09:42:30 Sailfish store-client[8166]: [D] Package::RepositoryTransactionPkgKit::restoreSsuVersion:246 - Resetting ssu version
Oct 20 09:42:30 Sailfish store-client[8166]: [D] Package::RepositoryTransactionPkgKit::setSsuVersion:211 - void Package::RepositoryTransactionPkgKit::setSsuVersion(const QString&) new version "2.0.4.13" current version "2.0.4.14"
Oct 20 09:42:30 Sailfish store-client[8166]: [D] Package::RepositoryTransactionPkgKit::setSsuVersion:216 - changing SSU release: "2.0.4.13"
Oct 20 09:42:30 Sailfish store-client[8166]: [D] Package::DistUpgradeTransactionPkgKit::~DistUpgradeTransactionPkgKit:39 - virtual Package::DistUpgradeTransactionPkgKit::~DistUpgradeTransactionPkgKit()
Oct 20 09:44:25 Sailfish dbus-daemon[933]: Failed to activate service 'org.maliit.server': timed out
Oct 20 09:44:29 Sailfish dbus-daemon[933]: Activating via systemd: service name='org.maliit.server' unit='maliit-server.service'
Oct 20 09:44:29 Sailfish systemd[722]: Started The lipstick UI.
Oct 20 09:44:29 Sailfish systemd[722]: Starting The Maliit server...
Oct 20 09:44:29 Sailfish invoker[8352]: CRITICAL: Failed to create display (No such file or directory)
Oct 20 09:44:29 Sailfish mapplauncherd[8228]: Boosted process (pid=8260) exited with status 1
Oct 20 09:44:29 Sailfish invoker[8352]: invoker: Invoking execution: '/usr/bin/maliit-server'
Oct 20 09:44:29 Sailfish systemd[722]: maliit-server.service: main process exited, code=exited, status=1/FAILURE
Oct 20 09:44:29 Sailfish systemd[722]: Failed to start The Maliit server.
Oct 20 09:44:29 Sailfish systemd[722]: Unit maliit-server.service entered failed state.
Thanks! Pardon the obvious, but the question manifests spontaneously : why would a system upgrade trigger a store update?
tortoisedoc ( 2016-10-20 11:52:37 +0300 )editIt doesn't. But you are lucky enough that an update app in Store showed up between your download of the OS update and selecting 'Install'.
xfade ( 2016-10-20 11:56:13 +0300 )edit@xfade : happy me (not). I assume you are talking about an update app notification? BTW the app in question, im running a more recent (development) version on my JollaC.
tortoisedoc ( 2016-10-20 11:58:40 +0300 )editduring dist-upgrade, zypper tries to downgrade your app to the one it knows from Store. So to get out of this situation you should probably uninstall the app from store, so that it isn't listed in that repostory. Still a bug, but at least that would get you out of this situation.
xfade ( 2016-10-20 12:18:09 +0300 )edit@xfade : thanks, that clarifies; still, it sounds weird that I get a notification for a version which is older of what I have installed (i currently run 0.63 development ver of Quickbar); Btw the current version available in harbour is 0.62-188
tortoisedoc ( 2016-10-20 12:53:37 +0300 )editHave the same problem with updating Jolla 1. Yesterday I set the phone to factory sets and began to tune up ones more. Before the reset, OS was updated to 2.0.4.14 and work normally. The updating process was stopped on Saimaa (the factory release - Tahkalampi): problem with Store ("Проблема с магазином. Невозможно определить размер файла" on russian). Using CLI (SSU & VERSION) the phone was update to 2.0.2.51. And the phone couldn't update to 2.0.4.14 yet. After these the phone was reseted to factory sets once again and update SFOS without installing any programs except SF Utilities for restoring the Store. The result was the same: Saimaa and Store's critical error. Using CLI OS was updated to Aurajoki (2.0.2.51), and 2.0.4.14 didn't download in the same reasons. Updating manually didn't help to resolved the problem, cause couldn't download one file from release repository. And now Jolla 1 works under SFOS ver. 2.0.2.51. The Store works normally (without any troubles). Waiting for comments. P.S.: Joola C was updated to SFOS ver. 2.0.4.14 in October using built-in GUI tools without any problems.
Asmir ( 2016-11-06 13:28:57 +0300 )edit