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 357032 - gnome-settings-daemon conflicts with input methods under Emacs
gnome-settings-daemon conflicts with input methods under Emacs
Status: RESOLVED INCOMPLETE
Product: gnome-settings-daemon
Classification: Core
Component: keyboard
2.22.x
Other All
: Normal normal
: ---
Assigned To: gnome-settings-daemon-maint
gnome-settings-daemon-maint
: 324289 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2006-09-21 08:38 UTC by Ning Ma
Modified: 2014-12-10 05:10 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14



Description Ning Ma 2006-09-21 08:38:22 UTC
Please describe the problem:
There's a lot of report from Chinese Emacs community that Emacs conflicts
with gnome-settings-daemon. I can not switch to Chinese input method, such as fcitx and scim, under Emacs in GNOME desktop environment. 

I'm not sure it's a bug of GNOME or Emacs, but everything works well under other WMs/Desktop Environments, however, Chinese IM under other applications are also work well.

Steps to reproduce:
1. set locale(LC_CTYPE) to *.UTF-8
2. start gnome-settings-daemon in any wm/de
3. try switching to Chinese input method in scim or fcitx under Emacs


Actual results:
XIM doesn't work, I can only input English characters under Emacs

Expected results:


Does this happen every time?
yes

Other information:
It also has sth to do with the locale setting. It's ok under zh_CN.GB2312 or zh_CN.GBK
Comment 1 Tom Tromey 2006-09-30 23:03:28 UTC
*** Bug 324289 has been marked as a duplicate of this bug. ***
Comment 2 Rui Matos 2012-09-29 19:56:44 UTC
Is this still a problem with a current gnome version?
Comment 3 Tobias Mueller 2013-01-25 00:32:37 UTC
Ning Ma: Ping
Comment 4 André Klapper 2014-12-10 05:10:55 UTC
(In reply to comment #2)
> Is this still a problem with a current gnome version?

Hi Ning, 
I am closing this bug report as no updated information has been provided.
Please feel free to reopen this bug if you can provide the information that was asked for in a previous comment.