[Bug 2233527] New: unset GTK_IM_MODULE and QT_IM_MODULE for Plasma
Wayland
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2233527
Bug ID: 2233527
Summary: unset GTK_IM_MODULE and QT_IM_MODULE for Plasma
Wayland
Product: Fedora
Version: 39
OS: Linux
Status: NEW
Component: ibus
Keywords: i18n
Severity: medium
Assignee: tfujiwar(a)redhat.com
Reporter: tagoh(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: extras-qa(a)fedoraproject.org,
i18n-bugs(a)lists.fedoraproject.org, ngompa13(a)gmail.com,
petersen(a)redhat.com, shawn.p.huang(a)gmail.com,
tagoh(a)redhat.com, tfujiwar(a)redhat.com
Depends On: 2232064
Target Milestone: ---
Classification: Fedora
To fill the last piece of the change to accomplish this, we need to add:
IMSETTINGS_IGNORE_SESSION=KDE-wayland
to ibus.conf.
+++ This bug was initially created as a clone of Bug #2232064 +++
With ibus-1.5.29 in Fedora 29, QT_IM_MODULE and GTK_IM_MODULE should no longer
be set for KDE Plasma Wayland.
Can you make such a change to imsettings, please?
Without that the behavior of ibus in Plasma Wayland is really bad.
(This change should not be made for Plasma X11.)
Reproducible: Always
Steps to Reproduce:
1. env | grep MODULE
Actual Results:
GTK_IM_MODULE=ibus
QT_IM_MODULE=ibus
Expected Results:
GTK_IM_MODULE and QT_IM_MODULE to be unset in Plasma Wayland
Related to https://fedoraproject.org/wiki/Changes/IBus_1.5.29
--- Additional comment from Akira TAGOH on 2023-08-15 07:44:31 UTC ---
Do we still need it for X11, right?
--- Additional comment from fujiwara on 2023-08-15 08:18:00 UTC ---
(In reply to Akira TAGOH from comment #1)
> Do we still need it for X11, right?
Yes, we do.
--- Additional comment from Akira TAGOH on 2023-08-17 14:01:21 UTC ---
One more question. This report requests to unset GTK_IM_MODULE too. does IBus
1.5.29 work without GSettings and GTK_IM_MODULE on Plasma-wayland?
--- Additional comment from fujiwara on 2023-08-18 02:20:19 UTC ---
(In reply to Akira TAGOH from comment #3)
> One more question. This report requests to unset GTK_IM_MODULE too. does
> IBus 1.5.29 work without GSettings and GTK_IM_MODULE on Plasma-wayland?
Yes, it does. Those environment variables need to be unset.
--- Additional comment from Jens Petersen on 2023-08-21 16:04:15 UTC ---
Seems imsettings-plasma was dropped from @input-methods:
https://pagure.io/fedora-comps/c/7553747fb0e4c1c6b97935dde1443e27de5fa3da...
https://pagure.io/fedora-comps/c/98e56a9cf0425b76e9a0e8237113d87ad0b4cafa...
So we may need to retest but this could this affect Plasma X11 aversely?
--- Additional comment from Neal Gompa on 2023-08-21 18:16:21 UTC ---
The way this gets set needs to be changed then to only activate when a Plasma
X11 session is used. It currently does it unconditionally.
--- Additional comment from Akira TAGOH on 2023-08-22 02:33:54 UTC ---
I'm going to update imsettings for this.
--- Additional comment from Fedora Update System on 2023-08-22 12:16:41 UTC ---
FEDORA-2023-adec06104c has been submitted as an update to Fedora 40.
https://bodhi.fedoraproject.org/updates/FEDORA-2023-adec06104c
--- Additional comment from Fedora Update System on 2023-08-22 12:19:15 UTC ---
FEDORA-2023-adec06104c has been pushed to the Fedora 40 stable repository.
If problem still persists, please make note of it in this bug report.
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=2232064
[Bug 2232064] unset GTK_IM_MODULE and QT_IM_MODULE for Plasma Wayland
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2233527
Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-...
6 months, 4 weeks
[Bug 2241232] New: missing font file ukai.ttc
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2241232
Bug ID: 2241232
Summary: missing font file ukai.ttc
Product: Fedora
Version: 39
Hardware: x86_64
OS: Linux
Status: NEW
Component: cjkuni-ukai-fonts
Keywords: Desktop
Severity: medium
Assignee: pwu(a)redhat.com
Reporter: dunchee81(a)gmail.com
QA Contact: extras-qa(a)fedoraproject.org
CC: i18n-bugs(a)lists.fedoraproject.org,
petersen(a)redhat.com, pwu(a)redhat.com
Target Milestone: ---
Classification: Fedora
Font file ukai.ttc is missing in package:
cjkuni-ukai-fonts-0.2.20080216.2-2.fc39.noarch
Reproducible: Always
Steps to Reproduce:
1. A Fedora 39 Workstation & update to latest
2. sudo dnf install cjkuni-ukai-fonts
3. Open up build-in Fonts app
Actual Results:
cjkuni-ukai fonts(shown as "AR PL UKai CN", "AR PL UKai HK", "AR PL UKai TW",
"AR PL UKai TW MBE") not found in build-in Fonts app.
Expected Results:
Those fonts should be present.
font file ukai.ttc is present in
cjkuni-ukai-fonts-0.2.20080216.1-68.fc39.noarch.rpm
Same missing fonts problem with Bug 2241231
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2241232
Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-...
7 months
[Bug 2241231] New: missing font file
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2241231
Bug ID: 2241231
Summary: missing font file
Product: Fedora
Version: 39
Hardware: x86_64
OS: Linux
Status: NEW
Component: cjkuni-uming-fonts
Keywords: Desktop
Severity: medium
Assignee: pwu(a)redhat.com
Reporter: dunchee81(a)gmail.com
QA Contact: extras-qa(a)fedoraproject.org
CC: i18n-bugs(a)lists.fedoraproject.org,
petersen(a)redhat.com, pwu(a)redhat.com
Target Milestone: ---
Classification: Fedora
Font file uming.ttc is missing in the package:
cjkuni-uming-fonts-0.2.20080216.2-2.fc39.noarch
Reproducible: Always
Steps to Reproduce:
1. A Fedora 39 Workstation & update to latest
2. sudo dnf install cjkuni-uming-fonts
3. Open up build-in Fonts app.
Actual Results:
cjkuni-uming fonts(shown as "AR PL UMing CN,Light", "AR PL UMing HK, Light",
"AR PL UMing TW,Light", "AR PL UMing TW MBE,Light") not found in build-in Fonts
app.
Expected Results:
Those fonts should be present.
font file uming.ttc is present in
cjkuni-uming-fonts-0.2.20080216.1-71.fc39.noarch.rpm
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2241231
Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-...
7 months
[Bug 2230471] New: [Lenovo] GB 18030-2022 compliant Chinese font
needed for OS preloads in China
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2230471
Bug ID: 2230471
Summary: [Lenovo] GB 18030-2022 compliant Chinese font needed
for OS preloads in China
Product: Fedora
Version: 38
Hardware: x86_64
OS: Linux
Status: NEW
Component: Fonts
Assignee: i18n-bugs(a)lists.fedoraproject.org
Reporter: mpearson(a)lenovo.com
QA Contact: fonts-bugs(a)lists.fedoraproject.org
Target Milestone: ---
Classification: Fedora
Description of problem:
The Chinese government have made it a requirement that OS vendors support GB
18030-2022. To my understanding this means that the preloaded OS needs to have
a font that supports this spec and if we don't have that we won't be able to
ship the Fedora OS in China.
I believe Fedora has the google-noto-cjk-fonts package and it looks like they
are working on having compliance for this specification (based on
https://github.com/notofonts/noto-cjk/issues/252)
The font is not part of the default install so I wanted to open the
conversation as to whether it can be included in the default workstation
include please.
If there is another font that is compliant available that I've missed let me
know - this isn't a world I know well (despite, bizarrely, the very first job I
ever had was making it so vector fonts could be rasterised for display :))
Version-Release number of selected component (if applicable): N/A
How reproducible: 100%
Steps to Reproduce: N/A
1.
2.
3.
Actual results: no compliant Chinese font available
Expected results:Compliant Chinese font available
Additional info:Let me know if there is anything we can help with directly
here. Our team in China can help :)
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2230471
Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-...
7 months, 2 weeks
[Bug 2240167] New: Need to press Super+space twice to
activate/deactivate on Cinnamon desktop
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2240167
Bug ID: 2240167
Summary: Need to press Super+space twice to activate/deactivate
on Cinnamon desktop
Product: Fedora
Version: 39
OS: Linux
Status: NEW
Component: ibus
Keywords: i18n
Severity: medium
Assignee: tfujiwar(a)redhat.com
Reporter: tagoh(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: i18n-bugs(a)lists.fedoraproject.org,
shawn.p.huang(a)gmail.com, tfujiwar(a)redhat.com
Target Milestone: ---
Classification: Fedora
Summary says it all. The first Super+space just inserts a space and no input
engine selector popped up. Super key needs to keep pressed though, the 2nd
Super+space pops up the selector as expected.
Reproducible: Always
Steps to Reproduce:
1.Install from Fedora-Cinnamon-Live-x86_64-39-20230920.n.0.iso with ja
2.Boot and open gnome-terminal and/or xed
3.Press Super and space
4.Release space key only and press space key again
Actual Results:
space character are inserted at 3, and the selector popped up at 4
Expected Results:
the selector should be popped up at 3 without inserting space
$ rpm -qa | grep -e ^ibus
ibus-libs-1.5.29~rc1-3.fc39.x86_64
ibus-gtk3-1.5.29~rc1-3.fc39.x86_64
ibus-gtk2-1.5.29~rc1-3.fc39.x86_64
ibus-setup-1.5.29~rc1-3.fc39.noarch
ibus-1.5.29~rc1-3.fc39.x86_64
ibus-panel-1.5.29~rc1-3.fc39.x86_64
ibus-anthy-python-1.5.15-2.fc39.noarch
ibus-anthy-1.5.15-2.fc39.x86_64
ibus-hangul-1.5.5-3.fc39.x86_64
ibus-libpinyin-1.15.4-1.fc39.x86_64
ibus-libzhuyin-1.10.2-4.fc39.x86_64
ibus-m17n-1.4.22-1.fc39.x86_64
ibus-typing-booster-2.24.1-1.fc39.noarch
ibus-gtk4-1.5.29~rc1-3.fc39.x86_64
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2240167
Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-...
7 months, 3 weeks
[Bug 2243053] New: Can't switch to Mozc to input Japanese characters
with fcitx5-mozc
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2243053
Bug ID: 2243053
Summary: Can't switch to Mozc to input Japanese characters with
fcitx5-mozc
Product: Fedora
Version: 38
Hardware: x86_64
OS: Linux
Status: NEW
Component: fcitx-qt5
Keywords: Desktop, i18n
Severity: medium
Assignee: yanqiyu01(a)gmail.com
Reporter: james(a)jamesnorth.net
QA Contact: extras-qa(a)fedoraproject.org
CC: i18n-bugs(a)lists.fedoraproject.org,
robinlee.sysu(a)gmail.com, yanqiyu01(a)gmail.com
Target Milestone: ---
Classification: Fedora
I'm trying to input Japanese characters with fcitx5-mozc on KDE Wayland, Fedora
38. I have this set in `/etc/profile.d/fcitx`:
```
QT_IM_MODULE=fcitx && export QT_IM_MODULE
GTK_IM_MODULE=fcitx && export GTK_IM_MODULE
XMODIFIERS=@im=fcitx && export XMODIFIERS
```
`fcitx5-diagnose` tells me the environment variables are set correctly. I can
confirm that myself when running `env` in a terminal.
I see two options (US and Mozc), but neither of the radio buttons is selected.
After I click Mozc, the radio button is still unselected and I can't input
Japanese characters.
I've tried inputting characters on Firefox, Alacritty, and Kwrite.
Reproducible: Always
Steps to Reproduce:
1. Install fcitx5-mozc
2. Add the environment variables
3. Reboot
4. Run fcitx5
5. Open configuration and add Mozc to the input method list
6. Try to switch to the Mozc IME to type Japanese
Actual Results:
I can't switch to Mozc and when I type, I only get US letters.
Expected Results:
I can type in 日本語.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2243053
Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-...
7 months, 3 weeks