inxi + window managers using other window managers

h2-1 · 12-14-2023, 04:49 PM

I'm upgrading the core inxi desktop / window manager, and want to make sure my handling of window managers that allow for using another window manager list is reasonably complete.

While this has always struck me as non intuititive, a wm using a different wm, it is a thing, which in the past I had experimented with quite a bit, but unfortunately did not document well.

For example, I believe FVWM, iceWM let you use another window manager as window manager. A surprising number of them do. Some desktops also do, like xfce, mate (maybe?).

Does anyone know of more window managers that can act as a 'parent' to another window manager? That is, from inside the first, you can start the second?

For the ongoing refactor I'd like to get this reasonably solid before releasing it to the wilds.

I know, I know, arcane, but thought I'd try asking in case someone is very up on this arcana.

rokytnji · 12-14-2023, 04:56 PM

Well rox desktop and zzzfm desktop run on top of Icewm or Fluxbox in antiX.
They come with the full iso install.

h2-1 · 12-14-2023, 05:17 PM

Are those detectable, or basically just wrappers over the wm?

Via ps aux, that is.

The inxi internal tools for detecting desktop/wm/features etc got pretty messy as I added stuff over years, so I'm stripping it all down and redoing it.

This is ongoing in pinxi, along with new features like screensaver/lockers.

If they are, what is the ps aux line for each?

I should probably grab the new antiX iso. I also have a few generations of wm focused vms which I've used in the past to figure this stuff out and test it, but it's a time consuming process since it requires doing each combination and checking the results.

I'm kicking myself for not having documented these possible combinations when I did the tests in the past since they only need to be done once.

I remember rox was not really detectable, so I think that may be the wrong direction, wrappers over parents, that is, I'm looking for wm capable of being parents to other wm.

h2-1 · 12-15-2023, 12:41 AM

I believe these can be parents, some from my notes, others from memory:

FVWM
BlackBox
iceWM

I know more than that meet the condition of being able to be parent of a different window manager however.

rokytnji · 12-15-2023, 07:53 PM

Code:

harry@biker:~
$ ps -aux fluxbox
error: unsupported option (BSD syntax)

Usage:
 ps [options]

 Try 'ps --help <simple|list|output|threads|misc|all>'
  or 'ps --help <s|l|o|t|m|a>'
 for additional help text.

For more details see ps(1).
harry@biker:~
$ ps aux jwm
error: conflicting format options

Usage:
 ps [options]

 Try 'ps --help <simple|list|output|threads|misc|all>'
  or 'ps --help <s|l|o|t|m|a>'
 for additional help text.

For more details see ps(1).

Been busy testing 23.1 runit 64 bit iso on some other boxes. This reading is off my antiX 22 laptop. Sorry it don't help.

h2-1 · 12-15-2023, 08:10 PM

If you put other strings like window manager names in there it will fail since it doesn't support those option letters.

ps is the command, aux are the option letters combined (- is not required).

The output contains the window manager data.

boughtonp · 12-16-2023, 09:07 AM

I don't know if I understand what is being asked here, but wouldn't the question be better targetted at the respective WM developers? (Who can presumably identify precisely what they do/don't support and how to detect it.)

If AntiX is relevant, maybe it would help if someone currently running it could show the output of "pstree -a" (or "pstree -aclptu") before and after switching between IceWM+zzzFM to Fluxbox+Rox or whatever?

//download.tuxfamily.org/antix/docs-antiX-23/FAQ/index.html#_what_window_managers_are_available_in_antix

If not, an example of (nested|embedded|chained|whatever) window managers and what the "ps aux" (i.e. "ps -eF") output looks like - or simply some code from the current/old test - might make it clearer.

rokytnji · 12-16-2023, 04:14 PM

Code:

$ pstree -a
runit
  ├─at-spi-bus-laun
  │   ├─dbus-daemon--config-file=/usr/share/defaults/at-spi2/accessibility.con
  │   └─3*[{at-spi-bus-laun}]
  ├─at-spi2-registr --use-gnome-session
  │   └─2*[{at-spi2-registr}]
  ├─chrome
  │   ├─cat
  │   ├─cat
  │   ├─chrome
  │   │   └─chrome
  │   │       └─13*[{chrome}]
  │   ├─chrome
  │   │   ├─chrome
  │   │   │   ├─chrome
  │   │   │   │   └─7*[{chrome}]
  │   │   │   ├─chrome
  │   │   │   │   └─10*[{chrome}]
  │   │   │   ├─chrome
  │   │   │   │   └─10*[{chrome}]
  │   │   │   ├─chrome
  │   │   │   │   └─10*[{chrome}]
  │   │   │   ├─chrome
  │   │   │   │   └─10*[{chrome}]
  │   │   │   ├─chrome
  │   │   │   │   └─10*[{chrome}]
  │   │   │   └─chrome
  │   │   │       └─9*[{chrome}]
  │   │   └─nacl_helper
  │   ├─chrome
  │   │   └─8*[{chrome}]
  │   ├─chrome
  │   │   └─7*[{chrome}]
  │   └─34*[{chrome}]
  ├─chrome_crashpad --monitor-self--monitor-self-annotat
  │   └─2*[{chrome_crashpad}]
  ├─chrome_crashpad --no-periodic-tasks--monitor-self-an
  │   └─{chrome_crashpad}
  ├─conky
  │   └─6*[{conky}]
  ├─conky
  │   └─6*[{conky}]
  ├─dbus-daemon --syslog-only --fork --print-pid 5 --print-address 7--sess
  ├─dbus-daemon --syslog-only --fork --print-pid 5 --print-address 7--sess
  ├─dbus-launch --autolaunch 56507f22267c6233e8fff9cc6578df09 ...
  ├─dbus-launch --autolaunch 56507f22267c6233e8fff9cc6578df09 ...
  ├─dconf-service
  │   └─2*[{dconf-service}]
  ├─devmon /usr/bin/devmon --exec-on-drive desktop-defaults-run -fm "%d"...
  │   └─udevil --monitor
  ├─gconfd-2
  ├─pipewire
  │   └─2*[{pipewire}]
  ├─pipewire-pulse
  │   └─2*[{pipewire-pulse}]
  ├─roxterm
  │   └─bash
  │       └─pstree -a
  ├─runsvdir -P /etc/service...
  │   ├─runsv dbus
  │   │   └─dbus-daemon --system --nofork --nopidfile
  │   ├─runsv udevd
  │   │   └─udevd
  │   ├─runsv seatd
  │   │   └─seatd -g video
  │   ├─runsv getty-tty3
  │   │   └─getty 38400 tty3 linux
  │   ├─runsv getty-tty1
  │   │   └─getty 38400 tty1 linux
  │   ├─runsv getty-tty2
  │   │   └─getty 38400 tty2 linux
  │   ├─runsv slimski
  │   │   └─slimski
  │   │       ├─Xorg -nolisten tcp -auth /var/run/slimski.auth
  │   │       │   └─2*[{Xorg}]
  │   │       └─desktop-session /usr/local/bin/desktop-session zzz-icewm
  │   │           └─icewm-session
  │   │               └─icewm --notify
  │   └─runsv connman
  │       └─connmand -n --nodnsproxy
  ├─startup /home/harry/.desktop-session/startup
  │   └─volumeicon
  │       └─3*[{volumeicon}]
  ├─upowerd
  │   └─2*[{upowerd}]
  ├─wireplumber
  │   └─4*[{wireplumber}]
  ├─wpa_supplicant -u -s -O /run/wpa_supplicant
  └─zzzfm --desktop
harry@antix1:~
$

Code:

$ pstree -a
runit
  ├─at-spi-bus-laun
  │   ├─dbus-daemon--config-file=/usr/share/defaults/at-spi2/accessibility.con
  │   └─3*[{at-spi-bus-laun}]
  ├─at-spi2-registr --use-gnome-session
  │   └─2*[{at-spi2-registr}]
  ├─chrome
  │   ├─cat
  │   ├─cat
  │   ├─chrome
  │   │   └─chrome
  │   │       └─13*[{chrome}]
  │   ├─chrome
  │   │   ├─chrome
  │   │   │   ├─chrome
  │   │   │   │   └─7*[{chrome}]
  │   │   │   ├─chrome
  │   │   │   │   └─10*[{chrome}]
  │   │   │   ├─chrome
  │   │   │   │   └─10*[{chrome}]
  │   │   │   ├─chrome
  │   │   │   │   └─10*[{chrome}]
  │   │   │   ├─chrome
  │   │   │   │   └─10*[{chrome}]
  │   │   │   ├─chrome
  │   │   │   │   └─10*[{chrome}]
  │   │   │   └─chrome
  │   │   │       └─9*[{chrome}]
  │   │   └─nacl_helper
  │   ├─chrome
  │   │   └─8*[{chrome}]
  │   ├─chrome
  │   │   └─7*[{chrome}]
  │   └─34*[{chrome}]
  ├─chrome_crashpad --monitor-self--monitor-self-annotat
  │   └─2*[{chrome_crashpad}]
  ├─chrome_crashpad --no-periodic-tasks--monitor-self-an
  │   └─{chrome_crashpad}
  ├─conky
  │   └─6*[{conky}]
  ├─conky
  │   └─6*[{conky}]
  ├─dbus-daemon --syslog-only --fork --print-pid 5 --print-address 7--sess
  ├─dbus-daemon --syslog-only --fork --print-pid 5 --print-address 7--sess
  ├─dbus-launch --autolaunch 56507f22267c6233e8fff9cc6578df09 ...
  ├─dbus-launch --autolaunch 56507f22267c6233e8fff9cc6578df09 ...
  ├─dconf-service
  │   └─2*[{dconf-service}]
  ├─devmon /usr/bin/devmon --exec-on-drive desktop-defaults-run -fm "%d"...
  │   └─udevil --monitor
  ├─gconfd-2
  ├─pipewire
  │   └─2*[{pipewire}]
  ├─pipewire-pulse
  │   └─2*[{pipewire-pulse}]
  ├─rox --pinboard=antiX-jwm
  ├─roxterm
  │   └─bash
  │       └─pstree -a
  ├─runsvdir -P /etc/service...
  │   ├─runsv dbus
  │   │   └─dbus-daemon --system --nofork --nopidfile
  │   ├─runsv udevd
  │   │   └─udevd
  │   ├─runsv seatd
  │   │   └─seatd -g video
  │   ├─runsv getty-tty3
  │   │   └─getty 38400 tty3 linux
  │   ├─runsv getty-tty1
  │   │   └─getty 38400 tty1 linux
  │   ├─runsv getty-tty2
  │   │   └─getty 38400 tty2 linux
  │   ├─runsv slimski
  │   │   └─slimski
  │   │       ├─Xorg -nolisten tcp -auth /var/run/slimski.auth
  │   │       │   └─2*[{Xorg}]
  │   │       └─desktop-session /usr/local/bin/desktop-session zzz-icewm
  │   │           └─jwm
  │   └─runsv connman
  │       └─connmand -n --nodnsproxy
  ├─startup /home/harry/.desktop-session/startup
  │   └─volumeicon
  │       └─3*[{volumeicon}]
  ├─upowerd
  │   └─2*[{upowerd}]
  ├─wireplumber
  │   └─4*[{wireplumber}]
  └─wpa_supplicant -u -s -O /run/wpa_supplicant
harry@antix1:~
$

Code:

$ pstree -a
runit
  ├─at-spi-bus-laun
  │   ├─dbus-daemon--config-file=/usr/share/defaults/at-spi2/accessibility.con
  │   └─3*[{at-spi-bus-laun}]
  ├─at-spi2-registr --use-gnome-session
  │   └─2*[{at-spi2-registr}]
  ├─chrome
  │   ├─cat
  │   ├─cat
  │   ├─chrome
  │   │   └─chrome
  │   │       └─13*[{chrome}]
  │   ├─chrome
  │   │   ├─chrome
  │   │   │   ├─chrome
  │   │   │   │   └─7*[{chrome}]
  │   │   │   ├─chrome
  │   │   │   │   └─10*[{chrome}]
  │   │   │   ├─chrome
  │   │   │   │   └─10*[{chrome}]
  │   │   │   ├─chrome
  │   │   │   │   └─10*[{chrome}]
  │   │   │   ├─chrome
  │   │   │   │   └─10*[{chrome}]
  │   │   │   ├─chrome
  │   │   │   │   └─10*[{chrome}]
  │   │   │   └─chrome
  │   │   │       └─9*[{chrome}]
  │   │   └─nacl_helper
  │   ├─chrome
  │   │   └─8*[{chrome}]
  │   ├─chrome
  │   │   └─7*[{chrome}]
  │   └─34*[{chrome}]
  ├─chrome_crashpad --monitor-self--monitor-self-annotat
  │   └─2*[{chrome_crashpad}]
  ├─chrome_crashpad --no-periodic-tasks--monitor-self-an
  │   └─{chrome_crashpad}
  ├─conky
  │   └─6*[{conky}]
  ├─conky
  │   └─6*[{conky}]
  ├─dbus-daemon --syslog-only --fork --print-pid 5 --print-address 7--sess
  ├─dbus-daemon --syslog-only --fork --print-pid 5 --print-address 7--sess
  ├─dbus-launch --autolaunch 56507f22267c6233e8fff9cc6578df09 ...
  ├─dbus-launch --autolaunch 56507f22267c6233e8fff9cc6578df09 ...
  ├─dconf-service
  │   └─2*[{dconf-service}]
  ├─devmon /usr/bin/devmon --exec-on-drive desktop-defaults-run -fm "%d"...
  │   └─udevil --monitor
  ├─gconfd-2
  ├─pipewire
  │   └─2*[{pipewire}]
  ├─pipewire-pulse
  │   └─2*[{pipewire-pulse}]
  ├─rox --pinboard=antiX-icewm
  ├─roxterm
  │   └─bash
  │       └─pstree -a
  ├─runsvdir -P /etc/service...
  │   ├─runsv dbus
  │   │   └─dbus-daemon --system --nofork --nopidfile
  │   ├─runsv udevd
  │   │   └─udevd
  │   ├─runsv seatd
  │   │   └─seatd -g video
  │   ├─runsv getty-tty3
  │   │   └─getty 38400 tty3 linux
  │   ├─runsv getty-tty1
  │   │   └─getty 38400 tty1 linux
  │   ├─runsv getty-tty2
  │   │   └─getty 38400 tty2 linux
  │   ├─runsv slimski
  │   │   └─slimski
  │   │       ├─Xorg -nolisten tcp -auth /var/run/slimski.auth
  │   │       │   └─2*[{Xorg}]
  │   │       └─desktop-session /usr/local/bin/desktop-session zzz-icewm
  │   │           └─icewm-session
  │   │               └─icewm --notify
  │   └─runsv connman
  │       └─connmand -n --nodnsproxy
  ├─startup /home/harry/.desktop-session/startup
  │   └─volumeicon
  │       └─3*[{volumeicon}]
  ├─upowerd
  │   └─2*[{upowerd}]
  ├─wireplumber
  │   └─5*[{wireplumber}]
  └─wpa_supplicant -u -s -O /run/wpa_supplicant

Code:

$ pstree -a
runit
  ├─at-spi-bus-laun
  │   ├─dbus-daemon--config-file=/usr/share/defaults/at-spi2/accessibility.con
  │   └─3*[{at-spi-bus-laun}]
  ├─at-spi2-registr --use-gnome-session
  │   └─2*[{at-spi2-registr}]
  ├─chrome
  │   ├─cat
  │   ├─cat
  │   ├─chrome
  │   │   └─chrome
  │   │       └─13*[{chrome}]
  │   ├─chrome
  │   │   ├─chrome
  │   │   │   ├─chrome
  │   │   │   │   └─7*[{chrome}]
  │   │   │   ├─chrome
  │   │   │   │   └─10*[{chrome}]
  │   │   │   ├─chrome
  │   │   │   │   └─10*[{chrome}]
  │   │   │   ├─chrome
  │   │   │   │   └─10*[{chrome}]
  │   │   │   ├─chrome
  │   │   │   │   └─10*[{chrome}]
  │   │   │   ├─chrome
  │   │   │   │   └─10*[{chrome}]
  │   │   │   └─chrome
  │   │   │       └─9*[{chrome}]
  │   │   └─nacl_helper
  │   ├─chrome
  │   │   └─8*[{chrome}]
  │   ├─chrome
  │   │   └─7*[{chrome}]
  │   └─34*[{chrome}]
  ├─chrome_crashpad --monitor-self--monitor-self-annotat
  │   └─2*[{chrome_crashpad}]
  ├─chrome_crashpad --no-periodic-tasks--monitor-self-an
  │   └─{chrome_crashpad}
  ├─conky
  │   └─6*[{conky}]
  ├─conky
  │   └─6*[{conky}]
  ├─dbus-daemon --syslog-only --fork --print-pid 5 --print-address 7--sess
  ├─dbus-daemon --syslog-only --fork --print-pid 5 --print-address 7--sess
  ├─dbus-launch --autolaunch 56507f22267c6233e8fff9cc6578df09 ...
  ├─dbus-launch --autolaunch 56507f22267c6233e8fff9cc6578df09 ...
  ├─dconf-service
  │   └─2*[{dconf-service}]
  ├─devmon /usr/bin/devmon --exec-on-drive desktop-defaults-run -fm "%d"...
  │   └─udevil --monitor
  ├─gconfd-2
  ├─pipewire
  │   └─2*[{pipewire}]
  ├─pipewire-pulse
  │   └─2*[{pipewire-pulse}]
  ├─rox --pinboard=antiX-fluxbox
  ├─roxterm
  │   └─bash
  │       └─pstree -a
  ├─runsvdir -P /etc/service...
  │   ├─runsv dbus
  │   │   └─dbus-daemon --system --nofork --nopidfile
  │   ├─runsv udevd
  │   │   └─udevd
  │   ├─runsv seatd
  │   │   └─seatd -g video
  │   ├─runsv getty-tty3
  │   │   └─getty 38400 tty3 linux
  │   ├─runsv getty-tty1
  │   │   └─getty 38400 tty1 linux
  │   ├─runsv getty-tty2
  │   │   └─getty 38400 tty2 linux
  │   ├─runsv slimski
  │   │   └─slimski
  │   │       ├─Xorg -nolisten tcp -auth /var/run/slimski.auth
  │   │       │   └─2*[{Xorg}]
  │   │       └─desktop-session /usr/local/bin/desktop-session zzz-icewm
  │   │           └─fluxbox
  │   └─runsv connman
  │       └─connmand -n --nodnsproxy
  ├─startup /home/harry/.desktop-session/startup
  │   └─volumeicon
  │       └─3*[{volumeicon}]
  ├─upowerd
  │   └─2*[{upowerd}]
  ├─wireplumber
  │   └─4*[{wireplumber}]
  └─wpa_supplicant -u -s -O /run/wpa_supplicant

HTH you.

h2-1 · 12-16-2023, 05:49 PM

boughtonp, if by 'better' you mean consuming a massive amount of time and generally getting no response, then going wm by wm and asking the devs would be better.

This would be in the area of: if someone other than me does that, then yes, it's better, but if I have to do it, no, it's not better.

It's far far faster to just boot vms, install the wm, then test.

But fastest yet is to ask, and hope someone very up on the innards of wms in general would know.

That does not unfortunately appear to be the case, but it was worth a shot anyway.

h2-1 · 12-16-2023, 07:04 PM

rokytnji, pstree makes very nice looking human readable output, but sadly tree format is close to impossible to machine parse, so that won't help, it would be nice if it did though.

I don't believe pstree is a default tool, again, if it were, it would be nice, particularly if has json output mode.

But I try to stick to the absolute basics when it comes to dependencies.

But pstree is a nice tool, I think I'll add it to the debugger since it gives such useful human structured output and might provide hints on how to use standard data output types.

h2-1 · 12-18-2023, 04:00 PM

By the way, the reason I no longer waste time going project by project, code repo to code repo, asking for such help, which to me, helps the project, helps me, is that almost invariably you do NOT get the response, instead, say, if you want to get the version output, instead of them just answering the question, they will tell you to install it and see for yourself. That is, they will literally take longer to type the response than it would have taken them to to provide the requested data.

I have no idea why this is, but it's why I do not generally engage with projects to get very specific data, often hard to explain, the signal (good answer, quick, covers it all), to noise (anything but the actual answer) is so close to zero that it's probably the very worst way to spend my dev time I've ever found, which is why I now no longer do it.

Sometimes I will go to their IRC if they have one and ask, but again, the signal to noise ratio is just way way too low to make it worth it. Though sometimes it works, that's why for example inxi can show SysvInit version info for some distros, it's Debian maintainer gave me some pointers that worked.

boughtonp · 12-19-2023, 07:21 AM

That's depressing. I would have assumed the average WM developer to be more engaging, especially with something that benefits both projects.

Sometimes feels like people today are less collaborative than in the past, but maybe that's just nostalgia.

I suggested pstree not as a final tool to use, but because I know the psmisc package is pre-installed on AntiX (though not Debian) and it can be a useful way of visualising child processes. (Although less so when there's a bunch of unrelated stuff that could have been pruned.)

For fans of tree structures, recent versions of column (from util-linux/bsdextrautils) have a --tree option for formatting arbitrary data. (Think it's a Recommends dependency on Debian, so usually exists but isn't guaranteed.)

h2-1 · 12-19-2023, 01:09 PM

It is actually very depressing, and no, it's not nostalgia, this difference is extremely visible to me because inxi grew up with a lot of input from people, I did not have to do much to get help or feedback etc. In fact, this is really my top concern for the future of inxi as a project, each tiny bit of data takes often huge amounts of time and research, and I'm not always going to spend that time, and in the future, may decide to just stop. Not now, but it is getting discouraging to me.

I will add the pstree to inxi debugger, it makes the structure of the PIDs / processes re parent/child relationships really clear.

The drag is that without json output option, the tree structure is totally unusuable as output for processing, but json is designed precisely to handle that exact type of data structure, hashes of hashes. That's how inxi works internally for creating output, which is why it was easy adding json output mode. Easy for me to add, not easy for people to use because the data structure is complicated and not newbie usable.

But yes, the difficulty of trying to get devs to spend a few seconds giving me data is so bad that I literally will do it only as my absolute LAST resort because the time-energy/results ratio is absolutely awful.

Something as trivial for example as just getting the version string and if it outputs to stdout or stderr I don't bother asking anymore because it's not worth the effort. I also find this depressing because to me, devs should be happy someone is trying to support their obscure project, and is interested in it, but as a rule, it's a poor use of my time to try.

I am going to try today with Alpine linux because I have a specific question re elogind/seatd acting as what I think of as a display manager to start wayland compositor, but I do not understand how the terms are being used, though clearly they are functioning in that role.

The overall utility of adding debugger items is not always the present, but the future, when I can go back and check on stuff, zgrep through the debugger archives, and find patterns that I may not have been looking for back then. So I tend to add more items as I go along, sometimes because I'm thinking of maybe using a specific tool or command and want to see what the data variations look like, other times more just to see what the data is, if it can be used for something.

These problems are not just devs, for example, some guys from a distro not to be named responded to my polite request, back in inxi bash/gawk days, if anyone wanted to test some stuff for their distro, and one of their IRC guys started railing on how inxi was going to pull in bash, and at that point, I just said, whatever, and that was literally the last time I ever interacted with them since this is not a job for me, and they have the choice of whether to be helpful, neutral, or hostile in a pointless way. If this were work and I was getting paid professional wages, I would not care, it would just be a job, often not pleasant, but I try to filter out the unpleasant stuff and people since I don't in fact get paid to deal with them.

enigma9o7 · 12-19-2023, 02:14 PM

I dunno if this is the kinda info you're asking for, but perhaps it is. Bodhi linux uses a fork of enlightenment called Moksha. When I look at neofetch, it identifies the DE as Enlightenment but the WM as Moksha. I'd imagine under pure enlightenment, those would both report e.

h2-1 · 12-20-2023, 12:21 AM

Yes, that's handled, that is actually similar, except different, so to speak.

Moksha is somewhat difficult to detect, but inxi does it fine, and doesn't confuse it with Enlightenment.

That is technically a case of a Desktop rather than a wm using a wm, xfce can for example use different window managers though it usually uses xfwm.

However the case I'm looking at is actual wm like iceWM using a different wm, which is a confusing notion, but is a thing.

Booted a bodhi vm to check:

Reports correctly as: Desktop: Moksha v: 0.4.0.17738 vt: 7

inxi doesn't repeat the wm if it's the same as the desktop.

neofetch fails on corner cases, it's bash, and there's a limit what it can do without a real programming language, I tried that for years with inxi too. screenfetch author used to use bits of inxi desktop at least, but now inxi is perl. But that project is apparently no longer maintained, which I understand, when I had to chose to continue inxi, it was either rewrite it into Perl from bash/gawk or stop doing it because bash was a constant obstacle to progress or solutions, which is not surprising since it is not meant to be a full programming language.

I have't tested Enlightenment for a while, and I don't think I've tested the wayland version, but it should show as Enlightenment, without a wm. wm only shows if it is different from the desktop.