Bug 5640

Summary:	Google Chrome visual issue
Product:	Mageia	Reporter:	Alejandro Cobo <alejandrocobo>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	Normal	CC:	eostapets, hugo.pereira, mageia, mailinglistsduraph
Version:	Cauldron	Keywords:	NEEDINFO, UPSTREAM
Target Milestone:	---
Hardware:	i586
OS:	Linux
Whiteboard:
Source RPM:		CVE:
Status comment:
Attachments:	Google Chrome visual issue

Description Alejandro Cobo 2012-04-27 18:13:10 CEST

Description of problem:
Google Chrome browser show some wrong graphics under Mageia 2 beta 3 KDE default Mageia theme.


Version-Release number of selected component (if applicable):
Last Google Chrome release

How reproducible:
Running Google Chrome

Steps to Reproduce:
1. Download Google Chrome RPM from: http://www.google.es/chrome/
2. Run the browser

Thanks.

Comment 1 Manuel Hiebel 2012-04-27 22:08:42 CEST

Can you add a screenshot ?

Keywords: (none) => NEEDINFO

Comment 2 Alejandro Cobo 2012-04-28 12:55:16 CEST

Created attachment 2128 [details]
Google Chrome visual issue

Here you can see what I tryed to explain.

Comment 3 Manuel Hiebel 2012-04-28 22:38:17 CEST

and with another theme ? (I don't know what google use)

and btw, we don't support chrome

Comment 4 Alejandro Cobo 2012-04-29 00:32:08 CEST

I tryed with another theme. I uninstalled oxygen-gtk and oxygen-gtk3 too but it doesn't work propertly (same problem).

I know you have no support for chrome but you need bug reports about oxygen-gtk and I tought it was one of those bugs.

If you are interested, I can try it under Gnome.

Comment 5 Raphaël Vinet 2012-04-29 09:29:48 CEST

Hi,

I confirm this bug too.
Chrome is not supported ... ok but do not forget that there is 'problem' for continuing to have an up to date chromium :( (see bug 4476) so personaly I prefer using an up to date chrome that an obsolete chromium.

CC: (none) => mailinglistsduraph

Comment 6 Sander Lepik 2012-04-29 09:34:22 CEST

Well, it would be a lot easier if Google would respect at least some standrards. As they don't it's very hard to package chromium. Even Fedora doesn't do it. And the reasons are the same.

http://ostatic.com/blog/making-projects-easier-to-package-why-chromium-isnt-in-fedora

CC: (none) => sander.lepik

Comment 7 Manuel Hiebel 2012-04-29 11:18:27 CEST

well I can't guess where is the issue so yes any test is helpful.

Comment 8 Alejandro Cobo 2012-04-29 19:48:07 CEST

Same problem in Gnome.

Comment 9 Hugo Pereira Da Costa 2012-04-30 18:37:30 CEST

Issue also happens with Raleigh theme (just checked)
This is _not_ an oxygen-gtk bug.
Should be closed as upstream.

CC: (none) => hugo

Comment 10 Raphaël Vinet 2012-04-30 19:33:14 CEST

Hi,

For sure it is a problem 'with something mageia 2' because no problem with a mageia 1 up to date and also the last stable version of chrome (what I use just now for posting :)).

Comment 11 Manuel Hiebel 2012-04-30 23:59:41 CEST

well open a bug upstream and ask...

Keywords: (none) => UPSTREAM
Status: NEW => UNCONFIRMED
Ever confirmed: 1 => 0

Manuel Hiebel 2012-05-01 00:04:44 CEST

Status: UNCONFIRMED => NEW
Ever confirmed: 0 => 1

Comment 12 Eugene Ostapets 2012-05-07 13:54:21 CEST

google-chrome conflicts with libgdk_pixbuf2.0_0-loaders-png15. If the package is removed - in chrome artifacts disappear, but at least break chromium and drakeconf.

CC: (none) => eostapets

Comment 13 Raphaël Vinet 2012-05-18 10:19:06 CEST

Hi,

For information these problem is apparently solved with the latest stable release (19.0.1084.46).

I don't know if the solution came with another package from Mageia and/or the update from the chrome package but now I have no more the graphic problems described upper

Rmk:
Starting with the mageia 2 RC (64 bits) I added all updates from cauldron and installed the last stable version of chrome (https://www.google.com/chrome/index.html?hl=fr, the 64 rpm package)

Comment 14 Manuel Hiebel 2012-05-18 13:24:21 CEST

closing then, thanks

Comment 15 Manuel Hiebel 2012-05-18 13:24:55 CEST

really

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