Kubuntu stopped booting to GUI

[KubuntuPasc]

Hello,

Yesterday I missed to shut down my computer, so it ran out of battery over night. Trying to restart it today resulted that it does not boot to the GUI anymore, but stays in command line mode. Reading many of the existing threads on that topic and trying the solutions provided there didn't help. I have Kubuntu 16.04 LTS installed.

I would be very glad about any help.

[GreyGeek]

When it boots up, does it get to the login screen and can you enter your password?
If not, are you really in the grub rescue mode?

[KubuntuPasc]

If I boot normally it just gets me to a black screen with a cursor which does not react to any keyboard entry. Pressing ctrl+alt+F1 opens a shell. There it asks me for username & password. In recovery mode I directly get to the shell asking for username & password. Furthermore while booting I get the following notifications:

„Failed to start Detect the available GPUs and deal with any system changes. See ‚systemctl status gpu-manager.service‘ for details“

and

„Failed to start Simple Desktop Manager. See ‚systemctl status sddm.service‘ for details“

Logging in also works and I can access my files and programs..

[GreyGeek]

See who owns ~/.Xauthority.
It should be yourname:yourname.

[KubuntuPasc]

It is me owning that file with -rw———-

[GreyGeek]

Kubuntu stopped booting to GUI

When you get the black screen open a terminal and issue
startkde

If that does’t work I’d check your install completeness:
sudo apt -f install
sudo dpkg —configure -a

Do that pair repeatedly until both show nothing done

And if the black screen persists try re-installing plasma-desktop

[KubuntuPasc]

Hello GreyGeek

When I try

startkde

the console outputs

$DISPLAY is not set or cannot connect to the X server

. For

sudo apt -f install

the system wants to remove the packages

python3-bs4, python3-cycler, python3-pandas, python3-dateutil, python3-html5lib, python3-lxml, python3-tables, python3-numexpr, python3-patsy, python3-pyparsing, python3-tz

which fails due to a Permission denied message. Performing the suggested command

sudo dpkg —configure -a

is performed without any message, and also does not change anything about the above behaviour

[GreyGeek]

Your system isn't healthy until both of those commands can execute sequentially without generating error msgs.
I'd delete the python packages and repeat the two commands until everything comes back clean. Then we can work from there to get the Desktop GUI running.

[KubuntuPasc]

Dear GreyGeek,

Thank you very much for your help. After spending another few hours to solve the appearing problems with the Python packages, I decided to take plan B and delete and reinstall my Kubuntu.

All the best

[GreyGeek]

Dear GreyGeek,

Thank you very much for your help. After spending another few hours to solve the appearing problems with the Python packages, I decided to take plan B and delete and reinstall my Kubuntu.

All the best

My most recommended step for malfunctions that cannot be easily diagnosed and repaired. My second most recommended step is to use Btrfs as the root file system when installing Kubuntu (or Neon). You can create a daily snapshot in seconds and if disaster strikes it takes less than 5 minutes to roll back to the most recent snapshot. That is a LOT easier than putzing around for hours or days trying to reverse a mistake, accident or other failure mode.

[JPRuehmann]

Hello
I have te same Problem since last week.
reinstall not work for me since I have 9000 installed Packets and above 20 Apps that working on Handmade Scripts.
So reinstalling would take Weeks.
apt and dpkg run flawlessly, but I only get a black screen with Cursor.
If I run start kde I get the same error.
Other DE are working, but only use the US Keyboard layout.
Is there a waz to make it work again?
For me it is happened after a normal reboot.
I am using Kubuntu 16.04 LTS (32Bit)
Thanks

[oshunluvr]

The "$DISPLAY is not set or cannot connect to the X server" error means the xserver isn't running. Try "startx". It may launch the desktop or result in error messages.

If it generates errors, look into /var/log/Xorg.0.log and see if it reveals anything.