kumabook/stickynotes

Does not work in linux/X11

Closed this issue · 3 comments

It appears to me that much of the basic functionality of stickynotes does not work on linux/X11. The following items do not work at all, or do not work properly, although on Windows10 they all work perfectly.

  1. generate sticky will place the sticky in lower left corner of the webpage, therefore often out of sight, rather than under cursor.
  2. move sticky with mouse1 does not work at all.
  3. resize sticky with mouse1 shows signs of working but the dragged out shape does not last.

These problems may be the reason why some users have reported in their review that the stickynotes "does not work at all".

Praise: I like very much the fact that you use sqlite with json export/.import, and that you have search functionality. It would be even nicer if I could set the location of the sqlite file to some arbitrary location outside the PROFILE directory.

Thanks for your reporting
Could you tell me linux OS version?
I'm gonna create linux environment and reproduce the bugs.

I checked manjaro linux 16.10 and gnome, but it works.

I discovered some new information: Stickynotes works well in another FF instance/profile in the same linux/X11 setup! Hence it is not the platform per se, but something else that is going on. I''m doing some more experiments to see if I can figure out what is the difference between the two profiles, if any.


The information you asked for may not be so relevant anymore, but here it is:

fedora 23, X11,twm with driver+kernel as follows.
X11 driver i915
filename: /lib/modules/4.8.13-100.fc23.x86_64/kernel/drivers/gpu/drm/i915/i915.ko.xz
Linux i4770 4.8.13-100.fc23.x86_64 #1 SMP Fri Dec 9 14:51:40 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

I now have stickynotes working also in the linux/X11 FF profile that previously caused trouble. I'm not sure what made the difference. It may have been some other "web annotation" extension that I was testing that conflicted somehow, but that I have since disabled. Sorry I have not been able to pin down exactly what the cause was. I'm going to close this one now.