System info generated by inxi is potentially more useful;
Output of this command (formatted according to forum requirements) may be useful for those wishing to help:
inxi --filter --verbosity=8
or the short form:
inxi -zv8
Be prepared to provide more information and outputs from other commands whenever asked. It’s equally important to provide as much actionable information as possible in your first post, rather than simply indicating there is a problem.
There is a name/version clash between AUR and Manjaro repo 2025-04-14T03:50:00Z
$ pamac search backintime
backintime-qt 1.5.4-1 extra
Qt frontend for Back In Time
backintime-git 1.4.3.r54.g50c74444-1 AUR
Simple backup/snapshot system inspired by Flyback and
TimeVault. Qt6 GUI version
backintime-cli-git 1.4.3.r54.g50c74444-1 AUR
Simple backup/snapshot system inspired by Flyback and
imeVault. CLI version
backintime-cli 1.5.4-1 AUR
Simple backup system inspired from the Flyback Project and
TimeVault. CLI version.
backintime 1.5.4-1 AUR
Simple backup system inspired from the Flyback Project and
TimeVault. Qt5 GUI version.
backintime 1.5.4-1 extra
Simple backup system inspired from the Flyback Project and
TimeVault.
Make sure you have not accidently using the qt5 version from AUR
I am on Xfce (X11), system all up-to-date, and backintime-qt crash also for me, version 1.5.4-1, installed from extra repo.
No Idea how to prove it, but I am using the package from the extra repo, otherwise, I would report it in the AUR.
There you go (from the laptop, because it doesn’t seem to be due to my config):
inxi -zv8 ✔
System:
Kernel: 6.6.86-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 14.2.1
clocksource: tsc avail: acpi_pm parameters: BOOT_IMAGE=/vmlinuz-6.6-x86_64
root=UUID=e42042bf-f4bf-4c84-8dc9-8f4cc745b18a rw quiet
cryptdevice=UUID=e30b42ae-6a14-4c68-a4ba-6cca0d90f151:luks-root
root=/dev/mapper/luks-root splash apparmor=1 security=apparmor
udev.log_priority=3
Desktop: GNOME v: 48.0 tk: GTK v: 3.24.49 wm: gnome-shell
tools: gsd-screensaver-proxy dm: GDM v: 48.0 Distro: Manjaro
base: Arch Linux
Machine:
Type: Convertible System: LENOVO product: 81Q9 v: Lenovo Yoga C940-14IIL
serial: <superuser required> Chassis: type: 31 v: Lenovo Yoga C940-14IIL
serial: <superuser required>
Mobo: LENOVO model: LNVNB161216 v: SDK0R32862 WIN
serial: <superuser required>
part-nu: LENOVO_MT_81Q9_BU_idea_FM_Yoga C940-14IIL
uuid: <superuser required> UEFI: LENOVO v: AUCN57WW date: 08/18/2020
Battery:
ID-1: BAT1 charge: 51.4 Wh (100.0%) condition: 51.4/60.0 Wh (85.7%)
power: 32.9 W volts: 7.9 min: 7.7 model: Simplo BASE-BAT type: Li-poly
serial: <filter> status: discharging
Memory:
System RAM: total: 16 GiB available: 15.19 GiB used: 5.97 GiB (39.3%)
Message: For most reliable report, use superuser + dmidecode.
Array-1: capacity: 16 GiB slots: 2 modules: 2 EC: None
max-module-size: 8 GiB note: est.
Device-1: ChannelA-DIMM0 type: LPDDR4 detail: synchronous size: 8 GiB
speed: spec: 4267 MT/s actual: 3733 MT/s volts: curr: 0.6 min: 2 max: 2
width (bits): data: 32 total: 32 manufacturer: Micron part-no: N/A
serial: N/A
Device-2: ChannelB-DIMM0 type: LPDDR4 detail: synchronous size: 8 GiB
speed: spec: 4267 MT/s actual: 3733 MT/s volts: curr: 0.6 min: 2 max: 2
width (bits): data: 32 total: 32 manufacturer: Micron part-no: N/A
serial: N/A
PCI Slots:
Permissions: Unable to run dmidecode. Root privileges required.
CPU:
Info: model: Intel Core i7-1065G7 bits: 64 type: MT MCP arch: Ice Lake
gen: core 10 level: v4 note: check built: 2019-21 process: Intel 10nm
family: 6 model-id: 0x7E (126) stepping: 5 microcode: 0xC6
Topology: cpus: 1x dies: 1 clusters: 4 cores: 4 threads: 8 tpc: 2
smt: enabled cache: L1: 320 KiB desc: d-4x48 KiB; i-4x32 KiB L2: 2 MiB
desc: 4x512 KiB L3: 8 MiB desc: 1x8 MiB
Speed (MHz): avg: 3370 min/max: 400/3900 scaling: driver: intel_pstate
governor: powersave cores: 1: 3370 2: 3370 3: 3370 4: 3370 5: 3370 6: 3370
7: 3370 8: 3370 bogomips: 23968
Flags: 3dnowprefetch abm acpi adx aes aperfmperf apic arat
arch_capabilities arch_perfmon art avx avx2 avx512_bitalg avx512_vbmi2
avx512_vnni avx512_vpopcntdq avx512bw avx512cd avx512dq avx512f
avx512ifma avx512vbmi avx512vl bmi1 bmi2 bts clflush clflushopt cmov
constant_tsc cpuid cpuid_fault cx16 cx8 de ds_cpl dtes64 dtherm dts epb
ept ept_ad erms est f16c flexpriority flush_l1d fma fpu fsgsbase fsrm
fxsr gfni ht hwp hwp_act_window hwp_epp hwp_notify hwp_pkg_req ibpb ibrs
ibrs_enhanced ida intel_pt invpcid lahf_lm lm mca mce md_clear mmx
monitor movbe msr mtrr nonstop_tsc nopl nx ospke pae pat pbe pcid
pclmulqdq pdcm pdpe1gb pebs pge pku pln pni popcnt pse pse36 pts rdpid
rdrand rdseed rdtscp rep_good sdbg sep sgx sgx_lc sha_ni smap smep
split_lock_detect ss ssbd sse sse2 sse4_1 sse4_2 ssse3 stibp syscall tm
tm2 tpr_shadow tsc tsc_adjust tsc_deadline_timer tsc_known_freq umip vaes
vme vmx vnmi vpclmulqdq vpid x2apic xgetbv1 xsave xsavec xsaveopt xsaves
xtopology xtpr
Vulnerabilities:
Type: gather_data_sampling mitigation: Microcode
Type: itlb_multihit status: KVM: VMX disabled
Type: l1tf status: Not affected
Type: mds status: Not affected
Type: meltdown status: Not affected
Type: mmio_stale_data mitigation: Clear CPU buffers; SMT vulnerable
Type: reg_file_data_sampling status: Not affected
Type: retbleed mitigation: Enhanced IBRS
Type: spec_rstack_overflow status: Not affected
Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
prctl
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
sanitization
Type: spectre_v2 mitigation: Enhanced / Automatic IBRS; IBPB:
conditional; RSB filling; PBRSB-eIBRS: SW sequence; BHI: SW loop, KVM: SW
loop
Type: srbds mitigation: Microcode
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: Intel Iris Plus Graphics G7 vendor: Lenovo driver: i915 v: kernel
arch: Gen-11 process: Intel 10nm built: 2019-21 ports: active: eDP-1
empty: DP-1,DP-2,DP-3 bus-ID: 00:02.0 chip-ID: 8086:8a52 class-ID: 0300
Device-2: Chicony Integrated Camera driver: uvcvideo type: USB rev: 2.0
speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 3-1:2 chip-ID: 04f2:b61e
class-ID: 0e02 serial: <filter>
Display: wayland server: X.org v: 1.21.1.16 with: Xwayland v: 24.1.6
compositor: gnome-shell driver: X: loaded: modesetting alternate: fbdev,vesa
dri: iris gpu: i915 display-ID: 0
Monitor-1: eDP-1 model: BOE Display 0x0821 built: 2018 res: 3840x2160
dpi: 316 gamma: 1.2 chroma: red: x: 0.667 y: 0.329 green: x: 0.271 y: 0.663
blue: x: 0.141 y: 0.059 white: x: 0.314 y: 0.329
size: 309x174mm (12.17x6.85") diag: 355mm (14") ratio: 16:9
modes: 3840x2160
EDID-Warnings: 1: parse_edid: unknown flag 0
API: EGL v: 1.5 hw: drv: intel iris platforms: device: 0 drv: iris
device: 1 drv: swrast gbm: drv: iris surfaceless: drv: iris wayland:
drv: iris x11: drv: iris
API: OpenGL v: 4.6 compat-v: 4.5 vendor: intel mesa v: 25.0.3-arch1.1
glx-v: 1.4 direct-render: yes renderer: Mesa Intel Iris Plus Graphics (ICL
GT2) device-ID: 8086:8a52 memory: 7.41 GiB unified: yes display-ID: :0.0
Info: Tools: api: eglinfo,glxinfo gpu: gputop, intel_gpu_top, lsgpu
x11: xdpyinfo, xprop, xrandr
Audio:
Device-1: Intel Ice Lake-LP Smart Sound Audio vendor: Lenovo
driver: sof-audio-pci-intel-icl
alternate: snd_hda_intel,snd_sof_pci_intel_icl bus-ID: 00:1f.3
chip-ID: 8086:34c8 class-ID: 0401
API: ALSA v: k6.6.86-1-MANJARO status: kernel-api with: aoss
type: oss-emulator tools: alsactl,alsamixer,amixer
Server-1: JACK v: 1.9.22 status: off tools: N/A
Server-2: PipeWire v: 1.4.1 status: active with: 1: pipewire-pulse
status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
tools: pactl,pw-cat,pw-cli,wpctl
Network:
Device-1: Intel Ice Lake-LP PCH CNVi WiFi driver: iwlwifi v: kernel
bus-ID: 00:14.3 chip-ID: 8086:34f0 class-ID: 0280
IF: wlp0s20f3 state: up mac: <filter>
IP v4: <filter> type: dynamic noprefixroute scope: global
broadcast: <filter>
IF-ID-1: br-3c7679397bd0 state: down mac: <filter>
IP v4: <filter> scope: global broadcast: <filter>
IF-ID-2: br-47195be9e978 state: down mac: <filter>
IP v4: <filter> scope: global broadcast: <filter>
IF-ID-3: br-4cbd404407fc state: down mac: <filter>
IP v4: <filter> scope: global broadcast: <filter>
IF-ID-4: br-b70272889e99 state: down mac: <filter>
IP v4: <filter> scope: global broadcast: <filter>
IF-ID-5: docker0 state: down mac: <filter>
IP v4: <filter> scope: global broadcast: <filter>
IF-ID-6: virbr0 state: down mac: <filter>
IP v4: <filter> scope: global broadcast: <filter>
Info: services: NetworkManager, systemd-timesyncd, wpa_supplicant
WAN IP: <filter>
Bluetooth:
Device-1: Intel AX201 Bluetooth driver: btusb v: 0.8 type: USB rev: 2.0
speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 3-10:4 chip-ID: 8087:0026
class-ID: e001
Report: btmgmt ID: hci0 rfk-id: 2 state: up address: <filter> bt-v: 5.2
lmp-v: 11 status: discoverable: no pairing: no class-ID: 6c0000
Logical:
Message: No logical block device data found.
Device-1: luks-root maj-min: 254:0 type: LUKS dm: dm-0 size: 653.32 GiB
Components:
p-1: nvme0n1p3 maj-min: 259:3 size: 653.32 GiB
RAID:
Message: No RAID data found.
Drives:
Local Storage: total: 953.87 GiB used: 310.31 GiB (32.5%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung
model: MZVLB1T0HBLR-000L2 size: 953.87 GiB block-size: physical: 512 B
logical: 512 B speed: 31.6 Gb/s lanes: 4 tech: SSD serial: <filter>
fw-rev: 3L1QEXF7 temp: 35.9 C scheme: GPT
Message: No optical or floppy data found.
Partition:
ID-1: / raw-size: 653.32 GiB size: 642 GiB (98.27%) used: 310.14 GiB (48.3%)
fs: ext4 dev: /dev/dm-0 maj-min: 254:0 mapped: luks-root label: N/A
uuid: N/A
ID-2: /boot raw-size: 1024 MiB size: 973.4 MiB (95.06%)
used: 147.5 MiB (15.1%) fs: ext4 dev: /dev/nvme0n1p2 maj-min: 259:2
label: linux boot uuid: 6542643d-e55f-448e-9edf-7974b392716a
ID-3: /boot/efi raw-size: 512 MiB size: 511 MiB (99.80%)
used: 31.4 MiB (6.1%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
label: BOOT uuid: 2A3C-FC50
Swap:
Kernel: swappiness: 60 (default) cache-pressure: 100 (default) zswap: yes
compressor: zstd max-pool: 20%
ID-1: swap-1 type: file size: 6 GiB used: 0 KiB (0.0%) priority: -2
file: /swapfile
Unmounted:
ID-1: /dev/nvme0n1p4 maj-min: 259:4 size: 16 MiB fs: <superuser required>
label: N/A uuid: N/A
ID-2: /dev/nvme0n1p5 maj-min: 259:5 size: 298.07 GiB fs: ntfs label: N/A
uuid: 7EF64129F640E2CF
ID-3: /dev/nvme0n1p6 maj-min: 259:6 size: 977 MiB fs: ntfs label: N/A
uuid: A8648CA7648C7A38
USB:
Hub-1: 1-0:1 info: hi-speed hub with single TT ports: 1 rev: 2.0
speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
class-ID: 0900
Hub-2: 2-0:1 info: super-speed hub ports: 4 rev: 3.1
speed: 10 Gb/s (1.16 GiB/s) lanes: 1 mode: 3.2 gen-2x1 chip-ID: 1d6b:0003
class-ID: 0900
Hub-3: 3-0:1 info: hi-speed hub with single TT ports: 12 rev: 2.0
speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
class-ID: 0900
Device-1: 3-1:2 info: Chicony Integrated Camera type: video
driver: uvcvideo interfaces: 2 rev: 2.0 speed: 480 Mb/s (57.2 MiB/s)
lanes: 1 mode: 2.0 power: 500mA chip-ID: 04f2:b61e class-ID: 0e02
serial: <filter>
Device-2: 3-5:3 info: Synaptics type: <vendor specific> driver: usbfs
interfaces: 1 rev: 2.0 speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1
power: 100mA chip-ID: 06cb:00be class-ID: ff00 serial: <filter>
Device-3: 3-10:4 info: Intel AX201 Bluetooth type: bluetooth driver: btusb
interfaces: 2 rev: 2.0 speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1
power: 100mA chip-ID: 8087:0026 class-ID: e001
Hub-4: 4-0:1 info: super-speed hub ports: 6 rev: 3.1
speed: 10 Gb/s (1.16 GiB/s) lanes: 1 mode: 3.2 gen-2x1 chip-ID: 1d6b:0003
class-ID: 0900
Sensors:
System Temperatures: cpu: 72.0 C mobo: N/A
Fan Speeds (rpm): N/A
Repos:
Packages: pm: pacman pkgs: 2378 libs: 486 tools: gnome-software,pamac
pm: flatpak pkgs: 0
Active pacman repo servers in: /etc/pacman.conf
1: https://mirrors.xtom.de/bioarchlinux/$arch
2: http://download.opensuse.org/repositories/home:/pbek:/QOwnNotes/Arch_Extra/$arch
Active pacman repo servers in: /etc/pacman.d/chaotic-mirrorlist
1: https://cdn-mirror.chaotic.cx/$repo/$arch
2: https://geo-mirror.chaotic.cx/$repo/$arch
3: https://br-mirror.chaotic.cx/$repo/$arch
4: https://bg-mirror.chaotic.cx/$repo/$arch
5: https://ca-mirror.chaotic.cx/$repo/$arch
6: https://cl-mirror.chaotic.cx/$repo/$arch
7: https://de-2-mirror.chaotic.cx/$repo/$arch
8: https://de-3-mirror.chaotic.cx/$repo/$arch
9: https://de-4-mirror.chaotic.cx/$repo/$arch
10: https://fr-mirror.chaotic.cx/$repo/$arch
11: https://gr-mirror.chaotic.cx/$repo/$arch
12: https://in-mirror.chaotic.cx/$repo/$arch
13: https://in-2-mirror.chaotic.cx/$repo/$arch
14: https://in-3-mirror.chaotic.cx/$repo/$arch
15: https://in-4-mirror.chaotic.cx/$repo/$arch
16: https://kr-mirror.chaotic.cx/$repo/$arch
17: https://es-mirror.chaotic.cx/$repo/$arch
18: https://es-2-mirror.chaotic.cx/$repo/$arch
19: https://us-mi-mirror.chaotic.cx/$repo/$arch
20: https://us-tx-mirror.chaotic.cx/$repo/$arch
21: https://us-ut-mirror.chaotic.cx/$repo/$arch
Active pacman repo servers in: /etc/pacman.d/mirrorlist
1: https://ftp.halifax.rwth-aachen.de/manjaro/unstable/$repo/$arch
2: https://mirror.23m.com/manjaro/unstable/$repo/$arch
3: http://ftp.uni-kl.de/pub/linux/manjaro/unstable/$repo/$arch
4: https://manjaro.kurdy.org/unstable/$repo/$arch
5: http://ftp.rz.tu-bs.de/pub/mirror/manjaro.org/repos/unstable/$repo/$arch
6: https://ftp.gwdg.de/pub/linux/manjaro/unstable/$repo/$arch
7: https://mirror.alpix.eu/manjaro/unstable/$repo/$arch
8: https://mirror.netcologne.de/manjaro/unstable/$repo/$arch
Processes:
CPU top: 5 of 323
1: cpu: 118% command: QtWebEngineProcess pid: 3123 mem: 402.4 MiB (2.5%)
2: cpu: 100% command: ps pid: 4506 mem: 4.48 MiB (0.0%)
3: cpu: 78.2% command: firefox pid: 3365 mem: 546.4 MiB (3.5%)
4: cpu: 39.1% command: zapzap started-by: python pid: 2395
mem: 356.4 MiB (2.2%)
5: cpu: 34.4% command: firefox pid: 3669 mem: 252.0 MiB (1.6%)
Memory top: 5 of 323
1: mem: 546.4 MiB (3.5%) command: firefox pid: 3365 cpu: 78.2%
2: mem: 485.8 MiB (3.1%) command: signal-desktop pid: 2399 cpu: 16.8%
3: mem: 402.4 MiB (2.5%) command: QtWebEngineProcess pid: 3123 cpu: 118%
4: mem: 381.6 MiB (2.4%) command: firefox pid: 3543 cpu: 22.3%
5: mem: 372.3 MiB (2.3%) command: gnome-shell pid: 2117 cpu: 19.9%
Info:
Processes: 323 Power: uptime: 1m states: freeze,mem,disk suspend: s2idle
avail: deep wakeups: 0 hibernate: platform avail: shutdown, reboot,
suspend, test_resume image: 6.06 GiB services: gsd-power,
power-profiles-daemon, upowerd Init: systemd v: 257 default: graphical
tool: systemctl
Compilers: clang: 19.1.7 gcc: 14.2.1 Shell: Zsh v: 5.9
running-in: gnome-terminal inxi: 3.3.37
As I understand it, use of the Chaotic AUR is even less recommended than the AUR itself, which is not officially supported by Manjaro.
Perhaps this factor may be contributing in some way.
As far as I am concerned, use of the Chaotic AUR is only more problematic than use of the “regular” AUR, when you use the stable branch of Manjaro.
Since I am on Manjaro Unstable, this shouldn’t be an issue, since the dependency version are usually identical with Arch Linux.
And what’s even more important is that I also get the crash on a fresh Manjaro VM, with no AUR or third-party repo packages installed.
I am not postulating anything - the problem with that is the name version clash - what I am saying … See for your self
→ https://aur.archlinux.org/packages?O=0&K=backintime
The only way you can be sure which one, is to use pacman to sync backintime to your system.
sudo pacman -Rns backintime backintime-cli
sudo pacman -Syu extra/backintime extra/backintime-qt
The GUI version in the extra repo is called backintime-qt.
So it is fairly easy to mix things up if you are using Pamac and not pacman and even easier if using a the chaotic repo and if you placed chaotic above core and extra - you are doomed and must face the consequences.
//EDIT:
@Yochanan is our highly capable packager and resident 
which has packaged backintime and backintime-qt and that makes me fairly certain there is not issues with the packaging for Manjaro extra repo.
I tested a clean install from the latest release-review full ISO - backintime-qt launches as expected so there is something off on your side - what it is - as I cannot reproduce, I have no idea?
Is this laptop the machine you’re having difficulty with?
Yes
I did execute exactly those commands (backintime-cli wasn’t installed, so I removed that), and get the same crash:
sudo pacman -Rns backintime backintime-qt 1 ✘
Abhängigkeiten werden geprüft …
:: inxi benötigt optional xorg-xdpyinfo: xdpyinfo: -G (X) Screen resolution, dpi; -Ga Screen size
:: python-wheel benötigt optional python-keyring: for wheel.signatures
Pakete (7) python-jaraco.classes-3.4.0-2 python-jeepney-0.9.0-1
python-keyring-25.6.0-1 python-secretstorage-3.3.3-6
xorg-xdpyinfo-1.3.4-2 backintime-1.5.4-1 backintime-qt-1.5.4-1
Gesamtgröße der entfernten Pakete: 6,48 MiB
:: Möchten Sie diese Pakete entfernen? [J/n] J
:: Paketänderungen werden verarbeitet …
(1/7) Entfernung läuft backintime-qt [######################] 100%
(2/7) Entfernung läuft xorg-xdpyinfo [######################] 100%
(3/7) Entfernung läuft backintime [######################] 100%
(4/7) Entfernung läuft python-keyring [######################] 100%
(5/7) Entfernung läuft python-secretstorage [######################] 100%
(6/7) Entfernung läuft python-jeepney [######################] 100%
(7/7) Entfernung läuft python-jaraco.classes [######################] 100%
:: Post-transaction-Hooks werden gestartet …
(1/4) Arming ConditionNeedsUpdate...
(2/4) Reloading system bus configuration...
(3/4) Updating icon theme caches...
(4/4) Updating the desktop file MIME type cache...
~ sudo pacman -Syu extra/backintime extra/backintime-qt ✔
:: Paketdatenbanken werden synchronisiert …
core ist aktuell
extra ist aktuell
multilib ist aktuell
chaotic-aur ist aktuell
bioarchlinux ist aktuell
home_pbek_QOwnNotes_Arch_Extra ist aktuell
:: Vollständige Systemaktualisierung wird gestartet …
Abhängigkeiten werden aufgelöst …
Nach in Konflikt stehenden Paketen wird gesucht …
Pakete (7) python-jaraco.classes-3.4.0-2 python-jeepney-0.9.0-1
python-keyring-25.6.0-1 python-secretstorage-3.3.3-6
xorg-xdpyinfo-1.3.4-2 backintime-1.5.4-1 backintime-qt-1.5.4-1
Gesamtgröße der installierten Pakete: 6,48 MiB
:: Installation fortsetzen? [J/n] J
(7/7) Schlüssel im Schlüsselbund werden geprüft [######################] 100%
(7/7) Paket-Integrität wird überprüft [######################] 100%
(7/7) Paket-Dateien werden geladen [######################] 100%
(7/7) Auf Dateikonflikte wird geprüft [######################] 100%
(7/7) Verfügbarer Festplattenspeicher wird erm... [######################] 100%
:: Paketänderungen werden verarbeitet …
(1/7) Installiert wird python-jaraco.classes [######################] 100%
(2/7) Installiert wird python-jeepney [######################] 100%
Optionale Abhängigkeiten für python-jeepney
python-trio: support D-Bus applications with Trio
(3/7) Installiert wird python-secretstorage [######################] 100%
(4/7) Installiert wird python-keyring [######################] 100%
Optionale Abhängigkeiten für python-keyring
libsecret: libsecret backend [Installiert]
python-dbus: kwallet backend [Installiert]
python-gobject: libsecret backend [Installiert]
python-keyrings-alt: Alternative backends
python-pluggy: devpi client [Installiert]
(5/7) Installiert wird backintime [######################] 100%
Optionale Abhängigkeiten für backintime
backintime-qt: Qt frontend [ausstehend]
encfs: encrypted filesystem in user-space
sshfs: FUSE client based on the ssh file transfer protocol [Installiert]
(6/7) Installiert wird xorg-xdpyinfo [######################] 100%
(7/7) Installiert wird backintime-qt [######################] 100%
Optionale Abhängigkeiten für backintime-qt
gnome-keyring: option for SSH key storage [Installiert]
kompare: option for comparing files
kwallet: option for SSH key storage [Installiert]
meld: option for comparing files [Installiert]
oxygen-icons: fallback in case of missing icons
python-secretstorage: option for SSH key storage [Installiert]
:: Post-transaction-Hooks werden gestartet …
(1/4) Arming ConditionNeedsUpdate...
(2/4) Reloading system bus configuration...
(3/4) Updating icon theme caches...
(4/4) Updating the desktop file MIME type cache...
~ backintime-qt ✔ 5s
Back In Time
Version: 1.5.4
Back In Time comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to redistribute it
under certain conditions; type `backintime --license' for details.
Traceback (most recent call last):
File "/usr/share/backintime/qt/app.py", line 2472, in <module>
mainWindow = MainWindow(cfg, appInstance, qapp)
File "/usr/share/backintime/qt/app.py", line 342, in __init__
SettingsDialog(self).exec()
~~~~~~~~~~~~~~^^^^^^
File "/usr/share/backintime/qt/manageprofiles/__init__.py", line 253, in __init__
self._tab_retention = RemoveRetentionTab(self)
~~~~~~~~~~~~~~~~~~^^^^^^
File "/usr/share/backintime/qt/manageprofiles/tab_remove_retention.py", line 65, in __init__
self._label_rule_execute_order()
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^
File "/usr/share/backintime/qt/manageprofiles/tab_remove_retention.py", line 177, in _label_rule_execute_order
icon = self.style().standardPixmap(
QStyle.StandardPixmap.SP_MessageBoxInformation)
TypeError: standardPixmap(self, standardPixmap: QStyle.StandardPixmap, opt: Optional[QStyleOption], widget: Optional[QWidget] = None): not enough arguments
I didn’t want to doubt anyone’s capabilities and am very happy for the great work that everybody at Manjaro does 
Anyway, there is a problem that I’m not able to fix on my own, that’s why I’m asking.
Did you test it with the Manjaro Gnome ISO? That’s what I used for my last test in the VM as well, where it crashed (no external repos there and AUR also disabled).
Edit: Just tried it again, fully updated my Manjaro Gnome VM and it still crashes.
[laurenz@laurenz-standardpc ~]$ sudo pacman -Syu
:: Synchronizing package databases...
core is up to date
extra is up to date
multilib is up to date
:: Starting full system upgrade...
there is nothing to do
[laurenz@laurenz-standardpc ~]$ backintime-qt
Back In Time
Version: 1.5.4
Back In Time comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to redistribute it
under certain conditions; type `backintime --license' for details.
Traceback (most recent call last):
File "/usr/share/backintime/qt/app.py", line 2472, in <module>
mainWindow = MainWindow(cfg, appInstance, qapp)
File "/usr/share/backintime/qt/app.py", line 342, in __init__
SettingsDialog(self).exec()
~~~~~~~~~~~~~~^^^^^^
File "/usr/share/backintime/qt/manageprofiles/__init__.py", line 253, in __init__
self._tab_retention = RemoveRetentionTab(self)
~~~~~~~~~~~~~~~~~~^^^^^^
File "/usr/share/backintime/qt/manageprofiles/tab_remove_retention.py", line 65, in __init__
self._label_rule_execute_order()
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^
File "/usr/share/backintime/qt/manageprofiles/tab_remove_retention.py", line 177, in _label_rule_execute_order
icon = self.style().standardPixmap(
QStyle.StandardPixmap.SP_MessageBoxInformation)
TypeError: standardPixmap(self, standardPixmap: QStyle.StandardPixmap, opt: Optional[QStyleOption], widget: Optional[QWidget] = None): not enough arguments
/usr/bin/backintime-qt: line 26: 2103 Segmentation fault (core dumped) /usr/bin/python -Es ${APP_PATH}/app.py "$@"
[laurenz@laurenz-standardpc ~]$
Unfortunately, inxi -zv8 gets stuck for some reason, so no good output there:
System:
Kernel: 6.12.21-4-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 14.2.1
clocksource: kvm-clock avail: tsc,acpi_pm
parameters: BOOT_IMAGE=/boot/vmlinuz-6.12-x86_64
root=UUID=0b72d104-1303-4a87-9d60-96485566868e rw quiet splash apparmor=1
security=apparmor udev.log_priority=3
Desktop: GNOME v: 48.0 tk: GTK v: 3.24.49 wm: gnome-shell
tools: gsd-screensaver-proxy dm: GDM v: 48.0 Distro: Manjaro
base: Arch Linux
Machine:
Type: Kvm System: QEMU product: Standard PC (Q35 + ICH9, 2009) v: pc-q35-9.2
serial: <superuser required> Chassis: type: 1 v: pc-q35-9.2
serial: <superuser required>
Mobo: N/A model: N/A serial: N/A uuid: <superuser required> BIOS: SeaBIOS
v: Arch Linux 1.16.3-1-1 date: 04/01/2014
Battery:
Message: No system battery data found. Is one present?
Memory:
System RAM: total: 4 GiB available: 3.82 GiB used: 1.59 GiB (41.6%)
Message: For most reliable report, use superuser + dmidecode.
Array-1: capacity: 4 GiB slots: 1 modules: 1 EC: Multi-bit ECC
max-module-size: 4 GiB note: est.
Device-1: DIMM 0 type: RAM detail: N/A size: 4 GiB speed: N/A volts: N/A
width: N/A manufacturer: Qemu part-no: N/A serial: N/A
PCI Slots:
Permissions: Unable to run dmidecode. Root privileges required.
CPU:
Info: model: Intel Core i5-8600K bits: 64 type: SMP arch: Coffee Lake
gen: core 8 level: v3 note: check built: 2018 process: Intel 14nm family: 6
model-id: 0x9E (158) stepping: 0xA (10) microcode: 0xFA
Topology: cpus: 4x dies: 1 clusters: 1 cores: 1 smt: <unsupported> cache:
L1: 4x 64 KiB (256 KiB) desc: d-1x32 KiB; i-1x32 KiB L2: 4x 4 MiB (16 MiB)
desc: 1x4 MiB L3: 4x 16 MiB (64 MiB) desc: 1x16 MiB
Speed (MHz): avg: 3600 min/max: N/A cores: 1: 3600 2: 3600 3: 3600 4: 3600
bogomips: 28808
Flags: 3dnowprefetch abm adx aes apic arat arch_capabilities arch_perfmon
avx avx2 bmi1 bmi2 clflush clflushopt cmov constant_tsc cpuid cpuid_fault
cx16 cx8 de ept ept_ad erms f16c flexpriority flush_l1d fma fpu fsgsbase
fxsr hypervisor ibpb ibrs invpcid lahf_lm lm mca mce md_clear mmx movbe
mpx msr mtrr nopl nx pae pat pcid pclmulqdq pdcm pdpe1gb pge pni popcnt
pse pse36 pti rdrand rdseed rdtscp rep_good sep smap smep ss ssbd sse
sse2 sse4_1 sse4_2 ssse3 stibp syscall tpr_shadow tsc tsc_adjust
tsc_deadline_timer tsc_known_freq umip vme vmx vnmi vpid x2apic xgetbv1
xsave xsavec xsaveopt xsaves xtopology
Vulnerabilities:
Type: gather_data_sampling status: Not affected
Type: itlb_multihit status: Not affected
Type: l1tf mitigation: PTE Inversion; VMX: flush not necessary, SMT
disabled
Type: mds mitigation: Clear CPU buffers; SMT Host state unknown
Type: meltdown mitigation: PTI
Type: mmio_stale_data mitigation: Clear CPU buffers; SMT Host state
unknown
Type: reg_file_data_sampling status: Not affected
Type: retbleed mitigation: IBRS
Type: spec_rstack_overflow status: Not affected
Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
prctl
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
sanitization
Type: spectre_v2 mitigation: IBRS; IBPB: conditional; STIBP: disabled;
RSB filling; PBRSB-eIBRS: Not affected; BHI: SW loop, KVM: SW loop
Type: srbds status: Unknown: Dependent on hypervisor status
Type: tsx_async_abort status: Not affected
[nothing more appears]
I don’t really know what else I can do to help reproducing this issue…
It should be somewhat clear, that it’s not just my system configuration, that leads to this error, since at least @D.Dave (on Xfce) and @Nachlese (on whatever) got the same error when starting as non-root.
Yup - I have manjaro-get-iso synced to my system
get-iso --review --full gnome
Then I launched a vm to install using the ISO I just downloaded and when the install was ready I rebooted the vm, updated the mirror pool to use an up-to-date mirror (mirror.easyname.at) and synced backintime-qt (adding -fc is forcing console mode - personal preference)
sudo pacman-mirrors --country Austria --interactive
sudo pacman -Sy backintime-qt
All this using stable branch - no issues - I am not the judge of what - but I am certain it is not related to the current state of stable branch.
This points to an underlying issue - I don’t know what … I really don’t … I cannot replicate your issue.
Okay interesting.
I will report it to the upstream devs and see what they are thinking.
Before you do - please test the latest review ISO released just a few days ago - if you use the release from December 2024 - it is outdated - and almost everything has been updated.
Best result comes from using the latest review …
I will.
This one? https://download.manjaro.org/gnome/24.2.1/manjaro-gnome-24.2.1-241216-linux612.iso
Ah probably not, i guess that’s from 2024 as well. Can you give me a link?
No - please use the get-iso script to get the latest release review as illustrated
My folder for iso is ~/iso
$ ls -l ~/iso/manjaro-gnome*
-rw-r--r-- 1 fh fh 3963842560 12 apr 20:17 manjaro-gnome-25.0-250412-linux612.iso
-rw-r--r-- 1 fh fh 105 14 apr 14:58 manjaro-gnome-25.0-250412-linux612.iso.sha256
sync the package manjaro-get-iso and run
get-iso --review --full gnome
It will default to use the current folder or your home if current folder is not writable. To adjust the defaults use the --help or -h to see what you can change.
So I just had this same issue occur. Here is what I found.
First, I created a new user and tried to see if Backintime would start, sure enough it did perfectly.
So then I wen tback to my regular user and same error as above. And as above, if I ran BIT as root, it would launch with no problem.
I noticed one thing, the settings dialog box that popped up asking to restore a settings file had a different theme, so I looked at my qt6ct and qt5ct settings and the one that was failing was the one using qt6ct settings. So I removed qt6ct and backintime fired right back up.
Why, I don’t know, but at least now there is a path to look down.
-John
Any idea what part of your ~/.config/qt6ct/qt6ct.conf might have caused the issue? That information would be most helpful to upstream and users alike.
My backup just completed and I decided to reinstall qt6ct and BIT starts with no issue, and is themed with qt6ct, which is much nicer looking.
As to the actual cause, I really don’t know. I know for a while there, qt5ct and qt6ct could not be installed together, they were in conflict, and my laptop has been running on the same install for 18 months. May there was a change in qt6ct, and we no longer need qt5ct. The other three machines that I run my Spin of Cinnamon, none of them are having any issue.
Here is the qt6ct.conf
[Appearance]
color_scheme_path=/usr/share/qt6ct/colors/darker.conf
custom_palette=true
icon_theme=breeze-dark
standard_dialogs=xdgdesktopportal
style=Breeze
[Fonts]
fixed="Liberation Mono,11,-1,5,400,0,0,0,0,0,0,0,0,0,0,1,Regular"
general="Inter,11,-1,5,400,0,0,0,0,0,0,0,0,0,0,1,Regular"
[Interface]
activate_item_on_single_click=1
buttonbox_layout=0
cursor_flash_time=1200
dialog_buttons_have_icons=1
double_click_interval=400
gui_effects=@Invalid()
keyboard_scheme=2
menus_have_icons=true
show_shortcuts_in_context_menus=true
stylesheets=@Invalid()
toolbutton_style=4
underline_shortcut=1
wheel_scroll_lines=3
[SettingsWindow]
geometry="@ByteArray(\x1\xd9\xd0\xcb\0\x3\0\0\0\0\x1N\0\0\0\x8c\0\0\x4,\0\0\x3\x1f\0\0\x1N\0\0\0\xa9\0\0\x4,\0\0\x3\x1f\0\0\0\0\0\0\0\0\x6\xdb\0\0\x1N\0\0\0\xa9\0\0\x4,\0\0\x3\x1f)"
[Troubleshooting]
force_raster_widgets=1
ignored_applications=/usr/bin/backintime-qt
Here is the qt5ct.conf
[Appearance]
color_scheme_path=/usr/share/qt5ct/colors/darker.conf
custom_palette=true
icon_theme=breeze-dark
standard_dialogs=gtk3
style=Breeze
[Fonts]
fixed="Liberation Mono,11,-1,5,50,0,0,0,0,0,Regular"
general="Inter,11,-1,5,50,0,0,0,0,0,Regular"
[Interface]
activate_item_on_single_click=1
buttonbox_layout=0
cursor_flash_time=1200
dialog_buttons_have_icons=1
double_click_interval=400
gui_effects=@Invalid()
keyboard_scheme=2
menus_have_icons=true
show_shortcuts_in_context_menus=true
stylesheets=/usr/share/qt5ct/qss/fusion-fixes.qss, /usr/share/qt5ct/qss/scrollbar-simple.qss, /usr/share/qt5ct/qss/sliders-simple.qss, /usr/share/qt5ct/qss/tooltip-simple.qss, /usr/share/qt5ct/qss/traynotification-simple.qss
toolbutton_style=4
underline_shortcut=1
wheel_scroll_lines=3
[SettingsWindow]
geometry=@ByteArray(\x1\xd9\xd0\xcb\0\x3\0\0\0\0\x2\x4\0\0\0J\0\0\x5\f\0\0\x3W\0\0\x2\x4\0\0\0j\0\0\x5\f\0\0\x3W\0\0\0\0\0\0\0\0\a\x80\0\0\x2\x4\0\0\0j\0\0\x5\f\0\0\x3W)
[Troubleshooting]
force_raster_widgets=1
ignored_applications=@Invalid()
Did that make any difference?
That should make no difference in theory, but have you tried using Kvantum?
Do you have QT_QPA_PLATFORMTHEME and/or QT_STYLE_OVERRIDE set on the affected machine?
No, I forgot to mention that I tried that as well, but it made no difference.
As for Breeze theme, it seems to look better with the Obsidian theme that I use, at least in my view.
My this is what I have in my .profile and switching to qt5ct made no difference either. Always logging out and loggin back in to test.
export QT_QPA_PLATFORMTHEME="qt6ct"
export EDITOR=/usr/bin/nano
If I start Back in Time like this: QT_QPA_PLATFORMTHEME=gnome backintime-qt or unset the variable completely, it launches without any problems.
Looks worse than with the qt6qc Breeze theme, but at least I can use it again.
Any idea where to report this problem?