Just out of curiosity I tried how amorad works over an ssh connection.
Besides many "Invalid event!" messages, I had a few strange hangs which may
or may not be related to the ssh-tunnel. I'll later try to sort out what's
causing them and what not.
The Setup:
* Nokia E51 with amora 1.1 beta
* EeePC with Debian Lenny and amora 1.1 (svn rev. 552) and debug messages
patch from Savago.
* Workstation with Debian Etch, three monitors (one DISPLAY on each, so
no xinerama), and FVWM with virtual desktops as window manager.
Setting up the ssh connection:
On the workstation I ssh'ed to the EeePC, starting amorad on the EeePC with
$DISPLAY (via ssh) set to the workstation's left screen.
Several different usages failed by hanging up something:
A simple screen shot of the xterm the ssh with amorad was running
succeeded, but afterwards (until I killed amorad from another shell on the
EeePC) FocusFollowsMouse didn't work anymore, neither could I change the
virtual desktop. And keyboard input was delayed until amorad was killed,
but everything I typed until then got inserted after amorad was killed.
Using the FVWM pager, you can focus windows not on your current desktop. I
did this and tried a screen shot then. The same happend as before, except
that (1) the screenshot didn't appear and amorad issues the following error
messages after killing it with SIGINT:
failed screen capture: cap!
: Resource temporarily unavailable
Invalid event!
failed screen capture: cap!
: Resource temporarily unavailable
Invalid event!
Additionally, amorad didn't notice anymore if a client exited after one of
these issues. (No appropriate message about the client exiting.)
Since this is a very unusual setup, I initially set the priority of this
issue to low. Will raise it as soon as I notice some of the issues in here
also happen in more usual setups.
Original issue reported on code.google.com by axel.bec...@gmail.com on 16 Jul 2008 at 5:21
Original issue reported on code.google.com by
axel.bec...@gmail.com
on 16 Jul 2008 at 5:21