On 11/25/19 7:28 PM, David Díaz wrote:
Hi there!
Today, while I was working to fix an issue when executing "yast2 system_settings" without enough permissions[1][2], some questions arose to my mind. Let me share them,
* If I run "/usr/sbin/yast2" it warns about the permissions and only shows a few modules[3]. So, * Can we manage [1] and [2] in a "centralized" way? I mean, do we have a way to know in advance when the execution of a certain module will require root permissions? If the answer is NO, * Can we open a discussion/research/whatever to do something to this regard? Do you think it worth it? Or do you already had such discussions in the past? If so, what was the conclusion?
Apart from these questions, a little bit off-topic but also related to the topic, I found weird that "yast2 storage" prompt a warning[4] saying
> The storage subsystem is locked by an unknown application. > You must quit that application before you can continue. > > Would you like to abort or try again?
when it is executed as a normal user. Actually is a problem with permissions, not an "unknown application locking the storage subsystem".
Regarding the storage message, I agree, it could be misleading. Basically, that message is shown when the lock file cannot be open (because it is already open or because whatever any other reason, e.g., lacking of permissions). Maybe we should distinguish the case and inform the user properly. I think it deserves a bug entry in bugzilla ;)
Waiting for your inputs, thanks in advance.
See you.
[1] https://github.com/yast/yast-tune/pull/40
[2] https://github.com/yast/yast-bootloader/pull/583
[3] https://gist.github.com/dgdavid/323e5aa879490e24ea2d0d520550e1fe#gistcomment...
[4] https://gist.github.com/dgdavid/323e5aa879490e24ea2d0d520550e1fe#gistcomment...
-- José Iván López González YaST Team at SUSE LINUX GmbH IRC: jilopez -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org