Created attachment 67184 [details] [review] improve MATE recognition 'xdg-su' plays a role in several components of openSUSE, being one of them YaST; the lack of support for MATE Desktop in xdg-su brings aditionals problems and neutralizes key features from YaST2 (as YasT2 itself). I believe this tiny patch might help; I leave to your review, and I'm willing to refactore it if it's not done in the proper way. thanks.
Why do you think either XDG_DESKTOP or DESKTOP_SESSION fallbacks are required? Does MATE_DESKTOP_SESSION_ID not get set properly in some circumstances?
Nevermind about XDG_CURRENT_DESKTOP, recognizing MATE there does indeed make sense, but I'm still curious about justifications for querying DESKTOP_SESSION
meh, I guess it doesn't hurt anything either :-/ committed, http://cgit.freedesktop.org/xdg/xdg-utils/commit/?id=8f92ae1b0c1253727873394cacfb42ab5ef26e02
(In reply to comment #3) > meh, I guess it doesn't hurt anything either :-/ > > committed, > http://cgit.freedesktop.org/xdg/xdg-utils/commit/?id=8f92ae1b0c1253727873394cacfb42ab5ef26e02 Rex, Actually this part of the patch does all the magic: diff --git a/scripts/xdg-su.in b/scripts/xdg-su.in index 6bd229a..6c5a124 100644 --- a/scripts/xdg-su.in +++ b/scripts/xdg-su.in @@ -155,7 +155,7 @@ case "$DE" in su_kde ;; - gnome*|lxde) + gnome*|lxde|mate) su_gnome ;; From my experience, if this isn't changed, then YaST will fail to find any valid handler and thus won't work (the password popup never comes); nmarques@mantis:~> /sbin/YaST2 xdg-su: no graphical method available for invoking '/sbin/yast2 sw_single' as 'root' By adding the patch above... then everything works; there's further impact; for example with keyring and NetworkManager accessing passwords. With this change I don't find more erratic behavior. Regarding your commit and my previous hack, I've tested it further in the last days and actilly only the part transcribed above works, so it's probably more cleaner. Thanks for this.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.