10-13-2016, 10:30 PM
(10-13-2016, 07:37 AM)RaimundEge Wrote: Have you checked this log file:
~/.altdrive-wbhome/ui.log ?
Yeah, it's empty (0 bytes long), though if I delete it and rerun the client script, it gets recreated. Content does get written there if I run the client-console executable, but unfortunately it's not possible to configure AltDrive from that.
I (and AltDrive support) assumed initially that this was an issue with an incompatible version of SWT, but I was able to run an example SWT app using that JAR (and I confirmed it's the same version they depend on), so I don't think that's it. And it's hard to tell what it's doing, because it exits too quickly for me to get a profiler or a debugger with a breakpoint attached (even with suspend=y, it still exits before the breakpoint goes active), and thread dumps haven't told me much that's useful. So I was hoping that maybe there was something you'd forgotten to list in your steps (or something you'd previously done to the Pine's OS) that might explain why it worked for you but not for me.