Losing the keyboard on F12

For test results, bug reports, announcements of new builds etc.

Moderators: winston, another_commander, Getafix

User avatar
Getafix
Quite Grand Sub-Admiral
Quite Grand Sub-Admiral
Posts: 960
Joined: Tue Apr 01, 2008 12:55 pm
Location: A small ice asteroid, orbiting Oresrati in Galaxy 8 (a.k.a. northwest Armorica).
Contact:

Re: Losing the keyboard on F12

Post by Getafix » Mon Jun 08, 2015 10:29 pm

@jh145: All of the below have been checked as 'buggy'.

LXLE 12.04 / 32-bit / Openbox
XMODIFIERS has the value @im=ibus and ibus version is ... ehm, well... due to incorrect O/S configuration, I couldn't get that.

Ubuntu 14.04 / 64-bit / Compiz
XMODIFIERS has the value @im=ibus and ibus version is 1.5.5

Fedora 22 / 64-bit / Gnome
XMODIFIERS has the value @im=ibus and ibus version is 1.5.10

The good news is that executing

Code: Select all

$ XMODIFIERS='' ~/GNUstep/Applications/Oolite/oolite
seems to tackle the issue for all three aforementioned systems. 8)

I would like to have this tested by a Commander having a keyboard with accented letters (i.e. á, é, í, ó, ú, ü, etc.).
Do we get the same text input behavior, editing ship registration, with and without XMODIFIERS='' preceding the Oolite command?
Last edited by Getafix on Tue Jun 09, 2015 9:51 am, edited 1 time in total.
Reason: Just formatting changes.
"Any sufficiently advanced information is indistinguishable from noise." [Newman, Lachmann, Moore]

User avatar
Getafix
Quite Grand Sub-Admiral
Quite Grand Sub-Admiral
Posts: 960
Joined: Tue Apr 01, 2008 12:55 pm
Location: A small ice asteroid, orbiting Oresrati in Galaxy 8 (a.k.a. northwest Armorica).
Contact:

Re: Losing the keyboard on F12

Post by Getafix » Tue Jun 16, 2015 9:13 am

Just a final attempt to revive this, before marking as "Solved".

Is there anybody out there with a French, German or other non QWERTY keyboard layout that could check "Edit ship registration" with a new Jameson running Oolite as follows?

Code: Select all

$ XMODIFIERS='' ~/GNUstep/Applications/Oolite/oolite
"Any sufficiently advanced information is indistinguishable from noise." [Newman, Lachmann, Moore]

User avatar
Norby
---- E L I T E ----
---- E L I T E ----
Posts: 2543
Joined: Mon May 20, 2013 9:53 pm
Location: Budapest, Hungary (Mainly Agricultural Democracy, TL10)
Contact:

Re: Losing the keyboard on F12

Post by Norby » Tue Jun 16, 2015 11:33 am

I have "éáöüóűőúí" keys but XMODIFIERS already empty both under Debian and Mint so these keys does nothing in Oolite regardless of started normally or with your method. (All other programs can use these keys.)

User avatar
jh145
Dangerous
Dangerous
Posts: 94
Joined: Thu Dec 25, 2014 8:39 pm

Re: Losing the keyboard on F12

Post by jh145 » Tue Jun 16, 2015 7:41 pm

I vote we modify the start script and wait for complaints. Specifically, if XMODIFIERS points to ibus, set it null, print a big warning to stderr, then start Oolite. Give this (or another relevant) thread id in the warning for feedback.

User avatar
Getafix
Quite Grand Sub-Admiral
Quite Grand Sub-Admiral
Posts: 960
Joined: Tue Apr 01, 2008 12:55 pm
Location: A small ice asteroid, orbiting Oresrati in Galaxy 8 (a.k.a. northwest Armorica).
Contact:

Re: Losing the keyboard on F12

Post by Getafix » Wed Jun 17, 2015 8:12 am

@Norby
Many thanks for the crystal clear feedback.

@jh145
Changing the startup script universally to address such Linux distro-dependent caprice, is not suggested.
Furthermore, it would only address the case for oolite.org package installations. Oolite installations coming from packages downloaded from Linux repositories will still have the issue. Perhaps, if an elegant solution cannot be found, ignoring it, or just mentioning the manual workaround in a readme file, could also be an approach; violently assaulting F12, is not a frequently encountered behavior after all.
"Any sufficiently advanced information is indistinguishable from noise." [Newman, Lachmann, Moore]

User avatar
jh145
Dangerous
Dangerous
Posts: 94
Joined: Thu Dec 25, 2014 8:39 pm

Re: Losing the keyboard on F12

Post by jh145 » Wed Jun 17, 2015 8:32 am

I encountered the problem plenty often enough without "violently assaulting" my keyboard. A single tap on F12 on startup, done quick enough (as I often did due to impatience), was sufficient to trigger keyboard lock-out.

I can't see the problem modifying the trunk nightly as I described. You'd quickly find out if it gave rise to a serious issue. By all means move the fix deeper into the code if the startup scripts are oolite.org-specific. Keeping the fix only in this thread or a README is a great way to effectively lose the work done up to this point, so please don't do that.

Post Reply