Cannot find UUID when it shouldn't be needed

[Mauro]

This is my situation. I have my main profile that backs up data on a USB device and a scheduled rule to start backup once a day as soon as the device is connected.
Then, I wanted to clone that backup job so that the same data is also copied on a NAS, using a remote SSH connection. To clone the profile, I followed the directions given by Germar on answer to question 244084. Then, I opened BackInTime GUI to change the backup destination of the new profile (obtained by cloning the main one). However, whenever I try to save changes to that new profile, BIT complains that it can't find the UUID for the USB device that is the target of the main profile. It can't because that device is not currently connected... however, why should it bother?
I don't think it should, because I'm editing a profile that has nothing to do with that device. I'm not even setting any schedule by now, so it shouldn't even try to get the UUID to set up scheduling and/or any udev rules.

In any case, the fact that the target device must be connected is annoying even if I were trying to change the main profile. In fact, it happens that you want to change some backup profile setting that has nothing to do with udev rules, so BIT should not force me to have the target device connected because it should not need to know the device UUID in those cases.
In my specific case this is even more annoying because I'm editing a profile that has nothing to do at all with that removable device.

So, is it possible to make BIT configuration dialog try to set up udev rules *only* when scheduling is changed and the new setting requires to set up udev rules or when the backup destination is changed and scheduling/udev rules are yet involed?

If this is not possible, is it possible at least to prevent BIT from requiring USB devices to be connected when you are editing a profile that is not using those devices at all?

[Germar (germar)]

Hi Mauro,

I'll "cache" the uuid so it will not fail anymore.

Regards,
Germar

[Mauro (mauromol)]

Great, thank you! :-)

[Germar (germar)]

Quote from bug #1431305:
> Also note that the fix for bug 1426881 (whose fix version is the same
> as this) seems not to be in this package, or at least it isn't working
> (I still get the "can't find UUID" error if I do not connect my USB
> device, even if I'm trying to change settings for another profile that
> doesn't use that device).

Please let us discus each issue in its related bug report. Would get confusing otherwise.

After upgrading to 1.1.3-4 did you connect your drive once and ran settings? Because the fix is to cache the UUID in config and use this next time the drive isn't available. If you didn't connect it and run settings there is no cached UUID in config and so it will still fail.

[Mauro (mauromol)]

Hi Germar,
I connected the USB device, re-entered in the settings dialog, saved, disconnected the USB drive and now I can change the settings again without the need to have the drive always connected.
So it works after re-saving settings, thank you! :-)