Thanks for all details of your tests.
I did a very fast build for possible SRU of 1.3.2-0.1 in this another ppa: https://launchpad.net/~fantonifabio/+archive/ubuntu/ubuntu-fixes2
But don't have additional debian/patches so should be the same of upstream ppa (https://launchpad.net/~bit-team/+archive/ubuntu/stable) and I suppose you will have the same result launching as root from desktop icon.
From a very fast look on upstream (https://github.com/bit-team/backintime) commits after 1.3.2 and upstream PR I don't saw possible fix related to this.
I need to reproduce it when I'll create a Jammy vm to try to understand the cause, on my tests on debian unstable the start as root was working correctly.
The only thing that comes to my mind is recent pkexec split into a separate package but I didn't add in deps on my recent NMU on debian.
Can you check if you have pkexec package installed please? if not is the cause and I must add also its dep. in my SRU patch.
Thanks for all details of your tests. /launchpad. net/~fantonifab io/+archive/ ubuntu/ ubuntu- fixes2 /launchpad. net/~bit- team/+archive/ ubuntu/ stable) and I suppose you will have the same result launching as root from desktop icon. /github. com/bit- team/backintime) commits after 1.3.2 and upstream PR I don't saw possible fix related to this.
I did a very fast build for possible SRU of 1.3.2-0.1 in this another ppa: https:/
But don't have additional debian/patches so should be the same of upstream ppa (https:/
From a very fast look on upstream (https:/
I need to reproduce it when I'll create a Jammy vm to try to understand the cause, on my tests on debian unstable the start as root was working correctly.
The only thing that comes to my mind is recent pkexec split into a separate package but I didn't add in deps on my recent NMU on debian.
Can you check if you have pkexec package installed please? if not is the cause and I must add also its dep. in my SRU patch.