[Bug 2164233] New: FcCacheFini: Assertion `fcCacheChains[i] == NULL'
failed.
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2164233
Bug ID: 2164233
Summary: FcCacheFini: Assertion `fcCacheChains[i] == NULL'
failed.
Product: Fedora
Version: 37
Status: NEW
Component: fontconfig
Assignee: tagoh(a)redhat.com
Reporter: byoungchan.lee(a)gmx.com
QA Contact: extras-qa(a)fedoraproject.org
CC: ajax(a)redhat.com, fonts-bugs(a)lists.fedoraproject.org,
gnome-sig(a)lists.fedoraproject.org,
i18n-bugs(a)lists.fedoraproject.org, mclasen(a)redhat.com,
pnemade(a)redhat.com, rstrode(a)redhat.com,
sandmann(a)redhat.com, tagoh(a)redhat.com
Target Milestone: ---
Classification: Fedora
Description of problem:
When I try to run openttd, fontconfig crashes due to an assertion.
https://github.com/freedesktop/fontconfig/blob/2.14.1/src/fccache.c#L808
Version-Release number of selected component (if applicable):
$ rpm -qa | grep fontconfig
fontconfig-2.14.1-2.fc37.x86_64
fontconfig-2.14.1-2.fc37.i686
fontconfig-devel-2.14.1-2.fc37.x86_64
fontconfig-debugsource-2.14.1-2.fc37.x86_64
$ rpm -qa | grep openttd
openttd-opengfx-7.1-3.fc37.noarch
openttd-12.2-4.fc37.x86_64
How reproducible:
Run openttd
Steps to Reproduce:
1.
2.
3.
Actual results:
Crash
Expected results:
Game runs.
Additional info:
I'm not sure why assertions are enabled in fontconfig.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2164233
1 year
[Bug 2124007] New: Keyboard disappears from list of installed
keyboards
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2124007
Bug ID: 2124007
Summary: Keyboard disappears from list of installed keyboards
Product: Fedora
Version: 36
Hardware: x86_64
OS: Linux
Status: NEW
Component: anthy
Assignee: tagoh(a)redhat.com
Reporter: Ben.Engbers(a)Be-Logical.nl
QA Contact: extras-qa(a)fedoraproject.org
CC: i18n-bugs(a)lists.fedoraproject.org, tagoh(a)redhat.com,
tfujiwar(a)redhat.com
Target Milestone: ---
Classification: Fedora
Description of problem:
I have installed 3 keyboards (English VS, English International and Anthy).
Anthy is mostly used in Libre Office Writer 7.3.4.2. I can switch the keyboard
either by selecting one in the upper right corner of the screen or by cycling
through te list of installed keyboards with Windows key/spacebar.
After a few minutes my Lenovo laptop goes to sleep automatically. When I wake
it up again, the Anthy keyboard has disappeared from the list of keyboards.
Only the 2 English keyboards can be selected. In the settings dialog however,
the Anthy keyboard is still visible.
It is only after a new logon that the Japanese keyboard shows up again.
Version-Release number of selected component (if applicable):
How reproducible:
Always
Steps to Reproduce:
1. Logon after boot
2. Wait till the laptop goes to sleep
3. Wake up.
Actual results:
Anthy keyboard is no longer visible
Expected results:
Anthy keyboard can not be selected
Additional info:
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2124007
1 year
[Bug 2062619] New: IBus stop working after locking screen
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2062619
Bug ID: 2062619
Summary: IBus stop working after locking screen
Product: Fedora
Version: rawhide
Status: NEW
Component: ibus
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
Description of problem:
When I keep preediting on apps and the screen is locked by idle, IBus stop
working after unlocking.
Version-Release number of selected component (if applicable):
ibus-1.5.25-13.fc36.x86_64
How reproducible:
always
Steps to Reproduce:
1.Install Workstation from Live
2.Setup with ja
3.Open LibreOffice Writer
4.Type something on preedit and wait for locking the screen
5.Unlock the screen
Actual results:
Unable to input through IBus on apps
Expected results:
Able to input through IBus
Additional info:
IBus get back after changing the focus for example.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2062619
1 year
[Fedora-i18n-bugs] [Bug 1895482] New: Liberation Fonts Support For Serbian locl Glyphs Incomplete
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1895482
Bug ID: 1895482
Summary: Liberation Fonts Support For Serbian locl Glyphs
Incomplete
Product: Fedora
Version: rawhide
Hardware: x86_64
OS: Linux
Status: NEW
Component: liberation-fonts
Assignee: vishalvijayraghavan(a)gmail.com
Reporter: aleslavista(a)outlook.it
QA Contact: extras-qa(a)fedoraproject.org
CC: caillon+fedoraproject(a)gmail.com,
fonts-bugs(a)lists.fedoraproject.org,
gnome-sig(a)lists.fedoraproject.org,
i18n-bugs(a)lists.fedoraproject.org, mclasen(a)redhat.com,
petersen(a)redhat.com, psatpute(a)redhat.com,
rhughes(a)redhat.com, rstrode(a)redhat.com,
sandmann(a)redhat.com, vishalvijayraghavan(a)gmail.com
Target Milestone: ---
Classification: Fedora
Created attachment 1727218
--> https://bugzilla.redhat.com/attachment.cgi?id=1727218&action=edit
Correctly Localized Glyphs
Description of problem:
Liberation Fonts do NOT provide full support for Serbian localized glyphs.
Version-Release number of selected component (if applicable):
Liberation-Fonts 2.1-1-1
How reproducible:
You need a program that is able to access the font's localized glyphs: usually
that's LibreOffice Writer.
Steps to Reproduce:
1. Open LibreOffice Writer
2. Type бгдпт, then бгдпт in Italic, бгдпт in Bold and finally бгдпт in Italic
Bold with Liberation Serif, and do the same with Liberation Sans
3. Set the language to "Serbian Cyrillic"
Actual results:
Not all glyphs are correctly localized
Expected results:
See attachment for correctly localized glyphs
Additional info:
Liberation Mono has slanted Italic, therefore only the first glyph should be
localized: CYRILLIC LETTER SMALL BE.
--
You are receiving this mail because:
You are on the CC list for the bug.
1 year
[Bug 2062407] New: msgfmt cannot invoke javac
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2062407
Bug ID: 2062407
Summary: msgfmt cannot invoke javac
Product: Fedora
Version: rawhide
Hardware: All
OS: Linux
Status: NEW
Component: gettext
Severity: low
Assignee: suanand(a)redhat.com
Reporter: loganjerry(a)gmail.com
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
Target Milestone: ---
Classification: Fedora
Description of problem:
I noticed while building jmol that every invocation of msgfmt failed, e.g.:
update-application-catalog-lang:
[echo] msgfmt Updating messages_ar.class file for Jmol ...
[exec] msgfmt: Java compiler not found, try installing gcj or set $JAVAC
[exec] msgfmt: compilation of Java class failed, please try --verbose or
set $JAVAC
[exec] 65 translated messages, 3 fuzzy translations, 380 untranslated
messages.
[exec] Result: 1
Setting JAVAC does *not* help. I used strace to see how javac is invoked and
found the problem: msgfmt passes -target 1.6, and sometimes -source 1.6, to
javac. Now that OpenJDK 17 is the default in Fedora, those arguments are no
longer valid. I don't remember if the minimum allowed is 1.7 or 1.8, but it is
one of the two. Since Fedora doesn't ship a JDK lower than 1.8, then 1.8 might
as well be used.
Version-Release number of selected component (if applicable):
gettext-0.21-11.fc37.0.20220228
How reproducible:
Always
Steps to Reproduce:
1. fedpkg clone jmol
2. cd jmol
3. fedpkg srpm
4. mock -r fedora-rawhide-x86_64 --rebuild jmol-14.32.22-1.fc37.src.rpm
Actual results:
The msgfmt invocations all fail.
Expected results:
The msgfmt invocations should succeed.
Additional info:
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2062407
1 year
[Bug 2157582] New: Environment variables are no longer set in
Wayland session after systemd subpackage was removed
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2157582
Bug ID: 2157582
Summary: Environment variables are no longer set in Wayland
session after systemd subpackage was removed
Product: Fedora
Version: 37
Status: NEW
Component: imsettings
Assignee: tagoh(a)redhat.com
Reporter: accounts+fedora(a)chiller3.com
QA Contact: extras-qa(a)fedoraproject.org
CC: i18n-bugs(a)lists.fedoraproject.org, tagoh(a)redhat.com
Target Milestone: ---
Classification: Fedora
Description of problem:
After the removal of the imsettings-systemd subpackage, the IM-related
environment variables (eg. QT_IM_MODULE) are no longer set in Wayland sessions
(as least for KDE). I believe this is because none of the xinput scripts are
read during Wayland session initialization and things previously relied on
systemd's ~/.config/environment.d/.
Version-Release number of selected component (if applicable):
imsettings-1.8.3-6.fc37.x86_64
How reproducible:
Always
Steps to Reproduce:
1. Install Fedora 37 KDE spin
2. Log into Wayland session
3. Install an input method, like fcitx5
4. Select fcitx5 with im-chooser
5. Log out and log back in (still Wayland session)
6. $ echo $QT_IM_MODULE
Actual results:
Environment variables like QT_IM_MODULE are not set.
Expected results:
The IM-related environment variables should be set. (Manually setting them
allows input methods to work properly in KDE Wayland.)
Additional info:
n/a
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2157582
1 year
[Bug 2156108] New: [abrt] ibus: XFree(): ibus-x11 killed by SIGABRT
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2156108
Bug ID: 2156108
Summary: [abrt] ibus: XFree(): ibus-x11 killed by SIGABRT
Product: Fedora
Version: rawhide
Hardware: x86_64
Status: NEW
Whiteboard: abrt_hash:0385d31cccb3ffe2c784112a5c2060eeaac62698;VAR
IANT_ID=workstation;
Component: ibus
Assignee: tfujiwar(a)redhat.com
Reporter: mikhail.v.gavrilov(a)gmail.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.27-8.fc38
Additional info:
reporter: libreport-2.17.6
type: CCpp
reason: ibus-x11 killed by SIGABRT
journald_cursor:
s=32500b5f39e6467e9ccddd56700852eb;i=43e8f3;b=f22e26d260164e228db6c4bc7b4ef7db;m=869ce7646;t=5f017821d96fc;x=29a8c76b08f7f956
executable: /usr/libexec/ibus-x11
cmdline: /usr/libexec/ibus-x11
cgroup:
0::/user.slice/user-1000.slice/user@1000.service/session.slice/org.gnome.SettingsDaemon.XSettings.service
rootdir: /
uid: 1000
kernel: 6.1.0-65.fc38.x86_64+debug
package: ibus-1.5.27-8.fc38
runlevel: N 5
backtrace_rating: 4
crash_function: XFree
Truncated backtrace:
Thread no. 1 (19 frames)
#8 XFree at /usr/src/debug/libX11-1.8.1-2.fc38.x86_64/src/XlibInt.c:1633
#9 ProcessQueue at ../../util/IMdkit/i18nPtHdr.c:1762
#10 _Xi18nMessageHandler at ../../util/IMdkit/i18nPtHdr.c:1923
#11 WaitXIMProtocol at ../../util/IMdkit/i18nX.c:524
#12 _gdk_x11_display_queue_events at ../gdk/x11/gdkeventsource.c:337
#13 gdk_display_get_event at ../gdk/gdkdisplay.c:442
#14 gdk_event_source_dispatch.lto_priv at ../gdk/x11/gdkeventsource.c:354
#17 g_main_context_iterate.constprop.0 at ../glib/gmain.c:4238
#18 g_main_context_iteration at ../glib/gmain.c:4303
#19 xim_forward_event.constprop.0 at
/usr/src/debug/ibus-1.5.27-8.fc38.x86_64/client/x11/main.c:631
#20 ForwardEventMessageProc at ../../util/IMdkit/i18nPtHdr.c:1224
#21 ProcessQueue at ../../util/IMdkit/i18nPtHdr.c:1758
#22 _Xi18nMessageHandler at ../../util/IMdkit/i18nPtHdr.c:1923
#23 WaitXIMProtocol at ../../util/IMdkit/i18nX.c:524
#24 _gdk_x11_display_queue_events at ../gdk/x11/gdkeventsource.c:337
#25 gdk_display_get_event at ../gdk/gdkdisplay.c:442
#26 gdk_event_source_dispatch.lto_priv at ../gdk/x11/gdkeventsource.c:354
#29 g_main_context_iterate.constprop.0 at ../glib/gmain.c:4238
#31 ibus_main at /usr/src/debug/ibus-1.5.27-8.fc38.x86_64/src/ibusshare.c:325
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2156108
1 year, 1 month
[Bug 2095904] New: [abrt] ibus-typing-booster: read():
gzip.py:496:read:zlib.error: Error -3 while decompressing data: invalid
distance too far back
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2095904
Bug ID: 2095904
Summary: [abrt] ibus-typing-booster: read():
gzip.py:496:read:zlib.error: Error -3 while
decompressing data: invalid distance too far back
Product: Fedora
Version: 36
Hardware: x86_64
Status: NEW
Whiteboard: abrt_hash:9aea8105e48adf15942982fad50f1476a116dd11;VAR
IANT_ID=workstation;
Component: ibus-typing-booster
Assignee: mfabian(a)redhat.com
Reporter: mfabian(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: anish.developer(a)gmail.com,
i18n-bugs(a)lists.fedoraproject.org, mfabian(a)redhat.com
Target Milestone: ---
Classification: Fedora
Description of problem:
Version-Release number of selected component:
ibus-typing-booster-2.15.27-1.fc36
Additional info:
reporter: libreport-2.17.1
cgroup:
0::/user.slice/user-1000.slice/user@1000.service/session.slice/org.freedesktop.IBus.session.GNOME.service
cmdline: /usr/bin/python /usr/share/ibus-typing-booster/engine/main.py
--ibus
crash_function: read
exception_type: zlib.error
executable: /usr/share/ibus-typing-booster/engine/main.py
interpreter: python-unversioned-command-3.10.4-1.fc36.noarch
kernel: 5.17.13-300.fc36.x86_64
runlevel: N 5
type: Python3
uid: 1000
Truncated backtrace:
#1 [/usr/lib64/python3.10/gzip.py:496] read
#2 [/usr/lib64/python3.10/_compression.py:68] readinto
#3 [/usr/lib64/python3.10/gzip.py:301] read
#4 [/usr/lib/python3.10/site-packages/langtable/langtable.py:912] _expat_parse
#5 [/usr/lib/python3.10/site-packages/langtable/langtable.py:932] _read_file
#6 [/usr/lib/python3.10/site-packages/langtable/langtable.py:2540] _init
#7 [/usr/lib/python3.10/site-packages/langtable/langtable.py:2547] __init__
#8 [/usr/lib/python3.10/site-packages/langtable/langtable.py:2553] <module>
#9 [/usr/lib/python3.10/site-packages/langtable/__init__.py:1] <module>
#10 [/usr/share/ibus-typing-booster/engine/itb_util.py:89] <module>
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2095904
1 year, 2 months
[Bug 2095905] New: [abrt] ibus-typing-booster: _expat_parse():
langtable.py:912:_expat_parse:xml.parsers.expat.ExpatError: not well-formed
(invalid token): line 11583, column 64
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2095905
Bug ID: 2095905
Summary: [abrt] ibus-typing-booster: _expat_parse():
langtable.py:912:_expat_parse:xml.parsers.expat.ExpatE
rror: not well-formed (invalid token): line 11583,
column 64
Product: Fedora
Version: 36
Hardware: x86_64
Status: NEW
Whiteboard: abrt_hash:9a0e6dba4ca5dc3486a02f907d47050684522fb5;VAR
IANT_ID=workstation;
Component: ibus-typing-booster
Assignee: mfabian(a)redhat.com
Reporter: mfabian(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: anish.developer(a)gmail.com,
i18n-bugs(a)lists.fedoraproject.org, mfabian(a)redhat.com
Target Milestone: ---
Classification: Fedora
Description of problem:
Version-Release number of selected component:
ibus-typing-booster-2.15.27-1.fc36
Additional info:
reporter: libreport-2.17.1
cgroup:
0::/user.slice/user-1000.slice/user@1000.service/session.slice/org.freedesktop.IBus.session.GNOME.service
cmdline: /usr/bin/python /usr/share/ibus-typing-booster/setup/main.py
crash_function: _expat_parse
exception_type: xml.parsers.expat.ExpatError
executable: /usr/share/ibus-typing-booster/setup/main.py
interpreter: python-unversioned-command-3.10.4-1.fc36.noarch
kernel: 5.17.13-300.fc36.x86_64
runlevel: N 5
type: Python3
uid: 1000
Truncated backtrace:
langtable.py:912:_expat_parse:xml.parsers.expat.ExpatError: not well-formed
(invalid token): line 11583, column 64
Traceback (most recent call last):
File "/usr/share/ibus-typing-booster/setup/main.py", line 87, in <module>
import tabsqlitedb
File "/usr/share/ibus-typing-booster/setup/../engine/tabsqlitedb.py", line
38, in <module>
import itb_util
File "/usr/share/ibus-typing-booster/setup/../engine/itb_util.py", line 89,
in <module>
import langtable # type: ignore
File "/usr/lib/python3.10/site-packages/langtable/__init__.py", line 1, in
<module>
from .langtable import *
File "/usr/lib/python3.10/site-packages/langtable/langtable.py", line 2553,
in <module>
__module_init = __ModuleInitializer()
File "/usr/lib/python3.10/site-packages/langtable/langtable.py", line 2547,
in __init__
_init()
File "/usr/lib/python3.10/site-packages/langtable/langtable.py", line 2539,
in _init
_read_file('territories.xml', TerritoriesContentHandler())
File "/usr/lib/python3.10/site-packages/langtable/langtable.py", line 932, in
_read_file
_expat_parse(file, sax_handler)
File "/usr/lib/python3.10/site-packages/langtable/langtable.py", line 912, in
_expat_parse
parser.ParseFile(file)
xml.parsers.expat.ExpatError: not well-formed (invalid token): line 11583,
column 64
Local variables in innermost frame:
file: <gzip on 0x7f2248a50700>
sax_handler: <langtable.langtable.TerritoriesContentHandler object at
0x7f2248a507f0>
parser: <pyexpat.xmlparser object at 0x7f2248a2e9e0>
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2095905
1 year, 2 months