there is no image, and run in console for see if there is some errors (there is no -debug fox chromium :/)

Component: Release (media, process) => RPM Packages
Severity: critical => normal

There was no output when run from a console. I then decided to try gdb which I have never used until now. Here is the output. Note the last line

[barry@TheBox ~]$ gdb chromium-browser
GNU gdb (GDB) 7.1-6.mga1 (Mageia release 1)
Copyright (C) 2010 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "i586-mageia-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
"/usr/bin/chromium-browser": not in executable format: File format not recognized
(gdb)

/usr/bin/chromium-browser is a link to /usr/lib/chromium-browser/chromium-wrapper

HTH

Source RPM: chromium-browser => chromium-browser 11.0.696.68

Sorry to be so long getting back to this bug report.

Can you post the output of
bash -x -v /usr/lib/chromium-browser/chromium-wrapper

CC: (none) => davidwhodgins

Is this bug still valid with chromium 14 or 15 ?

yes, I have now uninstalled 11, then installed 14. 14 is the newest in the list of RPMs. Here is the output from a terminal...
---------
[barry@TheBox ~]$ chromium-browser &
[2] 7884
[barry@TheBox ~]$ Check failed: g_shutdown_pipe_write_fd != -1

[1]+  Killed                  chromium-browser
[barry@TheBox ~]$
--------------
chromium 14 still fails to start.

I hope this gives some clues

Barry.

seems it's an upstream bug:

(in french) http://forums.fedora-fr.org/viewtopic.php?id=54659
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627348

(and there is no updated debug package) 

But we lost the package maintainer :(

Keywords: NEEDINFO => (none)
Source RPM: chromium-browser 11.0.696.68 => chromium-browser
Whiteboard: check => (none)

(In reply to comment #5)
> yes, I have now uninstalled 11, then installed 14. 14 is the newest in the list
> of RPMs. Here is the output from a terminal...
> ---------
> [barry@TheBox ~]$ chromium-browser &
> [2] 7884
> [barry@TheBox ~]$ Check failed: g_shutdown_pipe_write_fd != -1

Searching on the error message led me to
http://scientificlinuxforum.org/m/index.php/t990.html

I'm guessing you are using selinux. Try (as root)
chcon -t usr_t /usr/lib/chromium-browser/chrome-sandbox

This is a standard mageia1 installation on a new partition. I have never used selinux.

Output of cmd....

[root@TheBox barry]$ chcon -t usr_t /usr/lib/chromium-browser/chrome-sandbox
chcon: failed to get security context of `/usr/lib/chromium-browser/chrome-sandbox': Operation not supported

Can you try starting xfce4 instead of icewm, to see if that has
anything to do with it?

chromium starts in xfce4 from konsole.

In icewm from both urxvt and konsole a zombie xterm is created, but nothing else. A cold restart is required to get rid of the zombie.

looks like icewm has a problem.

icewm still has the same version in Mga 1

assigning to maitainer.

@ zézinho

Feel free to assign back to BugSquad, if I was wrong to assign to you, and please explain.
However, please set status to ASSIGNED if you think this bug was assigned correctly. If for workflow reasons you can't do that, then please put OK on the whiteboard instead.

CC: (none) => marja11
Assignee: bugsquad => lists.jjorge
Summary: Chromium fails to start => Chromium fails to start in IceWM
Source RPM: chromium-browser => chromium-browser, icewm-1.3.3-7.mga1.src.rpm

I could not reproduce on my Mageia 1 x86_64. Can you please try the following :
- login as the xguest user
- launch chromium-browser from a terminal

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

deleted then reinstalled xguest pkg.
/home/xguest.pki was NOT created

restarted my box - runlevel 3
logged in as barry
started urxvt
su to xguest
ran chromium-browser, chrome starts with 3 or 4 procs but no gui appears and no messages on tty. ~/.pki was created but not its 3 subdirectories.

Ksysguard shows 4 procs 

Stopped with ^c then received 'Check failed: g_shutdown_pipe_write_fd != -1' on tty

@ José

Removed the NEEDINFO keyword here, too. AFAICT, the requested information was given in comment 13

Keywords: NEEDINFO => (none)

(In reply to comment #14)
> @ José
> 
> Removed the NEEDINFO keyword here, too. AFAICT, the requested information was
> given in comment 13

No : a xguest IceWM was not opened. Can anyone else try to launch chromium-browser in a IceWM session, because I can and Barry does not...

Works fine for me in an i586 system with Mageia 1.  That may well be
because I already have Gnome and KDE installed as well.

This message is a reminder that Mageia 1 is nearing its end of life. 
In approximately 25 days from now, Mageia will stop maintaining and issuing 
updates for Mageia 1. At that time this bug will be closed as WONTFIX (EOL) if it 
remains open with a Mageia 'version' of '1'.

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 prior to Mageia 1's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that we may not 
be able to fix it before Mageia 1 is end of life.  If you would still like to see 
this bug fixed and 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.

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.

--
Mageia Bugsquad

Mageia 1 changed to end-of-life (EOL) status on ''1st December''. Mageia 1 is no 
longer maintained, which means that it will not receive any further security or 
bug fix updates. As a result we are closing this bug. 

If you can reproduce this bug against a currently maintained version of Mageia 
please feel free to click on "Version" change it against that version of Mageia and reopen this bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

--
Mageia Bugsquad

Status: UNCONFIRMED => RESOLVED
Resolution: (none) => WONTFIX