-
Notifications
You must be signed in to change notification settings - Fork 342
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for logging on unix like systems from the console. #7
Comments
ill see what I can compile. |
Ok, so what arm arch are you trying to run on? v6, v7? Hardfloat? Raspberry Pi? |
It´s an Raspberry Pi root@raspberrypi ~ # uname -a |
Can you grab the following two java properties from your jvm: System.getProperty("os.name"); |
root@raspberrypi ~ # java test |
Well that makes things really interesting. I need a way to tell what version of the arm processor I am dealing with from Java. Is this the openjdk or oracle? I was hoping os.arch would be closer to armv6 or armv6j. Does os.version, java.vendor or java.version have anything arch identifying? Also how much do you know about compiling for arm? I am interested in how the oracle jrm is arm v6/v7, does - |
I think I may have a solution, it may take a day or two. |
Try this binary out: https://drive.google.com/file/d/0BzIKwDqIyYGkVEt1a3RZTUtoakE/edit?usp=sharing Its untested but it will hopefully work with armv6j. Sorry about google drive, but apparently I cant attach binary files to github bugs. |
Were you able to test the attached zip? |
I tested the attached file but returned the error, you can check please? Error: |
Hmm, I tested last night and it seemed to run fine for me on RASPBIAN Wheezy. What arm chip are you using? Are you able to compile from source? Do you have the complete dump available? |
I tried starting the code does not compile, but I can try, just do not have much experience in native code, you can pass me the commands to compile? dump: Chip: |
Depending on your distribution you will probably need -dev packages for libXt libX11 libXtst. You wil also need autotools, autoreconf, and ant. You can build a working jar with Does the jar produce any console output? The problematic line is likely: https://github.com/kwhat/libuiohook/blob/f1f2de864c9d5ae55e40fb273b90cf960ddf6d16/src/x11/system_properties.c#L54 I am wondering if XOpenDisplay failed? |
console output: JNativeHook: Global keyboard and mouse hooking for Java. JNativeHook is free software: you can redistribute it and/or modify JNativeHook is distributed in the hope that it will be useful, You should have received a copy of the GNU Lesser General Public License
|
I'm not working with desktop, only via console, can it be the cause of XOpenDisplay failed? |
oh yes! It requires and active X11 session to function, although there should be a check(s) for XOpenDisplay failures to avoid segfaults. I would probably need to use the kernel event interface or evdev. I am not sure what kind of permission workaround are going to be needed. Some more info: https://kernel.googlesource.com/pub/scm/linux/kernel/git/legion/kbd/+/2.0.2/src/dumpkeys.c I will fix the issue with the XOpenDisplay segfaults, but its going to be a while before I can even take a look at supporting console input. Your free to hack around on your own. Any amount of information gathering helps. |
Hey, So I stumbled on this project while digging around on github: https://github.com/xoeye/evdev-java/compare/progman32:master...master It should do close to what you need until I can integrate full evdev support. |
Thanks for the help, I tried to use but returned the error below, know how to solve? EventDevice: System: arm . A fatal error has been detected by the Java Runtime Environment: Detail: |
My best guess, the binary you are using, the one packaged with the repo, was compiled with gprof support but your system doesn't have some dependency it needs. Try recompile the binary src without the -pg flag. |
This should be working at this point, please open a new bug if it is still an issue. |
I would like to see this
The text was updated successfully, but these errors were encountered: