hluk/CopyQ

copyq crashes after waking up from suspend

Open

#3,475 创建于 2026年3月11日

在 GitHub 查看
 (1 评论) (1 反应) (0 负责人)C++ (7,372 star) (419 fork)batch import
Waylandawaiting-user-responsebughelp wanted

描述

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

贡献者指南

技术栈
cppshell
领域
desktop
议题类型
bug
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
1-2 days
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
fresh
清晰度议题是否清楚说明期望改动、验收标准和下一步。
clear
前置要求
C++QtWayland basics
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
50
研究方向
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.