[Fedora-i18n-bugs] [Bug 1299596] New: [abrt] w3m: deleteFiles(): w3m killed by SIGSEGV
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1299596
Bug ID: 1299596
Summary: [abrt] w3m: deleteFiles(): w3m killed by SIGSEGV
Product: Fedora
Version: 23
Component: w3m
Assignee: pnemade(a)redhat.com
Reporter: xzj8b3(a)gmail.com
QA Contact: extras-qa(a)fedoraproject.org
CC: i18n-bugs(a)lists.fedoraproject.org, pnemade(a)redhat.com
Version-Release number of selected component:
w3m-0.5.3-22.fc23
Additional info:
reporter: libreport-2.6.3
backtrace_rating: 4
cmdline: w3m chimerarevo.com
crash_function: deleteFiles
executable: /usr/bin/w3m
global_pid: 3059
kernel: 4.3.3-300.fc23.x86_64
runlevel: N 5
type: CCpp
uid: 1000
Truncated backtrace:
Thread no. 1 (6 frames)
#0 deleteFiles at main.c:5746
#1 w3m_exit at main.c:5760
#3 pthread_cond_wait@(a)GLIBC_2.3.2 at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:183
#4 GC_wait_marker at pthread_support.c:2036
#5 GC_help_marker at mark.c:1168
#6 GC_mark_thread at pthread_support.c:389
--
You are receiving this mail because:
You are on the CC list for the bug.
7 years, 8 months
[Fedora-i18n-bugs] [Bug 1366533] New: [abrt] ibus-libpinyin: pinyin:: compute_pronunciation_possibility(): ibus-engine-libpinyin killed by SIGABRT
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1366533
Bug ID: 1366533
Summary: [abrt] ibus-libpinyin:
pinyin::compute_pronunciation_possibility():
ibus-engine-libpinyin killed by SIGABRT
Product: Fedora
Version: 24
Component: ibus-libpinyin
Assignee: pwu(a)redhat.com
Reporter: frank722(a)163.com
QA Contact: extras-qa(a)fedoraproject.org
CC: i18n-bugs(a)lists.fedoraproject.org, lijli(a)redhat.com,
petersen(a)redhat.com, pwu(a)redhat.com
Description of problem:
the fixed application is still unstable. It's crashed randomly
Version-Release number of selected component:
ibus-libpinyin-1.7.92-2.fc24
Additional info:
reporter: libreport-2.7.2
backtrace_rating: 4
cmdline: /usr/libexec/ibus-engine-libpinyin --ibus
crash_function: pinyin::compute_pronunciation_possibility
executable: /usr/libexec/ibus-engine-libpinyin
global_pid: 2029
kernel: 4.6.5-300.fc24.x86_64
pkg_vendor: Fedora Project
runlevel: N 5
type: CCpp
uid: 1000
Truncated backtrace:
Thread no. 1 (10 frames)
#4 pinyin::compute_pronunciation_possibility at phonetic_key_matrix.cpp:501
#5 pinyin::PinyinLookup2::validate_constraint at pinyin_lookup2.cpp:759
#6 pinyin_update_constraints at pinyin.cpp:1074
#7 pinyin_guess_sentence at pinyin.cpp:1087
#8 PY::PhoneticEditor::removeCharBefore at PYPPhoneticEditor.cc:439
#9 PY::PhoneticEditor::processFunctionKey at PYPPhoneticEditor.cc:82
#10 PY::PinyinEngine::processKeyEvent at PYPPinyinEngine.cc:223
#11 _ibus_marshal_BOOLEAN__UINT_UINT_UINT at ibusmarshalers.c:290
#16 ibus_engine_service_method_call at ibusengine.c:883
#17 call_in_idle_cb at gdbusconnection.c:4832
--
You are receiving this mail because:
You are on the CC list for the bug.
7 years, 8 months
[Fedora-i18n-bugs] [Bug 1364642] New: [abrt] ibus-libpinyin: pinyin_get_character_offset(): ibus-engine-libpinyin killed by SIGABRT
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1364642
Bug ID: 1364642
Summary: [abrt] ibus-libpinyin: pinyin_get_character_offset():
ibus-engine-libpinyin killed by SIGABRT
Product: Fedora
Version: 24
Component: ibus-libpinyin
Assignee: pwu(a)redhat.com
Reporter: tcfxfzoi(a)gmail.com
QA Contact: extras-qa(a)fedoraproject.org
CC: i18n-bugs(a)lists.fedoraproject.org, lijli(a)redhat.com,
petersen(a)redhat.com, pwu(a)redhat.com
Version-Release number of selected component:
ibus-libpinyin-1.7.92-1.fc24
Additional info:
reporter: libreport-2.7.2
backtrace_rating: 4
cmdline: /usr/libexec/ibus-engine-libpinyin --ibus
crash_function: pinyin_get_character_offset
executable: /usr/libexec/ibus-engine-libpinyin
global_pid: 2029
kernel: 4.6.4-301.fc24.x86_64
pkg_fingerprint: 73BD E983 81B4 6521
pkg_vendor: Fedora Project
runlevel: N 5
type: CCpp
uid: 1000
Truncated backtrace:
Thread no. 1 (10 frames)
#4 pinyin_get_character_offset at pinyin.cpp:2533
#5 PY::BopomofoEditor::updatePreeditText at PYPBopomofoEditor.cc:332
#6 PY::PhoneticEditor::update at PYPPhoneticEditor.cc:342
#7 PY::BopomofoEditor::insert at PYPBopomofoEditor.cc:74
#8 PY::BopomofoEditor::processBopomofo at PYPBopomofoEditor.cc:184
#9 PY::BopomofoEditor::processKeyEvent at PYPBopomofoEditor.cc:206
#10 PY::BopomofoEngine::processKeyEvent at PYPBopomofoEngine.cc:153
#11 _ibus_marshal_BOOLEAN__UINT_UINT_UINT at ibusmarshalers.c:290
#16 ibus_engine_service_method_call at ibusengine.c:883
#17 call_in_idle_cb at gdbusconnection.c:4832
--
You are receiving this mail because:
You are on the CC list for the bug.
7 years, 8 months
[Fedora-i18n-bugs] [Bug 1356642] New: Po-send-mail in po-mode doesn't work with emacs 25
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1356642
Bug ID: 1356642
Summary: Po-send-mail in po-mode doesn't work with emacs 25
Product: Fedora
Version: 24
Component: gettext
Assignee: dueno(a)redhat.com
Reporter: goeran(a)uddeborg.se
QA Contact: extras-qa(a)fedoraproject.org
CC: dueno(a)redhat.com, i18n-bugs(a)lists.fedoraproject.org,
petersen(a)redhat.com, praiskup(a)redhat.com
Description of problem:
After upgrading to the emacs version of F25, po-send-mail no longer works.
Normally it creates a buffer with an appropriate e-mail header and a base64
encoded body. But now the entire buffer gets base64 encoded. Not
surprisingly, the mail functions don't know what to do with that afterwards.
I believe this is because of the use of "(region-beginning)" near line 3525 in
po-mode.el. Probably something that used to set the mark in previous emacs
version doesn't do so any more, or possibly the other way around. To fix this,
I changed the save-excursion part of the function to look like below. That
appears to make things work again. Someone with more emacs lisp skills than I
have is welcome to comment if this is a good way to do it.
(save-excursion
(let
((beginning (point)))
(insert-buffer-substring buffer)
(shell-command-on-region
beginning (region-end)
(concat po-gzip-uuencode-command " " name ".gz") t t)))))))
Version-Release number of selected component (if applicable):
emacs-25.0.94-1.fc24.x86_64
emacs-gettext-0.19.8.1-1.fc24.noarch
How reproducible:
Every time
Steps to Reproduce:
1. Open a po file in emacs
2. Hit "M"
3. Answer the questions
Actual results:
A buffer completely base64 encoded.
Expected results:
A buffer with a legal mail header, and a base64 encoded body.
Additional info:
I've sent this report upstreams too:
http://lists.gnu.org/archive/html/bug-gettext/2016-07/msg00027.html
--
You are receiving this mail because:
You are on the CC list for the bug.
7 years, 8 months