-
Notifications
You must be signed in to change notification settings - Fork 58
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
Failed to correctly detect operating system. #68
Comments
That's the "warning" message. Maybe there's more and it was cut off. Do you have a [main] section In the file... ~/.config/kazam/kazam.conf Try removing/renaming that file and starting it again. |
WARNING Kazam - Failed to correctly detect operating system. |
this is the correct error message |
how do i add main |
In the file ~/.config/kazam/kazam.conf There should be a [main] section If you remove that file, it'll be recreated automatically. |
good to close, purging
seems to work |
WARNING Kazam - Failed to correctly detect operating system.
Traceback (most recent call last):
File "/usr/bin/kazam", line 148, in
from kazam.app import KazamApp
File "/usr/lib/python3/dist-packages/kazam/app.py", line 35, in
from kazam.backend.prefs import *
File "/usr/lib/python3/dist-packages/kazam/backend/prefs.py", line 478, in
prefs = Prefs()
File "/usr/lib/python3/dist-packages/kazam/backend/prefs.py", line 121, in init
self.read_config()
File "/usr/lib/python3/dist-packages/kazam/backend/prefs.py", line 199, in read_config
self.audio_source = int(self.config.get("main", "audio_source"))
File "/usr/lib/python3/dist-packages/kazam/backend/config.py", line 106, in get
self.set(section, key, default)
File "/usr/lib/python3/dist-packages/kazam/backend/config.py", line 125, in set
super().set(section, option, str(value))
File "/usr/lib/python3.9/configparser.py", line 1204, in set
super().set(section, option, value)
File "/usr/lib/python3.9/configparser.py", line 902, in set
raise NoSectionError(section) from None
configparser.NoSectionError: No section: 'mai
The text was updated successfully, but these errors were encountered: