https://bugzilla.redhat.com/show_bug.cgi?id=1787124
Bug ID: 1787124
Summary: [abrt] ibus-mozc: __fdelt_chk(): ibus-engine-mozc
killed by SIGABRT
Product: Fedora
Version: 31
Hardware: x86_64
Status: NEW
Whiteboard: abrt_hash:d88e523ce263f66e445a1a6f6cd666d77fad9e05;VAR
IANT_ID=matecompiz;
Component: mozc
Assignee: tagoh(a)redhat.com
Reporter: ryutaroh2006(a)gmail.com
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:
I don't know how or why ibuz-engine-mozc was killed by SIGABRT...
Version-Release number of selected component:
ibus-mozc-2.23.2815.102-8.fc31
Additional info:
reporter: libreport-2.11.3
backtrace_rating: 4
cgroup:
0::/user.slice/user-1000.slice/user@1000.service/dbus\x2d:1.2\x2dcom.redhat.imsettings.slice/dbus-:1.2-com.redhat.imsettings@0.service
cmdline: /usr/libexec/ibus-engine-mozc --ibus
crash_function: __fdelt_chk
executable: /usr/libexec/ibus-engine-mozc
journald_cursor:
s=4479f645f2da4f17afc9f9415d05055f;i=b7c0;b=a6e351a2ff374b38832aa98ebe9457dd;m=7e0bcb9b;t=59afce7bb1367;x=508717657a4cb7e9
kernel: 5.3.16-300.fc31.x86_64
rootdir: /
runlevel: N 5
type: CCpp
uid: 1000
Truncated backtrace:
Thread no. 1 (4 frames)
#6 __fdelt_chk at fdelt_chk.c:25
#7 mozc::(anonymous namespace)::IsWriteTimeout at ../../ipc/unix_ipc.cc:108
#8 mozc::(anonymous namespace)::SendMessage at ../../ipc/unix_ipc.cc:157
#9 mozc::IPCClient::Call at ../../ipc/unix_ipc.cc:328
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1899794
Bug ID: 1899794
Summary: Fails to run on KDE in Rawhide
Product: Fedora
Version: rawhide
Hardware: All
OS: Linux
Status: NEW
Component: system-config-language
Severity: high
Assignee: pnemade(a)redhat.com
Reporter: awilliam(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: i18n-bugs(a)lists.fedoraproject.org, nav007(a)gmail.com,
pnemade(a)redhat.com, psatpute(a)redhat.com
Target Milestone: ---
Classification: Fedora
In current Rawhide, system-config-language is installed on KDE out of the box,
but fails to run. Running from a console, after you are prompted for the root
password, you get these errors:
No protocol specified
Unable to init server: Could not connect: Connection refused
No protocol specified
Unable to init server: Could not connect: Connection refused
No protocol specified
Unable to init server: Could not connect: Connection refused
(system-config-language.py:2146): Gtk-WARNING **: 18:09:41.831: cannot open
display: :1
then it exits back to the console.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1903877
Bug ID: 1903877
Summary: kde-l10n-pa missing translated file
Product: Fedora
Version: 33
Status: NEW
Component: kde-l10n
Keywords: i18n
Assignee: than(a)redhat.com
Reporter: aalam(a)fedoraproject.org
QA Contact: extras-qa(a)fedoraproject.org
CC: i18n-bugs(a)lists.fedoraproject.org,
kde-sig(a)lists.fedoraproject.org, me(a)dvratil.cz,
rdieter(a)gmail.com, smparrish(a)gmail.com,
than(a)redhat.com
Target Milestone: ---
Classification: Fedora
Created attachment 1735891
--> https://bugzilla.redhat.com/attachment.cgi?id=1735891&action=edit
KDE system Tray (software, Keyboard Indicator)
Description of problem:
Version-Release number of selected component (if applicable):
kde-l10n-pa-17.08.3-9.fc33.noarch
apper-1.0.0-6.fc32.x86_64
How reproducible:
every time
Steps to Reproduce:
1. translation is not available for various KDE packages
2.rpm -q kde-l10n-pa -l|grep apper||grep
rpm -q kde-l10n-pa -l|grep kdeplasma
3.
Actual results:
applications are untranslated. Various untranslated section on KDE desktop in
Punjabi
No output for file search
Expected results: 4 following files
apper._desktop_.po
apper.po
org.kde.apper.appdata.po
plasma_applet_org.packagekit.updater.po
Additional info:
KDE svn source has apper fully transalted files for Punjabi since 2011:
https://websvn.kde.org/trunk/l10n-kf5/pa/messages/apper/
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1809989
Bug ID: 1809989
Summary: By default install Noto fonts for Unicode scripts not
already covered by default
Product: Fedora
Version: 31
Status: NEW
Component: google-noto-fonts
Assignee: petersen(a)redhat.com
Reporter: hsivonen(a)hsivonen.fi
QA Contact: extras-qa(a)fedoraproject.org
CC: fonts-bugs(a)lists.fedoraproject.org,
i18n-bugs(a)lists.fedoraproject.org,
petersen(a)redhat.com, psatpute(a)redhat.com,
pwu(a)redhat.com, tagoh(a)redhat.com
Target Milestone: ---
Classification: Fedora
There is currently movement towards protecting browser users from font
fingerprinting. This means refusing, by default, to load user-installed fonts,
which makes the set of fonts that each OS installs by default even more
important than before.
Firefox bug:
https://bugzilla.mozilla.org/show_bug.cgi?id=1582687
W3C CSS WG issue:
https://github.com/w3c/csswg-drafts/issues/4497
Currently, Windows 10, macOS, Android, and Chrome OS provide broader
installed-by-default Unicode coverage than Fedora.
Examples of living scripts that have enough active users to make it to the list
at
https://en.wikipedia.org/wiki/List_of_writing_systems#List_of_writing_scrip…
but are not supported by default in Fedora 31 include Javanese, Sundanese,
Batak, Balinese, Mongolian, and New Tai Lue.
Egyptian hieroglyphs is an example of a dead script the Fedora 31 doesn't
support out of the box but Windows 10, macOS, Chrome OS, and Android do.
To remedy this with minimal disk space impact, I suggest the same approach that
Apple took. Apple bundles with macOS those Noto fonts that cover scripts that
were not already covered by the previous installed-by-default set of fonts on
macOS. In the macOS case, the on-disk footprint of the Noto fonts that were
required to take macOS to Android/Chrome OS-competitive Unicode coverage was
only a couple of megabytes. (The fonts are hidden in /Library/Application
Support/Apple/Fonts/Language Support/.) In the case of Fedora, the set of Noto
fonts required to reach the Chrome OS / Android level of script coverage is a
bit larger than in the macOS case but should still be manageable.
Please install, by default, those Noto fonts that provide support for scripts
that are not properly supported by the fonts that Fedora already installs by
default.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1832351
Bug ID: 1832351
Summary: Macintosh keyboard variants not available
Product: Fedora
Version: 32
Hardware: x86_64
Status: NEW
Component: xkeyboard-config
Severity: medium
Assignee: peter.hutterer(a)redhat.com
Reporter: mthoemme(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: ajax(a)redhat.com, caillon+fedoraproject(a)gmail.com,
i18n-bugs(a)lists.fedoraproject.org,
john.j5live(a)gmail.com, negativo17(a)gmail.com,
peter.hutterer(a)redhat.com, rhughes(a)redhat.com,
rstrode(a)redhat.com, sandmann(a)redhat.com
Target Milestone: ---
Classification: Fedora
Description of problem:
I do not have any variants for Macintosh available when trying to change the
keyboard layout via the GUI (Region & Language Settings).
Trying to manually set the keymap in the locale works for the VC keymap, but
not for the X11 Layout. It will set VC keymap to "de-mac" or "de_mac"
respectively, leave the X11 Layout at "de"
localectl set-keymap de-mac
Digging even deeper, the following commands all yield the same errors:
localectl set-x11-keymap de-mac
localectl set-x11-keymap de_mac
localectl set-x11-keymap de macintosh de_mac
All yield: "Failed to set keymap: Specified keymap cannot be compiled, refusing
as invalid."
Version-Release number of selected component (if applicable):
dnf info xkeyboard-config
Last metadata expiration check: 1:03:51 ago on Mi 06 Mai 2020 15:54:00 CEST.
Installed Packages
Name : xkeyboard-config
Version : 2.29
Release : 1.fc32
Architecture : noarch
Size : 5.5 M
Source : xkeyboard-config-2.29-1.fc32.src.rpm
Repository : @System
From repo : anaconda
Summary : X Keyboard Extension configuration data
URL : http://www.freedesktop.org/wiki/Software/XKeyboardConfig
License : MIT
Description : This package contains configuration data used by the X Keyboard
Extension (XKB),
: which allows selection of keyboard layouts when using a
graphical interface.
How reproducible:
Happens consistently. I'm on a fresh Fedora 32 install.
Steps to Reproduce:
1. localectl set-x11-keymap de macintosh de_mac
Actual results:
"Failed to set keymap: Specified keymap cannot be compiled, refusing as
invalid."
Expected results:
Successfully sets the keyboard layout to a Macintosh variant.
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=1784650
Bug ID: 1784650
Summary: Fontconfig is slow, causing stuttering and freezing
Product: Fedora
Version: 31
Status: NEW
Component: fontconfig
Severity: high
Assignee: tagoh(a)redhat.com
Reporter: bepvte+bugzilla(a)gmail.com
QA Contact: extras-qa(a)fedoraproject.org
CC: ajax(a)redhat.com, caillon+fedoraproject(a)gmail.com,
fonts-bugs(a)lists.fedoraproject.org,
gnome-sig(a)lists.fedoraproject.org,
i18n-bugs(a)lists.fedoraproject.org,
john.j5live(a)gmail.com, mclasen(a)redhat.com,
pnemade(a)redhat.com, rhughes(a)redhat.com,
rstrode(a)redhat.com, sandmann(a)redhat.com,
tagoh(a)redhat.com
Target Milestone: ---
Classification: Fedora
Description of problem:
Fontconfig is much much slower than on other distros, and it stutters or
freezes applications that use it.
Version-Release number of selected component (if applicable):
Name : fontconfig
Version : 2.13.92
Release : 3.fc31
Architecture: x86_64
How reproducible:
I can reproduce this bug on a fresh Fedora 31 vm with the Xfce desktop and
google-noto-sans-* fonts installed.
Steps to Reproduce:
1. dnf install google-noto-sans-*
2. run gedit on the attached example file
alternatively
1. dnf install google-noto-sans-*
2. open firefox and browse to https://www.wikidata.org/wiki/Q52 (page with lots
of languages)
Actual results:
It takes around 60 seconds for gedit to become responsive to scrolling and
input. Mousepad is faster but still slow.
It takes firefox upwards of 5 minutes to get to first paint on a page with many
fonts or languages, compared to a simpler page.
Expected results:
Gedit should load files with many fonts at a similar speed as other distros.
The page should load quickly, like on Debian and others.
Additional info:
I have tried to diagnose the source of this issue in many ways.
Running `perf trace` on what sysprof indicated was the most busy function
(FcStrCmpIgnoreCaseAndDelims), shows that every name of every font family is
being compared to every other name of every other font family. I do not know if
this is a normal behaviour of fontconfig.
I have noticed the amount of calls to "FcStrCmpIgnoreCaseAndDelims" and program
startup time both drop to a similar amount as Debian's when all of the
"google-noto" configuration files in /etc/fonts/conf.d/ are deleted (These
files are not present in Debian). However, this might not be the source of the
problem:
In the Debian vm, with a copy of my computer's /etc/fonts/, including the
google-noto files, (I took care to ensure that there would be no broken
symlinks) and /usr/share/fonts, fontconfig does not stall any programs. The
amount of calls to FcStrCmpIgnoreCaseAndDelims is also much lower as well.
This led me to believe that it was a difference caused by compiler flags but
this does not seem to be the case. I tried to replace the optflags in the
package, except for the rpmbuild required debug ones, and found no difference.
I also checked to ensure that it was not caused by GCC version differences.
Debian results for mousepad:
1,845,449 calls to FcStrCmpIgnoreCaseAndDelims
Time: 5 seconds
Fedora results for mousepad:
11,658,380 calls to FcStrCmpIgnoreCaseAndDelims
Time: 23 seconds
https://perfht.ml/2tleJxN
Here is a link to a Firefox profiler result of the wikidata page, where in the
flame graph you can see that Firefox is spending most of its time in
fontconfig. You can also see "FirstNonBlankPaint" is at 50 seconds in the
marker table.
TLDR: Fontconfig matching is slow with all google-noto fonts installed, unless
you remove the noto config files. Using the same exact font directory and
config directory (including the noto config files) on Debian does not cause the
same problem.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1938091
Bug ID: 1938091
Summary: Kasumi-unicode: Check for only hiragana letters in
reading column fails as user can input non-hiragana
characters in it.
Product: Fedora
Version: 34
Status: NEW
Component: kasumi
Keywords: i18n
Assignee: tagoh(a)redhat.com
Reporter: bbarve(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: i18n-bugs(a)lists.fedoraproject.org, tagoh(a)redhat.com
Target Milestone: ---
Classification: Fedora
Created attachment 1762901
--> https://bugzilla.redhat.com/attachment.cgi?id=1762901&action=edit
kasumi unicode non-hiragana letters
Description of problem: In the kasumi-unicode dict, there is a message which
pops-up if user tries to input non-hiragana characters like kanji or katakana.
However this check is not consistent as user can input other non-hiragana input
like English words, letters, numbers etc. This can be done using any mode in
Anthy like hiragana or direct input. Attaching screenshot for reference.
Version-Release number of selected component (if applicable):
Fedora 34
kasumi-unicode-2.5.33.fc34
How reproducible:
always
Steps to Reproduce:
1. Run /usr/bin/kasumi-unicode from terminal
2. click on add
3. add a jpn word in any script under first column i.e. words
4. hit tab and enter to input in the second column i.e. reading
5. In hiragana mode, input 'k' and hit enter
6. click on save.
Actual results:
user is ablke to input non-hiragana input in reading column
Expected results:
The check for non-hiragana input should be consistent.
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=1923676
Bug ID: 1923676
Summary: emacs-lookup: FTBFS in Fedora rawhide/f34
Product: Fedora
Version: rawhide
Status: NEW
Component: emacs-lookup
Assignee: dueno(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
Blocks: 1868278 (F34FTBFS)
Target Milestone: ---
Classification: Fedora
emacs-lookup failed to build from source in Fedora rawhide/f34
https://koji.fedoraproject.org/koji/taskinfo?taskID=60913717
For details on the mass rebuild see:
https://fedoraproject.org/wiki/Fedora_34_Mass_Rebuild
Please fix emacs-lookup 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,
emacs-lookup will be orphaned. Before branching of Fedora 35,
emacs-lookup 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_Fails…
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1868278
[Bug 1868278] (F34FTBFS) - Fedora 34 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=1919932
Bug ID: 1919932
Summary: Culmus Hebrew fonts aren't usable by TeXLive after
installation
Product: Fedora
Version: 33
Status: NEW
Component: culmus-fonts
Assignee: petersen(a)redhat.com
Reporter: nikita(a)leshenko.net
QA Contact: extras-qa(a)fedoraproject.org
CC: i18n-bugs(a)lists.fedoraproject.org,
petersen(a)redhat.com, pnemade(a)redhat.com,
psatpute(a)redhat.com, vishalvijayraghavan(a)gmail.com
Target Milestone: ---
Classification: Fedora
Created attachment 1750496
--> https://bugzilla.redhat.com/attachment.cgi?id=1750496&action=edit
Basic Hebrew document
Description of problem:
On a clean Fedora 33 after installing texlive, babel-hebrew, and
tex-fonts-hebrew, I
can't use pdflatex to render a Hebrew document. Detailed steps to reproduce and
a possible fix are provided below.
Version-Release number of selected component (if applicable):
texlive 9:2020-34.fc33
texlive-babel-hebrew 9:svn30273.2.3h-34.fc33
tex-fonts-hebrew 0.1-33.fc33
How reproducible: Always
Steps to Reproduce:
1. Start a new Fedora 33 container: podman run -it fedora:33
2. dnf install texlive texlive-babel-hebrew tex-fonts-hebrew
3. Try to render hello.tex document attached to this bug report (this is a
basic
Hebrew document).
\documentclass{article}
\usepackage[utf8x]{inputenc}
\usepackage[english,hebrew]{babel}
\begin{document}
שלום!
\end{document}
Actual results:
We get the following error message:
!pdfTeX error: pdflatex (file rdavid): Font rdavid at 600 not found
==> Fatal error occurred, no output PDF file produced!
Full log is at first.log.
Expected results:
Document is rendered :)
Additional info:
We need two steps to resolve the problem here. I'm not sure if these steps are
the idiomatic way to fix the issue, but it worked for me...
The first issue that that culmus.map is not included in the pdflatex.map, even
though culmus.map is enabled in /etc/texlive/web2c/updmap.cfg. I was able to
solve it with
- updmap-sys --syncwithtrees
- updmap-sys
to recreate the map file. It would be nice the Culmus will do this by default
as
part of the installation. (Another temporary per-document solution is to add
\pdfmapfile{culmus.map} to the Hebrew document.)
Now if we re-run pdflatex we get a new error:
!pdfTeX error: pdflatex (file DavidCLM-Medium.pfa): cannot open Type 1 font
file for reading
==> Fatal error occurred, no output PDF file produced!
The full log is in second.log.
There are multiple ways around this problem:
1. Note that /usr/share/texmf/fonts/type1/public/ has a broken symlink to
culmus. Even if we fix the symlink to point to /usr/share/fonts/culmus/, it
doesn't work because pdflatex doesn't seem to follow directory symlinks. But
if we actually create a directory and symlink fonts individually, it will
work, like this:
mkdir /usr/share/texmf/fonts/type1/public/culmus2
for i in /usr/share/fonts/culmus/*; do ln $i
/usr/share/texmf/fonts/type1/public/culmus2/${i##*/}; done
2. A more "general" fix is to edit /etc/texlive/web2c/texmf.cnf instead and set
OSFONTDIR to /usr/share/fonts/, but it seems like this change extends beyond
Culmus so I'm not sure how practical is it to edit OSFONTDIR as part of
installation.
After building the map file and teaching latex to find Type1 Culmus fonts the
Hebrew document can compile successfully.
I hope that it will be possible to adjust the Culmus package so that Hebrew
latex works out of the box.
Thanks! I'm available for questions and clarifications.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1934320
Bug ID: 1934320
Summary: Led indicator of FnLock doesnot work...on 15ARH05H
Product: Fedora
Version: 33
Hardware: x86_64
OS: Linux
Status: NEW
Component: xkeyboard-config
Severity: medium
Assignee: peter.hutterer(a)redhat.com
Reporter: saurab.gyawali032(a)gmail.com
QA Contact: extras-qa(a)fedoraproject.org
CC: ajax(a)redhat.com, caillon+fedoraproject(a)gmail.com,
i18n-bugs(a)lists.fedoraproject.org,
negativo17(a)gmail.com, peter.hutterer(a)redhat.com,
rhughes(a)redhat.com, rstrode(a)redhat.com,
sandmann(a)redhat.com
Target Milestone: ---
Classification: Fedora
Description of problem:My Fn + Esc key activates the FNLOCK key which has a led
indicator in it but it either remain on or off on its own..... While booting if
it is on it remain on all the time and viceversa.......
I just want to make this correct....While hitting Fn +Ecs can you help me to
make the led indicator responsive
Version-Release number of selected component (if applicable): I don't know
anything
How reproducible:
Steps to Reproduce:
1.
2.
3.
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=1815510
Bug ID: 1815510
Summary: Input hangul -> cursor becomes ahead in preedit
Product: Fedora
Version: 32
Hardware: x86_64
OS: Linux
Status: NEW
Component: ibus-hangul
Assignee: pwu(a)redhat.com
Reporter: sangu.fedora(a)gmail.com
QA Contact: extras-qa(a)fedoraproject.org
CC: i18n-bugs(a)lists.fedoraproject.org, pwu(a)redhat.com,
shawn.p.huang(a)gmail.com, tfujiwar(a)redhat.com
Target Milestone: ---
Classification: Fedora
Description of problem:
Input hangul -> cursor becomes ahead in preedit
Version-Release number of selected component (if applicable):
1.5.3-2.fc32.x86_64
How reproducible:
always in haungul input state
Steps to Reproduce:
1. gedit starts
2. switch hangul
3. input hangul
Actual results:
Expected results:
Additional info:
ibus-1.5.22-4.fc32.x86_64
gtk3-3.24.14-1.fc32.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=1851919
Bug ID: 1851919
Summary: Pango 1.45 crashes pidgin with any link click
Product: Fedora
Version: rawhide
Status: NEW
Component: pango
Assignee: pwu(a)redhat.com
Reporter: zkabelac(a)redhat.com
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,
john.j5live(a)gmail.com, mclasen(a)redhat.com,
pwu(a)redhat.com, rhughes(a)redhat.com,
rstrode(a)redhat.com, sandmann(a)redhat.com,
tagoh(a)redhat.com
Target Milestone: ---
Classification: Fedora
Description of problem:
I've noticed instant crash of a pidgin - with this new pango 1.45 package.
I've downgraded to version pango-1.44.7-3.fc33 and pidgin is 'usable'
again (aka I can click on URL without getting instant core dump).
This is backtrace I'm getting on a crash:
(pidgin 2.13.0-20)
#0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:49
--Type <RET> for more, q to quit, c to continue without paging--
49 return ret;
[Current thread is 1 (Thread 0x7f2b86c61cc0 (LWP 100183))]
(gdb) bt
#0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:49
#1 0x00007f2b883a78a4 in __GI_abort () at abort.c:79
#2 0x00007f2b886d5b6c in g_assertion_message
(domain=<optimized out>, file=0x7f2b88b7e19b "../pango/pango-context.c",
line=<optimized out>, func=<optimized out>, message=<optimized out>) at
../glib/gtestutils.c:2930
#3 0x00007f2b8873408f in g_assertion_message_expr
(domain=0x7f2b88b79e0d "Pango", file=0x7f2b88b7e19b
"../pango/pango-context.c", line=1435, func=0x7f2b88b7e3d0
"itemize_state_process_run", expr=<optimized out>) at ../glib/gtestutils.c:2956
#4 0x00007f2b88b603d6 in itemize_state_process_run () at
/lib64/libpango-1.0.so.0
#5 0x00007f2b88b61218 in pango_itemize_with_base_dir () at
/lib64/libpango-1.0.so.0
#6 0x00007f2b88b6a695 in pango_layout_check_lines.part () at
/lib64/libpango-1.0.so.0
#7 0x00007f2b88b6c539 in pango_layout_get_extents_internal () at
/lib64/libpango-1.0.so.0
#8 0x00007f2b88b6cac1 in pango_layout_get_pixel_size () at
/lib64/libpango-1.0.so.0
#9 0x000056100c9047f1 in gtk_imhtml_tip ()
#10 0x00007f2b8870ba51 in g_timeout_dispatch
(source=source@entry=0x56100ec326c0, callback=0x56100c9045b0
<gtk_imhtml_tip>, user_data=0x56100d93c2b0)
at ../glib/gmain.c:4800
#11 0x00007f2b8870aeaf in g_main_dispatch (context=0x56100d287540) at
../glib/gmain.c:3309
#12 g_main_context_dispatch (context=0x56100d287540) at ../glib/gmain.c:3974
#13 0x00007f2b8870b238 in g_main_context_iterate
(context=0x56100d287540, block=block@entry=1, dispatch=dispatch@entry=1,
self=<optimized out>)
at ../glib/gmain.c:4047
#14 0x00007f2b8870b553 in g_main_loop_run (loop=0x56100ea147e0) at
../glib/gmain.c:4241
#15 0x00007f2b88f37ba2 in gtk_main () at /lib64/libgtk-x11-2.0.so.0
#16 0x000056100c8bdb4c in main ()
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1888536
Bug ID: 1888536
Summary: Wrong shape in U+300D
Product: Fedora
Version: 33
Status: NEW
Component: sil-nuosu-fonts
Assignee: pwu(a)redhat.com
Reporter: tagoh(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: eng-i18n-bugs(a)redhat.com,
i18n-bugs(a)lists.fedoraproject.org, kent.neo(a)gmail.com,
petersen(a)redhat.com, pwu(a)redhat.com,
qe-i18n-bugs(a)redhat.com
Depends On: 1762623
Target Milestone: ---
Classification: Fedora
+++ This bug was initially created as a clone of Bug #1762623 +++
Description of problem:
The short horizontal line must be at the bottom but currently it is at the top.
see attached and the legend in fontforge say.
Version-Release number of selected component (if applicable):
sil-nuosu-fonts-2.1.1-14.el8.noarch
How reproducible:
always
Steps to Reproduce:
1.see U+300D (」)
2.
3.
Actual results:
Expected results:
Additional info:
--- Additional comment from Akira TAGOH on 2019-10-17 05:43:53 UTC ---
--- Additional comment from Peng Wu on 2019-10-18 08:42:28 UTC ---
Okay, sent an message to Nuosu SIL upstream.
URL: https://software.sil.org/nuosu/#contact
--- Additional comment from Peng Wu on 2019-10-22 05:00:45 UTC ---
They replied they will fix it when next release.
But the next release may be some months later, not decided yet.
--- Additional comment from Jens Petersen on 2020-06-05 10:36:54 UTC ---
Not sure if there is any update on this yet?
--- Additional comment from Peng Wu on 2020-06-08 04:00:25 UTC ---
From https://software.sil.org/nuosu/ , it seems no updates.
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1762623
[Bug 1762623] Wrong shape in U+300D
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1930214
Bug ID: 1930214
Summary: Please retire man-pages-es
Product: Fedora
Version: rawhide
Status: NEW
Component: man-pages-es
Severity: high
Assignee: domingobecker(a)gmail.com
Reporter: nforro(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: domingobecker(a)gmail.com,
i18n-bugs(a)lists.fedoraproject.org, mfabian(a)redhat.com,
peter(a)thecodergeek.com
Target Milestone: ---
Link ID: Red Hat Bugzilla 1925829,Red Hat Bugzilla 1929938
Classification: Fedora
Updated Spanish translation of man pages now exists as part of manpages-l10n
project [1], which is already packaged in Fedora [2].
Could you please retire man-pages-es package so that it can be replaced with
updated translations from man-pages-l10n?
[1] https://manpages-l10n-team.pages.debian.net/manpages-l10n/
[2] https://src.fedoraproject.org/rpms/man-pages-l10n
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1659748
Bug ID: 1659748
Summary: Characters get deleted as you type
Product: Fedora
Version: 29
Status: NEW
Component: ibus-m17n
Severity: high
Assignee: pnemade(a)redhat.com
Reporter: lohang(a)gmail.com
QA Contact: extras-qa(a)fedoraproject.org
CC: i18n-bugs(a)lists.fedoraproject.org, pnemade(a)redhat.com,
shawn.p.huang(a)gmail.com
Target Milestone: ---
Classification: Fedora
Description of problem:
When you type Sinhala using Wijesekera keyboard layout through ibus the first
character gets deleted as soon as you start typing the second character. This
is similar to the bug previously reported for Fedora 28
https://bugzilla.redhat.com/show_bug.cgi?id=1617978
How reproducible:
(1) Steps to Reproduce:
1. Open Libre Office Writer (6.1.2.1)
2. Switch to Sinhala; Sinhalese (wijesekera (m17n))
3. Type keys vksIal kjSka
4. Hit space to separate the second word from the first word. And hit space at
the end of the first word.
Actual results: ක වීන්
Expected results: ඩනිෂ්ක නවීන්
Additional info:
(2) When you try this with emacs the results are a little different. I am
including it here assuming this is related to the same issue:
This is how to reproduce with emacs:
1. Open emacs 26.1 (build 1, x86_64-redhat-linux-gnu, GTK+ Version 3.23.2)
of 2018-08-13
2. Switch to Sinhala; Sinhalese (wijesekera (m17n))
3. Type keys vksIal kjSka
4. Hit space to separate the second word from the first word. And hit space at
the end of the first word.
Actual results: ඩනිෂ් කනවී න්
Expected results: ඩනිෂ්ක නවීන්
This adds a space before the last character of the first word, not where you
want the space to be.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1786596
Bug ID: 1786596
Summary: Vertical alignment is off with PANGO_GRAVITY_EAST and
PANGO_GRAVITY_HINT_LINE
Product: Fedora
Version: 31
OS: Linux
Status: NEW
Component: pango
Assignee: pwu(a)redhat.com
Reporter: abetakehiko(a)gmail.com
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,
john.j5live(a)gmail.com, mclasen(a)redhat.com,
pwu(a)redhat.com, rhughes(a)redhat.com,
rstrode(a)redhat.com, sandmann(a)redhat.com,
tagoh(a)redhat.com
Target Milestone: ---
Classification: Fedora
Description of problem:
Japanese chars and Latin chars in the same line do not vertically align when
the pango context's gravity is set to PANGO_GRAVITY_EAST and its hint set to
PANGO_GRAVITY_HINT_LINE.
Version-Release number of selected component (if applicable):
pango-1.44.7-1.fc31.x86_64
How reproducible:
Always
Steps to Reproduce:
pango-view --text="あーいうえお abcde" --gravity east --gravity-hint line
--font="NotoSerifJP 24"
Actual results:
Japanese chars and Latin chars in the same line do not vertically align.
Expected results:
Japanese chars and Latin chars in the same line vertically align as before.
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=1677534
Bug ID: 1677534
Summary: texttopaps OOMs with 4GB text file!
Product: Fedora
Version: rawhide
Hardware: x86_64
OS: Linux
Status: NEW
Component: paps
Severity: high
Assignee: tagoh(a)redhat.com
Reporter: petersen(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: desktop-qa-list(a)redhat.com, eng-i18n-bugs(a)redhat.com,
i18n-bugs(a)lists.fedoraproject.org, rhel(a)vlasiu.net,
tagoh(a)redhat.com
Depends On: 1635160
Target Milestone: ---
Classification: Fedora
(Cloned from a RHEL7 report)
+++ This bug was initially created as a clone of Bug #1635160 +++
Description of problem:
Trying to print with cups a 4Gb text file fail.
texttopaps consume all the memory and is killed bye the system:
[1023082.003989] Out of memory: Kill process xxxx (texttopaps) score 955 or
sacrifice child
[1023082.005120] Killed process xxxx (texttopaps) total-vm:19958848kB,
anon-rss:7531872kB, file-rss:84kB, shmem-rss:0kB
/usr/lib/cups/filter/texttopaps 1 user1 "example" 1 "" sample-4Gb.txt
--- Additional comment from Akira TAGOH on 2018-10-03 11:54:48 SGT ---
Hmm, that log says it all. I don't think OOM is a software bug.
--- Additional comment from GV on 2018-10-03 13:00:48 SGT ---
Of course OOM is not a software bug. Where exactly did I said that?
The problem is texttopaps that allocate memory out of control.
texttopaps should allocate memory, use-it, release-it. Like any sane program.
The issue was not present on RHEL 6. I had printed the same file multiple times
with cups on RHEL6 and it worked just fine (not sure it was texttopaps cups
filter involved). Printing the file does not work on RHEL 7 and it should.
The 4Gb file is a testcase for our application we develop.
--- Additional comment from Jens Petersen on 2018-10-18 17:49:35 SGT ---
I don't think the paps in RHEL7 is significantly different from RHEL6.
As you say it could be due to changes in Cups?
The cups versions in RHEL 6, 7 and Fedora are certainly quite different.
Unless texttopaps really worked in RHEL6 it might make to reassign this to
cups?
--- Additional comment from GV on 2018-10-25 18:29:46 SGT ---
Since the real computer running RHEL 6 was already scrapped, I tried to make a
virtual machine using RHEL 6. Unfortunately, now I also get a crash on RHEL 6
when printing the 4GB file. I can't recall how much memory was in that
computer. The virtual machine had 8Gb of memory allocated.
Still, it does not matter that much.
I think texttopaps have an issue and it should be fixed or at least an
workaround should be available (other than 'don't print a file that large').
I'm afraid this is not a cups issue since I can reproduce the issue running the
texttopaps standalone.
Sincerely,
Gabriel
--- Additional comment from Akira TAGOH on 2018-11-16 17:59:04 SGT ---
paps isn't supposed to work with large files. to support it, most of code needs
to rewritten. this isn't realistic to provide an update for existing products.
for a workaround, you can remove paps package (or simply remove
/usr/share/cups/mime/paps.convs file) to fall back the text filter to texttops
which CUPS originally provides. this should works for this issue and as long as
you don't need the internationalization support for printing.
Hope that helps.
--- Additional comment from GV on 2018-12-07 14:03:33 SGT ---
It helps. Thank you!
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1635160
[Bug 1635160] texttopaps OOMs with 4GB text file!
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1943000
Bug ID: 1943000
Summary: emacs-lookup: FTBFS with upcoming autoconf-2.71
Product: Fedora
Version: rawhide
Status: NEW
Component: emacs-lookup
Assignee: dueno(a)redhat.com
Reporter: odubaj(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: dueno(a)redhat.com, i18n-bugs(a)lists.fedoraproject.org
Blocks: 1942967
Target Milestone: ---
Classification: Fedora
Your package fails to build with the newest upcoming autoconf-2.71, which is
part of a wide Fedora change. Please see the attached copr:
https://copr.fedorainfracloud.org/coprs/odubaj/autoconf-2.70/packages/. More
information about testing your package when building with autoconf available
here: https://fedoraproject.org/wiki/Changes/Autoconf_271#How_To_Test
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1942967
[Bug 1942967] FTBFS with upcoming autoconf-2.71
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1951861
Bug ID: 1951861
Summary: switch to using %transfiletriggerin for updating ibus
cache
Product: Fedora
Version: rawhide
Status: NEW
Component: ibus
Assignee: tfujiwar(a)redhat.com
Reporter: petersen(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:
Rather than having each ibus engine update in a dnf transaction
running ibus write-cache --system twice (%post and %postun) or once
separately in %posttrans, it would be better to do it centrally
from ibus.spec using a file trigger on "/usr/share/ibus/component".
I think you tested it locally once and I believe it should work well enough.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1832098
Bug ID: 1832098
Summary: Due to socket path changes ibus not working in F32
Wayland for qt4 apps
Product: Fedora
Version: 32
Status: NEW
Component: ibus-qt
Severity: high
Assignee: tfujiwar(a)redhat.com
Reporter: petersen(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:
Due to changes in socket path for Wayland,
ibus input does not work for qt4 apps under Wayland in Fedora 32.
https://github.com/ibus/ibus-qt/pull/5
Version-Release number of selected component (if applicable):
ibus-qt-1.3.3-22.fc31
How reproducible:
100%
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1836327
Bug ID: 1836327
Summary: Hangul text commit and key forward don't preserve
order sometimes
Product: Fedora
Version: 32
Hardware: x86_64
OS: Linux
Status: NEW
Component: ibus
Severity: medium
Assignee: tfujiwar(a)redhat.com
Reporter: edward.park0203(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
Description of problem:
Hangul text commit and key forward don't preserve order sometimes
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
--
You are receiving this mail because:
You are on the CC list for the bug.