On Sat, 2022-10-29 at 12:39 +0000, c.buhtz@posteo.jp wrote:
But what can I do to manually (on my testing systems) do make this udev-debus-error-message go away?
Could you please give me some context around your question so that I can give a more specific answer? Generally: - To get rid of DBus errors and warnings only a successful installation of BiT common does really help (after solving all problems to get that far ;-) -> make install - Fixing #1333 is still on my TODO list which says (internal comments): BiT fails to build from AUR with yay in Arch https://github.com/bit-team/backintime/issues/1333 -> yay -S backintime-cli-git backintime-git Reasons: 1. Missing dependencies on fresh install in PKGBUILD: sudo pacman -Sy python-packaging (by BiT) + sudo pacman -Sy python-pyfakefs (only for some unit tests) 2. Error in implementation of "--diagnostics": RTE when using new rsync version that supports -VV to write version information as JSON because BiT tries a string trim on a dict (created from JSON) in that case instead of trimming a version string in 3. Unit test bug that I have introduced by changing the log output (write all log to stderr, incl. INFO and WARNING) https://github.com/bit-team/backintime/pull/1337 One unit test now fails in case of a first-time installation because the BiT serviceHelper D-Bus daemon is not yet installed and BiT throws a different sequence of warnings than the unit test ist ignoring (the regexp ignores any output at the beginning and end of the log output, but not within the expected output) for line in error.split("\n") # returns a list of strings new_list = [line for line in error.split("\n") if line ...] new_list = [] .... new_list.append(line) if not (line.startswith('TextGenerator')): "\n".join(new_list) 4. Further unit test bug(s) that we introduced with "--diagnostics" in case of unexpected or missing results -> eg. non-standard language settings (LC_ALL=C)