[Fedora-i18n-bugs] [Bug 1677534] New: texttopaps OOMs with 4GB text file!
by bugzilla＠redhat.com
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.
1 month
[Fedora-i18n-bugs] [Bug 1919932] New: Culmus Hebrew fonts aren't usable by TeXLive after installation
by bugzilla＠redhat.com
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.
1 month, 2 weeks
[Fedora-i18n-bugs] [Bug 1836327] New: Hangul text commit and key forward don't preserve order sometimes
by bugzilla＠redhat.com
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.
2 months
[Fedora-i18n-bugs] [Bug 1753295] New: Pango no longer supports bitmap fonts
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1753295
Bug ID: 1753295
Summary: Pango no longer supports bitmap fonts
Product: Fedora
Version: 31
Status: NEW
Component: pango
Assignee: tagoh(a)redhat.com
Reporter: jsbillin(a)umich.edu
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:
In pango 1.44, pango dropped support for bitmap fonts, so font packages like
terminus-fonts and ucs-miscfixed-fonts no longer appear in GNOME applications
that use pango, such as Terminal. If you did a dnf system-upgrade from Fedora
30 and were using a bitmap font like Terminus, all your terminals will show the
rectangular placeholders the first time you start a terminal.
Bitmap fonts like terminus and ucs-miscfixed are much easier to read in a
terminal since they are pixel perfect. If Fedora 31 is going to disable
support for bitmap fonts, it needs to be announced and the package maintainers
of those bitmap font packages are going to need to find a way to convert their
fonts.
Version-Release number of selected component (if applicable):
pango-1.44.6-1.fc31.x86_64
How reproducible:
always
Steps to Reproduce:
1. install 'terminus-fonts'
2. Start GNOME terminal
3. Open Terminal Preferences
4. Attempt to change the font to Terminus font
Actual results:
If you upgraded from Fedora 30 and had Terminus fonts as the default font, the
first time you launch Terminal, all the text will be the rectangular
placeholders. If you search for the Terminus font in the preferences, you
won't be able to find it.
Expected results:
Use the Terminus font as usual
Additional info:
It appears that pango switched from using FreeType to HarfBuzz, which only
supports truetype. I rebuilt the Fedora 30 pango package (1.43) for Fedora 31,
downgraded it, and now my terminals are fine showing my bitmap fonts.
--
You are receiving this mail because:
You are on the CC list for the bug.
2 months
[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.
2 months, 1 week
[Fedora-i18n-bugs] [Bug 1925030] New: [ibus-typing-booster] In gnome Wayland, while deleting with backspace, previously entered keywords appear repetitively in gedit.
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1925030
Bug ID: 1925030
Summary: [ibus-typing-booster] In gnome Wayland, while deleting
with backspace, previously entered keywords appear
repetitively in gedit.
Product: Red Hat Enterprise Linux 8
Version: 8.4
Hardware: All
OS: Linux
Status: NEW
Component: ibus-typing-booster
Keywords: i18n
Severity: medium
Priority: medium
Assignee: mfabian(a)redhat.com
Reporter: bbarve(a)redhat.com
QA Contact: qe-i18n-bugs(a)redhat.com
CC: anish.developer(a)gmail.com, bbarve(a)redhat.com,
eng-i18n-bugs(a)redhat.com, extras-qa(a)fedoraproject.org,
i18n-bugs(a)lists.fedoraproject.org, mfabian(a)redhat.com
Depends On: 1637647
Target Milestone: rc
Classification: Red Hat
Pool ID: sst_i18n_rhel_8
Cloning the Fedora bug for RHEL 8.4 flatpak only. This works as expected with
default gedit app. For flatpak i.e. org.gnome.gedit, the deletion shows
previously entered input.
Here is the version information -
flatpak-1.8.5-2.el8.x86_64
gedit org.gnome.gedit 3.38.0 stable
+++ This bug was initially created as a clone of Bug #1637647 +++
Description of problem: Observed with wayland. Entered a sentence in gedit.
After full stop, entered one more word. When tried deleting that keyword,
observed that, after deletion, all the previously entered keywords in the last
sentence were also appearing at the time of hitting backspace. Please see the
attached screen-cast for reproducer. This is observed with gedit. Works as
expected with gnome-terminal, oowriter etc.
Version-Release number of selected component (if applicable):
F29 workstation(2018-10-08)
[test@localhost ~]$ rpm -qa ibus-typing-booster
ibus-typing-booster-2.1.2-1.fc29.noarch
[test@localhost ~]$ rpm -qa ibus
ibus-1.5.19-4.fc29.x86_64
[test@localhost ~]$ rpm -qa gedit
gedit-3.30.1-2.fc29.x86_64
How reproducible:
always
Steps to Reproduce:
1. as above.
2.
3.
Actual results:
While deleting with backspace, previously entered words are showing up
repetitively.
Expected results:
Backspace should delete the whole sentence without showing it repetitively.
Additional info:
This works fine with xorg.
--- Additional comment from Bhushan Barve on 2018-10-09 16:23:04 UTC ---
--- Additional comment from Mike FABIAN on 2018-10-10 06:10:09 UTC ---
It works correctly in gedit in Gnome Xorg.
So this seems to be a problem in the surrounding text support in Gnome Wayland.
--- Additional comment from Mike FABIAN on 2018-10-10 06:15:20 UTC ---
See also: https://bugzilla.redhat.com/show_bug.cgi?id=1625626
--- Additional comment from Mike FABIAN on 2019-04-03 12:42:53 UTC ---
The bug still exists in Fedora 30.
--- Additional comment from Mike FABIAN on 2019-12-03 07:56:32 UTC ---
The bug still exists in Fedora 31.
--- Additional comment from Fedora Update System on 2020-02-27 18:20:33 UTC ---
FEDORA-2020-049620fad5 has been submitted as an update to Fedora 32.
https://bodhi.fedoraproject.org/updates/FEDORA-2020-049620fad5
--- Additional comment from Fedora Update System on 2020-02-27 18:22:15 UTC ---
FEDORA-2020-6ab69e189f has been submitted as an update to Fedora 31.
https://bodhi.fedoraproject.org/updates/FEDORA-2020-6ab69e189f
--- Additional comment from Fedora Update System on 2020-02-27 18:25:14 UTC ---
FEDORA-2020-f5d026d0c5 has been submitted as an update to Fedora 30.
https://bodhi.fedoraproject.org/updates/FEDORA-2020-f5d026d0c5
--- Additional comment from Fedora Update System on 2020-02-28 01:27:35 UTC ---
ibus-typing-booster-2.8.1-1.fc32 has been pushed to the Fedora 32 testing
repository. If problems still persist, please make note of it in this bug
report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-2020-049620fad5
--- Additional comment from Fedora Update System on 2020-02-29 03:11:33 UTC ---
ibus-typing-booster-2.8.1-1.fc31 has been pushed to the Fedora 31 testing
repository. If problems still persist, please make note of it in this bug
report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-2020-6ab69e189f
--- Additional comment from Fedora Update System on 2020-02-29 03:59:53 UTC ---
ibus-typing-booster-2.8.1-1.fc30 has been pushed to the Fedora 30 testing
repository. If problems still persist, please make note of it in this bug
report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-2020-f5d026d0c5
--- Additional comment from Fedora Update System on 2020-03-08 00:08:26 UTC ---
ibus-typing-booster-2.8.1-1.fc30 has been pushed to the Fedora 30 stable
repository. If problems still persist, please make note of it in this bug
report.
--- Additional comment from Fedora Update System on 2020-03-08 00:51:06 UTC ---
ibus-typing-booster-2.8.1-1.fc31 has been pushed to the Fedora 31 stable
repository. If problems still persist, please make note of it in this bug
report.
--- Additional comment from Fedora Update System on 2020-03-16 20:17:05 UTC ---
ibus-typing-booster-2.8.1-1.fc32 has been pushed to the Fedora 32 stable
repository. If problems still persist, please make note of it in this bug
report.
--- Additional comment from Fedora Update System on 2020-03-16 20:29:46 UTC ---
ibus-typing-booster-2.8.1-1.fc32 has been pushed to the Fedora 32 stable
repository. If problems still persist, please make note of it in this bug
report.
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1637647
[Bug 1637647] [ibus-typing-booster] In gnome Wayland, while deleting with
backspace, previously entered keywords appear repetitively in gedit.
--
You are receiving this mail because:
You are on the CC list for the bug.
2 months, 1 week
[Fedora-i18n-bugs] [Bug 1790554] New: Keyboard layout of Kana Kanji wont show up
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1790554
Bug ID: 1790554
Summary: Keyboard layout of Kana Kanji wont show up
Product: Fedora
Version: rawhide
Hardware: x86_64
Status: NEW
Component: ibus
Assignee: tfujiwar(a)redhat.com
Reporter: sumukher(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:
The keyboard layout for Kana Kanji Japanese doesnt show up
Version-Release number of selected component (if applicable):
Fedora-Rawhide-20200112.n.0
How reproducible:
Everytime
Steps to Reproduce:
1. Install Fedora-Rawhide-20200112.n.0 WS from live boot
2. Open settings and navigate to Region and Language
3. Add Japanese Kana Kanji in the input source
4. Click the icon looking like an eye button which should open the keyboard
layout
Actual results:
Doesn't show up the keyboard layout
Expected results:
The keyboard layout should show up like it shows up for english
Additional info:
--
You are receiving this mail because:
You are on the CC list for the bug.
2 months, 1 week
