[Desktop-packages] [Bug 1877597] Re: Does not see ~/.XCompose

2020-05-08 Thread Olivier Tilloy
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=” 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 : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1877597] Re: Does not see ~/.XCompose

2020-05-08 Thread Roman Odaisky
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.

-- 
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:
  Incomplete

Bug description:
  Unless I manually edit ~/.chromium-browser.init to include “export
  XCOMPOSEFILE=” 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 : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1877597] Re: Does not see ~/.XCompose

2020-05-08 Thread Olivier Tilloy
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 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:
  Incomplete

Bug description:
  Unless I manually edit ~/.chromium-browser.init to include “export
  XCOMPOSEFILE=” 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 : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1877597] Re: Does not see ~/.XCompose

2020-05-08 Thread Olivier Tilloy
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 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:
  Incomplete

Bug description:
  Unless I manually edit ~/.chromium-browser.init to include “export
  XCOMPOSEFILE=” 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 : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp