i18n-bugs November 2016

i18n-bugs@lists.fedoraproject.org

2 participants
185 discussions

[Fedora-i18n-bugs] [Bug 1326156] New: kernel hung when using fbterm on vmware workstation 12
by Red Hat Bugzilla 20 Dec '16

20 Dec '16

https://bugzilla.redhat.com/show_bug.cgi?id=1326156 Bug ID: 1326156 Summary: kernel hung when using fbterm on vmware workstation 12 Product: Fedora Version: 23 Component: fbterm Severity: high Assignee: bazanluis20(a)gmail.com Reporter: kuro(a)adm.tamagawa.ac.jp QA Contact: extras-qa(a)fedoraproject.org CC: bazanluis20(a)gmail.com, dchen(a)redhat.com, i18n-bugs(a)lists.fedoraproject.org, tfujiwar(a)redhat.com Description of problem: kernel hung up when using fbterm on vmware workstation 12 Version-Release number of selected component (if applicable): fbterm 1.7-7.fc23.x86_64 kernel 4.4.6-301.fc23 How reproducible: yes Steps to Reproduce: 1.login console 2.run fbterm 3.run find / -print Actual results: kernel hung up when printing find command result. Expected results: find command complete. Additional info: Kernel 4.2.300 is not hung up,but fbterm display is not correctly. I also test virtualbox with kernel 4.4.6-301,but not reproducible. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Fedora-i18n-bugs] [Bug 1324864] New: [abrt] ibus-gucharmap: character_to_iter(): ibus-engine-gucharmap killed by SIGSEGV
by Red Hat Bugzilla 20 Dec '16

20 Dec '16

https://bugzilla.redhat.com/show_bug.cgi?id=1324864 Bug ID: 1324864 Summary: [abrt] ibus-gucharmap: character_to_iter(): ibus-engine-gucharmap killed by SIGSEGV Product: Fedora Version: 23 Component: ibus-gucharmap Assignee: dueno(a)redhat.com Reporter: perso(a)hack-libre.org QA Contact: extras-qa(a)fedoraproject.org CC: dueno(a)redhat.com, i18n-bugs(a)lists.fedoraproject.org Description of problem: I just tried to use ibus-gucharmap and it didn't work. Version-Release number of selected component: ibus-gucharmap-1.4.0-12.fc23 Additional info: reporter: libreport-2.6.4 backtrace_rating: 4 cmdline: /usr/libexec/ibus-engine-gucharmap --ibus crash_function: character_to_iter executable: /usr/libexec/ibus-engine-gucharmap global_pid: 2412 kernel: 4.4.6-300.fc23.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 character_to_iter at gucharmap-block-chapters-model.c:120 #1 ibus_gucharmap_charmap_panel_real_activate_character at charmap-panel.c:468 #2 g_cclosure_marshal_VOID__FLAGSv at gmarshal.c:1570 #3 _g_closure_invoke_va at gclosure.c:864 #5 g_signal_emit_by_name at gsignal.c:3479 #6 ibus_gucharmap_charmap_panel_construct at charmap-panel.c:440 #7 ibus_gucharmap_charmap_panel_new at charmap-panel.c:453 #8 ibus_gucharmap_engine_constructor at engine.c:609 #9 g_object_new_with_custom_constructor at gobject.c:1697 #10 g_object_new_internal at gobject.c:1777 -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Fedora-i18n-bugs] [Bug 1310625] New: [abrt] ibus-mozc: __fdelt_chk(): ibus-engine-mozc killed by SIGABRT
by Red Hat Bugzilla 20 Dec '16

20 Dec '16

https://bugzilla.redhat.com/show_bug.cgi?id=1310625 Bug ID: 1310625 Summary: [abrt] ibus-mozc: __fdelt_chk(): ibus-engine-mozc killed by SIGABRT Product: Fedora Version: 23 Component: mozc Assignee: tagoh(a)redhat.com Reporter: franchukrom(a)gmail.com QA Contact: extras-qa(a)fedoraproject.org CC: i18n-bugs(a)lists.fedoraproject.org, tagoh(a)redhat.com Description of problem: I have the following setup: * English keyboard layout * Ukrainian keyboard layout * Japanese IME (mozc) The crash happened when trying to switch to Japanese IME in Skype. I don't think I'll be able to reproduce it again, or that it will reproduce on another system this way. Version-Release number of selected component: ibus-mozc-2.17.2077.102-5.fc23 Additional info: reporter: libreport-2.6.4 backtrace_rating: 4 cmdline: /usr/libexec/ibus-engine-mozc --ibus crash_function: __fdelt_chk executable: /usr/libexec/ibus-engine-mozc global_pid: 3606 kernel: 4.3.4-300.fc23.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (8 frames) #5 __fdelt_chk at fdelt_chk.c:25 #6 mozc::(anonymous namespace)::IsWriteTimeout at ../../ipc/unix_ipc.cc:108 #7 mozc::(anonymous namespace)::SendMessage(int, const char *, size_t, int, enum mozc::IPCErrorType *) at ../../ipc/unix_ipc.cc:157 #8 mozc::IPCClient::Call at ../../ipc/unix_ipc.cc:328 #9 mozc::renderer::(anonymous namespace)::CallCommand at ../../renderer/renderer_client.cc:76 #10 mozc::renderer::RendererLauncher::FlushPendingCommand at ../../renderer/renderer_client.cc:283 #11 mozc::renderer::RendererLauncher::Run at ../../renderer/renderer_client.cc:183 #12 mozc::Thread::WrapperForPOSIX at ../../base/thread.cc:242 -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Fedora-i18n-bugs] [Bug 1294727] New: [abrt] ibus: _g_log_abort(): ibus-daemon killed by SIGTRAP
by Red Hat Bugzilla 20 Dec '16

20 Dec '16

https://bugzilla.redhat.com/show_bug.cgi?id=1294727 Bug ID: 1294727 Summary: [abrt] ibus: _g_log_abort(): ibus-daemon killed by SIGTRAP Product: Fedora Version: 23 Component: ibus Assignee: tfujiwar(a)redhat.com Reporter: j-amano(a)jamano.org 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.11-1.fc23 Additional info: reporter: libreport-2.6.3 backtrace_rating: 4 cmdline: /usr/bin/ibus-daemon -r --xim crash_function: _g_log_abort executable: /usr/bin/ibus-daemon global_pid: 2010 kernel: 4.2.8-300.fc23.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (7 frames) #0 _g_log_abort at gmessages.c:324 #3 ik_source_read_some_events at inotify-kernel.c:156 #4 ik_source_read_all_the_events at inotify-kernel.c:172 #5 ik_source_dispatch at inotify-kernel.c:247 #9 g_main_context_iteration at gmain.c:3901 #10 glib_worker_main at gmain.c:5672 #11 g_thread_proxy at gthread.c:778 -- 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=XGYUwaGiDV&a=cc_unsubscribe

1 3

[Fedora-i18n-bugs] [Bug 1290660] New: trackpoint doesn't work on thinkpad x1 carbon 3rd generation
by Red Hat Bugzilla 20 Dec '16

20 Dec '16

https://bugzilla.redhat.com/show_bug.cgi?id=1290660 Bug ID: 1290660 Summary: trackpoint doesn't work on thinkpad x1 carbon 3rd generation Product: Fedora Version: 23 Component: input-pad Assignee: tfujiwar(a)redhat.com Reporter: lnie(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: i18n-bugs(a)lists.fedoraproject.org, tfujiwar(a)redhat.com Description of problem: I just did a fresh f23 installation on my thinkpad,and found out the trackpoint doesn't work at all. This bug really brings lots of inconveniences to me, as I always use the trackpoint Version-Release number of selected component (if applicable): f23 How reproducible: always 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. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=X34crGu8Tn&a=cc_unsubscribe

1 5

[Fedora-i18n-bugs] [Bug 1258924] New: [abrt] ibus-m17n: ibus_config_get_values(): ibus-setup-m17n killed by SIGABRT
by Red Hat Bugzilla 20 Dec '16

20 Dec '16

https://bugzilla.redhat.com/show_bug.cgi?id=1258924 Bug ID: 1258924 Summary: [abrt] ibus-m17n: ibus_config_get_values(): ibus-setup-m17n killed by SIGABRT Product: Fedora Version: 23 Component: ibus-m17n Assignee: dueno(a)redhat.com Reporter: mfabian(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: dueno(a)redhat.com, i18n-bugs(a)lists.fedoraproject.org, shawn.p.huang(a)gmail.com Version-Release number of selected component: ibus-m17n-1.3.4-19.fc23 Additional info: reporter: libreport-2.6.2 backtrace_rating: 4 cmdline: /usr/libexec/ibus-setup-m17n crash_function: ibus_config_get_values executable: /usr/libexec/ibus-setup-m17n global_pid: 15231 kernel: 4.2.0-0.rc8.git0.1.fc23.x86_64+debug runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (3 frames) #4 ibus_config_get_values at ibusconfig.c:476 #5 setup_dialog_load_config at setup.c:319 #6 start at setup.c:635 -- 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=xPMuV94Olm&a=cc_unsubscribe _______________________________________________ i18n-bugs mailing list i18n-bugs(a)lists.fedoraproject.org http://lists.fedoraproject.org/postorius/i18n-bugs@lists.fedoraproject.org

1 4

[Fedora-i18n-bugs] [Bug 1189423] New: Keyboard Layout not persistent through login
by Red Hat Bugzilla 20 Dec '16

20 Dec '16

https://bugzilla.redhat.com/show_bug.cgi?id=1189423 Bug ID: 1189423 Summary: Keyboard Layout not persistent through login Product: Fedora Version: 21 Component: xkeyboard-config Severity: low Assignee: peter.hutterer(a)redhat.com Reporter: nigel(a)nigelpond.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: A second keyboard layout has been defined and is usable/correct when initially logging in. When logged in the keyboard layout reverts to default. The new, desired layout then needs to be selected manually (via the drop-down en1, en2 selector in the top-right-hand corner of the Gnome Desktop) The same problem occurred in Fedora 14: https://bugzilla.redhat.com/show_bug.cgi?id=649604 Interestingly in CentOS 7 the settings menus are the same (there's no place to set a keyboard default) but the problem doesn't occur. I am able to login using my preferred layout and it persists after logging in. Version-Release number of selected component (if applicable): 21 How reproducible: Everytime - on restart/boot the keyboard layout is correct until you login. Steps to Reproduce: 1. Boot/Reboot - login using desired keyboard layout (says en1 - which is incorrect) 2. After successfully logging in the keyboard layout reverts to default (says en1) 3. Set en2 Actual results: Wrong keyboard layout Expected results: Correct keyboard layout (in my case Dvorak International) should persist through login. Additional info: -- 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=nH2jEYUqvE&a=cc_unsubscribe

1 8

[Fedora-i18n-bugs] [Bug 1036220] New: Font hinting and aliasing not properly configured on fresh Fedora 19 install.
by Red Hat Bugzilla 20 Dec '16

20 Dec '16

https://bugzilla.redhat.com/show_bug.cgi?id=1036220 Bug ID: 1036220 Summary: Font hinting and aliasing not properly configured on fresh Fedora 19 install. Product: Fedora Version: 19 Component: fontconfig Severity: high Assignee: tagoh(a)redhat.com Reporter: alxgrtnstrngl(a)gmail.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 Created attachment 830756 --> https://bugzilla.redhat.com/attachment.cgi?id=830756&action=edit These are the configurations for 10-antialias.conf and 10-hinting-slight.conf Description of problem: The fonts in Fedora 19 look odd, thin and the font alignment is totally off resulting in unreadable or very poor quality text. Setting Gnome Shell's or even Mate's anti-aliasing font-configuration here does nothing to enhance text quality. Web-pages in browsers such as Chrome and Firefox look ugly and strange. Other Linux distributions such as Ubuntu and Unixes like Mac OS X do not have this problem, on fresh installs fonts look crisp, beautiful and full. Version-Release number of selected component (if applicable): Fedora release 19 (Schrödinger’s Cat) How reproducible: Do a fresh install of Fedora 19 from the install images, look at the fonts. Steps to Reproduce: 1. Do a fresh install of Fedora 19 from the install images. 2. Attempt to use the desktop environment settings to adjust the font aliasing and hinting. 3. Look at text rendering versus that in other distributions. Actual results: Text is rendered in a very odd and thin way, kerning is also off and the fonts characters are misaligned, in Fedora resulting in a degraded visual experience especially in web-browsers, Expected results: Text should render in a similar beautiful and smooth fashion the way it does on other Linux distributions such as Ubuntu and Unixes such as Mac OS X. Additional info: Manual configuration is required to fix this by creating the proper symbolic links between '/usr/share/fontconfig/conf.avail/' and '/etc/fonts/conf.d' for the following configurations which are installed in 'conf.avail' but just never configured out of the box: '/usr/share/fontconfig/conf.avail/10-sub-pixel-rgb.conf' '/usr/share/fontconfig/conf.avail/11-lcdfilter-default.conf' It also requires the creation of the following two font configurations which are attached to this bug report and the creation of the corresponding symbolic links in '/etc/fonts/conf.d': '/usr/share/fontconfig/conf.avail/10-antialias.conf' '/usr/share/fontconfig/conf.avail/10-hinting-slight.conf' External References: http://ruturaj.net/tweaking-gnome3-fedora-fonts-like-ubuntu/ -- 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=t9AOC1hUH4&a=cc_unsubscribe

1 19

[Fedora-i18n-bugs] [Bug 887384] New: [abrt] WritRecogn-0.1.9-5.fc17: Process /usr/bin/WritRecogn was killed by signal 6 (SIGABRT)
by Red Hat Bugzilla 20 Dec '16

20 Dec '16

Product: Fedora https://bugzilla.redhat.com/show_bug.cgi?id=887384 Bug ID: 887384 Summary: [abrt] WritRecogn-0.1.9-5.fc17: Process /usr/bin/WritRecogn was killed by signal 6 (SIGABRT) Product: Fedora Version: 17 Component: WritRecogn Severity: unspecified Priority: unspecified Reporter: christianvanbrauner(a)gmail.com Version-Release number of selected component: WritRecogn-0.1.9-5.fc17 Additional info: libreport version: 2.0.18 abrt_version: 2.0.18 backtrace_rating: 4 cmdline: WritRecogn crash_function: ___3_writrecogn_radical_recognizer_libsvm_recognize kernel: 3.6.9-2.fc17.x86_64 truncated backtrace: :Thread no. 1 (10 frames) : #4 ___3_writrecogn_radical_recognizer_libsvm_recognize at /usr/lib64/WritRecogn/libWritRecogn.so : #5 writrecogn_radical_recognizer_recognize at /usr/lib64/WritRecogn/libWritRecogn.so : #6 on_recognizeButton_clicked : #7 _g_closure_invoke_va at gclosure.c:840 : #10 gtk_real_button_released at gtkbutton.c:1725 : #16 gtk_button_button_release at gtkbutton.c:1617 : #18 _gtk_marshal_BOOLEAN__BOXED at gtkmarshalers.c:86 : #23 gtk_widget_event_internal at gtkwidget.c:5017 : #24 gtk_widget_event at gtkwidget.c:4814 : #25 gtk_propagate_event at gtkmain.c:2490 -- 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=3TgbXPdPTr&a=cc_unsubscribe

1 5

[Fedora-i18n-bugs] [Bug 650205] New: [abrt] WritRecogn-0.1.9-1.fc11: raise: Process /usr/bin/WritRecogn was killed by signal 6 (SIGABRT)
by Red Hat Bugzilla 20 Dec '16

20 Dec '16

Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. Summary: [abrt] WritRecogn-0.1.9-1.fc11: raise: Process /usr/bin/WritRecogn was killed by signal 6 (SIGABRT) https://bugzilla.redhat.com/show_bug.cgi?id=650205 Summary: [abrt] WritRecogn-0.1.9-1.fc11: raise: Process /usr/bin/WritRecogn was killed by signal 6 (SIGABRT) Product: Fedora Version: 13 Platform: i686 OS/Version: Unspecified Status: NEW Status Whiteboard: abrt_hash:caf37a5446d0db49e10a286017b489bb0ae4f38b Severity: medium Priority: low Component: WritRecogn AssignedTo: dchen(a)redhat.com ReportedBy: martin(a)martindengler.com QAContact: extras-qa(a)fedoraproject.org CC: petersen(a)redhat.com, dchen(a)redhat.com, i18n-bugs(a)lists.fedoraproject.org Classification: Fedora abrt version: 1.1.13 architecture: i686 Attached file: backtrace cmdline: WritRecogn component: WritRecogn crash_function: raise executable: /usr/bin/WritRecogn kernel: 2.6.34.7-61.fc13.i686.PAE package: WritRecogn-0.1.9-1.fc11 rating: 4 reason: Process /usr/bin/WritRecogn was killed by signal 6 (SIGABRT) release: Fedora release 13 (Goddard) time: 1288965718 uid: 500 -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 10

← Newer
1
...
10
11
12
13
14
15
16
...
19
Older →

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

i18n-bugs November 2016