# Windows management + super key issues

**URL:** <https://discourse.ubuntubudgie.org/t/windows-management-super-key-issues/2645>\
**Category:** Budgie Desktop\
**Created:** [November 6, 2019, 4:37pm UTC](https://discourse.ubuntubudgie.org/t/windows-management-super-key-issues/2645 "2019-11-06T16:37:40Z")\
**Posts on this page:** 4\
**Page:** 2

<div class="post-metadata">

**Author:** ![Bird12](https://avatars.discourse-cdn.com/v4/letter/b/aca169/32.png) [@Bird12](https://discourse.ubuntubudgie.org/u/Bird12)\
**Post date:** [November 11, 2019, 9:43am UTC](https://discourse.ubuntubudgie.org/t/windows-management-super-key-issues/2645/21 "2019-11-11T09:43:19Z")

</div>

I don’t know if my version is the pre-instalated, I just installed the sistem of the zero and didn’t nothing to the previsualizations.

---

<div class="post-metadata">

**Author:** ![vlijm](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.ubuntubudgie.org/vlijm/32/34_2.png) [@vlijm](https://discourse.ubuntubudgie.org/u/vlijm)\
**Post date:** [November 11, 2019, 10:33am UTC](https://discourse.ubuntubudgie.org/t/windows-management-super-key-issues/2645/22 "2019-11-11T10:33:28Z")

</div>

We did & tried all that during development, but the possible time between destroy and check-for-existence was a dealbreaker. We fixed it then by `error_trap_push()` which even returns a result on (just) destroyed window. No clue why that does not work in op’s case. Never had a single issue. Would be interesting to find out if a specific event or window type is in the picture.

---

<div class="post-metadata">

**Author:** ![vlijm](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.ubuntubudgie.org/vlijm/32/34_2.png) [@vlijm](https://discourse.ubuntubudgie.org/u/vlijm)\
**Post date:** [November 14, 2019, 12:23pm UTC](https://discourse.ubuntubudgie.org/t/windows-management-super-key-issues/2645/23 "2019-11-14T12:23:16Z")

</div>

@Bird12 Would you share your hardware / specs with us? As said above, the attempt to create a window preview crashes if the window does not exist (any more). Most of the time that will be only a very tiny split second between checking on the window and actual preview creation. This is fixed in the code by using Gdk error\_trap(). So far, this is the first case as far as I can see where error\_trap does not do the job, which make me wonder:

- does this happen on a specific type of window?
- does this happen on a specific type of hardware?

If you’d be willing to share, would be much appreciated.

---

<div class="post-metadata">

**Author:** ![Bird12](https://avatars.discourse-cdn.com/v4/letter/b/aca169/32.png) [@Bird12](https://discourse.ubuntubudgie.org/u/Bird12)\
**Post date:** [November 14, 2019, 4:31pm UTC](https://discourse.ubuntubudgie.org/t/windows-management-super-key-issues/2645/24 "2019-11-14T16:31:23Z")

</div>

My hardware:

 ![Captura%20de%20tela%20de%202019-11-14%2013-29-58](https://canada1.discourse-cdn.com/flex035/uploads/ubuntubudgie/original/2X/b/bf76c37a0193699f5595fe673f794b80a1545fc8.png)  
Isn’t on a specific type of window, it’s in every window

[Previous page](https://discourse.ubuntubudgie.org/t/windows-management-super-key-issues/2645.md?page=1)
