This is a really strange issue, and I totally understand if you think I'm just making a dumb mistake, but somehow I think Solus changed my admin password.

This is on an old laptop that I wanted to repurpose as a media streamer etc, so password security wasn't a concern for me. I did a fresh install of Budgie 4.4, set the user and password (and wrote the password down), did an update and reboot and all seemed well until I tried to install some new packages after the reboot. I put in my password about twenty times, checking it to make sure I hadn't made a dumb mistake, but it won't take it.

I noticed in the change password dialogue that it will not accept a password that contains the username, which my original password did. Was this a change that was applied in an update to Budgie? And did it somehow decide to wipe my original password?

This is rather low stakes for me since it's an old laptop I was not really using anyway, it's just the loss of time and the fact that I'm seriously wondering if I have an early onset memory disease. But if someone can set me right it would be much appreciated.

  • brent and WetGeek replied to this.

  • Well I did a fresh install with a different password and everything went as normal.

    hdansin I noticed in the change password dialogue that it will not accept a password that contains the username, which my original password did.

    Solus did accept your password during install with your user name in it despite you violating the terms
    ...then it let you sudo eopkg up which is a strange thing to do BEFORE a reboot on your part...since everytime I ever install Solus it asked for a reboot immediately after install, not an update..
    ..after reboot when you try to install something it puts its foot down
    ... and retroactively denies you credential without telling you why (but you found out why).

    Either way, even if I misinterpreted your "update and reboot" sequence it makes me think password policy for the iso is different than the finished product?
    that's all I got but it's Occams-like🙂

    short version: likely snafu on yer part or Solus', I think your brain is fine
    edit/sp

        hdansin But if someone can set me right it would be much appreciated.

        I'm still pretty clear-headed, I believe, even at my age. But I've been guilty once or twice of leaving the install medium in place and booting again to the "live" session. I blame it on being tired, and distracted by a phone call or something else between installing and using Solus. When I finally noticed the "Install OS" icon on the desktop,
        I knew right away what had happened.

        Any password that was set in the previous live session would not still be in effect after a reboot.

            brent it makes me think password policy for the iso is different than the finished product?

            This is what I was thinking. I guess I'll just have to start over.

              Well I did a fresh install with a different password and everything went as normal.

                WetGeek But I've been guilty once or twice of leaving the install medium in place and booting again to the "live" session

                equally guilty🙂

                  hdansin and you probably left your username out of the password this time, too (?)

                  if true, then that explains everything about install #1

                      10 months later
                      Harvey locked the discussion .