[Fedora-i18n-bugs] [Bug 1178271] New: [abrt] ibus-chewing: g_settings_set_property(): ibus-engine-chewing killed by SIGTRAP
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1178271
Bug ID: 1178271
Summary: [abrt] ibus-chewing: g_settings_set_property():
ibus-engine-chewing killed by SIGTRAP
Product: Fedora
Version: 20
Component: ibus-chewing
Assignee: dchen(a)redhat.com
Reporter: novatw(a)novatw.info
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:
1. Switch to ibus-chewing
2. The crash happen
Version-Release number of selected component:
ibus-chewing-1.4.14-2.fc20
Additional info:
reporter: libreport-2.2.3
backtrace_rating: 4
cmdline: /usr/libexec/ibus-engine-chewing --ibus
crash_function: g_settings_set_property
executable: /usr/libexec/ibus-engine-chewing
kernel: 3.17.7-200.fc20.x86_64
runlevel: N 5
type: CCpp
uid: 0
Truncated backtrace:
Thread no. 1 (10 frames)
#2 g_settings_set_property at gsettings.c:492
#3 object_set_property at gobject.c:1366
#4 g_object_new_internal at gobject.c:1779
#5 g_object_new_valist at gobject.c:2002
#7 g_settings_new at gsettings.c:864
#8 mkdg_g_settings_backend_new at
/usr/src/debug/ibus-chewing-1.4.14-Source/src/GSettingsBackend.c:295
#9 ibus_chewing_engine_use_setting at
/usr/src/debug/ibus-chewing-1.4.14-Source/src/IBusChewingEngine.gob:304
#10 ibus_chewing_engine_init at
/usr/src/debug/ibus-chewing-1.4.14-Source/src/IBusChewingEngine.gob:282
#11 g_type_create_instance at gtype.c:1868
#12 g_object_constructor at gobject.c:2028
Potential duplicate: bug 1177999
--
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=5tj6kZBDRp&a=cc_unsubscribe
8 years, 3 months
[Fedora-i18n-bugs] [Bug 1300147] list most common and important keyboard layouts first
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1300147
David Shea <dshea(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |petersen(a)redhat.com
Flags| |needinfo?(petersen(a)redhat.c
| |om)
--- Comment #2 from David Shea <dshea(a)redhat.com> ---
Same question from bug 1158370: how do you propose that we determine what is
and is not a common layout? gnome-initial-setup uses a hard-coded list of
"common" languages to determine which layouts to present to the user first.
anaconda is not as able as gnome to make the determination of should or should
not be considered a common or support language, and this solution is not
appropriate.
--
You are receiving this mail because:
You are on the CC list for the bug.
8 years, 4 months
[Fedora-i18n-bugs] [Bug 1049304] localectl list-x11-keymap-models does not know 'evdev'
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1049304
--- Comment #6 from Peter Hutterer <peter.hutterer(a)redhat.com> ---
(In reply to Karel Volný from comment #5)
> > Aside from that, it's not really a bug, the setxkbmap output is not
> > trustworthy.
>
> well ... such behaviour is very confusing
agreed, but at least within X there isn't much we can do. setxkbmap's (and the
server's) approach to handling RMLVO dates back to when we only had one single
keyboard (pre-2007). Fixing the various tools is generally possible, but no-one
has put the effort in, there's just not that much benefit.
> if something is supposed to tell me what the settings are and it reports
> nothing, it is quite hard to tell if the settings are correct unless you
> have deep knowledge of the subject that you cannot expect from ordinary
> users ...
and this summarises the problem nicely. setxkbmap doesn't tell you the
settings, it merely tells you the value of an unrelated property that is set at
server startup and (hopefully) by the tools changing the keyboard layout.
keyboard layout configuration is lossy, once you load a layout you cannot go
back to the RMLVO designation that created the layout.
the only way for setxkbmap to actually tell you the current setting would be to
look at every key and match it up with a generated keyboard layout. given that
thousands of combinations, that's not really viable.
--
You are receiving this mail because:
You are on the CC list for the bug.
8 years, 4 months
[Fedora-i18n-bugs] [Bug 1049304] localectl list-x11-keymap-models does not know 'evdev'
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1049304
--- Comment #5 from Karel Volný <kvolny(a)redhat.com> ---
(In reply to Peter Hutterer from comment #4)
> Karel - do you have some xorg.conf.d snippets?
a bit late but anyways ...
$ cat /etc/X11/xorg.conf.d/00-keyboard.conf
# Read and parsed by systemd-localed. It's probably wise not to edit this file
# manually too freely.
Section "InputClass"
Identifier "system-keyboard"
MatchIsKeyboard "on"
Option "XkbLayout" "cz"
Option "XkbModel" "evdev"
Option "XkbVariant" "qwerty"
Option "XkbOptions" "terminate:ctrl_alt_bksp"
EndSection
> can you attach your Xorg.log?
guess there's no need to as we see "evdev" as "XkbModel" in the configfile ...
> Aside from that, it's not really a bug, the setxkbmap output is not
> trustworthy.
well ... such behaviour is very confusing
if something is supposed to tell me what the settings are and it reports
nothing, it is quite hard to tell if the settings are correct unless you have
deep knowledge of the subject that you cannot expect from ordinary users ...
--
You are receiving this mail because:
You are on the CC list for the bug.
8 years, 4 months
[Fedora-i18n-bugs] [Bug 1279587] Keyboard keydown getting stuck in wine LFS.exe when key presses repeat is enabled
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1279587
semiRocket <semiRocket(a)gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |i18n-bugs(a)lists.fedoraproje
| |ct.org,
| |shawn.p.huang(a)gmail.com,
| |tfujiwar(a)redhat.com
Component|gnome-shell |ibus
Hardware|Unspecified |x86_64
OS|Unspecified |Linux
--- Comment #3 from semiRocket <semiRocket(a)gmail.com> ---
Since I could not recreate working state with Fedora 23 easily, possibly due to
packages not being in repository any more to use with "dnf downgrade", I have
booted into Fedora 22 on my older hard drive in order to debug what package may
have caused this. Started from a perfectly working state...
As there was passed a lot of time since I have last used this Fedora 22
install, there was a lot of updates available, so I've decided to split them up
into sections to make debugging easier. After each update I have rebooted
computer and directly run LFS.exe.
So after command:
$ sudo dnf --exclude=wine*,xorg-x11*,mesa*,lib*,ibus* upgrade
And narrowing it down further:
$ sudo dnf upgrade ibus*
After which problems started to occur. And sure enough after downgrading ibus*
and rebooting game was again working fine. I have tested it couple of times.
The transaction details as follows:
$ sudo dnf history info 50
Last metadata expiration check performed 2:54:20 ago on Sat Jan 16 08:01:15
2016.
Transaction ID : 50
Begin time : Sat Jan 16 10:19:27 2016
Begin rpmdb : 2081:753d5fc7734c3cc90340034fbfc59232cb111588
End time : 10:19:41 2016 (14 seconds)
End rpmdb : 2081:da643116dfaf7924750a880c7d18cb22367e3475
User : <trim>
Return-Code : Success
Command Line : upgrade ibus*
Transaction performed with:
Installed dnf-1.1.5-1.fc22.noarch @updates
Installed rpm-4.12.0.1-14.fc22.x86_64 @updates
Packages Altered:
Upgraded ibus-1.5.10-5.fc22.x86_64 (unknown)
Upgrade 1.5.11-1.fc22.1.x86_64 @updates
Upgraded ibus-gtk2-1.5.10-5.fc22.x86_64 (unknown)
Upgrade 1.5.11-1.fc22.1.x86_64 @updates
Upgraded ibus-gtk3-1.5.10-5.fc22.x86_64 (unknown)
Upgrade 1.5.11-1.fc22.1.x86_64 @updates
Upgraded ibus-libs-1.5.10-5.fc22.x86_64 (unknown)
Upgrade 1.5.11-1.fc22.1.x86_64 @updates
Upgraded ibus-setup-1.5.10-5.fc22.noarch (unknown)
Upgrade 1.5.11-1.fc22.1.noarch @updates
Upgraded ibus-typing-booster-1.2.11-1.fc22.noarch (unknown)
Upgrade 1.3.0-3.fc22.noarch @updates
Upgraded ibus-wayland-1.5.10-5.fc22.x86_64 (unknown)
Upgrade 1.5.11-1.fc22.1.x86_64 @updates
--
You are receiving this mail because:
You are on the CC list for the bug.
8 years, 4 months
[Fedora-i18n-bugs] [Bug 1257496] Fonts are not antialiased in java applications
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1257496
Mario Torre <neugens(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |CLOSED
Resolution|--- |NOTABUG
Last Closed|2015-08-28 08:59:40 |2016-01-12 04:04:48
--- Comment #11 from Mario Torre <neugens(a)redhat.com> ---
(In reply to Akira TAGOH from comment #10)
> I'm not sure why Java prefer non-antialiased font by default. why don't you
> change the behavior like others?
For compatibility reasons, it is also a better default for connections over
SSH. I will speak with the AWT developers and see what they think about
changing this default, but I will close this bug for now since, well, it's not
exactly a bug.
--
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=RHZfHnq7kY&a=cc_unsubscribe
8 years, 4 months