Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Dartium viewport is always grey on Linux x64 with 1.5.1 #19718

Closed
DartBot opened this issue Jun 29, 2014 · 19 comments
Closed

Dartium viewport is always grey on Linux x64 with 1.5.1 #19718

DartBot opened this issue Jun 29, 2014 · 19 comments
Labels
closed-cannot-reproduce Closed as we were unable to reproduce the reported issue P1 A high priority bug; for example, a single project is unusable or has many test failures
Milestone
1.9

Comments

@DartBot
Copy link

DartBot commented Jun 29, 2014

This issue was originally filed by chris.eee...@gmail.com

  1. Start Dartium with $INSTALL_DIR/dart/chromium/chrome

Expect Dartium to start properly, but get dark grey viewport that does not change when entering URLs.

The following errors are on the terminal console:

[30843:30843:0628/225215:ERROR:browser_main_loop.cc(163)] Running without the SUID sandbox! See https://code.google.com/p/chromium/wiki/LinuxSUIDSandboxDevelopment for more information on developing with the sandbox on.
LaunchProcess: failed to execvp:
/home/chris/local/dart/chromium/chrome
LaunchProcess: failed to execvp:
/proc/self/exe
[30843:30843:0628/225215:ERROR:child_process_launcher.cc(329)] Failed to launch child process
[30843:30858:0628/225215:ERROR:raw_channel_posix.cc(139)] recvmsg: Connection reset by peer
[30843:30858:0628/225215:ERROR:channel.cc(297)] RawChannel fatal error (type 1)

This is Dartium that is bundled with DartEditor Dart VM version: 1.5.1 (Tue Jun 24 04:17:09 2014) on "linux_x64"
@floitschG
Copy link
Contributor

Added Area-Dartium, Triaged labels.

@vsmenon
Copy link
Member

vsmenon commented Jun 30, 2014

What version of Linux are you running? I assume Dartium doesn't run from the editor either?

Is this a fresh install or did you upgrade a previous version?

@DartBot
Copy link
Author

DartBot commented Jul 1, 2014

This comment was originally written by chris.eee...@gmail.com

Bah. I cannot reproduce this any longer after a system restart.

I am running Mint 15. This was a fresh install. I had closed all previous Dartiums (and Chromes), but was unable to start Dartium properly (and without the “failed to execvp” error). But a system restart and all is well.

This looks to be a one-time only bug on a single user system. Feel free to close.

@DartBot
Copy link
Author

DartBot commented Aug 3, 2014

This comment was originally written by @pjjjv

I'm seeing this after I updated the dart toolchain from 1.1 to 1.5.3 (all stable). This is on Mint Linux amd64. I also tried standalone dartium (dartium-lucid64-full-stable-37972.0), as well as the ubuntu-packages dart toolchain from Hachre.

This bug also seems to exist generically in chromium, but since I couldn't find a solution or an exact match on linux, I'd thought I'd start here.

Needless to say my regular stable chrome 36.0.1985.125 runs well enough. I also tried standalone dartium (dartium-lucid64-full-27560.0; 31.0.1612.0 (219647), which is the oldest I could find), and that works.

Dartium does not run from darteditor either. Linux 3.8.0-25-generic.

$ dartium
[3514:3514:0804/002126:ERROR:browser_main_loop.cc(163)] Running without the SUID sandbox! See https://code.google.com/p/chromium/wiki/LinuxSUIDSandboxDevelopment for more information on developing with the sandbox on.
LaunchProcess: failed to execvp:
/opt/google/dartium/chromium
[3514:3569:0804/002126:ERROR:nss_util.cc(853)] After loading Root Certs, loaded==false: NSS error code: -8018
LaunchProcess: failed to execvp:
/proc/self/exe
[3514:3514:0804/002127:ERROR:child_process_launcher.cc(329)] Failed to launch child process
LaunchProcess: failed to execvp:
/proc/self/exe
[3514:3514:0804/002127:ERROR:child_process_launcher.cc(329)] Failed to launch child process
[3514:3569:0804/002127:ERROR:raw_channel_posix.cc(139)] recvmsg: Verbinding is weggevallen
[3514:3569:0804/002127:ERROR:channel.cc(297)] RawChannel fatal error (type 1)
[3514:3514:0804/002127:ERROR:child_process_launcher.cc(329)] Failed to launch child process
[3514:3514:0804/002127:ERROR:child_process_launcher.cc(329)] Failed to launch child process
[3514:3569:0804/002127:ERROR:raw_channel_posix.cc(139)] recvmsg: Verbinding is weggevallen
[3514:3569:0804/002127:ERROR:channel.cc(297)] RawChannel fatal error (type 1)
[3514:3569:0804/002127:ERROR:child_process_launcher.cc(329)] Failed to launch child process
[3514:3569:08

@DartBot
Copy link
Author

DartBot commented Aug 6, 2014

This comment was originally written by @pjjjv

Seems I forgot to update, but "dartium-lucid64-full-stable-37348.0" is the last one that works for me. Version 37644 (from http://gsdview.appspot.com/dart-archive/channels/stable/release/) does not work any more. So the problem has likely been introduced in between.

@DartBot
Copy link
Author

DartBot commented Aug 7, 2014

This comment was originally written by @rodrigob

I have the same issue.
As reported in #­366056 using --single-process is a work around (changed chrome to be a script calling chrome --single-process so as to be able to use the dart editor as usual).

https://code.google.com/p/chromium/issues/detail?id=366056

@DartBot
Copy link
Author

DartBot commented Aug 7, 2014

This comment was originally written by @pjjjv

Thanks. Hadn't seen that yet. I've added the --single-process to the DartEditor run launcher for my project for now (which is a bit easier but more temporary).

@sethladd
Copy link
Contributor

This was reported in https://plus.google.com/u/0/+Pieter-JanVandormael/posts/c4JRzD1msMb

Can we take a look?

cc @vsmenon.
cc @a-siva.
Added this to the 1.6 milestone.
Removed Priority-Unassigned label.
Added Priority-Medium label.

@kasperl
Copy link

kasperl commented Aug 12, 2014

Removed Priority-Medium label.
Added Priority-High label.

@vsmenon
Copy link
Member

vsmenon commented Aug 13, 2014

It appears that the upstream chromium bug is fixed?

Can someone please try the latest dev dartium?:

http://storage.googleapis.com/dart-archive/channels/dev/release/latest/dartium/dartium-linux-x64-release.zip

This is now based on Chromium 37. (Stable / 1.5 is based on Chromium 36.)

@DartBot
Copy link
Author

DartBot commented Aug 13, 2014

This comment was originally written by @pjjjv

38967 does not work for me, same thing

@DartBot
Copy link
Author

DartBot commented Aug 14, 2014

This comment was originally written by @rodrigob

Same here dartium-lucid64-full-dev-38967.0 had exactly the same buggy
behaviour.

@dgrove
Copy link
Contributor

dgrove commented Aug 20, 2014

This appears to be an upstream chromium issue. Can some of the reporters try out content_shell (get it by running chromium/download_contentshell.sh from the editor directory)?

Removed this from the 1.6 milestone.
Added this to the 1.7 milestone.
Removed Priority-High label.
Added Priority-Medium label.

@kasperl
Copy link

kasperl commented Aug 26, 2014

I assume these are tagged for 1.7 because they are high priority issues. If not, please remove the milestone and lower the priority again.

Removed Priority-Medium label.
Added Priority-High label.

@DartBot
Copy link
Author

DartBot commented Aug 26, 2014

This comment was originally written by @rodrigob

Using drt-lucid64-full-stable-38663.0/content_shell also fails (page stays blank).
Adding --single-process works fine there too.

The same goes for dev-38967.

It there anything particular to do with content_shell? (some debug mode ?)

@DartBot
Copy link
Author

DartBot commented Aug 26, 2014

This comment was originally written by @pjjjv

Same as #­16: drt-lucid64-full-stable-37972.0/content_shell fails (stays blank).

@DartBot
Copy link
Author

DartBot commented Aug 27, 2014

This comment was originally written by vlo...@gmail.com

Got the same probleme on elementaryOS:Luna (=ubuntu 12.04), here is contentShell output:

...~/dart/chromium/drt-lucid64-full-stable-39553.0$ ./content_shell

[3125:3125:0827/202309:75779754712:ERROR:browser_main_loop.cc(161)] Running without the SUID sandbox! See https://code.google.com/p/chromium/wiki/LinuxSUIDSandboxDevelopment for more information on developing with the sandbox on.

LaunchProcess: failed to execvp:
/home/vloz/dart/chromium/drt-lucid64-full-stable-39553.0/content_shell
LaunchProcess: failed to execvp:
/proc/self/exe
[3125:3145:0827/202310:75779864880:WARNING:proxy_service.cc(901)] PAC support disabled because there is no system implementation
[3125:3125:0827/202310:75779901083:ERROR:child_process_launcher.cc(344)] Failed to launch child process
[3125:3145:0827/202310:75779908517:WARNING:raw_channel_posix.cc(214)] recvmsg: Connexion ré-initialisée par le correspondant
[3125:3125:0827/202352:75822460540:ERROR:child_process_launcher.cc(344)] Failed to launch child process

@vsmenon
Copy link
Member

vsmenon commented Sep 24, 2014

Removed this from the 1.7 milestone.
Added this to the 1.8 milestone.

@vsmenon
Copy link
Member

vsmenon commented Oct 15, 2014

Removed this from the 1.8 milestone.

@DartBot DartBot added Type-Defect P1 A high priority bug; for example, a single project is unusable or has many test failures closed-cannot-reproduce Closed as we were unable to reproduce the reported issue labels Oct 15, 2014
@DartBot DartBot added this to the 1.9 milestone Oct 15, 2014
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
closed-cannot-reproduce Closed as we were unable to reproduce the reported issue P1 A high priority bug; for example, a single project is unusable or has many test failures
Projects
None yet
Milestone
1.9
Development

No branches or pull requests
6 participants
@sethladd @dgrove @vsmenon @kasperl @floitschG @DartBot