[Bug 2045414] New: gettext: FTBFS in Fedora rawhide/f36
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2045414
Bug ID: 2045414
Summary: gettext: FTBFS in Fedora rawhide/f36
Product: Fedora
Version: rawhide
Status: NEW
Component: gettext
Assignee: suanand(a)redhat.com
Reporter: releng(a)fedoraproject.org
QA Contact: extras-qa(a)fedoraproject.org
CC: dueno(a)redhat.com, i18n-bugs(a)lists.fedoraproject.org,
jjanco(a)redhat.com, nphilipp(a)redhat.com,
petersen(a)redhat.com, praiskup(a)redhat.com,
suanand(a)redhat.com
Blocks: 1992484 (F36FTBFS)
Target Milestone: ---
Classification: Fedora
gettext failed to build from source in Fedora rawhide/f36
https://koji.fedoraproject.org/koji/taskinfo?taskID=81771851
For details on the mass rebuild see:
https://fedoraproject.org/wiki/Fedora_36_Mass_Rebuild
Please fix gettext at your earliest convenience and set the bug's status to
ASSIGNED when you start fixing it. If the bug remains in NEW state for 8 weeks,
gettext will be orphaned. Before branching of Fedora 37,
gettext will be retired, if it still fails to build.
For more details on the FTBFS policy, please visit:
https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fai...
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1992484
[Bug 1992484] Fedora 36 FTBFS Tracker
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2045414
1 week, 3 days
[Bug 2013323] New: Cursor position and conversion regioni of
ibus-anthy are invisible in Google Documents (both in firefox and
google-chrome)
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2013323
Bug ID: 2013323
Summary: Cursor position and conversion regioni of ibus-anthy
are invisible in Google Documents (both in firefox and
google-chrome)
Product: Fedora
Version: 34
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
Created attachment 1832255
--> https://bugzilla.redhat.com/attachment.cgi?id=1832255&action=edit
Video showing the wrongly displayed cursor position using ibus-anthy in Google
Documents
I did choose component ibus, although this is likely not an ibus bug but a
problem in google docs, but I wanted to report it somehow, maybe something can
be done to improve this:
Fedora-Workstation-Live-x86_64-35-20210829.n.0.iso installed in qemu-kvm with
all current updates.
firefox-93.0-2.fc35.x86_64
google-chrome-unstable-96.0.4662.6-1.x86_64
ibus-1.5.25-4.fc35.x86_64
ibus-anthy-1.5.13-1.fc35.x86_64
See the attached video.
In the video I type わたしのなまえはやまだです first in gedit to show how it should work.
After typing that hiragana, I type space to start conversion. The current
conversion region is indicated by the cursor position and a purple background
color. When the conversion to kanji is startet, at first the cursor position is
at the left of the preedit and the conversion region is わたしの. I can then move
the conversion region right with arrow-right and see that it moves because the
blue background and the cursor position moves.
Then I do the same in Google Documents (both in firefox and google-chrome, that
makes no difference):
- The cursor position is *always* shown at the right end of the preedit
- The purple background color of the conversion region is not there
One can move the conversion region around using the arrow keys, one just cannot
see where the conversion region currently is the purple background is missing
*and* the cursor position is *always* at the right end of the preedit.
The same problem happens when trying to use ibus-typing-booster with the
"inline completion" option in Google Documents. The color of the inline
completion is missing *and* the cursor position is always at the end of the
preedit, so one cannot see where the inline completion is and whether it has
been accepted or not.
In gedit in wayland, the colors don't work either, but at least the cursor
position is shown correctly. When only the cursor position is shown but no
color, it is not great at least somewhat usable. By carefully watching the
cursor one can still see what is going on. But when the cursor positon is
always at the right of preedit *and* there is no colour, this is completely
unusable.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2013323
2 weeks, 3 days
[Bug 2000380] New: [abrt] ibus: init_randr15.constprop.0(): ibus-x11
killed by SIGSEGV
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2000380
Bug ID: 2000380
Summary: [abrt] ibus: init_randr15.constprop.0(): ibus-x11
killed by SIGSEGV
Product: Fedora
Version: 34
Hardware: x86_64
Status: NEW
Whiteboard: abrt_hash:cd9845839762852ab4ef135377f2883b2d552150;VAR
IANT_ID=silverblue;
Component: ibus
Assignee: tfujiwar(a)redhat.com
Reporter: kxra(a)riseup.net
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
Version-Release number of selected component:
ibus-1.5.24-5.fc34
Additional info:
reporter: libreport-2.15.2
backtrace_rating: 4
cmdline: /usr/libexec/ibus-x11 --kill-daemon
crash_function: init_randr15.constprop.0
executable: /usr/libexec/ibus-x11
journald_cursor:
s=89baa82578634853a63ba62a62d92d6a;i=7640;b=80222bf928dc4844a5e32ad2c394174e;m=2f77a5dc83;t=5caa59828b956;x=2279ae7371a2632b
kernel: 5.13.12-200.fc34.x86_64
rootdir: /
runlevel: N 5
type: CCpp
uid: 1000
Truncated backtrace:
Thread no. 1 (10 frames)
#0 init_randr15.constprop.0 at x11/gdkscreen-x11.c:577
#1 init_multihead at x11/gdkscreen-x11.c:1020
#2 process_monitors_change at x11/gdkscreen-x11.c:1174
#3 _gdk_x11_screen_size_changed at x11/gdkscreen-x11.c:1213
#4 gdk_x11_display_translate_event at x11/gdkdisplay-x11.c:1201
#5 _gdk_x11_event_translator_translate at x11/gdkeventtranslator.c:51
#6 gdk_event_source_translate_event at x11/gdkeventsource.c:243
#7 _gdk_x11_display_queue_events at x11/gdkeventsource.c:341
#8 gdk_display_get_event at
/usr/src/debug/gtk3-3.24.30-1.fc34.x86_64/gdk/gdkdisplay.c:442
#12 g_main_context_iterate.constprop.0 at ../glib/gmain.c:4131
--
You are receiving this mail because:
You are on the CC list for the bug.
2 weeks, 3 days
[Bug 2004265] New: Official name of Taiwan is wrong
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2004265
Bug ID: 2004265
Summary: Official name of Taiwan is wrong
Product: Fedora
Version: 35
Hardware: All
Status: NEW
Component: iso-codes
Assignee: pnemade(a)redhat.com
Reporter: julian.g(a)posteo.de
QA Contact: extras-qa(a)fedoraproject.org
CC: caillon+fedoraproject(a)gmail.com,
gnome-sig(a)lists.fedoraproject.org,
i18n-bugs(a)lists.fedoraproject.org, mclasen(a)redhat.com,
pnemade(a)redhat.com, rhughes(a)redhat.com,
rstrode(a)redhat.com, sandmann(a)redhat.com
Target Milestone: ---
Classification: Fedora
Description of problem:
The "official name" of the country on Taiwan is wrong. It states "Province of
China", which is obviously not its official name. No country would call itself
"Province" of another country. The official name is "Republic of China".
Some sources:
- Official government website https://www.taiwan.gov.tw by the RoC Ministry of
Foreign Affairs
- You can ask any person living on the Island.
- As an IT person, you might have some hardware labeled "Made in RoC".
- The Hong Kong and the Taiwanese locale both have "中華民國" as a translation,
which means "Republic of China".
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2004265
2 weeks, 4 days
[Fedora-i18n-bugs] [Bug 1757760] New: Hiragana to English conversion with F10 key adds unwanted letters
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1757760
Bug ID: 1757760
Summary: Hiragana to English conversion with F10 key adds
unwanted letters
Product: Fedora
Version: rawhide
Status: NEW
Component: ibus-kkc
Assignee: dueno(a)redhat.com
Reporter: ykatabam(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
Description of problem:
When we enter an English word with consecutive double letters (e.g. assembly)
in Hiragana mode and use F10 to convert into English, the double letters
becomes the triple letters in some cases (e.g. asssembly).
This happens irregularly, but tends to happen more often for longer words.
Here are some examples:
communication becomes commmunication
bugzilla becomes bugzilla
Pittsburgh becomes Pitttsburgh
FYI, auto-correct is disabled, as auto-correct changes the input when it's not
a dictionary word so it doesn't allow us to convert into English properly in
hiragana mode.
--
You are receiving this mail because:
You are on the CC list for the bug.
2 weeks, 4 days
[Bug 1964374] New: stardict scan hotkey doesn't work
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1964374
Bug ID: 1964374
Summary: stardict scan hotkey doesn't work
Product: Fedora
Version: 33
Status: NEW
Component: stardict
Assignee: psatpute(a)redhat.com
Reporter: antmak.pub(a)gmail.com
QA Contact: extras-qa(a)fedoraproject.org
CC: anish.developer(a)gmail.com,
i18n-bugs(a)lists.fedoraproject.org, nav007(a)gmail.com,
petersen(a)redhat.com, psatpute(a)redhat.com,
pwu(a)redhat.com, robinlee.sysu(a)gmail.com,
yanqiyu01(a)gmail.com
Target Milestone: ---
Classification: Fedora
Description of problem:
The "Use scan hotkey:" option from StarDict's Preferences doesn't work
Version-Release number of selected component (if applicable):
stardict-3.0.6-15.fc33.x86_64
Fedore 33
GNOME @ Wayland session
How reproducible:
Just change the option to any value, it doesn't work.
Steps to Reproduce:
1. Open StarDict
2. Open Preferences, "Scan Selection" tab
3. Enable "Use scan hotkey" option.
4. Values: "<Primary><Alt>x", "<Super>j", "<Primary><Alt>j" don't work - it
can't scan selected words from other windows like Firefox or Gedit
Actual results:
It should scan selected words in other apps and open a translate window
Expected results:
Additional info:
--
You are receiving this mail because:
You are on the CC list for the bug.
2 weeks, 5 days
[Fedora-i18n-bugs] [Bug 1936777] New: [abrt] ibus: ibus_bus_connect_async(): ibus-x11 killed by SIGSEGV
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1936777
Bug ID: 1936777
Summary: [abrt] ibus: ibus_bus_connect_async(): ibus-x11 killed
by SIGSEGV
Product: Fedora
Version: 34
Hardware: x86_64
Status: NEW
Whiteboard: abrt_hash:e9e25725fbf5b802310f7153823734fd779117b2;VAR
IANT_ID=workstation;
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
Version-Release number of selected component:
ibus-1.5.24-1.fc34
Additional info:
reporter: libreport-2.14.0
backtrace_rating: 4
cgroup:
0::/user.slice/user-1000.slice/user@1000.service/session.slice/org.gnome.Shell@wayland.service
cmdline: /usr/libexec/ibus-x11 --kill-daemon
crash_function: ibus_bus_connect_async
executable: /usr/libexec/ibus-x11
journald_cursor:
s=f2062dd079fe488fb71eaaf5c3a6c6de;i=64d9;b=7aa46cfdf18e49c4bdacf0acfee8806c;m=b349fea0;t=5bd0beaaa310b;x=3f2d3a76fa7ae073
kernel: 5.11.3-300.fc34.x86_64
rootdir: /
runlevel: N 5
type: CCpp
uid: 1000
Truncated backtrace:
Thread no. 1 (6 frames)
#0 ibus_bus_connect_async at
/usr/src/debug/ibus-1.5.24-1.fc34.x86_64/src/ibusbus.c:462
#1 _g_cclosure_marshal_VOID__OBJECT_OBJECT_ENUMv at
../gio/gmarshal-internal.c:1380
#2 _g_closure_invoke_va at ../gobject/gclosure.c:873
#5 g_file_monitor_source_dispatch at ../gio/glocalfilemonitor.c:567
#8 g_main_context_iterate.constprop.0 at ../glib/gmain.c:4131
#10 ibus_main at /usr/src/debug/ibus-1.5.24-1.fc34.x86_64/src/ibusshare.c:318
Potential duplicate: bug 1926996
--
You are receiving this mail because:
You are on the CC list for the bug.
2 weeks, 5 days
[Fedora-i18n-bugs] [Bug 1847347] New: gnome-terminal and xfce4-terminal get surrounding text from previous application
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1847347
Bug ID: 1847347
Summary: gnome-terminal and xfce4-terminal get surrounding text
from previous application
Product: Fedora
Version: 32
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
I made the following screenshots and video by testing on Gnome-Xorg, but the
problem occurs on Gnome-Wayland as well.
How to reproduce (see also attached screenshots and video):
- To show what happens with the surrounding text, I first opened the
setup tool of ibus-typing-booster and set the debug level in the
options tab to 3.
When the debug level is high, the auxiliary text above the candidate
list shows what context has been obtained by using surrounding text
(if surrounding text is available, if it is not available like when
using xterm, the context is just remembered from what was typed
last).
- I opened 3 windows: gedit, firefox, and gnome-terminal.
- I focus on gedit and type "a b c d e"
On top of the candidate list one can see: "Context: b c d"
This is because when the letter "e" was typed, ibus-typing-booster
got the surrounding text at the cursor position and parsed the last
3 tokens left of the cursor out of the result. And these
last 3 tokens left of the cursor are "b c d".
- Now I focus on firefox and type "f g h i j"
On top of the candidate list one can see: "Context: g h i"
I.e. the correct context "g h i" to the left of the just typed "j"
(which is still in preedit) has been found using surrounding text.
- Now I focus on gnome-terminal and type "k l m"
On top of the candidate list one can see: "Context h i j"
This comes from the surrounding text left of the cursor in
*firefox*, *not* from gnome-terminal.
Although gnome-terminal reports that surrounding text is supported, i.e.
self.client_capabilities & IBus.Capabilite.SURROUNDING_TEXT
is True (see the code to get the context at:
https://github.com/mike-fabian/ibus-typing-booster/blob/master/engine/hun...
)
gnome-terminal does not really seem to support surrounding text.
The surrounding text comes from the previous client which really supported
surrounding text.
If the previous client was firefox, one still gets the surrounding text from
firefox while typing in gnome-terminal.
Same with gedit, if the previous client before focussing on gnome-terminal
was gedit, one still gets the surrounding text from gedit while typing in
gnome-terminal.
- The same problem occurs when using xfce4-terminal instead of gnome-terminal.
- When using xterm, the problem does *not* occur because when using xterm
self.client_capabilities & IBus.Capabilite.SURROUNDING_TEXT
is False and then the get_context() immediately returns and the context
remembered from the last text typed is used as a fallback.
--
You are receiving this mail because:
You are on the CC list for the bug.
3 weeks, 5 days
[Bug 1993618] New: [abrt] ibus-libpinyin:
PY::PunctEditor::moveCursorToBegin(): ibus-engine-libpinyin killed by SIGABRT
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1993618
Bug ID: 1993618
Summary: [abrt] ibus-libpinyin:
PY::PunctEditor::moveCursorToBegin():
ibus-engine-libpinyin killed by SIGABRT
Product: Fedora
Version: 34
Hardware: x86_64
Status: NEW
Whiteboard: abrt_hash:e41f218ee5601bc1377bb63d92ea7cfafa49f6df;VAR
IANT_ID=workstation;
Component: ibus-libpinyin
Assignee: pwu(a)redhat.com
Reporter: tcfxfzoi(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
Version-Release number of selected component:
ibus-libpinyin-1.12.0-3.fc34
Additional info:
reporter: libreport-2.15.2
backtrace_rating: 4
cgroup:
0::/user.slice/user-1000.slice/user@1000.service/session.slice/org.gnome.Shell@wayland.service
cmdline: /usr/libexec/ibus-engine-libpinyin --ibus
crash_function: PY::PunctEditor::moveCursorToBegin
executable: /usr/libexec/ibus-engine-libpinyin
journald_cursor:
s=b843de467070413eac4da2bc5d966ff5;i=701f;b=c1ce31806f0448d2826bedd20c47fa6b;m=99564a78;t=5c986a4580fd5;x=bf2d4d76d0a056b9
kernel: 5.13.9-200.fc34.x86_64
rootdir: /
runlevel: N 5
type: CCpp
uid: 1000
Truncated backtrace:
Thread no. 1 (9 frames)
#4 PY::PunctEditor::moveCursorToBegin at
/usr/src/debug/ibus-libpinyin-1.12.0-3.fc34.x86_64/src/PYPunctEditor.cc:317
#5 PY::PunctEditor::processKeyEvent at
/usr/src/debug/ibus-libpinyin-1.12.0-3.fc34.x86_64/src/PYPunctEditor.cc:190
#6 PY::BopomofoEngine::processKeyEvent at
/usr/src/debug/ibus-libpinyin-1.12.0-3.fc34.x86_64/src/PYPBopomofoEngine.cc:198
#8 _ibus_marshal_BOOLEAN__UINT_UINT_UINT at
/usr/src/debug/ibus-1.5.24-5.fc34.x86_64/src/ibusmarshalers.c:280
#13 ibus_engine_service_method_call at
/usr/src/debug/ibus-1.5.24-5.fc34.x86_64/src/ibusengine.c:1107
#14 call_in_idle_cb at ../gio/gdbusconnection.c:4913
#18 g_main_context_iterate.constprop.0 at ../glib/gmain.c:4131
#20 ibus_main at /usr/src/debug/ibus-1.5.24-5.fc34.x86_64/src/ibusshare.c:322
#21 start_component at
/usr/src/debug/ibus-libpinyin-1.12.0-3.fc34.x86_64/src/PYMain.cc:141
--
You are receiving this mail because:
You are on the CC list for the bug.
1 month, 1 week
