after upgrade to Kubuntu 18.04 X is not working anymore

[Lars Liedtke]

Hey guys,

On my home laptop I upgraded my Kubuntu 17.10 to 18.04 beta1. Since then I have problems starting an X-Session in general and the only fallback I came to was installing Gnome and trying with Wayland, which gave me at least a GUI Interface.

Additionally I can start a Plasma Session under Wayland with GDM enabled but neither with lightdm or sddm.

Still no X-Session with Ubuntu Desktop or Plasma.

I am fully aware of the conditions of a beta install but maybe this problem may help fixing a possible bug. It is totally possible as well that I made a mistake. But before doing a clean install, I wanted to put the problem here.

The behaviour with X is that it is not started properly so i only see a black screen. I can log into consoles via <CTRL> + <ALT> + <Number> and everything else seems to be loaded properly.

Also I am happy to provide more information and data, if you tell me what you need. Running "startx" in a console complains that no screen is connected.

Maybe someone can help me debug.

Cheers
Lars

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1760351/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.