No GUI after 1.1.4 update [answered]

asked 2015-05-05 00:12:44 +0300

Blizzz gravatar image

updated 2015-05-05 03:03:05 +0300

Updating did not go well for me. First, I downloaded and installed the update. Then after boot, all core icons were missing. In the system settings I was offered another update. I did this, but now after booting the screen stays black. 5 times the LED is flashing green rapidly. Then it is off as well as the screen.

Fortunately, Wifi and SSH is working. In the log i found messages like

unknown:0 - Failed to create display (Connection refused)

TLD;DR: SSHing via wifi and repeatedly running version --dup works eventually. Bring patience with you. You may need or need not run ssu re 1.1.4.29 once before, I did it, but I cannot say whether it's a must.

Now, I am still fumbling around without having much of a clue. Trying to update with pkcon…

Be careful.

UPDATE 1: pkconf-refresh outputs

Message: connection-refused: adaptation0: Store credentials not received. Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. adaptation1: Store credentials not received. Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. aliendalvik: Store credentials not received. Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. eas: Store credentials not received. Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. store: [|] Valid metadata not found at specified URL(s) xt9: Store credentials not received. Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

Does not sound good, right?

UPDATE 2: seems like the above was my fault. trying to update now using version --dup.

UPDATE 3: upgrade in running. On about 30% the screen comes to live and shows the pin lock. Gorgeous! I wait until i am completely done.

UPDATE 4: still not there:

version --dup  
REFRESHING CACHE
Refreshing: 91%
Message: adaptation0: Store credentials not received. Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
adaptation1: Store credentials not received. Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
aliendalvik: Store credentials not received. Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
eas: Store credentials not received. Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
store: [|] Valid metadata not found at specified URL(s)
xt9: Store credentials not received. Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

Finished transaction (status=1, runtime=254593ms)
UPGRADING SYSTEM
Finished: 68% (remaining: 384s)
Error: Installation aborted by user

Finished transaction (status=2, runtime=1318210ms)
UPGRADE NOT COMPLETE - Retry 1 of 3
Waiting 1 seconds before retry.
REFRESHING CACHE
Refreshing: 0%
Error: Authentication failed (is SSU set up correctly?)
Finished transaction (status=2, runtime=42202ms)
UPGRADE NOT COMPLETE - Retry 2 of 3
Waiting 3 seconds before retry.
REFRESHING CACHE
Finished transaction (status=1, runtime=102295ms)
UPGRADING SYSTEM
Installing: 4%
Error: Installation aborted by user

Finished transaction (status=2, runtime=47245ms)
UPGRADE NOT COMPLETE - Retry 3 of 3
Waiting 5 seconds before retry.
REFRESHING CACHE
Finished transaction (status=1, runtime=276875ms)
UPGRADING SYSTEM
Finished: 1%
Error: Installation aborted by user

Finished transaction (status=2, runtime=12889ms)
FINISHING

[…]

The upgrade could NOT be finished. Make sure you have
a working Internet Connection and SSU is propertly set up. In
case the repos are changing rapidly (e.g. during development),
just restarting the upgrade might fix the issue.

Will retry …

UPDATE 5:

# version --dup
REFRESHING CACHE
[W] QDBusConnectionPrivate::serviceOwnerChangedNoLock:1280 - QDBusConnection: name 'org.freedesktop.PackageKit' had owner '' but we thought it was ':1.661'
Finished transaction (status=1, runtime=94038ms)
UPGRADING SYSTEM
Finished: 45% (remaining: 173s)
Error: Installation aborted by user

Finished transaction (status=2, runtime=308597ms)
UPGRADE NOT COMPLETE - Retry 1 of 3
Waiting 1 seconds before retry.
REFRESHING CACHE
Refreshing: 91% (remaining: 5s)
Message: adaptation0: Store credentials not received. Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
adaptation1: Store credentials not received. Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
aliendalvik: Store credentials not received. Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
eas: Store credentials not received. Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
store: Store credentials not received. Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
xt9: Store credentials not received. Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

Finished transaction (status=1, runtime=205845ms)
UPGRADING SYSTEM
Finished: 2%
Error: Installation aborted by user

Finished transaction (status=2, runtime=20921ms)
UPGRADE NOT COMPLETE - Retry 2 of 3
Waiting 3 seconds before retry.
REFRESHING CACHE
Refreshing: 91% (remaining: 5s)
Message: adaptation0: Store credentials not received. Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
adaptation1: Store credentials not received. Activation of com.jolla.jollastore timed out
aliendalvik: Store credentials not received. Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
eas: Store credentials not received. Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
store: Store credentials not received. Activation of com.jolla.jollastore timed out
xt9: Store credentials not received. Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

Finished transaction (status=1, runtime=187432ms)
UPGRADING SYSTEM
Finished: 2%
Error: Installation aborted by user

Finished transaction (status=2, runtime=41963ms)
UPGRADE NOT COMPLETE - Retry 3 of 3
Waiting 5 seconds before retry.
REFRESHING CACHE
Refreshing: 91% (remaining: 5s)
Message: adaptation0: Store credentials not received. Activation of com.jolla.jollastore timed out
adaptation1: Store credentials not received. Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
aliendalvik: Store credentials not received. Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
eas: Store credentials not received. Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
store: Store credentials not received. Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
xt9: Store credentials not received. Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

Finished transaction (status=1, runtime=221922ms)
UPGRADING SYSTEM
Finished: 2%
Error: Installation aborted by user

Finished transaction (status=2, runtime=37557ms)
FINISHING

Install (34 packages)
[…]

The upgrade could NOT be finished. Make sure you have
a working Internet Connection and SSU is propertly set up. In
case the repos are changing rapidly (e.g. during development),
just restarting the upgrade might fix the issue.

Looks similar, but other packages were installed. Is it going bit by bit now?

UPDATE 6:

After another two runs (and when I was ready to leave it and go to bed finally, it is 2am), the upgrade seems to be completed:

REBOOT NOW unless you need to investigate update issues or know what you are doing (or both).

A reboot succeed, i can enter the pin code. I see my background and the loading indicator. After a bit, boot up is done (well, i guess some stuff is working in the background, as it is a bit sluggish, but OK). All icons are there. Settings tell me I am up to date. Awesome. Seems to be good now. Good night.

edit retag flag offensive reopen delete

The question has been closed for the following reason "the question is answered, an answer was accepted" by Blizzz
close date 2015-05-05 03:03:24.630772

Comments

I have the exact same issue with store credentials not found, on the same packages. However, I haven't had any luck repeating "version --dup" so far. I did it like 5 times I think, with 3 automatic retries in case of failure, but I still have the aborted upgrade problem.

Kabouik ( 2015-05-07 19:30:24 +0300 )edit

@Kabouik what was the output? Where new packages (i.e. different than before) installed successfully? The whole action was running for me about 2-3 hours.

Blizzz ( 2015-05-07 21:04:08 +0300 )edit

I don't think there was any package installed. Some where downloaded, but nothing installs because version --dup always fails refreshing (store credetnial issue) adaptation0, adaptation1, aliendalvik, eas and xt9, and consequently the "upgrading" step is aborted each time. I've tried doing like 10 more version --dup attempts since yesterday, plus the retries that are done automatically in each attempt.

I have a working internet connection on the Jolla through Internet sharing (pings are successful), and anyway in some (not all) attempts, the version --dup was able to download packages, but the upgrade was aborted at 0% each time I tried.

Thanks to Coderus' help, I've tried removing my Jolla account, uninstalling the corresponding package, reenabling the account, rebooting, resetting ssu, nothing fixed the "store credentials" issue. Note that when I launch the store client, it tells me I have no Jolla account and offers me to connect to one. If I do that, it will add another identical account, but then it will still tell me I have no account, though they are tagged as "Active" in Settings/Accounts.

I don't know what to do now. :/

Kabouik ( 2015-05-08 15:24:09 +0300 )edit

How long should I wait when after typing

version --dup

it has been REFRESHING CACHE for 5 hours now? How long it should normally take? My first attempt now.

Hente ( 2015-05-12 17:26:58 +0300 )edit