https://bugzilla.redhat.com/show_bug.cgi?id=1659748
Bug ID: 1659748
Summary: Characters get deleted as you type
Product: Fedora
Version: 29
Status: NEW
Component: ibus-m17n
Severity: high
Assignee: pnemade(a)redhat.com
Reporter: lohang(a)gmail.com
QA Contact: extras-qa(a)fedoraproject.org
CC: i18n-bugs(a)lists.fedoraproject.org, pnemade(a)redhat.com,
shawn.p.huang(a)gmail.com
Target Milestone: ---
Classification: Fedora
Description of problem:
When you type Sinhala using Wijesekera keyboard layout through ibus the first
character gets deleted as soon as you start typing the second character. This
is similar to the bug previously reported for Fedora 28
https://bugzilla.redhat.com/show_bug.cgi?id=1617978
How reproducible:
(1) Steps to Reproduce:
1. Open Libre Office Writer (6.1.2.1)
2. Switch to Sinhala; Sinhalese (wijesekera (m17n))
3. Type keys vksIal kjSka
4. Hit space to separate the second word from the first word. And hit space at
the end of the first word.
Actual results: ක වීන්
Expected results: ඩනිෂ්ක නවීන්
Additional info:
(2) When you try this with emacs the results are a little different. I am
including it here assuming this is related to the same issue:
This is how to reproduce with emacs:
1. Open emacs 26.1 (build 1, x86_64-redhat-linux-gnu, GTK+ Version 3.23.2)
of 2018-08-13
2. Switch to Sinhala; Sinhalese (wijesekera (m17n))
3. Type keys vksIal kjSka
4. Hit space to separate the second word from the first word. And hit space at
the end of the first word.
Actual results: ඩනිෂ් කනවී න්
Expected results: ඩනිෂ්ක නවීන්
This adds a space before the last character of the first word, not where you
want the space to be.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1677534
Bug ID: 1677534
Summary: texttopaps OOMs with 4GB text file!
Product: Fedora
Version: rawhide
Hardware: x86_64
OS: Linux
Status: NEW
Component: paps
Severity: high
Assignee: tagoh(a)redhat.com
Reporter: petersen(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: desktop-qa-list(a)redhat.com, eng-i18n-bugs(a)redhat.com,
i18n-bugs(a)lists.fedoraproject.org, rhel(a)vlasiu.net,
tagoh(a)redhat.com
Depends On: 1635160
Target Milestone: ---
Classification: Fedora
(Cloned from a RHEL7 report)
+++ This bug was initially created as a clone of Bug #1635160 +++
Description of problem:
Trying to print with cups a 4Gb text file fail.
texttopaps consume all the memory and is killed bye the system:
[1023082.003989] Out of memory: Kill process xxxx (texttopaps) score 955 or
sacrifice child
[1023082.005120] Killed process xxxx (texttopaps) total-vm:19958848kB,
anon-rss:7531872kB, file-rss:84kB, shmem-rss:0kB
/usr/lib/cups/filter/texttopaps 1 user1 "example" 1 "" sample-4Gb.txt
--- Additional comment from Akira TAGOH on 2018-10-03 11:54:48 SGT ---
Hmm, that log says it all. I don't think OOM is a software bug.
--- Additional comment from GV on 2018-10-03 13:00:48 SGT ---
Of course OOM is not a software bug. Where exactly did I said that?
The problem is texttopaps that allocate memory out of control.
texttopaps should allocate memory, use-it, release-it. Like any sane program.
The issue was not present on RHEL 6. I had printed the same file multiple times
with cups on RHEL6 and it worked just fine (not sure it was texttopaps cups
filter involved). Printing the file does not work on RHEL 7 and it should.
The 4Gb file is a testcase for our application we develop.
--- Additional comment from Jens Petersen on 2018-10-18 17:49:35 SGT ---
I don't think the paps in RHEL7 is significantly different from RHEL6.
As you say it could be due to changes in Cups?
The cups versions in RHEL 6, 7 and Fedora are certainly quite different.
Unless texttopaps really worked in RHEL6 it might make to reassign this to
cups?
--- Additional comment from GV on 2018-10-25 18:29:46 SGT ---
Since the real computer running RHEL 6 was already scrapped, I tried to make a
virtual machine using RHEL 6. Unfortunately, now I also get a crash on RHEL 6
when printing the 4GB file. I can't recall how much memory was in that
computer. The virtual machine had 8Gb of memory allocated.
Still, it does not matter that much.
I think texttopaps have an issue and it should be fixed or at least an
workaround should be available (other than 'don't print a file that large').
I'm afraid this is not a cups issue since I can reproduce the issue running the
texttopaps standalone.
Sincerely,
Gabriel
--- Additional comment from Akira TAGOH on 2018-11-16 17:59:04 SGT ---
paps isn't supposed to work with large files. to support it, most of code needs
to rewritten. this isn't realistic to provide an update for existing products.
for a workaround, you can remove paps package (or simply remove
/usr/share/cups/mime/paps.convs file) to fall back the text filter to texttops
which CUPS originally provides. this should works for this issue and as long as
you don't need the internationalization support for printing.
Hope that helps.
--- Additional comment from GV on 2018-12-07 14:03:33 SGT ---
It helps. Thank you!
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1635160
[Bug 1635160] texttopaps OOMs with 4GB text file!
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1703849
Bug ID: 1703849
Summary: [pango] pango-view fails for backend ft2 because of
missing dependency on ImageMagick
Product: Fedora
Version: 29
Hardware: x86_64
OS: Linux
Status: NEW
Component: pango
Assignee: tagoh(a)redhat.com
Reporter: jfrieben(a)hotmail.com
QA Contact: extras-qa(a)fedoraproject.org
CC: caillon+fedoraproject(a)gmail.com,
fonts-bugs(a)lists.fedoraproject.org,
gnome-sig(a)lists.fedoraproject.org,
i18n-bugs(a)lists.fedoraproject.org,
john.j5live(a)gmail.com, mclasen(a)redhat.com,
pwu(a)redhat.com, rhughes(a)redhat.com,
rstrode(a)redhat.com, sandmann(a)redhat.com,
tagoh(a)redhat.com
Target Milestone: ---
Classification: Fedora
Description of problem:
Using pango-view with backend ft2 in a current Fedora 29 Workstation
installation fails because pango-view tries to launch the display utility from
ImageMagick which has not been pulled in as a dependency.
Version-Release number of selected component (if applicable):
pango-1.42.4-2.fc29
How reproducible:
Always
Steps to Reproduce:
1. Launch GNOME session of a current Fedora 29 Workstation installation.
2. Run 'pango-view --backend=ft2 -t PANGO'.
Actual results:
Utility pango-view aborts with the error message:
"pango-view: When running ImageMagick 'display' command: Failed to execute
child process “display” (No such file or directory)"
Expected results:
Utility pango-view displays the sample text.
Additional info:
- Installing package ImageMagick prior to running pango-view ensures correct
execution. Therefore, adding ImageMagick as a requirement of package pango
solves this issue.
- It is probably preferable to patch pango-view such that it calls "gm display"
from package GraphicsMagick and to pull in the latter instead of ImageMagick.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1689745
Bug ID: 1689745
Summary: [abrt] ibus-libpinyin: pinyin_save():
ibus-engine-libpinyin killed by SIGSEGV
Product: Fedora
Version: 30
Hardware: x86_64
Status: NEW
Whiteboard: abrt_hash:cb822be7ac46c50ce113ca1671deec6e2f6c4599;
Component: ibus-libpinyin
Assignee: pwu(a)redhat.com
Reporter: robinlee.sysu(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:
Crash when updating system
Version-Release number of selected component:
ibus-libpinyin-1.11.0-2.fc30
Additional info:
reporter: libreport-2.10.0
backtrace_rating: 4
cmdline: /usr/libexec/ibus-engine-libpinyin --ibus
crash_function: pinyin_save
executable: /usr/libexec/ibus-engine-libpinyin
journald_cursor:
s=cc3b4d7aa103497a99d675649b9ae013;i=94c7;b=13573ad620e541ff8cacc1ad1ceca0c3;m=eea6a32;t=584549ca4b236;x=245f7212fc098115
kernel: 5.0.0-300.fc30.x86_64
rootdir: /
runlevel: N 5
type: CCpp
uid: 1000
Truncated backtrace:
Thread no. 1 (10 frames)
#0 pinyin_save at pinyin.cpp:736
#1 PY::LibPinyinBackEnd::clearPinyinUserData at PYLibPinyin.cc:307
#2 PY::PinyinConfig::valueChanged at
/usr/include/c++/9/bits/basic_string.h:2297
#3 PY::LibPinyinConfig::valueChangedCallback at
/usr/include/c++/9/bits/char_traits.h:300
#8 g_settings_real_change_event at ../gio/gsettings.c:391
#9 ffi_call_unix64 at ../src/x86/unix64.S:76
#10 ffi_call at ../src/x86/ffi64.c:525
#11 g_cclosure_marshal_generic_va at ../gobject/gclosure.c:1614
#12 _g_closure_invoke_va at ../gobject/gclosure.c:873
#15 settings_backend_path_changed at ../gio/gsettings.c:466
Potential duplicate: bug 1649100
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1672442
Bug ID: 1672442
Summary: Bug that will not accept input from keyboard
Product: Fedora
Version: 29
OS: Linux
Status: NEW
Component: ibus
Severity: medium
Assignee: tfujiwar(a)redhat.com
Reporter: qqke6wd9k(a)apricot.ocn.ne.jp
QA Contact: extras-qa(a)fedoraproject.org
CC: i18n-bugs(a)lists.fedoraproject.org,
shawn.p.huang(a)gmail.com, tfujiwar(a)redhat.com
Target Milestone: ---
Classification: Fedora
Description of problem:
When I input characters, sometimes this bug occurs, the PC will not accept
input from the keyboard morever. Since it accepts mouse operation, logout and
shutdown are possible.
When I log out and re-login, PC is able to accept only direct input (English).
Also, the IME icon on the task bar is lost. It will also be impossible to
switch input modes.
I am a Japanese user, but when after login, I cannot enter Japanese characters.
After this bug occurrence, only English characters can be entered.
Version-Release number of selected component (if applicable):
How reproducible:
everyday
Steps to Reproduce:
1.Open an application that can enter letters (eg gedit or Firefox)
2.keep typing characters until this bug occurs.
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=1660522
Bug ID: 1660522
Summary: [abrt] ibus-anthy-python:
__update_anthy_convert_chars():
engine.py:1269:__update_anthy_convert_chars:TypeError:
can only concatenate str (not "NoneType") to str
Product: Fedora
Version: 29
Hardware: x86_64
Status: NEW
Whiteboard: abrt_hash:68516d1ac979ea4a4ef53d1d33c98a5060591dde;VAR
IANT_ID=workstation;
Component: ibus-anthy
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, tagoh(a)redhat.com,
tfujiwar(a)redhat.com
Target Milestone: ---
Classification: Fedora
Version-Release number of selected component:
ibus-anthy-python-1.5.10-5.fc29
Additional info:
reporter: libreport-2.9.7
cmdline: python3 /usr/share/ibus-anthy/engine/main.py --ibus
crash_function: __update_anthy_convert_chars
exception_type: TypeError
executable: /usr/share/ibus-anthy/engine/main.py
interpreter: python3-3.7.1-4.fc29.x86_64
kernel: 4.19.5-300.fc29.x86_64
runlevel: N 5
type: Python3
uid: 10030
Truncated backtrace:
engine.py:1269:__update_anthy_convert_chars:TypeError: can only concatenate str
(not "NoneType") to str
Traceback (most recent call last):
File "/usr/share/ibus-anthy/engine/engine.py", line 1290, in __update
self.__update_convert_chars()
File "/usr/share/ibus-anthy/engine/engine.py", line 1213, in
__update_convert_chars
self.__update_anthy_convert_chars()
File "/usr/share/ibus-anthy/engine/engine.py", line 1269, in
__update_anthy_convert_chars
self.__convert_chars += text
TypeError: can only concatenate str (not "NoneType") to str
Local variables in innermost frame:
self: <engine.Engine object at 0x7f74fce16630 (engine+Engine at
0x558e39add170)>
pos: 0
i: 0
seg_index: -1
text: None
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1665761
Bug ID: 1665761
Summary: [abrt] imsettings: g_mutex_lock(): imsettings-daemon
killed by SIGSEGV
Product: Fedora
Version: 29
Hardware: x86_64
Status: NEW
Whiteboard: abrt_hash:306ca4522cde8dfac2023cfb1322a1924c487273;
Component: imsettings
Assignee: tagoh(a)redhat.com
Reporter: joaomfloriano(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:
I logged into Fedora and its error sequence was reported. I did not run or open
any application
Version-Release number of selected component:
imsettings-1.7.3-6.fc29
Additional info:
reporter: libreport-2.9.7
backtrace_rating: 4
cmdline: /usr/libexec/imsettings-daemon
crash_function: g_mutex_lock
executable: /usr/libexec/imsettings-daemon
journald_cursor:
s=79f49ceccf4744e99f013bda7b2b469e;i=6e1;b=35544eed6b7b4c5591e1c02456652103;m=1185506c;t=57f5ce41b707e;x=50618820333031c0
kernel: 4.19.13-300.fc29.x86_64
rootdir: /
runlevel: N 5
type: CCpp
uid: 1000
Truncated backtrace:
Thread no. 1 (10 frames)
#0 g_mutex_lock at gthread-posix.c:1343
#1 xfconf_cache_set_property_reply_handler at xfconf-cache.c:608
#2 g_task_return_now at gtask.c:1148
#3 g_task_return at gtask.c:1206
#4 reply_cb at gdbusproxy.c:2586
#5 g_task_return_now at gtask.c:1148
#6 g_task_return at gtask.c:1206
#7 g_dbus_connection_call_done at gdbusconnection.c:5713
#8 g_task_return_now at gtask.c:1148
#9 complete_in_idle_cb at gtask.c:1162
--
You are receiving this mail because:
You are on the CC list for the bug.