https://bugzilla.novell.com/show_bug.cgi?id=393955 User sh@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=393955#c3 Stefan Hundhammer <sh@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|sh@novell.com |jsrain@novell.com --- Comment #3 from Stefan Hundhammer <sh@novell.com> 2008-05-26 05:15:39 MDT --- (In reply to comment #1 from Bernhard Walle)
YaST people claim that every desktop environment has to implement
X-KDE-RootOnly=true
because KDE is the "standard". Or something like that. :)
No. That's a hint to KDE, as the name implies. If Xfce doesn't bother to honor that hint, that's bad for Xfce users. Looks like freedesktop.org doesn't have a standard way to handle such applications that require additional authentication?
Anyway, Stefan, maybe can you add
*I* am NOT going to change 87 .desktop files, add a change log to each corresponding pacakge, bump the version number, and then submit 80+ YaST2 packages (and then respond to an average of 20+ autobuild failures because of a completely unrelated previous change). Been there. Done that. Hated it. If anybody really wants or needs a change in all .desktop files (because of deficiencies in one window manager), all YaST2 package maintainers will have to do the change in their packages, add change logs etc. and submit the packages. -> jsrain (please evaluate if the result is worth the cost)
NotShowIn=XFCE; (note that the leading semicolon is mandatory)
to all YaST desktop files that should be called as root. Xfce users can call the YaST control center from Xfce settings panel which prompts for the root password.
AFAICS this is duplicating information. This will run out of sync quickly. IMHO it would be better to get an equivalent of X-KDE-RootOnly standardized by freedesktop.org or to add support for it (in one way or the other; other applications might be affected, too) to Xfce. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.