[pid 29795] open("/dev/input/js0", O_RDONLY) = 16
[pid 29797] <... select resumed> ) = 1 (out [14], left {0, 795000})
[pid 29795] ioctl(16, JSIOCGAXES <unfinished ...>
[pid 29797] write(14, <STUFF DELETED>[pid 29795] <... ioctl resumed> , 0xbfffe46f) = 0
[pid 29797] <... write resumed> ) = 1024
[pid 29795] ioctl(16, JSIOCGBUTTONS <unfinished ...>
[pid 29797] select(15, NULL, [14], NULL, {0, 800000} <unfinished ...>
[pid 29795] <... ioctl resumed> , 0xbfffe46f) = 0
[pid 29797] <... select resumed> ) = 1 (out [14], left {0, 800000})
[pid 29795] ioctl(16, 0x80806a13 <unfinished ...>
[pid 29797] write(14, <STUFF DELETED>[pid 29795] <... ioctl resumed> , 0xa9f2c84) = 36
[pid 29797] <... write resumed> ) = 1024
[pid 29795] fcntl64(16, F_SETFL, O_RDONLY|O_NONBLOCK <unfinished ...>
[pid 29797] select(15, NULL, [14], NULL, {0, 800000} <unfinished ...>
[pid 29795] <... fcntl64 resumed> ) = 0
[pid 29797] <... select resumed> ) = 1 (out [14], left {0, 800000})
[pid 29795] ioctl(16, JSIOCGCORR <unfinished ...>
<STUFF DELETED>
[pid 29795] <... ioctl resumed> , 0xbfffe470) = 0
[pid 29797] <... write resumed> ) = 1024
[pid 29795] ioctl(16, JSIOCSCORR <unfinished ...>
[pid 29797] select(15, NULL, [14], NULL, {0, 800000} <unfinished ...>
[pid 29795] <... ioctl resumed> , 0xbfffe470) = 0
[pid 29795] brk(0xb040000) = 0xb040000
[pid 29795] --- SIGSEGV (Segmentation fault) @ 0 (0) ---
[pid 29797] <... select resumed> ) = 1 (out [14], left {0, 800000})
<STUFF DELETED>
[pid 29796] <... futex resumed> ) = -1 EINTR (Interrupted system call)
[pid 29797] +++ killed by SIGSEGV +++
PANIC: handle_group_exit: 29797 leader 29795
[pid 29796] +++ killed by SIGSEGV +++
PANIC: handle_group_exit: 29796 leader 29795
+++ killed by SIGSEGV +++# jstest /dev/input/js0 It all seems OK.
# js_demo /dev/input/js0 Also OK.
# jscal /dev/input/js0 Joystick has 7 axes and 12 buttons. Correction for axis 0 is broken line, precision is 0. Coeficients are: 127, 127, 5534751, 5534751 Correction for axis 1 is broken line, precision is 0. Coeficients are: 127, 127, 5534751, 5534751 Correction for axis 2 is broken line, precision is 0. Coeficients are: 127, 127, 5534751, 5534751 Correction for axis 3 is broken line, precision is 0. Coeficients are: 127, 127, 5534751, 5534751 Correction for axis 4 is broken line, precision is 0. Coeficients are: 127, 127, 5534751, 5534751 Correction for axis 5 is broken line, precision is 0. Coeficients are: 0, 0, 536870912, 536870912 Correction for axis 6 is broken line, precision is 0. Coeficients are: 0, 0, 536870912, 536870912
# fgjs Found 2 joystick(s) Joystick 0 has 7 axes Joystick 1 has 3 axes Move the control you wish to use for elevator
Assigned axis 1 on joystick 0 to control elevator Press any button for next control
After moving the elevator, I get no response from any of the buttons/controls. If I use any other control first, other than the elevator, no responses from anything. I discount the hardware as the problem as jstest and js_demo work.
Regards
Sid.
Bohnert Paul wrote:
I had the same problem.
As a nonroot user fgfs would error;
"Unable to open aircraft directory"
Thanks for the strace hint.
I found in the Aircraft directory. The following
directories had the wrong permissions.
Spitfire Spitfire/Sounds Spitfire/Models
Group and user were not allowed to read.
Later, Paul
--- Sid Boyce <[EMAIL PROTECTED]> wrote:
Jeremy Johnson wrote:
SimGear-0.3.7 FlightGear-0.9.6 In linux as a normal user I get the following
error message
user:~$ fgfs --show-aircraft Unable to open aircraft directory.
But as root: root:~# fgfs --show-aircraft
Available aircraft: 737 Boeing 737 747 Boeing 747 (YASim) 747-100 Boeing 747-100
(JSBSim)
<--cut-->
All the files in /usr/shre/FlightGear seem to be
readable by all:
user:~$ ls -l /usr/share | grep FlightGear drwxr-xr-x 29 root root 4096 Nov 7 23:53
FlightGear
user:~$ ls -l /usr/share/FlightGear | grep
Aircraft
drwxr-xr-x 44 root root 4096 Nov 7 23:24
Aircraft
Also I get the following segmentation faults with
various splash screen errors
user:~$ fgfs
Object PanelInstruments not found
Object ControlsGroup not found
Error in loading splash screen texture /usr/share/FlightGear/Textures/Splash5.rgb
Segmentation fault
user:~$ fgfs
Object PanelInstruments not found
Object ControlsGroup not found
Error in loading splash screen texture /usr/share/FlightGear/Textures/Splash2.rgb
Segmentation fault
user:~$ fgfs
Object PanelInstruments not found
Object ControlsGroup not found
Error in loading splash screen texture /usr/share/FlightGear/Textures/Splash4.rgb
Segmentation fault
user:~$ fgfs
Object PanelInstruments not found
Object ControlsGroup not found
Error in loading splash screen texture /usr/share/FlightGear/Textures/Splash5.rgb
Segmentation fault
_______________________________________________ Flightgear-users mailing list [EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-users
2f585eeea02e2c79d7b1d8c4963bae2d
I'm seeing similar, but I haven't yet got around to
running it with strace to see where it's looking for stuff. I used
to see the splash screen, then it would segfault, now I only see the
outline of the splash screen, the morse code beeps are just an incoherent
string of dits.
# fgfs
Object PanelInstruments not found
Object ControlsGroup not found
Segmentation fault
Regards Sid. -- Sid Boyce .... Hamradio G3VBV and keen Flyer =====LINUX ONLY USED HERE=====
-- Sid Boyce .... Hamradio G3VBV and keen Flyer =====LINUX ONLY USED HERE=====
_______________________________________________ Flightgear-users mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d
