chromium-browser snap for armv7 does not read from .config/chromium-flags.conf
Bug #1984132 reported by
Da Xue
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
chromium-browser (Ubuntu) |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
Running Ubuntu 22.04 LTS and the chromium-browser snap on ARMv7 version 104.0.5112.79.
Added --ozone-
Start the chromium browser and it expects X11 components.
Manually starting chromium-browser with --ozone-
On ARMv8/arm64 this works fine.
To post a comment you must log in.
The file ~/.config/ chromium- flags.conf isn't read by the snap, so this won't work on any architecture.
However you can use ~/.chromium- browser. init for that purpose (that's for compatibility with the old deb package).