Bug 18918

Summary:	[6sta1] Mga6 Icewm, menu choice MCC launchers invisible window
Product:	Mageia	Reporter:	Ben McMonagle <westel>
Component:	RPM Packages	Assignee:	Shlomi Fish <shlomif>
Status:	RESOLVED DUPLICATE	QA Contact:
Severity:	normal
Priority:	Normal	CC:	fri, marja11
Version:	Cauldron	Keywords:	6sta1
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:		CVE:
Status comment:

Description Ben McMonagle 2016-07-11 10:02:56 CEST

Description of problem: after upgrading Mga5 x86_64 (6DEin1) to Mga6, MCC does not launch when choosing to launch from menu or Mageia Welcome link.
however does launch from terminal


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


How reproducible:every time


Steps to Reproduce:
1.upgrade Mga5 x86_64 (6DE in 1) to Mga6. reboot
2.choose IceWM at sddm greeter and login 
3.attempt tyo invoke Mageia Control Centre from menu launcher or Mageia welcome Launcher. it will fail to invoke.
4. open terminal, invoke MCC

Ben McMonagle 2016-07-11 10:03:11 CEST

Keywords: (none) => 6sta1

Comment 1 Morgan Leijström 2016-07-12 00:56:43 CEST

I see similar:
Setup: fresh install 6d1 a couple months ago, updated since, but have only been using Plasma until today when i installed other DEs to try

Today i tried icewm:
When i try to launch mcc from menu i see it and login window in in the task bar (or what it is called) but there is no window, i enter root password "in blind" and still no visible window.
If i instead open terminal, su to root and launch mcc it works.

As this happens also on an not from mga5 upgraded machine i change bug title accordingly.

CC: (none) => fri
Summary: [6sta1] after upgrade from Mga5, Mga6 Icewm, Mcc launchers not working => [6sta1] Mga6 Icewm, menu choice MCC launchers invisible window

Comment 2 Marja Van Waes 2016-07-14 14:15:29 CEST

Assigning to IceWM maintainer

CC: (none) => marja11
Assignee: bugsquad => shlomif

Comment 3 David Walser 2016-07-22 15:35:25 CEST

This is because chksession is broken.

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

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