(In reply to comment #0)
> Since the latest updates Mageia's Control Centre won't come up.
> Clicking the icon (Mageia Control Centre) brings up the login-screen for root.
> After purchasing the password and hitting enter, nothing happens.

I don't have any problems with MCC, but I think I use another mirror for Cauldron than you do. If the problem is related to an update, maybe I just didn't get that update yet.

Do you still have any (konsole-)output of those updates? Were you asked to make one or more choices?

CC: (none) => m.van.waes

https://bugs.mageia.org/show_bug.cgi?id=2827 might be the same bug:

Description of problem:
If
lib64gdk_pixbuf2.0_0-loaders-png12-2.24.0-3.mga2
and
lib64gdk_pixbuf2.0_0-loaders-png15-2.24.0-5.mga2
are installed together then mcc and many more applications fail.
They should conflict each other IIANM.

Yes, look at the changelog in gdk-pixbuf2.0-2.24.0-5.mga2.src.rpm

CC: (none) => zen25000

BTW the fix I used was to make sure that 
lib(64)gdk_pixbuf2.0_0-loaders-png15
was installed and then uninstall
lib(64)gdk_pixbuf2.0_0-loaders-png12
In my case it took picasa and google-earth with it - not yet tried to re-install those. ;) YMMV

*** Bug 2827 has been marked as a duplicate of this bug. ***

Funda, Thierry, bug related to the new libpng ?

CC: (none) => fundawang, thierry.vignaud
Source RPM: (none) => drakxtools

Could anybody post the log of urpmi? as png12 flavour shouldn't be installed for running systems. It is only needed for lsb packages.

Status: NEW => ASSIGNED
Blocks: (none) => 2810
Assignee: bugsquad => fundawang

Created attachment 821 [details]
messages

Hi Funda,
After this happened on my main Cauldron installation, I booted into a minimal test LXDE installation and let MageiaUpdate run.
Again mcc died and the panel icons failed to display.
Attached is the messages file from the start of mageiaupdate and also attached is a list of the packages in chronological order that were installed today on that system - you will see both packages in the first few.
If there is a urpmi log than I don't know where to find it.

To look at the messages file it may be worth filtering out any lines with "zm" as unfortunately a zoneminder server was running which spews out lots of crud.

Barry

Created attachment 822 [details]
packages installed in order

I guess that list is actually in reverse order :\

Problem solved by issuing the following commands:

[root@localhost ~]# urpmi libgdk_pixbuf2.0_0-loaders-png15
[root@localhost ~]# urpme libgdk_pixbuf2.0_0-loaders-png12

I mean the output of debug output of urpmi:

urpmi libgdk_pixbuf2.0_0 --debug --test

## or ##

urpmi --auto-select --debug --auto --test

This way we could see why urpmi is selecting png12 flavor though png15 is already preferred via config file.

Created attachment 827 [details]
output of urpmi --auto-select --debug --auto --test

(In reply to comment #12)
> I mean the output of debug output of urpmi:
> 
> urpmi libgdk_pixbuf2.0_0 --debug --test
> 
> ## or ##
> 
> urpmi --auto-select --debug --auto --test
> 
> This way we could see why urpmi is selecting png12 flavor though png15 is
> already preferred via config file.

OK - since it's now after the event and too late for that on the systems involved, I did the following:-
1. chroot'ed into a recent mga1 x86_64 installation
2. edited /etc/mageia-release to cauldron
3. Changed media to point to cauldron on my local up-to-date repo
4. ran urpmi --auto-select --debug --auto --test
5. Output attached (up to installing...)

OK, the problem comes from lsb-lib. It is pushing libpng12 flavour. I'll check it later for bug#2810.

Would libgdk_pixbuf2.0_0-loaders-png12-2.24.0-6.mga2 still crash?

(In reply to comment #15)
> Would libgdk_pixbuf2.0_0-loaders-png12-2.24.0-6.mga2 still crash?

...if what?


Sorry I can't understand the question ;)

If both png15 and png12-6.mga2 are installed, will mcc crash also?

Ah OK - a new png12 - yes that seems OK - I now have:-

[baz@jackodesktop ~]$ rpm -qa|grep libgdk_pixbuf2.0
libgdk_pixbuf2.0_0-2.24.0-6.mga2
libgdk_pixbuf2.0_0-loaders-png12-2.24.0-6.mga2
libgdk_pixbuf2.0_0-loaders-png15-2.24.0-6.mga2

mcc is working both before and after a reboot.

Sadly the KDE network monitor plasmoid is now blank after re-boot, but maybe not related as there were other kde updates last night and this is the first re-boot since.

It does kill the network monitor plasmoid in KDE. :(
I just did :-
urpme libgdk_pixbuf2.0_0-loaders-png12
log out -> log in and the plasmoid is back as normal.

On x86_64 cauldron, removing
lib64gdk_pixbuf2.0_0-loaders-png15
and installing
libgdk_pixbuf2.0_0-loaders-png12
helped

CC: (none) => mabuac.rhn

Today I upgraded Mageia 1 64bit to Cauldron, and also met the problem that rpmdrake and mcc couldn't run. After installing lib64gdk_pixbuf2.0_0-loaders-png15, the problem was solved.

CC: (none) => futureway

However, after installing lib64gdk_pixbuf2.0_0-loaders-png15 (lib64gdk_pixbuf2.0_0-loaders-png12 was already installed), the color of Chrome browser's window became red as the attached picture (chrome.jpg) shows. If lib64gdk_pixbuf2.0_0-loaders-png15 is removed, Chrome can display properly, but rpmdrake and mcc can't run.

Created attachment 967 [details]
Chrome's window became red

Hello what is the status of this bug ?

Now I am using Mageia 1 again, and don't know about the present status of the bug in Cauldron.

No problems here anymore since comment 11.

All OK here. The related issue with the net plasmoid mentioned has also disappeared.

Ok thanks.

Status: ASSIGNED => RESOLVED
Resolution: (none) => FIXED

Just as a heads-up, the png12 library rpm gets pulled in by the install of the current google-earth 6 rpm.

So I think we do need some way of preventing png12 from installing...

CC: (none) => ftg

(In reply to comment #24)
> Hello what is the status of this bug ?

On Mageia 2 beta 1 x86_64, the bug is valid, too. The package lib64gdk_pixbuf2.0_0-loaders-png12 is a dependency of Google Chrome, while lib64gdk_pixbuf2.0_0-loaders-png15 is a important dependency of Mageia 2. With lib64gdk_pixbuf2.0_0-loaders-png15, the color of Google Chrome's window shows red. Without lib64gdk_pixbuf2.0_0-loaders-png15, mcc and rpmdrake can't run.

The new versions of Adobe Flash Player for Linux will be only available for Google Chrome. If Google Chrome can run well, it will be very good. Now on the 64bit system, the 32bit version of Google Chrome runs properly.

Status: RESOLVED => REOPENED
Resolution: FIXED => (none)

since when do we support google chrome ?

(In reply to comment #31)
> since when do we support google chrome ?

I tend to say "google chrome" instead of "chromium browser", too

@ Jian

@ Jiang

What is the output of 
rpm -qa | grep chromium-browser

(In reply to comment #33)
> @ Jiang
> 
> What is the output of 
> rpm -qa | grep chromium-browser

I said Google Chrome.

I didn't install Chromium browser, but installed Google Chrome which was downloaded from its official site.

(In reply to comment #34)
> (In reply to comment #33)
> > @ Jiang
> > 
> > What is the output of 
> > rpm -qa | grep chromium-browser
> 
> I said Google Chrome.
> 
> I didn't install Chromium browser, but installed Google Chrome which was
> downloaded from its official site.

Then it is as Manuel said: we don't support it

*** Bug 4719 has been marked as a duplicate of this bug. ***

CC: (none) => epistemepromeneur

(In reply to comment #29)
> Just as a heads-up, the png12 library rpm gets pulled in by the install of the
> current google-earth 6 rpm.
> 
> So I think we do need some way of preventing png12 from installing...

mageia 2 b1 x86_64 dvd

the pb (see bug #4719) happens after installing Google-earth 6 rpm 64 bit from google site

mageia 2 b1 x86_64 dvd

if i uninstall lib64gdk_pixbuf2.0_0-loaders-png12-2.25.2-1.mga2.x86_64
then
we learn lib64gdk_pixbuf2.0_0-loaders-png12-2.25.2-1.mga2.x86_64 is installed by the installation of lsb-lib64-4.1-10.mga2.x86_64
and
this causes the uninstallation of google-earth

[root@localhost ~]# urpme lib64gdk_pixbuf2.0_0-loaders-png12-2.25.2-1.mga2.x86_64
Pour satisfaire les dépendances, les 3 paquetages suivants vont être désinstallés (102Mo):
  google-earth-stable-6.2.1.6014-0.x86_64
   (car lsb >= 3.2 est non satisfait)
  lib64gdk_pixbuf2.0_0-loaders-png12-2.25.2-1.mga2.x86_64
  lsb-lib64-4.1-10.mga2.x86_64
   (en raison du manque de lib64gdk_pixbuf2.0_0-loaders-png12)

after uninstalling lib64gdk_pixbuf2.0_0-loaders-png12-2.25.2-1.mga2.x86_64
there is no more pb with gkt apps

is there someone who knows how to install google-earth without installing
lib64gdk_pixbuf2.0_0-loaders-png12-2.25.2-1.mga2.x86_64
or perhaps easier how to uninstall lib64gdk_pixbuf2.0_0-loaders-png12-2.25.2-1.mga2.x86_64 without uninstalling lsb-lib64-4.1-10.mga2.x86_64 and
google-earth-stable-6.2.1.6014-0.x86_64 ?

(In reply to comment #40)
> is there someone who knows how to install google-earth without installing
> lib64gdk_pixbuf2.0_0-loaders-png12-2.25.2-1.mga2.x86_64
> or perhaps easier how to uninstall
> lib64gdk_pixbuf2.0_0-loaders-png12-2.25.2-1.mga2.x86_64 without uninstalling
> lsb-lib64-4.1-10.mga2.x86_64 and
> google-earth-stable-6.2.1.6014-0.x86_64 ?


The command to uninstall the package is "rpm -e --nodeps lib64gdk_pixbuf2.0_0-loaders-png12". "-e" means uninstallation. "--nodeps" means that other dependencies won't be uninstalled.

Google Earth 64bit version is not easy to work on Mageia x86_64. I installed Google Earth 32bit version on Mageia x86_64, and it works well.

thanks

1. i think as mandriva with plf google-earth packet we need some metapacket
to install Google-earth according to the mageia principles

2. curiously it seems that google-earth 64 bit needs some 32 bit libs !

lsb-core-lib
libglibc-lsb

libconfconfig.so.1 -> libfontconfig packet
libxrender.so.1 -> libxrender1 packet

see

http://www.mageialinux-online.org/forum/topic-12108+installation-de-googlearth-en-64-bits.php

the 32 bit library are not installed when installing google-earth 6 rpm 64 bit

It is not only google/chrome that pulls in the png12 libraries. On my cauldron system (i586), when I do "urpme libpng12_0", I get 3 dependencies to un-install:
  - kompozer
  - gocr
  - netpbm

urpmq --requires-recursive libgtk+2.0_0 | grep png12   gives
  libgdk_pixbuf2.0_0-loaders-png12|libgdk_pixbuf2.0_0-loaders-png15

yes but the png15 is in the prefer.vendor.list, so there is no bug...

Right now, the best workaround is to uninstall libpng_12 and it's dependencies, yes?

CC: (none) => rickstockton

No, you only need to get rid of libgdk_pixbuf2.0_0-loaders-png12. And, you will get non-working lsb apps, too.

Done, and I can live without google earth on a Beta. Thanks for the confirmation! (And yes, MCC is now working for me.)

Is there any progress being made on this bug?  I have been unable to run drakconf for a long time.  I don't have libgdk_pixbuf2.0_0-loaders-png12 installed.

CC: (none) => acitta1

Gary, do you still have this bug?
For me, it is solved since a recent update ( 2 or 3 days?)
I don't have libgdk_pixbuf2.0_0-loaders-png12 installed too.

CC: (none) => laurent_breton_web

Hi,

This bug was filed against cauldron, but we do not have cauldron at the moment.

Please report whether this bug is still valid for Mageia 2.

Thanks :)

Cheers,
marja

Keywords: (none) => NEEDINFO

still valid for mageia 2, run into the same issue after updating from mga1 to mga2 with MgaOnline.

Installing lib64gdk_pixbuf2.0_0-loaders-png15 solved the issue, mcc works fine with both lib64gdk_pixbuf2.0_0-loaders-png15 and lib64gdk_pixbuf2.0_0-loaders-png12

CC: (none) => shikamaru

Please look at the bottom of this mail to see whether you're the assignee of this  bug, if you don't already know whether you are.


If you're the assignee:

We'd like to know for sure whether this bug was assigned correctly. Please change status to ASSIGNED if it is, or put OK on the whiteboard instead.

If you don't have a clue and don't see a way to find out, then please put NEEDHELP on the whiteboard.

Please assign back to Bug Squad or to the correct person to solve this bug if we were wrong to assign it to you, and explain why.

Thanks :)

**************************** 

@ the reporter and persons in the cc of this bug:

If you have any new information that wasn't given before (like this bug being valid for another version of Mageia, too, or it being solved) please tell us.

@ the reporter of this bug

If you didn't reply yet to a request for more information, please do so within two weeks from now.

Thanks all :-D

For me solved a long time ago, as mentioned in comment 11.
https://bugs.mageia.org/show_bug.cgi?id=2822#c11

;)

mageia 2 x86_64

drakconf starts well

OK, so fixed.

Status: REOPENED => RESOLVED
Resolution: (none) => FIXED