tadas-s / android-xserver

Automatically exported from code.google.com/p/android-xserver
0 stars 0 forks source link

can't start xterm #18

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. Start X-Server
2. xterm -display 192.168.0.54:0
3. crash

What is the expected output? What do you see instead?

X Error of failed request:  BadLength (poly request too large or internal Xlib 
length error)
  Major opcode of failed request:  72 (X_PutImage)
  Serial number of failed request:  310
  Current serial number in output stream:  312

What version of the product are you using? On what operating system?

Please provide any additional information below.

Original issue reported on code.google.com by iamstupi...@gmail.com on 11 Dec 2012 at 7:22

GoogleCodeExporter commented 8 years ago
I experienced this same problem (only the IPs and serial numbers of the 
requests were different).  I used the same steps as the other user, with the 
following details:

1. I started the X-Server ver 1.13 on my Samsung Galaxy Tab (Model number 
GT-P7500).
2. I ran `xterm -display 192.168.0.6:0.0 &` on my Windows 7 box in a Cygwin 
terminal.
3. I expect to see a xterm open on my Galaxy Tab.  Instead, the X Server 
becomes slow for a while (pointer doesn't move around as quickly) and does not 
display any window, until finally I receive the same error listed by the 
previous user.  It comes out on stderr in my Cygwin terminal.

Thanks to anyone who solves the issue!

Original comment by tlane...@gmail.com on 12 Dec 2012 at 3:04

GoogleCodeExporter commented 8 years ago
You have to use the -fn option to indicate the font. I just use "xterm -fn 
fixed". You can see a list of available fonts in the file 
XServer/src/au/com/darkside/XServer/Font.java.

Original comment by pierrezu...@gmail.com on 14 Mar 2013 at 12:58

GoogleCodeExporter commented 8 years ago
Thanks, but no joy.  I still get a crash.

I do note it complaining about fonts, now you mention it, though.

I enter:
xterm -fn fixed -display 192.168.0.6:0.0

It says:
Warning: Missing charsets in String to FontSet conversion

It waits a bit, and continues as above:
X Error of failed request:  BadLength (poly request too large or internal Xlib 
length error)
  Major opcode of failed request:  72 (X_PutImage)
  Serial number of failed request:  416
  Current serial number in output stream:  418

Original comment by tlane...@gmail.com on 14 Mar 2013 at 4:05