The change of the mode of debian/source_sudo.py was unintentional (I used the git checkout from Debian to put the changes on top). I reuploaded the jammy SRU without the mode change of debian/source_sudo.py.
> Is there any possibility that passing through this environment variable when we previously did not will change behaviour in such a way that a user treats that as a regression? For example, if some user has a setting that causes some app to now break, when it didn't before?
XDG_CURRENT_DESKTOP is probably only taken into account by UI applications. If setting this variable causes a code path change and a regression for this one, the same regression should be triggered by running the application without sudo.
If the user blocked passing environment variables like DISPLAY, setting only XDG_CURRENT_DESKTOP did not made UI applications start (tested with: sudo env -i XDG_CURRENT_DESKTOP=$XDG_CURRENT_DESKTOP gnome-calculator)
The change of the mode of debian/ source_ sudo.py was unintentional (I used the git checkout from Debian to put the changes on top). I reuploaded the jammy SRU without the mode change of debian/ source_ sudo.py.
> Is there any possibility that passing through this environment variable when we previously did not will change behaviour in such a way that a user treats that as a regression? For example, if some user has a setting that causes some app to now break, when it didn't before?
XDG_CURRENT_DESKTOP is probably only taken into account by UI applications. If setting this variable causes a code path change and a regression for this one, the same regression should be triggered by running the application without sudo.
If the user blocked passing environment variables like DISPLAY, setting only XDG_CURRENT_DESKTOP did not made UI applications start (tested with: sudo env -i XDG_CURRENT_ DESKTOP= $XDG_CURRENT_ DESKTOP gnome-calculator)