Command line output:
ERROR: Invalid browser function table. Some functionality may be restricted.                                                                                                                 
/home/iurt/rpm/BUILD/icedtea-web-1.2/plugin/icedteanp/IcedTeaNPPlugin.cc:1543: thread 0x2ffa870: Error: Failed to spawn applet viewer: L'exécution du processus fils « /usr/lib/jvm/jre-1.6.0-openjdk.x86_64/bin/java » a échoué (Aucun fichier ou dossier de ce type)                                                                                                                    
Subroutine Gtk3::main redefined at /usr/lib/perl5/vendor_perl/5.18.1/Gtk3.pm line 296.

Bug not solved yet, apparently nobody has looked at it?


Issue solved on my side - had to force install of icedtea-web plugin. I think it had be removed after a urpme --auto-orphans.
There must be somehow a missing dependency on icedtea-web from drakconf package, or one of its dependencies - if drakconf is installed (quite always the case :)) then icedtea-web should never be reported as orphan - or if icedtea-web is not actually used by drakconf then code should be reworked to not try to initialize it.
Note: Mageia 4 upgraded from Mageia 3 with urpmi CLI (remove mga3 repos, add mga4 ones, urpmi --replacefiles --auto --auto-update)

well it's hard to fix a bug we cannot reproduce.
as for icedtea-web, drakconf uses webkit which doesn't really provide a way to disable plugins despite being unused
MCC works nicely here with & without icedtea-web, which it doesn't use.

Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer 
maintained, which means that it will not receive any further security or bug 
fix updates.

Package Maintainer: If you wish for this bug to remain open because you plan to 
fix it in a currently maintained version, simply change the 'version' to a later 
Mageia version.

Bug Reporter: Thank you for reporting this issue and we are sorry that we weren't 
able to fix it before Mageia 4's end of life. If you are able to reproduce it 
against a later version of Mageia, you are encouraged to click on "Version" and 
change it against that version of Mageia. If it's valid in several versions, 
select the highest and add MGAxTOO in whiteboard for each other valid release.
Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO.

Although we aim to fix as many bugs as possible during every release's lifetime, 
sometimes those efforts are overtaken by events. Often a more recent Mageia 
release includes newer upstream software that fixes bugs or makes them obsolete.

If you would like to help fixing bugs in the future, don't hesitate to join the
packager team via our mentoring program [1] or join the teams that fit you 
most [2].

[1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager
[2] http://www.mageia.org/contribute/

As announced over a month ago, Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates.

This issue may have been fixed in a later Mageia release, so, if you still see it and didn't already do so: please upgrade to Mageia 5 (or, if you read this much later than this is written: make sure you run a currently maintained Mageia version)

If you are able to reproduce it against a maintained version of Mageia, you are encouraged to 
1. reopen this bug report, by changing the "Status" from "RESOLVED - OLD" to "REOPENED"
2. click on "Version" and change it against that version of Mageia. If you know it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release.
Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO.
3. give as much relevant information as possible. If you're not an experienced bug reporter and have some time: please read this page:
https://wiki.mageia.org/en/How_to_report_a_bug_properly

If you see a similar issue, but are _not_sure_ it is the same, with the same cause, then please file a new bug report and mention this one in it (please include the bug number, too). 


If you would like to help fixing bugs in the future, don't hesitate to join the
packager team via our mentoring program [1] or join the teams that fit you 
most [2].
[1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager
[2] http://www.mageia.org/contribute/

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