[Fedora-i18n-bugs] [Bug 1231470] New: [abrt] ibus: IA__FcPatternDestroy(): ibus-x11 killed by SIGBUS
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1231470
Bug ID: 1231470
Summary: [abrt] ibus: IA__FcPatternDestroy(): ibus-x11 killed
by SIGBUS
Product: Fedora
Version: 22
Component: ibus
Assignee: tfujiwar(a)redhat.com
Reporter: sbandyop(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.10-5.fc22
Additional info:
reporter: libreport-2.5.1
backtrace_rating: 4
cmdline: /usr/libexec/ibus-x11 --kill-daemon
crash_function: IA__FcPatternDestroy
executable: /usr/libexec/ibus-x11
global_pid: 2983
kernel: 4.0.4-303.fc22.x86_64
runlevel: N 5
type: CCpp
uid: 1000
Truncated backtrace:
Thread no. 1 (10 frames)
#0 IA__FcPatternDestroy at fcpat.c:385
#1 IA__FcFontSetDestroy at fcfs.c:48
#2 IA__FcConfigDestroy at fccfg.c:287
#3 IA__FcConfigSetCurrent at fccfg.c:442
#4 IA__FcInitReinitialize at fcinit.c:197
#5 settings_update_fontconfig at gtksettings.c:2360
#6 gtk_settings_notify at gtksettings.c:1422
#12 g_object_notify_by_spec_internal at gobject.c:1149
#13 g_object_notify at gobject.c:1197
#14 _gtk_settings_handle_event at gtksettings.c:2151
--
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=hBhss6DErr&a=cc_unsubscribe
8 years, 11 months
[Fedora-i18n-bugs] [Bug 1185861] New: Feature request: adjusting executable script
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1185861
Bug ID: 1185861
Summary: Feature request: adjusting executable script
Product: Fedora
Version: 21
Component: system-config-language
Assignee: pnemade(a)redhat.com
Reporter: chat-to-me(a)raveit.de
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
Description of problem:
system-config-language use
#!/bin/sh
exec /usr/bin/pkexec
/usr/share/system-config-language/system-config-language.py
in executable script.
Unfortunately using 'exec' cause a double forking issue if starting from
mate-control-center, see https://bugzilla.redhat.com/show_bug.cgi?id=972534 .
Using '/usr/bin/pkexec
/usr/share/system-config-language/system-config-language.py' would fix the
issue.
Is it possible to change that or is there a technical reason to use 'exec' in
the script?
Thanks in advance
Version-Release number of selected component (if applicable):
all fedora branches
How reproducible:
always
Steps to Reproduce:
1. starting mate session
2. open mate-control-center from menu
3. try to start system-config-language
--
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=hnLXP8OOSA&a=cc_unsubscribe
8 years, 11 months
[Fedora-i18n-bugs] [Bug 1186030] no layout for chromebook keyboard
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1186030
--- Comment #19 from Benjamin Tissoires <btissoir(a)redhat.com> ---
(In reply to Kent W. Nixon from comment #18)
> Ben, your posted keymaps for the 2013 Pixel to not line up with what I have
> over here. My keyboard scancodes line up with the ones you posted from the
> 2015 Pixel (shown below [no idea how to attach things]). I don't know where
> or how you got your scan codes, but please be aware that I nuked Chrome OS
> off of my Pixel thing pretty much as soon as I got it from Google I/O 2013.
> I am also running a custom version of coreboot courtesy of johnlewis.ie. A
> later hardware revision or a firmware update through Chrome OS may have
> changed it to match what you posted for others.
>
OK. thanks for the notice, but hopefully we will not have to tune any custom
scancodes. As mentioned in comment #14, the idea is to use xkb, and not a
custom keymap config.
I have opened fdo bug #90684 for this and we are still waiting on upstream.
If you want to give a try, you can:
- revert the hwdb changes (and reboot)
- add the "inet" section from the patch in the fdo bug in
/usr/share/X11/xkb/symbols/inet (without the leading '+')
- run "setxkbmap -layout us -model chromebook"
This should make the right Alt key as a modifier and the function keys working
like they should.
--
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=FCZlIR24VQ&a=cc_unsubscribe
8 years, 11 months
[Fedora-i18n-bugs] [Bug 1048429] New: [abrt] ibus-setup: enginetreeview.py:131:__icon_cell_data_cb:AttributeError: 'NoneType' object has no attribute 'get_icon'
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1048429
Bug ID: 1048429
Summary: [abrt] ibus-setup:
enginetreeview.py:131:__icon_cell_data_cb:AttributeErr
or: 'NoneType' object has no attribute 'get_icon'
Product: Fedora
Version: 19
Component: ibus
Assignee: tfujiwar(a)redhat.com
Reporter: sun_465(a)hotmail.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-setup-1.5.4-2.fc19
Additional info:
reporter: libreport-2.1.10
cmdline: /usr/bin/python /usr/share/ibus/setup/main.py ibus-setup
executable: /usr/share/ibus/setup/main.py
kernel: 3.11.10-200.fc19.x86_64
runlevel: N 5
type: Python
uid: 1000
Truncated backtrace:
enginetreeview.py:131:__icon_cell_data_cb:AttributeError: 'NoneType' object has
no attribute 'get_icon'
Traceback (most recent call last):
File "/usr/share/ibus/setup/enginetreeview.py", line 131, in
__icon_cell_data_cb
pixbuf = load_icon(engine.get_icon(), Gtk.IconSize.LARGE_TOOLBAR)
AttributeError: 'NoneType' object has no attribute 'get_icon'
Local variables in innermost frame:
engine: None
self: <EngineTreeView object at 0x1da0dc0 (EngineTreeView at 0x1ec0080)>
celllayout: <TreeViewColumn object at 0x1fc1050 (GtkTreeViewColumn at
0x1e24d40)>
it: <GtkTreeIter at 0x2586820>
renderer: <CellRendererPixbuf object at 0x1fc1280 (GtkCellRendererPixbuf at
0x1b12dd0)>
icon_size: True
model: <ListStore object at 0x1da0d20 (GtkListStore at 0x1eb8d20)>
data: None
--
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=iPc7lMWlnx&a=cc_unsubscribe
8 years, 11 months
[Fedora-i18n-bugs] [Bug 1231499] New: ibus can't type in Telegram(from KDE 5)
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1231499
Bug ID: 1231499
Summary: ibus can't type in Telegram(from KDE 5)
Product: Fedora
Version: 22
Component: ibus
Assignee: tfujiwar(a)redhat.com
Reporter: litimetal(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:
I can't type Chinese with ibus-libpinyin in Telegram, which is provided by KDE5
in Fedora 22
Version-Release number of selected component (if applicable):
ibus 1.5.10
Intelligent Pinyin 1.7.1
How reproducible:
Always
Steps to Reproduce:
1. Logging into Telegram, start a chat
2. Switch Input Method ibus-libpinyin by Ctrl+Space (My config)
3. Type something, like "nihao". In other softwares, there will be a list of
candidates to choose, including 你好, 你, 泥, etc. But in Telegram, "nihao" is
shown in the chat box, and no candidates are shown.
4. If I type Chinese in other places, then copy them to Telegram, then it works
fine
Actual results:
Expected results:
Additional info:
My .xprofile:
export GTK_IM_MODULE="ibus"
export QT_IM_MODULE="ibus"
My .bashrc:
export GTK_IM_MODULE="ibus"
export QT_IM_MODULE="ibus"
export XMODIFIERS=@im=ibus
--
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=0Rp0cnRRMK&a=cc_unsubscribe
8 years, 11 months
[Fedora-i18n-bugs] [Bug 1186030] no layout for chromebook keyboard
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1186030
Kent W. Nixon <kentnixon(a)hotmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |kentnixon(a)hotmail.com
--- Comment #18 from Kent W. Nixon <kentnixon(a)hotmail.com> ---
(In reply to Benjamin Tissoires from comment #10)
> Created attachment 1015378 [details]
> 60-keyboard.hwdb
>
> I played a little bit with both the 2013 and 2015 today and came out with
> the following hwdb entry.
>
> To test it, just drop it under /etc/udev/hwdb.d (yes, the directory does not
> exists by default).
> Then run:
> $ sudo udevadm hwdb --update
> $ sudo udevadm trigger
>
> This should make the refresh, switchvideomode, brightness(up|down) and
> volume (mute, up, down) key working.
>
> I personally prefer not remapping the search key because I found it more
> interesting to have a super-L key, and back/forward either to be able to
> switch to a VT :)
>
> Unless there are strong opinion, I'll submit this upstream soonish after I
> made the tests against the latest systemd version.
I installed Fedora 22 on my 2013 Pixel (Link) the other day and have been
messing around trying to get the keymaps working correctly. Thanks to everyone
here for posting this great info.
Ben, your posted keymaps for the 2013 Pixel to not line up with what I have
over here. My keyboard scancodes line up with the ones you posted from the 2015
Pixel (shown below [no idea how to attach things]). I don't know where or how
you got your scan codes, but please be aware that I nuked Chrome OS off of my
Pixel thing pretty much as soon as I got it from Google I/O 2013. I am also
running a custom version of coreboot courtesy of johnlewis.ie. A later hardware
revision or a firmware update through Chrome OS may have changed it to match
what you posted for others.
Hope this helps!
# Chromebook Pixel 2013 (Link)
# Top row keys (between ESC and power button)
keyboard:dmi:bvn*:bvr*:svnGOOGLE:pnLink:pvr*
KEYBOARD_KEY_3b=back
KEYBOARD_KEY_3c=forward
KEYBOARD_KEY_3d=refresh
# KEYBOARD_KEY_3e=fullscreen -> no defined symbol
KEYBOARD_KEY_3f=switchvideomode
KEYBOARD_KEY_40=brightnessdown
KEYBOARD_KEY_41=brightnessup
KEYBOARD_KEY_42=mute
KEYBOARD_KEY_43=volumedown
KEYBOARD_KEY_44=volumeup
# KEYBOARD_KEY_db=search # Same position as caps lock key -> kept as Super_L
--
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=JesQMpPrhU&a=cc_unsubscribe
8 years, 11 months
[Fedora-i18n-bugs] [Bug 598277] New: [Indic] Rendering broken on 'Benchmark' Window
by Red Hat Bugzilla
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
Summary: [Indic] Rendering broken on 'Benchmark' Window
https://bugzilla.redhat.com/show_bug.cgi?id=598277
Summary: [Indic] Rendering broken on 'Benchmark' Window
Product: Fedora
Version: 13
Platform: All
OS/Version: Linux
Status: NEW
Keywords: i18n
Severity: medium
Priority: low
Component: gnome-disk-utility
AssignedTo: davidz(a)redhat.com
ReportedBy: aalam(a)redhat.com
QAContact: extras-qa(a)fedoraproject.org
CC: davidz(a)redhat.com, i18n-bugs(a)lists.fedoraproject.org
Classification: Fedora
Target Release: ---
Created an attachment (id=418426)
--> (https://bugzilla.redhat.com/attachment.cgi?id=418426)
Rendering Problem on Benchmark window
Description of problem:
While using application in Punjabi (pa_IN), I found some square box, which is
most probably i18n issue (translation is ok as render ok other places in
application). Bug seems similar to
Version-Release number of selected component (if applicable):
gnome-disk-utility-2.30.1-1.fc13.x86_64
How reproducible:
100%
Steps to Reproduce:
1. run application in Indic locale (pa_IN/hi_IN)
2. select disk and click on Benchmark
3.
Actual results:
Rendering Broken on both side of graph (check screenshot for detail)
Expected results:
should work as in english locale
Additional info:
same as Bug #560336
--
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.
8 years, 11 months