After Latest Tumbleweed update: Failed to start X Display Manager

Tried the latest kernel, as well as switching back to 6.17.0-2 kernel.

Seems Did OpenSuse removed X11 support without making the switch seamless?. I can sti start X11, but it’s now a tiny window that takes like 1/12 of my screen at the top left corner.

Hardware: Surface Laptop 4

Do you have sources for that?

This was speculation since they did that on Leap and I now have a X server issue.

A relevant error might be “Failed to create wl display (No such file or directory)”

Where do you get this?

Leap 16.0 can run on Xorg, it’s in the OSS Repo.

Look, I have an issue right now. I never said you couldn’t download it. But it’s removed by default.

I will appreciate if someone can help I need my PC and the update just broke it.

How do you start X11?

Maybe a wayland issue?

If using gdm can you switch to sddm (all as root):

update-alternatives --config default-displaymanager

Or switch your DE to another one:

update-alternatives --config default-xsession.desktop

I just booted and had the issue I mentioned. I was able to start X11 with startx, but I can only have one window at the time, which is stuck in top left corner and takes about 1/12 of the screen space. So most of my screen is dark.

Please, confirm which display manager you are using, gdm removed X11 support with the switch to Gnome 49.

It was already using sddm. I only have X11 options in the list.

I use the KDE version. How do I know which login manager do I use?

If you use sddm as displaymanager why do you need to run startx ?

When I booted, I was greeted with an error saying it couldn’t start X Display Manager. Then I had a console-only view.

Edit: with the instruction to change DM, I switched to xdm. I still have the window size issue, but at least I had a login GUI + the normal background.

What does

journalctl --no-hostname --no-pager --full --utc -b 0 -p 3

deliver at that moment (before you try to run startx)?

I ran the command with sudo, but now with xdm I have a broken DM but it’s enabled. Should I revert back to sddm (the default one, and the one which one I was having the problem) and give you that error ?

The error with xdm (and with apps running, so prob x11 enabled)

xdm[1661]: Pam_lastlog2(xdm:session): conversation failed

same line repeated with 2518

Also a bunch of Bluetooth lib errors.

Then, after I revert to sddm and reboot. I ran your command (with sudo).

I have a bunch of permissions denied error concerning the Bluetooth library, and one concerning rfkill.

I also have vbox errors, but not sure that is relevant.

Keep sddm as your displaymanager.

Restart your system and do

sudo journalctl --no-hostname --no-pager --full --utc -b 0 -p 3 > error.txt

and upload the file error.txt to paste.opensuse.org and show the link here.

https://paste.opensuse.org/pastes/f2813a1e8a31

(I redacted the end of the Bluetooth addresses)

Can you post
cat /var/log/Xorg.0.log
on susepaste?

cat /var/log/Xorg.0.log | susepaste -e 131040

Done (sorry for the delay). Thanks for the susepaste command tip, as I couldn’t really access a graphical UI while keeping logs intact.

I guess you can access the logs with the key after the -e ?

Would rather not paste the link as it contains somewhat private metrics.

That’s not a key, it is an expiry value in seconds for the paste that was uploaded. You need to share the URL if others are to able to view it.