Bug 11959 - MCC does not run with major desktops
Summary: MCC does not run with major desktops
Status: RESOLVED DUPLICATE of bug 10289
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: i586 Linux
Priority: release_blocker major
Target Milestone: ---
Assignee: Thierry Vignaud
QA Contact:
URL:
Whiteboard: Mageia 4 Beta 2
Keywords:
Depends on:
Blocks:
 
Reported: 2013-12-11 22:21 CET by Lewis Smith
Modified: 2013-12-12 09:52 CET (History)
0 users

See Also:
Source RPM: drakconf
CVE:
Status comment:


Attachments

Description Lewis Smith 2013-12-11 22:21:29 CET
Throughout recent (beta) Mageia 4 pre-release testing, Mageia Control Centre *has not worked*. This was noted in the PAD, but seems to need a new bug. This might be regarded as a duplicate of Bug 11184, but that got so long & convoluted & diverted that it seems better to start again, bring it back on course.

Simply, MCC does not work to varying degrees with most M4 desktops. Testing a Dec 9 2013 beta3 Classic DVD installation with 5 desktops - brought up-to-date 11 Dec - I offer the following precisions. In fact the picture has got better.

GNOME: Whether from icon or terminal, the pop-up root password dialogue bounces that (correct) password, so MCC cannot be launched. If this is by-passed by 'mcc' from a root terminal, it starts & disappears as for other desktops below.

KDE: Both from icon/menu or terminal, after accepting the root password, MCC starts up and immediately dies. Console O/P:-
$ mcc
[graphic root p/w dialogue]
LOG **: NP_Initialize at /usr/lib/libDrakX/mygtk2.pm line 589.
LOG **: NP_Initialize succeeded at /usr/lib/libDrakX/mygtk2.pm line 589.
LOG **: NP_Initialize at /usr/lib/libDrakX/mygtk2.pm line 589.
LOG **: NP_Initialize succeeded at /usr/lib/libDrakX/mygtk2.pm line 589.
LOG **: NP_Initialize at /usr/lib/libDrakX/mygtk2.pm line 589.
LOG **: NP_Initialize succeeded at /usr/lib/libDrakX/mygtk2.pm line 589.
LOG **: NP_Initialize at /usr/lib/libDrakX/mygtk2.pm line 589.
LOG **: NP_Initialize succeeded at /usr/lib/libDrakX/mygtk2.pm line 589.
"/usr/sbin/drakmenustyle" is not executable [Menus] at /usr/libexec/drakconf line 823.
"/usr/sbin/drakbackup" is not executable [Backups] at /usr/libexec/drakconf line 823.
"/usr/sbin/tomoyo-gui" is not executable [Tomoyo Policy] at /usr/libexec/drakconf line 823.
"/usr/sbin/drakguard" is not executable [Parental Controls] at /usr/libexec/drakconf line 823.
java version "1.7.0_45"
OpenJDK Runtime Environment (mageia-2.4.3.2.mga4-i386 u45-b15)
OpenJDK Client VM (build 24.45-b08, mixed mode, sharing)
Segmentation fault

LXDE: From icon/menu, nothing at all happens - no root password dialogue.
'mcc' from terminal asks for root p/w (in terminal, not graphic dialogue box), MCC appears then dies immediately with the same errors as above.

MATE: From icon/menu - WORKS! I think this is very recent.
From terminal, WORKS also, but with errors as above but *no* crash.

XFCE: From icon/menu, asks for root password then *works*; again I think this is very recent.
From terminal (root p/w input is from console), it gives the console errors noted above, *works* sometimes, no crash; or *crashes*. Almost alternately.

Version-Release number of selected component (if applicable):
 Mageia4 Betas (from Classic 32-bit DVD). 9 Dec 2013 system updated 11th.

How reproducible:
See description above. A bit of a moving target, but consistent at any one time.

Reproducible: 

Steps to Reproduce:
Lewis Smith 2013-12-11 22:21:59 CET

Whiteboard: (none) => Mageia 4 Beta 2

Lewis Smith 2013-12-11 22:24:42 CET

Priority: Normal => release_blocker

Manuel Hiebel 2013-12-11 23:52:31 CET

Assignee: bugsquad => thierry.vignaud
Source RPM: (none) => drakconf

Manuel Hiebel 2013-12-11 23:53:55 CET

See Also: (none) => https://bugs.mageia.org/show_bug.cgi?id=11956

Comment 1 Thierry Vignaud 2013-12-12 09:52:14 CET
Just reopen bug #10289, it's the same bug.
glib & webkit are creating threads behind us and sometimes segfault.
I'll need to further defer some action

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

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


Note You need to log in before you can comment on or make changes to this bug.