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 795184 - regression: 3.28.1 broke loading drafts, mailto:?body=foo and reply/forward styles inline/quoted
regression: 3.28.1 broke loading drafts, mailto:?body=foo and reply/forward s...
Status: RESOLVED FIXED
Product: evolution
Classification: Applications
Component: Composer
3.28.x
Other Linux
: Normal blocker
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2018-04-12 05:12 UTC by Paul Wise
Modified: 2018-04-12 12:16 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Paul Wise 2018-04-12 05:12:42 UTC
I can no longer use the inline/quoted styles for reply/forward. They both result in empty emails in the composer.

Opening drafts no longer fills out the mail body.

This command no longer fills out the mail body:

evolution mailto:?body=foo

These happened when I upgraded from evolution 3.28.0-4, evolution-data-server 3.28.0-3 to evolution/eds 3.28.1-1 with webkit2gtk 2.20.1-1 under GNOME 3.28 on Debian buster.

When I click reply/forward/mailto/drafts I get this error on the command-line:

** (evolution:10269): CRITICAL **: 13:10:52.640: void webkit_web_view_load_bytes(WebKitWebView*, GBytes*, const char*, const char*, const char*): assertion 'bytesDataSize' failed

When I close the window I get this message:

(evolution:10269): module-webkit-editor-WARNING **: 13:11:09.017: (/build/evolution-mVbd86/evolution-3.28.1/src/modules/webkit-editor/e-webkit-editor.c:5398):webkit_editor_finalize: runtime check failed: (g_queue_is_empty (priv->post_reload_operations))

If I save the message as a draft, there is no text in the mail.
Comment 1 Paul Wise 2018-04-12 05:48:08 UTC
It seems to have also broken pasting into emails and signatures.
Comment 2 André Klapper 2018-04-12 08:26:33 UTC
Were you on webkit2gtk 2.20.1-1 before upgrading to 3.28.1?
Comment 3 Paul Wise 2018-04-12 12:00:05 UTC
Initially I was on webkit2gtk 2.20.0-2, evolution 3.28.0-4 and got the bug. Then I upgraded evolution to 3.28.1-1 and got the bug. Then I upgraded webkit2gtk to 2.20.1-1 and still got the bug. Then I downgraded evolution to 3.28.0-4 and the bug was gone.
Comment 4 Paul Wise 2018-04-12 12:01:01 UTC
Here is my Debian bug:

https://bugs.debian.org/895504

Another Debian user also found this bug:

https://bugs.debian.org/895508
Comment 5 Paul Wise 2018-04-12 12:01:40 UTC
Er, I meant "Initially I was on webkit2gtk 2.20.0-2, evolution 3.28.0-4 and did not get the bug."
Comment 6 Jeremy Bicha 2018-04-12 12:16:41 UTC
To be more specific, I cherry-picked the first 2 (substantial) commits after 3.28.1 for Debian's 3.28.1-1 release. But a few hours later, there was this commit:

https://git.gnome.org/browse/evolution/commit/?h=gnome-3-28&id=bf8c368713

Cherry-picking that commit fixes several issues.