glegris / android-xserver Goto Github PK

What steps will reproduce the problem?
1. try to start $program
2. in 90% of the cases, "Xlib:  extension "SHAPE" missing on display 
"192.168.2.103:0"." is the error

I'm running 1.05 on Android 4.0.3 on Eee Pad Transformer TF101

On a sk17 (se xperia mini pro) at least, the windows seem to be drawn outside 
the canvas of the app, leaving only what seems like a portion of _whatever_ 
being pushed to the server (lxde wm, single apps etc).

(be advised, this is when running some chrooted stuff on the actual device, by 
"export DISPLAY=localhost:0.0")

running xdpyinfo tells me 
dimensions: 480x320 pixels
resolution: 194x194 dots per inch

so dimensions seem to be ok. That leaves resolution.

The ability to tweak either or both would be wonderful!

What steps will reproduce the problem?
xmodmap -pke
xmodmap -e 'keycode 114 = Control_L'
xmodmap -pke
 You would expect more than one line in the 3rd command output.

xmodmap -e 'add/remove/clear ...'
 No effect (not implemented)

This is on the git version.

I've implemented (I hope) modifier-map and fixed xmodmap -e 'keycode ... = ...'.

I've succeeded (on a ASUS Transformer) setting up a control key and closing an 
xterm using Ctrl-D.

I has tablet PC without any mouse, trackpad, etc.
How can I emulate clicking on mouse buttons?

What steps will reproduce the problem?
1.
2.
3.

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


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


Please provide any additional information below.

What steps will reproduce the problem?
1.Installing the app

What is the expected output? What do you see instead?
I'm trying to install this application on Android 2.1 (APIv7), but the package 
is not supported by system (syntax error)

What version of the product are you using? On what operating system?
Android 2.1-update1

Please provide any additional information below.

What steps will reproduce the problem?
1. x2x -east -to xxx.xxx.xxx.xxx:0

Result: display xxx.xxx.xxx.xxx:0 does not support the test extension

I guess the file Xext/xtest.c should be translated in java to Xext/Xtest.java 
and the file Xext/Extensions.java updated.

The effort of converting if should be quite low and the outcome would be to use 
the XServer on android as a remote screen to an actual computer (as with x2x).

This would allows a user to use mouse and keyboard on the android XServer and 
to quickly "send" a windows from a local screen onto the android screen.
This can be practical to transform your phone/tablet into an additional screen.

What steps will reproduce the problem?
1. start android-xserver
2. start xfe with display directed at android xserver

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

Display mostly correct but greyed-out icons missing.
Multiple errors reported to xfe console... BadLength (poly request too large or 
internal Xlib length error)

What version of the product are you using? On what operating system?
xfe running on ubuntu 12.04.
android-xserver 1.11 running on nexus 7.

Please provide any additional information below.


Greyed out icons seem to be delivered as format 2 (zpixmap) images with a depth 
of 1... but the image is delivered as a series of nibbles. Not so far found 
good documentation on why this happens.

The images are then delivered to the display using copyPlane which wasn't 
working due to the colour selection code... The original images were created 
with fg and bg colours which were at the time both white.

Attached is a version of Drawable.java which some changes to...

processPutImage
---------------
Check for nibble format images
Write images with black and white pixels

copyPlane
---------
Use translucent as background
Use foreground for white pixels

Changes are not rigorous but do correct display issues for xfe. It is of course 
possible suggested changes damage display of other applications.

What steps will reproduce the problem?
1. Java used signed values for all types, the x protocol uses unsigned types.
2. If a request with length greater than 0x7fff is received, it will be 
interpreted as negative.
3. Lots of places in the code check that the request length is not smaller than 
a value.
4. If the value is negative it will send an error to the client when it should 
not.
5. Could cause any number of problems.

http://code.google.com/p/android-xserver/source/browse/XServer/src/au/com/darksi
de/XServer/Client.java#220

Change this line from:

_inputOutput.writeShort ((short) 0xffff); // Max request length.

to:

_inputOutput.writeShort ((short) 0x7fff); // Max request length.

This will prevent clients from sending too large requests. If this reduces 
performance, implement BIG-REQUEST extension:

after enabling BIG-REQUEST (need to assign it a major opcode which will be 
negative in java, >127 in x protocol, reply to all requests with this opcode as 
in http://www.x.org/releases/X11R7.6/doc/bigreqsproto/bigreq.html),

http://code.google.com/p/android-xserver/source/browse/XServer/src/au/com/darksi
de/XServer/Client.java#244

check if this value is zero, if it is read an integer from the next 4 bytes 
(this is all the extension does). 

What steps will reproduce the problem?
1. DISPLAY=192.168.2.103:0 twm

What is the expected output? What do you see instead?
i expect twm to behave normally, but twm creates an infinite numer of windows 
until i press ^C in the terminal i started twm

What version of the product are you using? On what operating system?
1.05 on Android 4.0.3 on Eee pad transformer TF101

Please provide any additional information below.
twm version 1:1.0.6-1 (Ubuntu 11.10)

What steps will reproduce the problem?
1. Start X server
2. Attempt to run most any X application

What is the expected output? What do you see instead?
Expected output is for application to display and be usable.  Actual output is 
usually that the application almost start and then crashes.


What version of the product are you using? On what operating system?
I have version 1.02 on a Motorola xoom running ICS.

Please provide any additional information below.
That is all.

See 
http://www.centos.org/docs/5/html/5.1/Installation_Guide/s2-trouble-remotex.html
 for information on this.

The X server basically connects to a login server and runs a session on the 
remote machine, the session being forwarded over X11 protocols. This can also 
occur over SSH for security.

Adding this to configuration would allow mini-Android sticks to operate as full 
remote Linux clients. Oh, the money to be saved!

What steps will reproduce the problem?
1.Opening of GUI applications crashes the XServer 
2.
3.

What is the expected output? What do you see instead?
The expected output is visualize Interactive GUI of other linux executables 
like xclipboard and Jars on XServer.

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


Please provide any additional information below.
Issue in running GUI based jar application:
Hey , I have launch and tested xclock, xeyes and xterm GUI in the X-Server from 
my application , but not able to run a jar file having single jbutton 
component, even not able to run other linux based GUI executables. with it i 
just want to ask that can we set the position of the xclock , xterm GUI?? 
please help me out as soon as possible, give the information about it. Is there 
any alternate way to run it???

What steps will reproduce the problem?
1. DISPLAY=192.168.1.111:0 lxsession
2. Force close of XServer
3. Try any other session manager

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

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


logcat:
04-12 21:00:38.713 E/AndroidRuntime(2910):  at 
au.com.darkside.XServer.XServer.destroyClientResources(XServer.java:579)
04-12 21:00:38.713 E/AndroidRuntime(2910):  at 
au.com.darkside.XServer.Client.processKillClientRequest(Client.java:828)
04-12 21:00:38.713 E/AndroidRuntime(2910):  at 
au.com.darkside.XServer.Client.processRequest(Client.java:749)
04-12 21:00:38.713 E/AndroidRuntime(2910):  at 
au.com.darkside.XServer.Client.doComms(Client.java:255)
04-12 21:00:38.713 E/AndroidRuntime(2910):  at 
au.com.darkside.XServer.Client.run(Client.java:124)
04-12 21:00:38.713 W/ActivityManager(20633):   Force finishing activity 
au.com.darkside.XServer/au.com.darkside.XDemo.XServerActivity
04-12 21:00:40.733 I/ActivityManager(20633): Process au.com.darkside.XServer 
(pid 2910) has died.
04-12 21:00:41.763 I/ActivityManager(20633): Starting activity: Intent { 
act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] 
flg=0x10200000 
cmp=au.com.darkside.XServer/au.com.darkside.XDemo.XServerActivity } from pid 
20763
04-12 21:00:41.823 I/ActivityManager(20633): Start proc au.com.darkside.XServer 
for activity au.com.darkside.XServer/au.com.darkside.XDemo.XServerActivity: 
pid=2939 uid=10226 gids={3003}
04-12 21:01:01.313 E/AndroidRuntime(2939):  at 
au.com.darkside.XServer.Drawable.processGetImageRequest(Drawable.java:293)
04-12 21:01:01.313 E/AndroidRuntime(2939):  at 
au.com.darkside.XServer.Drawable.processRequest(Drawable.java:208)
04-12 21:01:01.313 E/AndroidRuntime(2939):  at 
au.com.darkside.XServer.Pixmap.processRequest(Pixmap.java:130)
04-12 21:01:01.313 E/AndroidRuntime(2939):  at 
au.com.darkside.XServer.Client.processRequest(Client.java:382)
04-12 21:01:01.313 E/AndroidRuntime(2939):  at 
au.com.darkside.XServer.Client.doComms(Client.java:255)
04-12 21:01:01.313 E/AndroidRuntime(2939):  at 
au.com.darkside.XServer.Client.run(Client.java:124)
04-12 21:01:01.313 W/ActivityManager(20633): Process au.com.darkside.XServer 
has crashed too many times: killing!
04-12 21:01:01.313 W/ActivityManager(20633):   Force finishing activity 
au.com.darkside.XServer/au.com.darkside.XDemo.XServerActivity
04-12 21:01:01.353 I/WindowManager(20633): WIN DEATH: Window{40cf3cc0 
au.com.darkside.XServer/au.com.darkside.XDemo.XServerActivity paused=true}
04-12 21:02:48.663 D/HomeLoaders(2965): Application(184): 
ApplicationInfo{4056baf0 au.com.darkside.XServer}
04-12 21:02:48.673 D/HomeLoaders(2965): Add to appinfoCache 
ResolveInfo{4056b968 au.com.darkside.XDemo.XServerActivity p=0 o=0 m=0x108000}, 
icon=0 android.graphics.drawable.BitmapDrawable@40668108

This issue is 100% repeatable on Android 4.2.1 (Nexus 7).

To reproduce:
1. Start the XServer.
2. Run urxvt.  I'm using the binary from the `rxvt-unicode` package in Ubuntu 
12.04, armhf port.  (The issue also appears with xterm, but it's far more 
obvious with urxvt, since it requests a Unicode font.)

This causes an ANR dialog (trace attached).

The problem is the implementation of Font.processQueryFontRequest.  For fonts 
with non-ASCII characters, it will make up to 65K calls to Android's 
Paint.getTextBounds, which in turn calls a native method.  This native method 
does not appear to be fast.  For the first few calls on an ASCII font it 
returns in 26 µs (on a Tegra3), but eventually ramps up to the 1-2ms range for 
a Unicode font.  At even 1ms/call it'll take 65 seconds to transmit font 
metrics.

(It *almost* looks O(n) in the character you request!  Haven't inspected the 
code to verify this.)

While the XServer is collecting this font data, it's holding a lock to the 
client I/O object.  The UI thread also takes this lock.  Thus, the font 
handling will starve the UI thread.

I'm poking around in the Android API trying to find a more efficient way of 
computing metrics for large fonts, but haven't seen anything obvious just yet.

What steps will reproduce the problem?
1. start X server
2. export display
3. start gnome-session
4. start Firefox from console
5. Firefox chrashes
6. log sais thatr RANDR extention is missing.
What is the expected output? What do you see instead?
That it works.

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

Please provide any additional information below.

What steps will reproduce the problem?
1. Buy an asus transformer with keyboard
2. start any x app from the x server (I'm running ubuntu locally)
3. find a text box, type some text then try to delete using the backspace key

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

nothing happened

What version of the product are you using? On what operating system?
1.3 I think, android 4.0

Please provide any additional information below.

that's it

What steps will reproduce the problem?
  1. Start android-xserver on emulator
  2. run "export DISPLAY=127.0.0.1:0". WM will use android-xserver
  3. run "adb forward tcp:6000 tcp:6000". Adb forward to a-xserver
  4. run a window manager. For example, wmaker (WindowMaker).

What is the expected output? 
  No errors for X_PutImage code.

What do you see instead?
  /usr/lib/WindowMaker/WindowMaker warning: internal X error: BadLength   (poly request too large or internal Xlib length error)
    Request code: 72 X_PutImage
    Request minor code: 0
    Resource ID: 0x0
    Error serial: 1622

What version of the product are you using? On what operating system?
  Git version. OS: Linux

Please provide any additional information below.
  Error was generated for Drawable.processPutImage on 

    if (bytesRemaining != n + pad) {
      io.readSkip(bytesRemaining);

    // I changed resource ID to another value to find this line.

      ErrorCode.write(client, ErrorCode.Length, RequestCode.PutImage, 0); 
      return false;
    }

What steps will reproduce the problem?
1. Fire up a terminal (I used urxvt)
2. Install enlightenment
3. Try to type enlightenment_start
4. Try to erase the line with ^u

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

Typing enlightenment_start creates the string enlightenmentt_start, with no way 
to type the t without typing another t.  I was able to try enlightenment_start 
by tab completing, but if it had not been for my tab key, I would still be 
wondering if enlightenment can run here.

Similarly, typing ctrl+u to kill the line always repeated whatever character I 
typed before pressing ctrl.  The ctrl did not register, I might have had better 
luck with Esc+U but I didn't try it.

What version of the product are you using? On what operating system?
1.03 on Transformer TF-101 with JellyBean 4.2 (EOS4) Nightly 92

Please provide any additional information below.
The terminal is very slow to paint with anti-aliased fonts.  I did not try 
other fonts, there are too many problems to consider using this ongoing in its 
current state.  It seems though far superior to running X11vnc and accessing it 
through AndroidVNC client.  Kudos.

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

Changed Bad-Match logic to check against the Drawable's actual depth.
Also, made code slightly easier to read.  Drew attention to a possible bug, but 
did not intentionally make any other change to operation (I can't test, so I 
can't prove it's really a bug).

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

Fix 2 race conditions:
1: in case of Extended request size, the bytesRemaining was wrong
2: 12 bytes read too much in case of RequestCode.CreatePixmap,
   this did mess up further requests, XServer seems to hang

hi ,i am a new here. i want to ask a question,how to use this app? i has 
installed it,and the connectbot.when i exec "xeyes",there are nothing on the 
screen. who can tell me how to use it? 

What steps will reproduce the problem?
1. start any x app linked to x server
2. although the mouse cursor moves both via my mousepad and touchscreen
3. neither longerpress, or clicking / doublie clicking on the touchscreen / 
mouse pad work
4. instead i have to click first  then use the volume controls to do a proper 
click

What is the expected output? What do you see instead?
expected similar mouse and touchscreen style mouse functionlaity as on android, 
e.g. long click to click, hold and drag to click and drag touchpard on my asus 
transformer to work for mouse clicks

I can't see this being hard to implement, with some kind of hot key to ungrab 
the muse if need be.

What version of the product are you using? On what operating system?
1.3 on android 4.0

Please provide any additional information below.

What steps will reproduce the problem?
1. Install App
2. Connect USB mouse 
3. Start App

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

I expected to use the USB mouse normally. Instead, the X server didn't react to 
mouse movements. 

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

I'm using version 1.09 on Android 4.0.4.

Please provide any additional information below.

I'm using a standard USB mouse through the Samsung USB adapter on a Samsung 
Galaxy S3.

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.

What steps will reproduce the problem?
1. install x server for android via play market
2. install archlinux in chroot
3. install and run a windowmanager, i.e fluxbox, icewm.
4. set DISPLAY to localhost:0 and run icewm

What is the expected output? What do you see instead?
I hoped to see fluxbox running in the window, instead I got the error message:

[johan@localhost /]$ openbox
Openbox-Message: Unable to make directory '/data/.cache/openbox': Permission 
denied
Obt-Message: XKB extension is not present on the server or too old
Obt-Message: Xinerama extension is not present on the server
Obt-Message: XRandR extension is not present on the server
Obt-Message: X Sync extension is not present on the server or is an 
incompatible version
XIO:  fatal IO error 12 (Cannot allocate memory) on X server "localhost:0"
      after 124 requests (124 known processed) with 0 events remaining.

What version of the product are you using? On what operating system?
I'm running android 4.0.3 on a Transformer Prime tf201.
X server is version 1.11

Please provide any additional information below.
All the window managers seem to fail with the same message, fatal
io error 12 cannot allocate memory.

What steps will reproduce the problem?
1. start a KDE APP

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

The output of the app on the tablet.

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

Latest from Play Store.

Please provide any additional information below.

X Error: BadDrawable (invalid Pixmap or Window parameter) 9
  Major opcode: 62 (X_CopyArea)
  Resource id:  0x0
gwenview(21627)/nepomuk (library): Could not find virtuoso to connect to. 
Aborting 
gwenview(21627)/nepomuk (library): Could not find virtuoso to connect to. 
Aborting 
gwenview(21627)/nepomuk (library): Could not find virtuoso to connect to. 
Aborting 
gwenview(21627)/kdeui (kdelibs): Attempt to use QAction "edit_redo" with 
KXMLGUIFactory! 
gwenview(21627)/kdeui (kdelibs): Attempt to use QAction "edit_undo" with 
KXMLGUIFactory! 
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
  Major opcode: 62 (X_CopyArea)
  Resource id:  0x0
gwenview(21627) Gwenview::ViewMainPagePrivate::setCurrentView: No index found 
for current view 
Xlib:  extension "SYNC" missing on display "192.168.0.102:0.0".

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

Make it possible to start XServer into portrait or landscape mode.
The default was unchanged: landscape.
If the file /sdcard/XServer/config exists,
it is checked for one line:
orientation=portrait
(or orientation=landscape) and XServer started accordingly.

When checking if an extension is implemented, currently searches in the values 
instead of the keys.

http://code.google.com/p/android-xserver/source/browse/XServer/src/au/com/darksi
de/XServer/XServer.java#658

if (_extensions.contains (s))

Should read:

if (_extensions.containsKey (s))

This can be seen if you use xdpyinfo (or another program that can dump 
information about an xserver). containsKey will allow the dummy extension to be 
reported as supported.

What steps will reproduce the problem?
1. Run gnome-terminal on the android-xserver.
2.
3.

What is the expected output? What do you see instead?
Expect 'normal' execution, instead an Error is sent as size of resource is 
incorrectly calculated. (calculated as 3*width*height bytes when the resource 
sent by gnome-terminal is width*height/8 bytes). I have no idea if this is 
correct behaviour by gnome-terminal but everything seems to run correctly when 
the following line is changed: 

http://code.google.com/p/android-xserver/source/browse/XServer/src/au/com/darksi
de/XServer/Drawable.java#885

Line reads:
                        if (depth != 32 || leftPad != 0)

To fix this, change to:

            if ((depth != 32 && depth!=1) || leftPad != 0)

The following code to handle a Bitmap will also handle this ZPixmap with depth 
of 1.

Minor cleanup of magic number, and make it so string would show correct port 
number, if the number were ever to change (hope I didn't miss any 6000's, not 
having my vim search function).

What steps will reproduce the problem?
1. Running Open Grid Scheduler on a 4.1.1 Android Tablet
2. I have also tried to run fvwm before, but it also crashes before running 
qmon (the graphical app from Open Grid Scheduler)
3. I can run it without problem with my Windows laptop and Xming X server.

What is the expected output? What do you see instead?
administrador@hpcserver:~$ qmon
XIO:  fatal IO error 11 (Resource temporarily unavailable) on X server 
"172.25.80.180:0.0"
      after 76 requests (76 known processed) with 0 events remaining.
administrador@hpcserver:~$

I have also tried running before fvwm (fvwm -d xxx.xxx.xxx.xxx:0) but it 
crashes:

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

Please provide any additional information below.

What steps will reproduce the problem?
1. start x server
2. pop open some window (I've tried mostly with gnuplot, using python 
matplotlib)

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

The window should fill up the X app area.
Instead, the window seems to be drawn partly outside, like if it's double the 
size (in x and y) than it should. I'm suspecting some dpi stuff/confusion.

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

I'm using cyanogen mod 9.1 with an xperia mini pro.

This patch creates preferences to make movements into drags and to make arrow 
keys work like arrows instead of buttons.  Making movements into drags allows 
you to click and drag items by touch.  Making arrows keys work like arrows 
makes it easier to run applications that use arrow keys.  The patches also 
implement control and alt on the hacker's keyboard.
The patches change the application name to XServerWB so that the patched 
version can be installed in parallel with the original version.  I can make a 
new version without the name change if necessary.

What steps will reproduce the problem?
1. Use with connectbot and connect with ssh over an IPv6 only network. Ssh will 
connect, but cannot open x applications
2. Try to input IPv6 address in access control.
3.

What is the expected output?
Accept IPv6 address

What do you see instead?
Not possible to type IPv6 address. Not possible to paste IPv6 address

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


Please provide any additional information below.