# KDE switches focus to Aseprite when screen is turned off

**URL:** https://community.aseprite.org/t/kde-switches-focus-to-aseprite-when-screen-is-turned-off/28924
**Category:** Help
**Created:** [October 14, 2026, 2:06pm UTC](https://community.aseprite.org/t/kde-switches-focus-to-aseprite-when-screen-is-turned-off/28924 "2026-10-14T14:06:54Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![oca](https://community.aseprite.org/letter_avatar/oca/32/5_5575768a8748004e209b776fc1b2916d.png) [@oca](https://community.aseprite.org/u/oca)
#### Post date: [October 14, 2026, 2:06pm UTC](https://community.aseprite.org/t/kde-switches-focus-to-aseprite-when-screen-is-turned-off/28924/1 "2026-10-14T14:06:54Z")

</div>

I am having an issue where often when my screen turns off, due to a keyboard short cut, time out, or the lid closing, my computer will switch apps and desktops to the one with Aseprite on it. This is annoying as I tend to leave the app open. Why is this happening and how can I stop it?

Using Arch with KDE 6.7

Aseprite installed as an app image from the website

---

<div class="post-metadata">

### Author: ![dacap](https://community.aseprite.org/user_avatar/community.aseprite.org/dacap/32/10_2.png) [@dacap](https://community.aseprite.org/u/dacap)
#### Post date: [October 15, 2026, 1:42pm UTC](https://community.aseprite.org/t/kde-switches-focus-to-aseprite-when-screen-is-turned-off/28924/2 "2026-10-15T13:42:10Z")

</div>

Hi @oca, what specific version are you using? We’ve solved some issues about Aseprite being restored when it’s minimized on Linux in the latest v1.3.18.6 that you might would like to check.

---

<div class="post-metadata">

### Author: ![oca](https://community.aseprite.org/letter_avatar/oca/32/5_5575768a8748004e209b776fc1b2916d.png) [@oca](https://community.aseprite.org/u/oca)
#### Post date: [October 15, 2026, 2:32pm UTC](https://community.aseprite.org/t/kde-switches-focus-to-aseprite-when-screen-is-turned-off/28924/3 "2026-10-15T14:32:50Z")

</div>

Thanks for the response! I was using 1.3.17. I have just installed the new version, I will see if the issue persists.
