Closed major-mayer closed 1 month ago
As far as I can tell this dialog means that there is newer version of Errands installed than you are currently running. This should be resolved by hard closing the application using system monitor or any alternative method (just closing the window won't work since the app is still running in the background).
Regarding the crash, it is hard to tell what is the cause. The logs don't show much and I'm not able to reproduce on the latest build. I was able to reproduce similar symptoms only by purposefully setting the command that should restart the app (application.py:51) to something that does not exit (eg. the yes
command) and runs forever.
I disabled update message here 9d5943a479e1dd6347959eb0c597b48dec35a8b7 for now. About sync error, I can't replicate it, maybe python-caldav bug. I wanted to just write ical data directly instead of relying on caldav library for types conversion anyway, so maybe it will fix it.
Weird... So I checked if the message appears again when i forcefully close the app using the tasks manager and it's still the case. However, I noticed that when i click the restart button, it actually spawns a second instance of Errands, but still the original application freezes and the new instance never appears. Maybe the original application doesn't really crash (I also can't find any core dumps or so) but just exists after a while when this timeout, mentioned in the logs, is reached? Could it be that the command to launch another instance of the app needs to be modified so that the new process gets detached?
And thanks for the information about the caldav error. Let me know when you made the change, so I can test it.
Edit: Yeah, it really seems like the use of os.system()
could cause issues when restarting the app, since it waits on some platforms for the return value: https://stackoverflow.com/questions/8246520/does-pythons-os-system-wait-for-an-end-of-the-process
I'll change it to use subprocess module tomorrow and make new release. Should fix the issue.
Sounds great. Thanks for the fast response.
Hello. This error is reproduced on ALT Regular Sisyphus (ALT Linux) DE: GNOME 46.1
I've pushed new update to flathub.
Omg. This issue is so frustrating. And sadly, it occurs in every ~1 minute. :cry: In the last 5-10 days there are a lot of error, before that it was an awesome app...
Another issue is that, I had a test task what has a due date. After a while I checked it out, after I deleted it, but it notifies me absolute randomly since then. (Today, I emptied the trash bin, so I hope...)
Sorry for the attitude, I really loved this app until now.
I've pushed new update to flathub.
All right, I will wait until the update is also on the AUR and let you know if it fixed my issue then.
@7system7 You should probably open a new issue so it can get resolved.
Another issue is that, I had a test task what has a due date. After a while I checked it out, after I deleted it, but it notifies me absolute randomly since then. (Today, I emptied the trash bin, so I hope...)
@32GBRat it's already opened: #276. And I fixed it in 344ac1763a95b0c1edeb0c2e43257960328cb9a3. Will be in 46.1.1
Sorry, missed that. Thanks for notifying me.
When I start Errands and capture the logs in the console, I see a couple of synchronization errors:
I am syncing my tasks to a Nextcloud instance.
This wouldn't bother me much, since everything else seems to be working, but for some reason this dialog always appears after a few minutes:
The app freezes and I can't click on the restart button.
Eventually it will crash anyway.
If there's anything you could need for debugging, feel free to tell me.