Mobian PIN changed after update!

[PineSupporter]

I'm running into a similar problem, but the pin is getting changed while I'm doing an apt update, not using the Software application. I did try to update via ssh, but found the connection dropped and I couldn't get back in. Updates from KingsCross were faster, it seemed, but once the screen locked, well, you know the rest.

There does seem to be a GitLab issue with Mobian:

https://gitlab.com/mobian1/issues/-/issues/174

I'll be trying some of these suggestions once I have time, will report back if anything of use comes of it.

I was using apt-get because the Software application was not working, so it was the same problem.

I don't think it really changes the pin. It's just the update locks you out if it finishes in the terminal and the screen is off. It needs a restart to finish the install, holding the power button in, powering off then powering back on will usually finish the install and your pin will work again. At least that has worked for me.

I mentioned above that rebooting led to an unusable phone. Obviously there are some issues that still need ironing out and keeping Mobian on the SD card instead of installing it seems a reasonable precaution for now.

---

The same exact thing happened to me yesterday Software couldn't update so I did it in terminal. Also locked me out, and wouldn't take the PIN anymore. I tried to restart the phone and got the same Oh no! message. I had to reflash the SD card, and now I'm scared to do any updates. I have the Mobian CE coming, hopefully it won't have the same problem.

[abstractWax]

This just happened to me. I reflashed my SD card and updated again but AGAIN it locked me out. A hard reset solved the problem - I was able to get in with my PIN.

[Mwo87]

For now I'm just going to check once in a while for new release images and write them on the SD card directly.

No more updating from within the OS for me until things get sorted out.

[derbaertigefrytz]

This is not an issue of apt (update/upgrade), but an issue of sudo/root.
I do not know, whether this is intended, however your mobian login is blocked, while a root session is running.
If you are used to use "sudo" as a prefix for your commands issued from mobian, you will not recognize this, until you do a long "sudo apt upgrade".
However I am used to use root sessions with "sudo su" sometimes. This can block your phone, even, when your kingscross session is idle.
No blocking problem with "sudo su" or long "sudo <command>" sessions in ssh (so, it might be a problem of kgx?).

[derbaertigefrytz]

and hey, this does not happen anymore after latest updates.

[cybercrypt13]

This is not an issue of apt (update/upgrade), but an issue of sudo/root.
I do not know, whether this is intended, however your mobian login is blocked, while a root session is running.
If you are used to use "sudo" as a prefix for your commands issued from mobian, you will not recognize this, until you do a long "sudo apt upgrade".
However I am used to use root sessions with "sudo su" sometimes. This can block your phone, even, when your kingscross session is idle.
No blocking problem with  "sudo su" or long "sudo <command>" sessions in ssh (so, it might be a problem of kgx?).

So does the phone start working again once the update has finished?

Or am I screwed and I need to rebuild OS?  I just got my phone yesterday and it has already bricked due to this bug so it is still a problem.

Thanks,

[cybercrypt13]

I had the same problem. Got my phone yesterday, attempted to do update through gui and it said dependency problems so I ran apt update and upgrade from prompt. System wouldn't let me login again. However, I lucked up and got past a popup during the update that needed me to say what to do. I then let it sit for an hour before I reboot it to make sure it had time to finish and everything works when I came back. So I guess I got lucky.

[C0ffeeFreak]

Follow the instructions and warnings in the official blog and you will be fine.

https://blog.mobian-project.org/posts/20...pam_issue/

[mdkierum]

So what do you do if you have reloaded a new Mobian image as a recovery method since I could not get past the screen lock, and it still cannot get past the lock screen?

The references to the "solutions" assumes one has not performed the first upgrade and to not let the screen to lock during the post-upgrade reboot.

[SerialNumber]

In my case, I updated the phone then got locked out.
I just left the phone plugged in for an hour as was suggested by a previous post and came back in an hour. Did a hard reset, and everything was working again.
So if anyone reads this message and made the mistake of upgrading before reading the blog warning, be patient... i guess?