Chaoimin

[Chaoimin]

So one thing I’m wondering about is what is the difference between a “/usr/NX/bin/nxserver --restart” and restarting SDDM, from nomachines perspective. I’d expect restarting the service would fix the issue after sleep state but it doesn’t, a SDDM restart does. So there is some part of nomachine that is stale and not affected by the nxserver restart. If I could get to that I could write a wrapper that executes after sleep and restart that specific part.

Is there a list somewhere with all the options like ‘DisplayServerExtraOptions “-eventdelay 0” ‘ I can try?

The output is from when I restarted SDDM, I’ll check again if the issue arises and see if any input device is missing. I wouldn’t know how to get it back after sleep without restarting SDDM though.

Output of DISPLAY=:0 xinput list –long :

~$ DISPLAY=:0 xinput list –long
⎡ Virtual core pointer                        id=2    [master pointer  (3)]
Reporting 3 classes:
Class originated from: 4. Type: XIButtonClass
Buttons supported: 10
Button labels: “Button Left” “Button Middle” “Button Right” “Button Wheel Up” “Button Wheel Down” “Button Horiz Wheel Left” “Button Horiz Wheel Right” None None None
Button state:
Class originated from: 4. Type: XIValuatorClass
Detail for Valuator 0:
Label: Rel X
Range: -1.000000 – -1.000000
Resolution: 0 units/m
Mode: relative
Class originated from: 4. Type: XIValuatorClass
Detail for Valuator 1:
Label: Rel Y
Range: -1.000000 – -1.000000
Resolution: 0 units/m
Mode: relative

⎜   ↳ Virtual core XTEST pointer                  id=4    [slave  pointer  (2)]
Reporting 3 classes:
Class originated from: 4. Type: XIButtonClass
Buttons supported: 10
Button labels: “Button Left” “Button Middle” “Button Right” “Button Wheel Up” “Button Wheel Down” “Button Horiz Wheel Left” “Button Horiz Wheel Right” None None None
Button state:
Class originated from: 4. Type: XIValuatorClass
Detail for Valuator 0:
Label: Rel X
Range: -1.000000 – -1.000000
Resolution: 0 units/m
Mode: relative
Class originated from: 4. Type: XIValuatorClass
Detail for Valuator 1:
Label: Rel Y
Range: -1.000000 – -1.000000
Resolution: 0 units/m
Mode: relative

⎜   ↳ SynPS/2 Synaptics TouchPad                  id=16    [slave  pointer  (2)]
Reporting 7 classes:
Class originated from: 16. Type: XIButtonClass
Buttons supported: 7
Button labels: “Button Left” “Button Middle” “Button Right” “Button Wheel Up” “Button Wheel Down” “Button Horiz Wheel Left” “Button Horiz Wheel Right”
Button state:
Class originated from: 16. Type: XIValuatorClass
Detail for Valuator 0:
Label: Rel X
Range: -1.000000 – -1.000000
Resolution: 0 units/m
Mode: relative
Class originated from: 16. Type: XIValuatorClass
Detail for Valuator 1:
Label: Rel Y
Range: -1.000000 – -1.000000
Resolution: 0 units/m
Mode: relative
Class originated from: 16. Type: XIValuatorClass
Detail for Valuator 2:
Label: Rel Horiz Scroll
Range: -1.000000 – -1.000000
Resolution: 0 units/m
Mode: relative
Class originated from: 16. Type: XIValuatorClass
Detail for Valuator 3:
Label: Rel Vert Scroll
Range: -1.000000 – -1.000000
Resolution: 0 units/m
Mode: relative
Class originated from: 16. Type: XIScrollClass
Scroll info for Valuator 2
type: 2 (horizontal)
increment: 120.000000
flags: 0x0
Class originated from: 16. Type: XIScrollClass
Scroll info for Valuator 3
type: 1 (vertical)
increment: 120.000000
flags: 0x0

⎣ Virtual core keyboard                       id=3    [master keyboard (2)]
Reporting 1 classes:
Class originated from: 5. Type: XIKeyClass
Keycodes supported: 248

↳ Virtual core XTEST keyboard                 id=5    [slave  keyboard (3)]
Reporting 1 classes:
Class originated from: 5. Type: XIKeyClass
Keycodes supported: 248

↳ Power Button                                id=6    [slave  keyboard (3)]
Reporting 1 classes:
Class originated from: 6. Type: XIKeyClass
Keycodes supported: 248

↳ Video Bus                                   id=7    [slave  keyboard (3)]
Reporting 1 classes:
Class originated from: 7. Type: XIKeyClass
Keycodes supported: 248

↳ Video Bus                                   id=8    [slave  keyboard (3)]
Reporting 1 classes:
Class originated from: 8. Type: XIKeyClass
Keycodes supported: 248

↳ Power Button                                id=9    [slave  keyboard (3)]
Reporting 1 classes:
Class originated from: 9. Type: XIKeyClass
Keycodes supported: 248

↳ Sleep Button                                id=10    [slave  keyboard (3)]
Reporting 1 classes:
Class originated from: 10. Type: XIKeyClass
Keycodes supported: 248

↳ AT Translated Set 2 keyboard                id=15    [slave  keyboard (3)]
Reporting 1 classes:
Class originated from: 15. Type: XIKeyClass
Keycodes supported: 248

[Chaoimin]

Hi,

I’ve sent two mails, one today and yesterday explaining what I experienced.
I hope this will help with a diagnosis on the issue.
Enabling the option in node.cfg didn’t fix the issue unfortunately.

Please let me know if there is anything I can do to help.

[Chaoimin]

Hey Britgirl,

This is a laptop I use daily so it’s not headless. For further reference: sddm runs on boot. The laptop contains a cpu/gpu and a Nvidia GTX980 mobile dedicated graphics card. External monitor is plugged in on the hdmi output, laptop screen is also used so it’s a dual screen setup.

[Author]

Posts