thanks for testing, after point 2 have you also installed the updated package, right? I tested 1.3.2-0.1 on debian unstable before upload on it and was working also as root, I suppose related to one of other fixes (but I not checked in code changed now if there are changes related to it), as wrote better porting it to Jammy but difficult that will be accepted. Probably I prepare a fast build on another ppa with it if someone want test.
@ubuntu developers: can you take a look to this and tell if 1.3.2-0.1 (with some other fixes and some tests done in debian unstable near to jammy release) will be accepted or someone else want invest enough time on an SRU that will be uploaded/accepted shortly instead me. I don't use Jammy in production for now, I use backintime in production on Focal and I used in Bionic, this is why I invested some time after saw the blocking bug in debian unstable and no activity from maintainers for months. Unfortunately I saw that it is difficult and takes a long time SRU procedure in ubuntu, when I had spent enough time and waited months for example even for just a small nemo crash fixes that I had already tested extensively and used a lot in production. For this reason I am a bit reluctant to start something that would take me a long time for small results after a long time. if there will be no one with the possibility of having a good SRU uploaded and accepted quickly, I will try to do myself anyway hoping not to waste too much time and that after having tested well it will be accepted within a few weeks. -- 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
