Leap 16 update, no graphical login screen - only in rescue mode

English Install/Boot/Login
1

Hi,
I made an update from Leap 15.6 to Leap 16. (intel graphics card)
It seems to work in general but on boot it does not load the graphical login.
I see the mouse cursor on a black screen.
In rescue mode I can startx and get KDE as expected (without login here)

I tries several hints I found like deleting SDD cache. But still no success.
in /var/log/messages I see:
sddm-greeter-qt6[1724]: Xcb EGL gl-integration initialize failed
sddm-greeter-qt6[1724]: QXcbIntegration: Cannot create platform OpenGL context, neither GLX nor EGL are enabled
…
sddm-greeter-qt6[1724]: Failed to create RHI (backend 2)
sddm-greeter-qt6[1724]: Failed to initialize graphics backend for OpenGL.
Then the process is terminated.

Do you have any hints for me, please?

2

Which Intel GPU? From Konsole, please copy and paste entire input line/output lines/trailing prompt as one unit from inxi -GSaz --za here within PRE (</> icon above typing area) tags.

1 Like
3

this is the output:

System:
  Kernel: 6.12.0-160000.5-default arch: x86_64 bits: 64 compiler: gcc v: 13.4.0 clocksource: tsc
    avail: hpet,acpi_pm parameters: BOOT_IMAGE=/boot/vmlinuz-6.12.0-160000.5-default
    root=UUID=<filter> showopts splash=silent
    resume=/dev/disk/by-uuid/ec61a69e-3059-4055-9590-fff18bc7a44b preempt=full mitigations=auto
    quiet
  Console: tty 4 DM: SDDM Distro: openSUSE Leap 16.0
Graphics:
  Device-1: Intel HD Graphics 630 vendor: ASUSTeK H110I-PLUS driver: i915 v: kernel arch: Gen-9.5
    process: Intel 14nm built: 2016-20 ports: active: HDMI-A-1 empty: DP-1,HDMI-A-2 bus-ID: 00:02.0
    chip-ID: 8086:5912 class-ID: 0300
  Display: unspecified server: X.org v: 1.21.1.15 with: Xwayland v: 24.1.6 driver: X:
    loaded: modesetting unloaded: vesa alternate: fbdev,intel gpu: i915 tty: 240x67
  Monitor-1: HDMI-A-1 model: Acer G226HQL serial: <filter> built: 2012 res: 1920x1080 dpi: 102
    gamma: 1.2 size: 509x286mm (20.04x11.26") diag: 551mm (21.7") ratio: 16:9 modes: max: 1920x1080
    min: 720x400
  API: EGL v: N/A platforms: inactive: gbm,wayland,x11,surfaceless,device-0,device-1
  API: OpenGL Message: GL data unavailable in console for root.
  API: Vulkan v: 1.4.309 layers: 1 device: 0 type: integrated-gpu name: Intel HD Graphics 630
    (KBL GT2) driver: N/A device-ID: 8086:5912 surfaces: N/A
4

Speculating here…the OpenGL/EGL initialization failure could be happening following the distro upgrade if some Mesa or Qt6 graphics libraries are missing or mismatched perhaps.

It would be good to check the configured repos:
zypper lr -d

Check to see which Mesa* packages and Qt graphics packages are installed…
zypper se -si mesa libQt6Gui6 libQt6OpenGL6
Others can compare with their working KDE installation, but you should see entries for at least Mesa-dri, Mesa-libGL1, and Mesa-libEGL1, as well as libQt6Gui6 and libQt6OpenGL6.

If not try
sudo zypper in -f Mesa-dri Mesa-libGL1 Mesa-libEGL1 libQt6Gui6 libQt6OpenGL6

1 Like
5

I’ve got no GUI either. Combined with the fact that my wireless card still doesnt work (could never make it work on 15.6) and that the new install screen is terrible, hard to use, and makes it a huge pain to reuse your /home partition, I am near to just switching distros.

I dont know of this helps at all but it gives me a new login prompt every few seconds when its stuck there without GUI.

Using an unmodified HP laptop by the way.

6

Yours might be due to a different underlying problem. I would start a new dedicated topic, otherwise it can lead to confusing discussions.

7

Actually this is my fault I just didnt install a GUI at all because this is the worst linux installer I have ever used in 20 years of using linux and I missed where I was supposed to. I tried to delete the prior post but cant. Hopefully installing it a second time works.

1 Like
8

The request was for “entire input line/output lines/trailing prompt as one unit”. It would need no descriptive comment. The idea is for us to see exactly what you saw, no guessing, like so:

# inxi GSaz --za
System:
  Kernel: 6.12.0-160000.5-default arch: x86_64 bits: 64 compiler: gcc
    v: 13.4.0 clocksource: tsc avail: hpet,acpi_pm
    parameters: BOOT_IMAGE=/boot/vmlinuz root=LABEL=<filter> noresume
    ipv6.disable=1 net.ifnames=0 consoleblank=0 preempt=full mitigations=off
  Desktop: KDE v: 3.5.10 tk: Qt v: 3.3.8c wm: kwin with: kicker vt: 7 dm:
    1: KDM note: stopped 2: XDM Distro: openSUSE Leap 16.0
Graphics:
  Device-1: Intel 4th Generation Core Processor Family Integrated Graphics
    vendor: ASUSTeK driver: i915 v: kernel arch: Gen-7.5 process: Intel 22nm
    built: 2013 ports: active: HDMI-A-3 empty: DP-1, HDMI-A-1, HDMI-A-2, VGA-1
    bus-ID: 00:02.0 chip-ID: 8086:041e class-ID: 0300
  Display: x11 server: X.Org v: 21.1.15 compositor: kwin driver: X:
    loaded: modesetting unloaded: fbdev,vesa alternate: intel dri: crocus
    gpu: i915 display-ID: :0 screens: 1
  Screen-1: 0 s-res: 2560x1440 s-dpi: 120 s-size: 541x304mm (21.30x11.97")
    s-diag: 621mm (24.43")
  Monitor-1: HDMI-A-3 mapped: HDMI-3 model: Acer K272HUL serial: <filter>
    built: 2018 res: mode: 2560x1440 hz: 60 scale: 100% (1) dpi: 109 gamma: 1.2
    size: 598x336mm (23.54x13.23") diag: 686mm (27") ratio: 16:9 modes:
    max: 2560x1440 min: 720x400
  API: EGL v: 1.5 hw: drv: intel crocus platforms: device: 0 drv: crocus
    device: 1 drv: swrast gbm: drv: crocus surfaceless: drv: crocus x11:
    drv: crocus inactive: wayland
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: intel mesa v: 24.3.3 glx-v: 1.4
    direct-render: yes renderer: Mesa Intel HD Graphics 4400 (HSW GT2)
    device-ID: 8086:041e memory: 1.46 GiB unified: yes
  API: Vulkan v: 1.4.309 layers: 1 device: 0 type: integrated-gpu name: Intel
    HD Graphics 4400 (HSW GT2) driver: mesa intel v: 24.3.3
    device-ID: 8086:041e surfaces: xcb,xlib device: 1 type: cpu name: llvmpipe
    (LLVM 19.1.7 256 bits) driver: mesa llvmpipe v: 24.3.3 (LLVM 19.1.7)
    device-ID: 10005:0000 surfaces: xcb,xlib
  Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo x11: xdriinfo,
    xdpyinfo, xprop, xrandr
#

This is pretty much what you should have seen if SDDM, and the rest of X, was installed and working correctly. Neither Plasma nor SDDM are used here on 16.0, and the GPU is a little older, but It’s an Asus with Intel on 16.0, and there should be little other difference. Hopefully your reinstallation try matches well, working as expected. :man_student:

1 Like
9

mrmazda and
deano_ferrari

thank you. I will try in the evening (German time) and let you know.

10

Folks, thank you!
All your hints helped me finding the issue. And now it is working! KDE starts and I can login.

Here is what was the issue:
After the update some Mesa libs have not been updated to 24.* from Leap 16. They still have been on 23.* from packman
So I forced the update - including dependencies - to the Leap 16 main repo.
Then after a restart it directly started into KDE login screen.

Thank’s a lot! Great help!

11

Thanks for the update. Yes, mismatched Mesa* versions between Packman and OSS repos are a common source of such issues for users. Glad to read of your success with this. :slight_smile:

1 Like
12

Per deano, I ran zypper se -si mesa libQt6Gui6 libQt6OpenGL6, and the output showed me in the same situation as the OP: “mismatched Mesa* versions between Packman and OSS repos”. I intend to use the migration tool when I go to Leap 16. Of course, the Packman repo will be disabled, then. Will the migration tool allow vendor change here, or will I have to fix this post-install?

13

At least for me the migration tool did not change the vendor completely on it’s own. That is why I had some leftovers as described in the threads.
I see the following options:

  • switch from packman to regular repo before updating
  • or after update when packman is disabled force switch all system packages to Leap 16 repo on text console
  • or (worked for me as well) boot into recovery mode, “startx” and use still available yast software management to force switch to Leap 16 repo. You can check manually as well which packages are not updated.
14

Ah, thanks for the reply. Forewarned is forearmed. I’ll do the first option, I think.

1 Like
15

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.