(KDE PLasma) Window manager doesn't start when I login.

English Install/Boot/Login
#1

I just installed Tumbleweed with the KDE Plasma Desktop, and when I login I get an xterm with a root shell and no window manager.
I can manually type **startkde **and then everything is fine.

When I click **Reboot **nothing happens. I have to type it at a command prompt.

#2

Le 15/11/2017 à 00:06, slickrick66 a écrit :
>
> I just installed Tumbleweed with the KDE Plasma Desktop, and when I
> login I get an xterm with a root shell and no window manager.
> I can manually type *startkde *and then everything is fine.
>
> When I click *Reboot *nothing happens. I have to type it at a command
> prompt.
>
>
you can try

init 3
init 5

to see what happen when going to graphical. what say the logs (dmesg,
journalctl -b0, less /var/log/X…)?

jdd

#3

I couldn’t figure it out and then I started getting this

Nov 15 23:35:11 localhost dns-resolver[19492]: You can find my version in /etc/resolv.conf.netconfig
Nov 15 23:35:11 localhost dns-resolver[19724]: ATTENTION: You have modified /etc/resolv.conf. Leaving it untouched…
Nov 15 23:35:11 localhost dns-resolver[19726]: You can find my version in /etc/resolv.conf.netconfig
Nov 15 23:35:14 localhost dns-resolver[19959]: ATTENTION: You have modified /etc/resolv.conf. Leaving it untouched…
Nov 15 23:35:14 localhost dns-resolver[19961]: You can find my version in /etc/resolv.conf.netconfig
Nov 15 23:35:17 localhost dns-resolver[20193]: ATTENTION: You have modified /etc/resolv.conf. Leaving it untouched…
Nov 15 23:35:17 localhost dns-resolver[20195]: You can find my version in /etc/resolv.conf.netconfig
Nov 15 23:35:20 localhost dns-resolver[20428]: ATTENTION: You have modified /etc/resolv.conf. Leaving it untouched…
Nov 15 23:35:20 localhost dns-resolver[20430]: You can find my version in /etc/resolv.conf.netconfig

but I had not modified resolv.conf, and I had no internet, which was a show stopper so I gave up and reinstalled Leap.

#4

Assume your re-install doesn’t have the same problems…
Although it doesn’t happen often, faulty installs <do> happen which is why

  1. I always test all basic functionality ASAP on new installs
  2. Whenever possible, once I have a good install, I use it to clone other machines (virtual), one reason to avoid install anomalies altogether.

If you were still on the old system and for future reference,
You should have begun any troubleshooting by

  1. Hit <ESC> on your keyboard after the Grub menu to display your stdout. Most likely a relevant error will display just before your logon prompt, describing some kind of graphical failure.
  2. Inspect your bootlog, Any prior bootlog can be displayed using the following command, the following displays the immediately <previous> bootlog. You can display prior bootlogs by incrementing the “-1”
journalctl -b -1

TSU