Github messages for voidlinux
 help / color / mirror / Atom feed
* [ISSUE] Chromium seemingly has incomplete dependencies
@ 2022-02-03 21:34 bluej99
  2022-02-04  4:53 ` abenson
                   ` (2 more replies)
  0 siblings, 3 replies; 4+ messages in thread
From: bluej99 @ 2022-02-03 21:34 UTC (permalink / raw)
  To: ml

[-- 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.


^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2022-02-04  4:56 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-02-03 21:34 [ISSUE] Chromium seemingly has incomplete dependencies bluej99
2022-02-04  4:53 ` abenson
2022-02-04  4:56 ` [ISSUE] [CLOSED] " bluej99
2022-02-04  4:56 ` bluej99

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).