[BUG] Stacking terminal/editor becomes unresponsive/unusable, with varied symptoms (cannot select/copy/type).
I noticed today that upon right-clicking in cosmic-term, the menu persists until a subsequent right-click.
I do not remember this being the case before (been using cosmic since July). The context menu stays even if:
- I left click/type in the terminal
- Switch to a different window on the same workspace
- Switch to a different workspace and come back.
Quick video here: https://photos.app.goo.gl/p8PXfgxQgUG9C9FB9
I found a similar sounding issue in the cosmic-files database, not sure if related: https://github.com/pop-os/cosmic-files/issues/389
I have attached my current cosmic versions. sys_info_sw_2024-Sep-10-1610.txt
As of the date of this comment (Jan 8-9), this issue has popped up again and is happening very often.
In addition to the initial symptom of the right-menu sticking around:
- I also lose the ability to select/copy from the terminal window.
- If I have split terminals, I lose the ability to type entirely into the (previously out of focus) terminal pane.
Exiting/restarting the terminal fixes the issue, but it happens again after 15-30 minutes.
My currently running version is cosmic-term/noble,noble,now 0.1.0~1736285623~24.04~4fd9731
Issue still reproducible(recurring) as of Feb 18 2025 update. cosmic-term/noble,now 0.1.0~1737658298~24.04~23a5851
It would be nice if the menu closed by left-clicking on the terminal of course but also by pressing the esc key.
In addition to all the above symptoms, I just noticed something else that seems to only happen when the bug is manifesting itself, namely that attempting to select via the mouse is causing my terminal window to be horizontally resized (as if I am clicking/dragging the border of the window). This is with recent (early March) updates.
I have replicated the same symptoms in Cosmic Edit as well this morning. Right-click is persisting, and trying to select text is causing the entire window to resize. Current versions I am running:
cosmic-edit/noble,noble,now 0.1.0~1741529916~24.04~bd5009a amd64 [installed,automatic] cosmic-term/noble,now 0.1.0~1741899959~24.04~91f252c amd64 [installed]
Updating headline to clearly reflect that issue makes terminal/editor unusable once it happens.
Adding my latest hardware and cosmic version info. reproduced again with this latest setup, demo video: https://photos.app.goo.gl/6uSAf566Upgsvktz5
sys_info_hw_2025-Mar-18-1351.txt sys_info_sw_2025-Mar-18-1351.txt
Not able to replicate here on any of the systems I have on hand. Would you be able to replicate within a live environment?
I have it replicated on my own machine as we speak, is that what you mean by a live environment? Is there anything I should try to capture?
@mmstick As suspected, I have strong evidence that the issue has to do with stacking the terminal/editor etc with other applications. Once a misbehaving window is unstacked, the issue goes away. Here is an example sequence where the issue happened:
- Have a single un-stacked terminal window running.
- Stack Brave browser with terminal. After switching focus to terminal, issue happened.
- Remove browser from stack (terminal left as single entry in stack), issue is still visible.
- Add browser back to stack, remove terminal from stack. Terminal works fine.
- Add terminal back to stack, issue is again visible.
- Remove browser from stack, then remove terminal from stack as well, issue is gone.
Note that although I was able to cause the issue once, as stated above, I was unable to reproduce it thereafter, so there is still some mystery to it. I have updated the bug record with the above info.
@mmstick @jackpot51 I just want to mention that this issue is still easily reproducible in on my system, making cosmic apps impractical to use in a stack. It would be great if someone could look into it. Jeremy mentioned months ago "I manged to reproduce this issue by using cosmic-term in stacks more often. Right click will clear the context menu, but left clicks and key presses don't appear to work. " which is exactly what I am seeing.
Furthermore, I was able to replicate the issue within a few hours of a fresh install on a separate partition (same computer).