Critique on your examples using hwinfo about hwinfo

[wfeldt]

No, this does not require root. Can you send me an example where it matters? Run
hwinfo --gfxcard --log=foo.log. Both as root and as normal user. I'd like to have a look at these logs.

[daniel-mueller]

I can confirm that I have to run hwinfo with sudo on a recent installation of Leap 15.

ll /usr/sbin/ | grep hwinfo
-rwxr-xr-x 1 root root      38K 22. Apr 21:38 hwinfo

[wfeldt]

I'm using Leap 15.0 myself and it works as expected. Please provide the logs as described above,

[daniel-mueller]

Without sudo (no log file generated):

hwinfo --gfxcard --log=foo.txt
              
Das Programm 'hwinfo' ist verfügbar im Paket 'hwinfo', das auf ihrem System installiert ist.

Der absolute Pfad für 'hwinfo' ist '/usr/sbin/hwinfo', daher kann das Programm möglicherweise nur    von Benutzern mit Superuser-Rechten gestartet werden (z. B. root).

With sudo:
foo.txt

Any more I could provide?

[wfeldt]

Without sudo (no log file generated)

That's impossible. It must contain something. Is the directory writable?

Das Programm 'hwinfo' ist verfügbar im Paket 'hwinfo', ...

Where does this come from?

[daniel-mueller]

Here is what I am doing (/bin/bash this time):

On a sidenote: This is not the first time I encountered the message telling my about absolute path and permissions of an executable. So I guess it's not specific to hwinfo.

[wfeldt]

My suspicion is that there is some tool spinning out those weird 'helpful' messages but in effect
not executing hwinfo at all.

Could you try running it with full path, like /usr/sbin/hwinfo --gfxcard?

[wfeldt]

It's this command-not-found thing. If you find it as unhelpful as I, do:

sudo zypper rm command-not-found
sudo zypper al command-not-found

Or add /usr/sbin to your PATH environment variable.

[daniel-mueller]

Yes, seems like /usr/sbin is not in $PATH by default and zypper tries to help. Thank you!