In the last week or so of updates M3A2 ( cauldron ) has lost the ability to launch drakconf. I have executed a complete new install and it still won't launch. Launched in a command line the following errors are reported: [wilcal@localhost ~]$ su Password: xxxxxx [root@localhost wilcal]# drakconf [root@localhost wilcal]# Gtk-Message **: Failed to load module "canberra-gtk-module" at /usr/lib/libDrakX/mygtk2.pm line 20. Can't load '/usr/lib/perl5/vendor_perl/5.16.0/i386-linux-thread-multi/auto/Gtk2/WebKit/WebKit.so' for module Gtk2::WebKit: /lib/libwebkitgtk-1.0.so.0: undefined symbol: UCNV_FROM_U_CALLBACK_SUBSTITUTE_50 at /usr/lib/perl5/5.16.2/i386-linux-thread-multi/DynaLoader.pm line 190. at /usr/sbin/drakconf.real line 37. Compilation failed in require at /usr/sbin/drakconf.real line 37. BEGIN failed--compilation aborted at /usr/sbin/drakconf.real line 37.
have you update your cauldron ? what is the output or rpm -q webkit ? it should be in the 1.10.1-3.mga3 release
Keywords: (none) => NEEDINFO
This all came from the fact that I had some time this afternoon so I did a test on my Cauldron install to install my printer. First I updated Cauldron then did the printer thing by simply plugging in a USB cable connected to a power up printer. When I got done with the printer install I then noticed that the MCC icon on the launch bar no longer worked. So I stopped doing the printer thing and tried to launch drakconf any way I could. Nothing worked. So using the 32-bit boot.iso ( 2 Nov 2012 ) I executed a ground up install using my local repo ( mirrored from mirrors.kernel.org ) updated every day. Install went fine but again before I could do anything the MCC/drakconf would not launch. Manuel Hiebel asked: > what is the output or rpm -q webkit webkit-1.10.1-2.mga3 ( That is what is in my local repo ) Opps, webkit-1.10.1-3.mga3.i586.rpm is in mirrors.kernel.org now and I only update my local repo in the morning. I'll try this again tomorrow. Thanks
Uptick to webkit-1.10.1-3.mga3.i586.rpm has solved this problem for me. I have changed the status of this bug to RESOLVED.
Status: NEW => RESOLVEDResolution: (none) => FIXED