Bug report compiled with help of kiro-cli. ### Checklist - [x] I'm using the latest version of the extension (Run `glab --version`) - Extension version: 1.85.2 (tested), currently reverted to 1.82.0 (working) - [x] Operating system and version: Ubuntu 22.04, Linux 6.8.0-94-generic x86_64 - [x] Gitlab.com or self-managed instance? self-managed - [x] GitLab version (if self-managed) 18.6.6 - [x] I have performed `glab auth status` to check for authentication issues - [x] Run the command in debug mode (like `DEBUG=true glab mr list`) and attach any useful output ### Summary glab snap versions 1.83.0 and newer hang indefinitely with 100% CPU usage when executing `glab ci view` command due to SIGTTOU signal blocking terminal output. Version 1.82.0 works correctly. ### Environment - OS: Linux 6.8.0-94-generic x86_64 - SHELL: /bin/bash - TERM: xterm-256color - GLAB: glab 1.82.0 (b932a8d) - reverted from 1.85.2 due to hang Other: - snapd version: 2.73+ubuntu22.04 - snap series: 16 - Installation method: snap (latest/stable channel) ### Steps to reproduce 1. Install glab snap version 1.83.0 or newer: `sudo snap refresh glab` 2. Navigate to a git repository with GitLab remote 3. Run `DEBUG=true /snap/bin/glab ci view` 4. Process hangs indefinitely with 100% CPU usage after entering TUI mode ### What is the current _bug_ behavior? When running `glab ci view`, the command successfully executes git operations and enters TUI mode (alternate screen buffer), but then immediately hangs with 100% CPU usage. The process receives SIGTTOU (terminal output control signal) and becomes blocked trying to write to the terminal. Debug output shows: 2026/02/16 08:08:27.446312 cmd_run.go:1598: WARNING: will not expose Kerberos tickets' path: Unsupported KRB5CCNAME: DIR:/tmp/krb5cc_1000 [git remote -v] [git config --get-regexp ^remote\..*\.glab-resolved$] [git symbolic-ref --quiet --short HEAD] Then TUI initialization sequences appear (`[?1049h[22;0;0t[?1h=[?25l[H[2J`) followed by complete hang. strace shows: `--- stopped by SIGTTOU ---` ### What is the expected _correct_ behavior? `glab ci view` should successfully enter interactive TUI mode and display pipeline information as it does in version 1.82.0, without hanging or terminal control issues. ### Relevant logs and/or screenshots Captured with `script -c "DEBUG=true timeout 30 /snap/bin/glab ci view" /tmp/glab-output.log`: Script started on 2026-02-16 08:04:48-05:00 [TERM="xterm-256color" TTY="/dev/pts/1" COLUMNS="146" LINES="37"] 2026/02/16 08:04:48.910017 cmd_run.go:1598: WARNING: will not expose Kerberos tickets' path: Unsupported KRB5CCNAME: DIR:/tmp/krb5cc_1000 [git remote -v] [git config --get-regexp ^remote\..*\.glab-resolved$] [git symbolic-ref --quiet --short HEAD] [?1000l[?1002l[?1003l[?1006l[?2004l[?1049h[22;0;0t[?1h=[?25l[H[2J[>4;2m[>1u[?9001h Script done on 2026-02-16 08:05:21-05:00 [COMMAND_EXIT_CODE="124"] strace output when attaching to hung process: ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ stopped by SIGTTOU --- ### Possible fixes The issue is a terminal control/job control bug in the TUI initialization code introduced in version 1.83.0. The process is blocked by SIGTTOU when attempting to write to the terminal. Possible fixes: - Review terminal control handling in TUI initialization code added/changed after 1.82.0 - Ensure proper terminal foreground process group handling before TUI writes - Check if snap confinement is interfering with terminal control signals - Add proper SIGTTOU signal handling or terminal control checks before entering TUI mode Root cause: Process attempts terminal output without proper terminal control, receives SIGTTOU, and enters infinite loop trying to write. Workaround: Revert to 1.82.0 with `sudo snap refresh glab --channel=1.82.0/stable` or install glab via non-snap method.