[Bug 2169205] New: [abrt] ibus: invoke_set_property_in_idle_cb():
ibus-daemon killed by SIGABRT
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2169205
Bug ID: 2169205
Summary: [abrt] ibus: invoke_set_property_in_idle_cb():
ibus-daemon killed by SIGABRT
Product: Fedora
Version: 37
Hardware: x86_64
Status: NEW
Whiteboard: abrt_hash:4e043177db9a4fb30f16b25cea5a2ff893c33bd1;VAR
IANT_ID=workstation;
Component: ibus
Assignee: tfujiwar(a)redhat.com
Reporter: redhat(a)nerdbynature.de
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-5.fc37
Additional info:
reporter: libreport-2.17.4
backtrace_rating: 4
cmdline: /usr/bin/ibus-daemon --panel disable --xim
crash_function: invoke_set_property_in_idle_cb
executable: /usr/bin/ibus-daemon
journald_cursor:
s=ad51c57b68c643e7a42dbc2d1074a8af;i=109d;b=02f54c0e24fd45ff9ba8f5c922677bfb;m=39a7096;t=5f484cab7de9e;x=a0fa4ec66a14d500
kernel: 6.1.10-200.fc37.x86_64
rootdir: /
runlevel: N 5
type: CCpp
uid: 1000
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2169205
7 months, 1 week
[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
7 months, 1 week
[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
7 months, 1 week
[Bug 2095964] New: [abrt] ibus-typing-booster:
_cairo_spline_decompose_into(): python3.10 killed by SIGSEGV
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2095964
Bug ID: 2095964
Summary: [abrt] ibus-typing-booster:
_cairo_spline_decompose_into(): python3.10 killed by
SIGSEGV
Product: Fedora
Version: 36
Hardware: x86_64
Status: NEW
Whiteboard: abrt_hash:2104ae08f8add1a3508578f46afd328904cf0c5f;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
backtrace_rating: 4
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: _cairo_spline_decompose_into
executable: /usr/bin/python3.10
journald_cursor:
s=d60f71b9c5714507ad521e587b3c1f0d;i=1248;b=dd038a3840c74507a58b652d3fc610f5;m=432f3ff97;t=5e118b88e9096;x=d66e6beb9878ecc
kernel: 5.17.13-300.fc36.x86_64
rootdir: /
runlevel: N 5
type: CCpp
uid: 1000
Truncated backtrace:
Thread no. 1 (1 frames)
#0 _cairo_spline_decompose_into at ../src/cairo-spline.c:252
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2095964
7 months, 1 week
[Bug 2165332] New: Please update ddskk to 17.1 in Fedora 37 & 36
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2165332
Bug ID: 2165332
Summary: Please update ddskk to 17.1 in Fedora 37 & 36
Product: Fedora
Version: 37
Status: NEW
Component: emacs-common-ddskk
Assignee: dueno(a)redhat.com
Reporter: dan.cermak(a)cgc-instruments.com
QA Contact: extras-qa(a)fedoraproject.org
CC: dueno(a)redhat.com, i18n-bugs(a)lists.fedoraproject.org
Target Milestone: ---
Link ID: Red Hat Bugzilla 2118205
Classification: Fedora
Description of problem:
It appears that ddskk 16.2 is causing issues with Emacs 28.2
(https://bugzilla.redhat.com/show_bug.cgi?id=2118205). I think that ddskk 17.1
resolves this problem. Can you please build it F37 & F36?
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1. dnf install emacs emacs-common-ddskk
2. run emacs
3. `Cannot open load file: No such file or directory, comp` is displayed in the
*Messages* buffer.
Actual results:
Expected results:
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=2165332
7 months, 2 weeks
[Bug 2129399] Postscript standard symbol font is not looked up
correctly
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2129399
--- Comment #31 from rgb(a)phy.duke.edu ---
Well, I read the fonts-conf documentation and examples pretty thoroughly,
installed font-manager so I could see the fonts themselves, and there are many,
many font sets on the system that contain the requisite characters. It is very
difficult to tell which one is causing the problem or how to replace it. I
spent two hours trying variations on your <alias> section including <match>
statements, replacing the various systems fond initialization steps, etc. It
sadly remains the case that while I can display my unembedded test file on a
scientific linux box in the department and it renders perfectly (over X) when I
try to look at exactly the same file on Fedora it has nothing but boxes. My
embedded font ps2pdf version of the same file displays everywhere.
I agree that it is probably something in /etc/fonts/fonts.conf and/or
/etc/fonts/conf.d/[??]whatever-symbol-font-isn't-working.conf and that just the
right override might fix it, that requires diffing and checking around 100+
files, most of which are certainly irrelevant, looking for a possibly
significant change in an XML that I don't completely understand to see which
one works correctly on scientific linux (a RH base IIRC) but not on Fedora
(another RH base). I could maybe install a Centos VM to test -- I don't have a
RH license on any personal systems, obviously.
The possibility remains that it is a change in evince itself as well. This I
can't really test -- obviously, if I copy over a binary from the system where
it works it has the wrong libraries on my laptop, and mucking around at the
library level is an open invitation to having to do a hard reinstall (been
there, done that:-).
Right now I HAVE to go back to my regular work and write a quiz for my physics
students with (sigh) embedded fonts and so far I nothing I've done has
fundamentally broken font rendering per se, but in any event no, the alias
above does not work whether or not it is font.conf or 0-symbol.conf. The
documentation suggests that the former is the right place for it -- and I could
verify that this file was indeed being parsed in real time as I made changes as
errors were instantly reported in tty's containing rendered fonts -- but the
latter seems like it might only be scanned at boot or login time, since the
leading 00 (if I understand things) represents the order in which the file
configs are layered at startup. I >>think<< the system rereads this ever 30
seconds by default so it shouldn't matter, but again -- no time to test, an
incredibly complex system and syntax, and crappy tools for manipulating it or
even displaying it. Font-manager is the best I've found, but I don't know if
it can be used to rewrite rules yet (or if it is wise to trust it while doing
so).
Sorry.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2129399
7 months, 2 weeks
[Bug 2129399] Postscript standard symbol font is not looked up
correctly
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2129399
--- Comment #30 from Akira TAGOH <tagoh(a)redhat.com> ---
Sorry, my words weren't enough. Well, you may need to write a config like the
above but replace DejaVu Sans to any of them. Unfortunately just installing
them doesn't help right. I'm asking what is sufficient for alternatives of
Symbol font.
Please put the following config into
$HOME/.config/fontconfig/conf.d/0-symbol.conf and replacing FONTNAME to any of
"Noto Sans Symbols", "Noto Sans Symbols 2", "Symbola".
<fontconfig>
<alias>
<family>Symbol</family>
<default><family>FONTNAME</family></default>
</alias>
</fontconfig>
This will makes fontconfig to pick up any of them as alternatives to Symbol.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2129399
7 months, 2 weeks