After 9/25 update boots to black screen with mouse pointer

After I updated on Sept 25 and rebooted now it goes to a black screen with a mouse cursor that you can move but nothing else. del+alt+F1 gets me to command line and I can log in. I have no previous snapper image to revert to. I am not using NVIDIA graphics just the IGPU 630. If I do an init 3 then init 5 it goes back to black screen with mouse pointer.
Any suggestions?
Thanks

Have you tried one of the other selections in the Grub menu, such as prior kernel or failsafe/recovery?

I have two installations of TW on 630 iGPUs. One was last updated 15 days OK, no trouble. The other just now. Both are running Xorg as expected on 6.4.12 kernels.

# inxi -SGaz --vs --zl --hostname
inxi 3.3.30-00 (2023-09-25)
System:
  Host: ab250 Kernel: 6.4.12-1-default arch: x86_64 bits: 64 compiler: gcc
    v: 13.2.1 clocksource: tsc available: 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: Trinity v: R14.1.0 tk: Qt v: 3.5.0 info: kicker wm: Twin v: 3.0
    vt: 7 dm: 1: TDM 2: XDM Distro: openSUSE Tumbleweed 20230922
Graphics:
  Device-1: Intel HD Graphics 630 vendor: ASUSTeK driver: i915 v: kernel
    arch: Gen-9.5 process: Intel 14nm built: 2016-20 ports:
    active: DP-1,HDMI-A-2,HDMI-A-3 empty: DP-2,HDMI-A-1 bus-ID: 00:02.0
    chip-ID: 8086:5912 class-ID: 0300
  Display: x11 server: X.Org v: 21.1.8 driver: X: loaded: modesetting
    unloaded: fbdev,vesa alternate: intel dri: iris gpu: i915 display-ID: :0
    screens: 1
  Screen-1: 0 s-res: 3600x2640 s-dpi: 120 s-size: 762x558mm (30.00x21.97")
    s-diag: 944mm (37.18")
  Monitor-1: DP-1 pos: primary,bottom-l model: Acer K272HUL serial: <filter>
    built: 2018 res: 2560x1440 hz: 60 dpi: 109 gamma: 1.2
    size: 598x336mm (23.54x13.23") diag: 686mm (27") ratio: 16:9 modes:
    max: 2560x1440 min: 720x400
  Monitor-2: HDMI-A-2 mapped: HDMI-2 pos: top-left model: NEC EA243WM
    serial: <filter> built: 2011 res: 1920x1200 hz: 60 dpi: 94 gamma: 1.2
    size: 519x324mm (20.43x12.76") diag: 612mm (24.1") ratio: 16:10 modes:
    max: 1920x1200 min: 640x480
  Monitor-3: HDMI-A-3 mapped: HDMI-3 pos: top-right model: Dell P2213
    serial: <filter> built: 2012 res: 1680x1050 hz: 60 dpi: 90 gamma: 1.2
    size: 473x296mm (18.62x11.65") diag: 558mm (22") ratio: 16:10 modes:
    max: 1680x1050 min: 720x400
  API: EGL v: 1.5 hw: drv: intel iris platforms: device: 0 drv: iris
    device: 1 drv: swrast surfaceless: drv: iris x11: drv: iris
    inactive: gbm,wayland
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: intel mesa v: 23.1.7 glx-v: 1.4
    direct-render: yes renderer: Mesa Intel HD Graphics 630 (KBL GT2)
    device-ID: 8086:5912 memory: 15.13 GiB unified: yes
#

If after switching to vtty3 you do systemctl restart xdm do you still get black screen?

Are you an auto-login user? If yes, try turning it off using text mode yast.

Which DE do you normally use?

Are you using Wayland instead of Xorg? Vice versa? Try the other.

Thanks for the response. I will answer some now and some after I boot TW again. I have a triple boot PC (TW, Win11, MacOS) so I can’t have TW booted while here in MacOS.
I can’t get ti Grub because like an idiot I set the timeout to 0 and can’t get to the menu. I also disabled snapper as it kept running me out of disk space even after setting to only 4 backups.
I can get to the command line with Cntl+alt+F1. I can get to yast but I have a 4k monitor and the text is to small. It does let me do zypper dup but no change. I am an auto login user. I am using KDE Plasma. I did try init 3 followed by init 5 and it went back to the black screen Alt space and Alt F2 have no effect. I remember trying wayland when it first cane out and it crashed so as far as I remember U am still on Xorg.
I will try the things you suggested and report back.

Just a crazy thought.

At the init 3 command line, are you executing “telinit 5” ?

If yes, try this versus telinit:

:.> startx < enter >

Any change ?

I tried startx and it flashes “Could not start plasma session” then goes to a black screen with mouse pointer only now alt/ctl/F1 no longer works to get back to cli.
I also let it install todays update and it made no difference,

Does that include F2-F6 as well?

Instead of appending just 3 to get into multi-user.target, also append another space and video=1920x1080@60. That will quadruple text size, facilitating text mode functionality. Then /etc/vconsole.conf can be used to configure a larger framebuffer font size for successive boots. If you can’t edit at Grub menu due to 0 timeout, boot install media to rescue mode to edit. From rescue boot you can chroot to the installed system to run YaST Bootloader text mode to make the timeout usable.

I was able to set the timeout to 10. Its been so long since I had a problem like this that I had forgotten that I did have snapper back on and set to just 1 snapshot. I tried booting into 6.5.3.1 and it did the same thing exactly with the black screen and mouse pointer. So its not a kernel problem. Something must have gotten corrupted when the 9/25 update was done. It will boot to kde when booting with the read only boot loader but not with either read only kernel.

Check if plymouth.enable=0, noplymouth or plymouth=0 appended to linu line in Grub help.

If SDDM is the problem, switching to LightDM using update-alternatives --config default-displaymanager may be your workaround.

What is input/output from ls -l /usr/share/xsessions/?

plymouth looked ok. The only other DE was XDM and it booted to the login page but after I entered my credentials it went to a gray screen with mouse cursor and nothing else. So looks like its not sddm.
output from ls -l /usr/share/xsessions/

XDM is a display manager, an alternate to GDM, LightDM and SDDM which in openSUSE either functions in that capacity itself, or launches a more sophisticated alternate. That gray screen that resulted should have had a small Xterm window in it if all was good.

Is there /var/log/sddm.log with clues in it?

Is .xsession-errors current, with clues? If small, paste it here. Otherwise susepaste it. Also find Xorg.0.log in /var/log/ or ~/.local/share/xorg/ and susepaste it. It may help to also launch an IceWM session from a vtty login screen and capture output from inxi -GSaz to paste here (if it works):

WINDOWMANAGER=/usr/bin/icewm startx

It may be worth also trying:

WINDOWMANAGER=/usr/bin/startplasma-x11 startx

Either of these two commands, if they work, should open an X session on the same vtty rather than on vtty7, or if a DM is running not on vtty1 and not on vtty2.

Found the problem! During the same session that I did the 9/25 update I had also changed the icon theme to a different one downloaded from the settings menu. I guess it didn’t like it. I changed it back to Breeze Dark and now all is well. never would have thought changing the icons would keep it from booting all the way.

1 Like