New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fcitx stop working at flatpak 1.0.0 #2031

Open
nakamuray opened this Issue Aug 28, 2018 · 4 comments

Comments

Projects
None yet
4 participants
@nakamuray

nakamuray commented Aug 28, 2018

Linux distribution and version

ubuntu 18.04

Flatpak version

1.0.0 (from ppa:alexlarsson/flatpak)

Description of the problem

After upgrading flatpak from 0.99.3 to 1.0.0, I can't input japanese characters on slack app.
While fcitx (mozc) is activated (input method indicator is apeard around cursor), typing keyboard has no effect.
Downgrading to 0.99.3 bring back to expected behavior.

Steps to reproduce

  1. setup fcitx on host side
  2. install slack app from flathub and run it
  3. activate fcitx (mozc) and type something
@alexlarsson

This comment has been minimized.

Show comment
Hide comment
@alexlarsson

alexlarsson Aug 28, 2018

Member

Hmm, this is probably due to a small change in how the dbus proxy works that was made to future proof the portals. In particular, this commit: ef9297a

We used to allow sandboxed apps to receive all broadcasts from portals, but we now limit them to those under the /org/freedesktop/portal object path. I wonder if the fcitx portal was using this? If so, it would need to change the broadcast object paths.

Member

alexlarsson commented Aug 28, 2018

Hmm, this is probably due to a small change in how the dbus proxy works that was made to future proof the portals. In particular, this commit: ef9297a

We used to allow sandboxed apps to receive all broadcasts from portals, but we now limit them to those under the /org/freedesktop/portal object path. I wonder if the fcitx portal was using this? If so, it would need to change the broadcast object paths.

@nakamuray

This comment has been minimized.

Show comment
Hide comment
@nakamuray

nakamuray Aug 29, 2018

I confirmed that at least on flatpak 1.0.0 without ef9297a (rebuild deb package with patch which revert the commit), fcitx works as expected.

nakamuray commented Aug 29, 2018

I confirmed that at least on flatpak 1.0.0 without ef9297a (rebuild deb package with patch which revert the commit), fcitx works as expected.

@alexlarsson

This comment has been minimized.

Show comment
Hide comment
@alexlarsson

alexlarsson Aug 29, 2018

Member

I realize this is a breaking change, but its unfortunately required for security reasons. However, it should be fixable, and If you have patches to fcitx I can apply them in the runtimes.

Member

alexlarsson commented Aug 29, 2018

I realize this is a breaking change, but its unfortunately required for security reasons. However, it should be fixable, and If you have patches to fcitx I can apply them in the runtimes.

@trulyliu

This comment has been minimized.

Show comment
Hide comment
@trulyliu

trulyliu Oct 9, 2018

I am also affected by this issue.
Should we patch fcitx? How?

trulyliu commented Oct 9, 2018

I am also affected by this issue.
Should we patch fcitx? How?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment