** No longer affects: lubuntu-default-settings
--
You received this bug notification because you are a member of AppArmor
Developers, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1928360
Title:
Switch to Fcitx 5 for Chinese
Status in Snappy:
Invalid
Status in
> @handsome_feng: Since Kylin will ship both fcitx 4 and fcitx 5 in 21.10, I'm
> thinking that Kylin
> would be a perfect platform for testing this input configuration. So it would
> be good if you
> could include some testing also of fcitx 5 and be attentive to possible
> issues in light of
** Changed in: snappy
Status: New => Invalid
--
You received this bug notification because you are a member of AppArmor
Developers, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1928360
Title:
Switch to Fcitx 5 for Chinese
Status in Lubuntu default settings:
On 2021-06-08 08:54, James Henstridge wrote:
>> Is there such a snap you could point me to so I can test?
>
> The candidate channel of the gedit snap is built with core20 and the
> gnome-3-38-2004 platform snap. But as I said, I don't think that
> platform snap currently includes the fcitx5
> Is there such a snap you could point me to so I can test?
The candidate channel of the gedit snap is built with core20 and the
gnome-3-38-2004 platform snap. But as I said, I don't think that
platform snap currently includes the fcitx5 input module.
--
You received this bug notification
So it was changed in im-config. In Debian the change was uploaded to
experimental instead of unstable/bullseye for now, since the principal
fcitx package maintainer Shengjing Zhu senses some degree of
uncertainty. He wants to give the users some time to provide feedback
before changing it in
This bug was fixed in the package im-config - 0.47-1
---
im-config (0.47-1) experimental; urgency=medium
* Team upload
* Bug script tweaks
[ Shengjing Zhu ]
* Change IM_MODULE env for fcitx5 to "fcitx" (closes: #977203,
LP: #1928360)
-- Gunnar Hjalmarsson Mon, 07 Jun
On 2021-06-05 06:32, James Henstridge wrote:
> It's probably going to be easiest to see if we can get things
> working with a core20 based platform snap though, since we have
> fcitx5 packages there (albeit for a git prerelease version).
Is there such a snap you could point me to so I can test?
I hadn't realised that they renamed the IM module with the version bump:
that means snaps built against older platforms won't load the old (but
working) Fcitx 4 module when run on a host system configured with Fcitx
5.
We can certainly look at adding the new IM module to the platform snaps,
but
On Sat, Jun 05, 2021 at 01:27:19AM -, Gunnar Hjalmarsson wrote:
> It means that it explicitly looks for the fcitx 5 gtk im module, while
> Chromium only has access to the fcitx 4 one.
Oh! Excellent debugging to find the root cause.
Thanks
signature.asc
Description: PGP signature
--
I presented the snap problem for James Henstridge, and he gave me a very
useful hint: The Chromium snap makes use of the bionic library stack
(the gnome-3-28-1804 snap) including the im module installed by fcitx-
frontend-gtk3, i.e. the fcitx 4 gtk im module.
That made me think of
Gunnar, indeed, it had much less in it than I expected; I don't know
much about the snap packaging for Chromium, but it looked to me like it
was trying to do bluetooth things and that's all that was denied.
I'm no fcitx expert but I didn't think it looked related.
Thanks
--
You received this
@Seth: I suppose that the DENIED file I attached in comment #7 does not
help much.
Fcitx 5 is a separate process, i.e. /usr/bin/fcitx5 as opposed to
/usr/bin/fcitx. When in Chromium it behaves as if fcitx5 does not exist,
even if the process runs and I can use fcitx5 in other applications. I
This bug was fixed in the package language-selector - 0.212
---
language-selector (0.212) impish; urgency=medium
* data/pkg_depends:
- Don't pull Fcitx for non-Chinese languages. This is consistent
with the IM_CONFIG_PREFERRED_RULE variable in
Thanks handsome_feng!
The Kylin discussion makes me confident that it's fine for Lubuntu as
well. The Lubuntu situation is different, though, since im-config is
disabled by default unless a Chinese locale is in effect. This discourse
topic comes to mind:
> Does this mean that the proposed changes to pkg_depends is fine from
> an Ubuntu Kylin POV, and that no further changes are needed?
Yes, Thanks!
--
You received this bug notification because you are a member of AppArmor
Developers, which is subscribed to the bug report.
On 2021-05-20 15:39, handsome_feng wrote:
> With the fcitx items in the current seed, I think pkg_depends don't
> need to pull in the fcitx 4 packages for Ubuntu Kylin 21.10,
Ok, good.
> also it's okay to pull in the fcitx 5 packages, since the im-config
> will set the default input method to
Hi,
With the fcitx items in the current seed, I think pkg_depends don't need
to pull in the fcitx 4 packages for Ubuntu Kylin 21.10, also it's okay
to pull in the fcitx 5 packages, since the im-config will set the
default input method to fcitx 4 for Ubuntu Kylin 21.10?
--
You received this bug
@handsome_feng: Great! I have a follow-up question then:
In the desktop seed of Ubuntu Kylin I see these packages:
* (im-config)
* (fcitx)
* (fcitx-frontend-gtk2)
* (fcitx-frontend-gtk3)
* (fcitx-frontend-qt5)
* (fcitx-ui-classic)
* (fcitx-table)
* (fcitx-module-cloudpinyin)
*
> Would that plan make sense to you?
This is a good way for us, we agree with it, thanks a lot!
--
You received this bug notification because you are a member of AppArmor
Developers, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1928360
Title:
Switch to Fcitx 5 for
@handsome_feng: I suppose it is possible. Of course it would have been
desirable to do it in 21.10 to get more time to identify possible issues
before next LTS, but OTOH I know that Sogou is considered important on
Kylin.
Thinking... Maybe we can have it both ways. :) What I mean is that we
could
Hi, Gunnar,
After talking to our partners such as Sogou, they want to postpone this
migration until 22.04 so that they have enough time to work on the
adaptation, is this possible?
Thanks,
handsome_feng
--
You received this bug notification because you are a member of AppArmor
Developers,
** Changed in: ubuntukylin
Status: New => In Progress
--
You received this bug notification because you are a member of AppArmor
Developers, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1928360
Title:
Switch to Fcitx 5 for Chinese
Status in Lubuntu default
Sure, Seth, attached please find the output from
cat /var/log/audit/audit.log | grep DENIED
** Attachment added: "apparmor_denied-lines_chromium.txt"
https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/1928360/+attachment/5498578/+files/apparmor_denied-lines_chromium.txt
--
On Tue, May 18, 2021 at 07:39:48PM -, Gunnar Hjalmarsson wrote:
> On 2021-05-16 22:23, Gunnar Hjalmarsson wrote:
> > As regards apparmor it's possible that no change is needed.
>
> Well, I simply tested with the Chromium snap. fcitx5 does not work in
> Chromium, while fcitx4 does. So
On 2021-05-16 22:23, Gunnar Hjalmarsson wrote:
> As regards apparmor it's possible that no change is needed.
Well, I simply tested with the Chromium snap. fcitx5 does not work in
Chromium, while fcitx4 does. So something needs to be done.
--
You received this bug notification because you are a
26 matches
Mail list logo