[SRU] Backintime in Jammy not launching because of error with python 3.10

Bug #1976164 reported by Fantu
48
This bug affects 8 people
Affects Status Importance Assigned to Milestone
backintime (Ubuntu)
Fix Released
Undecided
Unassigned
Jammy
Fix Released
High
Unassigned

Bug Description

[Impact]
Backintime don't start, this is caused by an error with python 3.10 that make it crash on start.

Applied only the specific commit from upstream that fix it to have it uploaded and accepted as soon as possible (in theory), patch attached here.
The ppa with the testing build: https://launchpad.net/~fantonifabio/+archive/ubuntu/ubuntu-fixes

[Test Plan]
Simply start backintime from desktop icon or cli

[Where problems could occur]
FWIK the issue happen always trying to start backintime

Revision history for this message
Fantu (fantonifabio) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in backintime (Ubuntu):
status: New → Confirmed
Revision history for this message
Brian Murray (brian-murray) wrote :

I went ahead and sponsored this after applying the patch and running update-maintainer. Thanks for the fix!

Changed in backintime (Ubuntu Jammy):
status: New → In Progress
importance: Undecided → High
Revision history for this message
Steve Langasek (vorlon) wrote : Please test proposed package

Hello Fantu, or anyone else affected,

Accepted backintime into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/backintime/1.2.1-3ubuntu0.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-jammy. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Changed in backintime (Ubuntu Jammy):
status: In Progress → Fix Committed
tags: added: verification-needed verification-needed-jammy
Revision history for this message
arend (arend-bayer) wrote :

This update fixed the bug for me.
Testing done: Upgraded to backintime-common and backintime-qt on kubuntu jammy system (all upgrades, no other packages from -proposed) to the jammy-proposed version today: 1.2.1-3ubuntu0.1' (Ubuntu:22.04/jammy-proposed [all] )

After the upgrade, I was able to start backintime both from cli and KDE startup menu. (Previously, it crashed immediately.) Let me know if you need more information.

Fantu (fantonifabio)
tags: added: verification-done verification-done-jammy
removed: verification-needed verification-needed-jammy
Revision history for this message
Ganton (ganton) wrote :

If it may be helpful: Previously, I executed `backintime` and it showed:
    Traceback (most recent call last):
        File "/usr/share/backintime/common/backintime.py", line 27, in <module>
            import config
        File "/usr/share/backintime/common/config.py", line 32, in <module>
            import tools
        File "/usr/share/backintime/common/tools.py", line 1802, in <module>
            class OrderedSet(collections.MutableSet):
    AttributeError: module 'collections' has no attribute 'MutableSet'

I executed
    $ dpkg -l | grep backi
    ii backintime-common 1.2.1-3 all simple backup/snapshot system (common files)
    ii backintime-qt 1.2.1-3 all simple backup/snapshot system (graphical interface)

I went to https://launchpad.net/ubuntu/jammy/amd64/backintime-common/1.2.1-3ubuntu0.1 , downloaded http://launchpadlibrarian.net/606412102/backintime-common_1.2.1-3ubuntu0.1_all.deb and executed:
    sudo apt install ./backintime-common_1.2.1-3ubuntu0.1_all.deb

I went to https://launchpad.net/ubuntu/jammy/amd64/backintime-qt/1.2.1-3ubuntu0.1, , downloaded http://launchpadlibrarian.net/606412105/backintime-qt_1.2.1-3ubuntu0.1_all.deb and executed:
    sudo apt install ./backintime-qt_1.2.1-3ubuntu0.1_all.deb

I executed:
    $ dpkg -l | grep backi
    ii backintime-common 1.2.1-3ubuntu0.1 all simple backup/snapshot system (common files)
    ii backintime-qt 1.2.1-3ubuntu0.1 all simple backup/snapshot system (graphical interface)

I executed `backintime` and everything seemed to work correctly.

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package backintime - 1.2.1-3ubuntu0.1

---------------
backintime (1.2.1-3ubuntu0.1) jammy; urgency=medium

  * Make tests compatible with python 3.10 to avoid crash on application
    start. (LP: #1976164)

 -- Fabio Fantoni <email address hidden> Tue, 24 May 2022 22:58:51 +0200

Changed in backintime (Ubuntu Jammy):
status: Fix Committed → Fix Released
Revision history for this message
Brian Murray (brian-murray) wrote : Update Released

The verification of the Stable Release Update for backintime has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

Fantu (fantonifabio)
Changed in backintime (Ubuntu):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.