How to solve "Stopping User Manager for UID 121" error after installing Nvidia drivers on Ubuntu?

Question

I'm on ubuntu 17.10. Got uid 121 after installing nvidia tested proprietary drivers. After purging nvidia-* finally solve uid 121. Later install not tested driver from same file, there's no uid 121, but drivers doesn't work at all. Can i have both working drivers and no uid 121? Geforce gtx 640m

Solution 1

I found that using lightdm the nomodeset parameter was the key to fixing my issue with 18.04

Nomodeset: How to get in once via temporary grub change

You can add the grub configuration parameters if you hold right shift at bootup and press e to edit Ubuntu parameters. You need to replace quiet splash with nomodeset. Then hit ctrl x to save and continue.

Lightdm: How to put in the permanent fix

Once in, open a terminal and type sudo apt install lightdm, then sudo dpkg-reconfigure lightdm, then sudo reboot

Please refer to this amazing guide for more details and screenshots!:

https://askubuntu.com/questions/162075/my-computer-boots-to-a-black-screen-what-options-do-i-have-to-fix-it

Solution 2

I solved this issue in Recovery Mode.

First "Activate Network" in Recovery Mode and then "Repair" Broken packages.

After reboot Ubuntu 18.4 boots as usual.

Solution 3

I experienced a slightly similar issue, although it was inside a VM environment (Ubuntu 18.04 LTS running inside VirtualBox v5.2.12).

In my case, I was able to solve the issue by unchecking the "Enable 3D Acceleration" option to disable it in the VM Settings at Display -> Screen tab;

and increasing the number of CPUs to 2 at System -> Processor screen.

I also checked the Enable PAE/NX setting on this screen.

Solution 4

My UiD 121 error was not solved by any solution I found on the web. I assumed it was due to an update, but actually it turned out to just result from a full hard drive. Solution:

Advanced options.

open a terminal as root

cd /

cd the-location-of-my-trash

cd files

then remove all the files in trash

rm -r *

A simple reboot after this worked fine. May be a very specific situation, but I hope it helps some other user.

Solution 5

I've encountered the same issue on Ubuntu 18.04 after installing Wine and restarting the OS.

I was able to solve it using options provided in the Recovery Mode:

• During boot, press Shift and then Escape, select advanced options and then select recovery mode

At first, I've removed Wine using shell in the recovery mode:

• select root (root shell prompt)
• remove Wine: apt remove ^wine

At that point, I thought I was done but after rebooting problem persisted. I went back into the recovery mode:

• I ran clean

Still the same.

I went back into the recovery mode:

• I ran network and then dpkg.

After that the problem was resolved!

I'm not sure if Wine needed to be removed and whether clean helped. network and dpkg could be enough.

View more solutions