@fantu, yes: if I didn't anyhting wrong, I currently have the fix package from https://launchpad.net/~fantonifabio/+archive/ubuntu/ubuntu-fixes installed.
For your information: before your package, I had installed the fix package from https://launchpad.net/~bit-team/+archive/ubuntu/stable mentioned by @ventusfahrer above in this thread. Not sure what is the difference between these two packages but, as far as I can see, they apparently produce the same outcome: in both cases, backintime-qt only starts for root user if invoked using sudo from the command line, not from the .desktop launcher. For clarity, Here's the full story of my attempts so far: ATTEMPT 1 Eager to resume daily backups of my main home PC after the recent Ubuntu 22.04 fresh install: 1.1 I added https://launchpad.net/~bit-team/+archive/ubuntu/stable repository using the Ubuntu "Software and Updates" tool. As usual, repositories got updated when I hit the "Close" button. 1.2 Using the Synaptic tool, I "Completely remove"d backintime-qt, then I reinstalled it. 1.3 To test the fix, I clicked on the "Back In Time (root)" desktop launcher. Outcome: Backintime not launching. 1.4 In the command shell (Gnome Terminal), I issued commend "sudo backintime-qt". Outcome: Backintime launched normally. Sorry that it didn't occur to me to test non-root backintime, since I do not normally use it. Now, at least, I could access and use the Backintime's GUI as root again, almost as I did in Ubuntu 20.04, but only launching it from the command line. Not much satisfacory. But now I started getting a number of "WITH ERRORS" snapshots mixed with successful snapshots, which may or may not be related to the unofficial fix I had installed. Having no better options I decided to keep it, waiting for an official fix. ATTEMPT 2 Hoping that your fix is brings some progress, I decided to remove the one from bit-team and install this one. My steps: 2.1 sudo add-apt-repository ppa:fantonifabio/ubuntu-fixes 2.2 sudo apt update 2.3 In the "Software and Updates" tool I unticked https://launchpad.net/~bit-team/+archive/ubuntu/stable repository. As usual, repositories got updated when I hit Close button. 2.4 Using the Synaptic tool, I "Completely remove"d backintime-qt, then reinstalled it. If I'm not wrong, now the new fix has completely replaced the previous one. 2.5 To test the fix, I clicked on the "Back In Time" .desktop launcher (non-root user). Outcome: Backintime GUI launched normally 2.6 I clicked on the "Back In Time (root) .desktop launcher (root user). Outcome: Backintime not launching. 2.7 In the Gnome command shell I issued command: sudo backintime-qt. Outcome: Backintime GUI launched normally. Now, if I may, I wish to share one general consideration: it is good for the @ubuntu change acceptance procedures ("SRU"s?) to be accurate, strict and therefore slow, provided that this guarantees consistent, bug-free distribution packages. But if, for any reasons, the @ubuntu team cannot afford any more the resources to keep their commitment to high-quality standards, which seems to be the case with Ubuntu 22.04, I would expect that change acceptance procedures be also adapted consistently, so they do not come across and discourage the efforts by outside collaborators to remediate with the needed speed and agility. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970090 Title: Backintime not launching because of python error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/backintime/+bug/1970090/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
