chromium doesn't starts with superkb

Bug #491513 reported by biker on 2009-12-02
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Superkb
Undecided
Unassigned

Bug Description

when I try to launch chromium with superkb, it throws me this error:

[3880:3880:4927910303:FATAL:/mnt/chromium/rpmbuild/BUILD/chromium-20091119svn32498/src/chrome/browser/zygote_host_linux.cc(167)] Check failed: pid_ > 0. Did not find zygote process

Octavio Alvarez (alvarezp) wrote :

I'm not sure if this is a Superkb bug or a Chromium one.

If you do <code>watch -n 0.01 'ps fax | tac'</code> you will see that the Chromium files are being correctly launched, being Chromium apparently at failure for not being able to recognize the zygote process.

As a workaround, you can use your terminal commands like "gnome-terminal -x chromium-browser" for launching it. You'll get an ugly terminal window in the back while running the browser, though.

Octavio Alvarez (alvarezp) wrote :

The following code triggers the problem.

$ cat test.c
#include <signal.h>
int main() {
 signal(SIGCHLD, SIG_IGN);

 if (fork() == 0) {
  system("chromium-browser\n");
 }
}

$ gcc -o test test.c
$ ./test

[18123:18123:7759939325:FATAL:/build/buildd/chromium-
browser-4.0.262.0~svn20091202r33615/build-tree/src/chrome/browser/
zygote_host_linux.cc(167)] Check failed: pid_ > 0. Did not find zygote
process

Octavio Alvarez (alvarezp) wrote :

This has been reported to the Chromium project as bug #29279
http://code.google.com/p/chromium/issues/detail?id=29279

Changed in superkb:
status: New → Incomplete
Octavio Alvarez (alvarezp) wrote :

Because the Chromium project acknowledged the bug and prepared a patch, this is not a bug in Superkb. Therefore I'm closing the bug as Invalid.

Changed in superkb:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.