From: bluej99 <bluej99@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] Chromium seemingly has incomplete dependencies
Date: Thu, 03 Feb 2022 22:34:45 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35387@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1136 bytes --]
New issue by bluej99 on void-packages repository
https://github.com/void-linux/void-packages/issues/35387
Description:
<!-- Don't request update of package. We have a script for that. https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt . However, a quality pull request may help. -->
### System
* xuname:
*Void 5.15.19_1 x86_64*
* package:
*chromium-97.0.4692.99_1*
### Expected behavior
Chromium should contain all of its dependencies and should start with the flag --ozone-platform-hint=auto on a wayland-only machine
### Actual behavior
a trace/breakpoint error
### Steps to reproduce the behavior
install chromium and run it on the command line
### SOLUTION
I tried everything, put my user in all possible groups, updated fontconfigs, etc. The actual solution was to have Electron13 installed on my system. This happened by accident as I happened to install vscode this morning, which depends on Electron13. Now, chromium starts without a hitch on wayland natively. Running xbps-query -x chromium does NOT have Electron as a dependency. I can create a PR if others can confirm this issue.
next reply other threads:[~2022-02-03 21:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-03 21:34 bluej99 [this message]
2022-02-04 4:53 ` abenson
2022-02-04 4:56 ` bluej99
2022-02-04 4:56 ` [ISSUE] [CLOSED] " bluej99
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35387@inbox.vuxu.org \
--to=bluej99@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).