| Summary: | Plasma hangs when launching a native game | ||
|---|---|---|---|
| Product: | [Plasma] plasmashell | Reporter: | Jannis Göing <jannis.goeing> |
| Component: | XembedSNIProxy | Assignee: | Plasma Bugs List <plasma-bugs-null> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | major | CC: | kde, materka, nate, noahadvs |
| Priority: | NOR | ||
| Version First Reported In: | 5.25.3 | ||
| Target Milestone: | 1.0 | ||
| Platform: | Arch Linux | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Jannis Göing
2022-07-27 15:11:45 UTC
This seems to be circumventable by turning of "Allow Apps to disable compositing" - but games like CS:GO are not enjoyable like this, the games feels like running at 30/60hz when this is turned on (eventough fps is high) on a 144hz Monitor. As soon as it is turned off and the game restarted, the game runs great but the problems with the panels comes back. > my entire Desktop crashes/hangs Hangs and crashes are different things. If something is crashing, what specifically is the process crashing? We also need a backtrace of it so we can figure out what's going on. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports. Or is nothing crashing, and what you're seeing is a hang? I think it just hangs, since I also could find any error and it recovers completely most of the times after the game is closed. I'll see if I can Figure out a useful backtrace. It really seems to not be crashing, so i don't know how/if i can get a backtrace. It seems that whenever compositing is blocked (i guess wine/proton games on't block compositing?) the panels are completely frozen. https://nextcloud.jannis-goeing.de/s/dN8P2YCRgt9mr6p <- this is a demonstration of what's happening. First try ist with "allow blocking compositing" disabled and alkl works fine and then i disable it again and try again. And a few seconds after closing it, it recovers (In reply to Jannis Göing from comment #4) > It really seems to not be crashing, so i don't know how/if i can get a > backtrace. It seems that whenever compositing is blocked (i guess > wine/proton games on't block compositing?) the panels are completely frozen. > > https://nextcloud.jannis-goeing.de/s/dN8P2YCRgt9mr6p <- this is a > demonstration of what's happening. First try ist with "allow blocking > compositing" disabled and alkl works fine and then i disable it again and > try again. And a few seconds after closing it, it recovers https://nextcloud.jannis-goeing.de/s/DXi6NPWa3YbdKWo * korrekt link After some troubleshooting and dogging, seems that running killall xembedsniproxy did the trick, after that it's no longer freezing. i only looked for logs that were somewhere visibly kde related but then i stumbled over many many messages in journalctl that were related to this, saying 'xembedsniproxy[4135]: Container window visible, stack below' but there was no stack and no other message. Thanks for the info! This seems to also be resolved when quitting all applications with tray icons (presumably that use xembedsniproxy). As soon as i start one again, like Bitwarden, the issue immediately returns. Might be related to https://bugs.kde.org/show_bug.cgi?id=425271 ? Is this still a problem? I have xembedsniproxy running in the background, but experienced no hangs or crashes with Plasma 5.26.1 on the Steam Deck while loading Left 4 Dead 2, Terraria and Kerbal Space Program. I experienced hangs while loading Left 4 Dead 2, but I'm pretty sure that was because of a sudden spike in storage read/write rates (more of an issue with the way a game loads and how the kernel handles the load). Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |