You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After running a process in the terminal, the green/red icon that represents the exit status of the process sometimes remains even after you activate the tab. I think it's limited to long-running processes, and since I always have more than one tab open it might be limited to such use-cases.
Steps to Reproduce
Start a long-running process, such as a gcc compilation job
Activate another window (or maybe another terminal tab), and let the process finish
Once the process has finished, a green/red icon (depending on the exit status of the process) will show up next to the directory name in the tab
Activate the tab to look at the process output
The icon remains
Expected Behavior
The icon goes away once the tab has been activated - at least that's how it was in 7.x.
OS Version
8.x (Circe)
Session Type
Secure Session (Wayland)
Software Version
Latest release (I have run all updates)
Log Output
No response
Hardware Info
8 × AMD Ryzen 7 4800U with Radeon Graphics
AMD® Renoir [Radeon RX Vega 6 (Ryzen 4000/5000 Mobile Series)]
The text was updated successfully, but these errors were encountered:
What Happened?
After running a process in the terminal, the green/red icon that represents the exit status of the process sometimes remains even after you activate the tab. I think it's limited to long-running processes, and since I always have more than one tab open it might be limited to such use-cases.
Steps to Reproduce
Expected Behavior
The icon goes away once the tab has been activated - at least that's how it was in 7.x.
OS Version
8.x (Circe)
Session Type
Secure Session (Wayland)
Software Version
Latest release (I have run all updates)
Log Output
No response
Hardware Info
8 × AMD Ryzen 7 4800U with Radeon Graphics
AMD® Renoir [Radeon RX Vega 6 (Ryzen 4000/5000 Mobile Series)]
The text was updated successfully, but these errors were encountered: