The wmii thread

harlekin · 2007-01-08 19:36:08

Thanks for the hint, veek. But I still cannot get wmii to work.

I've reinstalled libixp from extra.
I've built dmenu from AUR and I've built wmii with the PKGBUILD from abs.
I edited wmii's PKGBUILD that it depends on dmenu and libixp and for completeness libx11 as well.

dmenu, libixp and wmii are properly installed but when I want to start X I still get this error:

/usr/bin/wmii: line 10: /usr/bin/wmiiwm: No such file or directory
/usr/bin/wmii: line 10: /usr/bin/wmiiwm: success

(Translated error message)

Any suggestions? :

I run wmii via startx and this in my .xinitrc:

exec wmii

veek · 2007-01-08 20:43:44

Hey harlekin.

edit:
Just reboot your computer, and wmii should start fine. If not
you can take a look at the other stuff I spewed out below.

Details:

Look in the folder /tmp. There should be a folder called something like ns.yourusername.:0.

For me the folder is /tmp/ns.moveek.:0. Yours would be something like
/tmp/ns.harlekin.:0. If you look inside the folder it's probably empty,
and that's the problem.

Delete that folder and run startx. This time wmii should start properly
and that folder will be recreated with a socket inside.

More Details:

The real problem is that wmiiwm looks for
a socket in /tmp/ns.yourhostname.:0/, and if it doesn't find the socket it is supposed to create it.

The problem is that without dmenu installed wmiiwm creates the folder
in /tmp but it doesn't create the socket. Once you install dmenu, wmiiwm
tries to create the socket, but there is already a folder (empty) there so it doesn't
actually create it. So there is still no socket.

The solution is to remove the empty folder previously created in /tmp
then when wmii is run again it can create the folder and the socket.

In my case it is: /tmp/ns.moveek.:0/wmii.

/usr/bin/wmii is actually a script that calls /usr/bin/wmiiwm.

You can take a look in there if you want to know exactly what's going on.

alcazoid · 2007-01-08 23:19:27

veek wrote:

Hey harlekin.
edit:
Just reboot your computer, and wmii should start fine.

Come on... Rebooting is not unix-way of solving problems...

harlekin · 2007-01-09 05:40:54

Well... as I don't like to reboot my computer I tried first to delete the folder in /tmp. In fact there were even two folders:
ns.harlekin.:0 and ns.harlekin.:1 properly because I ran xinit -- :1 some time ago.
I deleted both of them and tried to run startx but I got the same problem as mentioned above.
I looked into /usr/bin/wmii and I see that ~/tmp/ns.$user.$display is created there but I couldn't find a line that creates a socket.

Neither I couldn't find a argument to wmiiwm or dmenu that creates a socket. I can tell wmiiwm which socket to use (-a) but if this does create the socket, the folder is there every time before wmiiwm is executed (first call to create directory then exec wmiiwm in /usr/bin/wmii).

Does anyone has other suggestions? (Thanks so far!)

tbroderick · 2007-01-09 06:35:21

harlekin wrote:

Does anyone has other suggestions? (Thanks so far!)

I do. I got the same error you did about /usr/bin/wmiiwm from installing libixp and wmii from extra. There is something wrong with the pkg's. Use the PKGBUILD and config.mk for wmii and libixp on the previous page that were posted by alcazoid and the dmenu from AUR. That worked for me.

veek · 2007-01-09 15:20:04

alcazoid

Hehe

harlekin

I was so sure I knew what the problem was .

I think the line that creates the socket is in the wmiiwm binary.
I think the -a line in /usr/bin/wmii just tells wmiiwm where to create the socket.

After you delete the existing folders in /tmp and then run startx
does the folder and socket get created in /tmp (even if wmii fails to start)?
Or does it only create the folder?

Also try removing libixp entirely and starting wmii. I'm able to get into
wmii without libixp even though I can't do anything. The socket should
get created when booting without libixp.

harlekin · 2007-01-09 15:33:26

First of all thanks for all your effort. (=

It's now working!

First wmii from extra if defenetly broken. I could not get wmii to start even I removed to error from it's dependencies (typo). I edited the PKGBUILD and built it which appeared to work out. Even installation was fine but the error I mentioned above occures.

I finally used alcazoid's PKGBUILDs both for libixp and wmii and they're working (except I had to edit the config.mk manually because vim added a space in the end of each line, but thats a vim bug).

I cannot say wether libixp from extra is broken, too. But I guess it's working.

As a matter of completeness:
veek: Only the folder is created. I don't know what actually causes wmii to fail to start.

Well. Thanks a lot again. I finally can and will after submitting this port, switch to wmii again (=

veek · 2007-01-09 15:41:19

Okay harlekin. Confusing business!

I might take a look at alcazoid's PKGBUILDS and see if I
can figure out the difference. I think what may have fixed the problem
is recompiling wmii after dmenu was installed.

There's a new PKGBUILD for wmii in extra that fixes the typo.
It still doesn't mention dmenu as a dependency though.

Glad you got it working, enjoy using wmii!

alcazoid · 2007-01-09 17:38:06

veek
I already looked through it to find the difference. Nothing special except there is VERSION=3 in extra PKGBUILDs, and I'm using VERSION=3.5.1 in my PKGBUILDs(I took it from original wmii-3.5.1 config.mk). I don't know if that makes any sense.
And I'm not sure if there is need to use dmenu as dependency, wmii is working without dmenu, it's just mentioned in wmiirc.
Update:
I just thought that one more reason not to add dmenu as a dependency is that dmenu is only in AUR, not in official repositaries, that's why pacman will be unable to solve the dependency.
Too bad that nobody tested packages before submitting to extra

veek · 2007-01-10 04:35:20

Hey alcazoid

I looked into it a little bit more.

The problem and difference is in the config.mk.

Yours, which works, uses different includes.

One difference (among several) is in the X11INC variable:

In your config.mk: X11INC = /usr/include/xorg.
config.mk in extra: X11INC = /usr/include/X11.

I'm guessing that the pkg in extra is using the wrong / old config.mk
considering that the variable VERSION = 3.

I'm not sure about the dmenu thing. I don't get any menu without it.

Sorry if I sent people on a wild goose chase.
Alcazoid's PKGBUILD solves the issue, specifically he supplied
the correct config.mk.

Good work Alcazoid

veek · 2007-01-10 04:48:40

alcazoid

I posted your copy of the config.mk to flyspray, here's the link:

http://bugs.archlinux.org/task/6189

Also are you positive you don't need dmenu?

Without it installed, I don't get the menu at the bar in the bottom of the screen when
I press ALT-a. the one that says:

quit status welcome wmiirc

Also I don't get the run command prompt when I press ALT-p, that
lets me launch programs by typing in the name.

tbroderick · 2007-01-10 05:03:29

The announcement on the wmii mailing list says dmenu and libixp are mandatory. So dmenu should be in extra too. I believe dmenu is only optional in dwm.

codemac · 2007-01-10 05:15:12

Wow.

I haven't screwed up on a package like this in a _while_.

I really apologize to the users of wmii, I really needed to test this package a bit more thoroughly. Like at all.

This was me just acting too quickly.

I'd also like to thank everyone who notified me about this. Normally my interaction with users has been that of demand and disrespect. EVERYONE I've talked to about these bugs has been polite, courteous, and even helpful with solutions.

The reason for the error in this package was that the "LD = ${CC}" line was missing. Don't know how, but it was. Fixed, and tested

PS: If you _really_ need to get a hold of me ( like a packaging error in [extra] ) please directly email me. I try to check the forums regularly, but it's hard with so many posts these days. The bug tracker is a good way too.

If your mirror wont have the packages, they are:
http://people.cs.vt.edu/~codemac/dmenu-1.8-1.pkg.tar.gz
http://people.cs.vt.edu/~codemac/wmii-3 … pkg.tar.gz

PeteMo · 2007-01-10 11:39:49

Codemac,

Everybody makes mistakes from time to time, so no sweat there. What I appreciate and thank you for is your response and speed in determining the problem, fixing it, and pushing out an updated pkg.

Thanks.

russ816 · 2007-01-19 18:09:20

harlekin wrote:

Control-h)
    echo -n "+0 +0 -48 +0"|wmiir write /view/sel/sel/geom;;

Is this supposed to work? I haven't been able to get it to. Is their another work around?

harlekin · 2007-01-19 22:53:17

It doesn't work with 3.5 anymore. It worked with the prior version. I don't know how to handle this with the current wmii. You can resize the Windows using MOD + RightClick (and moving your mouse) but I'd like to resize my windows using my keyboard. Does anyone know how I can do that?

PeteMo · 2007-01-19 23:50:03

It seems that the /view directory no longer exists in 3.5 Does anyone know of any documentation for the new version? The only stuff I can find on the wmii website applies to 3.1 only.

harlekin · 2007-01-20 11:09:51

I found this and I guess it is applying to wmii-3.5 but I cannot make sense out of it. I cannot find where app's geometry is saved. It may be handled different in 3.5?

http://suckless.org/~denisg/spec_3.7

PeteMo · 2007-01-20 13:40:54

From the wmii-3.7 spec linked above:

/tag/<tag>/index
    Reading index outputs the layout of the view belonging to the tag:
        # ~ <floating_area_width> <floating_area_height>n
        ~ <client_id> <x_y_width_height> <client_props>n
        ~ <...>n
        # <column_number> <column_width> <column_height>n
        <column_number> <client_id> <y> <height> <client_props>n
        <...>n
    Writing is not allowed.

Note: I added the underscores to make the text show up correctly in the forums.

These directories seem to exist and also to contain the information described above, so although they are for 3.7 it appears that they may apply to 3.5 as well. If you look at the last line, however, it appears that changing the client geometry via a keyboard shortcut is not possible.

Oin · 2007-01-22 15:40:54

I'm sorry if this has been discussed already, i must have missed it.

How do you people manage using wmii and say irssi at the same time while using Alt for MOD1? do you change all the other keymaps to use something other than Alt for MOD (i know i'd have to change irssi, my browser and gaim, just to name a few), or do you switch the MOD1 for wmii.
And if you do, what do you change it to? ctrl? winkey? (i've seen some keybindings in wmii-ruby which use the winkey already)

harlekin · 2007-01-22 16:07:38

I just switched accessing my irssi channels with ESC as MODKEY instead of ALT. At least for the windows 1 to 10. From 11 I can juse ALT again.

Another - I guess really senseless - thing I noticed is, that I can communicate with irssi if capslock is activated. Somehow irssi still responds to alt but wmii doen't.

Oin · 2007-01-22 16:50:52

Wow the CAPS key really works wonders, it even works with firefox!
thanks!

hope it's a feature, not a bug, so it never gets fixed

PeteMo · 2007-01-22 19:02:28

You can also use ctrl-p or crtl-n to cycle irssi windows (p = previous, n = next)

lateralus_ · 2007-02-19 17:08:30

Hi all,

I have some problems to get ruby-wmii working.
My wmii version is 3.5.1-3 and I have try with both the darcs version and the 0.3.1 version of ruby-wmii.
After running the installation of ruby-wmii (ruby install.rb), the $HOME/.wmii-3 is created.
However, when I first start wmii, a new empty directory $HOME/.wmii-3-5 is also created, disabling the other one

How can I solve this problem ?

Thanks in advance

Celti · 2007-02-20 06:48:32

ruby-wmii doesn't support wmii 3.5.1.

I poked Mauricio about this a while ago, he says he'll release a version for wmii 3.6. This may take a few weeks, though, as wmii development has hit a slight snag and we're back to snapshots instead of a new rc.

Arch Linux

#126 2007-01-08 19:36:08

Re: The wmii thread

#127 2007-01-08 20:43:44

Re: The wmii thread

#128 2007-01-08 23:19:27

Re: The wmii thread

#129 2007-01-09 05:40:54

Re: The wmii thread

#130 2007-01-09 06:35:21

Re: The wmii thread

#131 2007-01-09 15:20:04

Re: The wmii thread

#132 2007-01-09 15:33:26

Re: The wmii thread

#133 2007-01-09 15:41:19

Re: The wmii thread

#134 2007-01-09 17:38:06

Re: The wmii thread

#135 2007-01-10 04:35:20

Re: The wmii thread

#136 2007-01-10 04:48:40

Re: The wmii thread

#137 2007-01-10 05:03:29

Re: The wmii thread

#138 2007-01-10 05:15:12

Re: The wmii thread

#139 2007-01-10 11:39:49

Re: The wmii thread

#140 2007-01-19 18:09:20

Re: The wmii thread

#141 2007-01-19 22:53:17

Re: The wmii thread

#142 2007-01-19 23:50:03

Re: The wmii thread

#143 2007-01-20 11:09:51

Re: The wmii thread

#144 2007-01-20 13:40:54

Re: The wmii thread

#145 2007-01-22 15:40:54

Re: The wmii thread

#146 2007-01-22 16:07:38

Re: The wmii thread

#147 2007-01-22 16:50:52

Re: The wmii thread

#148 2007-01-22 19:02:28

Re: The wmii thread

#149 2007-02-19 17:08:30

Re: The wmii thread

#150 2007-02-20 06:48:32

Re: The wmii thread

Board footer