View previous topic :: View next topic |
Author |
Message |
mdl313 n00b
Joined: 11 May 2003 Posts: 63 Location: New York
|
Posted: Mon Dec 18, 2017 6:44 am Post subject: Lost root password after attempting profile update |
|
|
I recently attempted to update the desktop/plasma profile of my AMD64 installation. For unknown reasons, binutils failed to emerge. Before continuing on, I had to shut down my machine (probably a bad move). After that, KDE fails to install, apparently because dbus does not start up. I get messages such as,
"Unknown username "root" in message bus configuration file. Could not get password database information for UID or current process. User "???" unknown or no memory to allocate password entry. Failed to start message bus: Could not get UID and GID for user name "messagebus"."
This is followed by messages that /usr/bin/dbus-daemon, dbus, and a series of services failed to start. I wind up with a black screen just showing the mouse pointer. I am unable to log in from a terminal as root or user....my passwords are not recognized.
I tried a chroot with a live CD into my root partition. The /etc/passwd, /etc/shadow, and /etc/nsswitch files were present. I backed them up and replaced them with same files from my daily backup, but this had no effect. Also could not change my root password.
Would incomplete update of profile have caused this? Corruption of binutils programs? Would appreciate any suggestions for getting back into root so that I can update system. |
|
Back to top |
|
|
eccerr0r Watchman
Joined: 01 Jul 2004 Posts: 9691 Location: almost Mile High in the USA
|
Posted: Mon Dec 18, 2017 8:04 am Post subject: |
|
|
I don't think it's binutils that would have caused this kind of failure. It's probably something else.
So I don't understand, after you shutdown and restarted, you were able to login and restart the install, but after KDE fails, now you can't login at all?
The packages dealing with authentication are:
- sys-libs/pam
- sys-apps/shadow
These should not be using dbus, it would be some other authentication mechanism that's using dbus (like consolekit.) If pam completely broke, it may cause problems like this.
Since you're completely locked out, probably have to work from a chroot for now. Are there any etc-update/dispatch-conf configurations that are pending (especially pam)?
Did you compile and start using a new kernel recently? _________________ Intel Core i7 2700K/Radeon R7 250/24GB DDR3/256GB SSD
What am I supposed watching? |
|
Back to top |
|
|
Jaglover Watchman
Joined: 29 May 2005 Posts: 8291 Location: Saint Amant, Acadiana
|
|
Back to top |
|
|
Elleni Veteran
Joined: 23 May 2006 Posts: 1270
|
Posted: Mon Dec 18, 2017 12:15 pm Post subject: |
|
|
When I had a similar problem re-emerging shadow fixed it for me. Maybe worth a try. |
|
Back to top |
|
|
Tony0945 Watchman
Joined: 25 Jul 2006 Posts: 5127 Location: Illinois, USA
|
Posted: Mon Dec 18, 2017 3:55 pm Post subject: |
|
|
pam uses the pie flag. Did it re-emerge OK? Try re-emerging pam and openssh in a chroot.
The first time I switched to 17.0 it took forever. The second time, instead of re-emerging everything I did this: Code: | eselect profile {number of 17.0/Desktop}
. /etc/profile
emerge -1v gcc
emerge -1v sys-devel/libtool
emerge -1v binutils
emerge -1v glibc
emerge -1a /lib*/**.a /usr/lib*/**.a
emerge -auvND world | The next to the last step emerged 39 packages, The last step emerged pam and openssh.
I'm told by moderators that the order is critical. |
|
Back to top |
|
|
|