#1092 closed defect (fixed)
mupdf not responding to key events
Reported by: | Jiang | Owned by: | Jiang |
---|---|---|---|
Priority: | critical | Milestone: | 0.17 |
Component: | client | Version: | trunk |
Keywords: | Cc: |
Description
This is probably a minor problem peculiar to this particular program, but perhaps the underlying bug is implicated in other problems, too.
The program in question is an extremely fast pdf reader called mupdf
http://mupdf.com/
I downloaded the program from the website and compile it. I use it to quickly peek a pdf document.
In version 0.15, I can use the usual keyboard shortcuts to resize the window (e.g. + or -) reload the page (r) etc. However, none of these single key shortcuts work in 0.16.
I don't see any error in the log on the server or client side.
My systems are 64 bit 0.16.1-1 beta, released on Dec. 30 2015, on Ubuntu 14.04, both installed from the beta .deb files from the xpra website (thank you for keeping us trusty people afloat with these beta packages!) I am using rgb raw images with lz4 compression.
As I said, I have only observed the problem with mupdf, but not many other programs use single key shortcuts so this may affect other things as well.
Also, it appears 0.16 branch has much better-behaved audio and the audio-video sync is much better, just as promised! Thank you for these improvement!
Change History (6)
comment:1 Changed 6 years ago by
Status: | new → assigned |
---|
comment:2 Changed 6 years ago by
Priority: | major → critical |
---|
comment:4 Changed 6 years ago by
Owner: | changed from Antoine Martin to Jiang |
---|---|
Status: | assigned → new |
comment:5 Changed 6 years ago by
Resolution: | → fixed |
---|---|
Status: | new → closed |
This defect is fixed in the latest beta. Thank you for that!
However, mupdf is still not behaving properly as before or as under forwarded X11 window. I've filed a new ticket #1097.
comment:6 Changed 16 months ago by
this ticket has been moved to: https://github.com/Xpra-org/xpra/issues/1092
Thanks for reporting this!
Confirmed.
With 0.15.x server (client version makes no difference):
With 0.16:
Bar some logging differences, the steps look identical.
xev shows identical events:
So I suspect that the problem is not in the keyboard layer but maybe focus related instead.
One way to identify the problem would be to bisect it...