Skip to content
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 file is not loaded [linux bug] #133

Closed
sm-alejandro opened this issue Jan 28, 2023 · 3 comments
Closed

Config file is not loaded [linux bug] #133

sm-alejandro opened this issue Jan 28, 2023 · 3 comments

Comments

@sm-alejandro
Copy link

sm-alejandro commented Jan 28, 2023

On linux the config file is not loaded correctly when selected from the file selector window. I don't know yet why, but linux or maybe the file manager nautilus has a problem uploading files to certain programs. In firefox I can't upload images. When I try to load a config file from the GUI, the window does not load any settings and the GUI looks like this:
image
It also displays the following message on the console:
[CONFIG]: Ignoring key sets-separator-control-points: without arguments.

This is not a problem of the software because if I pass the --config argument at startup all the settings are loaded correctly, it is just information for anyone who encounters the same "bug" and looks for help.

Hardware info:

  • OS: LINUX / Ubuntu 22
  • MIDIVisualizer version 7.0
@kosua20
Copy link
Owner

kosua20 commented Jul 30, 2023

Hello, thank you for your feedback and for posting this to help others! I'll still try to investigate if I can reproduce the issue on Ubuntu 22 and Nautilus, to at least detect the problem and warn the user. If you still have one of the config files around, could you share it with me? maybe Nautilus is not expecting something in the file name or the path.

kosua20 added a commit that referenced this issue Jul 30, 2023
This fixes config loading on Ubuntu, where the file picker (or Wayland, or Nautilus?) would change the locale (#133).
@kosua20
Copy link
Owner

kosua20 commented Aug 30, 2023

Hello, this has been fixed in the latest 7.1 release.
The warning in the console is nothing to worry about, config files can contain 'empty' settings if you haven't customized them (for instance the separation control points mentioned above).

@sm-alejandro
Copy link
Author

Thank you very much!!!!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants