[Fedora-i18n-bugs] [Bug 1330162] New: [abrt] ibus: _g_log_abort(): ibus-ui-gtk3 killed by SIGTRAP
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1330162
Bug ID: 1330162
Summary: [abrt] ibus: _g_log_abort(): ibus-ui-gtk3 killed by
SIGTRAP
Product: Fedora
Version: 24
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
Version-Release number of selected component:
ibus-1.5.13-1.fc24
Additional info:
reporter: libreport-2.7.0
backtrace_rating: 4
cmdline: /usr/libexec/ibus-ui-gtk3
crash_function: _g_log_abort
executable: /usr/libexec/ibus-ui-gtk3
global_pid: 12788
kernel: 4.5.1-300.fc24.x86_64
pkg_fingerprint: 73BD E983 81B4 6521
pkg_vendor: Fedora Project
reproducible: Not sure how to reproduce the problem
runlevel: N 5
type: CCpp
uid: 1000
Truncated backtrace:
Thread no. 1 (9 frames)
#0 _g_log_abort at gmessages.c:325
#8 _XEventsQueued at xcb_io.c:364
#9 XPending at Pending.c:55
#10 gdk_check_xpending at gdkeventsource.c:271
#11 gdk_event_source_check at gdkeventsource.c:308
#12 g_main_context_check at gmain.c:3681
#15 gtk_main at gtkmain.c:1266
#16 application_run at application.c:199
#17 application_main at application.c:269
--
You are receiving this mail because:
You are on the CC list for the bug.
7 years, 11 months
[Fedora-i18n-bugs] [Bug 1297185] New: [abrt] ibus: bus_dbus_impl_name_owner_changed():
ibus-daemon killed by SIGABRT
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1297185
Bug ID: 1297185
Summary: [abrt] ibus: bus_dbus_impl_name_owner_changed():
ibus-daemon killed by SIGABRT
Product: Fedora
Version: rawhide
Component: ibus
Assignee: tfujiwar(a)redhat.com
Reporter: belcocco(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
Description of problem:
0)There are on my system two DE: Gnome and Cinnamon and one user.
1) Exit from Cinnamon Session and enter on Gnome session with the same user.
2) Appared "Oops, ......."
Version-Release number of selected component:
ibus-1.5.11-2.fc24
Additional info:
reporter: libreport-2.6.3
backtrace_rating: 4
cmdline: /usr/bin/ibus-daemon -r --xim
crash_function: bus_dbus_impl_name_owner_changed
executable: /usr/bin/ibus-daemon
global_pid: 2870
kernel: 4.4.0-0.rc6.git1.1.fc24.x86_64
runlevel: N 5
type: CCpp
uid: 1000
Truncated backtrace:
Thread no. 1 (9 frames)
#4 bus_dbus_impl_name_owner_changed at dbusimpl.c:1243
#9 bus_name_service_remove_owner at dbusimpl.c:457
#10 bus_dbus_impl_connection_destroy_cb at dbusimpl.c:1648
#15 ibus_object_dispose at ibusobject.c:135
#17 ffi_call_unix64 at ../src/x86/unix64.S:76
#18 ffi_call at ../src/x86/ffi64.c:525
#19 g_cclosure_marshal_generic at gclosure.c:1490
#24 emit_closed_in_idle at gdbusconnection.c:1357
#29 bus_server_run at server.c:143
Potential duplicate: bug 890645
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=2CEt7jPzIa&a=cc_unsubscribe
7 years, 11 months
[Fedora-i18n-bugs] [Bug 1288741] New: [abrt] ibus: bus_dbus_impl_connection_filter_cb(): ibus-daemon killed by SIGABRT
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1288741
Bug ID: 1288741
Summary: [abrt] ibus: bus_dbus_impl_connection_filter_cb():
ibus-daemon killed by SIGABRT
Product: Fedora
Version: 22
Component: ibus
Assignee: tfujiwar(a)redhat.com
Reporter: wallacehermano(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
Version-Release number of selected component:
ibus-1.5.10-5.fc22
Additional info:
reporter: libreport-2.6.3
backtrace_rating: 4
cmdline: ibus-daemon --xim --panel disable
crash_function: bus_dbus_impl_connection_filter_cb
executable: /usr/bin/ibus-daemon
global_pid: 2239
kernel: 4.2.6-201.fc22.x86_64
runlevel: N 5
type: CCpp
uid: 1000
Truncated backtrace:
Thread no. 1 (10 frames)
#4 bus_dbus_impl_connection_filter_cb at dbusimpl.c:1473
#5 on_worker_message_about_to_be_sent at gdbusconnection.c:2429
#6 _g_dbus_worker_emit_message_about_to_be_sent at gdbusprivate.c:498
#7 continue_writing at gdbusprivate.c:1501
#8 write_message_cb at gdbusprivate.c:1356
#9 g_simple_async_result_complete at gsimpleasyncresult.c:763
#10 write_message_continue_writing at gdbusprivate.c:1070
#11 write_message_async at gdbusprivate.c:1136
#12 continue_writing at gdbusprivate.c:1541
#13 write_message_cb at gdbusprivate.c:1356
Potential duplicate: bug 906086
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=6lvN5u4FnC&a=cc_unsubscribe
7 years, 11 months
[Fedora-i18n-bugs] [Bug 1279137] New: [abrt] system-config-language: install_packages3.py:291:install_language_packages:AttributeError: 'CalledProcessError' object has no attribute 'message'
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1279137
Bug ID: 1279137
Summary: [abrt] system-config-language:
install_packages3.py:291:install_language_packages:Att
ributeError: 'CalledProcessError' object has no
attribute 'message'
Product: Fedora
Version: 23
Component: system-config-language
Assignee: pnemade(a)redhat.com
Reporter: paulim.hardware(a)gmail.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
Version-Release number of selected component:
system-config-language-3.3.0-1.fc23
Additional info:
reporter: libreport-2.6.3
cmdline: /usr/bin/python3
/usr/share/system-config-language/system-config-language.py
executable: /usr/share/system-config-language/system-config-language.py
kernel: 4.2.5-300.fc23.x86_64
runlevel: N 5
type: Python3
uid: 0
Truncated backtrace:
install_packages3.py:291:install_language_packages:AttributeError:
'CalledProcessError' object has no attribute 'message'
Traceback (most recent call last):
File "/usr/share/system-config-language/install_packages3.py", line 288, in
install_language_packages
subprocess.check_output(cmd, shell=True)
File "/usr/lib64/python3.4/subprocess.py", line 620, in check_output
raise CalledProcessError(retcode, process.args, output=output)
subprocess.CalledProcessError: Command 'dnf langinstall -y pt_BR' returned
non-zero exit status 1
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/share/system-config-language/language_gui.py", line 308, in ok_btn
installed = self.instpkg.install_packages3(dlang)
File "/usr/share/system-config-language/install_packages3.py", line 275, in
install_packages3
ret = self.install_language_packages(langcode)
File "/usr/share/system-config-language/install_packages3.py", line 291, in
install_language_packages
print(e.message)
AttributeError: 'CalledProcessError' object has no attribute 'message'
Local variables in innermost frame:
cls: <class 'install_packages3.InstallLangpack'>
langcode: 'pt_BR'
cmd: 'dnf langinstall -y pt_BR'
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=fGMvZRpnQW&a=cc_unsubscribe
7 years, 11 months
[Fedora-i18n-bugs] [Bug 1339261] New: Not able to use software shortcuts
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1339261
Bug ID: 1339261
Summary: Not able to use software shortcuts
Product: Fedora
Version: 23
Component: xkeyboard-config
Assignee: peter.hutterer(a)redhat.com
Reporter: 8tomat8(a)gmail.com
QA Contact: extras-qa(a)fedoraproject.org
CC: i18n-bugs(a)lists.fedoraproject.org,
negativo17(a)gmail.com, peter.hutterer(a)redhat.com
Description of problem:
I use Shift+Ctrl to switch layout. But system "catches" my shortcut event, and
if I want use Shift+Ctrl+T in Terminal (to open a new tab) – it switches layout
and sends to terminal Ctrl+T.
Version-Release number of selected component (if applicable):
Bug was founded in 22 and 23 versions, and in some Debian systems(now fixed)
Desktop: Cinnamon 3.0.1, xfce 4.12
How reproducible:
1. Set "Shift+Ctrl" to switch layout.
2. Open Terminal Emulator
3. Press Shift+Ctrl+T
Actual results:
No new tab was opened.
Expected results:
New tab.
Additional info:
Same bug can be reproducible in any other software that use layout switch
buttons in there own combinations.
I have this problem in Sublime when try to use rectangle selection.
--
You are receiving this mail because:
You are on the CC list for the bug.
7 years, 11 months
[Fedora-i18n-bugs] [Bug 1169979] New: Some fonts not in fontconfig cache on Fedora 21 live images
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1169979
Bug ID: 1169979
Summary: Some fonts not in fontconfig cache on Fedora 21 live
images
Product: Fedora
Version: 21
Component: fontconfig
Assignee: tagoh(a)redhat.com
Reporter: awilliam(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: fonts-bugs(a)lists.fedoraproject.org,
i18n-bugs(a)lists.fedoraproject.org, pnemade(a)redhat.com,
tagoh(a)redhat.com
We've spotted an issue with Fedora 21 live images where some installed fonts
appear to be missing from the fontconfig cache in the live environment. An
'fc-cache -f' fixes this. For instance, on the Fedora 21 Final RC2 Workstation
x86_64 live:
[root@localhost liveuser]# fc-list | wc -l
141
[root@localhost liveuser]# fc-cache --force
[root@localhost liveuser]# fc-list | wc -l
159
The specific fonts that are missing on that image are:
/usr/share/fonts/dejavu/DejaVuSansMono-BoldOblique.ttf: DejaVu Sans
Mono:style=Bold Oblique
/usr/share/fonts/dejavu/DejaVuSansMono-Bold.ttf: DejaVu Sans Mono:style=Bold
/usr/share/fonts/dejavu/DejaVuSansMono-Oblique.ttf: DejaVu Sans
Mono:style=Oblique
/usr/share/fonts/dejavu/DejaVuSansMono.ttf: DejaVu Sans Mono:style=Book
/usr/share/fonts/dejavu/DejaVuSerif-BoldItalic.ttf: DejaVu Serif:style=Bold
Italic
/usr/share/fonts/dejavu/DejaVuSerif-Bold.ttf: DejaVu Serif:style=Bold
/usr/share/fonts/dejavu/DejaVuSerifCondensed-BoldItalic.ttf: DejaVu
Serif,DejaVu Serif Condensed:style=Condensed Bold Italic,Bold Italic
/usr/share/fonts/dejavu/DejaVuSerifCondensed.ttf: DejaVu Serif,DejaVu Serif
Condensed:style=Condensed,Book
/usr/share/fonts/dejavu/DejaVuSerif-Italic.ttf: DejaVu Serif:style=Italic
/usr/share/fonts/dejavu/DejaVuSerif.ttf: DejaVu Serif:style=Book
/usr/share/fonts/google-noto/NotoSansTagalog-Regular.ttf: Noto Sans
Tagalog:style=Regular
/usr/share/fonts/google-noto/NotoSansTaiViet-Regular.ttf: Noto Sans Tai
Viet:style=Regular
/usr/share/fonts/liberation/LiberationSerif-BoldItalic.ttf: Liberation
Serif:style=Bold Italic
/usr/share/fonts/liberation/LiberationSerif-Bold.ttf: Liberation
Serif:style=Bold
/usr/share/fonts/liberation/LiberationSerif-Italic.ttf: Liberation
Serif:style=Italic
/usr/share/fonts/liberation/LiberationSerif-Regular.ttf: Liberation
Serif:style=Regular
The log of the compose is here:
https://kojipkgs.fedoraproject.org//work/tasks/5463/8275463/root.log
In comparison, the i686 Workstation live is 'missing' only
/usr/share/fonts/google-noto/NotoSansTaiViet-Regular.ttf: Noto Sans Tai
Viet:style=Regular
its compose log is here:
https://kojipkgs.fedoraproject.org//work/tasks/5460/8275460/root.log
to me, it appears the affected cases are ones where more than one package
contains fonts in the same directory, for packages installed *after* the
fontconfig package. The fontconfig package has an 'fc-cache -f' in its %post,
so any inconsistencies that exist before it's installed get fixed by that.
My first thesis was 'for any given directory, only fonts from the first package
installed after fontconfig will make it to the cache, fonts in the same
directory from subsequently-installed packages won't be added'. But it doesn't
seem to be that simple, because some fonts in /usr/share/fonts/google-noto
*are* added - the first 'noto' package installed is google-noto-sans-lisu-fonts
, and after that several more noto packages are installed. The fonts from
google-noto-sans-mandaic-fonts, google-noto-sans-meeteimayek-fonts , and
google-noto-sans-tai-tham-fonts *do* get added to the cache - but the fonts
from google-noto-sans-tagalog-fonts and google-noto-sans-tai-viet-fonts do
*not* get added. It's quite odd.
This is a fairly bad bug because of its impact on DejaVu Sans Mono: this is the
default monospace font for both Workstation and KDE (and I think the
non-blocking spins too). Its absence from the cache results in them using
Nimbus Mono L as their monospace fonts, which is a pretty crappy font, ugly and
hard to read. The workaround is easy once you know it, but if you don't, you
just think we have a really bad font.
There's an easy big hammer workaround we can use for a quick rebuild of the RC2
lives, if we like:
--- a/fedora-live-base.ks
+++ b/fedora-live-base.ks
@@ -299,6 +299,12 @@ rm -f /core*
# convince readahead not to collect
# FIXME: for systemd
+# forcibly regenerate fontconfig cache (so long as this live image has
+# fontconfig) - see #XXXXXXX
+if [ -x /usr/bin/fc-cache ] ; then
+ fc-cache -f
+fi
+
%end
i.e., just do an fc-cache -f at the end of live generation %post. I've tested
that locally, and it works, the generated Workstation image has 159 fonts in
fc-list (I also generated an image with the exact same config and build host,
but no change to spin-kickstarts, to verify that it reproduced the bug, and it
does).
The real fix should likely be in fc-cache, but the spin-kickstarts workaround
would solve this problem for F21.
I think fc-cache's behaviour must have changed between F20 and F21, as F20
doesn't appear to be affected by this at all, at least not the x86_64 desktop
live. All F21 images I've tested seem to be affected to some extent, though the
exact affected fonts vary depending on the package install order that yum
decided on.
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=Ex4RiyuuM1&a=cc_unsubscribe
7 years, 11 months
[Fedora-i18n-bugs] [Bug 1319403] New: [RFE] ibus-chewing: New option: Caps Lock behavior
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1319403
Bug ID: 1319403
Summary: [RFE] ibus-chewing: New option: Caps Lock behavior
Product: Fedora
Version: rawhide
Component: ibus-chewing
Assignee: dchen(a)redhat.com
Reporter: dchen(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: dchen(a)redhat.com, i18n-bugs(a)lists.fedoraproject.org,
shawn.p.huang(a)gmail.com
Description of problem:
Currently in ibus-chewing, Caps Lock toggle English/Chinese.
However, in English environment, some users use Caps Lock to toggle upper/lower
case, and wish to keep this muscle memory in ibus-chewing English mode.
Version-Release number of selected component (if applicable):
1.4.14
Proposed Changes:
Add two options:
1. Caps Lock toggles Chinese Mode (boolean) Default: On
2. Letter case in English mode (Only enabled when Caps Lock toggle Chinese is
on)
a. Determine by Caps Lock state (Default)
b. Lowercase
c. Uppercase
Remove one option:
Force lowercase in En mode. Because it should be obsoleted by the new option
2.
--
You are receiving this mail because:
You are on the CC list for the bug.
7 years, 11 months
[Fedora-i18n-bugs] [Bug 1330194] New: Ctrl-c failed to output as Ctrl-c
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1330194
Bug ID: 1330194
Summary: Ctrl-c failed to output as Ctrl-c
Product: Fedora
Version: rawhide
Component: ibus-chewing
Severity: high
Assignee: dchen(a)redhat.com
Reporter: dchen(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: dchen(a)redhat.com, i18n-bugs(a)lists.fedoraproject.org,
shawn.p.huang(a)gmail.com
Description of problem:
Regardless with English or Chinese mode, the Ctrl-c was outputted as c
Version-Release number of selected component (if applicable):
1.5.0-SNAPSHOT
How reproducible:
Always
Steps to Reproduce:
1. Press Ctrl-c
2.
3.
Actual results:
"c" is outputed
Expected results:
Pass as Ctrl-c
Additional info:
--
You are receiving this mail because:
You are on the CC list for the bug.
7 years, 11 months