|
I'm using Gnome wayland but inxi says: Display Server: X.Org
I'm using Ubuntu 17.10 GNOME with Wayland but inxi says: Display Server: X.Org 1.19.3 driver: N/A
I was expecting 'wayland' so i don't understand. May You help me? Thanks :: Code :: corrado@corrado-art-gnome:~$ echo $XDG_SESSION_TYPE
wayland corrado@corrado-art-gnome:~$ inxi -Fx System: Host: corrado-art-gnome Kernel: 4.10.0-22-generic x86_64 (64 bit gcc: 6.3.0) Desktop: Gnome 3.24.2 (Gtk 3.22.15-0ubuntu1) 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: 3400 MHz 3: 3400 MHz 4: 3400 MHz Graphics: Card: Intel 4th Generation Core Processor Family Integrated Graphics Controller bus-ID: 00:02.0 Display Server: X.Org 1.19.3 driver: N/A Resolution: 1680x1050@59.85hz GLX Renderer: Mesa DRI Intel Haswell GLX Version: 3.0 Mesa 17.1.0 Direct Rendering: Yes Back to top |
|
inxi does not have wayland support yet, and in fact, while you may believe you're using pure wayland, you're almost certainly using the x compatibility version, which is why you see the display server info. I actually changed the 'display server' string a while back to prepare inxi for having alternate display servers, not just Xorg, but I never got any further than that.
I would have added wayland support ages ago but the people who do the test isos for it never had support for wayland in a vm, so I didn't do it. I still don't have anything that runs wayland, nor do I Have a single bit of data or information about how to get data from wayland, zero, zip. Since for something as complicated as supporting a new display server, I have to have the ability to test it locally, I'm still waiting for a virtual box installable iso from anyone out there. And to make it harder, almost all the implementations of wayland I've seen so far, actually use xorg hooks, which means inxi can get most of the data in those xorg/wayland hybrid systems. In your case, for example, there's only one piece of data missing even though inxi has no actual wayland support. The things I'm missing are: 1. commands to get information from wayland 2. samples of that information, so I know how inxi should parse it 3. tests to determine without doubt the actual server running the display 4. debugger data collectors in inxi to create that information for my use re user debugger data sets. This is critical, it's a chicken and egg thing, I can't add debugger data collectors without knowing the commands to get that data, or the things to test for, etc. 5. sufficient user sample data sets that contain this information for me to see the range of variants in user systems. I was aware that there were finally some wayland / weston things shipping, but I have personally not seen it, nor do I have access to anything that runs it, nor would I convert any of my systems to use it, which is why I have to have vm support to add support for wayland. Note that almost all, if not all, implementations of wayland that I'm aware of actually use the x server hooks, which is why you're seeing resolution and glx information in the first place. I was actually waiting to see what would happen to mir before deciding what to do re support for alternate display servers, but then ubuntu was nice enough to kill off mir, which from my point of view was fantastic, since that reduced the number to 1 new display server to add support for, which I'm quite pleased about. but I have still to this point exactly zero idea or knowledge about how to get information from wayland systems. Every 6-12 months I've checked out the latest wayland iso, and each time it fails to install on a vm. Once I have one running in a vm, I can start testing support, and once people tell me the full suite of reporting tools, and how they are implemented, for example, am I going to have to deal with a separate syntax and toolset for the gnome and kde implementations of wayland? or is there going to be one core one? all this is unknown to me, and I have never seen anything online that actually deals with actual technical questions like this. Back to top |
|
I have an Ubuntu 17.10 Gnome with a wayland session. I use 'echo $XDG_SESSION_TYPE' to check if i'm using it.
let me know if I can give you more info. thanks Back to top |
|
Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 (20170531) with wayland runs smoothly in virtuabox
:: Code :: corrado@corrado-VirtualBox:~$ echo $XDG_SESSION_TYPE
wayland corrado@corrado-VirtualBox:~$ inxi -Fx System: Host: corrado-VirtualBox Kernel: 4.10.0-21-generic x86_64 (64 bit gcc: 6.3.0) Desktop: Gnome 3.24.2 (Gtk 3.22.15-0ubuntu1) Distro: Ubuntu Artful Aardvark (development branch) Machine: Device: oracle System: innotek product: VirtualBox v: 1.2 Mobo: Oracle model: VirtualBox v: 1.2 BIOS: innotek v: VirtualBox date: 12/01/2006 CPU: Single core Intel Core i3-4130 (-UP-) cache: 3072 KB flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3) bmips: 6784 speed: 3392 MHz (max) Graphics: Card: InnoTek Systemberatung VirtualBox Graphics Adapter bus-ID: 00:02.0 Display Server: X.Org 1.19.3 driver: N/A Resolution: 1408x903@59.95hz GLX Renderer: Gallium 0.4 on llvmpipe (LLVM 4.0, 256 bits) GLX Version: 3.0 Mesa 17.1.0 Direct Rendering: Yes Audio: Card Intel 82801AA AC'97 Audio Controller driver: snd_intel8x0 ports: d100 d200 bus-ID: 00:05.0 Sound: Advanced Linux Sound Architecture v: k4.10.0-21-generic Network: Card: Intel 82540EM Gigabit Ethernet Controller driver: e1000 v: 7.3.21-k8-NAPI port: d010 bus-ID: 00:03.0 IF: enp0s3 state: up speed: 1000 Mbps duplex: full mac: 08:00:27:37:7f:5c Drives: HDD Total Size: 10.7GB (39.1% used) ID-1: /dev/sda model: VBOX_HARDDISK size: 10.7GB Partition: ID-1: / size: 9.8G used: 4.0G (43%) fs: ext4 dev: /dev/sda1 RAID: No RAID devices: /proc/mdstat, md_mod kernel module present Sensors: None detected - is lm-sensors installed and configured? Info: Processes: 198 Uptime: 35 min Memory: 897.7/3006.0MB Init: systemd runlevel: 5 Gcc sys: N/A Client: Shell (bash 4.4.121) inxi: 2.3.8 corrado@corrado-VirtualBox:~$ Back to top |
|
Well, this is a good start, I didn't even realize that:
:: Code :: echo $XDG_SESSION_TYPE
x11 exists, so that's a great beginning, for sure. Now I need to see what queries I can do to a wayland implementation re what data it can give me, x has tons of tools, most of which run with the wayland/xorg mix most wayland systems currently run, but the question is, what does wayland itself give, is the gnome version different from the kde or whatever else comes down the way versions, re commands to get data? and data structure, and so on. Back to top |
|
I have found also other debugging commands here: fedoraproject.org/wiki/How_to_debug_Wayland_problems
Back to top |
|
2.3.12 has basic attempt at wayland support.
There's also a new option, -xx, which is experimental effort to have compositor support. this is very unlikely to actually work as expected, or right, but it's a starting place, which is why I made it an -xx option. the output has changed slightly: Display Server x11 (X.Org 1.19.0) driver nvidia Note that there is no way I know of to detect out of the desktop, in console, wayland, so that remains, it will just look for xorg, and print the version information it finds there. Also, there is no support for pure wayland features, since as far as I know, none exist. Further, because the incredible mess that all the different compositors out there will create, for absolute certain, the odds are very low that a pure wayland system will ever return meaningful data that inxi uses, like screen resolution, the xprop stuff which is used to get desktop type, and in some systems, all the stuff that depends on the XDG_ environmental variables will also fail. But I had to start wayland support somewhere, and hopefully buggy inxi output will motivate bug reporters to find ways to detect the information. Also added to inxi was beginning wayland data grabbers, very raw and basic. Back to top |
|
inxi 2.3.18 works fine with wayland! thanks a lot!
:: Code :: corrado@corrado-HP-artful:~/Documents$ ./inxi -Fx
System: Host: corrado-HP-artful Kernel: 4.11.0-5-generic x86_64 (64 bit gcc: 6.3.0) Desktop: Gnome 3.24.2 (Gtk 2.24.31) Distro: Ubuntu Artful Aardvark (development branch) Machine: Device: laptop System: Hewlett-Packard product: HP 250 G3 Notebook PC v: 0991100000000000000600087 Mobo: Hewlett-Packard model: 2211 v: 86.49 UEFI: Insyde v: F.36 date: 12/18/2014 Battery BAT1: charge: 13.1 Wh 62.6% condition: 20.9/21.7 Wh (96%) model: 13-42 OA03031 status: Discharging CPU: Dual core Intel Core i5-4210U (-HT-MCP-) cache: 3072 KB flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 9578 clock speeds: max: 2700 MHz 1: 799 MHz 2: 799 MHz 3: 799 MHz 4: 807 MHz Graphics: Card: Intel Haswell-ULT Integrated Graphics Controller bus-ID: 00:02.0 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 Direct Rendering: Yes Audio: Card-1 Intel 8 Series HD Audio Controller driver: snd_hda_intel bus-ID: 00:1b.0 Card-2 Intel Haswell-ULT HD Audio Controller driver: snd_hda_intel bus-ID: 00:03.0 Sound: Advanced Linux Sound Architecture v: k4.11.0-5-generic Network: Card-1: Realtek RTL8101/2/6E PCI Express Fast/Gigabit Ethernet controller driver: r8169 v: 2.3LK-NAPI port: 3000 bus-ID: 08:00.0 IF: enp8s0 state: down mac: 5c:b9:01:06:ba:ce Card-2: Ralink RT3290 Wireless 802.11n 1T/1R PCIe driver: rt2800pci v: 2.3.0 bus-ID: 09:00.0 IF: wlo1 state: down mac: de:2f:66:f0:b8:51 Drives: HDD Total Size: 500.1GB (2.4% used) ID-1: /dev/sda model: ST500LT012 size: 500.1GB Partition: ID-1: / size: 32G used: 7.5G (26%) fs: ext4 dev: /dev/sda6 ID-2: swap-1 size: 4.29GB used: 0.00GB (0%) fs: swap dev: /dev/sda2 RAID: No RAID devices: /proc/mdstat, md_mod kernel module present Sensors: System Temperatures: cpu: 39.0C mobo: 39.0C Fan Speeds (in rpm): cpu: N/A Info: Processes: 190 Uptime: 5 min Memory: 659.3/3881.2MB Init: systemd runlevel: 5 Gcc sys: 6.3.0 Client: Shell (bash 4.4.121) inxi: 2.3.18 corrado@corrado-HP-artful:~/Documents$ Back to top |
|
How about inxi -Gxx
the -xx option is an early attempt to show the compositor, but that's going to need a lot of work before it actually works right, I thought I'd start it and then update it once I get more user data. All wayland data sets I can get ( inxi -xx@14 ) will help me find methods that will work to identify the following items: 1. if a compositor is running (that's tricky) 2. which compostor is running if one is 3. the version of the compositor Also, with -xx, you'd see the legacy compatibility glx version as well, now inxi shows the real core profile glx version, not the legacy version, which was another issue someone else just posted on. Back to top |
|
Here is the output for Gxx but I have a different output executing inxi with or whithout 'sudo'
:: Code ::
corrado@corrado-artful:~$ cd Documents corrado@corrado-artful:~/Documents$ ls inxi corrado@corrado-artful:~/Documents$ ./inxi -Gxx 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 corrado@corrado-artful:~/Documents$ sudo ./inxi -Gxx [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: 104x27 Advanced Data: N/A for root 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: 1944 MHz 2: 2024 MHz 3: 1799 MHz 4: 2319 MHz Graphics: Card: Intel 4th Generation Core Processor Family Integrated Graphics Controller bus-ID: 00:02.0 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 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.9% used) ID-1: /dev/sda model: ST1000DM003 size: 1000.2GB temp: 35C Partition: ID-1: / size: 32G used: 11G (36%) 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: 206 Uptime: 8 min Memory: 856.7/7861.1MB Init: systemd runlevel: 5 Gcc sys: N/A Client: Shell (bash 4.4.121) inxi: 2.3.19 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) Desktop: N/A 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: 1757 MHz 2: 1138 MHz 3: 991 MHz 4: 1028 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) tty size: 104x27 Advanced Data: N/A for root 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.9% used) ID-1: /dev/sda model: ST1000DM003 size: 1000.2GB temp: 35C Partition: ID-1: / size: 32G used: 11G (36%) 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: 207 Uptime: 8 min Memory: 858.0/7861.1MB Init: systemd runlevel: 5 Gcc sys: N/A Client: Shell (sudo) inxi: 2.3.19 corrado@corrado-artful:~/Documents$ Back to top |
|
All times are GMT - 8 Hours |