Back In Time (Qt) crashes on Gnome Wayland

Support Software & Applications
,
1

Hi everybody,
I just tried to run Back In Time with its Qt frontend on my Manjaro Unstable notebook with Gnome Wayland DE.
While at first everything looks decent and this dialog occurs, asking me if i want to import an existing profile (which i don’t have), as soon as i press “Nein” the application crashes with the following error:

grafik
grafik1044×432 56.4 KB

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.

The cached device pixel ratio value was stale on window update.  Please file a QTBUG which explains how to reproduce.
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 am not quite sure what’s going on here, but I can tell that it works on my KDE Wayland Desktop PC that is also using Manjaro Wayland.
Interestingly, it opens successfully if I start it as root.

Do you think this is an upstream issue or is something wrong with my configuration?
I am using the QAdwaitaDecorations and the Breeze theme if that makes any difference.

System Details Report

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.85-1-MANJARO
2

How did you do that?
… to specifically run the QT frontend …?

I ask because I just installed from AUR “backintime”

On a Gnome DE fully updated system.

In a VM - so it is not running Wayland - it is running x11/xorg

and I don’t get that response.

I do get:

backintime

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.

WARNING: Failed to connect to Udev serviceHelper daemon via D-Bus: org.freedesktop.DBus.Error.ServiceUnknown
WARNING: D-Bus message: The name is not activatable
WARNING: Udev-based profiles cannot be changed or checked due to Udev serviceHelper connection failure

but this is on Manjaro stable - not unstable like yours

same result if I start it as root

1 Like
3

I installed backintime from the extra repo, not from the AUR.
Then I just entered backintime-qt in the terminal and the crash happend.

When I only execute backintime, no error message is shown, but also no window opens:

backintime                                                       ✔ 

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.

Should backintime without the -qt suffix open a different type of frontend? Maybe a GTK based one?

4

I have no explanation.
I can’t get it to start either.

It asks for something that isn’t there - or isn’t be supplied - and it just crashes …

5

Okay, thanks for your confirmation.
It’s good to know that I’m not the only one with this issue, at least.

6

@MajorMayer

I wonder if this is a problem specific to gnome.
It works fine in Cinnamon and works steadily every hour.
Wayland?

7

I guess so.
As mentioned before, I use BackInTime also on KDE where I never had such issues.
And yes, I am on Wayland.

Edit: I just tried opening it under X11, but it seems like my Gnome X11 session is pretty much broken. I wasn’t even able to open a terminal there…