Bug 10472

Summary:	MCC opens, thens closes immediately, no segfault
Product:	Mageia	Reporter:	Frank Griffin <ftg>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED DUPLICATE	QA Contact:
Severity:	major
Priority:	Normal
Version:	Cauldron
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:	drakxtools	CVE:
Status comment:

Description Frank Griffin 2013-06-10 15:10:20 CEST

In current cauldron, invoking MCC either graphically or from the command line, puts up the password prompt, puts up the "loading" popup, opens the primary MCC window, and then immediately closes it.

This behavior has changed a bit since I first noticed it.  At first, because of the bit about retaining authorization for a short period of time after you give the root password, you would get the above behavior on the first try.  If you tried again immediately, you would get no password prompt and it would work.  In current cauldron, there appears to be no "period of forgiveness", the password prompt appears every time, and MCC closes every time.

This leads me to suspect that the problem is related to the password prompt.

Executed from the command line, there is no apparent segfault, just a few messages about varios MCC components being non-executable.  I don't know if these are related to the problem, or just noise:


[ftg@ftgme2 ~]$ mcc
[ftg@ftgme2 ~]$ "/usr/bin/drakmenustyle" is not executable [Menus] at /usr/sbin/drakconf.real line 823.
"/usr/sbin/drakbackup" is not executable [Backups] at /usr/sbin/drakconf.real line 823.
"/usr/sbin/drakvirt" is not executable [Virtualization] at /usr/sbin/drakconf.real line 823.
"/usr/sbin/tomoyo-gui" is not executable [Tomoyo Policy] at /usr/sbin/drakconf.real line 823.

In any case, MCC is unusable in current cauldron.

Reproducible: 

Steps to Reproduce:

Comment 1 Frank Griffin 2013-06-10 15:23:43 CEST

Addenda:

MCC works in current cauldron if invoked from the command line of a root session.

Comment 2 Frank Griffin 2013-06-10 15:27:02 CEST

More addenda:

The "not executable" messages occur in the case where it work, as well, so these are unrelated.

Invoking MCC from the command line of a root session you are running through ssh, e. g. ssh to a host, su to root, run MCC, does *not* produce a password prompt, but *does* exhibit the failure, closing immediately.

Comment 3 James Kerr 2013-06-10 15:55:14 CEST

Possibly a duplicate of Bug#10289

Comment 4 Manuel Hiebel 2013-06-10 19:47:36 CEST

(In reply to James Kerr from comment #3)
> Possibly a duplicate of Bug#10289

it's likely that yes, feel free to mark it as duplicate next time ;)

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

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