Right, so this is working "as intended". Even though, as you point out,
the line between what should be readable in a user's home directory and
what shouldn't is a fine one. But that's not a chromium-specific issue.
** Changed in: chromium-browser (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1877597
Title:
Does not see ~/.XCompose
Status in chromium-browser package in Ubuntu:
Invalid
Bug description:
Unless I manually edit ~/.chromium-browser.init to include “export
XCOMPOSEFILE=<path where no component starts with a dot>” and take
care to put a copy of XCompose at such a path, Chromium does not see
the XCompose file and so can’t make use of user-defined Compose
sequences.
Chromium needs to be able to see ~/.XCompose, possibly other X11 files
of similar nature.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1877597/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
