-
Notifications
You must be signed in to change notification settings - Fork 61
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Birdtray does not start #357
Comments
Can confirm this problem on Fedora 32 Gnome Wayland. Installed via flatpak. |
@Sirtz I'm using the flatpak on Fedora 31 Gnome Wayland, and a fix is to run:
and then try running Birdtray. |
@Mikail0 I get the same problem on Debian 9 (Stretch) / birdtray 1.8.0 / Cinnamon 3.2.7 I have checked out the latest source 3541386
|
…ailable. Per the QT documentation for QT4 & 5: https://doc.qt.io/qt-5/qsystemtrayicon.html#isSystemTrayAvailable The system tray icon will be automatically added if the system tray is visible (even if it was not available at launch). Fixes issue gyunaev#357
It seems that birdtray fails to start because it was calling @Mikail0 If you can build from source you might want to test out this commit c75759c |
OS: manjaro Description birdtray crash plasma wayland launch and do not launch as well. To Reproduce
|
Wayland is not supported. |
ok but in this case could you add this info to the "Troubleshooting" section in the README.md.
regards |
Note that you're using an old version; if you build it from source it won't crash, but show/hide won't work. |
OS: Arch
Birdtray version: I can not open the app. I have installed birdtray from the AUR
Thunderbird version:68.7
Birdtray origin: AUR
Qt version: NA
Description
I have installed birdtray on GNOME Wayland, tried to start it, but nothing happened.
After 1-2 minutes, I got an error message, that the status/system bar can not be be controlled by this addon. It also says that a protocol were written in the file /tmp/log.txt, but there is no with that name.
To Reproduce
Edit:
Tried to start it on GNOME Xorg. Still the same issue.
The text was updated successfully, but these errors were encountered: