Back In Time (Qt) crashes on Gnome Wayland

D.Dave · 6 May 2025 10:19

Here:
https://github.com/bit-team/backintime/issues/new?template=bug.yml

Ben · 6 May 2025 12:54

There’s also a regular backintime install (same version) which is not qt which should be preferable for Gnome if I’m not wrong.

MajorMayer · 6 May 2025 15:11

While I find references to a GTK-based gui in older articles, I think this is not the case anymore.
Seems like they completely switched to Qt in the meanwhile.

Anyways, one of the devs has confirmed the upstream bug. So nothing about Manjaro’s packaging.

github.com/bit-team/backintime

Crashes ("TypeError: standardPixmap(...") when running with qt6ct and Breeze theme

opened 11:47AM - 06 May 25 UTC

major-mayer

Qt Reproduced Bug

### Describe the problem, feature or ask a question: As reported downstream in …the Manjaro forums, I am getting crashes when running Back in Time as a normal user with qt6ct Breeze theme activated. I use this theme because usually it provides the best look for programs originally developed with Qt for the KDE desktop environment (like Okular e.g.). I have never experienced inconsistent or unreadable UI element, in comparison to e.g. some Kvantum themes, not to speak of crashes. Here is what happens when i run it with `QT_QPA_PLATFORMTHEME=qt6ct` (exported for my login shell, so active by default for all programs): ``` QT_QPA_PLATFORMTHEME=qt6ct 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 ``` I can see the first dialog, that mentions that no configuration has been found. When i choose to not import and existing one, the crash occurs. This does not happen if I unset the environment variable `QT_QPA_PLATFORMTHEME= backintime-qt`. This is my qt6ct configuration: ``` [Appearance] color_scheme_path=/usr/share/qt6ct/colors/airy.conf custom_palette=false icon_theme=breeze standard_dialogs=default style=Breeze [Fonts] fixed="Noto Sans Mono,10,-1,5,400,0,0,0,0,0,0,0,0,0,0,1" general="Noto Sans,10,-1,5,400,0,0,0,0,0,0,0,0,0,0,1" [Interface] activate_item_on_single_click=1 buttonbox_layout=3 cursor_flash_time=1200 dialog_buttons_have_icons=1 double_click_interval=400 gui_effects=@Invalid() keyboard_scheme=4 menus_have_icons=true show_shortcuts_in_context_menus=true stylesheets=@Invalid() toolbutton_style=4 underline_shortcut=1 wheel_scroll_lines=3 [PaletteEditor] geometry=@ByteArray(\x1\xd9\xd0\xcb\0\x3\0\0\0\0\x4\x15\0\0\x1\x11\0\0\x6\x8b\0\0\x3\x42\0\0\x4\x15\0\0\x1\x32\0\0\x6\x8b\0\0\x3\x42\0\0\0\0\0\0\0\0\a\x80\0\0\x4\x15\0\0\x1\x32\0\0\x6\x8b\0\0\x3\x42) [SettingsWindow] geometry=@ByteArray(\x1\xd9\xd0\xcb\0\x3\0\0\xff\xff\xff\xf5\xff\xff\xff\xcf\0\0\x2\xe9\0\0\x2p\0\0\0\0\0\0\0\0\0\0\x2\xde\0\0\x2\x65\0\0\0\0\0\0\0\0\n\0\0\0\0\0\0\0\0\0\0\0\x2\xde\0\0\x2\x65) [Troubleshooting] force_raster_widgets=1 ignored_applications=@Invalid() ``` And my system info: ``` # System Details Report --- ## Report details - **Date generated:** 2025-05-06 13:46:28 ## Hardware Information: - **Hardware Model:** Lenovo Lenovo Yoga C940-14IIL - **Memory:** 16.0 GiB - **Processor:** Intel® Core™ i7-1065G7 × 8 - **Graphics:** Intel® Iris® Plus Graphics (ICL GT2) - **Disk Capacity:** 1.0 TB ## Software Information: - **Firmware Version:** AUCN57WW - **OS Name:** Manjaro Linux - **OS Build:** rolling - **OS Type:** 64-bit - **GNOME Version:** 48 - **Windowing System:** Wayland - **Kernel Version:** Linux 6.6.87-1-MANJARO ``` If you think that this is not a problem with Backintime but rather with the Breeze theme, feel free to tell me where else I should report it. Edit: On a side note, this crash doesn't happen when I use the same theme (Breeze) on KDE. It seems to be specific to Gnome with the Breeze theme.

soundofthunder · 6 May 2025 15:28

A quick peek reveals that both backintime and backintime-qt (v1.5.4-1) are listed in all branches.

Branch compare: backintime

MajorMayer · 6 May 2025 21:30

I’m pretty sure that the backintime without the -qt suffix is just the CLI application/ library, without any GUI.
At least when uninstalling backintime-qt, I am not able to launch any GUI anymore.

soundofthunder · 7 May 2025 06:57

Maybe, maybe not. I only reported two distinct packages exist in the repositories. I don’t use it, so let’s leave the final confirmation to someone who is more than pretty sure.

Regards.

MajorMayer · 7 May 2025 08:40

It would be great if Manjaro/ Arch could backport/ cherry-pick the fix, once it is merged to the main/dev branch: Fix/2128qtbreeze by buhtz · Pull Request #2131 · bit-team/backintime · GitHub
One of their maintainers told me, that BIT doesn’t provide backports for their stable branches (at least they won’t backport this change to 1.5) and the package maintainers are responsible for that.

Maybe @Yochanan ?

buhtz · 7 May 2025 09:29

Upstream maintainer of Back In Time here.
Cause of the problem is found.

To Manjaro maintainers: Let me know if I can be of assistance somehow.

The upcoming release, after 1.5.4, will be 1.6.0. There is no strict schedule but I am assuming it will take some more weeks until we release it.

Yochanan · 8 May 2025 17:42

I can apply the PR as a patch ahead of 1.6.0 if @buhtz thinks that’s feasible.

system · 11 May 2025 17:42

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.