KDE Plasma crashed on VMWare

Hello Guys i used VMWare and the KDE Desktop suddenly crashing after starting, let me explain more detailed, so i fresh installed Garuda on my Laptop then after that i installed VMWare Workstation Pro, so i created Windows VM and after running it the guest work fine but the host is completely crashed. so i force rebooted and noticed that even opening that VMWare for 1 sec can make the host crash, i don’t know whether this is a VMWare fault or Garuda Fault.

What didn’t work :

  • All Desktop Component
  • Konsole
  • TTY (Dropping to tty show blackscreen)

Force Reboot :

  • Holding Laptop Power button to force it down (Worked)
  • CTRL + ALT + DEL (Didn’t work it stucked systemd and won’t restart)

garuda-inxi output :

╭─commandx@phoenix in ~ took 2ms
╰─λ sudo garuda-inxi
[sudo] password for commandx:
System:
Kernel: 6.6.1-arch1-1 arch: x86_64 bits: 64 compiler: gcc v: 13.2.1
clocksource: tsc available: acpi_pm
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux
root=UUID=5d9788ab-20f5-4ff4-a303-35d03700d0bc rw rootflags=subvol=@
resume=UUID=40f16898-fa11-4ed0-bbd7-15b328eed8d2 ibt=off
Desktop: KDE Plasma v: 5.27.9 tk: Qt v: 5.15.11 wm: kwin_x11 dm: SDDM
Distro: Garuda Linux base: Arch Linux
Machine:
Type: Laptop System: ASUSTeK product: VivoBook_ASUSLaptop X515JAB_X515JA
v: 1.0 serial: <filter>
Mobo: ASUSTeK model: X515JAB v: 1.0 serial: <filter>
UEFI: American Megatrends v: X515JAB.309 date: 08/17/2022
Battery:
ID-1: BAT0 charge: 14.6 Wh (47.2%) condition: 30.9/37.1 Wh (83.2%)
power: 6.8 W volts: 7.8 min: 7.8 model: ASUSTeK ASUS Battery type: Li-ion
serial: N/A status: discharging cycles: 473
CPU:
Info: model: Intel Core i3-1005G1 socket: U3E1 bits: 64 type: MT MCP
arch: Ice Lake gen: core 10 level: v4 note: check built: 2019-21
process: Intel 10nm family: 6 model-id: 0x7E (126) stepping: 5
microcode: 0xC2
Topology: cpus: 1x cores: 2 tpc: 2 threads: 4 smt: enabled cache:
L1: 160 KiB desc: d-2x48 KiB; i-2x32 KiB L2: 1024 KiB desc: 2x512 KiB
L3: 4 MiB desc: 1x4 MiB
Speed (MHz): avg: 1000 high: 2801 min/max: 400/3400 base/boost: 1200/8300
scaling: driver: intel_pstate governor: powersave volts: 0.7 V
ext-clock: 100 MHz cores: 1: 400 2: 400 3: 400 4: 2801 bogomips: 9524
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities: <filter>
Graphics:
Device-1: Intel Iris Plus Graphics G1 vendor: ASUSTeK driver: i915 v: kernel
arch: Gen-11 process: Intel 10nm built: 2019-21 ports: active: eDP-1
empty: HDMI-A-1 bus-ID: 00:02.0 chip-ID: 8086:8a56 class-ID: 0300
Device-2: IMC Networks USB2.0 VGA UVC WebCam driver: uvcvideo type: USB
rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-5:3 chip-ID: 13d3:5a11
class-ID: 0e02
Display: server: X.Org v: 21.1.9 with: Xwayland v: 23.2.2
compositor: kwin_x11 driver: X: loaded: modesetting
alternate: fbdev,intel,vesa dri: iris gpu: i915 display-ID: :0 screens: 1
Screen-1: 0 s-res: 1366x768 s-dpi: 96 s-size: 361x203mm (14.21x7.99")
s-diag: 414mm (16.31")
Monitor-1: eDP-1 model: BOE Display 0x07aa built: 2017 res: 1366x768
hz: 60 dpi: 101 gamma: 1.2 size: 344x194mm (13.54x7.64") diag: 395mm (15.5")
ratio: 16:9 modes: 1366x768
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.2.1-arch1.2
glx-v: 1.4 direct-render: yes renderer: Mesa Intel UHD Graphics (ICL GT1)
device-ID: 8086:8a56 memory: 7.33 GiB unified: yes
API: Vulkan v: 1.3.269 layers: 3 device: 0 type: integrated-gpu name: Intel
UHD Graphics (ICL GT1) driver: mesa intel v: 23.2.1-arch1.2
device-ID: 8086:8a56 surfaces: xcb,xlib device: 1 type: cpu name: llvmpipe
(LLVM 16.0.6 256 bits) driver: mesa llvmpipe v: 23.2.1-arch1.2 (LLVM
16.0.6) device-ID: 10005:0000 surfaces: xcb,xlib
Audio:
Device-1: Intel Ice Lake-LP Smart Sound Audio vendor: ASUSTeK
driver: snd_hda_intel v: kernel alternate: snd_sof_pci_intel_icl
bus-ID: 00:1f.3 chip-ID: 8086:34c8 class-ID: 0403
API: ALSA v: k6.6.1-arch1-1 status: kernel-api tools: N/A
Server-1: PipeWire v: 0.3.84 status: n/a (root, process) with:
1: pipewire-pulse status: active 2: wireplumber status: active
3: pipewire-alsa type: plugin 4: pw-jack type: plugin
tools: pactl,pw-cat,pw-cli,wpctl
Network:
Device-1: Intel Ice Lake-LP PCH CNVi WiFi driver: iwlwifi v: kernel
bus-ID: 00:14.3 chip-ID: 8086:34f0 class-ID: 0280
IF: wlo1 state: up mac: <filter>
IF-ID-1: vmnet1 state: unknown speed: N/A duplex: N/A mac: <filter>
IF-ID-2: vmnet8 state: unknown speed: N/A duplex: N/A mac: <filter>
Bluetooth:
Device-1: Intel Bluetooth 9460/9560 Jefferson Peak (JfP) driver: btusb
v: 0.8 type: USB rev: 2.0 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-10:4
chip-ID: 8087:0aaa class-ID: e001
Report: btmgmt ID: hci0 rfk-id: 2 state: down bt-service: enabled,running
rfk-block: hardware: no software: no address: <filter> bt-v: 5.1 lmp-v: 10
status: discoverable: no pairing: no
RAID:
Hardware-1: Intel 82801 Mobile SATA Controller [RAID mode] driver: ahci
v: 3.0 port: 3060 bus-ID: 00:17.0 chip-ID: 8086:282a rev: N/A class-ID: 0104
Drives:
Local Storage: total: 476.94 GiB used: 55.9 GiB (11.7%)
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Jual model: RX7 NVME 512GB
size: 476.94 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s
lanes: 4 tech: SSD serial: <filter> fw-rev: V0329A0 temp: 39.9 C
scheme: GPT
SMART: yes health: PASSED on: 86d 3h cycles: 2,305
read-units: 53,916,024 [27.6 TB] written-units: 56,336,970 [28.8 TB]
Partition:
ID-1: / raw-size: 29.3 GiB size: 29.3 GiB (100.00%) used: 10.21 GiB (34.8%)
fs: btrfs block-size: 4096 B dev: /dev/nvme0n1p2 maj-min: 259:2
ID-2: /boot/efi raw-size: 1024 MiB size: 1022 MiB (99.80%)
used: 580 KiB (0.1%) fs: vfat block-size: 512 B dev: /dev/nvme0n1p1
maj-min: 259:1
ID-3: /home raw-size: 431.01 GiB size: 431.01 GiB (100.00%)
used: 45.7 GiB (10.6%) fs: btrfs block-size: 4096 B dev: /dev/dm-0
maj-min: 253:0 mapped: luks-f133a026-d9a0-45c9-a26c-51ad7b8d8fa9
ID-4: /var/log raw-size: 29.3 GiB size: 29.3 GiB (100.00%)
used: 10.21 GiB (34.8%) fs: btrfs block-size: 4096 B dev: /dev/nvme0n1p2
maj-min: 259:2
ID-5: /var/tmp raw-size: 29.3 GiB size: 29.3 GiB (100.00%)
used: 10.21 GiB (34.8%) fs: btrfs block-size: 4096 B dev: /dev/nvme0n1p2
maj-min: 259:2
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
ID-1: swap-1 type: zram size: 7.51 GiB used: 0 KiB (0.0%) priority: 100
comp: zstd avail: lzo,lzo-rle,lz4,lz4hc,842 max-streams: 4 dev: /dev/zram0
ID-2: swap-2 type: partition size: 15.62 GiB used: 0 KiB (0.0%)
priority: -2 dev: /dev/nvme0n1p3 maj-min: 259:3
Sensors:
System Temperatures: cpu: 54.0 C mobo: N/A
Fan Speeds (rpm): cpu: 2400
Info:
Processes: 274 Uptime: 4m wakeups: 0 Memory: total: 8 GiB
available: 7.51 GiB used: 2.28 GiB (30.4%) igpu: 64 MiB Init: systemd v: 254
default: graphical tool: systemctl Compilers: gcc: 13.2.1 Packages:
pm: pacman pkgs: 1365 libs: 394 tools: gnome-software,octopi,pamac,paru
Shell: garuda-inxi (sudo) default: Bash v: 5.2.15 running-in: konsole
inxi: 3.3.31
Garuda (2.6.19-2):
System install date:     2023-11-15
Last full system update: 2023-11-16
Is partially upgraded:   No
Relevant software:       snapper NetworkManager dracut
Windows dual boot:       No/Undetected
Failed units:

If you have narrowed down the fault to vmware how about trying out virtualbox? You can import your vmware windows machine to virtualbox and check if that’s the cause of issue.

1 Like

Hmm VirtualBox is slow compared to VMWare and … i have Paid License to VMWare Workstation Pro so will not use VirtualBox but this time i will try VirtualBox as you said.

Bro , you are in Linux , use Virt-manager for the win . (Nothing better than Qemu in linux nor VMware )

Do remember to add your user to vboxusers group as well. can be automated with
garuda assistantsystem componentsvirtualization

fair. We are just debugging.

2 Likes

Yeah i have installed VirtualBox and run a Guest OS on it but the bug didn’t happend on VirtualBox…

so this is a vmware bug… You have paid for the software they should have a page for reporting issues and receiving support. They would be able to help you better with bugs in their software.

3 Likes

Ok i will file a complaint to VMWare

No, I’m in Windows. Just for today. :wink:

2 Likes

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