Arch Linux User Repository

Using an AUR helper such as yay to build packages including backintime is HIGHLY discouraged. The recommended build method is to use a clean chroot. See: https://wiki.archlinux.org/title/DeveloperWiki:Building_in_a_clean_chroot

I wrote a script that automates much of that called clean-chroot-manager offered here in the AUR.

Please stop posting build failures because you insist on building with yay or other AUR helpers.

@Rhinoceros

I just installed xorg-xdpyinfo and it still tests fine. Might be something else preventing the test from running though.

e.g. if xdpyinfo > /dev/null && echo $? returns a value <> 0 the systray icon is not shown (and the unit test cannot fail therefore)

... I am building on a headless system, but I'm just running makepkg, which creates both backintime and backintime-cli. I do only have backintime-cli installed on this system though. I was just building backintime here to test on a system without the icons installed.

Perhaps some icons were installed by another package so that the default theme contains the required icon file.

You can see the names of the installed icon themes with this command:

ls /usr/share/icons

@graysky Together we have found the reason for the sometimes failing unit test (see https://github.com/bit-team/backintime/issues/1404).

The reason is a missing icon file (BiT does not deliver its own app icon but relies on the installed icon theme to contain this).

There are at least two options now:

1. "Hotfix" this in your PKGBUILD file by adding oxygen-icons to the dependencies of backintime only (NOT for the CLI but for the GUI! The systray icon code is a plugin in of backintime-qt = the GUI). This is the "last ressort" fallback icon theme of BiT

2. Wait for my upcoming fix which hopefully solves all icon and systray related issues (except some edge cases as root and with wayland). I am intending to push the fix in about two weeks to our dev branch. When the fix makes its way into a new release is currently undetermined (no schedule).

@dev_aryoda Sorry I should have been clearer. The error ModuleNotFoundError: No module named 'PyQt5' was after running the github command you linked earlier. It wasn't anything from backintime per se.

Yes, I am building on a headless system, but I'm just running makepkg, which creates both backintime and backintime-cli. I do only have backintime-cli installed on this system though. I was just building backintime here to test on a system without the icons installed.

@Rhinoceros To re-run the unit tests without a re-installation you could invoke the unit tests manually from the AUR build folder (see https://github.com/bit-team/backintime/issues/1404#issuecomment-1418198930).

ModuleNotFoundError: No module named 'PyQt5'

That is surprising because BiT uses exactly the same python module and PKGBUILD even declares this dependency. Have you possibly only installed backintime-CLI (without backintime which is the GUI with the PyQt5 dependency)?

Edit: If you have installed only backintime-CLI then this explains why the unit tests succeed without an error because the "show system tray icon" functionality is implemented as plugin in the GUI part of the backintime package. Normally on headless systems only backintime-CLI should be installed! Nevertheless it is a BiT bug if the GUI part is installed on a headless system and the backintime (CLI) shows a Qt5 error! I am already fixing this...

@dev_aryoda I just get

Traceback (most recent call last):
  File "<string>", line 2, in <module>
ModuleNotFoundError: No module named 'PyQt5'

@dev_aryoda I just installed xorg-xdpyinfo and it still tests fine. Might be something else preventing the test from running though. Can I force the test to run manually?

@Rhinoceros To find out for sure which theme/icon set Qt5 is using by default you can use my console commands here: https://github.com/bit-team/backintime/issues/1098#issuecomment-1325794193

@Rhinoceros Then this may be a lucky side effect because xdpyinfo is not installed (so that BiT does not try to show a system tray icon at all and the unit test omits this part).

@dev_aryoda I don't have adwaita-icon-theme, breeze*, nor oxygen* installed. I also checked /usr/share/icons, but there's nothing substantial in there. Just a handful of app icons for gvim, htop, qv4l2, qvidcap. Still builds/tests fine.