[Fedora-i18n-bugs] [Bug 1786596] New: Vertical alignment is off with PANGO_GRAVITY_EAST and PANGO_GRAVITY_HINT_LINE
by bugzilla＠redhat.com
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.
2 years, 8 months
[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.
2 years, 10 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 years, 11 months
[Fedora-i18n-bugs] [Bug 1711646] New: Scriptlet error when updating through SSH
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1711646
Bug ID: 1711646
Summary: Scriptlet error when updating through SSH
Product: Fedora
Version: 30
Status: NEW
Component: ibus
Assignee: tfujiwar(a)redhat.com
Reporter: dreua(a)posteo.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
Description of problem:
When I update or reinstall ibus-1.5.20-4.fc30 over SSH, dnf outputs the error
"X11 connection rejected because of wrong authentication.".
This is caused by
https://src.fedoraproject.org/rpms/ibus/blob/master/f/ibus.spec#_338
running `sudo ibus write-cache --system` results in the same error when called
over SSH.
Version-Release number of selected component (if applicable):
ibus-1.5.20-4.fc30
How reproducible:
Always over SSH, never when using the terminal directly on the machine.
Steps to Reproduce:
1. Reinstall or update to ibus-1.5.20-4.fc30
Actual results:
Running scriptlet: ibus-1.5.20-4.fc30.x86_64
X11 connection rejected because of wrong authentication.
X11 connection rejected because of wrong authentication.
Verifying : ibus-1.5.20-4.fc30.x86_64
Expected results:
Running scriptlet: ibus-1.5.20-4.fc30.x86_64
Verifying : ibus-1.5.20-4.fc30.x86_64
--
You are receiving this mail because:
You are on the CC list for the bug.
2 years, 11 months
[Fedora-i18n-bugs] [Bug 1749943] New: pango contain header with wrong hb.h include
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1749943
Bug ID: 1749943
Summary: pango contain header with wrong hb.h include
Product: Fedora
Version: rawhide
Status: NEW
Component: pango
Assignee: tagoh(a)redhat.com
Reporter: vascom2(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:
I am try to build eiskaltdcpp and it fsilrd with error:
BUILDSTDERR: /usr/include/pango-1.0/pango/pango-coverage.h:28:10: fatal error:
hb.h: No such file or directory
BUILDSTDERR: 28 | #include <hb.h>
BUILDSTDERR: | ^~~~~~
Full build log
https://kojipkgs.fedoraproject.org/work/tasks/5226/37235226/build.log
Version-Release number of selected component (if applicable):
pango-1.44.6-1.fc32
How reproducible:
Always.
As I see this line was added in pango 1.44. But harfbuzz's hb.h in Fedora
placed at /usr/include/harfbuzz/
Need to solve it for build other packages.
--
You are receiving this mail because:
You are on the CC list for the bug.
3 years, 1 month
[Fedora-i18n-bugs] [Bug 1807534] New: pyzy requires Python 2 to build
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1807534
Bug ID: 1807534
Summary: pyzy requires Python 2 to build
Product: Fedora
Version: rawhide
Status: NEW
Component: pyzy
Assignee: pwu(a)redhat.com
Reporter: pviktori(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: i18n-bugs(a)lists.fedoraproject.org,
petersen(a)redhat.com, pwu(a)redhat.com
Blocks: 1803205 (BRPY27)
Target Milestone: ---
Classification: Fedora
Python 2 reached upstream end-of-life in January 2020. In Fedora Rawhide, it's
now provided from the compat package `python27`.
Packages that only use Python 2 at build time, like pyzy, had a general
exception to keep using it in Fedora 31. Now, the dependency should be removed.
Let us know if you need any help investigating or removing the dependency.
(There are dozens of packages like this, so we didn't investigate this one
thoroughly. We assume you know the package best.)
If it's possible that the dependency won't be removed in Fedora 33. Please
request a FESCo exception. You can refer to the exception for mercurial as an
example: https://pagure.io/fesco/issue/2243
It's good to mention:
- What is the reason for the Python 2 build dependency?
- What are the upstream/community plans/timelines regarding Python 2?
- What is the guidance for porting the build to Python 3? (Assuming that there
is someone who generally knows how to port to Python 3, but doesn't know
anything about the particular package, what are the next steps to take?)
If you need anything from us, or something is unclear, please mention it here.
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1803205
[Bug 1803205] Tracking: Packages BuildRequiring python27
--
You are receiving this mail because:
You are on the CC list for the bug.
3 years, 3 months
[Fedora-i18n-bugs] [Bug 1707001] New: Ibus-pinyin ERROR
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1707001
Bug ID: 1707001
Summary: Ibus-pinyin ERROR
Product: Fedora
Version: 30
Hardware: All
OS: Linux
Status: NEW
Component: ibus-pinyin
Severity: urgent
Assignee: pwu(a)redhat.com
Reporter: 1990konger(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:
The input method is incorrect and cannot be recognized correctly. The text to
be entered is required.
For example, 'nihao' should be right, '你好'.
Now enter 'nihao' to show 'niha o'.Unrecognized what you need
'ni' is a word.
'hao' is a word.
'ha' is a word but the display is wrong at this time and cannot be selected.
Unable to recognize 'hao'. Affect all input suggestions to withdraw to the old
version
Version-Release number of selected component (if applicable):
Name : ibus-pinyin
Version : 1.5.0
Release : 16.fc30
How reproducible:
'nihao' is meaning is 'Hello'
'niha o', it is an error
Steps to Reproduce:
1.All Chinese input is wrong
Additional info:
--
You are receiving this mail because:
You are on the CC list for the bug.
3 years, 3 months
[Fedora-i18n-bugs] [Bug 1787190] New: Windows+ Space shortcut opened KRunner instead of switch keyboard (ibus) in KDE plasma
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1787190
Bug ID: 1787190
Summary: Windows+ Space shortcut opened KRunner instead of
switch keyboard (ibus) in KDE plasma
Product: Fedora
Version: 31
Status: NEW
Component: kf5-plasma
Keywords: i18n
Assignee: me(a)dvratil.cz
Reporter: aalam(a)fedoraproject.org
QA Contact: extras-qa(a)fedoraproject.org
CC: i18n-bugs(a)lists.fedoraproject.org,
jgrulich(a)redhat.com, kde-sig(a)lists.fedoraproject.org,
me(a)dvratil.cz, rdieter(a)gmail.com, than(a)redhat.com
Target Milestone: ---
Classification: Fedora
Description of problem:
after updating KDE with Fedora 31, Windows+Space is opening 'Krunner', but not
switching keyboard (which is default shortcut for ibus keybaord switch).
Krunner is not running with Alt+F2
Krunner is running with Windows +F2
Version-Release number of selected component (if applicable):
plasma-desktop-5.17.4-1.fc31.x86_64
plasma-nm-openswan-5.17.4-1.fc31.x86_64
plasma-desktop-doc-5.17.4-1.fc31.noarch
plasma-browser-integration-5.17.4-1.fc31.x86_64
plasma-workspace-5.17.4-1.fc31.x86_64
plasma-nm-vpnc-5.17.4-1.fc31.x86_64
plasma-workspace-common-5.17.4-1.fc31.x86_64
plasma-nm-5.17.4-1.fc31.x86_64
plasma-workspace-geolocation-5.17.4-1.fc31.x86_64
plasma-milou-5.17.4-1.fc31.x86_64
plasma-integration-5.17.4-1.fc31.x86_64
plasma-discover-5.17.4-1.fc31.x86_64
plasma-nm-openvpn-5.17.4-1.fc31.x86_64
plasma-breeze-5.17.4-1.fc31.x86_64
plasma-drkonqi-5.17.4-1.fc31.x86_64
kdeplasma-addons-5.17.4-1.fc31.x86_64
plasma-user-manager-5.17.4-1.fc31.x86_64
plasma-pk-updates-0.3.2-4.fc31.x86_64
plasma-nm-l2tp-5.17.4-1.fc31.x86_64
plasma-nm-openconnect-5.17.4-1.fc31.x86_64
kf5-plasma-5.64.0-1.fc31.x86_64
plasma-workspace-geolocation-libs-5.17.4-1.fc31.x86_64
plasma-lookandfeel-fedora-5.17.4-1.fc31.noarch
plasma-nm-pptp-5.17.4-1.fc31.x86_64
plasma-workspace-libs-5.17.4-1.fc31.x86_64
plasma-systemsettings-5.17.4-1.fc31.x86_64
kde-settings-plasma-31.0-1.fc31.noarch
glibc-2.30-8.fc31.x86_64
glibc-langpack-pa-2.30-8.fc31.x86_64
glibc-langpack-en-2.30-8.fc31.x86_64
glibc-all-langpacks-2.30-8.fc31.x86_64
glibc-common-2.30-8.fc31.x86_6
ibus-setup-1.5.21-5.fc31.noarch
ibus-gtk3-1.5.21-5.fc31.x86_64
ibus-m17n-1.4.1-3.fc31.x86_64
ibus-gtk2-1.5.21-5.fc31.x86_64
ibus-qt-1.3.3-22.fc31.x86_64
ibus-libs-1.5.21-5.fc31.x86_64
ibus-1.5.21-5.fc31.x86_64
How reproducible:
Everytime after updating Fedora 31 KDE desktop with latest package
Steps to Reproduce:
1. Fresh install KDE Plasma with language (Punjabi, Hindi, any language using
iBus)
2. try to input by switching keyboard (ibus) pressing Windows+Space
3. sudo dnf update
4. Reboot
5. try to input by switching keyboard (ibus) pressing Windows+Space
Actual results:
Opened 'KRunner'
Expected results:
input keyboard layout should switch with 'Windows+space'.
Krunner should run with 'Alt+F2', which is not working
Additional info:
before updating, opened system setting -> Shortcut -> Global Shortcut - There
is NO krunner'
After update, system setting -> Shortcut -> Global Shortcut -> Krunner (this is
something new)
--
You are receiving this mail because:
You are on the CC list for the bug.
3 years, 5 months
[Fedora-i18n-bugs] [Bug 1703849] New: [pango] pango-view fails for backend ft2 because of missing dependency on ImageMagick
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1703849
Bug ID: 1703849
Summary: [pango] pango-view fails for backend ft2 because of
missing dependency on ImageMagick
Product: Fedora
Version: 29
Hardware: x86_64
OS: Linux
Status: NEW
Component: pango
Assignee: tagoh(a)redhat.com
Reporter: jfrieben(a)hotmail.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:
Using pango-view with backend ft2 in a current Fedora 29 Workstation
installation fails because pango-view tries to launch the display utility from
ImageMagick which has not been pulled in as a dependency.
Version-Release number of selected component (if applicable):
pango-1.42.4-2.fc29
How reproducible:
Always
Steps to Reproduce:
1. Launch GNOME session of a current Fedora 29 Workstation installation.
2. Run 'pango-view --backend=ft2 -t PANGO'.
Actual results:
Utility pango-view aborts with the error message:
"pango-view: When running ImageMagick 'display' command: Failed to execute
child process “display” (No such file or directory)"
Expected results:
Utility pango-view displays the sample text.
Additional info:
- Installing package ImageMagick prior to running pango-view ensures correct
execution. Therefore, adding ImageMagick as a requirement of package pango
solves this issue.
- It is probably preferable to patch pango-view such that it calls "gm display"
from package GraphicsMagick and to pull in the latter instead of ImageMagick.
--
You are receiving this mail because:
You are on the CC list for the bug.
3 years, 6 months