[Fedora-i18n-bugs] [Bug 1161284] New: git dependency
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1161284
Bug ID: 1161284
Summary: git dependency
Product: Fedora
Version: rawhide
Component: gettext
Severity: low
Assignee: dueno(a)redhat.com
Reporter: tessarek(a)evermeet.cx
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:
gettext-devel depends on git
Additional info:
Mail correspondence with Daiki Ueno:
> Can you please remove the git dependency for gettext-devel?
>
> This is supposed to be a development package (mainly include files).
> Since git on Fedora is very old and not updated reagularily, I tried to
> remove git (to compile my own git) and to my surprise I saw that
> gettext-devel depends on git.
>
> AFAIK this is the only *-devel package which depends on git.
Actually, it _was_ needed for autopoint (a developer script, like
autoconf or automake), when we used git as a compression method of
/usr/share/gettext/archive.dir.*. Now that the default changed to
tar.xz, git shouldn't be necessary anymore.
> I truly believe this is a bug. Can you please fix this?
Could you please file a bug on bugzilla.redhat.com, so we don't forgot
to fix it on the next update?
--
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=UK9aT8RR8W&a=cc_unsubscribe
7 years, 3 months
[Fedora-i18n-bugs] [Bug 1326156] New: kernel hung when using fbterm on vmware workstation 12
by Red Hat Bugzilla
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.
7 years, 5 months
[Fedora-i18n-bugs] [Bug 1324864] New: [abrt] ibus-gucharmap: character_to_iter(): ibus-engine-gucharmap killed by SIGSEGV
by Red Hat Bugzilla
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.
7 years, 5 months
[Fedora-i18n-bugs] [Bug 1310625] New: [abrt] ibus-mozc: __fdelt_chk(): ibus-engine-mozc killed by SIGABRT
by Red Hat Bugzilla
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.
7 years, 5 months
[Fedora-i18n-bugs] [Bug 1294727] New: [abrt] ibus: _g_log_abort(): ibus-daemon killed
by SIGTRAP
by Red Hat Bugzilla
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
7 years, 5 months
[Fedora-i18n-bugs] [Bug 1189423] New: Keyboard Layout not persistent through login
by Red Hat Bugzilla
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
7 years, 5 months