Recommended Free Tools
A Chromium error such as undefined symbol: snd_device_name_get_hint, version ALSA_0.9 usually points to a compatibility problem between the browser binary and the libraries available at runtime on the Ubuntu host. It does not, by itself, identify a faulty package or prove that installing a particular ALSA version will fix the problem. Start by confirming which executable Puppeteer launches, then inspect that binary’s dependencies and the host’s distribution and architecture.
What this error means
When Puppeteer starts Chromium, the operating system’s dynamic linker loads the shared libraries the browser needs. A “symbol lookup error” means a program or library tried to resolve a named function and could not find a compatible definition in the library resolution available to that process. Here, the missing symbol is snd_device_name_get_hint, associated with ALSA, the Linux audio library interface.
This is different from a straightforward “shared library not found” message. A missing-library check can be useful, but a clean result does not rule out a symbol or ABI incompatibility: the library may be present yet not provide the symbol version the binary expects. The error alone also does not establish whether the cause is an outdated library, a mismatched browser build, or another aspect of the host’s runtime setup.
First confirm which browser Puppeteer is starting
Do not install packages or change launch flags until you know which browser executable is failing. Puppeteer can use a browser it manages or an executable configured by the application. Older installations may point to a browser under a .local-chromium directory; changing a system package will not necessarily affect that binary.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errors#1 Best Overall
- Powerful Linux Laptop: This IdeaPad Slim 3 Laptop comes pre-installed with Ubuntu Linux, offering fast performance, robust security, and a clean, user-friendly experience. Enjoy full customization, seamless hardware compatibility, and access to thousands of open-source apps. Whether you're working, creating, or coding, it's built to keep up with everything you do.
- A Multitasking Master: The latest AMD Ryzen 7 5825U processor (up to 4.5 GHz) delivers powerful performance with 8 cores and 16 threads for smooth multitasking. Integrated AMD Radeon Graphics provide crisp visuals for streaming, browsing, photo editing, and casual gaming. With smart machine intelligence, it adapts to your needs for a fast, responsive experience.
- 15.6" Full HD Display: The IdeaPad Slim 3 boasts an 88% screen-to-body ratio for a floating, edge-to-edge visual experience. TÜV Low Blue Light certification reduces eye strain, making it perfect for long work or study sessions.
- Military-Grade Durability: The smart IdeaPad Slim 3 combines portability and durability, letting you work, study, and play on the go. With a profile 10% slimmer than the previous generation, it's lightweight yet military-grade rugged, ready for anything, anywhere.
- Versatile Connectivity: Enjoy the security of a built-in webcam with a privacy shutter. Connect effortlessly with multiple ports: 2x USB A, 1x USB C, 1x HDMI, 1x SD Card Reader, 1x Headphone/Microphone combo. Bundle comes with Stylus Pen, 256GB Portable SSD and 5-in-1 Docking Station.
- Record the environment: run
node --versionandnpm ls puppeteer puppeteer-corein the project directory. Note the Ubuntu release and CPU architecture too:cat /etc/os-releaseanduname -m. - Inspect the application configuration: find any
executablePathsetting and note the exact path. Also check the installed Puppeteer version and how the browser was installed or downloaded. - Capture the complete launch error: retain the executable path, the full symbol error, and the surrounding browser output. Do not report only “Puppeteer failed to launch”; those details distinguish a linker failure from other startup problems.
If the application does not specify executablePath, inspect its Puppeteer setup and launch logs to establish which binary it actually uses. A path in an old error report or deployment script is not proof that the current process launches that same file.
Check the active binary’s shared-library dependencies
Run the dependency check against the exact executable identified above. Puppeteer’s Linux troubleshooting guidance recommends ldd chrome | grep not; substitute the real path if the binary is not named chrome or is not in the current directory:
ldd /path/to/active/chrome | grep notReplace /path/to/active/chrome with the actual executable path; it is notation, not a literal path to run. If the command prints libraries marked “not found,” investigate those specific dependencies on that Ubuntu release. If it prints nothing, that means this check found no unresolved shared-library names. It does not prove that every loaded library has the ABI or symbol version the browser requires.
Rank #2
- Intel Core i5-10210U (up to 4.2GHz) - 1TB PCIe NVMe + 1TB HDD - 32GB DDR4 SDRAM
- 17.3" HD+ (1600x900) Display, Intel UHD Graphics 620
- Built in HD 720p Webcam with Microphone - Bluetooth Version4.2
- I/O Ports: 2x USB 3.1 (Data Only), 1x USB 2.0, 1x HDMI, 1x Headphone/Microphone Combo Jack
- Linux Mint Cinnamon 64-Bit - 6-Row Keyboard w/ Full Numberpad
To examine what the linker resolves for the named ALSA library, inspect the active binary’s dependency output and the host’s library cache, for example:
ldd /path/to/active/chrome | grep -i asound
ldconfig -p | grep libasoundThese commands help identify the resolved library path or whether a library is discoverable; they do not certify that a particular browser build is compatible. Preserve the output and the original symbol error when comparing the host with a known-good environment or asking for help.
Repair only dependencies the diagnostics identify
Puppeteer’s Debian/Ubuntu troubleshooting list includes libasound2 among a wider set of runtime dependencies. It also names packages for accessibility, graphics, fonts, GTK, NSS, Pango, X libraries and other runtime components. The documentation cautions that its dependency notes can become outdated and points readers to Chromium’s installer dependency manifest. Package names and availability can vary with Ubuntu release and enabled repositories, so validate guidance against the target host rather than copying a package list blindly.
Rank #3
- Intel Core i5-1335U Processor (12M Cache, 12 Threads, up to 4.6 GHz) - 256GB Solid State Drive - 16GB DDR4 SDRAM
- 15.6" FHD (1920x1080) Non-Touch Anti-Glare Display - Intel UHD 620 Integrated Graphics - Stereo Speakers
- 720p HD Webcam with Privacy Shutter. Integrated Microphone - Intel Dual Band Wireless-AC (2x2) 8265, Bluetooth Version 4.2
- I/O Ports: 2x USB 3.0, 1x USB 3.1 Type-C 3.1, Headphone/Mic Combo Port, 4-in-1 Card Reader, HDMI, Kensington Mini-Lock Slot
- Linux Mint (Cinnamon) 64-Bit - Keyboard with Full NumberPad - Fast Charging
- If
lddreports a library as missing, identify the Ubuntu package that supplies that library for the host’s release and architecture, then install or repair that package using the host’s configured repositories. - If the error names ALSA but
libasoundis present, do not assume that reinstalling it is the answer. Determine which library path is loaded and whether the browser expects a symbol or version unavailable there. - If the package state appears correct but the symbol error persists, compare the browser build and host runtime. A different compatible browser build may be more appropriate than adding unrelated packages, but the correct choice depends on the environment.
There is no universally established ALSA-specific package command for this exact symbol error. The published troubleshooting guide’s dependency list is a starting point for missing-library diagnosis, not a guarantee that a particular reinstall or upgrade resolves every symbol lookup failure.
Check Ubuntu, architecture and browser compatibility
Compare the browser binary with the target system’s Ubuntu release and CPU architecture. A binary that works on one Linux host is not automatically compatible with another host’s libraries or architecture. The Puppeteer GitHub report for this exact ALSA symbol error came from an EC2-hosted application using a legacy .local-chromium path. In that report, a maintainer asked for a current reproduction and the Linux distribution/version and CPU architecture, noting that the reported system appeared incompatible with prebuilt Chromium binaries. That is useful diagnostic direction for that report, not a confirmed root cause for every Ubuntu installation.
When gathering details, include:
- Ubuntu release information from
/etc/os-releaseand architecture fromuname -m. - Node.js and Puppeteer versions, plus how the browser was obtained.
- The exact executable path, full error output, and the relevant
lddresults. - A minimal current reproduction showing how the application launches Puppeteer.
If the application still launches a legacy or externally downloaded browser, compare it with a clean installation using a browser supported by the installed Puppeteer version. In the issue report, the maintainer noted that Puppeteer had moved away from the old Chromium download and asked for a reproduction with current Puppeteer, which uses Chrome for Testing. Browser releases and Ubuntu library sets change over time; verify the current installation path and version instead of assuming an old project’s download behavior still applies.
Rank #4
Keep sandbox errors separate
--no-sandbox is not the documented general remedy for undefined symbol: snd_device_name_get_hint. Puppeteer discusses that flag in relation to a different startup error, No usable sandbox!. Its guidance strongly discourages disabling the browser sandbox and recommends sandboxed execution. Do not add the flag to a symbol-error workaround simply because an online comment bundled it with package-install commands. If the actual error is No usable sandbox!, follow Puppeteer’s sandbox guidance and only consider running without the sandbox when the opened content is absolutely trusted.
Troubleshooting by symptom
| Symptom | What to check | Next step |
|---|---|---|
ldd reports a dependency as “not found” |
Confirm the check used the executable Puppeteer actually launches and identify the missing library. | Find and install the release-appropriate package for that specific dependency; rerun the check. |
ldd finds libraries, but the ALSA symbol error remains |
Check the resolved libasound path and compare the browser build with the host’s distribution and architecture. |
Investigate library resolution or test a browser build compatible with the host. A clean missing-library check alone does not settle symbol compatibility. |
| A package change had no effect | Check whether the changed system library belongs to the active browser’s runtime and whether Puppeteer uses a bundled or custom executable. | Repeat diagnostics against the exact active binary before making further package changes. |
The error comes from a .local-chromium path |
Establish whether the project is using a legacy browser download and record installed Puppeteer/browser versions. | Compare with a current Puppeteer setup and its supported Chrome for Testing installation; validate compatibility on the target host. |
The error says No usable sandbox! |
Confirm that this is the actual error rather than an ALSA symbol lookup failure. | Use Puppeteer’s sandbox guidance. Disabling the sandbox is strongly discouraged and is not a general fix for linker errors. |
Or skip the browser setup
If your goal is to capture website screenshots rather than operate Chromium yourself, ScreenshotNeo provides a screenshot API and MCP server. A single GET request returns a PNG, JPEG, WebP or PDF. For example, this cURL request saves a WebP screenshot of Stripe; the parameter names other screenshot APIs use also work, which can ease switching. See the ScreenshotNeo API documentation for options and response details.
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpScreenshotNeo accepts cookie or consent banners as a visitor and removes more than 60 known consent platforms, newsletter popups and chat widgets before capture; each of those steps can be turned off. Bot checks, blank pages, timeouts, failed loads and cache hits are not billed, and the response indicates the page verdict and billing status in headers. Its MCP server gives AI agents tools for screenshots, page information and PDF capture. The Free plan includes 1,000 screenshots per month with no card; paid plans start at $5 for 3,000 screenshots.
Sign up for ScreenshotNeo’s free plan to try 1,000 screenshots a month with no card.
Best Value
- 12th Intel Alder Lake N95 Processor – The GMKtec G3 S Mini PC is powered by the 12th Gen Intel N95 processor with 4 cores, 4 threads, 6MB cache and a burst frequency up to 3.4GHz. Compared with N100/N5105/N5100/N5095, the N95 delivers up to 36% overall performance improvement. Perfect for routine tasks, office work, and home entertainment, this compact mini desktop is more convenient than traditional bulky PCs.
- 8GB RAM & 256GB SSD Storage – Pre-installed with 8GB DDR4 memory and a fast 256GB M.2 2242 SSD, the G3 S mini desktop offers quicker startup, smoother multitasking, and faster file transfers. Enjoy seamless performance whether you’re working on multiple applications, browsing, or streaming content.
- Rich Interfaces & Connectivity – The G3 S mini computer comes equipped with USB 3.2 (up to 10Gbps), dual HDMI 2.0 (4K@60Hz), and a 3.5mm audio jack. With support for WiFi 5, Bluetooth 5.0, and Gigabit Ethernet (RJ45 1000MbE), it connects easily with monitors, projectors, printers, office equipment, and other peripherals, making it versatile for both home and business use.
- Dual 4K Display Support – Featuring upgraded Intel UHD Graphics (up to 1000MHz), the G3 S supports 4K video playback and AV1 decoding for a smooth viewing experience. With dual HDMI outputs, you can connect two 4K@60Hz displays simultaneously, enabling efficient multitasking for work and entertainment.
- GMKtec WARRANTY - GMKtec offers a 1-year limited GMKtec's warranty for each mini PC, starting from the date of the purchase. All defects due to design and workmanship are covered. With a professional after sales team always ready to attend to your needs, you can simply relax and enjoy your mini PC.
Frequently Asked Questions
Does the ALSA symbol error mean Ubuntu is missing libasound2?
Not necessarily. The error identifies an unresolved symbol, but does not establish whether the library is absent, incompatible, or being resolved from an unexpected path.
Should I use the system Chromium executable instead?
Not automatically. First compare its compatibility with the host and confirm that it is supported by the installed Puppeteer version; changing executables can introduce a different compatibility problem.
Is this the same as Puppeteer’s “No usable sandbox!” error?
No. They are distinct errors with different diagnostic paths.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchQuick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
