Hi, first of all: Thank you for your great work on limux! I really love the UX.
I'm trying to describe my issue below as good as I can - please let me know if there is any extra information I can provide or any other way I can help.
Environment
- OS: Ubuntu 25.10 (Questing Quokka)
- Kernel: 6.17.0-29-generic
- Desktop: KDE Plasma
- Session type: Wayland
- CPU: AMD Ryzen 9 7950X3D
- RAM: 62 GiB
- GPUs:
- NVIDIA GeForce RTX 3070 Ti (primary active)
- AMD Radeon iGPU
- limux package version: 0.1.19
Notes
- The app is running on Wayland under KDE Plasma.
- I also have an NVIDIA proprietary kernel module installed; the kernel-side module reports version 595.58.03.
Relevant log lines
May 25 10:20:20 <host> limux[5920]: Unrecognized value "gl-disable-gles". Try GDK_DEBUG=help
May 25 10:20:20 <host> limux[5920]: Unrecognized value "vulkan-disable". Try GDK_DEBUG=help
May 25 10:20:20 <host> limux[5920]: Unknown key gtk-modules in /home/<username>/.config/gtk-4.0/settings.ini
May 25 10:20:20 <host> limux[5920]: limux: control socket at /run/user/1000/limux/limux.sock
May 25 22:41:59 <host> limux-host[46941]: gtk_widget_get_parent: assertion 'GTK_IS_WIDGET (widget)' failed
May 25 22:42:29 <host> limux-host[46941]: gtk_widget_get_parent: assertion 'GTK_IS_WIDGET (widget)' failed
May 25 23:04:59 <host> limux-host[46941]: gtk_widget_get_parent: assertion 'GTK_IS_WIDGET (widget)' failed
("relevant" according to Codex CLI with GPT5.4-mini helping me collect the info for this report - apologies if it turns out not to be relevant)
What I’m seeing
The UI becomes unresponsive from time to time. I do not currently have a reliable reproduction sequence.
This time, it became unresponsive when I attempted to rename one of multiple tabs (see screenshot).
First I right clicked the tab name -> Rename, got an edit input field that didn't respond. I did the same clicks again hoping the first input may close, and got a second edit input field. I was able to type into that second one and confirm with enter, the tab was renamed, the second input field stayed open, and the whole UI froze.
The journal shows repeated GTK assertions in limux-host (gtk_widget_get_parent: assertion 'GTK_IS_WIDGET (widget)' failed) around the time of the freeze. I do not know whether this is the root cause, but it seems related to the UI becoming unresponsive.
[EDIT]
I left the frozen window open for about 20 minutes and asked Codex-CLI to gather more information.
It told me:
During the freeze, limux-host was repeatedly logging gtk_widget_get_parent: assertion 'GTK_IS_WIDGET (widget)' failed for an extended period. When sampled live, the process was sleeping in sock_alloc_send_pskb, with 80 threads and high RSS, which suggests the UI was hung in socket/IPC-related work rather than crashing.
Hi, first of all: Thank you for your great work on limux! I really love the UX.
I'm trying to describe my issue below as good as I can - please let me know if there is any extra information I can provide or any other way I can help.
Environment
Notes
Relevant log lines
("relevant" according to Codex CLI with GPT5.4-mini helping me collect the info for this report - apologies if it turns out not to be relevant)
What I’m seeing
The UI becomes unresponsive from time to time. I do not currently have a reliable reproduction sequence.
This time, it became unresponsive when I attempted to rename one of multiple tabs (see screenshot).
First I right clicked the tab name -> Rename, got an edit input field that didn't respond. I did the same clicks again hoping the first input may close, and got a second edit input field. I was able to type into that second one and confirm with enter, the tab was renamed, the second input field stayed open, and the whole UI froze.
The journal shows repeated GTK assertions in limux-host (gtk_widget_get_parent: assertion 'GTK_IS_WIDGET (widget)' failed) around the time of the freeze. I do not know whether this is the root cause, but it seems related to the UI becoming unresponsive.
[EDIT]
I left the frozen window open for about 20 minutes and asked Codex-CLI to gather more information.
It told me:
During the freeze, limux-host was repeatedly logging gtk_widget_get_parent: assertion 'GTK_IS_WIDGET (widget)' failed for an extended period. When sampled live, the process was sleeping in sock_alloc_send_pskb, with 80 threads and high RSS, which suggests the UI was hung in socket/IPC-related work rather than crashing.