In order to make the btrfs/snapper functionality more accessible, we are breaking it out from Garuda Assistant into it's own application.
In addition, some changes and new features:
Tabs are no longer hidden behind checkboxes because there is more room for tabs
The window is no longer forcibly centered
The dependency on pacman was removed
BTRFS balance is now run in the background
The application now runs as root since it needs root for almost everything with btrfs and snapper
Support for restoring snapshots with nested subvolumes under them has been added
The much requested feature to restore the snapshot even if the subvolume is mounted has been implemented
Of course, these changes mean we need a new round of testing! Especially those last 2 changes.
If anyone wants to test, btrfs-assistant-git is in both the AUR and chaotic-aur.
One thing I should mention is that if you boot off a snapshot, both Garuda Assistant and BTRFS Assistant are going to ask you to restore the snapshot. This is due to the fact that since this application isn't live yet, the functionality hasn't been removed from Garuda Assistant yet.
As always, thanks for the assistance and feedback!
Nice.
A nice additional feature to add would be to display how much space the snapshots are consuming. From my quick and lazy research recently it's not "hard" to find but if it can be integrated into the gui, that would be an exceptionally nice feature (though would take quite some effort to integrate into gui).
I feel like I looked at that when I first started. I don't think it was hard but it was expensive. If you had a good number of snapshots it took a long time to calculate.
I stated that because there is a chaotic-aur package, but assumed AUR because that's from dragonfire (and you said AUR not chaotic).
From a quick playthrough, assuming that theming and integration into Garuda Welcome will be done post-testing....
Restoration and snapper settings changes all worked for @root & @home
Tried to balance Btrfs even though not needed and that aborted immediately, which I guess it should
Deletion of restore backup subvolumes worked.
Console output (FWIW):
[đź”´] Ă— sudo btrfs-assistant
[sudo] password for peanut:
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
QMetaObject::connectSlotsByName: Connecting slot on_comboBox_btrfsdevice_activated() with the first of the following compatible signals: ("activated(int)", "activated(QString)")
QMetaObject::connectSlotsByName: No matching signal for on_checkBox_show_subvolume_clicked(bool)
QMetaObject::connectSlotsByName: Connecting slot on_comboBox_snapper_configs_activated() with the first of the following compatible signals: ("activated(int)", "activated(QString)")
QMetaObject::connectSlotsByName: Connecting slot on_comboBox_snapper_config_settings_activated() with the first of the following compatible signals: ("activated(int)", "activated(QString)")
QMetaObject::connectSlotsByName: No matching signal for on_checkBox_snapper_advanced_clicked(bool)
I would definitely make that call async if it was to be implemented. However, even async, waiting over a minute for a grid to fully populate seems unacceptable to me in an application like this.
It probably isn’t failing, it has been moved to the background. That was what we were discussing above. I need to add a notification about what is happening there.
Since it is now running as root, it is getting root’s theming.
I'm uncertain that this is related to testing this, but mentioning in case and maybe others can check there systems...
I was looking at my snapshots last night and noticed that I had a lot more than I should have, the cleanup didn't seem like it had run since around the time I was testing this btrfs assistant.
All the services were as they should be and cleanup said it had run and was due to run but
I decided I had it set to have too many anyway and wondered if tweaking/saving the setting would resolve and ... cleanup has now cleared previous snapshots to where it should have done.
Whether this was a cross-over issue or it was fiddling around to test the application, I dunno, maybe other's can check and verify or counter my findings.
I wonder if before changing the setting, cleanup was disabled in the config. If it is disabled in the config, even if the timer is running it won't do anything.
Either way, I don't think that would be related to this application because it doesn't touch those settings on install. Only if you go into the screen and make changes.
Mine had hourlys going back 3ish days, but system hadn't missed a cleanup timer.
I dunno, it's fine since I resaved settings. I only mentioned here because "testing" and "thought" he was having similar issue.
Apologies for the (hopefully) false alarm and thanks for the help.
Ok so I just installed this to check it out, and I really like that it is its own application now and such, but I noticed unlike Garuda assistant it does not ask for a password. This seems like a pretty powerful tool to not need to ask for root privilege and instead just have it automatically.
