Skip to content
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

KWin compositor crashes on scrcpy launch #114

Closed
LER0ever opened this issue Apr 4, 2018 · 6 comments
Closed

KWin compositor crashes on scrcpy launch #114

LER0ever opened this issue Apr 4, 2018 · 6 comments

Comments

@LER0ever
Copy link

LER0ever commented Apr 4, 2018

On Plasma Desktop, compositor crashes on every scrcpy launch and recovers after scrcpy exits.

Actual Behavior

Desktop effects and transparency not working, i.e. compositor exits or crashes.

Environment

Desktop: KDE Plasma 5.12
Kernel: 4.16.0
Graphics: NVIDIA 390
Distro: Manjaro Linux

@rom1v
Copy link
Collaborator

rom1v commented Apr 4, 2018

@LER0ever
Copy link
Author

LER0ever commented Apr 4, 2018

While there is nothing in stdout, there is a bunch of QPainter errors that may or may not be related to this. I've uploaded the journalctl -f output here

screenshot_20180404_181922

Also, I found that after the compositor recovers (that is after I Ctrl-C'ed the scrcpy), although the transparency and visual effects are back, I cannot take Window screenshot (full screenshot is fine), KWin crashes along with the compositor after I request the screenshot of my terminal window.

@LER0ever
Copy link
Author

LER0ever commented Apr 4, 2018

Ahh, sorry I did not read your links before replying... The issue is indeed due to SDL blocking the compositor, and I manage to work around this using KDE Window Rules (Preventing scrcpy from blocking compositors)


Attaching the Window Rule config in case someone also need a temporary fix on this problem.
image
image

@rom1v
Copy link
Collaborator

rom1v commented Apr 5, 2018

Thank you for the workaround. 👍 I added an entry in the FAQ.

@Dakai
Copy link

Dakai commented May 15, 2019

@LER0ever Thank you! It works like a charm.

@rom1v
Copy link
Collaborator

rom1v commented May 15, 2019

Does #522 fix the initial issue, or is it unrelated?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants