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
--
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-t
Note: the x11 interface does #include , which allows
read access to @{HOME}/.XCompose. So this *should* work?
** Changed in: chromium-browser (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ht
Could you please examine the journal (`journalctl | grep DEN`) for
denials related to ~/.XCompose ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1877597
Title:
Does not see ~/.XCompose
To manage n
