What steps will reproduce the problem? 1. Run inxi -S

What is the expected output? System: Host: xps Kernel: 3.13.0-1-generic x86_64 (64 bit) Desktop: Unity Distro: Ubuntu 14.04 trusty

What do you see instead? System: Host: xps Kernel: 3.13.0-1-generic x86_64 (64 bit) Desktop: Gnome Distro: Ubuntu 14.04 trusty

What version of the product are you using? $ inxi -V inxi 1.9.17-00 (2013-12-02)

On what operating system? Ubuntu 14.04 trusty

I have not received any data files that let me identify wayland.

Please run inxi with this command on a wayland system:

inxi -xx@14

to send me a full system data output.

Also, send any relevant output from wayland itself thazt could be used to identify it.

I've never seen any wayland output since it's almost barely out of alpha dev stages, so I don't know what data it offers or how to access any of that data, but some of the desktop stuff in -xx@14 may help spot it.

This is marked as an enhancement since wayland is a new system and I have no data on it or how to use it in terms of collecting data.

Unity has nothing to do with wayland, it runs on regular X11.

BTW you should put more warnings saying that command is going to send all the data of my system me to you, that felt pretty nasty to be honest.

Anyway you probably just want to have a look at the XDG_CURRENT_DESKTOP=Unity envvar

Sorry, mental glitch, mir/unity, wayland etc, all mixed together in my head as stuff not quite ready for prime time...

If the envvar is set it's easy, next I need to know how to get the version of unity:

ie, the command: unity --version or unity -v or however one gets unity version. No gui methods can be used, of course.

and also, assuming it's: unity --version

then: unity --version || echo yes

If it shows 'yes', then it's output to stderr.

The latter is because a handful of desktops put the version info out into stderr, for some inexplicable reason, so inxi needs to know that.

The output data is not very interesting unless you are making something like inxi, it's just tech specs of the system, and shortens my debugging time by about 50x in many cases since I don't have to ask for various files, then wait to get them, or not.

XDG_CURRENT_DESKTOP is not currently used at all in inxi, that must be some newish thing, I'll have to look into what is identifying itself with that. Looks like new kde's are, that's nice to see. Though just the basic string: KDE. Would be nice if all desktops used that, I'll it to the inxi debugging output data collection and see what shows up.

Oh, I forgot, what toolkit, if any, does unity use? inxi shows the toolkit, if available, like gtk, qt, etc, at least if it can find the data, as well.

Don't worry about the debugger data, only inxi devs, mostly me, see that, it's not public.

version 1.9.18 should now support unity, plus it shows default runlevel, and should show gtk version of desktop toolkit better too, though that will never be perfect.

Surprisingly few user systems show that env variable set for desktop, kde does, lxde does, unity does, and that's all I know about at this point, xfce does not, gnome does not, and the smaller window managers don't, except lxde for some reason. I'm assuming that some will use it more in the future, so I'll track that.

I'm closing this, so if there is an issue, file a new issue report.

Actually you did elif [[ $XDG_CURRENT_DESKTOP == 'UNITY' ]];then which should be elif [[ $XDG_CURRENT_DESKTOP == 'Unity' ]];then

So I did, must be a subconscious thing. I have now updated inxi but there's no new version number, but there is a new tarball with the fixed Unity.