As an alternative to what MountainX described, name the file
~/.xmodmaprc. The first time that file is present at login the user
will be asked if they want to load the file. There is an option to not
be asked again. Check that, select the file to load, and from there on
out the ~/.xmodmaprc will
Ok, the repro scenario is really easy: I started from the command line
as you describe ("f-spot --debug &> fspot-log.txt"). Then click the
File menu, then select Quit. It dies with a segv. The fspot-log.txt
file is attached.
** Attachment added: "fspot-log.txt"
http://launchpadlibrarian.net
I see this as well, running an HP 8710w. I have swapped Ctrl and
CapsLock. The key labeled "caps lock" works as control but toggles the
caps-lock LED. They key labeled "ctrl" works as caps-lock, but does
not toggle the caps-lock LED.
I agree that this did not happen in Gutsy.
Using Hardy x86
