-
Notifications
You must be signed in to change notification settings - Fork 310
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WSLg crashes when take a screenshot with QQ #348
Comments
@NijiharaTsubasa, thanks for reporting the issue, may I confirm the QQ you used is https://im.qq.com/linuxqq/index.html ? and installed the corresponding package from https://im.qq.com/linuxqq/download.html ? thanks! |
Not only caused by QQ , if anything try to copy image data to clipboard then WSLg crashes. |
@hideyukn88 I'm using Windows QQ to take the snapshot |
@NijiharaTsubasa and @sanjitako, would you please update WSLg to version 1.0.26 at https://github.com/microsoft/wslg/releases/tag/v1.0.26, and send us dump files at /mnt/wslg/dumps? thanks! |
Sorry for late response. |
I've been experiencing a related version of this problem. I'm not actually using WSLg, it's just running as it was installed as part of the Windows 11 upgrade. When I take a screenshot with Greenshot (1.2.10.6) and copy it to the clipboard, WSLg appears to die and get restarted. This shows in process explorer as mstsc processes starting and stopping every second or so: This also causes system tray icons to flash once a second, and sometimes grabs focus. Clearing the clipboard (or copying some text to it) makes the problem stop. Dump: core.zip Additional comments:
|
I have this issue too, seems the clipboard sharing feature crashes mstsc.exe when QQ screenshot or some other tools copy images into the clipboard. But Win+Shift+S works fine. |
@richardlawley, @liyafe1997, this issue should be fixed by newer release of WSLg from aka.ms/wslstorepage, please update, thanks! |
Environment
Steps to reproduce
Note that there's no problem with system's snipping tool, only QQ's one causing the problem.
WSL logs:
/mnt/wslg
logs.zip
core.weston.gz
Expected behavior
Everything works fine
Actual behavior
The text was updated successfully, but these errors were encountered: