Bug 17247

Summary:	[Mga6-dev1] PLasma5 live MCC crashes immediately upon launch
Product:	Mageia	Reporter:	Ben McMonagle <westel>
Component:	Release (media or process)	Assignee:	Thomas Backlund <tmb>
Status:	RESOLVED DUPLICATE	QA Contact:
Severity:	normal
Priority:	Normal	CC:	marja11, sysadmin-bugs, thierry.vignaud
Version:	Cauldron
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:	6dev1 NEEDINFO
Source RPM:	drakconf 12.60 - 2.mga6	CVE:
Status comment:
Attachments:	for x86 draconf "fix"

Description Ben McMonagle 2015-11-28 23:54:10 CET

Description of problem:MCC and Mageia Welcome crashes immediately upon launch. this appears to be due to missing dependencies.
To correct:  urpme drakconf, adding new online media, and then urpmi drakconf adds also 28-30 extra packages[depends on i586 or x86 arch].Retry MCC and now launches -ok. 
I did not remove orphan packages
As a bonus M/W also launches ok too


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


How reproducible:every time 


Steps to Reproduce:
1.install Plasma5 from Mga6-dev1 live
2.launch MCC either from konsole or icon
3.observe failure
4.remove drakconf , add new online media and re-install drakconf
5. check that launch and operation is ok

Reproducible: 

Steps to Reproduce:

Comment 1 Marja Van Waes 2015-11-29 20:40:52 CET

Hi Ben,

Thx for the bug report.

Do you mind listing the missing packages that got installed after adding online media and re-installing drakconf?

CC: (none) => marja11, sysadmin-bugs
Component: RPM Packages => Release (media or process)
Assignee: bugsquad => tmb
Summary: [Mga6-dev1] PLasma5 live MCC crashes immediately upon launch, => [Mga6-dev1] PLasma5 live MCC crashes immediately upon launch
Whiteboard: (none) => 6dev1 NEEDINFO

Comment 2 Ben McMonagle 2015-11-29 22:21:25 CET

Created attachment 7252 [details]
for x86 draconf "fix"

I currently dont have access to the i586 system

Comment 3 Thierry Vignaud 2015-12-02 08:35:28 CET

Dup.
This really is a gtk+2.0 issue, not a mcc one

*** This bug has been marked as a duplicate of bug 17236 ***

Status: NEW => RESOLVED
CC: (none) => thierry.vignaud
Resolution: (none) => DUPLICATE