Is there an existing issue for this?

• I have searched the existing issues

Platform

Linux

OS version

Fedora 44, KDE Edition, Plasma 6.6.5, Frameworks 6.26.0, Qt 6.11.1, Kernel 7.0.9-205.fc44.x86_64 (64-bit)

App version

6.5.2 (143), Flatpak

Current Behavior

When SimpleX is closed to the system tray, it can't subsequently be restored from it. Clicking on the system tray icon seems to do nothing (although it is clearly active, as intended, in that state, as the incoming message count changes as you would expect and so on).

This also has the effect of making the application uncloseable (aside from killing it from the process manager or similar) when the 'close to system tray' setting is activated.

It is a different issue from this: #6995. In my case, the app opens just fine and works perfectly normally... until you close it with the 'close to system tray' option enabled. Then see above.

I assume this was the original discussion around the feature I'm describing: #3154

~ ~ ~

This post is about SimpleX's behaviour on KDE Plasma but, as an aside, why is close to system tray not available on GNOME? GNOME has the concept, even if stock GNOME hides 'apps running in the background' in the power menu. System tray icons for those apps can be added with one of the most downloaded extensions to GNOME and are visible by default in Ubuntu.

Expected Behavior

• Right-click on system tray icon reveals a context menu with options to 'Show/Hide' or 'Open SimpleX' or similar, and (crucially) 'Quit'
• Left-click on system tray icon opens (i.e. restores) the SimpleX window
• CTRL-Q shuts down the application
  Expectations based on what all the other icons in my system tray do when interacted with.

Steps To Reproduce

1. Ensure settings -> appearance -> Minimise to tray when closing window is enabled
2. Close the SimpleX window in the usual way (e.g. close x at the top right)
3. Left or right-click on the system tray icon
4. Nothing happens - completely unresponsive. Application is clearly active, however. The incoming message count changes and so on.

Relevant log output

Don't think there are any clues in the log.  These are all from starting it.  Closing it (to tray) then interacting with the tray generated no further output:

philip@fedora:~$ flatpak run -v chat.simplex.simplex
F: Opening system flatpak installation at path /var/lib/flatpak
F: Opening user flatpak installation at path /home/philip/.local/share/flatpak
F: Opening user flatpak installation at path /home/philip/.local/share/flatpak
F: Opening system flatpak installation at path /var/lib/flatpak
F: Skipping parental controls check for app/chat.simplex.simplex/x86_64/stable since parental controls are disabled globally
F: Opening user flatpak installation at path /home/philip/.local/share/flatpak
F: Opening system flatpak installation at path /var/lib/flatpak
F: /lib32 does not exist in runtime
F: Cleaning up unused container id 3006952123
F: Cleaning up per-app-ID state for chat.simplex.simplex
F: Allocated instance id 1344970282
F: Add defaults in dir /chat/simplex/simplex/
F: Add locks in dir /chat/simplex/simplex/
F: Allowing dri access
F: Allowing homedir access
F: Allowing x11 access
F: Allowing pulseaudio access
F: Pulseaudio user configuration file '/home/philip/.config/pulse/client.conf': Error opening file /home/philip/.config/pulse/client.conf: No such file or directory
F: Running '/usr/bin/bwrap --args 70 -- /usr/bin/xdg-dbus-proxy --args=72'
F: Running '/usr/bin/bwrap --args 69 -- simplex'

If the missing client.conf pertinent?  It being missing was not due to anything I did...