https://bugzilla.redhat.com/show_bug.cgi?id=2004265
Bug ID: 2004265
Summary: Official name of Taiwan is wrong
Product: Fedora
Version: 35
Hardware: All
Status: NEW
Component: iso-codes
Assignee: pnemade(a)redhat.com
Reporter: julian.g(a)posteo.de
QA Contact: extras-qa(a)fedoraproject.org
CC: caillon+fedoraproject(a)gmail.com,
gnome-sig(a)lists.fedoraproject.org,
i18n-bugs(a)lists.fedoraproject.org, mclasen(a)redhat.com,
pnemade(a)redhat.com, rhughes(a)redhat.com,
rstrode(a)redhat.com, sandmann(a)redhat.com
Target Milestone: ---
Classification: Fedora
Description of problem:
The "official name" of the country on Taiwan is wrong. It states "Province of
China", which is obviously not its official name. No country would call itself
"Province" of another country. The official name is "Republic of China".
Some sources:
- Official government website https://www.taiwan.gov.tw by the RoC Ministry of
Foreign Affairs
- You can ask any person living on the Island.
- As an IT person, you might have some hardware labeled "Made in RoC".
- The Hong Kong and the Taiwanese locale both have "中華民國" as a translation,
which means "Republic of China".
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2004265
https://bugzilla.redhat.com/show_bug.cgi?id=1974076
Bug ID: 1974076
Summary: Chinese input methods use previously enabled layout
Product: Fedora
Version: 34
Hardware: All
OS: Linux
Status: NEW
Component: ibus-libpinyin
Severity: medium
Assignee: pwu(a)redhat.com
Reporter: nickolay.ilyushin(a)gmail.com
QA Contact: extras-qa(a)fedoraproject.org
CC: i18n-bugs(a)lists.fedoraproject.org,
petersen(a)redhat.com, pwu(a)redhat.com
Target Milestone: ---
Classification: Fedora
Description of problem:
ibus-libpinyin (and most probably several other input methods) uses `default`
keyboard layout instead of `us` or whatever fits best. This effectively means
that the last keyboard layout (non-IME) will be used for the pinyin input. For
users which use non-Latin keyboard layouts, such as Russian or Ukrainian, this
makes pinyin input unusable.
Version-Release number of selected component (if applicable): 1.12.0
How reproducible: easily.
Steps to Reproduce:
1. Enable pinyin input method in your settings.
2. Switch to e.g. Russian layout.
3. Switch to pinyin IME.
4. You will type Russian letters and pinyin IME will not trigger.
Actual results:
`4. You will type Russian letters and pinyin IME will not trigger.`
Expected results:
`4. You will type *Latin* letters and pinyin IME *will* trigger.`
Additional info:
There are two workarounds:
1. Manually patch `/usr/share/ibus/component/libpinyin.xml` and change `layout`
to `us` from `default`. I don't know how this will work with non-QWERTY
keyboards though.
2. Switch to a Latin layout before switching to pinyin.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1999864
Bug ID: 1999864
Summary: Cannot find package with font for Coptic although such
a package exists for Fedora 34
Product: Fedora
Version: 34
Status: NEW
Component: fontconfig
Assignee: tagoh(a)redhat.com
Reporter: mfabian(a)redhat.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, 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
Created attachment 1819530
--> https://bugzilla.redhat.com/attachment.cgi?id=1819530&action=edit
Gnome Software unable to find Coptic fonts
Using Fedora-Workstation-Live-x86_64-34-1.2.iso in qemu.
I played with emoji picker and Gnome popped up something requesting more fonts.
I clicked and then Gnome Software said:
“Unable to find the Coptic, Persian, Old (ca. 600-400 B.C.), Ugaritic you were
searching for. Please see _the documentation_ for more information.”
See attached screenshot.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1897782
Bug ID: 1897782
Summary: ibus pinyin input with special characters like '/'
will repeat itself non-stop and cause strange
behaviours with background applications
Product: Fedora
Version: 33
Status: NEW
Component: ibus-libpinyin
Assignee: pwu(a)redhat.com
Reporter: yemoran-2020(a)outlook.com
QA Contact: extras-qa(a)fedoraproject.org
CC: i18n-bugs(a)lists.fedoraproject.org,
petersen(a)redhat.com, pwu(a)redhat.com
Target Milestone: ---
Classification: Fedora
Description of problem:
In Fedora 33 Workstation, with a Chinese system language, when I try to input
with the ibus input (intelligent pinyin), and I pressed the slash key'/', then
the slash character '/' will automatically keep repeating itself, even if I
only pressed the slash key '/' once.
Not only this caused unwanted '/' to spam, but:
1. Also prevents me from pressing alphabetical characters to use pinyin input
normally, unless I delete all my remaining characters to exit pinyin prompt and
start over;
2. Can possibly delete my already-saved text, in combination with
<Ctrl-Backspace>.
It seems that I have completely lost control within the pinyin prompt. I have
met with other surprising conditions, though cannot be immediately reproduced
now, but I believe more combinations of inputs triggering different bugs will
be confirmed later.
Version-Release number of selected component (if applicable):
Any kind of version. I also tested with Fedora 32 Workstation, still have this
bug.
How reproducible:
Always
Steps to Reproduce:
1. Fetch any Fedora Workstation version, be it 32 or 33 or any updates applied.
2. Add Chinese input method 'Intelligent Pinyin' and switch to it
3. In GNOME(Wayland), open any GTK-based application, be it Firefox, GNOME
Terminal, gedit, Libreoffice, ... (take gedit as an example)
4. Input 你好,今天天气 (keypress: nihao<1>,jintian<1>) as a start up example, confirm
input use number key '1'. or keys like <Enter> or <Space>.
5. Input 怎么样/ (keypress: zenmy/). Do not confirm immediately after 'zenmy', but
press '/' exactly once.
6. The '/' character is repeating itself within several hundred milliseconds.
7. Press <Ctrl-Backspace>. gedit will highlight "你好,今天天气" (with a lot of
trailing '/').
8. Press <Backspace> to delete these Chinese characters.
Actual results:
Not only '/' is repeating itself, but also I lost control to gedit and gedit
thinks you want to press '/' forever or even wants to delete my
already-confirmed characters before this input.
Expected results:
1. '/' Should not trigger anything, unless I have pressed this key and did not
release this key press (but I always release keys)
2. '/' Should not make me lost control over pinyin prompt to gedit
3. <Backspace> Should only delete pinyin alphabets in pinyin prompt panel, and
should not do anything to the background gedit texts, unless I have exited the
pinyin prompt panel (because I confirmed my input or have deleted every pinyin
alphabet in it)
Additional info:
1. I did not found this bug on Debian buster or Arch with latest updates.
Additionally, '/' did not even input a single character '/' in these
distributions, but I cannot confirm if this is the expected behaviour. In
Fedora 33 KDE, '/' did input a single character '/', but immediately stopped.
2. I didn't find this behaviour in qt-based applications (like Fedora Image
Writer or Octave) in GNOME, or any application in other desktop environments
(including KDE, or even GTK-based Cinnamon Desktop). This bug seems to only
occur on GTK-based applications on GNOME.
3. I can be very sure that this is not caused by something wrong with my
specific keyboard, because (a) Other distributions worked very well (b) Other
Fedora spins worked very well (c) Qt-based applications in GNOME worked very
well (d) GNOME X11 session worked very well (e) I replicated this bug on a
fresh install of Fedora 32 Workstation in another laptop of mine.
4. I guess other special characters (or keys) like '[', ']', '\', '<Esc>',
'<Backspace>', etc. may trigger similar bugs, but I cannot confirm. '/' will
surely trigger this. ',' and '.' are used in pinyin input method to flip
candidate characters pages, so they doesn't trigger this bug. ' does not
trigger this bug (used in xi'an for 西安)
--
You are receiving this mail because:
You are on the CC list for the bug.
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/hunsp…
)
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.
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.
https://bugzilla.redhat.com/show_bug.cgi?id=1974983
Bug ID: 1974983
Summary: After upgrade xkeyboard-config to version 2.33-1.fc35
layout indicator stop react to layout switch by
Ctrl-Shift key combination.
Product: Fedora
Version: rawhide
Status: NEW
Component: xkeyboard-config
Assignee: peter.hutterer(a)redhat.com
Reporter: mikhail.v.gavrilov(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:
After upgrade xkeyboard-config to version 2.33-1.fc35 layout indicator stop
react to layout switch by Ctrl-Shift key combination.
The bug is affected only Wayland session and only non standard layout switch
key combination.
Last good version is 2.32-3.fc35
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1919963
Bug ID: 1919963
Summary: /usr/share/doc/libunistring-devel/libunistring.html
missing in devel
Product: Fedora
Version: 32
Hardware: All
OS: All
Status: NEW
Component: libunistring
Severity: medium
Assignee: p(a)draigbrady.com
Reporter: reini.urban(a)gmail.com
QA Contact: extras-qa(a)fedoraproject.org
CC: dueno(a)redhat.com, i18n-bugs(a)lists.fedoraproject.org,
jim(a)meyering.net, p(a)draigbrady.com,
redhat-bugzilla(a)linuxnetz.de
Target Milestone: ---
Classification: Fedora
Description of problem:
after installing libunistring and libunistring-devel the main doc entrypoint
for html is missing.
/usr/share/doc/libunistring-devel/libunistring.html
Version-Release number of selected component (if applicable):
libunistring-devel-0.9.10-7.fc32.x86_64
How reproducible:
Open a html doc, and click on Contents.
e.g firefox /usr/share/doc/libunistring-devel/libunistring_1.html
Haven't checked if that is an upstream problem, or just a bad rpm spec.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2013610
Bug ID: 2013610
Summary: Problem when ibus uses XIM: When committing something
and then sending a space by returning False, the
commit and the space are reversed
Product: Fedora
Version: 34
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
Created attachment 1832549
--> https://bugzilla.redhat.com/attachment.cgi?id=1832549&action=edit
Video showing the problem using ibus-m17n with si-wijesekera
[mfabian@fedora ~]$ cat /etc/fedora-release
Fedora release 35 (Thirty Five)
[mfabian@fedora ~]$ rpm -q ibus
ibus-1.5.25-4.fc35.x86_64
[mfabian@fedora ~]$ rpm -q ibus-m17n
ibus-m17n-1.4.7-1.fc35.x86_64
[mfabian@fedora ~]$ rpm -q ibus-typing-booster
ibus-typing-booster-2.14.13-1.fc35.noarch
[mfabian@fedora ~]$
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2013610
https://bugzilla.redhat.com/show_bug.cgi?id=2015149
Bug ID: 2015149
Summary: Candidate lists shown in gnome on-screen keyboard are
not hidden/closed when they should
Product: Fedora
Version: 34
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
Created attachment 1834251
--> https://bugzilla.redhat.com/attachment.cgi?id=1834251&action=edit
Video showing the problem
[mfabian@fedora ~]$ cat /etc/fedora-release
Fedora release 35 (Thirty Five)
[mfabian@fedora ~]$ rpm -q ibus
ibus-1.5.25-4.fc35.x86_64
[mfabian@fedora ~]$ rpm -q gnome-shell
gnome-shell-41.0-4.fc35.x86_64
[mfabian@fedora ~]$
Running in qemu-kvm with all current updates.
Gnome Xorg session.
Input methods sometimes show candidate lists and sometimes hide or close them
again.
For example, when a candidate is committed the candidate list usually
disappears.
The candidate list shown on top of the gnome on-screen keyboard should behave
the same way. Always when the “normal” candidate list would disappear, the
candidate list on top of the Gnome on-screen keyboard should disappear as well.
But this is not the case.
See the attached video.
The video shows using these input methods:
- ibus-libpinyin (Chinese (Intelligent Pinyin))
- ibus-kkc (Japanese (Kana Kanji))
- ibus-typing-booster (Other (Typing Booster))
- ibus-anthy (Japanese (Anthy))
*Only* if ibus-anthy is used, the candidate list disappears reliably when the
candidate currently shown in the preedit is commit by clicking on the "Return"
key on the on-screen keyboard.
When using ibus-kkc, the candidate list on top of the on-screen keyboard does
*not* disappear when committing the candidate currently shown in the preedit by
clicking on the Return key.
Same with ibus-libpinyin, when committing the candidate currently shown in the
preedit by clicking on the space bar on the on-screen keyboard, the candidate
list does *not* disappear.
Also the same with ibus-typing-booster, when committing the candidate currently
shown in the preedit by clicking either on the space bar or the return key on
hte on-screen keyboard, the candidate list does *not* disappear.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2015149
https://bugzilla.redhat.com/show_bug.cgi?id=1910836
Bug ID: 1910836
Summary: stardict-3.0.6.2 is available
Product: Fedora
Version: rawhide
Status: NEW
Component: stardict
Keywords: FutureFeature, Triaged
Assignee: psatpute(a)redhat.com
Reporter: upstream-release-monitoring(a)fedoraproject.org
QA Contact: extras-qa(a)fedoraproject.org
CC: anish.developer(a)gmail.com,
i18n-bugs(a)lists.fedoraproject.org, nav007(a)gmail.com,
petersen(a)redhat.com, psatpute(a)redhat.com,
pwu(a)redhat.com, robinlee.sysu(a)gmail.com
Target Milestone: ---
Classification: Fedora
Latest upstream release: 3.0.6.2
Current version/release in rawhide: 3.0.6-15.fc33
URL: http://sourceforge.net/projects/stardict-4
Please consult the package updates policy before you issue an update to a
stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/
More information about the service that created this bug can be found at:
https://fedoraproject.org/wiki/Upstream_release_monitoring
Please keep in mind that with any upstream change, there may also be packaging
changes that need to be made. Specifically, please remember that it is your
responsibility to review the new version to ensure that the licensing is still
correct and that no non-free or legally problematic items have been added
upstream.
Based on the information from anitya:
https://release-monitoring.org/project/4887/
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1813728
Bug ID: 1813728
Summary: Square four dot Unicode character has incorrect glyph
Product: Fedora
Version: 31
Hardware: x86_64
OS: Linux
Status: NEW
Component: pango
Severity: low
Assignee: pwu(a)redhat.com
Reporter: guillaumepoiriermorency(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:
The glyph for the Unicode "square four dot" character is incorrect.
Version-Release number of selected component (if applicable):
I think this problem arose when upgrading from Fedora 30 to Fedora 31.
How reproducible:
The simplest way is to start GNOME Characters Map and search for "square four
dot".
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1938251
Bug ID: 1938251
Summary: update_preedit_text_with_mode(..., .., ...,
IBus.PreeditFocusMode.COMMIT) doesn’t work in Gnome
Wayland (works fine in Gnome Xorg)
Product: Fedora
Version: 34
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 installed Fedora-Workstation-Live-x86_64-34-20210308.n.0.iso into qemu.
Add the ibus-typing-booster input method in the Gnome control center and
also add the “Vietnamese (telex (m17n))” input method from ibus-m17n.
Both input methods use
update_preedit_text_with_mode(..., .., ..., IBus.PreeditFocusMode.COMMIT)
and this problem can be reproduced with either of them.
Open a gedit and a gnome-terminal.
Select ibus-typing-booster in the Gnome panel and type “test”.
The word “test” is underlined, indicating that it is in preedit and not yet
committed to gedit.
Now click on gnome-terminal to change the focus to gnome-terminal.
The string “test” vanishes from gedit. It should *not* vanish, it should
be committed i.e. the underline under “test” should vanish and the string
“test” should be in gedit.
Same problem with the Vietnamese (telex (m17n)) input method.
Select it in the Gnome panel.
Type “a” into gedit. The “a” is underlined because it is in preedit.
Click on gnome-terminal to change the focus to gnome-terminal.
The “a” vanishes. Here as well the “a” should be commited to gedit, i.e.
the underline should disappear and the “a” should remain in gedit.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1964374
Bug ID: 1964374
Summary: stardict scan hotkey doesn't work
Product: Fedora
Version: 33
Status: NEW
Component: stardict
Assignee: psatpute(a)redhat.com
Reporter: antmak.pub(a)gmail.com
QA Contact: extras-qa(a)fedoraproject.org
CC: anish.developer(a)gmail.com,
i18n-bugs(a)lists.fedoraproject.org, nav007(a)gmail.com,
petersen(a)redhat.com, psatpute(a)redhat.com,
pwu(a)redhat.com, robinlee.sysu(a)gmail.com,
yanqiyu01(a)gmail.com
Target Milestone: ---
Classification: Fedora
Description of problem:
The "Use scan hotkey:" option from StarDict's Preferences doesn't work
Version-Release number of selected component (if applicable):
stardict-3.0.6-15.fc33.x86_64
Fedore 33
GNOME @ Wayland session
How reproducible:
Just change the option to any value, it doesn't work.
Steps to Reproduce:
1. Open StarDict
2. Open Preferences, "Scan Selection" tab
3. Enable "Use scan hotkey" option.
4. Values: "<Primary><Alt>x", "<Super>j", "<Primary><Alt>j" don't work - it
can't scan selected words from other windows like Firefox or Gedit
Actual results:
It should scan selected words in other apps and open a translate window
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=2013323
Bug ID: 2013323
Summary: Cursor position and conversion regioni of ibus-anthy
are invisible in Google Documents (both in firefox and
google-chrome)
Product: Fedora
Version: 34
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
Created attachment 1832255
--> https://bugzilla.redhat.com/attachment.cgi?id=1832255&action=edit
Video showing the wrongly displayed cursor position using ibus-anthy in Google
Documents
I did choose component ibus, although this is likely not an ibus bug but a
problem in google docs, but I wanted to report it somehow, maybe something can
be done to improve this:
Fedora-Workstation-Live-x86_64-35-20210829.n.0.iso installed in qemu-kvm with
all current updates.
firefox-93.0-2.fc35.x86_64
google-chrome-unstable-96.0.4662.6-1.x86_64
ibus-1.5.25-4.fc35.x86_64
ibus-anthy-1.5.13-1.fc35.x86_64
See the attached video.
In the video I type わたしのなまえはやまだです first in gedit to show how it should work.
After typing that hiragana, I type space to start conversion. The current
conversion region is indicated by the cursor position and a purple background
color. When the conversion to kanji is startet, at first the cursor position is
at the left of the preedit and the conversion region is わたしの. I can then move
the conversion region right with arrow-right and see that it moves because the
blue background and the cursor position moves.
Then I do the same in Google Documents (both in firefox and google-chrome, that
makes no difference):
- The cursor position is *always* shown at the right end of the preedit
- The purple background color of the conversion region is not there
One can move the conversion region around using the arrow keys, one just cannot
see where the conversion region currently is the purple background is missing
*and* the cursor position is *always* at the right end of the preedit.
The same problem happens when trying to use ibus-typing-booster with the
"inline completion" option in Google Documents. The color of the inline
completion is missing *and* the cursor position is always at the end of the
preedit, so one cannot see where the inline completion is and whether it has
been accepted or not.
In gedit in wayland, the colors don't work either, but at least the cursor
position is shown correctly. When only the cursor position is shown but no
color, it is not great at least somewhat usable. By carefully watching the
cursor one can still see what is going on. But when the cursor positon is
always at the right of preedit *and* there is no colour, this is completely
unusable.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2013323
https://bugzilla.redhat.com/show_bug.cgi?id=1779123
Bug ID: 1779123
Summary: Pango no longer supports type1 fonts
Product: Fedora
Version: rawhide
Status: NEW
Component: pango
Assignee: pwu(a)redhat.com
Reporter: mjg(a)fedoraproject.org
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 type1 fonts. Therefore, no application
which uses pango for font loading can use type1 fonts any more.
Version-Release number of selected component (if applicable):
pango-1.44.6-1.fc31.x86_64 (and later)
How reproducible:
always
Steps to Reproduce:
1. Upgrade F31 or rawhide
2. Open any pango-using application
3. Try to use type1 font
Actual results:
No type1 font is usable
Expected results:
Type1 font is usable
Additional info:
bug 1753295 is the same bug for dropped bitmap font support. Over there,
workarounds specific for bitmap fonts (conversion to opentype bitmap fonts) are
discussed. An attempt to discuss type1 there failed.
This bug here is specifically about type1 fonts to discuss ways (or their
absence) to deal with pangos dropped type 1 support.
--
You are receiving this mail because:
You are on the CC list for the bug.
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.
https://bugzilla.redhat.com/show_bug.cgi?id=2020514
Bug ID: 2020514
Summary: Ibus got installed on upgrading to Fedora 35 but it
doesn't work with KDE/Qt apps
Product: Fedora
Version: 35
Status: NEW
Component: ibus
Assignee: tfujiwar(a)redhat.com
Reporter: raghu+fac(a)raghukamath.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:
I was using KDE's plasma keyboard layout switcher to switch between input
keyboard layouts. Upon upgrading to Fedora 35 KDE spin, ibus got installed, But
ibus doesn't work with plasma desktop environment. I can't type in local
language in Qt apps and even on plasma desktop like krunner etc despite
switching to another keyboard layout. It works in GTK apps but not on any Qt
apps. Since Qt apps are common on KDE plasma environment ibus becomes a
hindrance.
Removing Ibus doesn't bring back the old native plasma keyboard layout switched
this rendering the plasma keyboard layout switcher KCM useless.
Version-Release number of selected component (if applicable):
How reproducible:
always
Steps to Reproduce:
1.Use ibus on KDE plasma environment.
Actual results:
Ibus doesn't work in Qt apps and plasma apps
Expected results:
layout switching should work across gtk as well as qt apps
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=2020514
https://bugzilla.redhat.com/show_bug.cgi?id=1931294
Bug ID: 1931294
Summary: URL tag is outdated
Product: Fedora
Version: 32
Status: NEW
Component: scim-anthy
Severity: low
Assignee: tagoh(a)redhat.com
Reporter: tim(a)tim-landscheidt.de
QA Contact: extras-qa(a)fedoraproject.org
CC: i18n-bugs(a)lists.fedoraproject.org,
petersen(a)redhat.com, tagoh(a)redhat.com
Target Milestone: ---
Classification: Fedora
The URL "http://scim-imengine.sourceforge.jp/" used in the URL tag for the
binary package scim-anthy is outdated. https://github.com/scim-im/scim-anthy
seems to be working.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1850832
Bug ID: 1850832
Summary: The Gujarati & Hindi itrans methods are not able to
type sentences correctly.
Product: Fedora
Version: 32
Hardware: x86_64
OS: Linux
Status: NEW
Component: ibus-m17n
Severity: high
Assignee: pnemade(a)redhat.com
Reporter: nirmalpathak(a)fedoraproject.org
QA Contact: extras-qa(a)fedoraproject.org
CC: i18n-bugs(a)lists.fedoraproject.org, mfabian(a)redhat.com,
pnemade(a)redhat.com, shawn.p.huang(a)gmail.com
Target Milestone: ---
Classification: Fedora
Created attachment 1698739
--> https://bugzilla.redhat.com/attachment.cgi?id=1698739&action=edit
Actual result while typing in GEdit using Gujarati and Hindi using itrans(m17n)
input method.
Description of problem:
The Gujarati & Hindi itrans methods are not able to type sentences correctly.
When you start typing in Gujarati or Hindi using itrans(m17n) input method, the
letters at times are replaced by 'space' or it simply doesn't print. At times,
the special characters like "?" are printed before the previously typed/printed
character.
This happens abruptly but in most cases, once you enter a new line by pressing
'enter' or 'return' key and start new sentence.
Version-Release number of selected component (if applicable):
m17n-db-1.8.0-9.fc32.noarch
ibus-m17n-1.4.2-2.fc32.x86_64
m17n-lib-1.8.0-7.fc32.x86_64
How reproducible:
Type in Gujarati or Hindi language using ibus itrans(m17n) method.
Steps to Reproduce:
1. Select Gujarati (itrans - m17n) or Hindi (itrans - m17n) method from ibus
input method.
2. Start typing multiple sentences in Gujarati or Hindi.
3. Press 'enter' or 'return' key to start a new sentence in a new line.
Actual results:
- કે મછે?
- બરાબ રનથી લખાતું
- कै से ?हो
- ऐसा क्युं छ परहा है?
Expected results:
- કેમ છે?
- બરાબર નથી લખાતું
- कैसे हो?
- ऐसा क्युं छप रहा है?
Additional info:
Please check attached GIF image for actual results.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1751061
Bug ID: 1751061
Summary: Compose doesn’t work when using ibus
Product: Fedora
Version: 31
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 installed Fedora-Everything-netinst-x86_64-31-20190909.n.0.iso in
qemu.
Ibus version is:
ibus-1.5.21-1.fc31.x86_64
I installed the gnome-tweaks package and set the compose key (Multi_key) to
“Scroll Lock”.
Configured input methods and keyboard layouts (as seen in the gnome panel) are:
English (US, euro on 5) en
日本語 ja
日本語(かな漢字) ja
その他(Typing Booster) 🚀
I choose the "English (US, euro on 5)" keyboard layout and
try to type into gedit.
When pressing <Multi_key> , I see
⎄
i.e. I see U+2384 COMPOSITION SYMBOL as expected.
But if I wait about a second, it disappears again.
Now I type <Multi_key> <'> fast, not waiting after <Multi_key>
I see
⎄'
and it disappears again after about a second.
<Multi_key> <'> <a> fast and I see:
á
After waiting for about a second, it turns into
á⎄
i.e. U+2384 COMPOSITION SYMBOL is added after the á without pressing any more
keys, just by waiting. This U+2384 COMPOSITION SYMBOL stays there, even if I
wait more. If I continue to type <'> <a>, I finally get:
áá
i.e. I have produced this “áá” by typing <Multi_key> <'> <a> <'> <a>.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1733869
Bug ID: 1733869
Summary: gettext: Getting errors in double free with msgfmt
command.
Product: Fedora
Version: 30
Status: NEW
Component: gettext
Assignee: panovotn(a)redhat.com
Reporter: poyadav(a)redhat.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,
panovotn(a)redhat.com, petersen(a)redhat.com,
praiskup(a)redhat.com, suanand(a)redhat.com
Target Milestone: ---
Classification: Fedora
Description of problem: Error in poc, please refer the result section for
details.
Version-Release number of selected component (if applicable):
gettext-0.19.8.1-18.fc30.x86_64
How reproducible:
Always
Steps to Reproduce:
1. Clone https://github.com/CCCCCrash/POCs.git.
2. Run valgrind msgfmt poc command.
3. Observe the output.
Actual results:
[poyadav@localhost doublefree]$ valgrind msgfmt poc
==8072== Memcheck, a memory error detector
==8072== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==8072== Using Valgrind-3.15.0 and LibVEX; rerun with -h for copyright info
==8072== Command: msgfmt poc
==8072==
==8072== Conditional jump or move depends on uninitialised value(s)
==8072== at 0x48D9940: freea (in /usr/lib64/libgettextlib-0.19.8.1.so)
==8072== by 0x487E8EA: po_lex_charset_set (in
/usr/lib64/libgettextsrc-0.19.8.1.so)
==8072== by 0x487E098: po_gram_parse (in
/usr/lib64/libgettextsrc-0.19.8.1.so)
==8072== by 0x487EB9A: ??? (in /usr/lib64/libgettextsrc-0.19.8.1.so)
==8072== by 0x487A773: catalog_reader_parse (in
/usr/lib64/libgettextsrc-0.19.8.1.so)
==8072== by 0x10E7C7: ??? (in /usr/bin/msgfmt)
==8072== by 0x10D8EB: ??? (in /usr/bin/msgfmt)
==8072== by 0x4AABF32: (below main) (in /usr/lib64/libc-2.29.so)
==8072==
poc:17: duplicate message definition...
poc:16: ...this is the location of the first definition
poc:18:3: syntax error
poc:18: keyword "n" unknown
poc:19: end-of-line within string
poc:28: duplicate message definition...
poc:24: ...this is the location of the first definition
poc:35: keyword "msgud_plural" unknown
poc:34: missing 'msgstr' section
poc:35:13: syntax error
poc:40: end-of-line within string
poc:46: end-of-line within string
poc: warning: Charset missing in header.
Message conversion to user's charset will not work.
poc:42: duplicate message definition...
poc:6: ...this is the location of the first definition
poc:46:2: syntax error
poc:46: keyword "Ep" unknown
poc:47: keyword "C" unknown
poc:48: keyword "s" unknown
poc:49: keyword "bo" unknown
poc:50: keyword "S" unknown
poc:50:236: invalid control sequence
poc:50:397: invalid control sequence
poc:51: end-of-line within string
msgfmt: too many errors, aborting
==8072==
==8072== HEAP SUMMARY:
==8072== in use at exit: 59,783 bytes in 123 blocks
==8072== total heap usage: 547 allocs, 424 frees, 99,479 bytes allocated
==8072==
==8072== LEAK SUMMARY:
==8072== definitely lost: 650 bytes in 82 blocks
==8072== indirectly lost: 0 bytes in 0 blocks
==8072== possibly lost: 0 bytes in 0 blocks
==8072== still reachable: 59,133 bytes in 41 blocks
==8072== suppressed: 0 bytes in 0 blocks
==8072== Rerun with --leak-check=full to see details of leaked memory
==8072==
==8072== Use --track-origins=yes to see where uninitialised values come from
==8072== For lists of detected and suppressed errors, rerun with: -s
==8072== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0)
Expected results:
No errors.
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=2026124
Bug ID: 2026124
Summary: add pkg-config file
Product: Fedora
Version: 35
Status: NEW
Component: libunistring
Severity: medium
Assignee: p(a)draigbrady.com
Reporter: drepper(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: dueno(a)redhat.com, i18n-bugs(a)lists.fedoraproject.org,
jim(a)meyering.net, p(a)draigbrady.com,
redhat-bugzilla(a)linuxnetz.de
Target Milestone: ---
Classification: Fedora
Description of problem:
To simplify the use of the library and checking in tools like rpm and cmake it
would be beneficial to have a pkg-config file in the -devel package
Version-Release number of selected component (if applicable):
libunistring-0.9.10-14
How reproducible:
always
Steps to Reproduce:
1.cat /usr/lib64/pkgconfig/libunistring.pc
2.
3.
Actual results:
no such file
Expected results:
Perhaps something like this:
prefix=/usr
exec_prefix=/usr
includedir=/usr/include
libdir=/usr/lib64
Name: GNU libunistring
Description: GNU libunistring library implementing Unicode string types in
three flavours
URL: https://www.gnu.org/software/libunistring/
Version: 0.9.10
Cflags: -I${includedir}
Libs: -L${libdir} -lunistring
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=2026124
https://bugzilla.redhat.com/show_bug.cgi?id=1954716
Bug ID: 1954716
Summary: Fonts not used correctly
Product: Fedora
Version: rawhide
Status: NEW
Component: fontconfig
Assignee: tagoh(a)redhat.com
Reporter: barbarah.duarte(a)fluocomunicacao.com.br
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, 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
Created attachment 1776799
--> https://bugzilla.redhat.com/attachment.cgi?id=1776799&action=edit
LibreOffice with all three fonts displayed in regular, italic and bold face.
I have installed some company-provided fonts for use in presentations etc.:
$ ls /usr/share/fonts/neo-sans-intel/
NeoSansIntel-Italic.ttf NeoSansIntel-MediumItalic.ttf
NeoSansIntel-LightItalic.ttf NeoSansIntel-Medium.ttf
NeoSansIntel-Light.ttf NeoSansIntel.ttf
In LibreOffice I have a choice of three separate fonts: Neo Sans Intel, Neo
Sans Intel Medium, and Neo Sans Intel Light.
For each of those three, the italic version of the font (from the separate TTF
file) is used. I can tell by the tail on the 'f' character. For bold text,
however, an 'emboldening' algorithm seems to be used instead of using the
appropriate separate font file.
In GNOME font selection dialogs, I see just one 'Neo Sans Intel' family, with a
choice of 8 styles. I'll ignore the italic versions since those do actually
seem to work as expected, so there are four weights listed:
- Light (== Neo Sans Intel Light)
- Regular (== Neo Sans Intel Medium)
- Medium (== Neo Sans Intel Medium)
- Bold (== Neo Sans Intel Medium + emboldening algorithm?)
I *don't* seem to have an option in GNOME which will just use the straight 'Neo
Sans Intel' font.
So both seem to be getting it wrong, in different ways. Or perhaps there's
something wrong with the fonts themselves?
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1981500
Bug ID: 1981500
Summary: [f34] some snaps are having font display issues
Product: Fedora
Version: 34
OS: Linux
Status: NEW
Component: fontconfig
Severity: medium
Assignee: tagoh(a)redhat.com
Reporter: dvd(a)redhat.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, 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:
Installing some snaps like codium are having font issues in dialog windows.
This has been widely discussed upstream [1]
Tried multiple workarounds and none of them are working:
~~~
sudo rm /var/cache/fontconfig/*
rm ~/.cache/fontconfig/*
rm -f ~/snap/codium/current/.cache/
fc-cache -r -v
snap run --shell codium
fc-cache -r -v
exit
~~~
I also tried this with VScodium running
Arch wiki [a] suspects it's an issue caused by fontconfig>=2.13.91
Version-Release number of selected component (if applicable):
fontconfig-2.13.93-6.fc34.x86_64
snapd-selinux-2.51-1.fc34.noarch
snap-confine-2.51-1.fc34.x86_64
snapd-2.51-1.fc34.x86_64
How reproducible:
All the time
Steps to Reproduce:
1. snap install codium
2. Open Folder dialog or any kind of dialog
Actual results:
All the text is square instead of readable characters
Expected results:
We should be able to read the text.
Additional info:
[a] https://wiki.archlinux.org/title/Talk:Snap
[1]
~~~
https://forum.snapcraft.io/t/snapped-app-not-loading-fonts-on-fedora-and-ar…https://forum.inkdrop.app/t/snap-with-no-visible-letters-in-system-dialogs-…https://wiki.archlinux.org/title/Talk:Snaphttps://githubmemory.com/repo/snapcrafters/codium/issues/6https://github.com/VSCodium/vscodium/issues/426
~~~
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1771836
Bug ID: 1771836
Summary: ibus not responsive on wayland with sway as
windowmanager
Product: Fedora
Version: 31
Status: NEW
Component: ibus
Assignee: tfujiwar(a)redhat.com
Reporter: chorn(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
Created attachment 1635626
--> https://bugzilla.redhat.com/attachment.cgi?id=1635626&action=edit
strace when running ibus-wayland from a terminal in sway
Description of problem:
ibus not responsive on wayland with sway as windowmanager
Version-Release number of selected component (if applicable):
ibus-wayland-1.5.21-3.fc31.x86_64
ibus-1.5.21-3.fc31.x86_64
ibus-mozc-2.23.2815.102-8.fc31.x86_64
How reproducible:
always
Steps to Reproduce:
1. install Fedora31, select lxde-desktop-environment to get wayland installed
2. dnf -y install sway ibus-wayland ibus-mozc
3. useradd -m chris; passwd chris
4. Use this in the users .bashrc :
[[ $(pgrep ibus-daemon) ]] || ibus-daemon --xim --daemonize -r
export IMSETTINGS_INTEGRATE_DESKTOP=yes
export IMSETTINGS_MODULE=ibus
export QT_IM_MODULE=ibus
export XMODIFIERS=@im=ibus
export GTK_IM_MODULE=ibus
5. Boot system into multi-usermode, for example in setting it as default target
and rebooting
6. login as user chris
7. run sway in executing 'sway'
8. get a terminal in pressing $mod + return (by default, $mod is the
windows-key)
9. verify ibus-daemon is running: 'ps ax|grep ibus'
10. try to run ibuswayland: '/usr/libexec/ibus-wayland'
Actual results:
No input_method global
Expected results:
ibus-wayland should run, and I should be able to switch input method to mozc as
configured with 'ibus-setup'.
Additional info:
- Might very well be an issue on my side.. but after trying this now for a
week, taking that to bugzilla.
- fcitx4 from Fedora works under sway.
- When setting up ibus as above, I was never able to run ibus-wayland, and ibus
did never react to attempts to switch the input method with shift+space or
ctrl+space, I tried these combinations after setting them up with ibus-setup
- Instead of running ibus-daemon from user .bashrc, I did run it from sway
directly. Steps:
mkdir ~/.config/sway
cp /etc/sway/config ~/.config/sway/config
echo 'exec /usr/bin/ibus-daemon --xim --daemonize' >>~/.config/sway/config
The result is the same though.
- When running ibus-daemon non-daemonizing from a terminal, I get this:
[chris@космос ~]$ ibus-daemon -r -v
(ibus-ui-gtk3:75725): IBUS-WARNING **: 15:00:43.303: panel.vala:255: If you
launch KDE5 on xterm, export XDG_CURRENT_DESKTOP=KDE before launch KDE5.
(ibus-ui-gtk3:75725): IBUS-WARNING **: 15:00:43.335: ibus_bus_call_sync:
org.freedesktop.DBus.Properties.Get:
GDBus.Error:org.freedesktop.DBus.Error.Failed: No global engine.
(and ibus-daemon stays running)
- I tried various terminals, for example xterm and terminator
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1933539
Bug ID: 1933539
Summary: Require mkfontdir/mkfontscale directly, not
xorg-x11-xkb-utils
Product: Fedora
Version: rawhide
Status: NEW
Component: liberation-fonts
Assignee: vishalvijayraghavan(a)gmail.com
Reporter: peter.hutterer(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: caillon+fedoraproject(a)gmail.com,
extras-qa(a)fedoraproject.org,
fonts-bugs(a)lists.fedoraproject.org,
gnome-sig(a)lists.fedoraproject.org,
i18n-bugs(a)lists.fedoraproject.org, mclasen(a)redhat.com,
mtasaka(a)tbz.t-com.ne.jp, petersen(a)redhat.com,
psatpute(a)redhat.com, rhughes(a)redhat.com,
rstrode(a)redhat.com, sandmann(a)redhat.com,
vishalvijayraghavan(a)gmail.com
Depends On: 1933537
Blocks: 1932731
Target Milestone: ---
Classification: Fedora
liberation-fonts currently BuildRequires: xorg-x11-font-utils
xorg-x11-font-utils is to be split up into multiple packages, see Bug 1932731.
This package only requires mkfontscale and mkfontdir, so let's BuildRequires
these directly. xorg-x11-font-utils has had Provides for those for ages now
anyway, so this is largely a noop from this package's POV.
Suggested diff:
diff --git a/liberation-fonts.spec b/liberation-fonts.spec
index a9cc575..583e224 100644
--- a/liberation-fonts.spec
+++ b/liberation-fonts.spec
@@ -24,7 +24,8 @@ Source8: %{fontname}-sans.metainfo.xml
Source9: %{fontname}-serif.metainfo.xml
BuildArch: noarch
-BuildRequires: fontpackages-devel >= 1.13, xorg-x11-font-utils
+BuildRequires: fontpackages-devel >= 1.13
+BuildRequires: mkfontscale mkfontdir
BuildRequires: fontforge
BuildRequires: libappstream-glib
BuildRequires: python3
Verified successful build in a local F33 container with only the mkfontscale
(Bug 1932734) and bdftopcf (Bug 1932736) packages installed, no
xorg-x11-font-utils.
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1932731
[Bug 1932731] X.org Utility Deaggregation - xorg-x11-font-utils
https://bugzilla.redhat.com/show_bug.cgi?id=1933537
[Bug 1933537] Require mkfontdir/mkfontscale directly, not xorg-x11-xkb-utils
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1858617
Bug ID: 1858617
Summary: vlgothic-fonts-20200719 is available
Product: Fedora
Version: rawhide
Status: NEW
Component: vlgothic-fonts
Keywords: FutureFeature, Triaged
Assignee: tagoh(a)redhat.com
Reporter: upstream-release-monitoring(a)fedoraproject.org
QA Contact: extras-qa(a)fedoraproject.org
CC: fonts-bugs(a)lists.fedoraproject.org,
i18n-bugs(a)lists.fedoraproject.org, tagoh(a)redhat.com
Target Milestone: ---
Classification: Fedora
Latest upstream release: 20200719
Current version/release in rawhide: 20141206-16.fc32
URL: https://osdn.jp/projects/vlgothic/releases/
Please consult the package updates policy before you issue an update to a
stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/
More information about the service that created this bug can be found at:
https://fedoraproject.org/wiki/Upstream_release_monitoring
Please keep in mind that with any upstream change, there may also be packaging
changes that need to be made. Specifically, please remember that it is your
responsibility to review the new version to ensure that the licensing is still
correct and that no non-free or legally problematic items have been added
upstream.
Based on the information from anitya:
https://release-monitoring.org/project/5103/
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2003233
Bug ID: 2003233
Summary: unicode-ucd-14.0.0 is available
Product: Fedora
Version: rawhide
Status: NEW
Component: unicode-ucd
Keywords: FutureFeature, Triaged
Assignee: petersen(a)redhat.com
Reporter: upstream-release-monitoring(a)fedoraproject.org
QA Contact: extras-qa(a)fedoraproject.org
CC: i18n-bugs(a)lists.fedoraproject.org, mfabian(a)redhat.com,
petersen(a)redhat.com
Target Milestone: ---
Classification: Fedora
Latest upstream release: 14.0.0
Current version/release in rawhide: 13.0.0-4.fc35
URL: http://www.unicode.org/Public/zipped/
Please consult the package updates policy before you issue an update to a
stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/
More information about the service that created this bug can be found at:
https://fedoraproject.org/wiki/Upstream_release_monitoring
Please keep in mind that with any upstream change, there may also be packaging
changes that need to be made. Specifically, please remember that it is your
responsibility to review the new version to ensure that the licensing is still
correct and that no non-free or legally problematic items have been added
upstream.
Based on the information from anitya:
https://release-monitoring.org/project/5045/
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1916743
Bug ID: 1916743
Summary: Fedora Scientific Spin does not include ibus-table*
packages
Product: Fedora
Version: 33
Hardware: x86_64
OS: Linux
Status: NEW
Component: ibus-table
Severity: high
Assignee: mfabian(a)redhat.com
Reporter: pa_ubach(a)alum.mit.edu
QA Contact: extras-qa(a)fedoraproject.org
CC: dchen(a)redhat.com, i18n-bugs(a)lists.fedoraproject.org,
kent.neo(a)gmail.com, mfabian(a)redhat.com,
pwu(a)redhat.com, shawn.p.huang(a)gmail.com
Target Milestone: ---
Classification: Fedora
Description of problem:
Clean install of Fedora Scientific (KDE) does not include the ibus-table*
packages that are necessary for local distributions of the keyboard.
Version-Release number of selected component (if applicable):
How reproducible:
Haven't tried
Steps to Reproduce:
1. Install Fedora Scientific
2. Try to type using dead keys in any KDE program or LibreOffice.
3.
Actual results: Vowel letters don't include accents.
Expected results: áàäâéèéêíïîóòöôúùüû
Additional info: To fix the problem, the user must install ibus-table*
packages, which is not described in the documentation, but it should not be
necessary to search it in the documentation anyway.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1757760
Bug ID: 1757760
Summary: Hiragana to English conversion with F10 key adds
unwanted letters
Product: Fedora
Version: rawhide
Status: NEW
Component: ibus-kkc
Assignee: dueno(a)redhat.com
Reporter: ykatabam(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: dueno(a)redhat.com, i18n-bugs(a)lists.fedoraproject.org
Target Milestone: ---
Classification: Fedora
Description of problem:
When we enter an English word with consecutive double letters (e.g. assembly)
in Hiragana mode and use F10 to convert into English, the double letters
becomes the triple letters in some cases (e.g. asssembly).
This happens irregularly, but tends to happen more often for longer words.
Here are some examples:
communication becomes commmunication
bugzilla becomes bugzilla
Pittsburgh becomes Pitttsburgh
FYI, auto-correct is disabled, as auto-correct changes the input when it's not
a dictionary word so it doesn't allow us to convert into English properly in
hiragana mode.
--
You are receiving this mail because:
You are on the CC list for the bug.
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=2001332
Bug ID: 2001332
Summary: pango-view with --backend=ft2 and ---antialias=none
generates antialiased renderings
Product: Fedora
Version: 34
Hardware: x86_64
OS: Linux
Status: NEW
Component: pango
Severity: high
Assignee: pwu(a)redhat.com
Reporter: andre.maute(a)gmx.de
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,
pwu(a)redhat.com, rhughes(a)redhat.com,
rstrode(a)redhat.com, sandmann(a)redhat.com,
tagoh(a)redhat.com
Target Milestone: ---
Classification: Fedora
Created attachment 1820649
--> https://bugzilla.redhat.com/attachment.cgi?id=1820649&action=edit
image showing the problem
Description of problem:
Hello Fedora Team,
I have a recently updated Fedora 34 installation.
The problem I want to report is that it looks like
the pango-view tool is always turning antialiasing on
when one uses the FreeType backend --backend=ft2,
even when one explicitly switches antialiasing off with --antialias=none,
whereas it works for the --backend=cairo option.
A second question would be if the FreeType backend
generally doesn't/can't support --antialias=none?
I tried to find some examples in C with antialising turned off
but I wasn't successful.
I must confess I didn't check other distributions.
As pango-view is regarded as a tool for creating minimal reproducers
against the font rendering stack, I dare to set the severity to 'high' :-)
Best Regards
Andre
Version-Release number of selected component (if applicable):
$ uname -a
Linux localhost.localdomain 5.13.13-200.fc34.x86_64 #1 SMP Thu Aug 26 17:06:39
UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
$ dnf list installed | grep dejavu
dejavu-lgc-sans-fonts.noarch 2.37-16.fc34
@fedora
dejavu-lgc-sans-mono-fonts.noarch 2.37-16.fc34
@fedora
dejavu-lgc-serif-fonts.noarch 2.37-16.fc34
@fedora
dejavu-sans-fonts.noarch 2.37-16.fc34
@fedora
dejavu-sans-mono-fonts.noarch 2.37-16.fc34
@fedora
dejavu-serif-fonts.noarch 2.37-16.fc34
@fedora
$ dnf list installed | grep ImageMagick
ImageMagick.x86_64 1:6.9.11.27-3.fc34
@fedora
ImageMagick-libs.x86_64 1:6.9.11.27-3.fc34
@fedora
$ dnf list installed | grep pango
pango.i686 1.48.9-2.fc34
@updates
pango.x86_64 1.48.9-2.fc34
@updates
pango-devel.x86_64 1.48.9-2.fc34
@updates
pangomm.x86_64 2.46.1-1.fc34
@updates
$ dnf list installed | grep freetype
freetype.i686 2.10.4-3.fc34
@fedora
freetype.x86_64 2.10.4-3.fc34
@fedora
freetype-devel.x86_64 2.10.4-3.fc34
@fedora
$ dnf list installed | grep fontconfig
fontconfig.i686 2.13.94-2.fc34
@updates
fontconfig.x86_64 2.13.94-2.fc34
@updates
fontconfig-devel.x86_64 2.13.94-2.fc34
@updates
$ dnf list installed | grep cairo
cairo.i686 1.17.4-3.fc34
@fedora
cairo.x86_64 1.17.4-3.fc34
@fedora
cairo-devel.x86_64 1.17.4-3.fc34
@fedora
cairo-gobject.i686 1.17.4-3.fc34
@fedora
cairo-gobject.x86_64 1.17.4-3.fc34
@fedora
cairomm.x86_64 1.14.2-8.fc34
@fedora
python2-cairo.x86_64 1.18.2-8.fc34
@fedora
python3-cairo.x86_64 1.20.0-2.fc34
@fedora
How reproducible:
Always
Steps to Reproduce:
$ pango-view --no-display --dpi=72 --backend=cairo --antialias=none
--font="DejaVu Sans 38" --text="ABCDEFGHIJKLMNOPQRSTUVWXYZ"
--output=abc-cairo-aa-none.png
$ pango-view --no-display --dpi=72 --backend=cairo --antialias=gray
--font="DejaVu Sans 38" --text="ABCDEFGHIJKLMNOPQRSTUVWXYZ"
--output=abc-cairo-aa-gray.png
$ pango-view --no-display --dpi=72 --backend=cairo --antialias=subpixel
--font="DejaVu Sans 38" --text="ABCDEFGHIJKLMNOPQRSTUVWXYZ"
--output=abc-cairo-aa-subpixel.png
$ pango-view --no-display --dpi=72 --backend=ft2 --antialias=none
--font="DejaVu Sans 38" --text="ABCDEFGHIJKLMNOPQRSTUVWXYZ"
--output=abc-ft2-aa-none.png
$ pango-view --no-display --dpi=72 --backend=ft2 --antialias=gray
--font="DejaVu Sans 38" --text="ABCDEFGHIJKLMNOPQRSTUVWXYZ"
--output=abc-ft2-aa-gray.png
$ pango-view --no-display --dpi=72 --backend=ft2 --antialias=subpixel
--font="DejaVu Sans 38" --text="ABCDEFGHIJKLMNOPQRSTUVWXYZ"
--output=abc-ft2-aa-subpixel.png
$ gimp abc-*.png
Actual results:
Attached pngs.
The file abc-ft2-aa-none.png is in gray-scale and not as expected in
black-white.
The file abc-cairo-aa-none.png is in black-white as expected.
Expected results:
I would have expected the files abc*--aa-none.png looking near identical.
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=2009807
Bug ID: 2009807
Summary: Change default Amharic font from Abyssinica SIL to
Noto Serif Ethiopic
Product: Fedora
Version: 35
Hardware: x86_64
OS: Linux
Status: NEW
Component: Fonts
Severity: medium
Assignee: i18n-bugs(a)lists.fedoraproject.org
Reporter: beta-stage(a)tutanota.com
QA Contact: fonts-bugs(a)lists.fedoraproject.org
Target Milestone: ---
Classification: Fedora
Description of problem:
Abyssinica SIL is an old font. It's barely legible and breaks in most apps.
Noto Serif Ethiopic, on the other hand, is a modern and well designed font.
Noto Serif Ethiopic is distributed with Open Font License, so packaging it
won't be a problem.
Link
https://fonts.google.com/noto/specimen/Noto+Serif+Ethiopic?noto.query=Amhar…
How reproducible:
always
Steps to Reproduce:
1. Pretty much using the the Amharic language anywhere on Fedora
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2009807
https://bugzilla.redhat.com/show_bug.cgi?id=2021366
Bug ID: 2021366
Summary: Nimbus Mono PS font should not fc-match Courier, as
certain letter combinations are not monospaced
Product: Fedora
Version: 35
Hardware: x86_64
OS: Linux
Status: NEW
Component: Fonts
Assignee: i18n-bugs(a)lists.fedoraproject.org
Reporter: info(a)skierpage.com
QA Contact: fonts-bugs(a)lists.fedoraproject.org
Target Milestone: ---
Classification: Fedora
Created attachment 1840789
--> https://bugzilla.redhat.com/attachment.cgi?id=1840789&action=edit
look at "affiliation"
Description of problem:
I visited https://schema.org/Person in Firefox in Fedora 35 KDE spin and
noticed the monospace text "affiliation" was not monospaced; the letters "ffi"
were on top of each other as if replaced by the ligature ffi.
The page CSS is styling the <code> tag "font-family: Courier, monospace;", and
in Fedora 35 KDE Spin `fc-match Courier` returns
NimbusMonoPS-Regular.otf: "Nimbus Mono PS" "Regular"
indeed, if I set font-family to "Nimbus Mono PS" in some simple HTML
https://www.skierpage.com/bugs/nimbusmono_not_monospaced.html , other ff
combinations are also "ligature-ized".
I tried these two URLs in the chromium-browser package and in the Epiphany and
Konqueror browser flatpaks. These did not use "Nimbus Mono PS" as the fallback
font for font-family "Courier" so did not display "affiliation" badly on the
Person web page, but if you specify font-family "Nimbus Mono PS", you get the
ligature.
Version-Release number of selected component (if applicable):
Mozilla Firefox 94.0
urw-base35-fonts-20200910-9.fc35.src.rpm
How reproducible:
Always.
Steps to Reproduce:
1. Visit https://schema.org/Person and
https://www.skierpage.com/bugs/nimbusmono_not_monospaced.html in Firefox and
other browsers.
2. Note how "ffi" appears.
Actual results:
Firefox uses "Nimbus Mono PS" as the fallback for font-family Courier; all
these browsers replace "ffi" and such with the ligature character in "Nimbus
Mono PS", destroying the desired monospace effect.
Expected results:
Monospaced fonts should appear... monospaced, so every character should occupy
the same amount of horizontal space. However, if a font provides ligature
glyphs for "ffi" and such, then it's unclear if it's wrong for the browser to
use them; (l33t developers now explicitly use monospaced coding fonts that do
wacky substitutions.)
So the fix could be for Firefox and/or fc-match to _not_ use Nimbus Mono PS
when text handling requests Courier. The other browsers on my system don't,
I'm not sure why. Another could be to remove the ligatures from Nimbus Mono PS.
Additional info:
The rendering of code on that page (see attachment) is pretty terrible, note
the oversized 'd's in "address". Another reason to have Courier match some
other monospaced font than Nimbus Mono PS.
You can use the Fontmatrix program to enable OpenType features; checking latn >
dflt > liga changes the display of "ff" combinations.
Firefox using ligatures in monospaced fonts is
https://bugzilla.mozilla.org/show_bug.cgi?id=384395 , was closed WONTFIX "We
can't really do anything about it -- the underlying text system is doing the
ligaturization, not us".
ArchLinux users discussed the problem in
https://bbs.archlinux.org/viewtopic.php?id=238832
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2021366
https://bugzilla.redhat.com/show_bug.cgi?id=2015628
Bug ID: 2015628
Summary: No entry /sys/class/leds for Fn 5 key that toggles
keyboard backlight
Product: Fedora
Version: 34
Hardware: x86_64
OS: Linux
Status: NEW
Component: xkeyboard-config
Severity: medium
Assignee: peter.hutterer(a)redhat.com
Reporter: eb30750(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: Keyboard backlight worked until upgrading to FC34. The
Fn 5 key toggled the keyboard backlight on and off. In researching the new
method to expose the Fn keys to the user I found that there is no input/input5.
The input/input3 is configured.
lrwxrwxrwx 1 root root 0 Jul 10 16:30 input3::capslock ->
../../devices/platform/i8042/serio0/input/input3/input3::capslock
lrwxrwxrwx 1 root root 0 Jul 10 16:30 input3::numlock ->
../../devices/platform/i8042/serio0/input/input3/input3::numlock
lrwxrwxrwx 1 root root 0 Jul 10 16:30 input3::scrolllock ->
../../devices/platform/i8042/serio0/input/input3/input3::scrolllock
lrwxrwxrwx 1 root root 0 Jul 10 16:30 phy0-led ->
../../devices/pci0000:00/0000:00:1c.0/0000:01:00.0/leds/phy0-led
Version-Release number of selected component (if applicable):
5.14.11-200.fc34.x86_64
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
A script or kernel option that builds the /sys/class/leds/input/input5
hierarchy.
Additional info:
If the input5 exists then simply changing the brightness value should turn on
the keyboard backlight.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2015628
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=1961723
Bug ID: 1961723
Summary: dnf reports errors when processing
translate-toolkit.noarch
Product: Fedora
Version: rawhide
Hardware: x86_64
OS: Linux
Status: NEW
Component: translate-toolkit
Severity: high
Assignee: suanand(a)redhat.com
Reporter: grgoffe(a)yahoo.com
QA Contact: extras-qa(a)fedoraproject.org
CC: dwayne(a)translate.org.za,
i18n-bugs(a)lists.fedoraproject.org, mfabian(a)redhat.com,
petersen(a)redhat.com, suanand(a)redhat.com
Target Milestone: ---
Classification: Fedora
Description of problem: Attempting upgrade of this system; dnf reports an error
condition which stops upgrade (see below)
Version-Release number of selected component (if applicable):
see below
How reproducible:
always
Steps to Reproduce:
1.see below
2.
3.
Actual results: see below
Expected results: successful and clean system upgrade
Additional info:
/usr/bin/dnf --noautoremove --refresh --skip-broken --allowerasing --best
--setopt=zchunk=0 --exclude='*'kernel'*' --exclude=erlang'*'
--exclude='environment-modules*' --exclude=Lmod upgrade /root/upgrade.log
Script started, output log file is '/root/upgrade.log'.
Fedora rawhide openh264 (From Cisco) - x86_64
2.5 kB/s | 989 B 00:00
Fedora - Modular Rawhide - Developmental packages for the next Fedora release
679 kB/s | 1.6 MB 00:02
Fedora - Rawhide - Developmental packages for the next Fedora release
1.3 MB/s | 64 MB 00:47
Error:
Problem: cannot install the best update candidate for package
translate-toolkit-3.3.5-1.fc35.noarch
- problem with installed package translate-toolkit-3.3.5-1.fc35.noarch
- nothing provides python3.9dist(lxml) >= 4.6.3 needed by
translate-toolkit-3.3.6-1.fc35.noarch
--
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=1969644
Bug ID: 1969644
Summary: xkeyboard-config-2.33 is available
Product: Fedora
Version: rawhide
Status: NEW
Component: xkeyboard-config
Keywords: FutureFeature, Triaged
Assignee: peter.hutterer(a)redhat.com
Reporter: upstream-release-monitoring(a)fedoraproject.org
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
Latest upstream release: 2.33
Current version/release in rawhide: 2.32-3.fc35
URL: https://www.freedesktop.org/wiki/Software/XKeyboardConfig/
Please consult the package updates policy before you issue an update to a
stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/
More information about the service that created this bug can be found at:
https://fedoraproject.org/wiki/Upstream_release_monitoring
Please keep in mind that with any upstream change, there may also be packaging
changes that need to be made. Specifically, please remember that it is your
responsibility to review the new version to ensure that the licensing is still
correct and that no non-free or legally problematic items have been added
upstream.
Based on the information from anitya:
https://release-monitoring.org/project/5191/
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2025224
Bug ID: 2025224
Summary: extra keys on Lenovo / IBM keyboard are not working
anymore
Product: Fedora
Version: 34
Hardware: x86_64
OS: Linux
Status: NEW
Component: xkeyboard-config
Severity: low
Assignee: peter.hutterer(a)redhat.com
Reporter: af(a)getwings.eu
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:
The extra keys "Lock Desktop", "My Documents", "Calculator", "E-Mail",
"Internet" in the top row of a Lonovo or IBM keyboard (such a thing:
https://support.lenovo.com/us/en/solutions/pd010250-lenovo-enhanced-perform…)
do not work anymore. The keys "Work Processor" and "Spreadsheet" never did.
However. It is convenient to just press such a button and i wonder, why this
functionality has been broken with Fedora 34 or one of the "updates". Even the
blue button was usable for something, now it is not anymore.
Version-Release number of selected component (if applicable):
2.33 . Not sure, if the issue has really to do with the keyboard configuration.
How reproducible:
Steps to Reproduce:
1. Press one of the buttons in the top row
Actual results:
nothing happens. The keys are not visible anymore in the output of xmodmap -pk
Expected results:
The respective action is performed
Additional info:
It was working for years, actually i can't remember, that it did not work since
i use such keyboards with Linux.
xev does not show any of these key presses or releases.
It happens with both gnome and plasma and it does not matter, whether Xorg or
@$%&* wayland is running, thus i assume, the issue is in one of the plethora of
lower layers.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2025224
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=2002446
Bug ID: 2002446
Summary: zinnia-0.07 is available
Product: Fedora
Version: rawhide
Status: NEW
Component: zinnia
Keywords: FutureFeature, Triaged
Assignee: liangsuilong(a)gmail.com
Reporter: upstream-release-monitoring(a)fedoraproject.org
QA Contact: extras-qa(a)fedoraproject.org
CC: i18n-bugs(a)lists.fedoraproject.org,
liangsuilong(a)gmail.com, petersen(a)redhat.com,
pwu(a)redhat.com
Target Milestone: ---
Classification: Fedora
Latest upstream release: 0.07
Current version/release in rawhide: 0.06-55.fc35
URL: https://github.com/silverhikari/zinnia/
Please consult the package updates policy before you issue an update to a
stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/
More information about the service that created this bug can be found at:
https://fedoraproject.org/wiki/Upstream_release_monitoring
Please keep in mind that with any upstream change, there may also be packaging
changes that need to be made. Specifically, please remember that it is your
responsibility to review the new version to ensure that the licensing is still
correct and that no non-free or legally problematic items have been added
upstream.
Based on the information from anitya:
https://release-monitoring.org/project/5302/
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1993670
Bug ID: 1993670
Summary: segfault with pango-view assert in cairo
Product: Fedora
Version: 34
Hardware: x86_64
OS: Linux
Status: NEW
Component: pango
Severity: high
Assignee: pwu(a)redhat.com
Reporter: andre.maute(a)gmx.de
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,
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:
1. This one works
$ pango-view --nodisplay --text "abc"
2. This one doesn't
$ pango-view --no-display --text "abc"
pango-view: cairo-hash.c:217: _cairo_hash_table_destroy: Assertion
`hash_table->live_entries == 0' failed.
Aborted (core dumped)
So pango-view triggers an assertion in Cairo.
Version-Release number of selected component (if applicable):
$ dnf repoquery --installed pango
pango-0:1.48.7-1.fc34.i686
pango-0:1.48.7-1.fc34.x86_64
How reproducible:
always
Steps to Reproduce:
1. see 1. of description above
2. see 2. of description above
Actual results:
segfault
Expected results:
no segfault
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=2023222
Bug ID: 2023222
Summary: ibus cannot open display via imsettings in Plasma
Wayland
Product: Fedora
Version: 35
Status: NEW
Component: imsettings
Assignee: tagoh(a)redhat.com
Reporter: tfujiwar(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
Description of problem:
im-chooser can launch imsettings-daemon and ibus-daemon and imsettings-daemon
launches ibus-daemon again when user log into the Plasma Wayland session but
ibus-ui-gtk3 fails to be launched because ibus-ui-gtk3 fails to open Display
with XOpenDisplay(NULL) via imsettings-daemon while I confirmed ibus-ui-gtk3
got DISPLAY=:0 environment variable.
If I invoke ibus-daemon by manual ibus-daemon can launch ibus-ui-gtk3
successfully so this issue would be imsettings in Plasma Wayland.
Version-Release number of selected component (if applicable):
imsettings-1.8.2-4.fc35.x86_64
ibus-1.5.25-4.fc35.x86_64
plasma-workspace-wayland-5.22.5-2.fc35.x86_64
How reproducible:
Steps to Reproduce:
1. Log into Plasma Wayland session
2. Run im-chooser and select IBus and ibus-daemon runs
3. Log out the session and imsettings-daemon is still running
4. Log into Plasma Wayland session again
or
5. Run im-chooser again and select IBus -> No input method -> IBus
Actual results:
ibus-ui-gtk3 and ibus-x11 are not running and no IBus panel icon in the Plasma
desktop
Expected results:
ibus-ui-gtk3 and ibus-x11 are running and users can switch IBus engines from
IBus panel icon in the Plasma desktop
Additional info:
I'm thinking to launch imsettings-daemon from
/usr/libexec/plasma-dbus-run-session-if-needed until Plasma Wayland can manage
IBus input contexts with D-Bus likes GNOME Wayland so I'm fine to terminate
imsettings-daemon by logging out the desktop session.
--- /usr/libexec/plasma-dbus-run-session-if-needed.orig07:11:14.936606871 +0900
+++ /usr/libexec/plasma-dbus-run-session-if-needed
@@ -2,6 +2,10 @@
# Usage: plasma-dbus-run-session-if-needed PROGRAM [ARGUMENTS]
# If the session bus is not available it is spawned and wrapper round our
program
# Otherwise we spawn our program directly
+if [ -x /usr/libexec/xinput-run-in-session ] ; then
+ nohup /usr/libexec/xinput-run-in-session &
+fi
+
drs=
if [ -z "${DBUS_SESSION_BUS_ADDRESS}" ]
then
# cat /usr/libexec/xinput-run-in-session
#!/bin/sh
# Wait for running a desktop session with D-Bus
sleep 180
if [ -x /etc/X11/xinit/xinitrc.d/50-xinput.sh ] ; then
/etc/X11/xinit/xinitrc.d/50-xinput.sh
ibus exit
imsettings-switch -n -q -x
fi
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2023222
https://bugzilla.redhat.com/show_bug.cgi?id=2021739
Bug ID: 2021739
Summary: no fonts available in this package
Product: Fedora
Version: 35
Hardware: noarch
OS: Linux
Status: NEW
Component: japanese-bitmap-fonts
Assignee: tagoh(a)redhat.com
Reporter: takemurafedora(a)gmail.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:
The size of all the font files (*.pcf.gz) are only 20 bites which are gziped
empty files. fonts.dir shows the number of fonts included in the directory is
0.
Version-Release number of selected component (if applicable):
0.20080710-29.fc35
How reproducible:
always
Steps to Reproduce:
1. check to see the fonts that should be proveded with xfontsel, xlsfonts, etc.
2.
3.
Actual results:
No fonts are available.
Expected results:
Many japanese fonts should be availabe from X.
Additional info:
Rebuilding failed with "Missing build dependency: perl", as perl-interpreter
does not provides perl, but /usr/bin/perl.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2021739
https://bugzilla.redhat.com/show_bug.cgi?id=2026540
Bug ID: 2026540
Summary: ibus should own /var/cache/ibus
Product: Fedora
Version: 35
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:
Currently it seems /var/cache/ibus is not owned by any package.
I guess it is created at install time or runtime by ibus write-cache.
So either ibus could just include the directly explicitly or
%ghost it, so that it would be owned.
See
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org…
about unowned /var/cache/ dirs, which prompted this report.
Steps to Reproduce:
1. rpm -qf /var/cache/ibus
Actual results:
file /var/cache/ibus is not owned by any package
Expected results:
owned by ibus
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2026540
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=2026992
Bug ID: 2026992
Summary: harfbuzz-3.1.2 is available
Product: Fedora
Version: rawhide
Status: NEW
Component: harfbuzz
Keywords: FutureFeature, Triaged
Assignee: pnemade(a)redhat.com
Reporter: upstream-release-monitoring(a)fedoraproject.org
QA Contact: extras-qa(a)fedoraproject.org
CC: i18n-bugs(a)lists.fedoraproject.org, klember(a)redhat.com,
moceap(a)hotmail.com, pnemade(a)redhat.com,
psatpute(a)redhat.com
Target Milestone: ---
Classification: Fedora
Latest upstream release: 3.1.2
Current version/release in rawhide: 3.0.0-1.fc36
URL: https://harfbuzz.github.io/
Please consult the package updates policy before you issue an update to a
stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/
More information about the service that created this bug can be found at:
https://fedoraproject.org/wiki/Upstream_release_monitoring
Please keep in mind that with any upstream change, there may also be packaging
changes that need to be made. Specifically, please remember that it is your
responsibility to review the new version to ensure that the licensing is still
correct and that no non-free or legally problematic items have been added
upstream.
Based on the information from anitya:
https://release-monitoring.org/project/1299/
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2026992
https://bugzilla.redhat.com/show_bug.cgi?id=1922346
Parag Nemade <pnemade(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |CURRENTRELEASE
Status|ON_QA |CLOSED
Last Closed| |2021-11-27 08:18:12
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1922346
https://bugzilla.redhat.com/show_bug.cgi?id=1913836
Parag Nemade <pnemade(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |CURRENTRELEASE
Status|ON_QA |CLOSED
Last Closed| |2021-11-27 08:15:35
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1913836
https://bugzilla.redhat.com/show_bug.cgi?id=1913431
Parag Nemade <pnemade(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ON_QA |CLOSED
Resolution|--- |CURRENTRELEASE
Last Closed| |2021-11-27 08:15:26
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1913431
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=2018036
Bug ID: 2018036
Summary: pango 1.49.1 broke multi-line text rendering in
Inkscape
Product: Fedora
Version: 35
Status: NEW
Component: pango
Assignee: pwu(a)redhat.com
Reporter: akiyks(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, 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
Created attachment 1837826
--> https://bugzilla.redhat.com/attachment.cgi?id=1837826&action=edit
Inkscape input and output
Description of problem:
I'm observing mis-placement of multi-line texts in .pdf converted
from .svg via Inkscape on pre-release Fedora 35.
On Fedora 34, they are rendered correctly.
Version-Release number of selected component (if applicable):
On Fedora 35, "incscape --debug-info" says:
Inkscape 1.1 (c68e22c387, 2021-05-23)
GLib version: 2.70.0
GTK version: 3.24.30
glibmm version: 2.66.1
gtkmm version: 3.24.5
libxml2 version: 2.9.12
libxslt version: 1.1.34
Cairo version: 1.17.4
Pango version: 1.49.1
HarfBuzz version: 2.8.2
Poppler version: 21.08.0
OS version: Fedora Linux 35 (Container Image)
On Fedora 34, "incscape --debug-info" says:
Inkscape 1.1 (c68e22c387, 2021-05-23)
GLib version: 2.68.4
GTK version: 3.24.30
glibmm version: 2.66.1
gtkmm version: 3.24.5
libxml2 version: 2.9.12
libxslt version: 1.1.34
Cairo version: 1.17.4
Pango version: 1.48.10
HarfBuzz version: 2.7.4
Poppler version: 21.01.0
OS version: Fedora 34 (Container Image)
How reproducible:
Always.
Steps to Reproduce:
Convert pubsub.svg in the attachment by Inkscape.
1. Run the command "inkscape -o pubsub-xxx.pdf pubsub.svg"
Actual results:
See pubsub-pango-1.49.1.pdf in the attachment.
Expected results:
See pubsub-pango-1.48.10.pdf in the attachment, which is converted
on Fedora 34.
Additional info:
On Fedora 35, by downgrading pango to 1.48.9
(https://kojipkgs.fedoraproject.org//packages/pango/1.48.9/1.fc35/x86_64/pan…)
correct rendering can be restored.
The same issue is reported at upstream Inkscape project at:
https://gitlab.com/inkscape/inkscape/-/issues/2864
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2018036
https://bugzilla.redhat.com/show_bug.cgi?id=2026369
Bug ID: 2026369
Summary: Some applications show weird font
Product: Fedora
Version: 35
Status: NEW
Component: Fonts
Assignee: i18n-bugs(a)lists.fedoraproject.org
Reporter: d.lesca(a)solinos.it
QA Contact: fonts-bugs(a)lists.fedoraproject.org
Target Milestone: ---
Classification: Fedora
Created attachment 1843408
--> https://bugzilla.redhat.com/attachment.cgi?id=1843408&action=edit
Wreid fonds on torbrowser and libreoffice
Description of problem:
Some applications like libreoffice and torbrowser show weird font
Version-Release number of selected component (if applicable):
Fedora 35 Workstation
* Live images
* Fresh installed
* Up to date
How reproducible:
Start with live iso image, open libreoffice write and drop down fonts select
This problem still exist after a new installation and after a full update.
Steps to Reproduce:
1. Start live iso (install it or install it and update)
2. Open libreoffice
3. drop down fonts selector
4. Install torbrowser-laucher an open it
Actual results:
In all of this case wreid fonts appear like attached images
Expected results:
Not wreid fond appear
Additional info:
I have also fill this bug:
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2026369
https://bugzilla.redhat.com/show_bug.cgi?id=1987650
Bug ID: 1987650
Summary: libkkc: FTBFS in Fedora rawhide/f35
Product: Fedora
Version: rawhide
Status: NEW
Component: libkkc
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: 1927309 (F35FTBFS,RAWHIDEFTBFS)
Target Milestone: ---
Classification: Fedora
libkkc failed to build from source in Fedora rawhide/f35
https://koji.fedoraproject.org/koji/taskinfo?taskID=72393843
For details on the mass rebuild see:
https://fedoraproject.org/wiki/Fedora_35_Mass_Rebuild
Please fix libkkc 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,
libkkc will be orphaned. Before branching of Fedora 36,
libkkc 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=1927309
[Bug 1927309] Fedora 35 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=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=2000426
Bug ID: 2000426
Summary: [F36FTBFS]: gettext fails to build from source in
Fedora Rawhide
Product: Fedora
Version: rawhide
Status: NEW
Component: gettext
Assignee: suanand(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,
jjanco(a)redhat.com, nphilipp(a)redhat.com,
petersen(a)redhat.com, praiskup(a)redhat.com,
suanand(a)redhat.com
Blocks: 1936597
Target Milestone: ---
Classification: Fedora
Your package fails to build with the newest autoconf-2.71, which was part of a
recent wide Fedora change. More information about Fedora autoconf Change
available here:
https://fedoraproject.org/wiki/Changes/Autoconf_271#How_To_Test. The easiest
way to reproduce the problem is to execute a fedora scratch-build on your
package. Thank you for cooperation!
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1936597
[Bug 1936597] 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=1806272
Parag Nemade <pnemade(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |CLOSED
Resolution|--- |NEXTRELEASE
Last Closed| |2021-11-22 06:36:12
--- Comment #39 from Parag Nemade <pnemade(a)redhat.com> ---
I believe all the reported issues here are already fixed in Fedora.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1806272
https://bugzilla.redhat.com/show_bug.cgi?id=2023908
Bug ID: 2023908
Summary: pango_item_split: assertion 'split_offset > 0' failed
(crashing nm-applet)
Product: Fedora
Version: 35
Status: NEW
Component: pango
Assignee: pwu(a)redhat.com
Reporter: bcafarel(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, 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: ---
Link ID: GNOME Gitlab GNOME/pango/-/issues/627
Classification: Fedora
Description of problem:
After upgrading to Fedora 35, nm-applet (from
network-manager-applet-1.24.0-1.fc35.x86_64) segfaults on a pango assert:
(nm-applet:8121): Pango-CRITICAL **: 19:26:36.541: pango_item_split: assertion
'split_offset > 0' failed
Version-Release number of selected component (if applicable):
pango-1.49.3-1.fc35.x86_64
How reproducible:
100%
Steps to Reproduce:
1. Left-click on nm-applet to get list of possible connections
Actual results:
Immediate crash
Expected results:
List of connections (note that some sections show small cap letters)
Additional info:
The linked gnome gitlab issue mentions this is generic for strings in string in
a GtkLabel (with small caps)
Rebuilding pango 1.49.3 with patch from
https://gitlab.gnome.org/GNOME/pango/-/merge_requests/505 fixes the issue
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2023908
https://bugzilla.redhat.com/show_bug.cgi?id=2021378
Bug ID: 2021378
Summary: translate-toolkit-3.5.1 is available
Product: Fedora
Version: rawhide
Status: NEW
Component: translate-toolkit
Keywords: FutureFeature, Triaged
Assignee: suanand(a)redhat.com
Reporter: upstream-release-monitoring(a)fedoraproject.org
QA Contact: extras-qa(a)fedoraproject.org
CC: dwayne(a)translate.org.za,
i18n-bugs(a)lists.fedoraproject.org, mfabian(a)redhat.com,
petersen(a)redhat.com, suanand(a)redhat.com
Target Milestone: ---
Classification: Fedora
Latest upstream release: 3.5.1
Current version/release in rawhide: 3.4.1-1.fc36
URL: http://toolkit.translatehouse.org/
Please consult the package updates policy before you issue an update to a
stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/
More information about the service that created this bug can be found at:
https://fedoraproject.org/wiki/Upstream_release_monitoring
Please keep in mind that with any upstream change, there may also be packaging
changes that need to be made. Specifically, please remember that it is your
responsibility to review the new version to ensure that the licensing is still
correct and that no non-free or legally problematic items have been added
upstream.
Based on the information from anitya:
https://release-monitoring.org/project/3685/
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2021378
https://bugzilla.redhat.com/show_bug.cgi?id=2018089
Bug ID: 2018089
Summary: translate-toolkit-3.5.0 is available
Product: Fedora
Version: rawhide
Status: NEW
Component: translate-toolkit
Keywords: FutureFeature, Triaged
Assignee: suanand(a)redhat.com
Reporter: upstream-release-monitoring(a)fedoraproject.org
QA Contact: extras-qa(a)fedoraproject.org
CC: dwayne(a)translate.org.za,
i18n-bugs(a)lists.fedoraproject.org, mfabian(a)redhat.com,
petersen(a)redhat.com, suanand(a)redhat.com
Target Milestone: ---
Classification: Fedora
Latest upstream release: 3.5.0
Current version/release in rawhide: 3.4.1-1.fc36
URL: http://toolkit.translatehouse.org/
Please consult the package updates policy before you issue an update to a
stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/
More information about the service that created this bug can be found at:
https://fedoraproject.org/wiki/Upstream_release_monitoring
Please keep in mind that with any upstream change, there may also be packaging
changes that need to be made. Specifically, please remember that it is your
responsibility to review the new version to ensure that the licensing is still
correct and that no non-free or legally problematic items have been added
upstream.
Based on the information from anitya:
https://release-monitoring.org/project/3685/
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2018089
https://bugzilla.redhat.com/show_bug.cgi?id=2024120
--- Comment #5 from Jens Petersen <petersen(a)redhat.com> ---
Okay based on input from Takao I did manage now to get ibus working in Xorg
now, though reboots should really not be necessary.
1. install KDE Spin (I used latest Rawhide iso) - I installed for Japanese
locale
2. switch to Xorg and login
3. install ibus-anthy or some other ibus IME
4. reboot
5. install im-chooser and imsettings-qt and turn on ibus
6. reboot and login
7. then the ibus applet is already running in the panel (rather hard to see
because both dark)
8. start kwrite and activate ibus Anthy IME and input Japanese
A few of these steps can probably we combined (like installation) or the order
does not always matter (eg "2. Xorg" can be later).
What can I do better?
Doesn't Plasma also have a custom ibus GUI widget indicator UI?
And for Wayland additionally it is necessary to manually export QT_IM_MODULE=qt
say in Konsole to launch apps to get ibus working there.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2024120
https://bugzilla.redhat.com/show_bug.cgi?id=2024120
fujiwara <tfujiwar(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |NOTABUG
Status|NEW |CLOSED
Last Closed| |2021-11-18 07:12:51
--- Comment #4 from fujiwara <tfujiwar(a)redhat.com> ---
(In reply to Rex Dieter from comment #2)
> My f35 plasma wayland session has ibus-related stuff running:
>
You're right. Seems I was confused by bug 2023222 .
I'm closing this issue at the moment and will file another bug for Plasma
Wayland to export QT_IM_MODULE environment variable and the suggested fix is
similar with this bug description.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2024120
https://bugzilla.redhat.com/show_bug.cgi?id=2024120
--- Comment #3 from Jens Petersen <petersen(a)redhat.com> ---
(In reply to Rex Dieter from comment #2)
> My f35 plasma wayland session has ibus-related stuff running:
I suggest trying in a Plasma Live image or for a refresh VM/user.
We found it rather tricky to get ibus up and running in current Fedora KDE.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2024120
https://bugzilla.redhat.com/show_bug.cgi?id=2024120
fujiwara <tfujiwar(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |i18n-bugs(a)lists.fedoraproje
| |ct.org
--- Comment #1 from fujiwara <tfujiwar(a)redhat.com> ---
If you're fine, I can create a pull request for Fedora.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2024120
https://bugzilla.redhat.com/show_bug.cgi?id=1670078
Mike FABIAN <mfabian(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |CLOSED
Resolution|--- |CURRENTRELEASE
Last Closed| |2021-11-15 06:48:57
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1670078
https://bugzilla.redhat.com/show_bug.cgi?id=1690326
fujiwara <tfujiwar(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Version|33 |35
--- Comment #18 from fujiwara <tfujiwar(a)redhat.com> ---
Under the discussion in GNOME-Shell upstream.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1690326
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=2021316
Bug ID: 2021316
Summary: harfbuzz-3.1.1 is available
Product: Fedora
Version: rawhide
Status: NEW
Component: harfbuzz
Keywords: FutureFeature, Triaged
Assignee: pnemade(a)redhat.com
Reporter: upstream-release-monitoring(a)fedoraproject.org
QA Contact: extras-qa(a)fedoraproject.org
CC: i18n-bugs(a)lists.fedoraproject.org, klember(a)redhat.com,
moceap(a)hotmail.com, pnemade(a)redhat.com,
psatpute(a)redhat.com
Target Milestone: ---
Classification: Fedora
Latest upstream release: 3.1.1
Current version/release in rawhide: 3.0.0-1.fc36
URL: https://harfbuzz.github.io/
Please consult the package updates policy before you issue an update to a
stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/
More information about the service that created this bug can be found at:
https://fedoraproject.org/wiki/Upstream_release_monitoring
Please keep in mind that with any upstream change, there may also be packaging
changes that need to be made. Specifically, please remember that it is your
responsibility to review the new version to ensure that the licensing is still
correct and that no non-free or legally problematic items have been added
upstream.
Based on the information from anitya:
https://release-monitoring.org/project/1299/
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2021316
https://bugzilla.redhat.com/show_bug.cgi?id=1498269
John L. Chmielewski <jlcster(a)gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Version|33 |34
--- Comment #15 from John L. Chmielewski <jlcster(a)gmail.com> ---
This bug is reproducible in f34
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1498269
https://bugzilla.redhat.com/show_bug.cgi?id=2019880
Bug ID: 2019880
Summary: iso-codes-4.8.0 is available
Product: Fedora
Version: rawhide
Status: NEW
Component: iso-codes
Keywords: FutureFeature, Triaged
Assignee: pnemade(a)redhat.com
Reporter: upstream-release-monitoring(a)fedoraproject.org
QA Contact: extras-qa(a)fedoraproject.org
CC: caillon+fedoraproject(a)gmail.com,
gnome-sig(a)lists.fedoraproject.org,
i18n-bugs(a)lists.fedoraproject.org, mclasen(a)redhat.com,
pnemade(a)redhat.com, rhughes(a)redhat.com,
rstrode(a)redhat.com, sandmann(a)redhat.com
Target Milestone: ---
Classification: Fedora
Latest upstream release: 4.8.0
Current version/release in rawhide: 4.6.0-2.fc35
URL: https://salsa.debian.org/iso-codes-team/iso-codes
Please consult the package updates policy before you issue an update to a
stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/
More information about the service that created this bug can be found at:
https://fedoraproject.org/wiki/Upstream_release_monitoring
Please keep in mind that with any upstream change, there may also be packaging
changes that need to be made. Specifically, please remember that it is your
responsibility to review the new version to ensure that the licensing is still
correct and that no non-free or legally problematic items have been added
upstream.
Based on the information from anitya:
https://release-monitoring.org/project/1406/
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2019880
https://bugzilla.redhat.com/show_bug.cgi?id=2020154
Bug ID: 2020154
Summary: harfbuzz-3.1.0 is available
Product: Fedora
Version: rawhide
Status: NEW
Component: harfbuzz
Keywords: FutureFeature, Triaged
Assignee: pnemade(a)redhat.com
Reporter: upstream-release-monitoring(a)fedoraproject.org
QA Contact: extras-qa(a)fedoraproject.org
CC: i18n-bugs(a)lists.fedoraproject.org, klember(a)redhat.com,
moceap(a)hotmail.com, pnemade(a)redhat.com,
psatpute(a)redhat.com
Target Milestone: ---
Classification: Fedora
Latest upstream release: 3.1.0
Current version/release in rawhide: 3.0.0-1.fc36
URL: https://harfbuzz.github.io/
Please consult the package updates policy before you issue an update to a
stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/
More information about the service that created this bug can be found at:
https://fedoraproject.org/wiki/Upstream_release_monitoring
Please keep in mind that with any upstream change, there may also be packaging
changes that need to be made. Specifically, please remember that it is your
responsibility to review the new version to ensure that the licensing is still
correct and that no non-free or legally problematic items have been added
upstream.
Based on the information from anitya:
https://release-monitoring.org/project/1299/
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2020154
https://bugzilla.redhat.com/show_bug.cgi?id=1833858
--- Comment #27 from Luke Hutchison <luke.hutch(a)gmail.com> ---
Still an issue in Fedora 34. Can somebody please bump the version number?
Is there some way to flag Droid Sans Fallback so that it is never used to
display characters in the Hangeul range?
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1833858
https://bugzilla.redhat.com/show_bug.cgi?id=1084493
--- Comment #13 from Ben Cotton <bcotton(a)redhat.com> ---
This message is a reminder that Fedora 33 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with
a
Fedora 'version' of '33'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 33 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1084493
https://bugzilla.redhat.com/show_bug.cgi?id=1090631
--- Comment #12 from Ben Cotton <bcotton(a)redhat.com> ---
This message is a reminder that Fedora 33 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with
a
Fedora 'version' of '33'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 33 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1090631
https://bugzilla.redhat.com/show_bug.cgi?id=1806272
--- Comment #38 from Ben Cotton <bcotton(a)redhat.com> ---
This message is a reminder that Fedora 33 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with
a
Fedora 'version' of '33'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 33 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1806272
https://bugzilla.redhat.com/show_bug.cgi?id=1076190
--- Comment #17 from Ben Cotton <bcotton(a)redhat.com> ---
This message is a reminder that Fedora 33 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with
a
Fedora 'version' of '33'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 33 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1076190
https://bugzilla.redhat.com/show_bug.cgi?id=1013949
--- Comment #17 from Ben Cotton <bcotton(a)redhat.com> ---
This message is a reminder that Fedora 33 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with
a
Fedora 'version' of '33'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 33 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1013949
https://bugzilla.redhat.com/show_bug.cgi?id=1690326
--- Comment #17 from Ben Cotton <bcotton(a)redhat.com> ---
This message is a reminder that Fedora 33 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with
a
Fedora 'version' of '33'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 33 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1690326
https://bugzilla.redhat.com/show_bug.cgi?id=1498269
--- Comment #14 from Ben Cotton <bcotton(a)redhat.com> ---
This message is a reminder that Fedora 33 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with
a
Fedora 'version' of '33'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 33 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1498269
https://bugzilla.redhat.com/show_bug.cgi?id=1670078
--- Comment #11 from Ben Cotton <bcotton(a)redhat.com> ---
This message is a reminder that Fedora 33 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with
a
Fedora 'version' of '33'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 33 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1670078
https://bugzilla.redhat.com/show_bug.cgi?id=1580458
--- Comment #11 from Ben Cotton <bcotton(a)redhat.com> ---
This message is a reminder that Fedora 33 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with
a
Fedora 'version' of '33'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 33 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1580458
https://bugzilla.redhat.com/show_bug.cgi?id=1072095
--- Comment #19 from Ben Cotton <bcotton(a)redhat.com> ---
This message is a reminder that Fedora 33 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with
a
Fedora 'version' of '33'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 33 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1072095
https://bugzilla.redhat.com/show_bug.cgi?id=1924576
--- Comment #13 from Ben Cotton <bcotton(a)redhat.com> ---
This message is a reminder that Fedora 33 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with
a
Fedora 'version' of '33'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 33 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1924576
https://bugzilla.redhat.com/show_bug.cgi?id=1833858
--- Comment #26 from Ben Cotton <bcotton(a)redhat.com> ---
This message is a reminder that Fedora 33 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with
a
Fedora 'version' of '33'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 33 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1833858
https://bugzilla.redhat.com/show_bug.cgi?id=683325
--- Comment #32 from Ben Cotton <bcotton(a)redhat.com> ---
This message is a reminder that Fedora 33 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with
a
Fedora 'version' of '33'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 33 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=683325
https://bugzilla.redhat.com/show_bug.cgi?id=1072095
--- Comment #18 from Ben Cotton <bcotton(a)redhat.com> ---
This message is a reminder that Fedora 33 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with
a
Fedora 'version' of '33'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 33 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1072095
https://bugzilla.redhat.com/show_bug.cgi?id=1924576
--- Comment #12 from Ben Cotton <bcotton(a)redhat.com> ---
This message is a reminder that Fedora 33 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with
a
Fedora 'version' of '33'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 33 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1924576
https://bugzilla.redhat.com/show_bug.cgi?id=1833858
--- Comment #25 from Ben Cotton <bcotton(a)redhat.com> ---
This message is a reminder that Fedora 33 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with
a
Fedora 'version' of '33'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 33 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1833858
https://bugzilla.redhat.com/show_bug.cgi?id=683325
--- Comment #30 from Ben Cotton <bcotton(a)redhat.com> ---
This message is a reminder that Fedora 33 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with
a
Fedora 'version' of '33'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 33 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=683325
https://bugzilla.redhat.com/show_bug.cgi?id=1833858
--- Comment #24 from Ben Cotton <bcotton(a)redhat.com> ---
This message is a reminder that Fedora 33 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with
a
Fedora 'version' of '33'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 33 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1833858
https://bugzilla.redhat.com/show_bug.cgi?id=683325
--- Comment #29 from Ben Cotton <bcotton(a)redhat.com> ---
This message is a reminder that Fedora 33 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with
a
Fedora 'version' of '33'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 33 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=683325
https://bugzilla.redhat.com/show_bug.cgi?id=1942970
Fedora Update System <updates(a)fedoraproject.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ON_QA |CLOSED
Resolution|--- |ERRATA
Last Closed| |2021-11-04 01:46:34
--- Comment #7 from Fedora Update System <updates(a)fedoraproject.org> ---
FEDORA-2021-f5f819f8d0 has been pushed to the Fedora 35 stable repository.
If problem still persists, please make note of it in this bug report.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1942970
https://bugzilla.redhat.com/show_bug.cgi?id=2005831
Bug ID: 2005831
Summary: Non-responsive maintainer check for beckerde
Product: Fedora
Version: rawhide
Hardware: All
OS: Linux
Status: NEW
Component: man-pages-es
Severity: medium
Priority: medium
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: ---
Classification: Fedora
This bug is part of the non-responsive maintainer procedure for beckerde,
following
https://docs.fedoraproject.org/en-US/fesco/Policy_for_nonresponsive_package….
Please respond if you are still active in Fedora and want to maintain
man-pages-es.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2005831
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=1987663
Ben Cotton <bcotton(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |CURRENTRELEASE
Status|ON_QA |CLOSED
Last Closed| |2021-11-02 16:03:44
--- Comment #8 from Ben Cotton <bcotton(a)redhat.com> ---
F35 was released today. Closing the trackers.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1987663
https://bugzilla.redhat.com/show_bug.cgi?id=1987434
Bug ID: 1987434
Summary: eb: FTBFS in Fedora rawhide/f35
Product: Fedora
Version: rawhide
Status: NEW
Component: eb
Assignee: petersen(a)redhat.com
Reporter: releng(a)fedoraproject.org
QA Contact: extras-qa(a)fedoraproject.org
CC: i18n-bugs(a)lists.fedoraproject.org, moceap(a)hotmail.com,
petersen(a)redhat.com
Blocks: 1927309 (F35FTBFS,RAWHIDEFTBFS)
Target Milestone: ---
Classification: Fedora
eb failed to build from source in Fedora rawhide/f35
https://koji.fedoraproject.org/koji/taskinfo?taskID=72340359
For details on the mass rebuild see:
https://fedoraproject.org/wiki/Fedora_35_Mass_Rebuild
Please fix eb 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,
eb will be orphaned. Before branching of Fedora 36,
eb 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=1927309
[Bug 1927309] Fedora 35 FTBFS Tracker
--
You are receiving this mail because:
You are on the CC list for the bug.