Today, there are many problems with the graphics card driver. One of them is that after the computer restarts, the resolution of the display screen becomes 800600, and the normal resolution is 19201080. There is no other resolution option in the system settings, so it cannot be modified. Try to create the xorg. Conf file, which is described on the Internet, to set the custom desktop resolution. After the modification, the resolution has changed, but it is 1600 * 1200, which is still very abnormal. Using the combination of CVT and xrandr to modify the resolution indicates another error, xrandr: failed to get size of gamma for output default. One problem after another, what a tangle!
It has to be said that it’s really unpleasant to search these professional problems with Baidu in China. What often appears are some irrelevant or unsolvable web pages. Fortunately, it’s all solved now, and the problem is still in the driver side of the graphics card [1]. Software & amp; update in system settings; In updates, click additional drivers and change it to NVIDIA driver (I choose the third one here, as shown in the figure below). The application modification needs to wait for a little time, restart the computer after completion, and the resolution is normal again.
After the driver is re installed, the problem of circular login appears again. You may encounter it later. Record the solution here.
ctrl +alt +f2
sudo service lightdm stop
sudo apt-get --purge remove nvidia-*
After many months, I stepped on the big pit of circular login again, but the previous solution was invalid. Another possible problem is that the owner and all groups of the. Xauthority file become root. There is a. Xauthority file in the user’s home directory. View the owner and all groups of the file
ls -la .Xauthority
If it is root, you need to change it to your login user:
sudo chown username:username .Xauthority
(there will always be all kinds of accidents in the actual solution, one by one, don’t worry.)
Read More:
- [Solved] Login with Ubuntu graphical interface, error sorry, that didn’t work.please try again
- [Solved] secureCRT Failed to Login Ubuntu20.04 Error: Key exchange failed
- [Solved] SSH Failed to Login Ubuntu Error: Socket error Event: 32 Error: 10053. Connection closing…Socket close.
- The solution of insufficient disk space of docker in Ubuntu
- Ubuntu sub process/usr/bin/dpkg returned an error code (1) solution
- C Language Compilation Error: variably modified ‘* *’ at file scope
- [Solved] Linux SSH Login Terminal Error: shell request failed on channel 0
- NVIDIA SMI error after Ubuntu 20.04 restart [How to Solve]
- Solution of device eth0 does not see to be present, delaying initialization. Error in network card under Linux
- Ubuntu: rabbitmq reports an error; Solution error: unable to connect to node rabbit@localhost : nodedown
- [Nginx] solution: it can’t be accessed on the background API interface after HTTPS (access the specified port through the domain name)
- Opensuse12.3 installation of VirtualBox error resolution
- [Solved] Ubuntu Server 18.4 System /etc/sudoers: syntax error near line 32
- Login Error: token failed, reason: getaddrinfo EAI_AGAIN ks-apiserver (kubesphere is Installed)
- [Solved] ubuntu Boot Error: /dev/nume0n1p2:clean
- Ubuntu18.04 Install ROS Error: rosdep update [How to Solve]
- [Solved] lftp Login Error: Fatal error: Certificate verification: Not trusted
- Ubuntu Run Error: not syncing : VFS: Unable to mount root
- Git Error Resolution: errno:10054 Time out
- How to Fix Ubuntu(Linux) mount error(22)