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

Bug Description

Running Ubuntu 22.04 LTS and the chromium-browser snap on ARMv7 version 104.0.5112.79.

Added --ozone-platform-hint=auto to .config/chromium-flags.conf

Start the chromium browser and it expects X11 components.

Manually starting chromium-browser with --ozone-platform=wayland works.

On ARMv8/arm64 this works fine.

Tags: wayland
Revision history for this message
Olivier Tilloy (osomon) wrote :

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

Changed in chromium-browser (Ubuntu):
status: New → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.