chrome-aws-lambda VS steam-for-linux

Lambda would be my choice for this. You could even stay within the free tier depending how often you run this process. You can orchestrate puppeteer UI flows in lambda using this package https://github.com/alixaxel/chrome-aws-lambda My team does this and it works great.

git clone --depth=1 https://github.com/alixaxel/chrome-aws-lambda.git && \ cd chrome-aws-lambda && \ make chrome_aws_lambda.zip

When requesting the API route, the Next.js serverless function will actually spin up a web browser on the server (a headless instance of Chromium, using chrome-aws-lambda). Next, a webpage will be generated with HTML we can define ourselves. This HTML will be used to construct the image. That means that as a developer we can generate images using HTML and CSS, technologies we are already familiar with!

This plugin is used for all our AWS Lambda deployments, using a wide range of Node modules, some with more quirks than others. We use it together with Lambda Layer Sharp and Chrome AWS Lambda.

I was able to successfully to run chrome with puppeteer in AWS Lambda for a similar use case. I used an "optimized" version of chrome packaged as an AWS Lambda Layer.

git clone --depth=1 https://github.com/alixaxel/chrome-aws-lambda.git && \ cd chrome-aws-lambda && \ make chrome_aws_lambda.zip

Simplest method use ]Puppeteer](https://blog.risingstack.com/pdf-from-html-node-js-puppeteer/) with chrome-aws-lambda.

For example, we can use chrome-aws-lambda binaries. They were built to fit Lambda layers, so the size is much smaller than regular chrome installation.

I just spent a few hours working on that problem that Steam takes very long to appear. I did not have xdg-desktop-portal-gnome installed, and Steam is the only application that has that problem, so it's not the one from the update forum post. What my (and probably your) problem is, is this one: https://github.com/ValveSoftware/steam-for-linux/issues/9780. Some bug where CEF gets stuck in a loop. When I executed steam --reset an error about steamwebhelper and glibc appeared like 50 times, each taking a few seconds.

The issue seems to be the steamwebhelper constantly crashing. It only appears to be happening when starting Steam with my dedicated GPU and not with the integrated GPU. So right clicking and starting with your integrated GPU should work while the issue is not fixed.

There's a github issue and a much older discussion thread.

Uninstalling the xdg-desktop-portal-gnome package fixed it as described in this old issue thread.

Following the latest UI update from Steam on all systems and the newest NVIDIA driver version (535.43.02), some Linux users had their Steam clients constantly crashing, including my own. An issue has been filed under Steam's Linux port on GitHub and a section has been added to the official troubleshooting page for Steam on the official ArchLinux site. If you wish to use sudo pacman -Syu to update your software, I advise that you be wary of these versions, as they WILL cause Steam to fail upon launch for NVIDIA users.

I can't link OP's bug report but have a look here and here.

GitHub link