Closed jalsti closed 2 months ago
Hello jalsti,
Thank you for taking the time to report the bug and providing the details.
Is this the first time you do use Back In Time or the first time you use it on a Devuan system?
Can you please ask in the Devuan community about this error message? Might be that it is a Devuan specific security setting.
Best regards, Christian
EDIT: Found the error string in #1008 but do not see how this could help.
This is related to our serviceHelper.py
and must be a configuration, installation or special hardening/setting thing:
I am not sure how to find the exact reason for the exception but debugging our code won't help I guess.
I thought the same. It seems that Devuan don't have a distro specific package for Back In Time. Debians package (incl. its maintainer) is used. My suggestion would be to first ask the Devuan community instead of opening a ticket at Debian.
EDIT: Found the error string in #1008 but do not see how this could help.
Actually this might help(?), because I use an older config where the old backup disk does not exist anymore, and a new, empty, one is taken. So this is more like 'changing backup destination'. I will try a new backup profile and see what happens.
(By the way: Devuan is basically a Debian version with stripped systemd dependencies, so, yes, most packages are original Debian ones.)
I will try a new backup profile and see what happens.
Does not change anything, when trying to save, the error appears. (Funnily in the meantime, even before removing config folders, I could not reproduce the part where the error pops up in switching the profile in the settings anymore, although it came up many times.)
(By the way: Devuan is basically a Debian version with stripped systemd dependencies, so, yes, most packages are original Debian ones.)
My thought where that there might be Devuan specific security settings causing the problem. In this case a Devuan specific package maintainer would be more helpful then a Debian one. Additionally to that "our" Debian maintainer is not very responsive.
I posted at the Devuan mailing list https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng – for now closing this here, thx all.
Ok, thank you. Feel free to re-open if we can be of assistance.
I think it could be helpful to extract the exact error message of dbus
(not the BiT stacktrace) from the system log to help the devuan community to identify the problem:
Run BiT until the error occurs and then use journalctl --since "1 minute ago" | grep -i backintime
(you can adjust the minutes accordingly). There you must find a dbus
policy (or polkit) error that may be helpful.
It would also be helpful to post this log output here (for other users with the same problem to find this issue and because I am curious ;-)
When trying to set udev rules in backintime-qt, so that it starts if the matching disk is attached, the message "com.ubuntu.DeviceDriver.PermissionDeniedByPolicy: net.launchpad.backintime.UdevRuleSave" appears, as soon as clicking 'OK', and nothing gets saved. When configuring manually via config file, to use udev, and having set up the rule manually, the same message appears already when entering the profile via GUI, after BIT start.