After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 794630 - After scrolling, clicking to set the cursor position jumps back
After scrolling, clicking to set the cursor position jumps back
Status: RESOLVED OBSOLETE
Product: evolution
Classification: Applications
Component: Composer
3.26.x (obsolete)
Other Linux
: Normal normal
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
https://gitlab.gnome.org/GNOME/gtk/is...
Depends on:
Blocks:
 
 
Reported: 2018-03-23 16:51 UTC by Tanu Kaskinen
Modified: 2018-03-27 10:56 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
yesterday's package update log (7.00 KB, text/plain)
2018-03-23 16:51 UTC, Tanu Kaskinen
Details

Description Tanu Kaskinen 2018-03-23 16:51:21 UTC
Created attachment 370058 [details]
yesterday's package update log

Distribution: Debian testing
Evolution version: 3.26.5-1+b1

Scrolling in the composer stopped working properly recently. I'm pretty sure this happened after yesterday's package update. I'll attach the aptitude log that shows which packages were updated (evolution was not one of them, so maybe the bug is somewhere lower in the stack).

When I scroll in the composer (plain text mode) and then click to set the cursor position, the text area jumps back to roughly where it was before starting to scroll. It seems that the jump is done to bring the old cursor position into view - if I scroll down and click, the topmost line in the new view is the line where the old cursor position was. After the jump, the new cursor position is set according to wherever the mouse happens to point in the new view.

PS. Even worse composer bug has appeared after yesterday's update too: sometimes text gets seemingly randomly deleted just by left-clicking in the text area. I don't have exact steps to reproduce this, so let's ignore that for now.
Comment 1 Tanu Kaskinen 2018-03-23 16:54:39 UTC
Oh, I forgot to mention: starting evolution with GDK_BACKEND=x11 makes the composer work fine again, so this is somehow specific to wayland. (I knew to try that, because gnumeric's scrolling has been even more broken for a while now, and I found that workaround from some bug report.)
Comment 2 Tanu Kaskinen 2018-03-24 07:29:49 UTC
Hmm, gedit has started to exhibit similar behaviour...
Comment 3 Tanu Kaskinen 2018-03-26 08:21:11 UTC
There's a gtk bug report now: https://gitlab.gnome.org/GNOME/gtk/issues/132
Comment 4 Daniel Boles 2018-03-27 10:56:19 UTC
Thanks. Let's use that one!