We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
GTG simply wouldn't start after I closed it.
this is the log message:
\**Context:** Activation ```python-traceback None``` **Software versions:** * Getting Things GNOME! v0.6 * CPython 3.9.9 (main, Nov 10 2011, 15:00:00) [GCC 11.2.0] * GTK 3.24.33, GLib 2.70.5 * PyGLib 3.42.0, PyGObject 3.42.0 * Linux-5.4.0-107-generic-x86_64-with-glibc2.33
1 - I tried deleting the gtg_data.xml file to bring back the default file and it wouldn't run either.
2 - So i did the same to the gtg.config file. And it worked, however as expected it reseted all configs, including plugins.
3 - I tried to debug the gtg.config file by testing each field... turns out deleting hamster from enabled plugins at gtg.config solves the issue
Probably some deeper compatibility problems there since the plugin wouldn't work anyway. Hope I saved someone some time and tears ;)
The text was updated successfully, but these errors were encountered:
Also see #770 (comment) (same solution)
Sorry, something went wrong.
Ops total duplicate, hanks for pointing that out! It seems though I can't delete the issue just close it.
No branches or pull requests
GTG simply wouldn't start after I closed it.
this is the log message:
1 - I tried deleting the gtg_data.xml file to bring back the default file and it wouldn't run either.
2 - So i did the same to the gtg.config file. And it worked, however as expected it reseted all configs, including plugins.
3 - I tried to debug the gtg.config file by testing each field... turns out deleting hamster from enabled plugins at gtg.config solves the issue
Probably some deeper compatibility problems there since the plugin wouldn't work anyway. Hope I saved someone some time and tears ;)
The text was updated successfully, but these errors were encountered: