Tag Info

New answers tagged

0

First try: askubuntu > nvidia-drivers-mystery and use @robblue2x's method. Finishing with sudo apt-get install nvidia-346 What screen resolution are you using? eg. 1920x1080 (Full HD), 2560x1600, 4K, etc. And what port/cable? eg. DisplayPort, DVI Dual-Link, etc. You may need to remove your earlier effort (driver download, from Nvidia). Also, do you ...


0

Don't muck with scripts or configuration files that have the possibility of rendering your login screen unusable! Instead, login and set your preferred screen settings*, then run this command: sudo ln ~/.config/monitors.xml /var/lib/lightdm/.config/monitors.xml Your login resolution will now always reflect the settings of the user you're currently signed ...


0

The lightdm log can be viewed by running sudo less /var/log/lightdm/lightdm.log The issue you're describing is a known bug. A few potential workarounds are shown in the comments on that ticket. One workaround is to drop into a terminal by pressing ctrl+alt+F1, logging in, and then running unity --replace. Other variations are shown in the bug comments.


0

lightdm-gtk-greeter depends on liblightdm-gobject-1-0 that contains the interface to LightDM that the greeter is using. liblightdm-gobject-1-0 depends on lightdm so lightdm-gtk-greeter indirectly depends on lightdm, too


2

On the terminal type: sudo service lightdm restart


0

I think you want the old Ctrl+Alt+Backspace command enabled, to restart X. See this question for more info, it's basically: In a terminal, enter sudo dpkg-reconfigure keyboard-configuration press Enter 5 times to skip unrelated questions until the "Terminate the X server with Control+Alt+Backspace" question, and set to Yes. If you can get to another ...


0

I recently had a similar problem. I'm on Ubuntu 14.04 so the problem may have been completely different from yours, but I was able to fix it by re-installing Unity (Ubuntu's default desktop environment). To be honest I don't remember exactly which commands I used, but here are a few threads that were useful to me while troubleshooting this problem: How ...


0

I find that setting any of the above is overridden by the users last session stored by lightdm. You may have to remove or edit the user files at /var/cache/lightdm/dmrc to enable the global default setting. Or on an individual basis by editing the user.dmrc file that has the following contents: [Desktop] Session=ubuntu


0

If your system uses AccountsService, you cannot hide a user from the greeter screen by reconfiguring lightdm because it defers to AccountsService. That is stated very clearly in the comments in: /etc/lightdm/users.conf What you need to do instead is to reconfigure AccountsService. To hide a user named XXX, create a file named ...


0

You should edit vi /usr/share/lightdm/lightdm.conf.d/50-ubuntu.conf And append greeter-hide-users=true


0

First, I would try repairing Unity using a script from this question sudo apt-get install unity-tweak-tool unity-tweak-tool --reset-unity If that doesn't work, I would follow Mahesh's advice and try to reset gnome If all else fails I would recommend that you install a different desktop interface, such as KDE (picked because it exists in the main ...


0

It turns out it was a typo in my /etc/profile file...


0

After an extremely long time searching for the answer... This is what worked for me: Ctrl+Alt+F1 then I entered sudo install gnome and after the install I entered sudo reboot I logged in using the gnome environment although I have heard of someone logging back in with the ubuntu environment also! ps: this was with the 14.04 version


1

The SeatDefaults section, as expected, set the default values. However, once a user has already logged, the session they used (even if it was the default left unchanged) is taken as their session choice. So changes to SeatDefaults no longer apply to them. They'll have to manually select the session from the menu next to their username (usually a gear icon).


0

I also have a non-password account for my little brother and therefore I'm used to the same problem (running Ubuntu 14.10). I don't know whether it is a bug, but I think so. My solution now is: When you locked the screen, there is the small window with only the locked user name and a text field to type in the password. Here, you have to click on the gear ...


0

It looks like you are stuck here. Traditionally, you can open an xlock with the root password (and this means the true root user named "root"; alternate root accounts don't work) no matter who was logged in originally but Ubuntu has abandoned the root user in favour of a list of sudo'ers; bad luck again. I don't know whether there are any hacks to open an ...


2

All the major display managers' packages are set to "provide" a meta-package called x-display-manager. When you have more than one of these, installed, running... sudo dpkg-reconfigure lightdm ...should open up a dialogue for picking the default. If that doesn't work, calling dpkg-reconfigure for the gdm (or whatever other DMs you have) should have the ...


0

I have found answer to my problem and hope it will also serve best to the others who need it. It's so simple. Just make some changes to .conf file and its done. I had to make changes to two .conf files in order to get what I want. 1. Disable Guest Login In Ubuntu 14.04 the .conf file to be edited has been moved to /usr/share/lightdm/lightdm.conf.d from ...


2

I encountered the same on the lock screen, and found out that my account was suddenly locked. I'm using Ubuntu 14.04.1 (lsb_release -a). I installed the latest update and then encountered the issue, password is incorrect when the screen locked. So I googled and saw that from most of the suggestions, one is to change password. I found out that the only ...


0

after a couple of months with no answers in any "ubuntu" community , i tried to : sudo apt-get update sudo apt-get upgrade since after a couple of months there sure would be kernel update and drivers , and it was , i just waited for the system to install ~400mb new packages , hoping everything would be ok , guess what, it didn't . The solution to ...



Top 50 recent answers are included