Timeshift shows wrong free space on device

[servimo]

Describe the bug

Timeshift shows wrong free space on device in the gtk window.
df shows: 135G
/dev/sdc1 916G 735G 135G 85% /HD.Interno1

timeshift: 194,9G

*In Fedora it shows wrong free space too.

To Reproduce

Expected behavior

Timeshift should display 135G too.

Screenshots

System:

• Linux Distro: Manjaro Linux 23.0.0
• Desktop: Xfce 4.18
• Application Version: Timeshift 22.11.2

[bkmo]

On Arch with btrfs I have 128G available and Timeshift says 138G.

[Prizmagnetic]

Is it including the other partitions? I think that's what mine is doing. When you add up all of them its amount that its off by

$ df -h
Filesystem      Size  Used Avail Use% Mounted on
tmpfs           583M  4.1M  579M   1% /run
/dev/sda5       468G  383G   62G  87% /
tmpfs           2.9G  4.0K  2.9G   1% /dev/shm
tmpfs           5.0M  4.0K  5.0M   1% /run/lock
/dev/sda1       511M  4.0K  511M   1% /boot/efi
tmpfs           583M  116K  583M   1% /run/user/1000

$ sudo timeshift --list
Mounted '/dev/sda5' at '/run/timeshift/298997/backup'
Device : /dev/sda5
Path   : /run/timeshift/298997/backup
Mode   : RSYNC
Status : OK
2 snapshots, 66.0 GB free

[tbertels]

When the partition is detected as btrfs, it should show the unallocated space.

[zhurin]

Is it including the other partitions? I think that's what mine is doing. When you add up all of them its amount that its off by

Not on mine. I only have sda1 and it's still wrong.

/dev/sda1 458G 252G 183G 58% /

Timeshift says 196.3 GB available on /dev/sda1. I wouldn't mind so much if it was under estimating since that's relatively harmless. But assuming more space available than exists is a fast way to fill the drive to the point of boot failure.

[github-actions]

This issue has been automatically marked as stale because it has not had
any activity in over 2 years.

If this issue is still relevant:

• Please test on a current version of this package.
• Add a comment with your findings

If no activity occurs in the next 30 days, this issue will be
automatically closed. Issues can be reopened if needed.

[tbertels]

Still reproduceable with Timeshift 25.12.4.

[Prizmagnetic]

Hmm so I just noticed everyone here has it reporting ~7% higher than it should be. except for OP which is much higher

So I tried running df -H instead (GB instead of GiB) and now they report the same number. I don't think any of us are reproducing the same bug