-
Notifications
You must be signed in to change notification settings - Fork 164
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
Version 0.5 fails to parse tasks file (and refuses to launch) when a saved search's name and query matches exactly one of the tags #629
Comments
Did you go from 0.3 to 0.4 and then 0.5? It's a versioning thing, since we have a new file format. I didn't expect many people to still have the 0.3 style filenames :) Try this:
Try running gtg again |
Hi @diegogangl, thank you for your answer, I did what you mentioned, and started
I'm totally new to Flatpak, I tried the following commands:
|
That message is harmless since GTG isn't storing any passwords ATM. Is the window not coming up when you run the flatpak? |
Unfortunately not. But the message in the Terminal is a bit more verbose today:
No window appears but a process is running in the background:
|
Kill the running process. Make a backup of Note that some other error could occur if you delete the wrong one, since the tasks uses the id ( (You can ignore the |
Fixed! I had to delete a search query that was similar to a tag name. More details: The file
The problem occurs only when the What I did precisely:
Thanks a lot @Neui for giving me the right direction! I let this ticket opened, as something may need to be fixed. Feel free to close if it's a corner case |
Aaah, so we may finally have found what was causing these issues? Might be when a saved search matches exactly the name of a tag (a bit similar maybe to what was found in #616 (comment) regarding dots/periods in tag names). Maybe @diegogangl can figure a way to detect and correct that... |
I experience similar behaviour in 0.5 when editing a tag name. I had a tag 'Open', which I changed to 'open' (i.e. changed the first letter to lower case). After closing GTG and running again it produced the errors seen in the comment above. Looking at |
Similar problem happened to me as well, and since then GTG won't start. |
Retitling (for clarity) + retagging + targetting this issue. High priority because it can prevent launch and is quite confusing when it happens, not "critical" because at least there is a workaround and the file format can be somewhat easily corrected by users. I suspect this will be one of the things Diego hopes to address as part of #553 so we'll need to keep an eye on this for whenever that lands. |
I have experience the same but deleting the saved search and same label tag did not work for me. It still shows the same error when launching in flatpak. I have fixed this by simply restoring backup. In which, it is weird that the backup still contains the similar tag with upper case problem, and save search, it launch |
This got me when I had similar named tags with capitalization differences and I changed one to match the other tag. I also added an icon to one or both of the tags. |
Hello there,
I was using GTG 0.4 with Flatpak and everything was going smoothly.
Today the new version (0.5) is running after an automatic update. Unfortunately, only the test tasks are showing now:
I think there's no data loss though, here is the treeview of
~/.var/app/org.gnome.GTG
Any hint, or additional way to report relevant infos?
The text was updated successfully, but these errors were encountered: