lxkeymap does not remember settings

Bug #1026510 reported by Rafal Zawadzki
36
This bug affects 7 people
Affects Status Importance Assigned to Milestone
AC100_enablement
Confirmed
High
Unassigned
lxkeymap (Ubuntu)
Invalid
Undecided
Unassigned
ubiquity (Ubuntu)
Triaged
Undecided
Unassigned

Bug Description

lxkeymap is not able to read its own config.

bluszcz@rafal ~ $ cat .config/lxkeymap.cfg
[Global]
layout = us
variant = euro
option =

bluszcz@rafal ~ $ lxkeymap
Sections: ['Global']
Layouts: ['es']
Variants: []
Options: []

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: lxkeymap 0.7.99+dfsg-0ubuntu1.1
ProcVersionSignature: Ubuntu 3.2.0-26.41-generic 3.2.19
Uname: Linux 3.2.0-26-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.0.1-0ubuntu11
Architecture: amd64
Date: Thu Jul 19 10:23:41 2012
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: lxkeymap
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Rafal Zawadzki (bluszcz) wrote :
Revision history for this message
karl anliot (kanliot) wrote :

how would i reproduce this bug?

Revision history for this message
Rafal Zawadzki (bluszcz) wrote :

0. Relocate to Spain [optional]

1. Install lubuntu with choosing Spanish layout during installation.

2. Spend 1 week trying to buy US keyboard in Spain [or buy online]

3. Replace your ES keyboard with US one.

4. Run your Ubuntu

5. Run lxkeymap and change layout

6. Reboot computer

7. GOTO 5

I made some workaround changing keyboard layout on the kernel level or messing in etc - so its changed global now. Unfortunately I don't remember what exactly - but for now I am happy not to have using lxkeymap again.

I hope it help - if you have more questions - let me know.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in lxkeymap (Ubuntu):
status: New → Confirmed
Revision history for this message
ԜаӀtеr Ⅼарсһуnѕkі (wxl) wrote :

actually let's revise #6. just log out and log back in. confirmed.
here i'm on Lubuntu 12.04 _Precise Pangolin_ - Release i386 (20120423) fwiw

Revision history for this message
Leszek Lesner (leszek-lesner) wrote :

Is the keymap restored by running lxkeymap --autostart after the logout and login ?
If yes, then simply put it in the autostart.

Revision history for this message
ԜаӀtеr Ⅼарсһуnѕkі (wxl) wrote :

nope. after logging back in:

$ lxkeymap --autostart
Sections: ['Global']
Layouts: ['us']
Variants: []
Options: []
Traceback (most recent call last):
  File "/usr/bin/lxkeymap", line 621, in <module>
    (options, args) = parser.parse_args()
  File "/usr/lib/python2.7/optparse.py", line 1399, in parse_args
    stop = self._process_args(largs, rargs, values)
  File "/usr/lib/python2.7/optparse.py", line 1439, in _process_args
    self._process_long_opt(rargs, values)
  File "/usr/lib/python2.7/optparse.py", line 1514, in _process_long_opt
    option.process(opt, value, values, self)
  File "/usr/lib/python2.7/optparse.py", line 788, in process
    self.action, self.dest, opt, value, values, parser)
  File "/usr/lib/python2.7/optparse.py", line 808, in take_action
    self.callback(self, opt, value, parser, *args, **kwargs)
  File "/usr/bin/lxkeymap", line 611, in autostart
    LxkeymapWindow.loadFromConfig()
TypeError: unbound method loadFromConfig() must be called with LxkeymapWindow instance as first argument (got nothing instead)

and subsequently lxkeymap is back to default settings

Revision history for this message
karl anliot (kanliot) wrote : Re: [Bug 1026510] Re: lxkeymap does not remember settings

I noticed that lxsession is supposed to be doing keyboard mapping
stuff in 12.04 is there something here that i'm missing?

On Fri, Sep 14, 2012 at 3:51 PM, Walter Lapchynski
<email address hidden> wrote:
> nope. after logging back in:
>
> $ lxkeymap --autostart
> Sections: ['Global']
> Layouts: ['us']
> Variants: []
> Options: []
> Traceback (most recent call last):
> File "/usr/bin/lxkeymap", line 621, in <module>
> (options, args) = parser.parse_args()
> File "/usr/lib/python2.7/optparse.py", line 1399, in parse_args
> stop = self._process_args(largs, rargs, values)
> File "/usr/lib/python2.7/optparse.py", line 1439, in _process_args
> self._process_long_opt(rargs, values)
> File "/usr/lib/python2.7/optparse.py", line 1514, in _process_long_opt
> option.process(opt, value, values, self)
> File "/usr/lib/python2.7/optparse.py", line 788, in process
> self.action, self.dest, opt, value, values, parser)
> File "/usr/lib/python2.7/optparse.py", line 808, in take_action
> self.callback(self, opt, value, parser, *args, **kwargs)
> File "/usr/bin/lxkeymap", line 611, in autostart
> LxkeymapWindow.loadFromConfig()
> TypeError: unbound method loadFromConfig() must be called with LxkeymapWindow instance as first argument (got nothing instead)
>
> and subsequently lxkeymap is back to default settings
>
> --
> You received this bug notification because you are a member of Lubuntu
> Packages Team, which is subscribed to lxkeymap in Ubuntu.
> https://bugs.launchpad.net/bugs/1026510
>
> Title:
> lxkeymap does not remember settings
>
> Status in “lxkeymap” package in Ubuntu:
> Confirmed
>
> Bug description:
> lxkeymap is not able to read its own config.
>
> bluszcz@rafal ~ $ cat .config/lxkeymap.cfg
> [Global]
> layout = us
> variant = euro
> option =
>
> bluszcz@rafal ~ $ lxkeymap
> Sections: ['Global']
> Layouts: ['es']
> Variants: []
> Options: []
>
> ProblemType: Bug
> DistroRelease: Ubuntu 12.04
> Package: lxkeymap 0.7.99+dfsg-0ubuntu1.1
> ProcVersionSignature: Ubuntu 3.2.0-26.41-generic 3.2.19
> Uname: Linux 3.2.0-26-generic x86_64
> NonfreeKernelModules: nvidia
> ApportVersion: 2.0.1-0ubuntu11
> Architecture: amd64
> Date: Thu Jul 19 10:23:41 2012
> InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
> PackageArchitecture: all
> ProcEnviron:
> TERM=xterm
> PATH=(custom, no user)
> LANG=en_US.UTF-8
> SHELL=/bin/bash
> SourcePackage: lxkeymap
> UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/lxkeymap/+bug/1026510/+subscriptions

Revision history for this message
afri donschoe (afri-alex) wrote :

this bug affects me using lubuntu-12.10-armhf and is really annyoing. any workarounds or fixes yet?

Revision history for this message
Leszek Lesner (leszek-lesner) wrote :

I think rhis bug was fixed by me long time ago upstream. So please grab the latest upstream version. Btw why wasn't this reported upstream ?

Changed in lxkeymap (Ubuntu):
status: Confirmed → Fix Committed
Revision history for this message
Klaus Rotter (kzq-luaas-x8o) wrote :

Unfortunately, the fix didn't make it into ubunbtu 12.10 beta2. I had this problem using quantal on a ARM Netbook AC100.
The fix is rather simple. lxkeymap is python based so you can simply change the source code. Edit /usr/bin/lxkeymap
and change line 611 form
> LxkeymapWindow.loadFromConfig()
to
< window.loadFromConfig()

Revision history for this message
afri donschoe (afri-alex) wrote :

this is a quite major issue for the #ac100 release of the armhf-ubuntu version.

Changed in ac100:
importance: Undecided → High
status: New → Confirmed
Revision history for this message
Oliver Grawert (ogra) wrote :

the problem here is not lxkeymap, but the fact that oem-config (ubiquity) does not offer keyboard selection during install and just defaults to whatever is set in /etc/default/keyboard (which lxkeymap just uses as well) ... to work around the issue until the bug is fixed:

edit /etc/default/keyboard to use the keymap you want
run "sudo dpkg-reconfigure console-setup", answer all questions with their defaults and reboot (along with a proper desktop keymap you now should also have the right keymap on the console)

Changed in lxkeymap (Ubuntu):
status: Fix Committed → Invalid
Changed in ubiquity (Ubuntu):
status: New → Triaged
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.