Does not see ~/.XCompose

Bug #1877597 reported by Roman Odaisky
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
chromium-browser (Ubuntu)
Invalid
Undecided
Unassigned

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.

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

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

Changed in chromium-browser (Ubuntu):
status: New → Incomplete
Revision history for this message
Olivier Tilloy (osomon) wrote :

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

Revision history for this message
Roman Odaisky (to-roma-from-lp) wrote :

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.

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

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