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

Failed update to 2.1.1, now user session won't start (no GUI)

asked 2017-09-01 13:28:03 +0300

Camil B gravatar image

updated 2017-09-01 14:24:12 +0300

I started the normal update process, through Settings, which said finished after an hour with "Cannot update at the time". The device remained in a weird state. When turned on, it will show the Jolla logo, load for a while then turn black. WLAN connects automatically and SSH is on, so I could connect to the phone.

I tried this:

# systemctl --state=failed
UNIT                           LOAD   ACTIVE SUB    DESCRIPTION
mount-sd@mmcblk1.service       loaded failed failed Handle sdcard
start-user-session.service     loaded failed failed Start User Session
systemd-tmpfiles-setup.service loaded failed failed Create Volatile Files and Directories
user@100000.service            loaded failed failed User Manager for UID 100000

I tried version --dup too:

# version --dup
REFRESHING CACHE AND DOWNLOADING PACKAGES
QDBusConnection: name 'org.freedesktop.PackageKit' had owner '' but we thought it was ':1.47'
Refreshing: 84%
Message: adaptation0: Store credentials not received. Not connected to D-Bus server
aliendalvik: Store credentials not received. Not connected to D-Bus server
customer-jolla: Store credentials not received. Not connected to D-Bus server
eas: Store credentials not received. Not connected to D-Bus server
store: [|] Valid metadata not found at specified URL(s)
xt9: Store credentials not received. Not connected to D-Bus server

Resolving: 84%
Error: nothing provides jolla-devicelock-daemon-encpartition needed by pattern:jolla-hw-adaptation-sbj-0.9.13-10.62.17.jolla.noarch
Finished transaction (status=2, runtime=24966ms)
UPGRADE NOT COMPLETE - Retry 1 of 9

Obviously, version --dup needs a user session to login to the Jolla server. I tried systemctl start user@100000, which won't work without devel-su (and I forgot the password).

What can I do, other than a full reset? Can I somehow retrieve my password and manually start a user session? Note that I connect to SSH with keys, not with password.

EDIT: I manually changed the devel-su password in the recovery mode shell. Now I have access to better logs. This comes from journalctl -xe, after running systemctl start user@100000:

Sep 01 14:12:33 jollaphone systemd[1]: user@100000.service: Failed to load environment files: No such file or directory
Sep 01 14:12:33 jollaphone systemd[1]: user@100000.service: Failed to run 'start-pre' task: No such file or directory
Sep 01 14:12:33 jollaphone systemd[1]: Failed to start User Manager for UID 100000.
-- Subject: Unit user@100000.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit user@100000.service has failed.
-- 
-- The result is failed.
Sep 01 14:12:33 jollaphone systemd[1]: user@100000.service: Unit entered failed state.
Sep 01 14:12:33 jollaphone systemd[1]: user@100000.service: Failed with result 'resources'.
Sep 01 14:12:34 jollaphone systemd[1]: user@100000.service: Service hold-off time over, scheduling restart.
Sep 01 14:12:34 jollaphone systemd[1]: Stopped User Manager for UID 100000.
-- Subject: Unit user@100000.service has finished shutting down

Comments

Not knowing the devel-su is incredibly annoying: I can't even journalctl. Is there a way to set the password for nemo / devel-su if I'm already logged in as nemo using my SSH keys?

Camil B ( 2017-09-01 13:47:06 +0300 )

I had similar lproblem with update to 2.1.1 (2.1.1.26) but did not check if I could connect to the phone. I reset my phone to factory settings through recovery mode. Got instructions from https://jolla.zendesk.com/hc/fi/articles/204709607-Jolla-puhelin-Miten-k%C3%A4yt%C3%A4n-Recovery-Modea-

Hannu ( 2017-09-01 17:08:36 +0300 )

I also have problem with updating and Store credentials. At first, I didn't have any problem with user@10000, but later on, it wouldn't start due to some missing socket.

-- Unit user@100000.service has begun starting up.
sep 03 16:17:36 Jolla systemd[22046]: pam_unix(systemd-user:session): session opened for user nemo by (uid=0)
sep 03 16:17:36 Jolla validate-user[22046]: /usr/lib/startup/validate-user checking  100000
sep 03 16:17:36 Jolla kernel: systemd(1) send signal 9 to (sd-pam)(22047)
sep 03 16:17:36 Jolla kernel: systemd(1) send signal 9 to (sd-pam)(22047)
sep 03 16:17:36 Jolla systemd[22053]: pam_unix(systemd-user:session): session opened for user nemo by (uid=0)
sep 03 16:17:36 Jolla systemd[22053]: Failed to open private bus connection: Failed to connect to socket /run/user/100000/dbus/user_bus_socket: No such file or directory
sep 03 16:17:36 Jolla systemd[22053]: Failed to create private D-Bus server: Failed to bind socket "/run/user/100000/systemd/private": No such file or directory
sep 03 16:17:36 Jolla systemd[22053]: Failed to allocate manager object: Input/output error
sep 03 16:17:36 Jolla systemd[22054]: pam_unix(systemd-user:session): session closed for user nemo
sep 03 16:17:36 Jolla systemd[1]: user@100000.service: main process exited, code=exited, status=1/FAILURE
sep 03 16:17:36 Jolla systemd[22056]: pam_unix(systemd-user:session): session opened for user nemo by (uid=0)
sep 03 16:17:36 Jolla systemctl[22056]: Failed to get D-Bus connection: Failed to connect to socket /run/user/100000/dbus/user_bus_socket: Filen eller katalogen finns inte
sep 03 16:17:36 Jolla systemd[22057]: pam_unix(systemd-user:session): session closed for user nemo
sep 03 16:17:36 Jolla systemd[1]: user@100000.service: control process exited, code=exited status=1
sep 03 16:17:36 Jolla systemd[1]: Failed to start User Manager for UID 100000.
-- Subject: Unit user@100000.service has failed
Vilkz ( 2017-09-03 17:19:39 +0300 )
add a comment

2 Answers

Sort by » oldest newest most voted
1

answered 2017-10-11 02:42:08 +0300

rzr gravatar image

Kiiminkijoki failed on my JP1 too ...

link

Comments

Same here, "update cannot be completed, please try at another time" message, select ok, phone stuck in a boot loop.

JonS ( 2017-10-11 19:42:55 +0300 )

Me too. I had the progress bar stuck, pulled the battery, now it's half-working. I have ssh, though. Created this issue. Update: actually, if you swipe to unlock, the gui shows up and is usable. Also, update can be completed using version --dup in console or via ssh, but the spinner issue stays.

articice ( 2017-10-20 11:50:31 +0300 )
add a comment
0

answered 2017-11-13 01:52:49 +0300

gaute gravatar image

updated 2017-11-13 02:27:24 +0300

I had this problem and discarded the phone. Now I picked it back up and made another attempt. I add description of the steps here, in case others find this page. I am trying to reconstruct work done over several days, so there may be inaccuracies.

ssh to the phone was possible. My aim was to make version --dup work. I attacked this mainly on two fronts.

Running systemd user session

Running it manually gave some cgroup permission error message, so I did (quite haphazardly) as root:

chmod -R a+rwx `mount | grep cgroup | cut -d" " -f3`

Then as nemo:

/lib/systemd/systemd --user --unit=default.target

Installing extra packages

version --dup threw these errors about jolla-devicelock. On another jolla phone (I have two) I downloaded:

  • jolla-devicelock-daemon-encpartition-0.2.4.6-10.37.1.jolla.armv7hl.rpm
  • jolla-devicelock-plugin-encpartition-0.2.4.6-10.37.1.jolla.armv7hl.rpm
  • nemo-qml-plugin-devicelock-0.2.2.3-1.9.2.armv7hl.rpm

Using commands like: pkcon download /tmp jolla-devicelock-daemon-encpartition

I'm sure you can get these files otherwise. Possibly even on the sick phone. Anyway, I put them up here: http://files.idrift.no/gaute/jollarpms/

I transferred them two the sick phone, and ran:

rpm -i --force jolla-devicelock-daemon-encpartition-0.2.4.6-10.37.1.jolla.armv7hl.rpm jolla-devicelock-plugin-encpartition-0.2.4.6-10.37.1.jolla.armv7hl.rpm nemo-qml-plugin-devicelock-0.2.2.3-1.9.2.armv7hl.rpm

Run version --dup

After that version --dup ran it's course. It took quite a while.

Update to 2.1.1.26 from console

This was the final step that revived the phone. Just do

devel-su
ssu re 2.1.1.26
version --dup
reboot

See here about freeing up space and rebalancing if necessary:

https://reviewjolla.blogspot.no/2017/08/sailfish-os-21126-jamsanjoki-released.html

link
add a comment
Login/Signup to Answer

Question tools

Follow
1 follower

Stats

Asked: 2017-09-01 13:28:03 +0300

Seen: 741 times

Last updated: Nov 13 '17