Basically to get root graphics working, I had to add in several more tests and case handlers.
Not all systems support running glxinfo as root, and I've actually never once tried running inxi itself with sudo, the thought literally never crossed my mind. however, with that said, I tried it, and got this: :: Code :: sudo inxi -Gxxx
[sudo] password for me: Graphics: Card: NVIDIA GT218 [GeForce 210] bus-ID: 02:00.0 chip-ID: 10de:0a65 Display Server: X.Org 1.19.0 driver: nvidia Resolution: 1280x1024@60.02hz, 1280x1024@60.02hz GLX Renderer: GeForce 210/PCIe/SSE2/3DNOW! GLX Version: 3.3.0 NVIDIA 340.102 Direct Rendering: Yes so you can see for yourself what happens by simply running glxinfo as root, or with sudo, which should be the same thing. Now inxi is more dynamic, and determines if the system isn't going to work with glxinfo as root, then assigns the proper values for output, and grabs the terminal size, so it appears that it's all working as expected. Now, why debian based ubuntu is not allowing glxinfo to be run as root is beyond me to explain, unless it's something related to wayland and xwayland? anyway, since the original behavior was hard coded root test to show no root support output, and since that behavior is now assigned based on the data returned, there's actually no change in that with your system. I think this is what you're asking anyway, so yes, in your case, root and user show different output. In my case, they show the same. Back to top |
Actually, looking at your -F, the -S line isn't handling the root null data case, that should actually be also switching back to the previous form, showing console info instead of desktop. I forgot to handle that since it's slightly awkward to test for now, the old absolute if root case was obviously logically much more simple.
Back to top |
The failure to fallback correctly in -S line to "Console: tty 1" when no gfx based desktop data available should now be corrected in 2.3.21, I had just forgotten that case. As noted, it was a lot easier to simply make all the graphics based stuff work only in x and as non root, now it's working out of x and or as root. Note that in no case that I have found does it work out of x and as root.
in your case, for example, no gfx stuff is working in x as root, in my case, it works fine as regular user or root in x, and also out of x as regular user, with the -! 40 option. However, intel drivers do not appear to support the out of x option at all, they simply hang on output, I still have not verified if that is all free x drivers, or just intel. Back to top |
New output from -Gxx
:: Code :: corrado@corrado-artful:~$ cd Documents
corrado@corrado-artful:~/Documents$ ls out inxi corrado@corrado-artful:~/Documents$ ./inxi -GxxI Graphics: Card: Intel 4th Generation Core Processor Family Integrated Graphics Controller bus-ID: 00:02.0 chip-ID: 8086:041e Display Server: wayland (X.Org 1.19.3) drivers: modesetting (unloaded: fbdev,vesa) Resolution: 1680x1050@59.85hz GLX Renderer: Mesa DRI Intel Haswell GLX Version: 4.5 Mesa 17.1.2 (compat-v: 3.0) Direct Rendering: Yes Info: Processes: 217 Uptime: 1:28 Memory: 1153.8/7861.1MB Init: systemd v: 233 runlevel: 5 Gcc sys: N/A Client: Shell (bash 4.4.121 running in gnome-terminal-) inxi: 2.3.21 corrado@corrado-artful:~/Documents$ sudo ./inxi -GxxI [sudo] password for corrado: Graphics: Card: Intel 4th Generation Core Processor Family Integrated Graphics Controller bus-ID: 00:02.0 chip-ID: 8086:041e Display Server: X.org 1.19.3 drivers: modesetting (unloaded: fbdev,vesa) tty size: 111x27 Advanced Data: N/A for root Info: Processes: 218 Uptime: 1:28 Memory: 1155.3/7861.1MB Init: systemd v: 233 runlevel: 5 Gcc sys: N/A Client: Shell (sudo running in bash) inxi: 2.3.21 corrado@corrado-artful:~/Documents$ Back to top |
From a different hardware:
:: Code :: corrado@corrado-HP-artful:~$ cd Documents
corrado@corrado-HP-artful:~/Documents$ ls inxi out corrado@corrado-HP-artful:~/Documents$ ./inxi -GxxI Graphics: Card: Intel Haswell-ULT Integrated Graphics Controller bus-ID: 00:02.0 chip-ID: 8086:0a16 Display Server: wayland (X.Org 1.19.3) drivers: modesetting (unloaded: fbdev,vesa) Resolution: 1366x768@59.80hz GLX Renderer: Mesa DRI Intel Haswell Mobile GLX Version: 4.5 Mesa 17.1.2 (compat-v: 3.0) Direct Rendering: Yes Info: Processes: 199 Uptime: 15 min Memory: 849.4/3881.2MB Init: systemd v: 233 runlevel: 5 Gcc sys: N/A Client: Shell (bash 4.4.121 running in gnome-terminal-) inxi: 2.3.21 corrado@corrado-HP-artful:~/Documents$ Back to top |
|
so running on Ubuntu Gnome NO wayland the output does not chanhe using sudo:
:: Code :: corrado@corrado-artful:~$ cd Documents
corrado@corrado-artful:~/Documents$ ./inxi -GxxI Graphics: Card: Intel 4th Generation Core Processor Family Integrated Graphics Controller bus-ID: 00:02.0 chip-ID: 8086:041e Display Server: x11 (X.Org 1.19.3) drivers: modesetting (unloaded: fbdev,vesa) Resolution: 1680x1050@59.88hz GLX Renderer: Mesa DRI Intel Haswell GLX Version: 4.5 Mesa 17.1.2 (compat-v: 3.0) Direct Rendering: Yes Info: Processes: 218 Uptime: 1 min Memory: 628.8/7861.1MB Init: systemd v: 233 runlevel: 5 Gcc sys: N/A Client: Shell (bash 4.4.121 running in gnome-terminal-) inxi: 2.3.21 corrado@corrado-artful:~/Documents$ sudo ./inxi -GxxI [sudo] password for corrado: Graphics: Card: Intel 4th Generation Core Processor Family Integrated Graphics Controller bus-ID: 00:02.0 chip-ID: 8086:041e Display Server: X.Org 1.19.3 drivers: modesetting (unloaded: fbdev,vesa) Resolution: 1680x1050@59.88hz GLX Renderer: Mesa DRI Intel Haswell GLX Version: 4.5 Mesa 17.1.2 (compat-v: 3.0) Direct Rendering: Yes Info: Processes: 219 Uptime: 2 min Memory: 629.5/7861.1MB Init: systemd v: 233 runlevel: 5 Gcc sys: N/A Client: Shell (sudo running in bash) inxi: 2.3.21 corrado@corrado-artful:~/Documents$ sudo ./inxi -Fx System: Host: corrado-artful Kernel: 4.11.0-6-generic x86_64 (64 bit gcc: 6.3.0) Console: tty 0 Distro: Ubuntu Artful Aardvark (development branch) Machine: Device: desktop Mobo: Gigabyte model: H87M-D3H v: x.x UEFI: American Megatrends v: F3 date: 04/24/2013 CPU: Dual core Intel Core i3-4130 (-HT-MCP-) cache: 3072 KB flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 13568 clock speeds: max: 3400 MHz 1: 970 MHz 2: 887 MHz 3: 860 MHz 4: 816 MHz Graphics: Card: Intel 4th Generation Core Processor Family Integrated Graphics Controller bus-ID: 00:02.0 Display Server: X.Org 1.19.3 drivers: modesetting (unloaded: fbdev,vesa) Resolution: 1680x1050@59.88hz GLX Renderer: Mesa DRI Intel Haswell GLX Version: 4.5 Mesa 17.1.2 Direct Rendering: Yes Audio: Card-1 Intel 8 Series/C220 Series High Definition Audio Controller driver: snd_hda_intel bus-ID: 00:1b.0 Card-2 Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller driver: snd_hda_intel bus-ID: 00:03.0 Sound: Advanced Linux Sound Architecture v: k4.11.0-6-generic Network: Card: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller driver: r8169 v: 2.3LK-NAPI port: e000 bus-ID: 02:00.0 IF: enp2s0 state: up speed: 100 Mbps duplex: full mac: 94:de:80:7e:90:a7 Drives: HDD Total Size: 1000.2GB (1.5% used) ID-1: /dev/sda model: ST1000DM003 size: 1000.2GB temp: 35C Partition: ID-1: / size: 32G used: 6.3G (22%) fs: ext4 dev: /dev/sda6 ID-2: swap-1 size: 8.59GB used: 0.00GB (0%) fs: swap dev: /dev/sda2 RAID: No RAID devices: /proc/mdstat, md_mod kernel module present Sensors: System Temperatures: cpu: 29.8C mobo: 27.8C Fan Speeds (in rpm): cpu: N/A Info: Processes: 220 Uptime: 3 min Memory: 631.8/7861.1MB Init: systemd runlevel: 5 Gcc sys: N/A Client: Shell (sudo) inxi: 2.3.21 corrado@corrado-artful:~/Documents$ ./inxi -Fx System: Host: corrado-artful Kernel: 4.11.0-6-generic x86_64 (64 bit gcc: 6.3.0) Desktop: Gnome 3.24.2 (Gtk 3.22.15-0ubuntu2) Distro: Ubuntu Artful Aardvark (development branch) Machine: Device: desktop Mobo: Gigabyte model: H87M-D3H v: x.x UEFI: American Megatrends v: F3 date: 04/24/2013 CPU: Dual core Intel Core i3-4130 (-HT-MCP-) cache: 3072 KB flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 13568 clock speeds: max: 3400 MHz 1: 3400 MHz 2: 2145 MHz 3: 2165 MHz 4: 2327 MHz Graphics: Card: Intel 4th Generation Core Processor Family Integrated Graphics Controller bus-ID: 00:02.0 Display Server: x11 (X.Org 1.19.3) drivers: modesetting (unloaded: fbdev,vesa) Resolution: 1680x1050@59.88hz GLX Renderer: Mesa DRI Intel Haswell GLX Version: 4.5 Mesa 17.1.2 Direct Rendering: Yes Audio: Card-1 Intel 8 Series/C220 Series High Definition Audio Controller driver: snd_hda_intel bus-ID: 00:1b.0 Card-2 Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller driver: snd_hda_intel bus-ID: 00:03.0 Sound: Advanced Linux Sound Architecture v: k4.11.0-6-generic Network: Card: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller driver: r8169 v: 2.3LK-NAPI port: e000 bus-ID: 02:00.0 IF: enp2s0 state: up speed: 100 Mbps duplex: full mac: 94:de:80:7e:90:a7 Drives: HDD Total Size: 1000.2GB (1.5% used) ID-1: /dev/sda model: ST1000DM003 size: 1000.2GB temp: 35C Partition: ID-1: / size: 32G used: 6.3G (22%) fs: ext4 dev: /dev/sda6 ID-2: swap-1 size: 8.59GB used: 0.00GB (0%) fs: swap dev: /dev/sda2 RAID: No RAID devices: /proc/mdstat, md_mod kernel module present Sensors: System Temperatures: cpu: 29.8C mobo: 27.8C Fan Speeds (in rpm): cpu: N/A Info: Processes: 219 Uptime: 3 min Memory: 630.7/7861.1MB Init: systemd runlevel: 5 Gcc sys: N/A Client: Shell (bash 4.4.121) inxi: 2.3.21 corrado@corrado-artful:~/Documents$ Back to top |
looks like it's all working now. Clearly given the wide range of possible output results with root in and out of x etc, the only way to handle this type of display was full dynamic testing of results to determine what would show an dhow.
There's clearly going to be more wayland differences, and how various distributions decide to handle wayland and xorg together is also going to impact everything, for example, on a pure wayland system, without xwayland etc, glxinfo, xprop, and xdpyinfo will probably not be available, depending on the decisions made by packagers and compositors etc. I note as well that my initial guess at raw compositor is not working for gnome, but I didn't expect that stuff to work without a lot more datasets from confirmed compositor running systems, something I still have little to know idea how to actually detect. that is, say, how does one determine if xfce4 is running with or without a compositor? or kde? or gnome? and given in wayland systems, they are by definition running with one, that's another point, which is why I made compositor output only work in theory for wayland systems, though your example shows the theory not working. Back to top |
bug: bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1701822 will change wayland dependecies:
:: Code ::
This bug was fixed in the package gnome-session - 3.24.1-0ubuntu8 --------------- gnome-session (3.24.1-0ubuntu8) artful; urgency=medium * Change ubuntu-session to Arch: any for new xwayland dependency gnome-session (3.24.1-0ubuntu7) artful; urgency=medium * debian/control.in: - Have ubuntu-session depend on xwayland like gnome-session does Thanks corrado for the report! (LP: #1701822) - Have ubuntu-session and gnome-session depend on gnome-shell. Now that gnome-shell recommends instead of depends on gnome-session | ubuntu-session, there is no circular dependency so let's not diverge from Debian. -- Jeremy Bicha <jbicha@ubuntu.com> Sat, 01 Jul 2017 14:35:17 -0400 Changed in gnome-session (Ubuntu): status: Fix Committed → Fix Released Back to top |
I can't see any connection with inxi here, that's just a bug in ubuntu.
Back to top |
All times are GMT - 8 Hours |