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 795721 - Strange behaviour with left mouse button click
Strange behaviour with left mouse button click
Status: RESOLVED DUPLICATE of bug 794723
Product: evolution
Classification: Applications
Component: Mailer
3.28.x
Other Linux
: Normal normal
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2018-05-01 16:20 UTC by Michael Jarosch
Modified: 2018-05-03 11:49 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Michael Jarosch 2018-05-01 16:20:22 UTC
Package: evolution
Version: 3.28.1-2
Severity: normal

--- Please enter the report below this line. ---
Dear Maintainer,

I used the template from debians "reportbug", 'cause it contained some infos you might find interesting…

To my problem: If I'm marking a text (with mouse or by setting the cursor to a start- or end-point and complete it with keyboard) and left-click to another position in the text, the marked text disappears and can't be restored (via [CTRL]-Z or sth like that).
Additionally, (without marking anything) if I scroll to a point, where the cursor's not visible anymore and left-click into a text (f.e. to edit sth), the cursor won't go where I clicked. (It goes to another position between the former 
one and the one I clicked to.)

If this is meant as a feature, please, change that to make evolution behave like any other graphical editor out there. Thanks!

--- System information. ---
Architecture: 
Kernel:       Linux 4.15.0-3-amd64

Debian Release: buster/sid
  500 trusty          ppa.launchpad.net 
  500 testing         httpredir.debian.org 

--- Package information. ---
Depends                      (Version) | Installed
======================================-+-=============
libc6                        (>= 2.14) | 
libcamel-1.2-61            (>= 3.28.1) | 
libclutter-gtk-1.0-0       (>= 0.91.8) | 
libecal-1.2-19             (>= 3.28.1) | 
libedataserver-1.2-23      (>= 3.28.1) | 
libevolution               (>= 3.28.1) | 
libevolution                 (<< 3.29) | 
libglib2.0-0               (>= 2.46.0) | 
libgtk-3-0                  (>= 3.0.0) | 
libical3                    (>= 3.0.0) | 
libnotify4                  (>= 0.7.0) | 
libsoup2.4-1                 (>= 2.42) | 
libwebkit2gtk-4.0-37        (>= 2.5.3) | 
libxml2                     (>= 2.7.4) | 
evolution-common          (= 3.28.1-2) | 
evolution-data-server      (>= 3.28.1) | 
evolution-data-server        (<< 3.29) | 
dbus                                   | 
psmisc                                 | 


Recommends                         (Version) | Installed
============================================-+-===========
evolution-plugins                            | 3.28.1-2
evolution-plugin-bogofilter                  | 3.28.1-2
 OR evolution-plugin-spamassassin            | 
evolution-plugin-pstimport                   | 3.28.1-2
yelp                                         | 3.28.1-1


Suggests                            (Version) | Installed
=============================================-+-===========
evolution-ews                                 | 
evolution-plugins-experimental                | 
gnupg                                         | 2.2.5-1
network-manager                               | 1.10.6-3
Comment 1 André Klapper 2018-05-02 08:43:37 UTC
Which exact version of libwebkit2gtk is installed?
Comment 2 Michael Jarosch 2018-05-02 08:55:24 UTC
aptitude says 2.20.1-1

Forgot to mention: It doesn't matter if you choose html or plain text. The editor behaves the same.
Comment 3 Milan Crha 2018-05-03 06:31:04 UTC
Thanks for a bug report. This had been reported already and it is fixed in gtk+, thus I mark this as a duplicate of the previous bug report.

*** This bug has been marked as a duplicate of bug 794723 ***
Comment 4 Michael Jarosch 2018-05-03 09:28:30 UTC
I know, it's my fault sticking two issues together and not filing 2 bugreports. But I thought it was somehow related… Maybe it is… Do you think, a new gtk+-version will also fix the "the cursor won't go where I click"-problem?
Comment 5 Milan Crha 2018-05-03 11:49:44 UTC
I do not know, I'm not the gtk+ developer. You'll see when you get gtk+ with that fix included. After that, if still reproducible, you can file a new bug report. I've older versions of both gtk+ and webkitgtk+, and they are not affected with this.