JFYI: The new keycodes (r656) work for me.
Axel Beckert
just read Savago's log message at
http://code.google.com/p/amora/source/detail?r=656
At least on my EeePC with X.org 7.4 (from Debian unstable) the new
keycodes (left, right, delete) work fine. Didn't even know the delete
key of my E51 has some function in amora. :-)
Haven't though tested the old keycodes.
I though had one strange crash of amorad (1.2) where the process
vanished, but the shell didn't return to the prompt and neither Ctrl-C
nor Ctrl-Z nor Ctrl-Q (in case I typed Ctrl-S accidentially) helped
anything. Had to close the xterm. But since I had other problems with
the bluetooth stack too after suspend and resume, I guess it could be
related to this:
!520 Z11 ?255 L1 abe@nemo:pts/2 (-zsh) 14:06:36 [~] > amorad
closing socket...
: Address already in use
build_bluetooth_socket error!
: Address already in use
!520 Z12 ?255 L1 abe@nemo:pts/2 (-zsh) 14:09:09 [~] >
Regards, Axel
--
Axel Beckert - a...@deuxchevaux.org, a...@noone.org - http://noone.org/abe/
Adenilson Cavalcanti
Thanks for confirming that the xevent codes changed. Since I'm running
Ubuntu 8.10 in a macbook, I was somewhat suspecting that my hardware
could be the reason for this behavior.
Concerning your other comment, amora server will try to create a
bluetooth socket and export a service (i.e. serial port) using SDP. If
the same channel used by amora is in use, it will abort the startup
and exit. Currently I use channel 16 for that.
But amora should not crash in this case, if it did, it is a bug and we
got to trace it and fix. Can you reproduce this bug and maybe collect
a backtrace?
Best regards
Adenilson
Axel Beckert
On Tue, May 26, 2009 at 01:12:47PM -0300, Adenilson Cavalcanti wrote:
> Concerning your other comment, amora server will try to create a
> bluetooth socket and export a service (i.e. serial port) using SDP. If
> the same channel used by amora is in use, it will abort the startup
> and exit. Currently I use channel 16 for that.
I expect that there was already an amorad running in that case. At
least I later found a running amorad arguing about a lost connection
when I closed all windows to shut the computer down. Thought I had
overview over my xterms when I wrote the mail but I guess I hadn't.
> But amora should not crash in this case,
That was before. A running and working amorad suddenly stopped working
(i.e. no commands from the mobile phone caused anything anymore but
the phone didn't argue about a lost connection either) and when I
looked for the process it was gone while the xterm still showed it.
> if it did, it is a bug and we got to trace it and fix. Can you
> reproduce this bug and maybe collect a backtrace?
Unfortunately not, but as soon as I hit it again, I'll try to find out
what was common with the first case.