You are not logged in.
Hello,
I had a freeze and I had to do a hard reset.
Now, my loginscreen doesn't accept my password anymore.
Someone suggested on Ubuntu forum that by deleting the .Xauthority file might solve the problem, but it didn't
Does anyone know how to fix this.
Thank you.
Offline
How did you delete the .Xauthority file if you could not log in?
Give more details of what you have done and how
Can you log in as root?
Offline
How did you delete the .Xauthority file if you could not log in?
Give more details of what you have done and how
Can you log in as root?
Thanks for replying,
I can't log in either as user or root.
I deleted the .Xauthority file from other linux on a separate partition.
I also tried to use the install usb and arch-chroot into the partition and I got an error message:
chroot: failed to run command /bin/sh: Exec format errorOffline
Have you fsck'ed the partition? You have have lost something important as a result of an unclean shutdown.
[edit] By the way, fsck'ing/scrubbing, in my opinion, should be the first thing you do after an unclean shutdown before you mount a partition. In the case of a btrfs scrub, you have to mount it RW, but do so very carefully, and after checking it first.
Last edited by nstgc (2015-09-19 18:25:57)
Offline
@nstgc alternatively could be an architecture miss match chroot-cannot-execute-bin-sh-exec-format-error
Offline
Have you fsck'ed the partition? You have have lost something important as a result of an unclean shutdown.
[edit] By the way, fsck'ing/scrubbing, in my opinion, should be the first thing you do after an unclean shutdown before you mount a partition. In the case of a btrfs scrub, you have to mount it RW, but do so very carefully, and after checking it first.
fsck says: the partition is clean.
Offline
@nstgc alternatively could be an architecture miss match chroot-cannot-execute-bin-sh-exec-format-error
On a different partition I have the same architecture installed but with different desktop environment. I chrooted in that partition without any problem.
Offline
From the live media assuming you have file-system to be chrooted into is mounted at /mnt what is the output of
file /mnt/bin/shfile /mnt/usr/bin/bashOffline
From the live media assuming you have file-system to be chrooted into is mounted at /mnt what is the output of
file /mnt/bin/shfile /mnt/usr/bin/bash
Output:
file /mnt/bin/sh
/mnt/bin/sh: symbolic link to bash
file /mnt/usr/bin/bash
/mnt/usr/bin/bash: emptyOffline
loqs wrote:From the live media assuming you have file-system to be chrooted into is mounted at /mnt what is the output of
file /mnt/bin/shfile /mnt/usr/bin/bashOutput:
file /mnt/bin/sh /mnt/bin/sh: symbolic link to bash file /mnt/usr/bin/bash /mnt/usr/bin/bash: empty
So the bash shell executable which also supplies sh has been replaced by an empty file that explains the inability to chroot.
You could reinstall the bash package using the procedure outlined at pacman_crashes_during_an_upgrade but theres no guarantee that the extent of corruption was limited to that package.
Offline
jmak wrote:loqs wrote:From the live media assuming you have file-system to be chrooted into is mounted at /mnt what is the output of
file /mnt/bin/shfile /mnt/usr/bin/bashOutput:
file /mnt/bin/sh /mnt/bin/sh: symbolic link to bash file /mnt/usr/bin/bash /mnt/usr/bin/bash: emptySo the bash shell executable which also supplies sh has been replaced by an empty file that explains the inability to chroot.
You could reinstall the bash package using the procedure outlined at pacman_crashes_during_an_upgrade but theres no guarantee that the extent of corruption was limited to that package.
Thanks loqs,
I tried to reinstall bash but I got tons of other error massages, missing file and the likes.
I will have to reinstall the whole system, I guess.
Offline