This bug happens in the same way on my system.
The bug occurs for both armel and armhf debian on an Android tablet,
running side-by-side with the android system.
I also live in emacs. There is no vnc4server in the arm distributions,
so I am out of luck. Running tightvncserver by itself also works
for me, as reported before. But I can't find a useful client
for what I need.
The bug occurs both for an android client on the tablet as
well as the kde client on the desktop connected to
xrdp on the tablet.
I do have a slightly closer to minimal example, listed below, as well
as a clue to a fix, but not a fix: Maybe it is some kind of race
condition.
Below, I call nanosleep or XtAppAddTimeOut.
Bug occurs if xtime_out is 1 or 1000.
Bug occurs if the argument to nanosleep
is 100 usec, but *not* if it is greater than
or equal to 900 usec.
------------
xrdp 0.6.1-1 armhf
tightvncserver 1.3.9-6.4 armhf
Linux version 3.4.39-perker-3+ (peter@crunchbang)
(gcc version 4.6.x-google 20120106 (prerelease)
(GCC) ) #1 SMP PREEMPT
------------
#include <X11/Xlib.h>
#include <X11/Shell.h>
#include <X11/Xaw/Box.h>
#include <stdlib.h>
#include <unistd.h>
#include <stdio.h>
#include <time.h>
void timeout(XtPointer p, XtIntervalId* i)
{
exit(0);
}
int main(int argc, char* argv[])
{
struct timespec ts;
ts.tv_sec = 0;
// ts.tv_nsec = 900 * 1000;
ts.tv_nsec = 100 * 1000;
int xtime_out = 1000; // in ms
XtAppContext context;
Widget top;
Widget box;
Display* dpy;
top = XtVaAppInitialize(&context, "ClearCutBuffers",
0, 0, &argc, argv, NULL,NULL);
dpy = XtDisplay(top);
XStoreBuffer(dpy, "", 0, 0);
XtAppAddTimeOut(context, xtime_out, timeout, 0);
// while (nanosleep(&ts, &ts) != 0);
XtAppMainLoop(context);
return 0;
}
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
