Bug 1376977

Summary:	Evolution can't be opened after update
Product:	[Fedora] Fedora	Reporter:	Dio Putra <diooktput97>
Component:	evolution	Assignee:	Milan Crha <mcrha>
Status:	CLOSED CANTFIX	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	24	CC:	diooktput97, lucilanga, mbarnes, mcrha, tpopela
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-09-21 11:11:34 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Dio Putra 2016-09-17 06:54:22 UTC

Description of problem:
After updating my system, Evolution client now can't be opened

Version-Release number of selected component (if applicable):
evolution-3.20.5-1.fc24

How reproducible:
Try to update all packages your system into latest version, and then you'll see your evolution can't be opened anymore

Steps to Reproduce:
1. "sudo dnf update -y"
2. Wait your updates until finished
3. Now, try to open your Evolution client. Now Evolution can't be opened on my systemd

Actual results:
See this log on GNOME Pastebin
https://paste.gnome.org/ptesfp9f7

Expected results:
Evolution client should be opened normally

Additional info:

Comment 1 Dio Putra 2016-09-17 06:55:40 UTC

Sorry, little bit typo on systemd word. I mean my system, not systemd.

Comment 2 Dio Putra 2016-09-17 07:02:16 UTC

Hmm, things like because pepperflash which make this regression. Apologies for myself if nobody care about that problem. :-)

Comment 3 Milan Crha 2016-09-19 09:57:39 UTC

Thanks for a bug report.

> See this log on GNOME Pastebin

that paste is gone. Better to paste it into the bugzilla for history and search reason.

(In reply to Dio Oktarianos Putra from comment #2)
> Hmm, things like because pepperflash which make this regression. Apologies
> for myself if nobody care about that problem. :-)

I'm sorry, I didn't get it. Do you mean that the problem was caused by some other package, which you possibly removed and it started to work again?

Comment 4 Dio Putra 2016-09-20 13:53:28 UTC

(In reply to Milan Crha from comment #3)
> Thanks for a bug report.
> 
> > See this log on GNOME Pastebin
> 
> that paste is gone. Better to paste it into the bugzilla for history and
> search reason.
My bad.

> 
> (In reply to Dio Oktarianos Putra from comment #2)
> > Hmm, things like because pepperflash which make this regression. Apologies
> > for myself if nobody care about that problem. :-)
> 
> I'm sorry, I didn't get it. Do you mean that the problem was caused by some
> other package, which you possibly removed and it started to work again?
No, fedora package don't make this problem but the pepperflash library (libfreshwrapper-flashplayer.so) which makes this problem. If you install libfreshwrapper-flashplayer.so in your system, you'll see the regression caused by pepperflash library (So badly, my gdb debug log was deleted).

And last time I saw pepperflash github repo, it's seem not actived fr now.

Comment 5 Milan Crha 2016-09-21 11:11:34 UTC

Thanks for the update.  As the problem depends on a 3rd-party custom web browser plugin, which evolution disables on its start, to avoid WebKit using them, I'm afraid we cannot do anything about it in the evolution. It would be interesting to know whether the evolution 3.22.x will survive, because it's using WebKit2, instead of WebKit1, though that will not change anything.