Xfce Forum

RogerHat

Member

Registered: 2025-09-09

Posts: 2

Locking up

Excited to return to XFCE. I'm running it on Proxmox as virtual desktop machine. But it randomly crashes/locks up after a few minutes of light use. Sometimes 2 minutes, sometimes 10 or 20. One minute I'm typing into the terminal the next second everything in the screen is locked like a plate of glass. No interaction at all.

I've looked at coredumpctl and there is nothing there. What are some other debug steps? TIA

Host: KVM/QEMU Standard PC (i440FX + PIIX, 1996) (pc-i440fx-9.2)
Kernel: Linux 6.12.43+deb13-amd64
Uptime: 1 hour, 21 mins
Packages: 1492 (dpkg)
Shell: bash 5.2.37
Display (Virtual-1): 1600x1200 @ 60 Hz
DE: Xfce4 4.20
WM: Xfwm4 (X11)
WM Theme: Default
Theme: Adwaita-dark [GTK2/3/4]
Icons: Tango [GTK2/3/4]
Font: Sans (10pt) [GTK2/3/4]
Cursor: Adwaita
Terminal: xfce4-terminal 1.1.4
Terminal Font: FiraCode Nerd Font Mono weight=450 (10pt)
CPU: QEMU Virtual version 2.5+ (4) @ 4.70 GHz
GPU: Red Hat, Inc. QXL paravirtual graphic card
Memory: 945.31 MiB / 5.65 GiB (16%)
Swap: 0 B / 4.11 GiB (0%)
Disk (/): 9.47 GiB / 74.15 GiB (13%) - ext4
Locale: en_US.UTF-8

ToZ

Administrator

From: Canada

Registered: 2011-06-02

Posts: 12,190

Re: Locking up

Hello and welcome.

Looking at the relevant logs might yield some useful info:

• As root, "journalctl -b -1 --no-pager"

• ~/.xsession-errors.old (if the file exists)

• Any proxmox logs that might be available.

---

Mark solved threads as [SOLVED] to make it easier for others to find solutions.
--- How To Ask For Help | FAQ | Developer Wiki  |  Community | Contribute ---

RogerHat

Member

Registered: 2025-09-09

Posts: 2

Re: Locking up

Thank you. the xsession file doesn't seem to be there, and I can't imagine what log from proxmox would be helpful for inside a VM. Memory and CPU usage were quite low when the screen went down.

Output from journalctl -b -1 --no-pager is extensive. I'm not sure what is a fatal error in these logs.

I've been terminal only for quite a while and nothing has crashed, but this has been happening since I installed several weeks ago. Firefox seemed to crash it right away. Today chromium and VSCode were running the times it went down. I will try to crash it and look for entries from about that time.