With opened menu, left-click outside of it not close the menu.As the menu is not the same as the others, left-click open the app, while right-click open the context menu.
If I'm right officially currently GNOME Panel do not differentiate left- or right-click on them.The very first right-click not works, we have to click on it more times.It is different from visual and also fromworking method aspects: The menu is not the same type of menu which 'every other' normal systray icons offer, but at least it works.So summarized: after installing dbus-x11, and edit the corresponding flatpak app shortcut ( /var/lib/flatpak/app//current/active/export/share/applications/) to Exec=dbus-launch /usr/bin/flatpak run -branch=stable -arch=x86_64 -command=viber instead of original execution attribution, the context menu of the systray icon works.īut there are some comments on it, just to know: On 'stock' (from this aspect) Ubuntu 22.10 nightly, after installing dbus-x11 package, despite I'm on Wayland the solution works. If I try to open these files with The GNOME image viewer, they are shown normally. I can find in my /var/log/messages these entries:Īug 24 13:30:45 my-pc-name journal: invalid image format: /home/my-username/.var/app//cache/runtime-my-username/qt-trayicon-ZwnrsD.png Aug 24 13:30:45 my-pc-name journal: invalid image format: /home/my-username/.var/app//cache/runtime-my-username/qt-trayicon-ZwnrsD.png Aug 24 13:30:45 my-pc-name journal: invalid image format: /home/my-username/.var/app//cache/runtime-my-username/qt-trayicon-ZwnrsD.png Aug 24 13:30:45 my-pc-name journal: invalid image format: /home/my-username/.var/app//cache/runtime-my-username/qt-trayicon-ZwnrsD.png Aug 24 13:30:45 my-pc-name journal: invalid image format: /home/my-username/.var/app//cache/runtime-my-username/qt-trayicon-ZwnrsD.png Aug 24 13:30:45 my-pc-name journal: invalid image format: /home/my-username/.var/app//cache/runtime-my-username/qt-trayicon-ZwnrsD.png Aug 24 13:34:26 my-pc-name journal: invalid image format: /home/my-username/.var/app//cache/runtime-my-username/qt-trayicon-QzLLOE.png Aug 24 13:34:26 my-pc-name journal: invalid image format: /home/my-username/.var/app//cache/runtime-my-username/qt-trayicon-QzLLOE.png Aug 24 13:34:26 my-pc-name journal: invalid image format: /home/my-username/.var/app//cache/runtime-my-username/qt-trayicon-QzLLOE.png Aug 24 13:34:26 my-pc-name journal: invalid image format: /home/my-username/.var/app//cache/runtime-my-username/qt-trayicon-QzLLOE.png Aug 24 13:34:26 my-pc-name journal: invalid image format: /home/my-username/.var/app//cache/runtime-my-username/qt-trayicon-QzLLOE.png Aug 24 13:34:26 my-pc-name journal: invalid image format: /home/my-username/.var/app//cache/runtime-my-username/qt-trayicon-QzLLOE.png Scour yet another GitHub issue page and hopefully make Linux less Hopefully this gets merged so that people using Viber don't have to
Sub-package regexes, but not actual string regexes, because if that were Secondly: Flatpak doesn't allow string regexes. "-$randomNumber-1".įor one: Letting Viber talk to a bus won't work as it's **initiating** It instead opts to create it's own under the name So what's the rationale, why does Viber need an access to an entireīasically since Viber DOES NOT use the "" bus, Thirdly, keeping track of background tasks via the tray icons is cool as System regardless whether the application window is open or not is Secondly, having the ability to be aware that Viber's running on the (Andįirstly, not being able to quit Viber is ONE BIG issue. Simply due to the issues that not having an tray icon would cause. "org.kde.*" namespace being exposed, I think it's worth to merge it While this "fix" does introduce holes in the sandbox, namely the entire This has been a long running issue flathub#4 and it's been bothering me as
0 kommentar(er)
