> Based on the packages updated, this seems to be an X server related issue
> indeed. I'd say it's either the server itself (there might have been changes
> in the order in which events/requests are processed, causing some deadlock
> in the processing either of pointer motion events or of display refresh
> requests), or the intel driver (because the bug only hits when rotated!).
> The wacom driver would have been another candidate normally, but since the
> bug has been reported by others to happen even when drawing with a mouse,
> it's not too likely.

My laptop gets hit with the bug even when non-rotated.

> Question: does the bug still appear if you run "xournal --sync" instead of
> the usual? (This makes X server calls synchronous, so in case the issue is a

the bug is still there when running xournal with --sync

> conflict between event processing and rendering requests, this might
> help...). If --sync fixes the bug, can you further assess whether adding the
> line
>
> gdk_display_sync(gdk_display_get_default());
>
> at the place where you inserted the printf() would be sufficient (perhaps
> with a lower performance cost than --sync, since it'd synchronize things
> only in the motion event processing code) ?
>

--dmg

------------------------------------------------------------------------------
Achieve unprecedented app performance and reliability
What every C/C++ and Fortran developer should know.
Learn how Intel has extended the reach of its next-generation tools
to help boost performance applications - inlcuding clusters.
http://p.sf.net/sfu/intel-dev2devmay
_______________________________________________
Xournal-devel mailing list
Xournal-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xournal-devel

Reply via email to