# DemoRunner crashes gnome-shell on manjaro

**URL:** <https://forum.juce.com/t/demorunner-crashes-gnome-shell-on-manjaro/63947>\
**Category:** Linux\
**Created:** [October 26, 2024, 12:37am UTC](https://forum.juce.com/t/demorunner-crashes-gnome-shell-on-manjaro/63947 "2024-10-26T00:37:02Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![xor1](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/xor1/32/19606_2.png) [@xor1](https://forum.juce.com/u/xor1)\
**Post date:** [October 26, 2024, 12:37am UTC](https://forum.juce.com/t/demorunner-crashes-gnome-shell-on-manjaro/63947/1 "2024-10-26T00:37:02Z")

</div>

Moin,

I just tried to run the **DemoRunner** from JUCE v8.0.3 on linux66 manjaro GNOME, but it crashes my GNOME session:

```auto
...
Okt 25 19:24:36 manjarobox gnome-shell[5307]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x280000a
Okt 25 19:24:36 manjarobox gnome-shell[5307]: Received an X Window System error.
                                         This probably reflects a bug in the program.
                                         The error was 'BadWindow (invalid Window parameter)'.
                                           (Details: serial 25188 error_code 3 request_code 2 (core protocol) minor_code 0)
                                           (Note to programmers: normally, X errors are reported asynchronously;
                                            that is, you will receive the error a while after causing it.
                                            To debug your program, run it with the MUTTER_SYNC environment
                                            variable to change this behavior. You can then get a meaningful
                                            backtrace from your debugger if you break on the mtk_x_error() function.)
Okt 25 19:24:36 manjarobox gnome-shell[5307]: == Stack trace for context 0x564a4c8bf790 ==
Okt 25 19:24:36 manjarobox gnome-shell[5307]: #0 564a4c9a9898 i resource:///org/gnome/shell/ui/init.js:21 (e69bb370bf0 @ 48)
...

```

If I comment out the call to the **setIconImage** method in the **DemoTaskbarComponent** constructor, the DemoRunner GUI app starts and everything seems to be fine:

 ![Screenshot from 2024-10-26 02-18-05](https://us1.discourse-cdn.com/flex026/uploads/juce/original/3X/4/9/492ef7767d6fb29471cb418c01bc9db922eb6cda.png)

Of course, this line cannot simply be deleted, but does anyone have any idea what the problem might be?

TIA & Cheers

---

<div class="post-metadata">

**Author:** ![xor1](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/xor1/32/19606_2.png) [@xor1](https://forum.juce.com/u/xor1)\
**Post date:** [October 26, 2024, 1:08am UTC](https://forum.juce.com/t/demorunner-crashes-gnome-shell-on-manjaro/63947/2 "2024-10-26T01:08:27Z")

</div>

I find it extremely interesting that although the GNOME session crashes (white error screen with the logout button), I can still view the open windows via the taskbar and the window switcher. I can also see the DemoRunner running.

I could not screenshot the GNOME snap screen, but here the debugger ran over the **SetIconImage** method. So either no exception is thrown, or it is caught somewhere?!

Does anyone know anything about this?

 ![Screenshot from 2024-10-26 02-57-27](https://us1.discourse-cdn.com/flex026/uploads/juce/original/3X/c/5/c5e001eaa3584f705dd0b2c1815d19926e89b36f.png)

---

<div class="post-metadata">

**Author:** ![xor1](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/xor1/32/19606_2.png) [@xor1](https://forum.juce.com/u/xor1)\
**Post date:** [October 26, 2024, 1:16am UTC](https://forum.juce.com/t/demorunner-crashes-gnome-shell-on-manjaro/63947/3 "2024-10-26T01:16:12Z")

</div>

Btw. the GNOME error screen looks like this (not my screen, but similar image):

 ![image](https://us1.discourse-cdn.com/flex026/uploads/juce/original/3X/0/1/019d1ddfccf9aa88f58b698fe285d316e80ffd6b.jpeg)

---

<div class="post-metadata">

**Author:** ![xor1](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/xor1/32/19606_2.png) [@xor1](https://forum.juce.com/u/xor1)\
**Post date:** [October 27, 2024, 1:10pm UTC](https://forum.juce.com/t/demorunner-crashes-gnome-shell-on-manjaro/63947/4 "2024-10-27T13:10:15Z")

</div>

Okay, I’m kind of replying to my own thread 😄

I found this issue in the JUCE git repo: [[Bug]: [Ubuntu 24.04] SystemTrayIconComponent Crashes Desktop Session · Issue #1421 · juce-framework/JUCE · GitHub](https://github.com/juce-framework/JUCE/issues/1421)

And guess what, after disabling the _AppIndicator and KStatusNotifierItem support_, which was enabled on my system, the DemoRunner app starts 🙂

But now the SystemTrayIcon is in the upper left corner of my desktop. That’s strange, isn’t it?

 ![image](https://us1.discourse-cdn.com/flex026/uploads/juce/original/3X/c/1/c131ff081ba7b5400ae1a1600cbc7cd94d4396d5.jpeg)