After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 699123 - Typing options not working
Typing options not working
Status: RESOLVED OBSOLETE
Product: gnome-tweak-tool
Classification: Applications
Component: general
3.8.x
Other Linux
: Normal normal
: ---
Assigned To: GNOME Tweak Tool maintainer(s)
GNOME Tweak Tool maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2013-04-28 12:10 UTC by xgdgsc
Modified: 2018-01-24 15:07 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
journal (631.69 KB, text/plain)
2013-04-28 14:53 UTC, xgdgsc
Details
journal after removing Xmodmap (15.55 KB, text/plain)
2013-04-29 01:48 UTC, xgdgsc
Details

Description xgdgsc 2013-04-28 12:10:55 UTC
None of the options in Typing section works.
Comment 1 Rui Matos 2013-04-28 12:54:29 UTC
Please post the output of these 2 commands:

$ setxkbmap -query
$ gsettings list-recursively org.gnome.desktop.input-sources

After changing one of those options.
Comment 2 xgdgsc 2013-04-28 14:16:18 UTC
$setxkbmap -query
rules:      evdev
model:      evdev
layout:     us
$gsettings list-recursively org.gnome.desktop.input-sources
org.gnome.desktop.input-sources current uint32 0
org.gnome.desktop.input-sources per-window false
org.gnome.desktop.input-sources show-all-sources false
org.gnome.desktop.input-sources sources [('xkb', 'us')]
org.gnome.desktop.input-sources xkb-options ['terminate:ctrl_alt_bksp', 'numpad:pc']

But now numpad start with numlock disabled and ctrl alt bksp to kill X not working.
Comment 3 Rui Matos 2013-04-28 14:23:16 UTC
Which version of gnome-settings-daemon do you have? Can you attach you session log? Depending on which distro you're using it might be in either ~/.xsession-errors, ~/.cache/gdm/session.log or in the systemd journal (use journalctl to get it).
Comment 4 xgdgsc 2013-04-28 14:53:21 UTC
Created attachment 242716 [details]
journal
Comment 5 xgdgsc 2013-04-28 14:55:27 UTC
archlinux 
Version        : 3.8.1-1
Comment 6 Rui Matos 2013-04-28 16:44:41 UTC
Can you remove your .Xmodmap file out of the way and try again please?
Comment 7 xgdgsc 2013-04-29 01:47:26 UTC
I removed it and here's the journalctl-b log:
Comment 8 xgdgsc 2013-04-29 01:48:01 UTC
Created attachment 242764 [details]
journal after removing Xmodmap
Comment 9 Rui Matos 2013-04-29 11:27:19 UTC
I see that you're running fcitx. Have you perhaps disabled the gnome-settings-daemon keyboard plugin? You can check with

$ gsettings get org.gnome.settings-daemon.plugins.keyboard active
Comment 10 xgdgsc 2013-04-29 14:05:48 UTC
Yes, I disabled that to use fcitx. I won' t use ibus.
Comment 11 Rui Matos 2013-04-29 14:28:30 UTC
Ok, then that means that it's fcitx's responsibility to manage all your keyboard settings.
Comment 12 John Stowers 2013-04-29 14:34:11 UTC
Rui, can I detect (nicely?) if the user is running fcitx and disable the settings in tweak tool.
Comment 13 Rui Matos 2013-04-29 14:37:55 UTC
(In reply to comment #12)
> Rui, can I detect (nicely?) if the user is running fcitx and disable the
> settings in tweak tool.

Well, we can check if org.gnome.settings-daemon.plugins.keyboard active is false and not show them then because that means they won't be applied.
Comment 14 GNOME Infrastructure Team 2018-01-24 15:07:40 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gnome-tweaks/issues/31.