https://bugs.kde.org/show_bug.cgi?id=359567
--- Comment #5 from Kiril Vladimiroff <ki...@vladimiroff.org> --- I knew that Spotify is using Chromium now, but I've ruled out Chromium to be responsible for this, because suspend doesn't happen when I start Chromium, Chrome or some Chrome app (like SlackDeck for example). However, I've just learned that Spotify is NOT a Chromium app, but uses Chromium Embedded Framework[1]. According to what I've been able to find the Steam client for Linux is also using CEF. Starting Steam involves updating (if not already up-to-date), logging in (if not already), before showing the actual client. The first two windows cause exactly the same issue: 1. Start Steam for the first time since weeks (i.e. it's not up-to-date) 2. Starts updating, showing a small window it a progress bar. 3. Composite goes to suspend. 4. I resume it with a shortcut. 5. Update is complete and login window is being showed. 6. Composite goes to suspend. 7. I resume it with a shortcut. 8. Successful login leads to opening the actual client window, *without* suspending the compositor. Once updated, if I simply start it (i.e. already logged in and up-to-date) it goes directly to step 8 and everything is fine. However if I log out, stop the client and try starting it again (i.e. still up-to-date, so steps 2, 3, 4 are omitted), the compositor gets suspended because of the login window. I will attach the output from xprop when clicking on the Steam's login window. Could it be that something in CEF is causing this? [1] https://en.wikipedia.org/wiki/Chromium_Embedded_Framework -- You are receiving this mail because: You are watching all bug changes.
