-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
Launch Hanging on Ubuntu when snap
version of Chromium is installed
#7020
Comments
Same problem here. Happened after Ubuntu wanted to update so perhaps the list of last updated packages can be helpful:
And as OP I'm on:
Normally I'd roll back the packages and be on my marry way but it seems apt does not support this, so I'll be moving on to a more stable distro. I'll keep this install around if any further testing is needed though. |
I am also experiencing this issue, but I am using ubuntu 18.04. Edit: After installing chromium it started to work again (was using google chrome before). Not sure if we have the same issue here, as DieterE has already installed chromium as you can see in the updated packages. Edit2: I actually first uninstalled chromium from snapd and reinstalled with apt. |
stuck today on my work. i refresh everything but none of that resolve the issue. please help @bahmutov @jennifer-shehane Fixed it by removing chromium browser on my laptop |
I also have that issue:
Similar issue that I reported: #7027 Removed chromium from snapd and regular apt and now is worked. |
Thanks for reporting the problem, I have the same issue on my workstation. I think removing Chromium is just a way to get around this, I think we need a fix. In any case, I still haven't understood what the problem is, Chromium or cypress? Does anyone know? |
Thanks for the report. In my case: ubuntu 19.10 the same problem. Removing Chromium didn't help. Is there any progress on it? UPD: Removing Chromium actually helps. Forgot to remvoe it from snap package |
I can reproduce this by installing Chromium as a snap instead of via apt. Workaround:Install Chromium via apt ( |
In my case, on Ubuntu 18.04, the test launcher window would open using |
One of my colleagues saw the following output in his Visual Studio Code terminal after running
|
I've managed to fix the browser detection in #7039; however, when launching Chromium as a snap, it exits because of permission issues writing to the Cypress profile dir:
Guessing that this is because the snap's sandboxing only allows it to write to certain locations, and the Cypress profile dir falls outside of those locations. Anyone know how to change the locations the snap is allowed to access? |
Is it possible to run cypress without chromium (even if installed with snap) and possibly report the problem with a message on the UI? Why is the error present even when I execute cypress with the |
@erosval Internally, that command runs the regular browser detection and then filters "firefox" from the list of detected browsers, so it hangs in the same place. It should probably be optimized to only lookup browsers matching the passed flag. Try passing
Yeah, in the meantime, Cypress could still detect the Snap version of Chromium, and add a warning to it in the GUI that it may fail to launch. But I'd like to do some investigation to see if there's an easy way for users to fix this... for example, if it's possible to whitelist the Cypress profile dir manually, which would be like a one-time fix we can document and point users to. |
Also solved by uninstalling the snap version of Chromium. Thanks @Lektro9 & @jbpallingayan. |
snap
version of Chromium is installed
snap
version of Chromium is installedsnap
version of Chromium is installed
Seems the apt version of chromium is updated now too :( Mine is installed using apt, as exposes the same behavior |
Looks like in Ubuntu 19.10, the developers started shipping There's a link to this PPA which can be used to install Chromium as a regular binary, as a workaround: https://launchpad.net/~saiarcot895/+archive/ubuntu/chromium-dev Side note: I use a fork of Ubuntu called Pop_OS, I am also on 19.10 but it seems like my
|
For those on Ubuntu 19.10 and above who doesn't want to use a ppa there's a pure snap based solution too. First close chromium and chromium.launcher then change the channel on snap:
Edit: looks like my workaround was a one-off on my machine, so the PPA suggested earlier is probably a safer bet. A possibly useful comment from TheLukeMcCarthy on Stack Overflow: "I uninstalled Chromium and re-installed using apt. It didn't remove the snap link in /usr/local/bin/chromium-browser so it seemed to reinstall snap chromium when I run cypress. I finally got it to work when I uninstalled chromium, manually deleted the link /usr/local/bin/chromium-browser installed Chromium with apt when manually create the link /usr/local/bin/chromium-browser again" |
Hello everyone, Just to let you know that removing chromium from |
@Anomen are you running without Chromium on your system, then? |
Yes, I use Chrome, not Chromium-browser. Sometimes I liked having chromium for a few tests, but since I haven't used it for a long time, it doesn't bother me to uninstall it. The command that I ran to remove chromium was: |
The code for this is done in cypress-io/cypress#7039, but has yet to be released. |
And a workaround that doesn't require any changes in packages, change the path for the command until the patch is on npm: For fish shells:
for bash and similar:
Make sure to adjust the path for your system, so start by doing |
Released in This comment thread has been locked. If you are still experiencing this issue after upgrading to |
Current behavior:
cypress open
does not open Cypress.cypress run
just seems to hang.Logs:
https://pastebin.com/ULZwQEj8
Snapshot of behavior and logs:
System:
Desired behavior:
Should be able to run tests.
Test code to reproduce
As this is happening prior to Cypress running I don't think its anything I can give reproduction steps for.
DEBUG=* $(npm bin)/cypress open
DEBUG=* $(npm bin)/cypress run
Are the commands I am running.
Versions
v4.3.0 and v4.4.0
The text was updated successfully, but these errors were encountered: