Closed Aditeya closed 2 years ago
did you reboot after the update as specified in the release notes?
if you wish to reset the config, please just delete it, keyboard-center should generate a new file.
EDIT: thanks for the report, invalid config file is certainly something that I need to make more robust, this error by itself is a bug
I believe I ran keyboard-center once after rebooting. I was only aware of rebooting after that when i checked release notes.
I also deleted the .config/keyboard-center
directory and rebooted, but it gives this error despite the file being present:
terminal output:
[aditeya@nemo ~]$ keyboard-center
[root] INFO: 27.06.2022 09:34:43 AM ------------ starting -------------
[Configparser] DEBUG: 27.06.2022 09:34:43 am Config file location: /home/aditeya/.config/keyboard-center/settings.yml
[Configparser] INFO: 27.06.2022 09:34:43 am copying template config file
[Configparser] DEBUG: 27.06.2022 09:34:43 am source: /usr/lib/keyboard-center/config/testconfig.yaml.example
[Configparser] DEBUG: 27.06.2022 09:34:43 am destinatin: /home/aditeya/.config/keyboard-center/settings.yml
[root] ERROR: 27.06.2022 09:35:35 am [Errno 2] No such file or directory: '/usr/lib/keyboard-center/config/testconfig.yaml.example'
Traceback (most recent call last):
File "/usr/lib/keyboard-center/main.py", line 55, in <module>
window = MainWindow(app, devmode)
File "/usr/lib/keyboard-center/mainUi.py", line 139, in __init__
self.configparser = self.getConfiguration()
File "/usr/lib/keyboard-center/mainUi.py", line 211, in getConfiguration
configparser = Configparser(TEMPLATE_LOCATION, silent=False)
File "/usr/lib/keyboard-center/lib/configparser.py", line 41, in __init__
self._getConfigLocation(locConfTemplate)
File "/usr/lib/keyboard-center/lib/configparser.py", line 63, in _getConfigLocation
self._copyConfig(confTemplate, confLoc)
File "/usr/lib/keyboard-center/lib/configparser.py", line 248, in _copyConfig
with open(src, "r") as s:
FileNotFoundError: [Errno 2] No such file or directory: '/usr/lib/keyboard-center/config/testconfig.yaml.example'
Traceback (most recent call last):
File "/usr/lib/keyboard-center/main.py", line 55, in <module>
window = MainWindow(app, devmode)
File "/usr/lib/keyboard-center/mainUi.py", line 139, in __init__
self.configparser = self.getConfiguration()
File "/usr/lib/keyboard-center/mainUi.py", line 211, in getConfiguration
configparser = Configparser(TEMPLATE_LOCATION, silent=False)
File "/usr/lib/keyboard-center/lib/configparser.py", line 41, in __init__
self._getConfigLocation(locConfTemplate)
File "/usr/lib/keyboard-center/lib/configparser.py", line 63, in _getConfigLocation
self._copyConfig(confTemplate, confLoc)
File "/usr/lib/keyboard-center/lib/configparser.py", line 248, in _copyConfig
with open(src, "r") as s:
FileNotFoundError: [Errno 2] No such file or directory: '/usr/lib/keyboard-center/config/testconfig.yaml.example'
I Installed this through the AUR (keyboard-center)
ok I see the issue, sorry about that, but I messed up on two places at the same time with this release
I will push a fix asap
I pushed an update, which should fix both of the issues.
Please let me know if that fixes it for you.
Yup its working now, but upon startup theres an invisible/transparend window with a border:
Its barely visible, but you can see the border. Clicking unhide & then hide fixes the issue. Another one is after i hide and unhide and change workspaces, (like say to 1 where the browser is) it overlays the entire space.
I'm not sure if this is a quirk with bspwm or if its an issue with the program tho
thanks for the feedback
That is very weird. Does changing the setting "minimize on start" have any influence on that?
I think one workaround would be to minimize the application instead hiding to tray. It seems like hiding the window does cause issues for you.
I sadly cannot reproduce that, I am just using QT's window.hide()
function ._.
Yes, disabling minimize on start works well. However it keeps the window open on start up. Would it be possible to add a CLI option or flag, so it just runs in the background. That way I can just add it to a startup script, but I can start up the GUI to configure if need be. Sort of like how the systemd background process worked.
Would it be possible to add a CLI option or flag, so it just runs in the background.
Adding CLI option is of course possible, but I sadly do not know, what I should do with the window.
The reason why I moved away from the systemd process, is because otherwise the "run command" feature does not work, since processes started from systemd do not have access to the display without some weird workarounds, which I do not want to rely on.
I pushed yet another update which disables a KDE bug workaround for QT >= 5.15. I think that might have been the cause of your window shadow glitch.
Let me know if that changes anything for the better for you.
Yup! It works as expected, though I'd like to hide the tray icon since I don't really change my options that much, but it works!
The problem with the tray icon is sadly not easily solvable.
I need it, in order to make the command feature work properly.
If I give the user the option to hide the tray icon as well, the user will not be able to reactivate the window anymore. If the user just opens the application up again, it will be a new instance with a new process, completely independent from the first.
Sadly on Wayland there is no way for me to maximize a window of a different process unless I start implementing Unix or network sockets for IPC, which is quite ugly.
If you do not care about the command feature, feel free to revert back to a 0.1.x version, the PKGBUILD is in the AUR, you can pull it and just install it with makepkg -si
Ah I see, I guess I'm okay with this current implementation then. Thank you!
If you have an idea how to solve this, feel free to let me know, I am open to suggestions and I fully understand if you find the icon in the tray annoying.
I will look into implementing a global hotkey for reactivation, I think that could be a potential solution for power users.
Since the original issue is solved, I will close this issue.
I'm was trying to start keyboard-center but it wouldn't start up and would show this error:
Running it in the terminal gives this error:
This error showed up after I tried resetting the config. I did the reset because the application wasn't working and if I try to start it, a transparent window just opens.
EDIT: forgot to mention, I updated it yesterday