Sinity

[LOG] [08:36:59.154810095] [AQ] drm: Disabling output DP-3
[LOG] [16:05:43.660735777] [AQ] drm: Modesetting DP-3 with 3840x2160@60.00Hz
[LOG] [16:05:43.805179048] [AQ] [libinput] event2  - Logitech G502: SYN_DROPPED event - some input events have been lost.

[LOG] [16:05:43.805740056] cursorImage request: shape 9 -> text
[LOG] [16:05:43.806117866] [AQ] drm: Cursor buffer imported into KMS with id 156
[LOG] [16:05:43.813436390] Hyprctl: new connection from pid 2789983
[LOG] [16:05:43.813454274] Hyprctl: dispatcher dpms : on
[LOG] [16:05:49.653114749] [AQ] udev: new udev change event for card1
[LOG] [16:05:49.653199634] [AQ] udev: DRM device card1 changed

Sinity

socket kitty-sinity-1353464: Error: Failed to connect to unix:/run/user/1000/kitty-sinity-1353464 with error: dial unix /run/user/1000/kitty-sinity-1353464: connect: connection refused
socket kitty-sinity-1353602: Error: Failed to connect to unix:/run/user/1000/kitty-sinity-1353602 with error: dial unix /run/user/1000/kitty-sinity-1353602: connect: connection refused
ws 5 | weechat | kitty_pid 1549002 | socket kitty-sinity-1549002 | window 1 | foreground: /nix/store/8qk1gyrr0r7q3nybq34sfp0b92p6mwl8-weechat-4.7.1/bin/weechat --run-command ; (pid 1549134, cwd /home/sinity)
ws 1 | codex --dangerously-bypass-approvals-and-sandbox resume | kitty_pid 1549423 | socket kitty-sinity-1549423 | window 1 | foreground: codex --dangerously-bypass-approvals-and-sandbox resume (pid 1553518, cwd /realm/project/voyage-embeddings)
ws 1 | codex --dangerously-bypass-approvals-and-sandbox | kitty_pid 1549560 | socket kitty-sinity-1549560 | window 1 | foreground: codex --dangerously-bypass-approvals-and-sandbox (pid 2584232, cwd /r

Sinity

[{
    "address": "0x32664220",
    "mapped": true,
    "hidden": false,
    "at": [23, 23],
    "size": [3794, 2075],
    "workspace": {
        "id": 5,
        "name": "5"
    },

Sinity

[{
    "address": "0x32664220",
    "mapped": true,
    "hidden": false,
    "at": [23, 23],
    "size": [3794, 2075],
    "workspace": {
        "id": 5,
        "name": "5"
    },

Sinity

--------------------------------------------
   Hyprland Crash Report
--------------------------------------------
Well this is awkward.

Hyprland received signal 11(SEGV)
Version: 3bcfa94ee4189faaa4daf661949e88cf28c00d94
Tag: v0.51.0
Date: 2025-10-02
Flags:

Sinity

[LOG] [CPrimarySelectionManager] New primary selection data device bound at 1f998200
[LOG] [CWLDataDeviceManagerResource] New data device bound at 1faabb10
[LOG] [CWLCompositorResource] New wl_surface with id 24 at 1f8b8c30
[LOG] [17:55:03.470201451] [AQ] [libinput] event16 - solaar-keyboard: is tagged by udev as: Keyboard Mouse

[LOG] [17:55:03.470220662] [AQ] [libinput] event16 - solaar-keyboard: emulating high-resolution scroll wheel events.

[LOG] [17:55:03.470280285] [AQ] [libinput] event16 - solaar-keyboard: device is a pointer

[LOG] [17:55:03.470282555] [AQ] [libinput] event16 - solaar-keyboard: device is a keyboard

Sinity

diff --git a/src/protocols/ColorManagement.cpp b/src/protocols/ColorManagement.cpp
index 5af099287..0831bd7c2 100644
--- a/src/protocols/ColorManagement.cpp
+++ b/src/protocols/ColorManagement.cpp
@@ -169,8 +169,12 @@ wl_client* CColorManagementSurface::client() {
 }
 
 const SImageDescription& CColorManagementSurface::imageDescription() {
-    if (!hasImageDescription())
-        LOGM(WARN, "Reading imageDescription while none set. Returns default or empty values");

Sinity

 # Post-Mortem

  - 20:00–00:50 the Hyprland process uwsm_hyprland-uwsm.desktop spammed ~2.3e5 identical colour-management warnings (see journalctl -b -1
  --since '2025-10-05 20:00' -g ColorManagement), filling the persistent journal directory var/log/journal/6a54b66b60514271988a75fc27d4ef55
  with 54 G of logs.
  - 00:11 the kernel began reporting soft-lockups on many CPUs; every trace showed kworkers in wb_workfn/inode_switch_wbs_work_fn, meaning the
  write‑back threads for NVMe disk 259:0 were spinning on a cgroup writeback lock under extreme log-flush pressure.
  - 00:32 systemd-logind hit its watchdog; repeated restart attempts failed because the same writeback stall kept user-space starved, so even
  systemd-coredump timed out.
  - 00:40–00:52 RCU stall warnings and watchdog messages continued until you forced a reboot, leaving the journal unclean (confirmed by