Bug 20092 - Evolution segfaults on 'Check for Supported Types'
Summary: Evolution segfaults on 'Check for Supported Types'
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 5
Hardware: All Linux
Priority: Normal critical
Target Milestone: ---
Assignee: GNOME maintainers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-01-08 20:37 CET by Herbert Poetzl
Modified: 2018-10-07 17:02 CEST (History)
3 users (show)

See Also:
Source RPM: evolution-3.13.90-1.1.mga5.src.rpm
CVE:
Status comment:


Attachments
Three stack traces from 'Check for Supported Types' in Receiving (10.61 KB, text/plain)
2017-01-08 20:43 CET, Herbert Poetzl
Details
Similar trace for Check for Supported Types in Sending (5.25 KB, text/plain)
2017-01-08 20:45 CET, Herbert Poetzl
Details

Description Herbert Poetzl 2017-01-08 20:37:18 CET
Description of problem:
When trying to configure evolution the first time, it segfaults when detecting the supported Authentication types.

Version-Release number of selected component (if applicable):
evolution-3.13.90-1.1.mga5.x86_64


How reproducible:
Always

Steps to Reproduce:
1. Create new account
2. Check for Supported Types
3.
Comment 1 Herbert Poetzl 2017-01-08 20:43:49 CET
Created attachment 8846 [details]
Three stack traces from 'Check for Supported Types' in Receiving

config so far:

http://vserver.13thfloor.at/Stuff/MAGEIA/evolution_identity.jpg
http://vserver.13thfloor.at/Stuff/MAGEIA/evolution_imap.jpg

CC: (none) => herbert

Comment 2 Herbert Poetzl 2017-01-08 20:45:35 CET
Created attachment 8847 [details]
Similar trace for Check for Supported Types in Sending

same config as for the IMAP case plus:

http://vserver.13thfloor.at/Stuff/MAGEIA/evolution_smtp.jpg
Marja Van Waes 2017-01-08 22:46:28 CET

CC: (none) => marja11, olav
Assignee: bugsquad => gnome

Comment 3 Marja Van Waes 2018-07-12 13:07:07 CEST
Hi Herbert,

Did this bug get fixed? If so, please change its status to RESOLVED - FIXED

If it didn't, then we regret that we weren't able to fix it in Mageia 5. Mageia 5 has officially reached its End of Life on December 31st, 2017 https://blog.mageia.org/en/2017/11/07/mageia-5-eol-postponed/
It only continued to get important security updates since then, because we were waiting for the big Plasma5 update in Mageia 6, that fixed many of the Mageia 5 => 6 upgrade issues.

If you haven't seen that this bug got fixed, then please check whether this bug still exists in Mageia 6. If it does, then please change the Version (near the top, at the left) to "6". If you know it exists in Cauldron, then change Version to Cauldron. If you see it in both Cauldron and Mageia 6, then please set Version to Cauldron and add MGA6TOO on the Whiteboard.
Comment 4 Marja Van Waes 2018-10-07 17:02:54 CEST
No reply, so closing as OLD since Mageia 5 is no longer maintained.

Status: NEW => RESOLVED
Resolution: (none) => OLD


Note You need to log in before you can comment on or make changes to this bug.