hluk/CopyQ

copyq crashes after waking up from suspend

Open

#3475 opened on Mar 11, 2026

View on GitHub
 (1 comment) (1 reaction) (0 assignees)C++ (7,372 stars) (419 forks)batch import
Waylandawaiting-user-responsebughelp wanted

Description

Describe the bug copyq crashes after waking up from suspend doesn't happen all the time, like once every 2-3 cycles, more likely to happen with longer sleeps it may be a bug with the Hyprland compositor or something else upstream because same issue happens with a few other apps

To Reproduce

  1. start copyq
  2. suspend with systemctl suspend
  3. wake it up later
  4. copyq process is gone

Expected behavior it continues to work after suspend and wake

Version, OS and Environment CopyQ Clipboard Manager 13.0.0 Qt: 6.10.0 KNotifications: 6.19.0 Compiler: GCC Arch: x86_64-little_endian-lp64 OS: Arch Linux WM: Hyprland Installation method: pacman

Additional context logs

Warning <cmd/monitorClipboard-1801>: [default] The Wayland connection experienced a fatal error: Invalid argument
Warning <Server-1490>: [default] The Wayland connection broke. Did the Wayland compositor die?
ERROR <cmd/show-96301>: Cannot connect to server! Start CopyQ server first.

stdout from recent attempt

wl_display#1: error 0: invalid object 26
Warning: [default] The Wayland connection experienced a fatal error: Invalid argument

Contributor guide

Tech stack
cppshell
Domain
desktop
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
C++QtWayland basics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50
Research direction
Investigate the crash by examining the Wayland connection error logs. Focus on the `monitorClipboard` and `Server` classes in the source code, particularly their handling of Wayland connections during suspend/resume events. Look for any missing reconnection logic or improper handling of Wayland display errors. The logs indicate a fatal error on the Wayland connection, so check the clipboard monitor's code for error recovery.