-
Notifications
You must be signed in to change notification settings - Fork 283
incompatibility with latest rsync 3.2.4 #891
Comments
I haven't encountered any issues so far running |
Got the same issue, there is barely anything besides "E: rsync returned an error", even with --debug and --verbose flags, as mentioned in the archlinux forum post. Downgrading rsync works for now. And timeshift deletes the fill rsync-log along with the folder once it finishes. Any idea how to retain that? |
Thanks @clusterx, I was struggling finding a solution. Downgrading rsync indeed made Timeshift work again. |
Woah, I tried to do so many things and wondered why it didn't work.. |
Downgrading |
Well someone needs to figure out why it's incompatible with the latest rsync |
Timeshift GUI didn't work, but it worked on terminal with |
For me, the GUI works and creates a snapshot folder, but it is not listed. The manual snapshots are missing the |
I also experienced it a few days ago. Timeshift suddenly creates a snapshot every hour. But I see in timeshift GUI No snapshot list as usual. Checking with the "systemctl status cronie" command shows that it failed to create a new snapshot. Finally I tried uninstalling timeshift. The intention was to reclaim free space in the /run/timeshift/ folder, I tried the command sudo rm -rf /run/timeshift/, but it showed an error device is busy and my linux couldn't be used. I finally immediately reinstalled my linux |
Why don't you try reporting the bug here https://github.com/WayneD/rsync/issues?q=is%3Aissue |
@Reno-Sifana this version of rsync works fine on it's own, but not with Timeshift |
Okay. I understand what you're saying. |
Has anyone actually tried rebuilding the package against the latest |
@jonathonf yes. Didn't fix it |
the new rsync version was released due to security critical vulnerabilities so downgrading is not a permanent solution! Rsync version 3.2.4 has been released. Another typical release with both bug fixes and some enhancements. It also contains a security fix for the bundled zlib 1.2.8, which may or may not be used in your particular build configuration. |
My downgraded rsync does work with the zlib 1.2.12. |
basically means, it's not compatible with the official rsysnc version |
20 days without an reaction. What's about borg backup? It's more used than timeshift and well maintained. |
Hmm. I'm curious, Why in some Linux distributions Timeshift is pre-installed. For example in Linux Mint. |
It's an old decision in the past. Also the newest rsync version in ubuntu is They will throw Timeshift away after they update rsync. |
Same bug here: Manjaro stable 21.2.6, rsync 3.2.4-1, Timeshift 21.09.1-3. This issue should be addressed with high priority, since many users, and especially newbies, have learned and been trained to use Timeshift for safe backups. |
I was thinking the same. Is it borg as easy to use as Timeshift? |
In my opinion yes |
Thank you!!! Gonna check it out. |
I'd argue that the two tools were build for completely different purposes: I use Timeshift to try out new settings, software or configs and if it does not work or something breaks I can easily go back to a working system version. On the other hand I'd use something like Borg to backup important files in case my HDD breaks. From the Timeshift description: |
I see. I liked Timeshift a lot for the two weeks it worked for me, but since it not working properly for now I gonna check out alternatives. |
Timeshift does snapshots and also backups the user. The files are in the backups and the backups are either btrfs or hardlink snapshots via rsync. Borg backup also backup files and "snapshot" them like Timeshift, but doesn't depend on rsync. |
Hi, same problem here, on both computers with Manjaro. Downgrade rsync solution is not nice. |
Yes, it isn't. Check out Borg Backup, it seems a good alternative. |
Thank you for the advice. But I'm not really sure if Borg Backup is really alternative. I just want to "save" my system and when something goes wrong to easily restore it. Well, I think that I'll wait some time if it'll be solved. |
PR submitted. |
@ratcashdev Is it really that simple? No wonder I wasn't affected as I'm already using UTF-8. I've implemented your PR with 21.09.1-4 in the Manjaro community repo and the AUR. |
It is possible to have timeshift version in flatpack because then theoretically we could still keep obsolete versions to run timeshift and it would not be bad because dependencies would not affect the system and they would be in a container? |
Package updated on my laptop and working nicely. Thanks for this quick repo update on Manjaro (my favorite OS)! Much obliged! |
thank you, it works fine now 👍 |
@clusterx the PR is not merged. So the issue is still existing for everyone without this AUR package but with rsync 3.2.4. |
A workaround could be run |
teejee2008/timeshift#904 Based on the changelog of rsync 3.2.4 - https://download.samba.org/pub/rsync/NEWS#3.2.4 A long-standing bug was preventing rsync from figuring out the current locale's decimal point character, which made rsync always output numbers using the "C" locale. Since this is now fixed in 3.2.4, a script that parses rsync's decimal numbers (e.g. from the verbose footer) may want to setup the environment in a way that the output continues to be in the C locale. For instance, one of the following should work fine: Fixes teejee2008/timeshift#891
save_bash_script_temp() is a common function that is used by all functions that execute Rsync. Set LC_ALL=C.UTF-8 for all scripts.
Hello! Same issue on Fedora 36. Downgrade and versionlocking solved the issue for now. |
Yes, same issue with Fedora 36. Workaround as described above fixes the issue for now:
|
Fedora hasn't moved to the maintained fork? |
Seems like Fedora/RedHat has not switched yet, yes 21.09.x is their last version. |
Details:
https://bbs.archlinux.org/viewtopic.php?pid=2032506#p2032506
temporary solution - downgrade rsync to version 3.2.3-4
pacman -U https://archive.archlinux.org/packages/r/rsync/rsync-3.2.3-4-x86_64.pkg.tar.zst
The text was updated successfully, but these errors were encountered: