anticapitalista
Status: Contributor
Joined: 13 Jun 2008
Posts: 202
Location: Greece
Reply Quote
This is great stuff. Thanks.

Now, there are plenty of inxi users with tiling wms such as wmii, dwm, awesome to name a few. Can they be detected? If so what info do you need?
Back to top
techAdmin
Status: Site Admin
Joined: 26 Sep 2003
Posts: 4127
Location: East Coast, West Coast? I know it's one of them.
Reply Quote
re adding wm, this is what I need:

the name of the windows manager, let's call it: tvwm
then:
output of: xprop -root
while IN the windows manager session.

Then: the version data, this is usually found by this: tvwm --version

If the wm is actually run by another one, like lxde is run by openbox, or fluxbox is run by blackbox, I also need to see the container wm --version

Currently supported:
gnome
kde 3.5, 4, 5
xfce 4,5
icewm
fluxbox
lxde
openbox
blackbox (but not re versioning, can't find that)
pekwm
awesome
fvwm
fvwm-crystal
twm (no versioning available)

If N/A is returned in X, that means inxi can't recognize anything about the wm in its current state.

You can just enter all the data in a new thread, it's not going to take much room up, the: xprop -root
output is not very long for small wm
Back to top
various wms.
anticapitalista
Status: Contributor
Joined: 13 Jun 2008
Posts: 202
Location: Greece
Reply Quote
wmii
:: Code ::

xprop -root
_NET_CLIENT_LIST(WINDOW): window id # 0xc00032, 0xe00004, 0x1000003
_NET_CURRENT_DESKTOP(CARDINAL) = 0
_NET_NUMBER_OF_DESKTOPS(CARDINAL) = 1
_NET_DESKTOP_NAMES(UTF8_STRING) = "1"
_NET_CLIENT_LIST_STACKING(WINDOW): window id # 0xc00032, 0xe00004, 0x1000003
_NET_SUPPORTED(ATOM) = _NET_SUPPORTED, _NET_ACTIVE_WINDOW, _NET_CLOSE_WINDOW, _NET_CURRENT_DESKTOP, _NET_FRAME_EXTENTS, _NET_WM_DESKTOP, _NET_WM_FULLSCREEN_MONITORS, _NET_WM_NAME, _NET_WM_STRUT, _NET_WM_STRUT_PARTIAL, _NET_WM_STATE, _NET_WM_STATE_DEMANDS_ATTENTION, _NET_WM_STATE_FULLSCREEN, _NET_WM_STATE_SHADED, _NET_WM_WINDOW_TYPE, _NET_WM_WINDOW_TYPE_DIALOG, _NET_WM_WINDOW_TYPE_DOCK, _NET_WM_WINDOW_TYPE_NORMAL, _NET_WM_WINDOW_TYPE_SPLASH, _NET_WM_ALLOWED_ACTIONS, _NET_WM_ACTION_FULLSCREEN, _NET_DESKTOP_NAMES, _NET_NUMBER_OF_DESKTOPS, _NET_CLIENT_LIST, _NET_CLIENT_LIST_STACKING
_NET_DESKTOP_VIEWPORT(CARDINAL) = 0, 0
_NET_SUPPORTING_WM_CHECK(WINDOW): window id # 0x800032
_XKB_RULES_NAMES(STRING) = "evdev", "pc105", "us,gr", ",", "grp:alt_shift_toggle,terminate:ctrl_alt_bksp,grp_led:scroll"
XFree86_VT(INTEGER) = 7

wmii -v
wmii-3.9.2, ©2010 Kris Maglione


dwm
:: Code ::

dwm

xprop -root
_NET_SUPPORTED(ATOM) = _NET_SUPPORTED, _NET_WM_NAME, _NET_WM_STATE, _NET_WM_STATE_FULLSCREEN
_XKB_RULES_NAMES(STRING) = "evdev", "pc105", "us,gr", ",", "grp:alt_shift_toggle,terminate:ctrl_alt_bksp,grp_led:scroll"
XFree86_VT(INTEGER) = 7

dwm -v
dwm-5.8.2, © 2006-2010 dwm engineers, see LICENSE for details

Back to top
techAdmin
Status: Site Admin
Joined: 26 Sep 2003
Posts: 4127
Location: East Coast, West Coast? I know it's one of them.
Reply Quote
I need the --version, I'll assume it works, the version function only works with --version, not -v.

If it's the same, don't worry, if it doesn't work, let me know.

I do read that correctly, that there is no space, rather a dash? amazing.... it never ceases to amaze me how many different ways projects can find to show simple data.

dwm-5.8.2, ©
wmii-3.9.2,

All other projects use name number or some version of that, sigh... here it's name-number... so I'll have to add explicit handling for that, grrrr.
Back to top
anticapitalista
Status: Contributor
Joined: 13 Jun 2008
Posts: 202
Location: Greece
Reply Quote
:: Code ::

dwm --version
usage: dwm [-v]

wmii --version
wmii: fatal: usage: wmii [-a <address>] [-r <wmiirc>] [-v]


More bad news :)
Back to top
techAdmin
Status: Site Admin
Joined: 26 Sep 2003
Posts: 4127
Location: East Coast, West Coast? I know it's one of them.
Reply Quote
And added trigger to change default --version if dwm/wmii in get_de_version function, sigh.

However, I can't really complain about this, it's only in this release that inxi supports --version either, this is actually one reason I added that.

anticap, update and let's see some sample output.
Back to top
anticapitalista
Status: Contributor
Joined: 13 Jun 2008
Posts: 202
Location: Greece
Reply Quote
dwm
:: Code ::

inxi -S
System:    Host antiX1 Kernel 2.6.38-7.dmz.1-liquorix-686 i686 (32 bit)
           Desktop dwm Distro antiX-M11-686-pt2 05 March 2011


wmi
:: Code ::

inxi -S
System:    Host antiX1 Kernel 2.6.38-7.dmz.1-liquorix-686 i686 (32 bit)
           Desktop wmii 3.9.2 Distro antiX-M11-686-pt2 05 March 2011


scrotwm. It presently shows up as twm
:: Code ::


xprop -root
_NET_WM_NAME(UTF8_STRING) = "LG3D"
_NET_SUPPORTING_WM_CHECK(WINDOW): window id # 0x15a
_XKB_RULES_NAMES(STRING) = "evdev", "pc105", "us,gr", ",", "grp:alt_shift_toggle,terminate:ctrl_alt_bksp,grp_led:scroll"
XFree86_VT(INTEGER) = 7

scrotwm --version
Welcome to scrotwm V0.9.20 cvs tag: $scrotwm: scrotwm.c,v 1.277 2009/11/25 17:03:53 marco Exp $
scrotwm: other wm running

Back to top
techAdmin
Status: Site Admin
Joined: 26 Sep 2003
Posts: 4127
Location: East Coast, West Coast? I know it's one of them.
Reply Quote
come to irc.oftc.net #smxi now, takes too long to do this.

I fixed the scrotwm by adding it, and also added a space test pre twm/dwm because those are short non-unique search terms

Update, no new version number so far.

let me see: ps aux | grep twm
or
ps aux | grep twm
when running scrotwm

the failure to show -v data for dwm I assume means it has a space, to test for spaces etc in output do this:

data="$( dwm -v )"; echo ":$data:"

this reveals unexpected white spaces.

need to make sure the twm has a space in front of it and not the system path.

I changed it a bit, but if you have more issues, please find me on channel #smxi so we don't have to spend all day debugging desktops etc.
Back to top
anticapitalista
Status: Contributor
Joined: 13 Jun 2008
Posts: 202
Location: Greece
Reply Quote
I posted in irc. Hope you got the info.
Just in case:

:: Code ::

ps aux | grep twm
antiX     7327  0.0  0.0   3756   784 ?        S    00:27   0:00 ck-launch-session dbus-launch /bin/bash -login /home/antiX/.xinitrc scrotwm
antiX     7334  0.0  0.0   6732  1588 ?        S    00:27   0:00 scrotwm
antiX     7764  0.0  0.0   5148   760 pts/0    S+   00:30   0:00 grep twm


:: Code ::

inxi -S
System:    Host antiX1 Kernel 2.6.38-7.dmz.1-liquorix-686 i686 (32 bit)
           Desktop Scrotwm Distro antiX-M11-686-pt2 05 March 2011

Back to top
techAdmin
Status: Site Admin
Joined: 26 Sep 2003
Posts: 4127
Location: East Coast, West Coast? I know it's one of them.
Reply Quote
it appears that both scrotwm and dwm have a bug with their version output.

Rather than use this slow method, which is no fun for debugging, let's meet on IRC when we can both be there.

The logic follows whatever you posted, so failure to work is caused by something else. Both should be showing version information, in other words, unless you didn't update inxi.

As you can see, the output works fine:
:: Code ::
echo 'welcome to scrotwm v1.2.3' | gawk '/welcome.*scrotwm/ {sub(/v/,"",$4);print $4}'
1.2.3

so I'm guessing other perverse causes like scrotwm and dwm actually returning the stuff as an error not straight stdout output.
Back to top
Display posts from previous:   

All times are GMT - 8 Hours