Upgrade to Plasma 5.11.2 stalls at boot screen

[Snowhog]

Edit (as root) /etc/default/grub and remove ‘quiet splash’ from the options. Save/close the file and in a konsole run:

sudo update-grub

Reboot.

If/when the hang happens, what is the last line on the screen reporting?

[marco07]

Edit (as root) /etc/default/grub and remove ‘quiet splash’ from the options. Save/close the file and in a konsole run:

sudo update-grub

Reboot.

Thanks for your reply! Unfortunately it did not help. Again I had to access the system through "Resume" in recovery booting.

If/when the hang happens, what is the last line on the screen reporting?

There are no message or any other thing . It is a black screen with the arrow head and 3 dots (like the start icon in the panel) and curser in the middle of it.

FYI, the booting grub is that of Kubuntu 16.04, my main OS. The desk top is a multi boot system with 4 or 5 Linux OS's installed at various partitions. None has any boot-up problem at all except 17.10.

[Snowhog]

Thanks for your reply! Unfortunately it did not help. Again I had to access the system through "Resume" in recovery booting.

IF the two options are removed, and you rebuild the grub configuration files (sudo update-grub), then when you boot, grub is in a textual, not a graphical, environment. There should be all sorts of text output being displayed.

$ sudo cat /usr/share/grub/default/grub
# If you change this file, run 'update-grub' afterwards to update
# /boot/grub/grub.cfg.
# For full documentation of the options in this file, see:
# info -f grub -n 'Simple configuration'

GRUB_DEFAULT=0
GRUB_HIDDEN_TIMEOUT=0
GRUB_HIDDEN_TIMEOUT_QUIET=true
GRUB_TIMEOUT=10
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
GRUB_CMDLINE_LINUX=""

So, removing quiet splash between the quotes (you have to leave the quote marks) so the line reads:

GRUB_CMDLINE_LINUX_DEFAULT=“”

Saving and closing the file and then issuing sudo update-grub rebuilds the grub configuration files, and when you reboot, you see the boot process in all it’s glory.

[marco07]

So, removing quiet splash between the quotes (you have to leave the quote marks) so the line reads:

GRUB_CMDLINE_LINUX_DEFAULT=“”

Saving and closing the file and then issuing sudo update-grub rebuilds the grub configuration files, and when you reboot, you see the boot process in all it’s glory.

I did exactly as you described above in the main boot-up Grub (16.04) which did not help. Or do you mean to do the above in the grub of 17.10?
Thanks!

[Snowhog]

In 17.10, as that’s the vesion you say you having an issue with.

[marco07]

In 17.10, as that’s the vesion you say you having an issue with.

Yes, I did this. Still to no avail.
Here is a copy of what I did;

# If you change this file, run 'update-grub' afterwards to update
# /boot/grub/grub.cfg.
# For full documentation of the options in this file, see:
# info -f grub -n 'Simple configuration'

GRUB_DEFAULT=0
#GRUB_HIDDEN_TIMEOUT=0
GRUB_HIDDEN_TIMEOUT_QUIET=true
GRUB_TIMEOUT=10
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT=""
GRUB_CMDLINE_LINUX=""

Here is where it stalls:
Sorry i took a picture (.jpg) with my phone. But could not insert it. The "insert Image" does not load it.

[claydoh]

We are editing the booting grub, the one on 16.04, from 16.04, correct?

Sent from my LG-H931 using Tapatalk

[marco07]

We are editing the booting grub, the one on 16.04, from 16.04, correct?

Sent from my LG-H931 using Tapatalk

I tried both from booting 16.04, and 17.10. Unfortunately none worked.

[vinnywright]

I do not think editing grub to see the boot process is going to help hear ,,,,his problem is the login stalling AFTER puting in his password and geting to the desktop ,,,,,,,is this correct @marco07

VINNY

[marco07]

Yes, that is correct Vinny. I log in and go past of this process but get stalled in boot splash.
What I do not understand is why all is OK while booting from the Recovry's resume option, but not from main grub. Strange!!

[vinnywright]

Yes, that is correct Vinny. I log in and go past of this process but get stalled in boot splash.
What I do not understand is why all is OK while booting from the Recovry's resume option, but not from main grub. Strange!!

just for an of the wall check run this and post the output ,,,if you get any.

find ~/ -user root

VINNY

[marco07]

just for an of the wall check run this and post the output ,,,if you get any.

find ~/ -user root

VINNY

here it is:
marco@Lenovo:~$ find ~/ -user root
marco@Lenovo:~$

[vinnywright]

here it is:
marco@Lenovo:~$ find ~/ -user root
marco@Lenovo:~$

well that eliminates one possibility ,,,,,,,,

from the login screen (do not log in) press "ctrl+alt+F6" ,,,,you get a TTY (text login) type your user name , press enter ,,,,type your password , press enter ,,,,once loged in type startx and press enter look for error output ,,,what happens?

VINNY

[marco07]

well that eliminates one possibility ,,,,,,,,

from the login screen (do not log in) press "ctrl+alt+F6" ,,,,you get a TTY (text login) type your user name , press enter ,,,,type your password , press enter ,,,,once loged in type startx and press enter look for error output ,,,what happens?

VINNY

Well here is what happened in order:
-startx
-Black screen boot splash with the loading circle in the middle, for a short time, then
-curser in the middle of black screen, with
-hard drive activity for a long time, then
-curser changing to "I" in the middle of screen, then
-No further progress, system stalled at this screen.

After waiting for a long time, had to get out by manually powering off.
Now, strange is that on ensuing boot-up, I no longer was able to get back into the system (17.10) through "Resume" function of the Grub's recovery option.
Of course this issue all started after upgrading of the KDE to version 5.11.4. Prior to upgrade all was OK.

[vinnywright]

I think their is an "incompatible" library version problem in 5.11.4 ,,,,,look hear https://www.kubuntuforums.net/showth...l=1#post407679

you can try from the TTY renaming .kde .config and .local with the "mv" command "mv .local .local.old" and so forth ,,,they will get recreated as defaults on loging in ,, this got me back it ,,,,,but first maybe try "startkde" once where you tried startx before...and or just try one more time .

read that thread over first ,,,,,I lost some system settings things when I renamed the .files ,,,the auto start problem has resolved it's self with time (probably an update) but the theme settings are still broken.

VINNY