Thanks a lot for helping.
I found a solution. I have written a shell script which I start using desktop
manager:
[Desktop Entry]
Name=/home/pi/xcsoar-start.sh
Exec=xcsoar
Type=Application
This script starts a tty and xcsoar:
lxterminal -e 'xcsoar -fly'
Then it works!
> XCSoar 6.8 reads all user input directly from /dev/input/* devices,
> and that does not require a TTY; that is much more robust. However,
> it needs permission to access these devices, and it must have
> exclusive access.
That brings me to my next problem: compiling xcsoar on a raspberry. I will ask
in an other mail for this problem.
Thanks
Dirk
Gesendet von unterwegs.
> Am 23.07.2014 um 01:27 schrieb [email protected]:
>
> Send Xcsoar-user mailing list submissions to
> [email protected]
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.sourceforge.net/lists/listinfo/xcsoar-user
> or, via email, send a message with subject or body 'help' to
> [email protected]
>
> You can reach the person managing the list at
> [email protected]
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Xcsoar-user digest..."
>
>
> Today's Topics:
>
> 1. Re: Volkslogger (Max Kellermann)
> 2. Thermal assistant Inforbox (Ramy Yanetz)
> 3. XCSoar and autostart on Raspberry (Dirk Jung)
> 4. Re: XCSoar and autostart on Raspberry (Max Kellermann)
> 5. Re: XCSoar and autostart on Raspberry (Martin Gregorie)
> 6. Re: XCSoar and autostart on Raspberry (Folken)
> 7. Re: XCSoar and autostart on Raspberry (Martin Gregorie)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Mon, 23 Jun 2014 20:51:07 +0200
> From: Max Kellermann <[email protected]>
> Subject: Re: [Xcsoar-user] Volkslogger
> To: "[email protected]" <[email protected]>
> Cc: "[email protected]"
> <[email protected]>
> Message-ID: <[email protected]>
> Content-Type: text/plain; charset=us-ascii
>
>> On 2014/06/23 20:40, "[email protected]" <[email protected]> wrote:
>> Thanks. Is that only true for the Volkslogger or for any logger that
>> requires the baud rate to be adjusted for declaration and download?
>
> If the logger requires changing the baud rate, but your adapter can't
> change the baud rate, it won't work. Does this really need further
> explanation?
>
>
>
> ------------------------------
>
> Message: 2
> Date: Sun, 20 Jul 2014 20:31:41 -0700
> From: Ramy Yanetz <[email protected]>
> Subject: [Xcsoar-user] Thermal assistant Inforbox
> To: "[email protected]"
> <[email protected]>
> Message-ID:
> <[email protected]>
> Content-Type: text/plain; charset="iso-8859-1"
>
> FWIW I thought I should share with XCSoar users my experience with the
> thermal assistant.
>
> I admit I didnt think I needed a thermal assistant and never used one with
> Winpilot and XCSoar before, especially since I didnt want my map to be
> replaced with the thermal assistant whenever I am thermaling.? but recently I
> noticed that it is also available as an infobox, and since I had place for an
> extra infobox in my thermal page I figured I will give it a try. I found out
> that if I am completely focused it wouldnt tell me more than the vario, the
> trace and the seat of my pants tells me, but sooner or later I am loosing
> some focus, especially later in the flight when getting tired, and this is
> when the thermal assistant is a huge help. It makes finding the core so much
> easier. 9 out of 10 times it would take me back to the core with one circle.
> Just follow the instructions in the manual how to use it and you will find it
> works very well.?
>
> Just my 2 cents,
>
> Ramy
> -------------- next part --------------
> An HTML attachment was scrubbed...
>
> ------------------------------
>
> Message: 3
> Date: Tue, 22 Jul 2014 12:23:42 +0200
> From: Dirk Jung <[email protected]>
> Subject: [Xcsoar-user] XCSoar and autostart on Raspberry
> To: [email protected]
> Message-ID: <[email protected]>
> Content-Type: text/plain; charset="windows-1252"
>
> Hi guys,
>
> hopefully someone can helps me. I got two problems with running XCSoar on my
> Raspberry Pi:
>
> ? If I use a script to start XCSoar (6.7.5) when I starting the Raspberry,
> XCSoar crashes. I use the following script at /home/pi/.config/autostart:
> [Desktop Entry]
> Name=XCSoar
> Exec=xcsoar
> Type=Application
>
> ? If I use xcsoar -fly in /etc/rc.local XCSoar starts perfekt, but I can't
> control using the keyboard. I have to quit and restart XCSoar at a terminal
> using xcsoar -fly, then the keyboard works perfekt
>
> Thanks for helping!
> Dirk
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: signature.asc
> Type: application/pgp-signature
> Size: 203 bytes
> Desc: Message signed with OpenPGP using GPGMail
>
> ------------------------------
>
> Message: 4
> Date: Tue, 22 Jul 2014 19:36:47 +0200
> From: Max Kellermann <[email protected]>
> Subject: Re: [Xcsoar-user] XCSoar and autostart on Raspberry
> To: Dirk Jung <[email protected]>
> Cc: [email protected]
> Message-ID: <[email protected]>
> Content-Type: text/plain; charset=us-ascii
>
>> On 2014/07/22 12:23, Dirk Jung <[email protected]> wrote:
>> Hi guys,
>>
>> hopefully someone can helps me. I got two problems with running XCSoar on my
>> Raspberry Pi:
>>
>> ? If I use a script to start XCSoar (6.7.5) when I starting the
>> Raspberry, XCSoar crashes. I use the following script at
>> /home/pi/.config/autostart:
>> [Desktop Entry]
>> Name=XCSoar
>> Exec=xcsoar
>> Type=Application
>
> A crash is a bug and should be reported to the bug tracker. However,
> I'm not sure if that is really a crash. You should provide more
> information when you write the ticket.
>
>> ? If I use xcsoar -fly in /etc/rc.local XCSoar starts perfekt, but I
>> can't control using the keyboard. I have to quit and restart XCSoar at a
>> terminal using xcsoar -fly, then the keyboard works perfekt
>
> XCSoar 6.7 reads keyboard input from the current TTY, therefore it
> must be run on a TTY.
>
> XCSoar 6.8 reads all user input directly from /dev/input/* devices,
> and that does not require a TTY; that is much more robust. However,
> it needs permission to access these devices, and it must have
> exclusive access.
>
> Max
>
>
>
> ------------------------------
>
> Message: 5
> Date: Tue, 22 Jul 2014 20:17:50 +0100
> From: Martin Gregorie <[email protected]>
> Subject: Re: [Xcsoar-user] XCSoar and autostart on Raspberry
> To: [email protected]
> Message-ID: <[email protected]>
> Content-Type: text/plain; charset="UTF-8"
>
>> On Tue, 2014-07-22 at 12:23 +0200, Dirk Jung wrote:
>> ? If I use xcsoar -fly in /etc/rc.local XCSoar starts perfekt, but I
>> can't control using the keyboard. I have to quit and restart XCSoar at a
>> terminal using xcsoar -fly, then the keyboard works perfekt
>>
> Thats's not surprising. rc.local is run as a root process at boot time,
> so any programs started by it will also run as root, which you almost
> certainly did not intend or want. Its usual purpose is to modify global
> settings, e.g. changing access permissions for /dev/ttyS* and/or to
> start site-specific servers or utilities that, for some reason, can't be
> run as normal system services. It is *NOT* intended to start user
> programs because these should never be run as root and anyway, as you
> found out, a normal user will not be able to use their i/o channels.
>
> If you want to start a program when you login to a particular user you
> should either use services provided by the desktop manager (Gnome, XFCE,
> Cinnamon, etc) or, if you don't need to start a desktop manager, you can
> start it from the .bash_profile in the user's home directory.
>
> The fact that XCSoar crashes when you try to make the desktop manager
> start it suggests that that environment is not providing something it
> needs. For instance, is XCSoar really crashing or is it just the manager
> not being able to find XCSoar? Things to check and do:
>
> - Is the directory containing XCSoar in $PATH? If not, you need
> to change .bash_profile so it adds that directory to $PATH
>
> - Does it work if you use an absolute pathname for XCSoar? That type of
> program launcher often ignores $PATH and so an absolute path name is
> required.
>
> - write a bash script to start XCSoar and also load add diagnostic
> statements into it such as:
>
> pwd
> which XCSoar
> echo $USER
> echo $PATH
>
> and run it from the command line. When its working properly, tell the
> desktop manager to run the script at login time. If the diagnostic
> displays differ, add statements to the script to fix the differences
> until XCSoar does run.
>
>
> Martin
>
>
>
>
>
>
>
> ------------------------------
>
> Message: 6
> Date: Wed, 23 Jul 2014 00:17:37 +0200
> From: Folken <[email protected]>
> Subject: Re: [Xcsoar-user] XCSoar and autostart on Raspberry
> To: [email protected]
> Message-ID: <[email protected]>
> Content-Type: text/plain; charset="utf-8"
>
>> On Tue, Jul 22, 2014 at 08:17:50PM +0100, Martin Gregorie wrote:
>>> On Tue, 2014-07-22 at 12:23 +0200, Dirk Jung wrote:
>>> ? If I use xcsoar -fly in /etc/rc.local XCSoar starts perfekt, but I
>>> can't control using the keyboard. I have to quit and restart XCSoar at a
>>> terminal using xcsoar -fly, then the keyboard works perfekt
>> and run it from the command line. When its working properly, tell the
>> desktop manager to run the script at login time. If the diagnostic
>> displays differ, add statements to the script to fix the differences
>> until XCSoar does run.
>
> To this i'd like to add that most distributions log to a file called
> .xsession-errors in your home directory. Usually errors on failing
> programs should be displayed in there.
>
> I run xcsoar with i3-wm. In this wm i only have to specify
> exec /opt/xcsoar/bin/xcsoar
> in .i3/config in my homedirectory
>
> Cheers,
> - Folken
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: not available
> Type: application/pgp-signature
> Size: 819 bytes
> Desc: Digital signature
>
> ------------------------------
>
> Message: 7
> Date: Wed, 23 Jul 2014 00:27:28 +0100
> From: Martin Gregorie <[email protected]>
> Subject: Re: [Xcsoar-user] XCSoar and autostart on Raspberry
> To: [email protected]
> Message-ID: <[email protected]>
> Content-Type: text/plain; charset="UTF-8"
>
>> On Wed, 2014-07-23 at 00:17 +0200, Folken wrote:
>>> On Tue, Jul 22, 2014 at 08:17:50PM +0100, Martin Gregorie wrote:
>>>> On Tue, 2014-07-22 at 12:23 +0200, Dirk Jung wrote:
>>>> ? If I use xcsoar -fly in /etc/rc.local XCSoar starts perfekt, but I
>>>> can't control using the keyboard. I have to quit and restart XCSoar at a
>>>> terminal using xcsoar -fly, then the keyboard works perfekt
>>> and run it from the command line. When its working properly, tell the
>>> desktop manager to run the script at login time. If the diagnostic
>>> displays differ, add statements to the script to fix the differences
>>> until XCSoar does run.
>>
>> To this i'd like to add that most distributions log to a file called
>> .xsession-errors in your home directory. Usually errors on failing
>> programs should be displayed in there.
>>
>> I run xcsoar with i3-wm. In this wm i only have to specify
>> exec /opt/xcsoar/bin/xcsoar
>> in .i3/config in my homedirectory
>>
> In case you wondered, I was being deliberately non-distro-specific whe I
> wrote that because, although I have a RaspberryPi I haven't done much
> with it and I run it headless over SSH from one of my Fedora-based Linux
> machines using XFCE.
>
> Consequently I know nothing about the RPi's desktop manager, or what
> that might be capable of in the way of debugging. If it uses the system
> logger to output diagnostics that may well be lost on an out-of-the box
> install because detail that gets logged is minimal, probably to avoid
> hammering the SD card the machine uses as its main fs.
>
>
> Thermals,
> Martin
>
>
>
>
>
>
>
>
> ------------------------------
>
> ------------------------------------------------------------------------------
> Want fast and easy access to all the code in your enterprise? Index and
> search up to 200,000 lines of code with a free copy of Black Duck
> Code Sight - the same software that powers the world's largest code
> search on Ohloh, the Black Duck Open Hub! Try it now.
> http://p.sf.net/sfu/bds
>
> ------------------------------
>
> _______________________________________________
> Xcsoar-user mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/xcsoar-user
>
>
> End of Xcsoar-user Digest, Vol 95, Issue 1
> ******************************************
------------------------------------------------------------------------------
Want fast and easy access to all the code in your enterprise? Index and
search up to 200,000 lines of code with a free copy of Black Duck
Code Sight - the same software that powers the world's largest code
search on Ohloh, the Black Duck Open Hub! Try it now.
http://p.sf.net/sfu/bds
_______________________________________________
Xcsoar-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/xcsoar-user
