PDA

View Full Version : GUI is frozen at login



thompsonm3301
2018-11-02, 23:36
Hello, I'm having an issue with the GUI being frozen when I try and login. I have all the latest package/firmware updates, and I am using KDE plasma desktop. Basically when I boot up, I can see the GUI and login page, but as soon as I try and login it just freezes. I switched to the terminal by pressing CTRL-3, and I used htop and I checked dmesg and other log files but I can't find any reason why it would be crashing. Can someone help me troubleshoot this?

n0r
2018-11-05, 11:16
Hello, did you tried to click on the little engine icon and change from KDE to system x11 default and see if it works?
also you can try this, during booting enter recovery mode, after that log in as root and type
nano /etc/default/grub

go to the line GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" and add acpi=off at the end. so it will look like this GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi=off" it could be possible "splash" is missing but it should work anyway.
after this press CTRL+X then Y and Enter
type sudo update-grub and then reboot. let me know what happend.

grid
2018-11-05, 13:24
Hmm, am guessing it's a video card issue; what kind is it? While I don't have one, Nvidia cards have seemed problematic in the past. Do you get the same problem when using the gnome GUI?

broomdodger
2018-11-05, 15:23
To clarify...
+ boot to GUI login screen... works
+ type username and password... works
+ click Login then hang

If that is correct then
continually and vigorously move the mouse pointer around the screen

Does the mouse pointer freeze?
--or--
Does login continue to the desktop?

cipherhat
2018-11-11, 14:44
Hello, did you tried to click on the little engine icon and change from KDE to system x11 default and see if it works?
also you can try this, during booting enter recovery mode, after that log in as root and type
nano /etc/default/grub

go to the line GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" and add acpi=off at the end. so it will look like this GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi=off" it could be possible "splash" is missing but it should work anyway.
after this press CTRL+X then Y and Enter
type sudo update-grub and then reboot. let me know what happend.


code worked thanks but keyboard and mouse not working after login

To clarify...
+ boot to GUI login screen... works
+ type username and password... works
+ click Login .....works
+ after login keyboard and mouse ...hangs not working

n0r
2018-11-12, 14:24
It seems that you have a problem with Xorg.
Can you please post your xorg.conf file to see what's going on. You can find it in etc/X11/xorg.conf

cipherhat
2018-11-13, 15:52
https://prnt.sc/lhvwrd
no xorg.conf

n0r
2018-11-14, 18:32
Ok it doesn't matter, let's try this.. Enter recovery mode.
Put your root password and type

apt install xserver-xorg-input-all
reboot


Sometimes it may happen that you are not able to use your connection, in this case use a cabled connection or
Type

service network-manager start
It's possible anyway that you need to manually connect to your network you can do it by this

ifconfig wlan0 up
or your wlan id, using only ifconfig you can know what is your wlan id

iwlist wlan0 scan
when you find your networkuse this to connect

iwconfig wlan0 essid YOURNETWORKID key s:YOURWIRLESSKEY

I really hope you can solve this!

cipherhat
2018-11-14, 23:14
Having issues connecting to wifi via command line and i don't have a LAN keep getting SET failed on device wlan0; operation already in progress

n0r
2018-11-16, 18:23
So try check whats your wlanID, using ifconfig command you are able to see it. Maybe is not wlan0.

cipherhat
2018-11-17, 23:43
ran this commands "apt install xserver-xorg-input-all" "reboot"

but still same login issues

Mister_X
2018-12-03, 20:17
connecting to a wifi network via the command line has to be done via wpa_supplicant regardless of the encryption, not iwconfig (and in this example, it is limited to WEP networks). dhclient has to be run after connection to the AP.

saikhan
2019-06-10, 18:02
Hello, did you tried to click on the little engine icon and change from KDE to system x11 default and see if it works?
also you can try this, during booting enter recovery mode, after that log in as root and type
nano /etc/default/grub

go to the line GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" and add acpi=off at the end. so it will look like this GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi=off" it could be possible "splash" is missing but it should work anyway.
after this press CTRL+X then Y and Enter
type sudo update-grub and then reboot. let me know what happend.

It worked- awesome sauce- thanks man

Orkeven
2019-06-15, 09:45
I have a similar problem, although I cannot boot into the GUI and get a failed to start entropy daemon, failed to start modem manager, failed to start hostname service.

Ctrl-Alt-F3 took me to terminal, where I tried a systemctl => "systemctl status systemd-hostnamed.service" for details as instructed on the failed boot page.

The systemctl command above returned:
=> Failed to run 'start' task: No space left on device
=> Failed with result 'resources'
=> Failed to start Hostname Service

I have tried to update or upgrade and no command has been initialised, but keeps returning an error that ends with No space left on device.

I initially had 8.3GB of free disk space which mysteriously disappeared while I was working and the system shutdown and won't boot into the GUI anymore.

When I type "ls" at the terminal prompt folders are listed in blue.
I can "cd" into directories.