bwhmather / wmii

Automatically exported from code.google.com/p/wmii
MIT License
0 stars 1 forks source link

wmiir blocks in read /event --> wmii does not react to any events #235

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. start wmii
2. wmii does not react to any user input

What is the expected result? What do you see instead?
Expected: Main event loop should start processing events that are read via 
"wmiir read /event").
Actual: wmiir never returns from "wmiir read /event", instead it blocks forever

What version of the product are you using (wmii -v)? On what operating
system (uname -a)?
wmii-hg2786+, libixp 141 (latest tips)
Linux x 2.6.37-gentoo-r4 #1 SMP Sat Apr 30 14:08:23 CEST 2011 i686 Intel(R) 
Core(TM) Duo CPU L2500 @ 1.83GHz GenuineIntel GNU/Linux

Please provide any additional information below.

I'm quite lost here, since current tips seem to work for everyone else...
The problem can also be reproduced by running a pair of "wmiir read /event" and 
"echo foo | wmiir write /event" commands. "foo" arrives in wmiir (I verified by 
debug prints inside wmiir), but wmiir does not return after that and waits 
forever for more data to come.

I tracked this down inside libixp - the actual blocking appears in
transport.c:mread(), when invoking "r = thread->read(fd, msg->pos, n);"

Version 3.9.2 does work fine, also the test with with the "wmii read/write 
pair" works fine with that.

$HOME/.wmii* has been wiped for all tests.

Is there any fundamental thing that I overlooked during install/build? (Well... 
same steps work fine for 3.9.2 at least).

Original issue reported on code.google.com by a...@fractal9.net on 1 May 2011 at 2:20

GoogleCodeExporter commented 9 years ago
Try setting your LANG=C, as suggested in this thread:
http://thread.gmane.org/gmane.comp.misc.suckless/5302

Original comment by sun...@gmail.com on 1 May 2011 at 6:11

GoogleCodeExporter commented 9 years ago
Thank you, the locale was indeed the problem here. With a UTF-8 setting for 
LC_CTYPE, everything works fine. Phew.

Original comment by a...@fractal9.net on 1 May 2011 at 9:02

GoogleCodeExporter commented 9 years ago

Original comment by sun...@gmail.com on 19 Sep 2011 at 7:56

GoogleCodeExporter commented 9 years ago
This issue was closed by revision 1d200a866939.

Original comment by maglion...@gmail.com on 20 Sep 2011 at 3:45