1/7/2023 0 Comments I have viber but no viber iconThirdly, 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 Hopefully this gets merged so that people using Viber don't have to scour yet another GitHub issue page and hopefully make Linux less tedious for them to use. It does allow sub-package regexes, but not actual string regexes, because if that were the case I could do -* instead. Hence the need for own-name.įlatpak doesn't allow string regexes. Letting Viber talk to a bus won't work as it's initiating instead of using one. So what's the rationale, why does Viber need an access to an entire session bus?īasically since Viber DOES NOT use the bus, it instead opts to create it's own under the name -$randomNumber-$anotherRandomNumber. Keeping track of background tasks via the tray icons is cool as well.Having the ability to be aware that Viber's running on the system regardless whether the application window is open or not is pretty neat.Not being able to quit Viber is ONE BIG issue.(And the amount of frustration that brings) While this "fix" does introduce holes in the sandbox, namely the entire org.kde.* namespace being exposed, I think it's worth to merge it simply due to the issues that not having an tray icon would cause. ![]() This has been a long running issue #4 and it's been bothering me as well.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |