backintime
backintime copied to clipboard
[Mint, MX] New system tray icons appear with every snapshot, many icons accumulate
Icon appears in system tray when a backup job is running, does NOT disappear when the job is done. Stuck on "Finalizing".
As a result, I often get several such icons lined up side by side.
Backintime 1.1.12 running on Linux Mint 18.1
The same happens on MX Linux 19
I can not reproduce this with current Debian 10 and XFCE.
Which desktop enviroments do you use?
This happens on MX Linux 19 XFCE and also happened on Linux Mint 18 Cinnamon
Thanks for the report, @dave62020. This Issue is probably a duplicate of #1002. Does the problem still happen?
Yes this is still happening
Yes this is still happening
Thanks for your feedback! We're in the middle of sorting old tickets, and we'll hopefully get to this in due time.
This must be a bug in qtsystrayicon.py or the "busy" indicator file:
https://github.com/bit-team/backintime/blob/88d19d42e9128f60b8952a64ed1fff23bd28108f/qt/qtsystrayicon.py#L145-L149
Could you please show me the existing files in ~/.local/share/backintime when this error occurs?
ls -l ~/.local/share/backintime/
I would expect to see a worker*.lock file even though the backup seems to have finished.
If true I need to know more about the configuration (profile)...
@DonEdwards @dave62020
Could you please
- install the most recent release of BiT and check if the problem still occurs
- show me the output of
backintime --diagnostics - execute two BiT backup jobs
- show me the output of
journalctl -since "10 minutes ago" | grep -i backintime(adjust the "minutes" part to catch the full the log of both backup job executions and anonymize the output by replacing sensitive strings like your user name before uploading the log here
Dear @DonEdwards @dave62020 , we would like to work on that issue. Can you please give us some feedback and the required information aryoda was asking for.
Apologies for lack of reply. Since switching to MX Linux some time ago I have no longer had any issues.
Thanks for reporting back :) Closing the issue, as there is nobody left to reproduce. Anyone still seeing this: feel free to re-open.