Chromium doesn't get launched on Guix #265
Labels
compatibility
Something is not working, and it's not our fault.
upstream
Issue related to an upstream library
Comments
|
Hey @wehlutyk , thanks for the report! That's interesting, it hangs after the "unzip" stage. Which auth method did you use? Before I'm able to reproduce the issue or look into fixing it, you have the following workarounds availble:
There are two types of login that the new automation supports:
I should probably document this. |
|
Hey @wehlutyk , have you had a chance to try the suggested steps? |
|
Hey @rusq , apologies for the lag! I git pulled, then cleaned:
I can select it, but still no window opens.
Then a few checks:
Now selecting I'm not sure why downloaded chromium doesn't get seen. |
|
Exploring a little more: sl@beoga ~/C/S/slackdump (master) > /home/sl/.cache/ms-playwright-go/1.41.1/node ~/.cache/ms-playwright-go/1.41.1/package/lib/cli/cli.js --test
fish: Job 1, '/home/sl/.cache/ms-playwright-g…' terminated by signal SIGSEGV (Address boundary error)but using the system's sl@beoga ~/C/S/slackdump (master) > node ~/.cache/ms-playwright-go/1.41.1/package/lib/cli/cli.js
Usage: npx playwright [options] [command]
[...]So playing with playwright shows: sl@beoga ~/C/S/slackdump (master) > node ~/.cache/ms-playwright-go/1.41.1/package/lib/cli/cli.js open
Error: Executable doesn't exist at /home/sl/.cache/ms-playwright/chromium-1097/chrome-linux/chrome
╔═════════════════════════════════════════════════════════════════════════╗
║ Looks like Playwright Test or Playwright was just installed or updated. ║
║ Please run the following command to download new browsers: ║
║ ║
║ npx playwright install ║
║ ║
║ <3 Playwright Team ║
╚═════════════════════════════════════════════════════════════════════════╝
sl@beoga ~/C/S/slackdump (master) > npx playwright install
Need to install the following packages:
playwright@1.42.1
Ok to proceed? (y)
╔═══════════════════════════════════════════════════════════════════════════════╗
║ WARNING: It looks like you are running 'npx playwright install' without first ║
║ installing your project's dependencies. ║
║ ║
║ To avoid unexpected behavior, please install your dependencies first, and ║
║ then run Playwright's install command: ║
║ ║
║ npm install ║
║ npx playwright install ║
║ ║
║ If your project does not yet depend on Playwright, first install the ║
║ applicable npm package (most commonly @playwright/test), and ║
║ then run Playwright's install command to download the browsers: ║
║ ║
║ npm install @playwright/test ║
║ npx playwright install ║
║ ║
╚═══════════════════════════════════════════════════════════════════════════════╝
BEWARE: your OS is not officially supported by Playwright; downloading fallback build for ubuntu20.04-x64.
Downloading Chromium 123.0.6312.4 (playwright build v1105) from https://playwright.azureedge.net/builds/chromium/1105/chromium-linux.zip
154.7 MiB [====================] 100% 0.0s
Chromium 123.0.6312.4 (playwright build v1105) downloaded to /home/sl/.cache/ms-playwright/chromium-1105
BEWARE: your OS is not officially supported by Playwright; downloading fallback build for ubuntu20.04-x64.
Downloading FFMPEG playwright build v1009 from https://playwright.azureedge.net/builds/ffmpeg/1009/ffmpeg-linux.zip
2.6 MiB [====================] 100% 0.0s
FFMPEG playwright build v1009 downloaded to /home/sl/.cache/ms-playwright/ffmpeg-1009
BEWARE: your OS is not officially supported by Playwright; downloading fallback build for ubuntu20.04-x64.
Downloading Firefox 123.0 (playwright build v1440) from https://playwright.azureedge.net/builds/firefox/1440/firefox-ubuntu-20.04.zip
84.7 MiB [====================] 100% 0.0s
Firefox 123.0 (playwright build v1440) downloaded to /home/sl/.cache/ms-playwright/firefox-1440
BEWARE: your OS is not officially supported by Playwright; downloading fallback build for ubuntu20.04-x64.
Downloading Webkit 17.4 (playwright build v1983) from https://playwright.azureedge.net/builds/webkit/1983/webkit-ubuntu-20.04.zip
133.2 MiB [====================] 100% 0.0s
Webkit 17.4 (playwright build v1983) downloaded to /home/sl/.cache/ms-playwright/webkit-1983
Playwright Host validation warning:
╔══════════════════════════════════════════════════════╗
║ Host system is missing dependencies to run browsers. ║
║ Missing libraries: ║
║ libgobject-2.0.so.0 ║
║ libglib-2.0.so.0 ║
║ libnss3.so ║
║ libnssutil3.so ║
║ libsmime3.so ║
║ libnspr4.so ║
║ libdbus-1.so.3 ║
║ libatk-1.0.so.0 ║
║ libatk-bridge-2.0.so.0 ║
║ libcups.so.2 ║
║ libgio-2.0.so.0 ║
║ libdrm.so.2 ║
║ libatspi.so.0 ║
║ libexpat.so.1 ║
║ libX11.so.6 ║
║ libXcomposite.so.1 ║
║ libXdamage.so.1 ║
║ libXext.so.6 ║
║ libXfixes.so.3 ║
║ libXrandr.so.2 ║
║ libgbm.so.1 ║
║ libxcb.so.1 ║
║ libxkbcommon.so.0 ║
║ libpango-1.0.so.0 ║
║ libcairo.so.2 ║
║ libasound.so.2 ║
║ libgcc_s.so.1 ║
╚══════════════════════════════════════════════════════╝
at validateDependenciesLinux (/home/sl/.npm/_npx/e41f203b7505f1fb/node_modules/playwright-core/lib/server/registry/dependencies.js:216:9)
at async Registry._validateHostRequirements (/home/sl/.npm/_npx/e41f203b7505f1fb/node_modules/playwright-core/lib/server/registry/index.js:627:43)
at async Registry._validateHostRequirementsForExecutableIfNeeded (/home/sl/.npm/_npx/e41f203b7505f1fb/node_modules/playwright-core/lib/server/registry/index.js:725:7)
at async Registry.validateHostRequirementsForExecutablesIfNeeded (/home/sl/.npm/_npx/e41f203b7505f1fb/node_modules/playwright-core/lib/server/registry/index.js:714:43)
at async t.<anonymous> (/home/sl/.npm/_npx/e41f203b7505f1fb/node_modules/playwright-core/lib/cli/program.js:119:7)
npm notice
npm notice New minor version of npm available! 10.2.3 -> 10.5.0
npm notice Changelog: https://github.com/npm/cli/releases/tag/v10.5.0
npm notice Run npm install -g npm@10.5.0 to update!
npm notice Now, not having made any node project inside Guix, I'm not sure the library paths are compatible. But maybe that's not the problem as I'm running npx/npm completely out of context. |
|
Hey @wehlutyk thanks for your investigation! This looks like compatibility issue with Guix that could be raised with playwright/go-rod teams? Looks like it misses some dependency libraries, but clearly if you're expecting the browser to open, so you have X11 installed, and they should be present on the system (i.e. "libX11.so.6").
When I wrote "Follow the Manual steps", I meant manually retrieving the slack token and cookie values from the browser, as per this guide, this doesn't need the browser automation, as everything it needs (token, cookies) is provided manually. If you go down this route, I suggest exporting the cookies to the "cookies.txt" file. |
rusq
added
upstream
|
|
Now, cleaning again: Then: Might indeed be an issue to explore with the playwright/go-rod teams :) Then just to check: |
|
Thanks for the browser's token point! I'll try that in the meantime -- hoping it can also manually solve #273 which I just bumped into when trying this in an Ubuntu VM. |
|
No problem, sorry, can't be of much help with this, thank you for all the diagnostics. I doubt that the manual method will help overriding the issue described in #273 as it is API restriction. Interestingly, many people are facing it now, seems to be something fresh. I'll close this issue for now, but please let me know if you're able to fix it, it would be great to include these instructions in the readme. |
|
Just to mention, the manual method seems to work (under Ubuntu, ongoing)! The snippet In my case the token was reached by replacing |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
./slackdumpon Guix just hangs after downloading Chromium (be it the release or dev version).To Reproduce
Download current release, and run
./slackdumpwith any configuration.For the dev version, get
goenvironment in Guix by runningguix shell --network go, thengo build ./cmd/slackdumpas in the instructions, and run as above.Expected behavior
I expect Chromium to open up for signing in. But no browser appears and the log just hangs there.
Output
Desktop (please complete the following information):
Additional context
None.
The text was updated successfully, but these errors were encountered: