Trouble after switching distros (Mint 22.2 -> LMDE 7)
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- linux
- Domain
- documentation, operating-systems
Research direction
The issue names no files, tests, or entry points. Start by reviewing the documented distro-switch and backup-drive scenario, then inspect the relevant documentation or code warning surfaces mentioned in the report. Done means producing a confirmed, actionable warning or documenting why the behavior cannot be addressed.
Written by the indexing model from the issue text.
Description
I recently switched from Mint 22.2 to LMDE 7. I knew that a best practice for Timeshift would be to use a new backup drive, but the type of trouble I had might be worth a warning in the documentation or the code itself.
First off, I knew this was a different distro and package base, so I was not surprised that Timeshift made an entirely new copy of everything. The Timeshift progress bar indicated this went as expected. The problems happened after the backup appeared to be finished:
- The backup hard drive would not unmount.
- Any file operation on the backup hard drive took an extremely long time.
- Application Menu button for shutdown would only log off.
- Login screen buttons for shutdown/restart were non-existent.
- Attempting
sudo shutdownresulted in an error message. - Invoking
systemctlwas the only way to shutdown or restart the computer. - Reformatting the backup hard drive on the same device did not resolve any of these issues. However, reformatting it on a different device did.
My own problem appears resolved; I have not had further trouble with Timeshift on LMDE. I did not lose any current user data, however, I lost all previous backups.
I realize I could have avoided this with wiser decisions. However, if someone without troubleshooting skills or a second machine attempts this, they might conclude Timeshift damaged their backup drive. Possibly worth adding a warning either in the documentation or the code.
I hope this is helpful. Thanks!
- Dominant language
- Vala
- Stars
- 4.3k
- Forks
- 158
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from linuxmint/timeshift
-
Difficulty 1/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 1/5 Under an hour Newbie friendliness 68/100
-
timeshift --create hangs indefinitely at exit in infinite read() = 0 loop on aarch64 (Fedora 44 / Kernel 7.2.x)Possibly taken @ygerlach claimed this today. Open
Difficulty 4/5 3-5 days Newbie friendliness 28/100
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
All issues in linuxmint/timeshift
Similar issues
-
sync-en
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
sync-en
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 4 days
-
Перевод устарел
Difficulty 1/5 Under an hour Newbie friendliness 85/100
-
Incorrect Link in README.mdPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 1/5 Under an hour Newbie friendliness 95/100
flameshot-org/flameshot#4996 ·
Maintainers usually reply within 2 days
-
docs(evals): note CLAUDE_CODE_PRINT_BG_WAIT_CEILING_MS for headless eval runs that use workflowsOpengood first issue needs-triage priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
melodic-software/claude-code-plugins#7022 · 1 comment ·
Maintainers usually reply within 1 day