https://bugs.kde.org/show_bug.cgi?id=523971
--- Comment #8 from Ellie <[email protected]> --- If I had to guess, the problem is probably the process launch. Some systems have quite slow I/O. This is especially the case of e.g. the old Steam Deck that used to have an SD Card, for example. This means even for a small graphical program, you're often looking at a launch time of a few seconds simply because the OS loader needs to read all the libraries from disk. This typically won't result in a reasonable screenshot delay. Therefore, if you ask me as a relatively uninformed user, I'm feeling like all the components that can take a screenshot should probably be running once the session starts. So either a spectacle service that runs in the background (although that seems undesirable for other reasons, e.g. RAM footprint), or perhaps the shortcut service should just know to tell KWin directly to take the screenshot and then KWin could launch Spectacle afterward and hand it the image. Wouldn't that perhaps get rid of this problem? -- You are receiving this mail because: You are watching all bug changes.
