I was looking for info on an issue with Notifications of ProtonVPN app
I did notice a thread about notification errors related to bluetooth - this seems different
Notification is no longer working in QuBes-4.3 and Debian 13 xfce template
it was fine in qubes-4.2 with Debian 12
it is failing with this error:
$ protonvpn-app
Unrecognized value "gl-disable". Try GDK_DEBUG=help
Unrecognized value "vulkan-disable". Try GDK_DEBUG=help
2026-01-30T11:18:42.575418+00:00 | proton.vpn.core.connection:508 | INFO | CONN:STATE_CHANGED | Disconnected (initial state)
2026-01-30T11:18:42.878217+00:00 | proton.vpn.app.gtk.app:56 | INFO | APP:PROCESS_START | self=<app.App object at 0x794574914d40 (proton+vpn+app+gtk+app+App at 0x1b183980)>
2026-01-30T11:18:42.984458+00:00 | proton.vpn.app.gtk.widgets.main.tray_indicator:122 | WARNING | Tray icon enabled on an unsupported Desktop Environment
2026-01-30T11:18:42.986423+00:00 | proton.vpn.app.gtk.widgets.main.tray_icon:264 | WARNING | TRAY_ICON:STATUS_NOTIFIER_WATCHER_REGISTRATION_FAILED | Failed to register to StatusNotifierWatcher
config of notifications in appvm - same as it was in debian12 :
thanks for the suggestion, but this package is already installed:
$ sudo apt install gnome-shell-extension-appindicator
gnome-shell-extension-appindicator is already the newest version (59-4).
once started, protonvpn-app will minimise to task-bar
if closed, it will remain in background
if you try to start another instance, the instance running will re-surface
(correct behaviour)
No solution but I just want to validate that I am also experiencing this issue using Fedora 43. I had to rebuild sys-vpn and not enable “start app minimized” in order to have access to the protonvpn app.
Did this worked out for you? I had to roll back from a backup in order to have it in previous state, but having not updated qubes makes me nervous, so I would prefer to find working solution.
The issue neither has anything to do with QubesOS version upgrade from 4.2 to 4.3 or with debian upgrade from 12 to 13. The issue is actually with Proton VPN version 4.14. The issue was not there in 4.13
I can’t repor the bug on their github forum because when I choose to report a bug they redirect me to Proton VPN support page on their website.
I used “dnf downgrade proton-vpn-gtk-app” until I got back to noarch 4.13.0-1.fc43, and the systray is working again. Which demonstrates the issue is with ProtonVPN 4.14 not with Qubes 4.3, Fedora 43, or Debian 13.