Bug 2014869 - Timeshift can't be configured and does not launch snapshoting
Summary: Timeshift can't be configured and does not launch snapshoting
Keywords:
Status: CLOSED DUPLICATE of bug 1897979
Alias: None
Product: Fedora
Classification: Fedora
Component: timeshift
Version: 35
Hardware: All
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: srakitnican
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-10-17 14:37 UTC by Tommy Beauclair
Modified: 2021-11-26 22:58 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-11-26 22:58:23 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Tommy Beauclair 2021-10-17 14:37:27 UTC
Description of problem:
When we want to adjust some settings or create a configuration, timeshift says in graphical and in CLI that it can not find partitions (even those who are formatted and with data on it)

Version-Release number of selected component (if applicable): 20.03-4


How reproducible: Always


Steps to Reproduce:
1. Launch Timeshift and enter root password to start the software
2. Do a new configuration or change the actual one
3. Timeshift says it can't find partition and cannot continue, and for existing conf it does not run the snapshoting

Actual results: No snapshoting, configuration cannot be saved


Expected results: Normal running of the conf assistant and snapshot are done


Additional info: The packed version is outdated, upstream is at version 21.09.1 (as seen at https://github.com/teejee2008/Timeshift/releases). Compiling upstream and installing it makes timeshift working normally

Comment 1 ingli 2021-11-03 21:57:13 UTC
I confirm this, and I like to add, that this illfunction does not seem influenced by whether the backup location is mounted or not.

Comment 2 ingli 2021-11-03 21:58:11 UTC
duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1897979

Comment 3 Alessio 2021-11-26 22:58:23 UTC

*** This bug has been marked as a duplicate of bug 1897979 ***


Note You need to log in before you can comment on or make changes to this bug.