Two problems in MX-17 keyboard and screen

[duane]

Today shortly after rebooting MX-17 the wallpaper left and an error message came up something like "couldn't grab a screenshot screenshot already grabbed". I was about to look at some keyboard settings when this suddenly happened. I hit the escape key and my wallpaper came back and everything was normal. This only happened once so far.

The other problem is that unlike MX-16.1 MX-17 does not come up with the number locks on. Dual booting MX-17 and MX16.1 on same machine in sig. different behavior.
I have not changed any settings.

The number locks is a minor thing but I thought I should report it.

[Jerry3904]

I'll pass over the first, since it seems like user error to me (sorry) as no one during development or since has reported anything of the kind.

About the second: numlock comes up enabled to "restore the numlock state" by default, but the default itself was set to not be enabled:

Code: Select all

<?xml version="1.0" encoding="UTF-8"?>

<channel name="keyboards" version="1.0">
  <property name="Default" type="empty">
    <property name="Numlock" type="bool" value="false"/>
  </property>
</channel>

Since the numlock state is set to be restored, I believe that once you hit the numlock button, then it will be enabled every time you login ever after (attached). I'm going to test that after posting this...
--------
88888 << yup

[duane]

Agreed. I think the first was most likely user error except I have no idea how I got that message.

What I am seeing is those numlock settings don't seem to be working on this machine like I would expect.

[Jerry3904]

Did you hit the key to engage numlock, then log out and back in and test if it is working?

I agree that engaged is not the default state, and the code I showed that proves it.

[azrielle]

OS's that boot with numlock enabled by default are REALLY IRRITATING to those of us with 10", 11.6", 12.5", or 13" screen notebooks and so-called "embedded" number pads. It really screws up the typing of passwords for example.

[duane]

Did that. This computer is not saving the previous state in MX 17.
MX 16.1 is saving it. That is what I can't figure out.

[duane]

It happens that I have two of these computers that are identical except I put a larger hard drive in the other one.
I get the same behavior on that one as well.