Cannot install apps or change system settings
I have had this happen twice now on my Xperia X. I am unable to set a password for ssh access, as in it will not generate a password and it will not save one that I set. It shows a single bullet character in the password field even if I type a new password and click save. And of course nothing that I try for the password will work for ssh connections or devel-su elevation. Also, changing settings for things like location service and VPN are not saved, and apps cannot be installed or updated.
The first time this happened, it was on release 3.0.0 (upgraded from a 2.x release). I re-flashed it to release 3.0.2.8 and that corrected the problem. The second time (on release 3.0.2.8), I looked at the permissions for /etc/shadow there are no permissions set:
[nemo@Sailfish ~]$ ls -l /etc/shad*
---------- 1 root root 2094 2019-05-02 12:40 /etc/shadow
---------- 1 root root 2192 2019-05-02 11:55 /etc/shadow-
So that's my problem, but I can't figure out how that happened. I checked the system date and time just to be sure something odd wasn't going on there, and they are correct. So I wanted to check here to see if anyone has heard of this before I do another re-flash.
EDIT: the problem is not with /etc/shadow, it's something else unknown. Thanks @hlub.
I have solved this. It is due to not enough inodes in the root filesystem. This can be verified with the following in a shell:
The IFree column should list thousands. Mine was showing more like 150.
The thing that led me to this was viewing the zypper history:
This shows errors installing apps, with the reason listed as "installing package <pkg name=""> needs 796 inodes on the / filesystem".</pkg>
And thanks to the comments by @aerique on this post, I confirmed that I likewise had a lot of inodes taken up by unused
/var/lib/connman
files and directories.Because I could not elevate my shell permissions with devel-su, I had to boot into recovery mode to delete the unneeded connman directories. Once in the recovery mode shell, here's the process I used.
After all of this, the phone is back to functioning normally. And apparently this issue is fixed in 3.0.3 Hossa. Now I am able to update to that version.
ajwatt ( 2019-05-29 00:46:12 +0200 )edit