deskmon crash loop (trap int3 in libglib-2.0.so) on AnduinOS 1.1.12

Hello,
I finished installing AnduinOS a moment ago, after quite a few issues before succeeding. (No details here, just the context, for this bug report).

Then I met with a freeze and wanted to investigate as to why the machine has frozen, with an impossibility to do anything else than a hard reboot. No SysRQ, no tty available, even the ssh console was frozen. Then while investigating I found this specific issue related to deskmon crashing on a crash loop, and I wanted to report it.

System Context / Hardware and OS
OS: AnduinOS 1.1.12 (Base Ubuntu 24.04 Noble)

Machine: Lenovo ThinkPad T420
CPU: Intel Core i5-2520M (Sandy Bridge)
GPU: Intel HD Graphics 3000
RAM: 8 GB
Storage: 128 GB SSD SATA 2.5"

BIOS Note (version 2018) : Intel VT-d (Directed I/O) has since been disabled in the BIOS to prevent ACPI/kernel hard freezes linked to the i915 driver under multi-tasking conditions.

Target Binary Information
Path: /usr/local/bin/deskmon

File Type: ELF 64-bit LSB pie executable, x86-64, not stripped

BuildID (sha1): 94b4e69738fc210eeef2c270194a9ecf22672c02

Symptom & Description
The deskmon process crashed during a specific combination of simultaneous actions: local package installations had just finished running, a concurrent apt show query was being executed via an SSH session, and a major system update via Synaptic was about to be launched.

Because deskmon.service is configured with Restart=on-failure and RestartSec=5s in /etc/systemd/user/deskmon.service, the crash triggers an infinite restart loop that floods dmesg and degrades the GNOME session.

Log from dmesg output:
“ traps: deskmon[2621] trap int3 ip:7f13b9487cbb sp:7ffe3b1405e0 error:0 in libglib-2.0.so.0.8000.0[7f13b9442000+a4000] ”

Could not find any other logs. I installed rsyslog and will keep an eye open for a pair of days.

Start with the reported dmesg trap and inspect /usr/local/bin/deskmon alongside /etc/systemd/user/deskmon.service. Reproduce the package-installation, apt show, and Synaptic-update combination while collecting logs. Done means the crash cause is identified and deskmon no longer enters a restart loop under the reported conditions.