-
Notifications
You must be signed in to change notification settings - Fork 28
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 interface #10
Comments
Hi @GarethDownes , Sorry to hear something is not working well for you. Let's try to get it going. Cheers, |
Hi @tiktaalik-dev, Thanks for speedy reply. Currently running Ubuntu 20.04.01. I reinstalled all the modules listed in README and checked for dependencies issues. Log file doesn't give much detail/errors. Thanks again |
Hi Gareth, OK, we got that out of the way. Next step: By any chance are you using Gnome?... |
Hi @tiktaalik-dev, Yes indeed, I'm using Gnome. |
Hi Gareth, Oh I see, that explains it all. It turns out that your log shows that the program is actually running but you can't see the main window due to a know issue with Gnome. The thing is that Gnome developers in their almighty wisdom decided that they didn't like "Status Icons" in spite of them being a common feature for every other Desktop Interface, and instead of accommodating a feature that a vast number of programs actually use (because it's mainstream) in a way that Gnome internally would translate that feature into something that suit the stylistic lines of their new design... They simply dropped it. No replacement. Nothing. https://extensions.gnome.org/extension/615/appindicator-support/ Hope that helps somehow in the meantime! Cheers, |
Hi, Regards, Edit: The gnome logs are filling a lot
by using the command |
hello, i have also problem that it is not opening. |
Hi @tiktaalik-dev,
Super silly issue to have, but I can't work it out.
Output from terminal:-
" Using config file 'standard.conf'.
<_io.TextIOWrapper name='/home/gareth/blueproximity.log' mode='a' encoding='UTF-8'>"
Thanks in advance
The text was updated successfully, but these errors were encountered: