Hi,
I have a problem with a fresh install of osmc. I have a raspberry pi 4, an sd card sandisk 64 Go for the boot and a usb SSD.
When i’m in ssh mode in Putty i tried to change the password. I have a message telling me that the change is ok, but when i reboot the new password doesn’t work, it’s still the default password: osmc.
I read that it could be a problem of a corrupt sd card. I bought a new one today and the problem is still there.
Another problem, at the reboot it changes the skin alone (estuary>osmc skin)
Here is the log: https://paste.osmc.tv/uduzuyipaj
Thanks for the help
Did you do a fresh install on that SD card?
How are you trying to change the password?
The log won’t show a password for obvious reasons.
Yes fresh install on the new sd card
I do it with: sudo passwd
and i get this message: passwd: password updated successfully
Then I would check cat /etc/passwd to see if it is updated as expected.
You could also check with ls when it was last modified.
Sam
I have this anwser with the cat command:
root:x:0:0:root:/root:/bin/bash
daemon:x:1:1:daemon:/usr/sbin:/usr/sbin/nologin
bin:x:2:2:bin:/bin:/usr/sbin/nologin
sys:x:3:3:sys:/dev:/usr/sbin/nologin
sync:x:4:65534:sync:/bin:/bin/sync
games:x:5:60:games:/usr/games:/usr/sbin/nologin
man:x:6:12:man:/var/cache/man:/usr/sbin/nologin
lp:x:7:7:lp:/var/spool/lpd:/usr/sbin/nologin
mail:x:8:8:mail:/var/mail:/usr/sbin/nologin
news:x:9:9:news:/var/spool/news:/usr/sbin/nologin
uucp:x:10:10:uucp:/var/spool/uucp:/usr/sbin/nologin
proxy:x:13:13:proxy:/bin:/usr/sbin/nologin
www-data:x:33:33:www-data:/var/www:/usr/sbin/nologin
backup:x:34:34:backup:/var/backups:/usr/sbin/nologin
list:x:38:38:Mailing List Manager:/var/list:/usr/sbin/nologin
irc:x:39:39:ircd:/run/ircd:/usr/sbin/nologin
gnats:x:41:41:Gnats Bug-Reporting System (admin):/var/lib/gnats:/usr/sbin/nologi n
nobody:x:65534:65534:nobody:/nonexistent:/usr/sbin/nologin
_apt:x:100:65534::/nonexistent:/usr/sbin/nologin
systemd-network:x:101:102:systemd Network Management,:/run/systemd:/usr/sbin/n ologin
systemd-resolve:x:102:103:systemd Resolver,:/run/systemd:/usr/sbin/nologin
messagebus:x:103:104::/nonexistent:/usr/sbin/nologin
_rpc:x:104:65534::/run/rpcbind:/usr/sbin/nologin
ntp:x:105:108::/nonexistent:/usr/sbin/nologin
statd:x:106:65534::/var/lib/nfs:/usr/sbin/nologin
avahi:x:107:110:Avahi mDNS daemon,:/run/avahi-daemon:/usr/sbin/nologin
sshd:x:108:65534::/run/sshd:/usr/sbin/nologin
osmc:x:1000:1000::/home/osmc:/bin/bash
systemd-timesync:x:999:999:systemd Time Synchronization:/:/usr/sbin/nologin
systemd-coredump:x:998:998:systemd Core Dumper:/:/usr/sbin/nologin
Sorry, I meant /etc/shadow. If the system is default (untouched), it will be:
osmc:$y$j9T$YO0bsdRQoKHvOxZPFBn5q/$D5DzjNAvfOy.ftwO5IE2FkbrZNsC2DtiNZO9Q5.9UF1:19871:0:99999:7:::
You can also check with sudo getent shadow osmc
Sam
With the command cat /etc/shadow:
root:$y$j9T$z5dVqzLqGb.pvXFho36sj/$yL6Q6jh7X8K0uGNe3eHYWSiORpegWw4T.7JdpkbQZX3:20213:0:99999:7:::
daemon::20031:0:99999:7:::
bin::20031:0:99999:7:::
sys::20031:0:99999:7:::
sync::20031:0:99999:7:::
games::20031:0:99999:7:::
man::20031:0:99999:7:::
lp::20031:0:99999:7:::
mail::20031:0:99999:7:::
news::20031:0:99999:7:::
uucp::20031:0:99999:7:::
proxy::20031:0:99999:7:::
www-data::20031:0:99999:7:::
backup::20031:0:99999:7:::
list::20031:0:99999:7:::
irc::20031:0:99999:7:::
gnats::20031:0:99999:7:::
nobody::20031:0:99999:7:::
_apt::20031:0:99999:7:::
systemd-network::20031:0:99999:7:::
systemd-resolve::20031:0:99999:7:::
messagebus::20031:0:99999:7:::
_rpc::20031:0:99999:7:::
ntp::20031:0:99999:7:::
statd::20031:0:99999:7:::
avahi::20031:0:99999:7:::
sshd::20031:0:99999:7:::
osmc:$y$j9T$YO0bsdRQoKHvOxZPFBn5q/$D5DzjNAvfOy.ftwO5IE2FkbrZNsC2DtiNZO9Q5.9UF1:20031:0:99999:7:::
systemd-timesync:!:20031::::::
systemd-coredump:!:20031::::::
OK,
The hash is identical, just the last change date on the password (which is expected as I’m running a version of OSMC that was built earlier than yours).
When you run passwd to change your password, the osmc hash should change in /etc/shadow. See if it changes, and if it does, see if that persists on reboot.
Sam
Still the same hash and persist after reboot…
I would check if the filesystem is read-only.
Something like touch /home/osmc/testfile
Reboot and see if it exists…
The file testfile is still there after reboot
I would check the SD with a tool like h2testw.
I know you have already tried another card…
No problem detected with h2testw
Wait!!! Are you trying to change the osmc password? Why would you use sudo for that?
You only need sudo if you either want to change the root password. Or if you forgot the osmc user password and want to change it. But then it’s sudo passwd osmc.
So to just change the osmc password just use passwd without sudo.
1 Like
Ooh thank you. Sudo is my mistake. Sorry .
And have you an idea for the change of skin when I reboot?
Try to change it and then don’t reboot but just use the Exit option. See if it remains. If yes then reboot.
1 Like
I should’ve seen that earlier…
It changes when I exit too
So also changing back to OSMC?
If so then I suggest to stop mediacenter and manually change the skin in the guisettings.xml
Try change another setting after changing the skin.
This should trigger the guisettings.xml to be updated.
It’s a known issue in Kodi.
Sam