Description of problem: In the process of editing an email message to send, the cursor randomly jumps to the end of the message - mid-typing. This occurs: in every message composed (as a reply), in both plain-text or HTML composition, multiple times in longer messages, it occurs on both laptops and desktops (as reported at forums.fedoraforum.org) Version-Release number of selected component (if applicable): evolution-3.18.3-1.fc23.x86_64 How reproducible: Within evolution reply to a message, after you start typing in the message window at random times the cursor will jump to the end of the message. This behavior is independent of the message window size; even if the message window is small the cursor jumps to the end of the message (so you have to scroll back to your place). This happens in every message I respond to, and often multiple times within the same response. However, today as a test, I tried writing three new messages (NOT a reply to an email - start a new email message), and I did not see this behavior. I have observed this cursor jumping behavior every time I reply to a message, this is 30+ messages. There are no other applications with this problem, that I have observed. Steps to Reproduce: 1. In evolution, reply to an email 2. start typing, the jumps do not happen immediately; you may have to type several lines. 3. The jumps sometimes occur after I resume typing after a pause, but mid-word. Actual results: Expected results: Additional info: This cursor jumping began after I upgraded to Fedora 23 (using the dnf system-upgrade). It has persisted over two fc23 kernels (current: kernel-4.2.8-300.fc23.x86_64 ) My system: I am using the XFCE desktop This is a desktop machine that has been very stable across 6 versions of Fedora. AMD Phenom II X6 processor 8 GB DDR3 RAM
I'm seeing this, too, in GNOME. I see that this bug has been marked as closed upstream. I take it the fixed upstream version will be pushed to Fedora 23 some time soon...?
For me it happens exactly afeter 60 seconds and I don't have to type anything. Reporuduced like this: 1. click reply 2. wait 60 seconds 3. cursor jumps to end of message I do have an exchange account as well as one gmail and a plain account.
The 60 seconds timeout leads to the message autosave. I tried to reproduce it here, under GNOME and under a different Desktop Environment, but no luck, the cursor stays where I left it. I thought it's something with the CSS changes (evo had similar issues in the preview panel), but it doesn't matter too (I moved away from the composer window under GNOME Shell, which uses different colors, thus requires redraw of the view). It can depend on the settings in the composer window, like signatures, digital signing, attachments, .... I do not know what all. I tried with auto-generated signature, but it still didn't cause the issue. Edit->Preferences->Composer Preferences settings might be also interesting. The bug is cloned upstream, thus the best to move the investigation there, if possible for you.
Hi Milan I have the same issue and it's been bugging me! Whever I reply to a message I end up typing and suddenly am at the bottom of the message, often multiple times. I agree with Smola that it happens after 60 seconds. In my settings, I DO have a proper signature. I have selected: - Format messages in HTML - Automatically insert emoticons - Keep signature above the original message on replying. - I have two languages for spell checking (English South Africa and Afrikaans South Africa) - All confirmations are checked If this has been fixed, will it be pushed to Fedora 23? Thanks!
This has to be pushed to 23 because composer window is almost unusable, unless you write quick an brief replies. Also, I couldn't find any setting to turning off the autosave or at least to extend it. I tweaked almost all the settings for the composer window, reply top/bottom etc... I don't know how to get to the "upstream bug", wherever that is. TIA
The thing is that neither me nor Tomas can reproduce this locally. I used the settings from comment #4, set a signature for the account and hit reply to none quite long message. Then I clicked few lines below the top, in a quoted part of the message and pressed Enter to break it into two parts. Then I left the window as is, without any interaction from my side. I return back to the window and the cursor, together with the scrollbar position, is where I left it.
(In reply to Smola from comment #5) > I don't know how to get to the "upstream bug", wherever that is. You can click the bug ID at the top, in the External Trackers section. It is: http://bugzilla.gnome.org/show_bug.cgi?id=759873
Evolution just updated to evolution-3.18.4-1.fc23.x86_64. It is still doing this.
Louis, could you capture a video where it'll be shown from the time you open the composer to the time where the cursor position changes, please? I couldn't reproduce this, thus I hope it'll give me some insight (maybe it's also related to the desktop environment and used theme, I do not know). Feel free to send the video only to me, to my bugzilla email address, just reference this bug report in the subject, otherwise I could overlook it in my spam folder. Ideally if you give it on some web space and send only the link to it, but I do not know whether you've anything like that available.
Thanks Smola for the screen capture. It helped, I am able to reproduce it here now. My settings: Reply style: Inline (Outlook style) Everything else is off in the Composer general preferences, except of the option for "sign if signed GPG or S/MIME". The steps: a) stay on a one-line HTML message (I've the one from Smola) b) press Ctrl+R c) if asked whether to lose formatting, choose No (it doesn't ask in the Smola's capture, because he has "Format messages in HTML") d) do nothing - composer opens with the cursor at the very top, the line which reads "Original Message" with leading "-" and trailing "-". e) after ~a minute the cursor jumps from the beginning to the end of the message. Using "Reply Style: Quoted" doesn't exhibit the issue, even I noticed a little cursor flash, most likely in the time when it would end at the end of the message.
I can confirm that using "Reply Style: Quoted" fixes this behaviour.
*** Bug 1303482 has been marked as a duplicate of this bug. ***