-
Notifications
You must be signed in to change notification settings - Fork 22
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
~/.config/siglo.ini was not created during build #81
Comments
weird, i will test when i get the time |
Hm, I got this too just now on a new Pop_OS! 21.04 desktop. I ran the build steps (got an unrelated error) so decided to install the flatpak and hit this too:
|
Yeah, this error doesn't show up if Siglo has previously created the file before being updated. $ rm ~/.var/app/com.github.alexr4535.siglo/config/siglo.ini
$ flatpak run com.github.alexr4535.siglo
Traceback (most recent call last):
File "/app/bin/siglo", line 41, in <module>
main()
File "/app/bin/siglo", line 24, in main
d = daemon.daemon()
File "/app/share/siglo/siglo/daemon.py", line 13, in __init__
self.manager = InfiniTimeManager()
File "/app/share/siglo/siglo/bluetooth.py", line 62, in __init__
if not self.conf.get_property("paired"):
File "/app/share/siglo/siglo/config.py", line 43, in get_property
prop = config["settings"][key]
File "/usr/lib/python3.8/configparser.py", line 960, in __getitem__
raise KeyError(key)
KeyError: 'settings' |
Had the same happen when installing from flathub on Fedora 34. creating siglo.ini text file in ~/.var/app/com.github.alexr4535.siglo/config/ with the following contents did the trick though.
|
Same problem here installing from flathub on Linux Mint 20.1. |
Same problem (freshly) installing from flathub on Fedora 34. |
97b4ca8 should fix it |
After building the project from source on my PinePhone running Mobian I received the following error when running:
I eventually figured out the error was because it was looking for ~/.config/siglo.ini that was not created. I created the .ini file with the default values below, which fixed the issue.
I am not sure if this was something I did wrong during the build or if it is a recent bug in the project.
The text was updated successfully, but these errors were encountered: