N
NorthWest
Guest
Linuxminhelp wrote:
Thanks for that very clear procedure that you follow. It is not standard and really shouldn't be so involved.
You can consider re-installing as Tolkem suggests since you have other issues as well with sound.
Usually with linux there are ways and means of dealing with issues so that re-installation is not required, but it can become a cost/benefit issue ... there may be more benefit and less cost (in terms of time and research) with re-installation.
That said, there are some things you can try. These are things I would try so they are opinions if you like and they can all be reversed unproblematically. Note that I will not deal with the decryption process ... you'll have to insert that yourself in the procedure.
You could try to log in and start the GUI session without first booting to a GUI. The point of this would be to see if it avoids permission issues. To do this I would alter the target of the display manager (as root) and configure the computer to boot to a text prompt:
Rename the .Xauthority in your home directory to something else so it is out of the process, for example rename it .XauthorityBackUp.
When those are set, reboot.
When you reboot, you would normally boot to a text prompt. There you login as user. That's what should happen.
You should now be able to bring up X and the GUI with:
If you can bring up the GUI with these steps, then that is normal without having to change any permissions.
Now it may actually be the case that no .Xauthority file reappears in your home directory at all. That is not uncommon and generally has no effect on X starting up. You can create an .Xauthority if you need it and generate its contents with xauth. It's usually needed if forwarding X stuff between computers, but on stand alone computers you may not need it.
If none of this works, there are other things to try, but I'll leave it for the moment.
These are the steps I have to take to log in,
1) At password screen of GUI press control alt f3
2) at black screen terminal enter username then new password
3) type "ecryptfs-mount-private" then my OLD password to decrypt it
4) CD /home/user
5) Ls -la
6) sudo chown user:user .Xauthority
7) control alt f7 to get GUI OS login. Works normal now.
On a side note, There is no sound from speakers or even visible slider on the host OS or virtual boxes but the virtual machine KVM qemu sound works.
Thanks for that very clear procedure that you follow. It is not standard and really shouldn't be so involved.
You can consider re-installing as Tolkem suggests since you have other issues as well with sound.
Usually with linux there are ways and means of dealing with issues so that re-installation is not required, but it can become a cost/benefit issue ... there may be more benefit and less cost (in terms of time and research) with re-installation.
That said, there are some things you can try. These are things I would try so they are opinions if you like and they can all be reversed unproblematically. Note that I will not deal with the decryption process ... you'll have to insert that yourself in the procedure.
You could try to log in and start the GUI session without first booting to a GUI. The point of this would be to see if it avoids permission issues. To do this I would alter the target of the display manager (as root) and configure the computer to boot to a text prompt:
Code:
systemctl set-default multi-user.target
When those are set, reboot.
When you reboot, you would normally boot to a text prompt. There you login as user. That's what should happen.
You should now be able to bring up X and the GUI with:
Code:
startx
If you can bring up the GUI with these steps, then that is normal without having to change any permissions.
Now it may actually be the case that no .Xauthority file reappears in your home directory at all. That is not uncommon and generally has no effect on X starting up. You can create an .Xauthority if you need it and generate its contents with xauth. It's usually needed if forwarding X stuff between computers, but on stand alone computers you may not need it.
If none of this works, there are other things to try, but I'll leave it for the moment.
Last edited by a moderator: