https://bugzilla.redhat.com/show_bug.cgi?id=2164891
Bug ID: 2164891
Summary: librime-1.8.3 is available
Product: Fedora
Version: rawhide
Status: NEW
Component: librime
Keywords: FutureFeature, Triaged
Assignee: pwu(a)redhat.com
Reporter: upstream-release-monitoring(a)fedoraproject.org
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
Releases retrieved: 1.8.0, 1.8.1, 1.8.2, 1.8.3
Upstream release that is considered latest: 1.8.3
Current version/release in rawhide: 1.7.3-6.fc38
URL: https://rime.im/
Please consult the package updates policy before you issue an update to a
stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/
More information about the service that created this bug can be found at:
https://docs.fedoraproject.org/en-US/package-maintainers/Upstream_Release_M…
Please keep in mind that with any upstream change, there may also be packaging
changes that need to be made. Specifically, please remember that it is your
responsibility to review the new version to ensure that the licensing is still
correct and that no non-free or legally problematic items have been added
upstream.
Based on the information from Anitya:
https://release-monitoring.org/project/228902/
To change the monitoring settings for the project, please visit:
https://src.fedoraproject.org/rpms/librime
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2164891
https://bugzilla.redhat.com/show_bug.cgi?id=2131673
Bug ID: 2131673
Summary: Default GTK_IM_MODULE should be ibus in GNOME Xorg
Product: Fedora
Version: 37
Status: NEW
Whiteboard: AcceptedFreezeException
Component: imsettings
Assignee: tagoh(a)redhat.com
Reporter: tfujiwar(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: awilliam(a)redhat.com, bcotton(a)redhat.com,
extras-qa(a)fedoraproject.org, fmuellner(a)redhat.com,
gnome-sig(a)lists.fedoraproject.org,
i18n-bugs(a)lists.fedoraproject.org, klember(a)redhat.com,
mkasik(a)redhat.com, ofourdan(a)redhat.com,
robatino(a)fedoraproject.org, rstrode(a)redhat.com,
tagoh(a)redhat.com, tiagomatos(a)gmail.com,
yaneti(a)declera.com
Depends On: 2128423
Blocks: 2009539 (F37FinalBlocker,FinalBlocker), 2009540
(F37FinalFreezeException,FinalFreezeException)
Target Milestone: ---
Classification: Fedora
+++ This bug was initially created as a clone of Bug #2128423 +++
Now GNOME Xorg sets GTK_IM_MODULE to "ibus" in some Asian locales using
/etc/X11/xinit/xinitrc.d/50-xinput.sh but "gtk-im-context-simple" in other
locales.
But previously GNOME Xorg sets GTK_IM_MODULE to "ibus" in all locales.
Probably a GNOME desktop module always can set the default GTK_IM_MODULE in
GNOME Xorg.
To reproduce:
1. Log into GNOME Xorg in en_US.UTF-8 locale
2. Run `ibus im-module`
"gtk-im-context-simple" is output.
Expected result:
"ibus" is output.
Note: GTK_IM_MODULE="wayland" in GNOME Wayland by default now
--- Additional comment from Jens Petersen on 2022-09-29 03:27:49 UTC ---
This means in particular that if you try to add a first input method in
gnome-control-center
you need to restart gnome in order for it to work properly, which is not a
great experience
(unlike in Wayland where the input method just works immediately).
Strictly speaking this regression started actually in F36 (Gnome 42) I believe.
But we feel it is actually a potential blocker bug.
Though this is not resolved yet upstream.
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=2009539
[Bug 2009539] Fedora 37 Final blocker bug tracker
https://bugzilla.redhat.com/show_bug.cgi?id=2009540
[Bug 2009540] Fedora 37 Final freeze exception bug tracker
https://bugzilla.redhat.com/show_bug.cgi?id=2128423
[Bug 2128423] Default GTK_IM_MODULE should be ibus in GNOME Xorg
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2131673
https://bugzilla.redhat.com/show_bug.cgi?id=2156939
Fedora Update System <updates(a)fedoraproject.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ON_QA |CLOSED
Resolution|--- |ERRATA
Last Closed| |2023-01-21 04:08:17
--- Comment #3 from Fedora Update System <updates(a)fedoraproject.org> ---
FEDORA-EPEL-2023-f5cc5c23ae has been pushed to the Fedora EPEL 9 stable
repository.
If problem still persists, please make note of it in this bug report.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2156939
https://bugzilla.redhat.com/show_bug.cgi?id=2158787
Bug ID: 2158787
Summary: mozc.el: Emacs compiler warnings about undefined
functions ‘first’ and ‘third’
Product: Fedora
Version: 37
Hardware: x86_64
OS: Linux
Status: NEW
Component: mozc
Severity: low
Assignee: tagoh(a)redhat.com
Reporter: edgar.hoch(a)ims.uni-stuttgart.de
QA Contact: extras-qa(a)fedoraproject.org
CC: i18n-bugs(a)lists.fedoraproject.org,
robinlee.sysu(a)gmail.com, tagoh(a)redhat.com,
tfujiwar(a)redhat.com
Target Milestone: ---
Classification: Fedora
Description of problem:
When I start emacs 28.2 on Fedora 37 the first time, I get the following
warning:
Warning (comp): mozc.el:664:22: Warning: the function ‘first’ is not known to
be defined.
Warning (comp): mozc.el:664:9: Warning: the function ‘third’ is not known to be
defined.
Version-Release number of selected component (if applicable):
mozc-2.28.4950.102-1.fc37.x86_64
emacs-28.2-1.fc37.x86_64
How reproducible:
Always.
But note: Warnings are only displayed on the first start of a new emacs
version.
Steps to Reproduce:
1. Install packages mozc-2.28.4950.102-1.fc37.x86_64 emacs-28.2-1.fc37.x86_64
2. Remove emacs cache files in ~/.emacs.d/eln-cache/28.2-*
rm -rf ~/.emacs.d/eln-cache/28.2-*
3. Start emacs.
4. Check the emacs buffer "*Warnings*".
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2158787
https://bugzilla.redhat.com/show_bug.cgi?id=2155094
Bug ID: 2155094
Summary: mozc.el: Emacs compiler warnings about obsolete
function
Product: Fedora
Version: 37
Hardware: x86_64
OS: Linux
Status: NEW
Component: mozc
Severity: low
Assignee: tagoh(a)redhat.com
Reporter: edgar.hoch(a)ims.uni-stuttgart.de
QA Contact: extras-qa(a)fedoraproject.org
CC: i18n-bugs(a)lists.fedoraproject.org,
robinlee.sysu(a)gmail.com, tagoh(a)redhat.com,
tfujiwar(a)redhat.com
Target Milestone: ---
Classification: Fedora
Description of problem:
When I start Emacs on Fedora 37 for the first time, I got the following
compiler warning:
Warning (comp): mozc.el:429:21: Warning: ‘case’ is an obsolete alias (as of
27.1); use ‘cl-case’ instead. Disable showing Disable logging
Warning (comp): mozc.el:825:61: Warning: ‘case’ is an obsolete alias (as of
27.1); use ‘cl-case’ instead. Disable showing Disable logging
Warning (comp): mozc.el:1256:18: Warning: ‘incf’ is an obsolete alias (as of
27.1); use ‘cl-incf’ instead. Disable showing Disable logging
Warning (comp): mozc.el:1642:18: Warning: ‘case’ is an obsolete alias (as of
27.1); use ‘cl-case’ instead. Disable showing Disable logging
Version-Release number of selected component (if applicable):
emacs-28.1-3.fc37.x86_64
emacs-color-theme-el-6.6.0-23.fc37.noarch
How reproducible:
First start of Emacs on Fedora 37.
Steps to Reproduce:
1. Check in ~/.emacs.d/eln-cache/ exists. Delete (or rename) it
to simulate a fresh, first start of Emacs on this Fedora version.
2. Start Emacs
3. Read the buffer *Warnings*
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2155094
https://bugzilla.redhat.com/show_bug.cgi?id=2160957
Bug ID: 2160957
Summary: rpm -Va reports error on /var/cache/ibus/bus/registry
Product: Fedora
Version: rawhide
Hardware: x86_64
OS: Linux
Status: NEW
Component: ibus
Severity: low
Assignee: tfujiwar(a)redhat.com
Reporter: pampelmuse(a)gmx.at
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
Description of problem:
"rpm -Va" reports error on mode for /var/cache/ibus/bus/registry
Version-Release number of selected component (if applicable):
ibus-1.5.27-11.fc38.x86_64
How reproducible:
Always
Steps to Reproduce:
1. Make a fresh installation
2. run "rpm -Va"
Actual results:
.M....... g /var/cache/ibus/bus/registry
Expected results:
No output
Additional info:
Maybe the spec-file "ibus.spec" line 480 should contain:
Instead of:
%ghost %pkgcache/bus/registry
maybe better:
%ghost %verify(not mode) %pkgcache/bus/registry
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2160957
https://bugzilla.redhat.com/show_bug.cgi?id=2158951
Bug ID: 2158951
Summary: update ddskk to 17.1 from github
Product: Fedora
Version: rawhide
Status: NEW
Component: emacs-common-ddskk
Assignee: dueno(a)redhat.com
Reporter: petersen(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: dueno(a)redhat.com, i18n-bugs(a)lists.fedoraproject.org
Target Milestone: ---
Classification: Fedora
ddskk development seems to have moved to https://github.com/skk-dev/ddskk
It would be good to update to a new release
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2158951
https://bugzilla.redhat.com/show_bug.cgi?id=2125153
Bug ID: 2125153
Summary: ibus does not support special Arabic compose sequences
Product: Fedora
Version: 36
Status: NEW
Component: ibus
Assignee: tfujiwar(a)redhat.com
Reporter: mfabian(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
The following compose sequences do not work in ibus:
$ grep -i arabic.*ligature /usr/share/X11/locale/en_US.UTF-8/Compose
# Arabic Lam-Alef ligatures
<UFEFB> : "لا" # ARABIC LIGATURE LAM WITH ALEF
<UFEF7> : "لأ" # ARABIC LIGATURE LAM WITH ALEF WITH HAMZA ABOVE
<UFEF9> : "لإ" # ARABIC LIGATURE LAM WITH ALEF WITH HAMZA BELOW
<UFEF5> : "لآ" # ARABIC LIGATURE LAM WITH ALEF WITH MADDA ABOVE
They are needed because the Arabic keyboard layout outputs UFEFB on some key:
$ grep -i fefb /usr/share/X11/xkb/symbols/ara
key <AB05> { [ UFEFB, UFEF5,
NoSymbol, NoSymbol ]}; // ﻻ ﻵ
key <AB05> { [ UFEFB, UFEF5,
U06AB, U06AD ]}; // ﻻ ﻵ ګ ڭ
but the UFEFB characters is not what is desired, what one really wants is
U+0644 U+0627. But xkb keyboard layouts can only output one keysym when typing
a key, not two. So compose was used as a hack to work around this limitation of
xkb:
The keyboard produces UFEFB and then the compose support replaces this with
U+0644 U+0627.
This works when the compose support in Xorg is used but not when the compose
support in ibus is used.
How to reproduce:
1) First show that it works when using the Xorg compose support:
Start xterm like this (to disable ibus and use the Xorg compose support):
env XMODIFIERS=@im=none xterm &
Then in the xterm, type
$ echo -n b | iconv -f utf8 -t utf16le | od -x
0000000 0062
0000002
and we see that the b produces U+0062, which is correct.
Switch to the Arabic keyboard
setxkbmap ara
type “arrow up” to get the echo -n b | iconv -f utf8 -t utf16le | od -x line
back, go back to the b with “arrow left”, type b and now one gets:
echo -n لا | iconv -f utf8 -t utf16le | od -x
0000000 0644 0627
0000004
I.e. even though the keyboard surely outputs only U+FEFB, the Compose support
of Xorg transforms this into U+0644 U+0627
2) Now repeat the same test using the compose support in ibus:
Start xterm like this to use the ibus compose support:
env XMODIFIERS=@im=ibus xterm &
Then in the xterm, type
$ echo -n b | iconv -f utf8 -t utf16le | od -x
0000000 0062
0000002
and we see that the b produces U+0062, which is correct.
Switch to the Arabic keyboard
setxkbmap ara
type “arrow up” to get the echo -n b | iconv -f utf8 -t utf16le | od -x line
back, go back to the b with “arrow left”, type b and now one gets:
echo -n ﻻ | iconv -f utf8 -t utf16le | od -x
0000000 fefb
0000002
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2125153