Backup crashed during folder selection. Backup was failing to execute because could not get write permission

Bug #1877700 reported by ernestrayburn@hotmail.com
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ubuntu
Invalid
Undecided
Unassigned

Bug Description

Backup would not execute because it could not get access permission to drive and folder automatically on its own. Running Backup manually was not a problem. Decided to re-select folder for backup destination and program hung.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubuntu-release-upgrader-core 1:20.04.18
ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
Uname: Linux 5.4.0-29-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CrashDB: ubuntu
CurrentDesktop: ubuntu:GNOME
Date: Sat May 9 09:07:02 2020
InstallationDate: Installed on 2020-04-25 (13 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
Symptom: release-upgrade
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
ernestrayburn@hotmail.com (ernestrayburn) wrote :
Revision history for this message
Chris Guiver (guiverc) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem.

You have stated the issue relates to a backup, not getting permission for a drive, but have tagged `ubuntu-release-upgrader` package (which is the package that will bump your 20.04 release to 22.04 or 20.10). I don't see any evidence of trying to bump your recent install to either 20.10 so it could just be the wrong package was marked.

If the program crashed, you'll likely find a crash report in /var/crash/ which will have the date & time stamp of the crash. You can submit that using
`ubuntu-bug /var/crash/[package-name.crash]`
(no back-quotes, and replace [package-name.crash] with the name of the file)

Please clarify what program you were using for backups (

We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures.

At a minimum, we need:
1. The specific steps or actions you took that caused you to encounter the problem.
2. The behavior you expected.
3. The behavior you actually encountered (in as much detail as possible).
Thanks!

affects: ubuntu-release-upgrader (Ubuntu) → ubuntu
Revision history for this message
Paul White (paulw2u) wrote :

Ernest,

When you say 'Backup' do you mean Deja-Dup?
If not, which backup application?

Is this still an issue now that you may have run the backup
application several times since filing the bug report?

When did the problem occur? When trying to run a scheduled backup?

Marking as "Incomplete" awaiting the requested information.

Changed in ubuntu:
status: New → Incomplete
Revision history for this message
Paul White (paulw2u) wrote :

No reply from reporter after 6 or so weeks so closing.

Changed in ubuntu:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.