Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upDo no restore (some of) the Dom0 home dir on backup restore #1106
Comments
rootkovska
added
bug
C: core
C: qubes-manager
P: minor
labels
Aug 6, 2015
rootkovska
added this to the Release 3.0 milestone
Aug 6, 2015
marmarek
modified the milestones:
Release 3.1,
Release 3.0
Sep 2, 2015
rootkovska
added
P: major
and removed
P: minor
labels
Jan 15, 2016
marmarek
modified the milestones:
Release 3.1,
Release 3.1 updates
Feb 8, 2016
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
marmarek
Feb 26, 2016
Member
One problem with excluding those directories completely - it will also exclude user-created menu entries. For example I have additional entries for DispVMs (other browsers mostly). Some people create entries for applications without proper desktop file, etc.
Maybe it should be some smart exclude to still include user-created entries? Or simply optional feature (enabled by default) to exclude those entries during restore (but keep then in the backup). Then if user want to restore any custom entries, he/she would also need to possibly delete unwanted ones manually (as you've done).
|
One problem with excluding those directories completely - it will also exclude user-created menu entries. For example I have additional entries for DispVMs (other browsers mostly). Some people create entries for applications without proper |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
rootkovska
Feb 26, 2016
Member
Given how the appmenu restore process has always left me with broken appmenus, I would consider this a big advantage, actually. Seriously.
|
Given how the appmenu restore process has always left me with broken appmenus, I would consider this a big advantage, actually. Seriously. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
rootkovska
Jun 27, 2016
Member
I vote for just excluding the .local/share/{applications,desktop-directories} by default. Given that majority of users would not make custom menu entries, this seems like a reasonable decision, to make sure that the majority of the users would not get screwed appmenus after restore.
|
I vote for just excluding the .local/share/{applications,desktop-directories} by default. Given that majority of users would not make custom menu entries, this seems like a reasonable decision, to make sure that the majority of the users would not get screwed appmenus after restore. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
|
Related: #2271 |
andrewdavidwong
modified the milestones:
Release 3.1 updates,
Release 3.2 updates
May 31, 2017
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
|
Since #2271 is implemented, this is fixed too. |
rootkovska commentedAug 6, 2015
When the user wants to restore only a subset of his or her VMs, but decides to restore also the Dom0 home dir (the default option suggested by the Qubes Manager and qvm-backup-restore), then this will also bring
~/.local/share/{applications,desktop-directories}content, which itself contains all the appmenus the user had while making the backup. This will result in creation of extra appmenus, not backed up by real AppVMs. Very annoying to remove them manually later on, which should be done using: