Help>>System Info is partial info in non-Ubuntu distros.

[STrRedWolf]

If you're in another distro that locks things down, some info isn't presented. For instance, in Gentoo, lspci is not allowed for ordinary users. When you get some system info, you need to be root to run lspci, or else you get a "sh: lspci: command not found" where you ran Steam at the command line.

Here's the results.

Processor Information:

Vendor:  GenuineIntel

Speed: 2534 Mhz

2 logical processors

2 physical processors

HyperThreading:  Unsupported

FCMOV:  Supported

SSE2:  Supported

SSE3:  Supported

SSSE3:  Supported

SSE4a:  Unsupported

SSE41:  Supported

SSE42:  Unsupported

Network Information:

Network Speed:  

Operating System Version:

"Gentoo Base System release 2.1" (64 bit)

Kernel Name:  Linux

Kernel Version:  3.6.7-sandra

X Server vendor:  The X.Org Foundation

X Server release:  11301000

Video Card:

Driver:  NVIDIA Corporation GeForce GTX 260M/PCIe/SSE2

Driver Version:  3.3.0 NVIDIA 310.19

Desktop Color Depth: 24 bits per pixel

Monitor Refresh Rate: 60 Hz

VendorID:  0x10de

DeviceID:  0x618

Number of Monitors:  1

Number of Video Cards Not Detected

Primary Display Resolution:  1920 x 1080

Desktop Resolution: 1920 x 1080

Primary Display Size: 13.54" x 7.60"  (15.51" diag)

                                        34.4cm x 19.3cm  (39.4cm diag)

Primary Bus: PCI Express 16x

Primary VRAM: 1024 MB

Supported MSAA Modes:  2x 4x 8x 16x 

Sound card:

Audio device: 

Memory:

RAM:  3953 Mb

Miscellaneous:

UI Language:  English

LANG:  en_US.UTF-8

Microphone:  Not set

Total Hard Disk Space Available:  179502 Mb

Largest Free Hard Disk Block:  23044 Mb

Installed software:

Recent Failure Reports:

[MrSchism]

I'd honestly like to see an implementation that allows for policies on flags beyond the basics. That way on systems like gentoo, a regular user could lspci but not something like "lspci -qq".

[ancow]

@MrSchism sudo allows something like that. (You can allow "lspci" to be executed as root without password but not when it's passed any flags.)

[MrSchism]

Sudo is a whole separate thing that I've never dug too much... but I've never noticed that sort of feature.

[eliasp]

That's actually not a permission issue on Gentoo, but rather a $PATH issue. The log output says

sh: lspci: command not found

but nothing about not having permissions.

The reason for this happening is: only root has /sbin and /usr/sbin in its $PATH, while a regular user doesn't. It is still executable for everyone:

-rwxr-xr-x 1 root root 69648 27. Sep 15:30 /usr/sbin/lspci*

So the simple fix here would be to fall back to /usr/sbin/lspci when simply executing lspci doesn't succeed.

[eliasp]

According to https://www.archlinux.org/packages/core/x86_64/pciutils/ Arch Linux might also be affected by this bug and the solution I proposed in the previous comment would solve it there, too.