[Fedora-i18n-bugs] [Bug 1825060] New: Cannot add input method to ibus
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1825060
Bug ID: 1825060
Summary: Cannot add input method to ibus
Product: Fedora
Version: 31
Hardware: x86_64
OS: Linux
Status: NEW
Component: ibus
Assignee: tfujiwar(a)redhat.com
Reporter: jon780(a)gmail.com
QA Contact: extras-qa(a)fedoraproject.org
CC: i18n-bugs(a)lists.fedoraproject.org,
shawn.p.huang(a)gmail.com, tfujiwar(a)redhat.com
Target Milestone: ---
Classification: Fedora
Description of problem:
When starting ibus (ibus-daemon --xim or just ibus-daemon) after updating last
night (dnf update) ibus lost my input method (anthy). If I go into preferences
to re-add it, after hitting close and re-opening preferences, it's gone again.
It won't actually save it. Also I get the following output in the terminal
after launching ibus-daemon:
"portal is not running: Timeout was reached"
I've also tried adding other input methods with the same results.
Version-Release number of selected component (if applicable): iBus 1.5.21
How reproducible:
Every time, even after completely rebooting the PC.
Steps to Reproduce:
1. Run ibus-daemon
2. Go to Preferences > Input Method > Add > Japanese > Anthy > Add
3. Click close
4. Re-open Preferences and go to Input Method tab, it will still be empty.
Actual results:
Expected results:
Additional info:
--
You are receiving this mail because:
You are on the CC list for the bug.
3 years, 7 months
[Fedora-i18n-bugs] [Bug 1784430] New: Please package python3-polib for EPEL 8
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1784430
Bug ID: 1784430
Summary: Please package python3-polib for EPEL 8
Product: Fedora EPEL
Version: epel8
Status: NEW
Component: python-polib
Assignee: suanand(a)redhat.com
Reporter: vtrefny(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: diegobz(a)gmail.com, dingyichen(a)gmail.com,
i18n-bugs(a)lists.fedoraproject.org,
ivazqueznet(a)gmail.com, moez.roy(a)gmail.com,
reallylongword(a)gmail.com, suanand(a)redhat.com
Target Milestone: ---
Classification: Fedora
It's available for EPEL 7 and it would be nice to have it for CentOS/RHEL 8
too.
I'm packager and I can help as a co-maintainer if needed.
--
You are receiving this mail because:
You are on the CC list for the bug.
3 years, 7 months
[Fedora-i18n-bugs] [Bug 1823637] Terminus fonts broken after terminus-fonts-4.48-5.fc32.noarch update
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1823637
--- Comment #2 from Akira TAGOH <tagoh(a)redhat.com> ---
Well, this is caused by 0 timestamp on ostree system. the scenario leading up
to this issue is:
1. fc-cache create a cache when installing a font; cache contains timestamp and
timestamp is used to detect an update on the target directory. if the directory
timestamp is different compared to one in a cache, cache will be updated.
2. ostree resets timestamp to 0
3. when running fontconfig-aware applications, all caches is basically updated
due to the above, except it has already been done since last install of fonts.
i.e. not if there are valid caches in user cache directory.
4. considered users caches is newer than system caches due to the above and has
priority to be used.
5. When going to install a new font package on this state, 3) won't happen
because of 4). plus, in general, parent cache is going to be updated when
installing a new font on new directory though, this won't happen. thus,
fontconfig doesn't recognize a directory newly created and then can't find out
fonts.
I'm not sure what is better to fix. we may have some options:
1. restore timestamp for caches; everything will works back. but there may be a
problem from ostree POV. dunno.
2. stop detecting updates and update caches; may see similar problem when
installing fonts manually on user side.
3. stop updating caches for system directories; somewhat sounds realistic to me
but this needs to assume fc-cache is run in a timely manner. which isn't
acceptable somewhat from upstream POV.
4. any more idea?
--
You are receiving this mail because:
You are on the CC list for the bug.
3 years, 7 months
[Fedora-i18n-bugs] [Bug 1823637] Terminus fonts broken after terminus-fonts-4.48-5.fc32.noarch update
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1823637
Jens Petersen <petersen(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ajax(a)redhat.com,
| |caillon+fedoraproject@gmail
| |.com,
| |fonts-bugs(a)lists.fedoraproj
| |ect.org,
| |gnome-sig(a)lists.fedoraproje
| |ct.org,
| |i18n-bugs(a)lists.fedoraproje
| |ct.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
Component|terminus-fonts |fontconfig
Assignee|rhbugs(a)n-dimensional.de |tagoh(a)redhat.com
--
You are receiving this mail because:
You are on the CC list for the bug.
3 years, 7 months
[Fedora-i18n-bugs] [Bug 1134299] Layout switching happens with unspecified shortcut
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1134299
Pravin Satpute <psatpute(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |psatpute(a)redhat.com
--- Comment #22 from Pravin Satpute <psatpute(a)redhat.com> ---
Created attachment 1678415
--> https://bugzilla.redhat.com/attachment.cgi?id=1678415&action=edit
Image showing default next input source selection options in F31, F32-Beta
Steps followed:
1. Added more inputs
2. Pressed "Both Shift keys"
Behaviour Observed: No changes in input sources.
Steps Followed:
1. Window Key + Space
Behaviour Observed: Next input source getting selected.
Working as expected for me.
Not reproducible in both Fedora 31 and Fedora 32 Beta as well. Let me know, if
anyone else can reproduce this issue, else will close this by next week.
Additional Info: Though i observed one another bug : I cant change default next
input source selection keys, but that deserve more discussion and another bug.
--
You are receiving this mail because:
You are on the CC list for the bug.
3 years, 7 months