-
-
Notifications
You must be signed in to change notification settings - Fork 925
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
No tray icon on Ubuntu 18.04 #461
Comments
Howdy, This happens because VeraCrypt only has a tray icon, and GNOME has dropped support for that (as well as appindicators, but since you use Ubuntu you get those back by default.) If you want the tray icon back, you have several options:
Hope one of these helps! ~Unit 193 |
This also happens on Ubuntu 20.10. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue has been automatically closed because it has not had recent activity. This probably means that it is not reproducible or it has been fixed in a newer version. If it’s an enhancement and hasn’t been taken on for so long, then it seems no one has the time to implement this. Please reopen if you still encounter this issue with the latest stable version. You can also contribute directly by providing a pull request. Thank you! |
Unlike the Windows version, VeraCrypt does not appear on tray not even when closed (as opposite to "exited").
![linux-already-running](https://user-images.githubusercontent.com/32184973/58860385-e9b11a80-86a3-11e9-9888-6ed004b0a93f.png)
To do any action (mounting/unmounting/etc.), I now have to rerun the program which gives me this annoying warning: "VeraCrypt is already running."
This must be an error because there is no problem with other apps like Telegram as you can see:
![linux-tray](https://user-images.githubusercontent.com/32184973/58860406-f2a1ec00-86a3-11e9-80a3-c00a974d2df0.png)
VeraCrypt version: 1.23
OS: Ubuntu 18.04 x64
Installed/Activated extensions:
Related/same(?) issue: #211
The text was updated successfully, but these errors were encountered: