Personal / community use only. I use TeamViewer to help my parents and my uncle. Not a commercial ticket.
Summary
The TeamViewer GUI (/opt/teamviewer/tv_bin/TeamViewer) SIGSEGVs on the main thread about 99 ms after logging that XRandR CRTC 0 has no outputs and falling back to NoXRandR. The daemon (teamviewerd) stays up. This is not an active remote session. The GUI had been idle overnight.
Environment
- TeamViewer 15.79.4 (official DEB payload; Arch AUR teamviewer 15.79.4-1)
- Bundled Qt 5.15.19, platform: xcb / XWayland (X11 GUI path, not portal/wlroots Wayland)
- OS: Omarchy (Arch-based) 4.0.2; compositor Hyprland 0.56.2 (Aquamarine, not wlroots)
- Displays: HDMI-A-1 1920x1080@60 scale 1.25 + DP-1 1920x1200
- Signal: SIGSEGV, si_code=SEGV_MAPERR; not OOM; first TeamViewer crash on this machine
Timeline (local EDT, 2026-09-02)
13:43:14 MonitorInfo CRTC HDMI-A-1 1920x1080@60Hz DPI=96; Virtual Desktop [0, 0, 3840, 1200]
13:45:41 MonitorInfo: [XRandR 1.2] CRTC 0 has no outputs
13:45:41 No monitor attached, falling back to NoXRandR
13:45:41 Crash: stack dump written, Errorcode=11
13:46:13 Process received fatal SIGSEGV
Kernel DRM did not log a physical unplug. Hyprland still had both outputs. The empty CRTC is what XWayland reported to the X11 GUI.
Stack
Crashing thread was in QSocketNotifier::activated (bundled libQt5Core.so.5). Frame 0 is inside stripped TeamViewer. Instruction at 0x173d46b: movslq 0xe0(%rax), %rbx when ebx == -1 (invalid monitor index), then DPI-style cvtsi2ss/divss. rax was unmapped/NULL (SEGV_MAPERR).
Expected
The NoXRandR fallback should not dereference a null/invalid monitor object.
Arch is unofficial and Wayland is experimental. Reporting because this is the X11 MonitorInfo fallback path, which other Linux setups can hit (hotplug, DPMS, XWayland RandR glitches). One-off so far. Happy to paste .stack and redacted logs. Cores omitted (process memory). Forum attachments allow images only, not zip/txt.
