Wrong location for timeshift backup

[MagnusA]

According to the FAQ, location for the backup is /timeshift on the root of the selected device.
But when binding folders in /etc/fstab, the backup locates to the last line of the binded folders
Excerpts from my /etc/fstab (edited for anomity)
Root device:
UUID=xxxxx-xxxx-xxxx-xxxxx-xxxxxx/ ext4 errors=remount-ro 0 1
....
Binded folders:
/var/log/a /var/www/a/log none bind,nobootwait 0 0
/var/log/b /var/www/b/log none bind,nobootwait 0 0
/var/log/c /var/www/c/log none bind,nobootwait 0 0
...
After mount, /etc/mtab looks like this:
/dev/yyyyy / ext4 rw,relatime,errors=remount-ro,data=ordered 0 0
...
/dev/yyyyy /var/www/a/log ext4 rw,relatime,errors=remount-ro,data=ordered 0 0
/dev/yyyyy /var/www/b/log ext4 rw,relatime,errors=remount-ro,data=ordered 0 0
/dev/yyyyy /var/www/c/log ext4 rw,relatime,errors=remount-ro,data=ordered 0 0
...
where yyyyy is the indentifier for the chosen device
The backup then ends up in
/var/log/c/timeshift
which is inconvenient. These folders are added and deleted automatically by other processes.
It seems like the last line from /etc/mtab containing the device id is chosen to represent the path to the root of the device.
In my opinion, location should be selectable or another method for selecting the location should be used.

[teejee2008]

Will be fixed in next update. Thanks for reporting this.

[Rumptil]

I can't use timeshift because of this bug...

Any workaround ?

[Tibladar]

Still an issue with timeshift 19.08.1