Tag Info

New answers tagged

0

I had similar issues after trying to add some startup scripts (black screen with cursor and a half-active search box). In my case deleting .cache directory from home dir unlocked my system. At this point I think that my problems originate from sudo not respecting -S switch when used in script. No idea why, as in Konsole it works OK...


0

tl;dr: My specific problem was that at one point I had put exec /bin/zsh in ~/.bashrc (no memory of why I did this). strace was not able to track this down but fatrace was since it could trace accesses for the whole system, not just a process subtree. Probably boring details: I was pretty sure that my issue had to do with something in my primary users home ...


0

try the following command: sudo dpkg-reconfigure lighdm a screen will appear asking you to choose between display managers (if you have more than one).


0

Why are you using xorg.conf to set the resolution and not Settings -> Display? To get it working again press ctrl+alt+F1 to open a tty, then login. Remove the xorg.conf file you created and reboot. If the resolution you want is missing use: cvt 1920 1080 60 to create a new modeline. xrandr --newmode "1920x1080_60.00" 173.00 1920 2048 2248 2576 1080 ...


1

Read Only is the state that recovery mode boots into intentionally. What you need to do is remount the root partition with read-write privileges. This will remount the drive as readable and writable. Execute this in the recovery console: mount -rw -o remount /


0

My ordeal has been with adding or removing *.desktop files on my machine, and getting a black screen with only a cursor and the "search bar" from alt-F2. The first time, I tried to manually add a *.desktop file to /.local/share/application for Sublime Text, and that messed up my machine. The second time I added a launcher for Android Studio using the ...


0

I had this problems after upgrading from 14.04. I restarted the system and went in to a terminal and tested the login at the terminal and determined my logins worked. I logged in as root and did apt-get update and saw an error that stated that I needed to run dpkg --configure -a. I ran the command and let it reconfigure the system. After it was finished( ...


0

In my case the problem was caused by wrong permissions on my home directory. 1: Boot from a live media (or different linux distro installed on the same system) and open a terminal with Ctrl-Alt-T 2: Make a temporary mount point and Mount the partition that contains your /home (in my case it was /dev/sda6) sudo mkdir /mnt/sda6 sudo mount /dev/sda6 ...


-1

Press CTRL+ALT+F1 and log in there and run: sudo chown -R $USER:$USER $HOME $USER is your username Ex - sudo chown -R singh:singh /home/ Then press CTRL+ALT+F7 and try to log in


1

I am also having problems with lightdm refusing to show up. In my case, I have both "plain" ubuntu and kubuntu-desktop, so I chose sddm as login screen (sudo dpkg-reconfigure lightdm allowed me to select which login manager I wanted). Maybe installing sddm (if you don't want all of Kubuntu desktop) might be a workaround (I don't know detailed steps on how to ...


1

This is a known bug with lightdm. There are ways to possibly fix it, along with ways of working around the problem. Make sure your computer is connected to the internet and enter a TTY by pressing Ctrl + ALT + F2. Log in here, then try the following: Purge and reinstall lightdm: Run sudo apt-get remove --purge lightdm. Once that's done, run sudo apt-get ...


1

I had a very similar issue where I could log in on the terminal but not on the desktop, my wallpaper from the profile was loaded during login, but after a few seconds it jumped back to the login screen. I checked all file permissions as suggested, they were fine. I tried without a separate home partition and was able to log in to the desktop. After that I ...


0

I switched from fglrx-updates to xserver-xorg-video-ati and it solved both the unlockable lock screen problem and the blank consoles problem.


0

With Xorg 1.17 and later, -nolisten tcp is the default, and you need to explicitly state -listen tcp to enable tcp connections.


1

You may want to cleanup your ecryptfs setup and startover. You can do this by removing the /home/.ecryptfs/username folder.


-1

You can log to the machine using another machine, for example like this: ssh login@machine download drivers from here: wget http://us.download.nvidia.com/XFree86/Linux-x86_64/346.59/NVIDIA-Linux-x86_64-346.59.run install them and configure system to use them.


0

I think you hit bug #1286910. George Karakostas has reported there that Martin Jurča's workaround to bug 1240198 worked for this bug also. Here's an easy fix: open terminal run ibus-setup open the extra settings (the last tab) check the "use system keyboard layout" checkbox Now, how about you guys (yes, you, Canonical) make this ...


4

I fixed this problem by removing the nvidia drivers sudo apt-get remove --purge nvidia-* sudo apt-get install ubuntu-desktop


-1

You can try this first, here is a link. Ubuntu gets stuck in a Login Loop If worse comes to worse you can remake the live USB. I would recommend Unetbootin as it really easily helps you to make it. The links for Unetbootin is here http://unetbootin.sourceforge.net/. And the one for Ubuntu is here .http://www.ubuntu.com/download/desktop. When you go back ...


0

Through trial and error, I managed to fix this on my own, although I'm not sure what my exact steps were. I identified a total of 7 different nvidia-* packages, and decided to try each one, starting with the most recent, nvidia-349. I installed the xorg-edgers PPA, which contains more recent versions of these drivers, and manually checked to see if they ...


1

The only way for me was this: Ctrl+Alt+F1 and this command sudo apt-get purge fontconfig-infinality and a reboot.


0

If you want lightdm you just have to install it: sudo apt-get install lightdm. During the install, you'll be asked to select your default display manager. Select lightdm. If lightdm is already installed, run sudo dpkg-reconfigure lightdm.


0

It's hard to know exactly what is going wrong, but here are a couple easy ideas that might help: To start off, when you can't access a GUI you can switch to a shell command prompt with Ctrl+Alt+F1, where you can log in using your user name (not display name) and password. It then functions like Terminal would. You can switch back to the GUI to see if it's ...


1

I have tried all sorts of things from the forums to fix my login loop problem. None of them worked. I ended up figuring out a less than optimal solution, but one that worked (which makes it preferable over everything else I tried). This is what I ended up doing: Ctrl+Alt+F1 Logged in using my user account. It let me log in there, even though it did not ...



Top 50 recent answers are included