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 782059 - Evolution crashes when timezone offset other than local timezone offset
Evolution crashes when timezone offset other than local timezone offset
Status: RESOLVED OBSOLETE
Product: evolution
Classification: Applications
Component: Mailer
3.18.x (obsolete)
Other Linux
: Normal critical
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2017-05-02 11:54 UTC by ruebezaehler
Modified: 2017-05-03 13:15 UTC
See Also:
GNOME target: ---
GNOME version: 3.17/3.18


Attachments
run debug version of evolution with gdb. Opened an E-Mail with UTC timezone (offset=0). StackTrace after crash. (16.79 KB, text/plain)
2017-05-02 11:54 UTC, ruebezaehler
Details
Example Message which causes the Segmentation fault. (10.08 KB, message/rfc822)
2017-05-03 09:06 UTC, ruebezaehler
Details
Debug report with webkitdbg installed (26.07 KB, text/plain)
2017-05-03 09:08 UTC, ruebezaehler
Details

Description ruebezaehler 2017-05-02 11:54:56 UTC
Created attachment 350862 [details]
run debug version of evolution with gdb. Opened an E-Mail with UTC timezone (offset=0). StackTrace after crash.

Evolution 3.18.5.2 on Ubuntu-Gnome 16.04.3

When opening/preview an E-Mail with a Header-Timezone-Offset other than localzone offset (here +0200) Evolution crahses.

Example:

    Crash: Date: Sat, 29 Apr 2017 10:25:51 +0000

    Crash: Date: Sat, 29 Apr 2017 10:25:51 +0100

    Ok, no crash: Date: Sat, 29 Apr 2017 10:25:51 +0200

gdb report see attachment
Comment 1 Milan Crha 2017-05-03 05:18:40 UTC
Thanks for a bug report. First of all, setting blocker status for a version which is ancient doesn't make much sense. The current stable is 3.24.1.

Looking into the backtrace, it's all in webkitgtk3, not in evolution itself, thus it can be just a coincidence with the time header. There had been some crashes in webkigtk3 reported in the past, but I cannot tell for sure whether it's any of those, because there is no debugging information for webkitgtk3 in the backtrace, neither minimal debug info, like function names (full debuginfo for webkitgtk3 is tricky to get and it's very large). Nonetheless, the current stable version doesn't use webkigtgtk3, it switch from WebKit1 to WebKit2, thus this particular issue is gone in a way that it cannot repeat in the exact form.

I can try whether the issue is present in the current stable, if you've a reproducer message to try with and you can share it, either by attaching it here or by sending it only to me, to my bugzilla email, to avoid sharing private information publicly. If you'd do that, reference this bug report in the subject, please, thus I'd not overlook it in my spam folder. To save the message, turn off Preview panel (Ctrl+M), then right-click the message and Save as mbox, or drag and drop it into the composer.
Comment 2 ruebezaehler 2017-05-03 09:06:41 UTC
Created attachment 350954 [details]
Example Message which causes the Segmentation fault.

E-Mail: 1493793481.2785_14290.ws1:2,S

Example Message (from Milan Crha) which causes the Segmentation fault. 
Date: Wed, 03 May 2017 05:18:40 +0000
Comment 3 ruebezaehler 2017-05-03 09:08:30 UTC
Created attachment 350955 [details]
Debug report with webkitdbg installed

I installed the webkit debug version (1.3GB!). 

Attached debug report evolution-crash-webkitdbg-20170503a
Comment 4 Milan Crha 2017-05-03 09:44:25 UTC
Thanks for the update. Does that message (comment #2) cause a crash for you? It doesn't for me, I can view it without any issue both in 3.18.5.2 and in the current git master of evolution.

The updated backtrace (yes, webkitgtk package with debug symbols is very large), suggests that the crash happened when positioning table into the view, when determining font pitch. I'd try to change your font settings for the desktop or in Edit->Preferences->Mail Preferences->General tab->at the top of the Message Display section.

This issue seems to be fixed upstream, reported as:
https://bugs.webkit.org/show_bug.cgi?id=125687
Comment 5 ruebezaehler 2017-05-03 10:30:05 UTC
Thank You for taking care of the problem.

Yes, the crash happens, when positioning the table to an email with the mentioned timezone offset and if preview is on. It also happens when opening the mail, but not when replying or forwarding.

But You were right, it's the font. About 6 month ago I switched from 

(excuse, I'm using the german version and do not know the exact english terms)

1) Preferences->E-Mail->Message->use fonts as other applications

to 

2) -standard: Regular 10
   -monospaced: FreeMono Standard 11

It works fine until last week. 2 Days after I installed the Ubuntu requested updates I noticed the crashes (why not direct after the updates when regarding new mails?)

I do not know the development path, but perhaps this may also happen in new versions of evolution resp. the webkitgtk.

For me the problem is solved (switching to another font).

Thank You again for Your essential hint.
Comment 6 ruebezaehler 2017-05-03 10:56:48 UTC
I forgot to ask one question: where/how does the timezone offset impact the crash?
Comment 7 Milan Crha 2017-05-03 13:15:49 UTC
(In reply to ruebezaehler from comment #5)
> 2) -standard: Regular 10
>    -monospaced: FreeMono Standard 11

Hmm, I do not see these fonts here. I chose some close to it, but still no crash.

(In reply to ruebezaehler from comment #6)
> I forgot to ask one question: where/how does the timezone offset impact the
> crash?

I didn't say it's due to it. It can be just a coincidence. Depending on your settings, having other timezone can mean to show two times in the Date header in the preview, one value being verbatim from the message with a bracket value being converted into the local time zone, thus it changes the content to render, thus can, eventually, trigger the crash for you. But it's still just a coincidence.

In any case, good you have evolution working without crashing again.