I am booting this off of a USB that I did a proper installation on. I got it to work for a while until everytime I booted it, it said something like "unable to launch because file not found" I will attach a picture of the error. But it kicks me to the default log-in screen and I can not do anything anymore. Terminal does not open, I can not log in, and I can not find a file directory. Is there any fix to this or will I just have to format the drive and start over?
Maybe create a new user and login with that.
I tried, but there is no option to make a new user. It just pops up on the lock screen. When I try to input the password to my normal account, the same error pops up and there appears to be no way to make a new user. I tried right-clicking and other button combinations I could think of.
No dude drop to a terminal by tressing ctrl-alt-f1 at the login screen before logging in.
Then set a root password by typing:
'''sudo passwd root'''
Follow this:
Now a new user is created.
So I made a new user and gave it superuser access. I tried going in to the second account, but it still gave me the same error. I tried a couple of times to make sure I wasn't using the original account but the error kept on popping up.
If you ctrl-alt-f1 to the terminal and login with the new user then type
startx
What happens? Can you post a screenshot?
I believe we should know about the configuration of his disks first. If it's a single partition, it may well be damaged platters or NAND flash making his data inaccessible, which is irreversible. If it's multiple disks or network-related, it could be either his hardware isn't configured properly (reversible), the other hardware /home is on had become damaged (irreversible) or his network configuration had changed recently and he hadn't changed his settings to preserve remote access (reversible).
In my opinion, a fresh start would be nice, however if he finds all of his data in /home is there and if it's an fstab issue, he should just fix it using a live session or if it's a deeper than that; back up what he can, nuke the home part and reinstall the system.
If he is using counterfeit flash hardware, then it might just be that new data wrote over old data and messed his system up.
That is the link to the picture (sorry it's so long). To reply to @tiox this is a single partition drive. I will check if this is counterfeit flash hardware, however I highly doubt it with the specific drive I am using. Unless if @pallebone can find something in the screenshot, I will just wipe the drive and start over.
The link doesnt load for me?
Try it again, I updated the link in the post.
How about throwing up a paste of $HOME/.local/share/xorg/Xorg.1.log for us? cp to another device and dump it for us to see? Mind, I cannot decipher crash logs for the life of me but other people here may be able to help.
man cp for more information on use in case you need help with that.
In terminal try
sudo apt-get remove ubuntu-mate-desktop
sudo apt-get install ubuntu-mate-desktop
Then reboot and try login normally
I just thought of one more thing.
What if, during installation the connection the USB data pins were interrupted? If the USB socket is known to cause issues with other devices, it should never, ever be used for a USB installation of Ubuntu. Unless you are willing to play statue for an hour until installation is finished, there is no reason to not use a better USB port on the same machine or if that is not an option, a USB hub with its connector to the host device stabilized.
1 Like