Does not see ~/.XCompose

[Roman Odaisky]

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.

[Olivier Tilloy (osomon)]

Note: the x11 interface does #include <abstractions/X>, which allows read access to @{HOME}/.XCompose. So this *should* work?

[Olivier Tilloy (osomon)]

Could you please examine the journal (`journalctl | grep DEN`) for denials related to ~/.XCompose ?

[Roman Odaisky (to-roma-from-lp)]

Ah, I think the true source of the problem was that my .XCompose was a symlink into a subdirectory of .config, so that’s what was actually denied. This is at least understandable, even if it still makes no sense (~/.config/my-dotfiles-git-repository is off limits but ~/Documents/financial-report-top-secret.pdf is not).

Sorry for the misleading bug description.

[Olivier Tilloy (osomon)]

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.