Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fancy input methods can interfere and break the keyboard #286

Closed
totaam opened this issue Mar 8, 2013 · 8 comments
Closed

fancy input methods can interfere and break the keyboard #286

totaam opened this issue Mar 8, 2013 · 8 comments

Comments

@totaam
Copy link
Collaborator

totaam commented Mar 8, 2013

Issue migrated from trac ticket # 286

component: core | priority: critical | resolution: fixed

2013-03-08 15:54:05: antoine created the issue


If you start xpra from an environment which has input methods defined, the applications that you start will inherit those settings (and they might be global anyway via gconf or whatever?) and in some cases the application will be completely unable to use the keyboard!

Here are some of the environment variables that we may want to filter out, or even hardcode to sensible values that will not interfere with what we do:

DISABLE_IMSETTINGS=yes
GTK_IM_MODULE=gtk-im-context-simple
GTK_IM_MODULE=xim
GTK_IM_MODULE=
#IMSETTINGS_MODULE=
#QT_IM_MODULE as above?

Bonus difficulty: GTK and QT can lookup the immodule to use from the xsettings, which we forward from the client...
I am starting to think that we shouldn't just copy the xsettings blindly (breaks multi-user for example) and that we should just deal with individual xsettings explicitly (like we do for dpi).
So, clearing the module is not sufficient for now, we have to override the xsettings with the "good" value. (whatever that is)

@totaam
Copy link
Collaborator Author

totaam commented Mar 9, 2013

2013-03-09 09:03:10: antoine changed status from new to assigned

@totaam
Copy link
Collaborator Author

totaam commented Mar 9, 2013

2013-03-09 09:03:10: antoine edited the issue description

@totaam
Copy link
Collaborator Author

totaam commented Mar 9, 2013

2013-03-09 10:39:05: antoine edited the issue description

@totaam
Copy link
Collaborator Author

totaam commented Mar 9, 2013

2013-03-09 10:39:05: antoine commented


Documentation on those things is pretty scarce, r2922 tries to force all these things off... (and includes rpm dep update for gtk's 'xim' input module wherever appropriate)

Links:

Will need testing on:

  • CentOS 5.x which does not have gtk xim
  • Debian minimal (which does not have new dependencies - not needed?)
  • KDE / Qt DEs

@totaam
Copy link
Collaborator Author

totaam commented Mar 20, 2013

2013-03-20 14:20:33: antoine changed status from assigned to closed

@totaam
Copy link
Collaborator Author

totaam commented Mar 20, 2013

2013-03-20 14:20:33: antoine changed resolution from ** to fixed

@totaam
Copy link
Collaborator Author

totaam commented Mar 20, 2013

2013-03-20 14:20:33: antoine commented


No-one complained, and if someone does, we'll re-open this ticket.

@totaam totaam closed this as completed Mar 20, 2013
@totaam
Copy link
Collaborator Author

totaam commented Aug 13, 2014

2014-08-13 09:37:00: totaam commented


Someone complained, see #634

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant