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 777193 - evolution 3.22.3 crash in webkit_editor_paste_clipboard_targets_cb
evolution 3.22.3 crash in webkit_editor_paste_clipboard_targets_cb
Status: RESOLVED FIXED
Product: evolution
Classification: Applications
Component: general
3.22.x (obsolete)
Other Linux
: Normal critical
: ---
Assigned To: Evolution Shell Maintainers Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2017-01-12 21:05 UTC by Jeremy Bicha
Modified: 2017-01-16 11:01 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
stacktrace (98.44 KB, text/plain)
2017-01-12 21:05 UTC, Jeremy Bicha
Details

Description Jeremy Bicha 2017-01-12 21:05:42 UTC
Created attachment 343391 [details]
stacktrace

In Ubuntu 16.10, there are reports of a crash. https://launchpad.net/bugs/1654044 We don't have reports of a webkit editor crash in errors.ubuntu.com before 3.22.3 (the previous 16.10 version was 3.22.1).

Because you might not have access to errors.ubuntu.com, I'm attaching the stacktrace from there here.

The crash signature is:

 /usr/bin/evolution:11:webkit_editor_paste_clipboard_targets_cb:request_targets_received_func:selection_received:g_closure_invoke:signal_emit_unlocked_R
Comment 1 Milan Crha 2017-01-13 14:31:25 UTC
Thanks for a bug report. Pasting backtraces is better for searching. Anyway, this had been fixed recently with the below commits. The 3.22.4 will be released the next Monday.

Created commit 960890f in evo master (3.23.4+)
Created commit 63c80a1 in evo gnome-3-22 (3.22.4+)
Comment 2 Jeremy Bicha 2017-01-13 14:40:28 UTC
So next time, you want me to just paste the whole thing in the bug report instead of as an attachment? Ok, I can do that. Thank you!
Comment 3 Milan Crha 2017-01-16 11:01:37 UTC
(In reply to Jeremy Bicha from comment #2)
> So next time, you want me to just paste the whole thing in the bug report
> instead of as an attachment?

Yes, please. This bugzilla knows how to parse backtraces and shows them better than plain text (the parser is not perfect, but good enough). The searching ability is more important here, when looking whether the crash had been already reported, eventually fixed, because searching through attachments costs way more than through the comments.