void-linux / void-linux/void-packages

Cannot start qutebrowser 3.5.1_1

Open
#57,772 18 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug needs-testing
Dominant language
Shell
Stars
3.4k
Forks
2.8k
Avg merge
2d 5h
Merged PRs (30d)
299

Description

Is this a new report?

Yes

System Info

Void 6.14.11_1 x86_64-musl AuthenticAMD uptodate rr

Package(s) Affected

qutebrowser-3.5.1_1

Does a report exist for this bug with the project's home (upstream) and/or another distro?

No response

Expected behaviour

qutebrowser starts

Actual behaviour

qutebrowser immediately crashes on start:

$ qutebrowser
10:43:52 WARNING: Could not find the Qt platform plugin "wayland" in ""
[1:1:1105/104352.776307:ERROR:content_main_runner_impl.cc(419)] Unable to load CDM /home/bp99/.config/chromium/WidevineCdm/4.10.2891.0/_platform_specific/linux_x64/libwidevinecdm.so (error: Error loading shared library ld-linux-x86-64.so.2: No such file or directory (needed by /home/bp99/.config/chromium/WidevineCdm/4.10.2891.0/_platform_specific/linux_x64/libwidevinecdm.so))
[14266:14266:1105/104352.776339:ERROR:content_main_runner_impl.cc(419)] Unable to load CDM /home/bp99/.config/chromium/WidevineCdm/4.10.2891.0/_platform_specific/linux_x64/libwidevinecdm.so (error: Error loading shared library ld-linux-x86-64.so.2: No such file or directory (needed by /home/bp99/.config/chromium/WidevineCdm/4.10.2891.0/_platform_specific/linux_x64/libwidevinecdm.so))
[1:1:1105/104352.776731:FATAL:credentials.cc(115)] Check failed: . : Invalid argument (22)
[14210:14210:1105/104352.780272:FATAL:zygote_host_impl_linux.cc(224)] Check failed: . : No such file or directory (2)
zsh: trace trap  qutebrowser

This issue seems very similar to #55571 but I don’t know if the root cause is the same. On the same system, the latest chromium (chromium-142.0.7444.59_1) works fine.

Steps to reproduce
  1. Install the latest version of qutebrowser (3.5.1_1) on an up-todate musl system
  2. Attempt to start qutebrowser

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing qutebrowser-3.5.1_1 on an up-to-date Void musl system and compare its startup errors with the working chromium package. Investigate the missing Wayland plugin, Widevine loader error, and zygote crash; done means qutebrowser starts successfully on the reported system.

Written by the indexing model from the issue text.

Assessment

Tech stack
linux
Domain
operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
28/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.