Michael Büker
Michael Büker
> a) try to make the crash reproducible with a minimal reproducible (code) example (**MRE**) Hmm, that's tricky. From what I've seen, it' not 100% reproducable, but it happens _almost_...
Digging around the discussions in https://bugzilla.redhat.com/show_bug.cgi?id=1844781 and https://forum.manjaro.org/t/python-crash-when-exiting-back-in-time/102856/11, I see three hints on a possible root of the problem: 1) https://www.riverbankcomputing.com/static/Docs/PyQt5/gotchas.html#crashes-on-exit – quote: > "When the Python interpreter leaves a...
Adding https://github.com/bit-team/backintime/labels/Python-Specific, because only Python 3.9 and 3.10 seem affected right now.
Here's another piece to the puzzle – but be careful, there's a good chance it will melt your brain: https://github.com/bit-team/backintime/commit/1d63ced1d0025dc4ca18f595bf3e0c8b18b555d0#commitcomment-21596448
I agree that this is out of scope, but we may keep the Issue as a reminder.
To everyone involved: Would you say this Issue can be closed?
Agreed, we'll give this Issue a 4-week timeout.
Hi Steffen, did you ever find further clues (in logs, for example) or a solution to this problem?
I'm not sure this is possible in the way that the reporter envisioned it. It would at least require an implementation of #406. Or did I misunderstand? In any case,...
Smells like the crontab might not be doing what it should. Could you post the output of `crontab -l` for your user? Thanks for your patience and cooperation in debugging,...