OpenLeap 15.6 fresh install, no gui

[Starfish4711]

Hello,

I have installed a new Leap 15.6 server as an ESXi VM (v7.x). After the setup finished the system rebooted, but no GUI was visible (just a blank screen). During setup I had selected “Desktop with GNOME”. I have installed all available updates, but no improvement. However, I can switch to a text console, login as root and run “startx” to get a GUI.

Within messages file there is a bunch of lines regarding gnome, here just a part of them:

2024-06-26T09:50:37.055903+02:00 (hostname) /usr/lib/gdm/gdm-wayland-session[1380]: dbus-daemon[1380]: [session uid=458 pid=1380] Activating service name='org.freedesktop.systemd1' requested by ':1.2' (uid=458 pid=1382 comm="/usr/lib/gnome-session-binary --autostart /usr/sha")
2024-06-26T09:50:37.063954+02:00 (hostname) gnome-session[1382]: gnome-session-binary[1382]: WARNING: Could not check if unit gnome-session-wayland@gnome-login.target is active: Error calling StartServiceByName for org.freedesktop.systemd1: Process org.freedesktop.systemd1 exited with status 1
2024-06-26T09:50:37.063996+02:00 (hostname) gnome-session-binary[1382]: WARNING: Could not check if unit gnome-session-wayland@gnome-login.target is active: Error calling StartServiceByName for org.freedesktop.systemd1: Process org.freedesktop.systemd1 exited with status 1
2024-06-26T09:50:37.568450+02:00 (hostname) gnome-shell[1437]: Running GNOME Shell (using mutter 45.3) as a Wayland display server
2024-06-26T09:50:38.367396+02:00 (hostname) org.gnome.Shell.desktop[1437]: VMware: No 3D enabled (0, Success).
2024-06-26T09:50:38.391806+02:00 (hostname) org.gnome.Shell.desktop[1437]: VMware: No 3D enabled (0, Success).
2024-06-26T09:50:38.391909+02:00 (hostname) org.gnome.Shell.desktop[1437]: libEGL warning: egl: failed to create dri2 screen
2024-06-26T09:50:38.393582+02:00 (hostname) org.gnome.Shell.desktop[1437]: VMware: No 3D enabled (0, Success).
2024-06-26T09:50:38.393645+02:00 (hostname) org.gnome.Shell.desktop[1437]: libEGL warning: egl: failed to create dri2 screen
2024-06-26T09:50:38.395564+02:00 (hostname) org.gnome.Shell.desktop[1437]: VMware: No 3D enabled (0, Success).
2024-06-26T09:50:38.395649+02:00 (hostname) org.gnome.Shell.desktop[1437]: libEGL warning: egl: failed to create dri2 screen
2024-06-26T09:50:38.395804+02:00 (hostname) gnome-shell[1437]: (../src/backends/native/meta-kms-impl-device-simple.c:1714):meta_kms_impl_device_simple_open_device_file: runtime check failed: (!meta_device_file_has_tag (device_file, META_DEVICE_FILE_TAG_KMS, META_KMS_DEVICE_FILE_TAG_ATOMIC))
2024-06-26T09:50:38.396202+02:00 (hostname) gnome-shell[1437]: Added device '/dev/dri/card0' (vmwgfx) using non-atomic mode setting.
2024-06-26T09:50:38.397245+02:00 (hostname) gnome-shell[1437]: Failed to initialize accelerated iGPU/dGPU framebuffer sharing: Not hardware accelerated
2024-06-26T09:50:38.397358+02:00 (hostname) gnome-shell[1437]: Created gbm renderer for '/dev/dri/card0'
2024-06-26T09:50:38.397441+02:00 (hostname) gnome-shell[1437]: Boot VGA GPU /dev/dri/card0 selected as primary
2024-06-26T09:50:38.582714+02:00 (hostname) gnome-shell[1437]: Disabling DMA buffer screen sharing (not hardware accelerated)
2024-06-26T09:50:38.592965+02:00 (hostname) /usr/lib/gdm/gdm-wayland-session[1380]: dbus-daemon[1380]: [session uid=458 pid=1380] Activating service name='org.a11y.Bus' requested by ':1.4' (uid=458 pid=1437 comm="/usr/bin/gnome-shell ")
2024-06-26T09:50:38.609114+02:00 (hostname) gnome-shell[1437]: Using public X11 display :1024, (using :1025 for managed services)
2024-06-26T09:50:38.609164+02:00 (hostname) gnome-shell[1437]: Using Wayland display name 'wayland-0'
2024-06-26T09:50:38.713758+02:00 (hostname) org.gnome.Shell.desktop[1465]: VMware: No 3D enabled (0, Success).
2024-06-26T09:50:38.713862+02:00 (hostname) org.gnome.Shell.desktop[1465]: libEGL warning: egl: failed to create dri2 screen
2024-06-26T09:50:38.716925+02:00 (hostname) org.gnome.Shell.desktop[1465]: VMware: No 3D enabled (0, Success).
2024-06-26T09:50:38.716997+02:00 (hostname) org.gnome.Shell.desktop[1465]: libEGL warning: egl: failed to create dri2 screen
2024-06-26T09:50:38.720136+02:00 (hostname) org.gnome.Shell.desktop[1465]: VMware: No 3D enabled (0, Success).
2024-06-26T09:50:38.720206+02:00 (hostname) org.gnome.Shell.desktop[1465]: libEGL warning: egl: failed to create dri2 screen
2024-06-26T09:50:39.089478+02:00 (hostname) /usr/lib/gdm/gdm-wayland-session[1463]: dbus-daemon[1463]: Activating service name='org.a11y.atspi.Registry' requested by ':1.0' (uid=458 pid=1437 comm="/usr/bin/gnome-shell ")
2024-06-26T09:50:39.096553+02:00 (hostname) org.gnome.Shell.desktop[1465]: Failed to initialize glamor, falling back to sw
2024-06-26T09:50:39.097449+02:00 (hostname) dbus-daemon[793]: [system] Activating via systemd: service name='org.freedesktop.ColorManager' unit='colord.service' requested by ':1.20' (uid=458 pid=1437 comm="/usr/bin/gnome-shell ")
...
...
2024-06-26T09:50:41.361257+02:00 (hostname) org.gnome.Shell.desktop[1718]: > Internal error:   Could not resolve keysym XF86KbdLcdMenu5
2024-06-26T09:50:41.373034+02:00 (hostname) org.gnome.Shell.desktop[1718]: Errors from xkbcomp are not fatal to the X server
2024-06-26T09:50:41.447675+02:00 (hostname) gnome-shell[1437]: Registering session with GDM
2024-06-26T09:50:41.558377+02:00 (hostname) gnome-session-binary[1382]: Entering running state
2024-06-26T09:50:41.715443+02:00 (hostname) /usr/lib/gdm/gdm-wayland-session[1380]: dbus-daemon[1380]: [session uid=458 pid=1380] Activating service name='org.gnome.ScreenSaver' requested by ':1.22' (uid=458 pid=1568 comm="/usr/lib/gsd-power ")
2024-06-26T09:50:41.795211+02:00 (hostname) /usr/lib/gdm/gdm-wayland-session[1380]: dbus-daemon[1380]: [session uid=458 pid=1380] Successfully activated service 'org.gnome.ScreenSaver'
2024-06-26T09:51:43.767596+02:00 (hostname) dbus-daemon[793]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.20' (uid=458 pid=1437 comm="/usr/bin/gnome-shell ")
2024-06-26T09:51:50.619316+02:00 (hostname) dbus-daemon[1893]: [session uid=0 pid=1893] Activating via systemd: service name='ca.desrt.dconf' unit='dconf.service' requested by ':1.1' (uid=0 pid=1889 comm="dconf reset /org/gnome/mutter/experimental-feature")
2024-06-26T09:52:01.041460+02:00 (hostname) gnome-shell[1437]: (../src/core/meta-context.c:532):meta_context_terminate: runtime check failed: (priv->state == META_CONTEXT_STATE_RUNNING)
2024-06-26T09:52:01.041525+02:00 (hostname) gnome-shell[1437]: g_main_loop_is_running: assertion 'loop != NULL' failed
2024-06-26T09:52:01.041566+02:00 (hostname) gnome-shell[1437]: (../src/core/meta-context.c:533):meta_context_terminate: runtime check failed: (g_main_loop_is_running (priv->main_loop))
2024-06-26T09:52:01.041596+02:00 (hostname) gnome-shell[1437]: g_main_loop_quit: assertion 'loop != NULL' failed
2024-06-26T09:52:01.041625+02:00 (hostname) gnome-shell[1437]: Shutting down GNOME Shell
2024-06-26T09:52:01.047107+02:00 (hostname) gnome-shell[1437]: Object Gdm.GreeterProxy (0x5619581f21a0), has been already disposed — impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.#012== Stack trace for context 0x56195538dc00 ==#012#0   7ffd723a8fc0 b   resource:///org/gnome/gjs/modules/core/overrides/GObject.js:708 (825b469c1f0 @ 25)#012#1   7ffd723a9080 b   resource:///org/gnome/shell/misc/signalTracker.js:127 (825b4680c40 @ 21)#012#2   7ffd723a9150 b   resource:///org/gnome/shell/misc/signalTracker.js:172 (825b4680e20 @ 35)#012#3   7ffd723a9250 b   self-hosted:203 (825b4695a60 @ 245)#012#4   7ffd723a9310 b   resource:///org/gnome/shell/misc/signalTracker.js:171 (825b4680dd0 @ 135)#012#5   56195545c460 i   resource:///org/gnome/shell/misc/signalTracker.js:123 (825b4680bf0 @ 17)#012#6   56195545c3a8 i   resource:///org/gnome/shell/ui/layout.js:247 (825b46d4150 @ 333)
2024-06-26T09:52:01.047229+02:00 (hostname) gnome-shell[1437]: ../gobject/gsignal.c:2777: instance '0x5619581f21a0' has no handler with id '13142'
2024-06-26T09:52:01.047260+02:00 (hostname) gnome-shell[1437]: Object Gdm.GreeterProxy (0x5619581f21a0), has been already disposed — impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.#012== Stack trace for context 0x56195538dc00 ==#012#0   7ffd723a8fc0 b   resource:///org/gnome/gjs/modules/core/overrides/GObject.js:708 (825b469c1f0 @ 25)#012#1   7ffd723a9080 b   resource:///org/gnome/shell/misc/signalTracker.js:127 (825b4680c40 @ 21)#012#2   7ffd723a9150 b   resource:///org/gnome/shell/misc/signalTracker.js:172 (825b4680e20 @ 35)#012#3   7ffd723a9250 b   self-hosted:203 (825b4695a60 @ 245)#012#4   7ffd723a9310 b   resource:///org/gnome/shell/misc/signalTracker.js:171 (825b4680dd0 @ 135)#012#5   56195545c460 i   resource:///org/gnome/shell/misc/signalTracker.js:123 (825b4680bf0 @ 17)#012#6   56195545c3a8 i   resource:///org/gnome/shell/ui/layout.js:247 (825b46d4150 @ 333)
2024-06-26T09:52:01.047346+02:00 (hostname) gnome-shell[1437]: ../gobject/gsignal.c:2777: instance '0x5619581f21a0' has no handler with id '13143'
2024-06-26T09:52:01.047385+02:00 (hostname) gnome-shell[1437]: Object Gdm.GreeterProxy (0x5619581f21a0), has been already disposed — impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.#012== Stack trace for context 0x56195538dc00 ==#012#0   7ffd723a8fc0 b   resource:///org/gnome/gjs/modules/core/overrides/GObject.js:708 (825b469c1f0 @ 25)#012#1   7ffd723a9080 b   resource:///org/gnome/shell/misc/signalTracker.js:127 (825b4680c40 @ 21)#012#2   7ffd723a9150 b   resource:///org/gnome/shell/misc/signalTracker.js:172 (825b4680e20 @ 35)#012#3   7ffd723a9250 b   self-hosted:203 (825b4695a60 @ 245)#012#4   7ffd723a9310 b   resource:///org/gnome/shell/misc/signalTracker.js:171 (825b4680dd0 @ 135)#012#5   56195545c460 i   resource:///org/gnome/shell/misc/signalTracker.js:123 (825b4680bf0 @ 17)#012#6   56195545c3a8 i   resource:///org/gnome/shell/ui/layout.js:247 (825b46d4150 @ 333)
2024-06-26T09:52:01.047427+02:00 (hostname) gnome-shell[1437]: ../gobject/gsignal.c:2777: instance '0x5619581f21a0' has no handler with id '13144'

I am not familiar with all this GUI stuff, basically I don’t need hardware acceleration or any fancy stuff…

Thanks in advance!

Edit by Sauerland:
Please use CodeTags for Terminal output:

Code-Tags
I have done it here.

[dcurtisfra]

@Starfish4711:

First, welcome to the openSUSE Forums.

---

“startx”

• It ain’t no more the way a Display is started –

 # systemctl status display-manager.service 
● display-manager.service - X Display Manager
     Loaded: loaded (/usr/lib/systemd/system/display-manager.service; enabled; preset: enabled)
     Active: active (running) since Wed 2024-06-26 07:31:22 CEST; 4h 25min ago
   Main PID: 2092 (sddm)
      Tasks: 17 (limit: 4915)
        CPU: 4min 17.481s
     CGroup: /system.slice/display-manager.service
             ├─2092 /usr/bin/sddm
             └─2111 /usr/bin/X -nolisten tcp -background none -seat seat0 vt2 -auth /run/sddm/xauth_MhMynt -noreset -di>

Jun 26 08:23:46 eck001 sddm-helper[3916]: [PAM] Conversation with 1 messages
Jun 26 08:23:46 eck001 sddm-helper[3916]: [PAM] returning.
Jun 26 08:23:46 eck001 sddm[2092]: Authentication for user  "dcu"  successful
Jun 26 08:23:46 eck001 sddm[2092]: Auth: sddm-helper exited successfully
Jun 26 08:23:46 eck001 sddm[2092]: Greeter stopped. SDDM::Auth::HELPER_SUCCESS
Jun 26 08:23:47 eck001 sddm-helper[3916]: pam_unix(sddm:session): session opened for user dcu by (uid=0)
Jun 26 08:23:47 eck001 sddm-helper[3916]: pam_kwallet5(sddm:session): pam_kwallet5: pam_sm_open_session
Jun 26 08:23:47 eck001 sddm-helper[3916]: Writing cookie to "/tmp/xauth_ptXdfx"
Jun 26 08:23:47 eck001 sddm-helper[3916]: Starting X11 session: "" "/etc/X11/xdm/Xsession \"/usr/bin/startplasma-x11\""
Jun 26 08:23:47 eck001 sddm[2092]: Session started true
 #

OK – I use KDE Plasma – therefore the Display Manager is SDDM – GNOME uses GDM …

• But, with systemd it’s still the Display Manager Service which has to be started.

 # systemctl get-default
graphical.target
 #

Therefore, if no graphical display is present, you need to check where systemd stopped during the boot process.
First, check if systemd considers that the system is running –

 # systemctl is-system-running
running
 #

The messages file in /var/log/ is fine and dandy but, we’re running systemd – therefore the systemd Journal is a better indicator for what’s going on –

# journalctl -b 0 --no-hostname --output=short-monotonic

• Shows the current boot, without outputting the hostname and, the time stamps are the delta time from the start of the bootstrap.

Also useful –
# dmesg --human

• Also incremental monotonic time stamps and, no hostname.
  Apart from –

[ +0,000140] systemd[1]: Hostname set to <xxx>.

[Starfish4711]

Hello @dcurtisfra,

thank you!

Yes, “startx” may be outdated, it’s quite long ago that I had to deal with some GUI issues.

The display-manager has been started:

isam-fs-monitor24:~ # systemctl status display-manager.service
? display-manager.service - X Display Manager
Loaded: loaded (/usr/lib/systemd/system/display-manager.service; enabled; preset: enabled)
Active: active (running) since Wed 2024-06-26 12:18:18 CEST; 1h 14min ago
Process: 1036 ExecStart=/usr/lib/X11/display-manager start (code=exited, status=0/SUCCESS)
Main PID: 1104 (gdm)
Tasks: 4 (limit: 4915)
CPU: 67ms
CGroup: /system.slice/display-manager.service
±1104 /usr/sbin/gdm

Jun 26 12:18:18 (hostname) systemd[1]: Starting X Display Manager…
Jun 26 12:18:18 (hostname) display-manager[1070]: /etc/vconsole.conf available
Jun 26 12:18:18 (hostname) display-manager[1070]: KEYMAP: de-nodeadkeys
Jun 26 12:18:18 (hostname) display-manager[1070]: Command: localectl set-keymap de-nodeadkeys
Jun 26 12:18:18 (hostname) display-manager[1070]: W: Cannot find mapping for de-nodeadkeys in /usr/share/systemd/kbd-mod>
Jun 26 12:18:18 (hostname) display-manager[1070]: W: This will result in an ‘us’ X keyboard layout as default
Jun 26 12:18:18 (hostname) display-manager[1036]: Starting service gdm…done
Jun 26 12:18:18 (hostname) systemd[1]: Started X Display Manager.

systemctl get-default shows “graphical.target” and systemctl is-system-running shows “running”.

I have exported the output from journalctl and dmesg to files, but I don’t see a way to attach them to my post. Have read that paste.opensuse.org is the way to go…?

Thanks!

[Starfish4711]

EDIT: ok, here we should go:
journal
dmesg

[mrmazda]

@Starfish4711

journal
dmesg

Short before end of each file we see crash, this from journal:

[   13.146749] systemd[1]: Startup finished in 759ms (kernel) + 2.592s (initrd) + 9.794s (userspace) = 13.146s.
[   13.166255] /usr/lib/gdm/gdm-wayland-session[1346]: dbus-daemon[1346]: [session uid=458 pid=1346] Successfully activated service 'org.gnome.ScreenSaver'
[   13.335490] kernel: ------------[ cut here ]------------
[   13.335493] kernel: Command buffer error.
[   13.335529] kernel: WARNING: CPU: 1 PID: 398 at ../drivers/gpu/drm/vmwgfx/vmwgfx_cmdbuf.c:399 vmw_cmdbuf_ctx_process+0x22c/0x240 [vmwgfx]
[   13.335571] kernel: Modules linked in: af_packet nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib nft_reject_inet nf_reject_ipv4 nf_reject_ipv6 nft_reject nft_ct nft_chain_nat nf_tables ebtable_nat ebtable_broute ip6table_nat ip6table_mangle ip6table_raw ip6table_security iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 iptable_mangle iptable_raw iptable_security rfkill ip_set nfnetlink ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter bpfilter qrtr(n) nls_iso8859_1 nls_cp437 vfat fat intel_rapl_msr intel_rapl_common intel_uncore_frequency_common vmw_balloon nfit libnvdimm pcspkr vmxnet3 i2c_piix4 tiny_power_button(n) ac button joydev mptctl fuse efi_pstore(n) configfs dmi_sysfs ip_tables x_tables crc32_pclmul polyval_clmulni(n) polyval_generic(n) gf128mul sr_mod cdrom ghash_clmulni_intel sha512_ssse3 sha256_ssse3 sha1_ssse3 ata_generic ata_piix ahci libahci libata mptsas scsi_transport_sas mptscsih mptbase sd_mod scsi_dh_emc scsi_dh_rdac scsi_dh_alua t10_pi crc64_rocksoft_generic aesni_intel
[   13.335629] kernel:  crypto_simd crc64_rocksoft vmwgfx sg crc64 cryptd drm_ttm_helper scsi_mod ttm serio_raw btrfs blake2b_generic libcrc32c crc32c_intel xor raid6_pq vmw_vsock_vmci_transport vmw_vmci vsock msr efivarfs
[   13.335645] kernel: Supported: No, Unsupported modules are loaded
[   13.335647] kernel: CPU: 1 PID: 398 Comm: irq/16-vmwgfx Tainted: G                   n 6.4.0-150600.23.7-default #1 SLE15-SP6 128952646fcb1614c051ed5f88ec9aef64f90f32
[   13.335651] kernel: Hardware name: VMware, Inc. VMware7,1/440BX Desktop Reference Platform, BIOS VMW71.00V.21100432.B64.2301110304 01/11/2023
[   13.335653] kernel: RIP: 0010:vmw_cmdbuf_ctx_process+0x22c/0x240 [vmwgfx]
[   13.335683] kernel: Code: 28 83 00 01 48 83 c4 30 5b 5d 41 5c 41 5d 41 5e 41 5f c3 cc cc cc cc 48 c7 c7 6a ad 5e c0 c6 05 8e 0b 01 00 01 e8 04 09 b1 ea <0f> 0b e9 27 ff ff ff 66 66 2e 0f 1f 84 00 00 00 00 00 66 90 90 90
[   13.335686] kernel: RSP: 0018:ffff97e100627de0 EFLAGS: 00010282
[   13.335688] kernel: RAX: 0000000000000000 RBX: ffff8a161007b888 RCX: 0000000000000027
[   13.335690] kernel: RDX: 0000000000000000 RSI: 00000000ffffdfff RDI: ffff8a1737d23508
[   13.335692] kernel: RBP: ffff8a161007b898 R08: 0000000000000000 R09: c0000000ffffdfff
[   13.335693] kernel: R10: ffff97e10119b9d8 R11: ffff97e100627c08 R12: 0000000000000003
[   13.335695] kernel: R13: ffff8a1650287718 R14: ffff8a1650287700 R15: ffff8a161007b880
[   13.335696] kernel: FS:  0000000000000000(0000) GS:ffff8a1737d00000(0000) knlGS:0000000000000000
[   13.335698] kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[   13.335700] kernel: CR2: 00007fde3801a668 CR3: 00000001210aa001 CR4: 00000000007706e0
[   13.335728] kernel: PKRU: 55555554
[   13.335729] kernel: Call Trace:
[   13.335732] kernel:  
[   13.335735] kernel:  ? __warn+0x7d/0x140
[   13.335776] kernel:  ? vmw_cmdbuf_ctx_process+0x22c/0x240 [vmwgfx 29d1a84e0ee156a30c03d3e0979dcb3420a473e4]
[   13.335806] kernel:  ? report_bug+0xfb/0x1e0
[   13.335829] kernel:  ? prb_read_valid+0x17/0x20
[   13.335842] kernel:  ? handle_bug+0x44/0x80
[   13.335850] kernel:  ? exc_invalid_op+0x13/0x60
[   13.335854] kernel:  ? asm_exc_invalid_op+0x16/0x20
[   13.335869] kernel:  ? vmw_cmdbuf_ctx_process+0x22c/0x240 [vmwgfx 29d1a84e0ee156a30c03d3e0979dcb3420a473e4]
[   13.335907] kernel:  ? __pfx_irq_thread_fn+0x10/0x10
[   13.335910] kernel:  vmw_cmdbuf_man_process+0x5d/0x100 [vmwgfx 29d1a84e0ee156a30c03d3e0979dcb3420a473e4]
[   13.335934] kernel:  vmw_cmdbuf_irqthread+0x21/0x30 [vmwgfx 29d1a84e0ee156a30c03d3e0979dcb3420a473e4]
[   13.335958] kernel:  vmw_thread_fn+0x36/0x70 [vmwgfx 29d1a84e0ee156a30c03d3e0979dcb3420a473e4]
[   13.335981] kernel:  irq_thread_fn+0x1e/0x60
[   13.335984] kernel:  irq_thread+0xec/0x1a0
[   13.335987] kernel:  ? __pfx_irq_thread_dtor+0x10/0x10
[   13.335990] kernel:  ? __pfx_irq_thread+0x10/0x10
[   13.335992] kernel:  kthread+0xdf/0x120
[   13.335998] kernel:  ? __pfx_kthread+0x10/0x10
[   13.336000] kernel:  ret_from_fork+0x29/0x50
[   13.336008] kernel:  
[   13.336009] kernel: ---[ end trace 0000000000000000 ]---
[   13.338673] rtkit-daemon[1711]: Successfully made thread 1459 of process 1434 owned by 'gdm' RT at priority 20.
[   13.361525] chronyd[1015]: Selected source 192.168.250.24 (ntp.(domain))
[   13.362661] kernel: [drm] vmwgfx: mob memory overflow. Consider increasing guest RAM and graphicsMemory.**
[   13.363335] kernel: [drm] vmwgfx: increasing guest mob limits to 24576 kB.

[dcurtisfra]

@Starfish4711

ESXi VM

Please note the following VMware Handbook – <VMware Configure Maximums>

dmesg entries –

[  +0.026652] [drm] vmwgfx: mob memory overflow. Consider increasing guest RAM and graphicsMemory.
[  +0.000674] [drm] vmwgfx: increasing guest mob limits to 24576 kB.

[Starfish4711]

@mrmazda

[   13.362661] kernel: [drm] vmwgfx: mob memory overflow. Consider increasing guest RAM and graphicsMemory.**
[   13.363335] kernel: [drm] vmwgfx: increasing guest mob limits to 24576 kB.

Thanks (to both of you) to pointing me to this. To be honest I expected some of the many warning and error messages way before to be a pointer to the issue’s cause.

The VM was created with the default of 4 MB video memory, so far I had no need to change this for any of my machines. I have increased the video memory to 64 MB now (started at 256 MB and tested some lower values, too) and GUI is now showing correctly!

Thank you very much!