Ask / Submit
2

Blank screen after updating to 1.1.4.29 (glibc broken) [answered]

asked 2015-05-07 00:49:57 +0200

mholo65 gravatar image

updated 2015-05-07 22:28:21 +0200

heubergen gravatar image

First off, update process failed due to disk space issue which was fixed by btrfs balancing (root-and-home-disks-full-and-causing-various-problems)

After btrfs balancing was done I still wasn't able to update via GUI (could be that previous attempts had installed some packages from 1.1.4.29), so I updated from terminal.

version --dup

Everything went fine, but after restart all I have is a blank screen. WLAN is working, so I tried to SSH in to my device.


ssh nemo@xxx.xxx.xxx.xxx

Last login: Wed May  6 21:08:57 2015
id: cannot find name for user ID 100000
id: cannot find name for group ID 100000
id: cannot find name for user ID 100000
,---
| SailfishOS 1.1.4.29 (Äijänpäivänjärvi) (armv7hl)
'---

Any suggestions what to do next?

Update:

After checking juornalctl, i can see this output. Doesn't look good.

May 07 17:25:23 Jolla systemd[810]: Failed to start Generic application launch booster.
May 07 17:25:23 Jolla systemd[810]: Failed to start check for EAS accounts.
May 07 17:25:23 Jolla systemd[810]: Dependency failed for as-daemon.
May 07 17:25:23 Jolla systemd[810]: Failed to start check accounts for messageserver5.
May 07 17:25:23 Jolla systemd[810]: Dependency failed for messageserver5.
May 07 17:25:23 Jolla systemd[810]: Failed to start Telepathy mission control daemon.
May 07 17:25:23 Jolla systemd[810]: Failed to start The lipstick UI.
May 07 17:25:23 Jolla systemd[810]: Dependency failed for Run first time usage demo to user.
May 07 17:25:23 Jolla systemd[810]: Dependency failed for Jolla sign-on UI daemon.
May 07 17:25:23 Jolla systemd[810]: Dependency failed for Application launch booster for Sailfish Browser.
May 07 17:25:23 Jolla systemd[810]: Dependency failed for Application launch booster for Silica on QtQuick2.
May 07 17:25:23 Jolla systemd[810]: Dependency failed for Voicecall ui prestart.
May 07 17:25:23 Jolla systemd[810]: Dependency failed for Store client osupdate check.
May 07 17:25:23 Jolla systemd[810]: Dependency failed for simkit agent.
May 07 17:25:23 Jolla systemd[810]: Dependency failed for The Maliit server.
May 07 17:25:23 Jolla systemd[810]: Failed to start Application launch booster for Qt5.
May 07 17:25:23 Jolla systemd[810]: Dependency failed for Contacts daemon.
May 07 17:25:23 Jolla systemd[810]: Dependency failed for Signal booster that boot is over.
May 07 17:25:23 Jolla systemd[810]: Dependency failed for Communication history daemon.
May 07 17:25:23 Jolla systemd[810]: Dependency failed for Connection Agent.
May 07 17:25:23 Jolla systemd[810]: Dependency failed for Sync FW daemon.
May 07 17:25:23 Jolla systemd[810]: Dependency failed for Runs the accounts update tool to execute scheduled commands.
May 07 17:25:23 Jolla systemd[810]: Dependency failed for Voicecall manager.
May 07 17:25:23 Jolla systemd[810]: Dependency failed for Ambience daemon.

Update

Okay, this should be it:

error while loading shared libraries: libm.so.6: cannot open shared object file: No such file or directory 
error while loading shared libraries: libresolv.so.2: cannot open shared object file: No such file or directory
edit retag flag offensive reopen delete

The question has been closed for the following reason "the question is answered, an answer was accepted" by heubergen
close date 2015-05-07 22:42:42.787641

Comments

Check that you have entry for "nemo" user in your /etc/passwd, /etc/shadow, /etc/group....

Altough I find it strange that any of those could be missing...?

juiceme ( 2015-05-07 06:25:27 +0200 )edit

2 Answers

Sort by » oldest newest most voted
4

answered 2015-05-07 22:42:03 +0200

mholo65 gravatar image

Issue was that OS update process failed to install Glibc.

Downloaded rpm from here:

https://releases.jolla.com/releases/1.1.4.29/jolla/armv7hl/core/armv7hl/glibc-2.15-1.7.1.armv7hl.rpm

Had to do a tarred file transfer via SSH (since SCP was not working)

tar zcf - glibc-2.15-1.7.1.armv7hl.rpm | ssh nemo@xxx.xxx.xxx.xxx 'tar zxf -'

And then lastly installed it:

rpm -iv glibc-2.15-1.7.1.armv7hl.rpm  --force

It feels like phone is functional again!

edit flag offensive delete publish link more

Comments

Same thing happened during 1.1.6.27 update. Here's the link to that glibc package

https://releases.jolla.com/releases/1.1.6.27/jolla/armv7hl/core/armv7hl/glibc-2.15-1.5.1.armv7hl.rpm
mholo65 ( 2015-06-15 22:36:50 +0200 )edit
0

answered 2015-05-07 13:46:18 +0200

Jolly-Jo gravatar image

In case no-one comes up with a better idea: Try to copy all relevant data out of there and do a factory reset... If passwd is missing entries and lipstick does not want to start, who knows what else is missing.

edit flag offensive delete publish link more

Comments

Yes, factory reset is my last resort. But I strongly want to avoid it.

mholo65 ( 2015-05-07 14:55:27 +0200 )edit

Question tools

Follow
1 follower

Stats

Asked: 2015-05-07 00:49:57 +0200

Seen: 397 times

Last updated: May 07 '15