Bug 17283

Summary:	freshplayerplugin causes the Mageia Control Center to crash
Product:	Mageia	Reporter:	Ezequiel Partida <ezequiel_partida>
Component:	RPM Packages	Assignee:	Thierry Vignaud <thierry.vignaud>
Status:	RESOLVED FIXED	QA Contact:
Severity:	major
Priority:	High	CC:	luigiwalser, mageia, marja11
Version:	5
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:	drakconf	CVE:
Status comment:

Description Ezequiel Partida 2015-12-03 22:54:26 CET

Description of problem:

After Installing freshplayerplugin-0.3.1-1.mga5.x86_64

This is what a I get.

[root@localhost ~]# mcc
No bp log location saved, using default.
[000:000] Cpu: 6.42.7, x4, 3200Mhz, 3833MB
[000:000] Computer model: Not available
[000:000] Browser XEmbed support present: 1
[000:000] Browser toolkit is Gtk2.
[000:000] Using Gtk2 toolkit
NOT SANDBOXED
[ERROR:flash/platform/pepper/common/pep_process.cpp(19)] CHECK(g_process_type == PROCESS_TYPE_UNKNOWN) failed


MCC closes immediately


Version-Release number of selected component (if applicable):

freshplayerplugin-0.3.1-1.mga5.x86_64

How reproducible:

Just install freshplayerplugin-0.3.1-1.mga5.x86_64 and run mcc on konsole.

If you try to run it via Mageia menu It just doesn't open at all.


P.S. it also happens on Mageia 6 as of today Dec-3-2015.

Reproducible: 

Steps to Reproduce:

Rémi Verschelde 2015-12-03 22:57:01 CET

Summary: Creshplayerplugin Conflicts with Mageia Control Center => freshplayerplugin causes the Mageia Control Center to crash

Samuel Verschelde 2015-12-07 12:10:17 CET

Priority: Normal => High
Assignee: bugsquad => thierry.vignaud
Source RPM: freshplayerplugin-0.3.1-1.mga5.x86_64 => drakconf
Severity: normal => major

Rémi Verschelde 2015-12-07 12:36:39 CET

CC: (none) => luigiwalser

Comment 1 David Walser 2015-12-07 12:42:42 CET

Very strange.  Certainly not freshplayerplugin's fault.  I'm not sure why or how it or gtk+2 are being pulled in.  May be related to recent gtk+ changes or something, but Thierry should have a better idea.

Comment 2 Nicolas Lécureuil 2017-10-28 19:21:09 CEST

is it still valid ? i don't reproduce on mga6/cauldron

CC: (none) => mageia

Comment 3 Ezequiel Partida 2018-09-25 01:14:29 CEST

Hello..

Sorry for not answering before.. This is now working fine after some upgrades.

I will mark this as solved.

Thank you everyone.

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

Comment 4 David Walser 2018-09-25 02:41:41 CEST

It's not fixed until the update is pushed.  What architecture did you test?

Resolution: FIXED => (none)
Status: RESOLVED => REOPENED

Comment 5 Marja Van Waes 2018-10-07 17:33:52 CEST

(In reply to Nicolas Lécureuil from comment #2)
> is it still valid ? i don't reproduce on mga6/cauldron

Ah good, so this report won't need to stay open for 6 or cauldron.

(In reply to Ezequiel Partida from comment #3)
> Hello..
> 
> Sorry for not answering before.. This is now working fine after some
> upgrades.
> 
> I will mark this as solved.
> 
> Thank you everyone.

(In reply to David Walser from comment #4)
> It's not fixed until the update is pushed.  What architecture did you test?

Where do you see that he updated from testing? He doesn't say that anywhere, so I assume he got normal package updates.

Re-closing as FIXED

Resolution: (none) => FIXED
CC: (none) => marja11
Status: REOPENED => RESOLVED

Comment 6 Thierry Vignaud 2018-10-08 17:52:37 CEST

Singe mga5, porting to WebKit2 (bug #15031) has enabled us to explicitly disable plugins & java, which was not possible with WebKit1