Fedora Account System
Red Hat Associate
Red Hat Customer
- Fedora-19-Alpha-TC3-x86_64-DVD.iso - After a default installation, add gnome-classic: yum install gnome-classic-session - in gdm, select "gnome", log in, check ~/.cache/imsettings/log - log out and in gdm select "gnome-classic", log in, check ~/.cache/imsettings/log There is some difference in the logs: gnome: ... Is GTK+ supported: yes ... DESKTOP: gnome ... GTK_IM_MODULE: <- empty ... gnome-classic: ... Is GTK+ supported: no ... DESKTOP: gnome-classic ... GTK_IM_MODULE: xim ... Rui Matos: “Both classic and regular gnome should be treated the same, there is no fallback session anymore, both classic and regular gnome use the same gnome-shell now.”
imsettings-1.6.1-1.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/imsettings-1.6.1-1.fc19
Package imsettings-1.6.1-1.fc19: * should fix your issue, * was pushed to the Fedora 19 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing imsettings-1.6.1-1.fc19' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-4889/imsettings-1.6.1-1.fc19 then log in and leave karma (feedback).
This update msettings-1.6.1-1.fc19 does not seem to treat “gnome” and “gnome-classic” the same way yet. Relevant difference between .cache/imsettings/log between “gnome” and “gnome-classic”: < [ 1365152204.483622]: IMSettings-Daemon[4062]: INFO: Attempting to switch IM to X compose table [lang=pt_BR.UTF-8, update=false] < org.gnome.settings-daemon.plugins.keyboard.active is true. imsettings is going to be disabled. < < [ 1365152206.268340]: IMSettings-Daemon[4062]: WARNING **: Current desktop isn't targeted by IMSettings. --- > [ 1365152559.961295]: IMSettings-Daemon[4980]: INFO: Attempting to switch IM to X compose table [lang=pt_BR.UTF-8, update=false] > [ 1365152561.180318]: IMSettings-Daemon[4980]: INFO: no need to invoke any auxiliary process for X compose table > [ 1365152561.181116]: IMSettings-GSettings backend[4980]: INFO: Setting up xim:xim as gtk+ immodule So on “gnome”, it detects that “org.gnome.settings-daemon.plugins.keyboard.active is true” and says that it disables itself. On “gnome-classic” it doesn’t detect that this key is set to true and sets xim:xim as the gtk+ immodule. I have Brazilian Portuguese language and keyboard: [mfabian@Fedora-19-Alpha-TC4-x86_64-DVD ~]$ cat /etc/locale.conf LANG="pt_BR.UTF-8" [mfabian@Fedora-19-Alpha-TC4-x86_64-DVD ~]$ dconf dump /org/gnome/desktop/input-sources/ [/] current=uint32 0 sources=[('xkb', 'br'), ('xkb', 'us')] xkb-options=@as [] [mfabian@Fedora-19-Alpha-TC4-x86_64-DVD ~]$ When logging into “gnome”, gnome-terminal uses the “simple” input module and the key to the right of P followed by c inserts a ć. When logging into “gnome-classic”, gnome-terminal uses the “xim” input module and the key to the right of P followed by c inserts a ç. So it still doesn’t behave the same way on “gnome” and “gnome-classic”.
Thanks for testing. should works with -2.
Package imsettings-1.6.1-2.fc19: * should fix your issue, * was pushed to the Fedora 19 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing imsettings-1.6.1-2.fc19' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-4889/imsettings-1.6.1-2.fc19 then log in and leave karma (feedback).
(In reply to comment #4) > Thanks for testing. should works with -2. Yes, this works, “gnome” and “gnome-classic” are treated the same way now. By the way, imsettings writes into ~/.cache/imsettings/log [ 1365513547.246338]: IMSettings-Daemon[4511]: WARNING **: Current desktop isn't targeted by IMSettings. But why does it keep running? Shouldn’t it stop if it does not target the current desktop?
That makes sense. did it in git.
imsettings-1.6.1-2.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.