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.
Two problems in MX-17 keyboard and screen
Two problems in MX-17 keyboard and screen
Lenovo M92p Quad Core i5 3470 3.2Ghz
Re: Two problems in MX-17 keyboard and screen
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: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
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>
--------
88888 << yup
You do not have the required permissions to view the files attached to this post.
Production: 5.10, MX-23 Xfce, AMD FX-4130 Quad-Core, GeForce GT 630/PCIe/SSE2, 16 GB, SSD 120 GB, Data 1TB
Personal: Lenovo X1 Carbon with MX-23 Fluxbox and Windows 10
Other: Raspberry Pi 5 with MX-23 Xfce Raspberry Pi Respin
Personal: Lenovo X1 Carbon with MX-23 Fluxbox and Windows 10
Other: Raspberry Pi 5 with MX-23 Xfce Raspberry Pi Respin
Re: Two problems in MX-17 keyboard and screen
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.
What I am seeing is those numlock settings don't seem to be working on this machine like I would expect.
Lenovo M92p Quad Core i5 3470 3.2Ghz
Re: Two problems in MX-17 keyboard and screen
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.
I agree that engaged is not the default state, and the code I showed that proves it.
Production: 5.10, MX-23 Xfce, AMD FX-4130 Quad-Core, GeForce GT 630/PCIe/SSE2, 16 GB, SSD 120 GB, Data 1TB
Personal: Lenovo X1 Carbon with MX-23 Fluxbox and Windows 10
Other: Raspberry Pi 5 with MX-23 Xfce Raspberry Pi Respin
Personal: Lenovo X1 Carbon with MX-23 Fluxbox and Windows 10
Other: Raspberry Pi 5 with MX-23 Xfce Raspberry Pi Respin
Re: Two problems in MX-17 keyboard and screen
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.
Lenovo T430 i5/3320m 8GB MX17.1/Win7SP1 180GB SSD/128GB mSATA
Lenovo X230 i7/3520m 12GB MX17.1/Win7SP1 500GB SSD 480GB mSATA
Lenovo X131e i3/3227u 8GB MX21Xfce/Win7SP1 500GB SSD
Lenovo 11e Celeron n3150 4GB MX19/Fedora30Games 128GB SSD
Lenovo X230 i7/3520m 12GB MX17.1/Win7SP1 500GB SSD 480GB mSATA
Lenovo X131e i3/3227u 8GB MX21Xfce/Win7SP1 500GB SSD
Lenovo 11e Celeron n3150 4GB MX19/Fedora30Games 128GB SSD
Re: Two problems in MX-17 keyboard and screen
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.
MX 16.1 is saving it. That is what I can't figure out.
Lenovo M92p Quad Core i5 3470 3.2Ghz
Re: Two problems in MX-17 keyboard and screen
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.
I get the same behavior on that one as well.
Lenovo M92p Quad Core i5 3470 3.2Ghz