Jethro_uk

Forum Replies Created

Viewing 7 posts - 1 through 7 (of 7 total)
  • Author
    Posts
  • in reply to: Input issues between Win10 Client and Linux Mint server #42211
    Jethro_uk
    Participant

    I’m afraid I haven’t. But it’s still occurring from time to time. It’s definitely some process “stealing” the “ctrl+” input and not releasing it.

    Workaround is to close the NoMachine window (not session, for a clue) and reconnect. Since I have a workaround I can live with the bug. However YMMV.

    in reply to: Input issues between Win10 Client and Linux Mint server #40482
    Jethro_uk
    Participant

    System:    Kernel: 5.4.0-126-generic x86_64 bits: 64 compiler: gcc v: 9.4.0
    Desktop: Cinnamon 5.2.7 wm: muffin dm: GDM3 Distro: Linux Mint 20.3 Una
    base: Ubuntu 20.04 focal
    Machine:   Type: Laptop System: Hewlett-Packard product: HP ProBook 650 G1 v: A3009DD10303
    serial: <filter> Chassis: type: 10 serial: <filter>
    Mobo: Hewlett-Packard model: 1993 v: KBC Version 16.39 serial: <filter>
    BIOS: Hewlett-Packard v: L77 Ver. 01.20 date: 07/17/2014
    Battery:   ID-1: BAT0 charge: 46.4 Wh condition: 48.2/48.2 Wh (100%) volts: 12.3/10.8
    model: Hewlett-Packard Primary serial: <filter> status: Unknown
    CPU:       Topology: Dual Core model: Intel Core i3-4000M bits: 64 type: MT MCP arch: Haswell
    rev: 3 L2 cache: 3072 KiB
    flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 19156
    Speed: 2395 MHz min/max: 800/2400 MHz Core speeds (MHz): 1: 2395 2: 2395 3: 2395
    4: 2395
    Graphics:  Device-1: Intel 4th Gen Core Processor Integrated Graphics vendor: Hewlett-Packard
    driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:0416
    Display: x11 server: X.Org 1.20.13 driver: modesetting unloaded: fbdev,vesa
    resolution: 1366×768~60Hz
    OpenGL: renderer: Mesa DRI Intel HD Graphics 4600 (HSW GT2) v: 4.5 Mesa 21.2.6
    compat-v: 3.0 direct render: Yes
    Audio:     Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio vendor: Hewlett-Packard
    driver: snd_hda_intel v: kernel bus ID: 00:03.0 chip ID: 8086:0c0c
    Device-2: Intel 8 Series/C220 Series High Definition Audio vendor: Hewlett-Packard
    driver: snd_hda_intel v: kernel bus ID: 00:1b.0 chip ID: 8086:8c20
    Sound Server: ALSA v: k5.4.0-126-generic
    Network:   Device-1: Intel Ethernet I217-V vendor: Hewlett-Packard driver: e1000e v: 3.2.6-k
    port: 3080 bus ID: 00:19.0 chip ID: 8086:153b
    IF: enp0s25 state: down mac: <filter>
    Device-2: Broadcom and subsidiaries BCM43228 802.11a/b/g/n driver: wl v: kernel
    port: ef80 bus ID: 02:00.0 chip ID: 14e4:4359
    IF: wlo1 state: up mac: <filter>
    Drives:    Local Storage: total: 223.57 GiB used: 222.05 GiB (99.3%)
    ID-1: /dev/sda model: SATA3 240GB SSD size: 223.57 GiB speed: 6.0 Gb/s serial: <filter>
    Partition: ID-1: / size: 216.82 GiB used: 110.44 GiB (50.9%) fs: ext4 dev: /dev/dm-1
    ID-2: /boot size: 702.1 MiB used: 215.8 MiB (30.7%) fs: ext4 dev: /dev/sda5
    ID-3: swap-1 size: 976.0 MiB used: 976.0 MiB (100.0%) fs: swap dev: /dev/dm-2
    USB:       Hub: 1-0:1 info: Full speed (or root) Hub ports: 2 rev: 2.0 chip ID: 1d6b:0002
    Hub: 1-1:2 info: Intel ports: 6 rev: 2.0 chip ID: 8087:8008
    Hub: 2-0:1 info: Full speed (or root) Hub ports: 2 rev: 2.0 chip ID: 1d6b:0002
    Hub: 2-1:2 info: Intel ports: 8 rev: 2.0 chip ID: 8087:8000
    Hub: 3-0:1 info: Full speed (or root) Hub ports: 14 rev: 2.0 chip ID: 1d6b:0002
    Device-1: 3-5:2 info: Validity Sensors VFS495 Fingerprint Reader
    type: <vendor specific> driver: N/A rev: 1.1 chip ID: 138a:003f
    Device-2: 3-7:3 info: Chicony HP HD Webcam type: Video driver: uvcvideo rev: 2.0
    chip ID: 04f2:b3ed
    Device-3: 3-12:4 info: Broadcom HP Portable Bumble Bee type: <vendor specific>
    driver: btusb rev: 2.0 chip ID: 0a5c:21f1
    Hub: 4-0:1 info: Full speed (or root) Hub ports: 6 rev: 3.0 chip ID: 1d6b:0003
    Sensors:   System Temperatures: cpu: 49.0 C mobo: 0.0 C
    Fan Speeds (RPM): N/A
    Repos:     No active apt repos in: /etc/apt/sources.list
    Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list
    1: deb http: //packages.linuxmint.com una main upstream import backport #id:linuxmint_main
    2: deb http: //archive.ubuntu.com/ubuntu focal main restricted universe multiverse
    3: deb http: //archive.ubuntu.com/ubuntu focal-updates main restricted universe multiverse
    4: deb http: //archive.ubuntu.com/ubuntu focal-backports main restricted universe multiverse
    5: deb http: //security.ubuntu.com/ubuntu/ focal-security main restricted universe multiverse
    6: deb http: //archive.canonical.com/ubuntu/ focal partner
    Active apt repos in: /etc/apt/sources.list.d/signal-xenial.list
    1: deb [arch=amd64 signed-by=/usr/share/keyrings/signal-desktop-keyring.gpg] https: //updates.signal.org/desktop/apt xenial main
    Info:      Processes: 292 Uptime: 7d 2h 01m Memory: 3.75 GiB used: 2.60 GiB (69.2%) Init: systemd
    v: 245 runlevel: 5 Compilers: gcc: 9.4.0 alt: 9 Client: Unknown python3.8 client
    inxi: 3.0.38

    in reply to: Can’t connect until local user logged in #24451
    Jethro_uk
    Participant

    # /usr/NX/bin/nxserver --userlist

    All was making sense until I tried this, and got :

    -bash: /usr/NX/bin/nxserver: No such file or directory

    So I’m going to have to cram up on “How Macs work” and get back to you.

    in reply to: Force login to physical desktop each connection? #22399
    Jethro_uk
    Participant

    Many thanks for replying – and it seems you have nailed it 🙂

    1) For some reason my server.cfg had CreateDisplay
    set to “1”. I changed this. Then issuing the nxserver –restart command threw up an error:

    NX> 162 Disabled service: nxserver.
    NX> 162 Service: nxnode already disabled.
    NX> 162 Disabled service: nxd.
    NX> 111 New connections to NoMachine server are enabled.
    NX> 161 Enabled service: nxserver.
    NX> 162 WARNING: Cannot find X servers running on this machine.
    NX> 162 WARNING: A new virtual display will be created on demand.
    NX> 161 Enabled service: nxd.

    AHA ! – So there really was no XServer running. For my particular machine, running:

     

    sudo service lightdm restart

     

    seemed to do the trick. The nxserver –restart then seemed happy. And connecting to the machine, I got the login window I used to get.

     

    Case closed !

    in reply to: Force login to physical desktop each connection? #22373
    Jethro_uk
    Participant

    Update:

    One thing that has also started happening which never used to, is I am getting a message:

    “Cannot detect any display running. Do you want NoMachine to create a new display and proceed to connect to the desktop?”

     

    Something has definitely changed and it happened Friday 17th May between 15:00 and 17:00 (when I rebooted).

    How can I tell ??

     

    root@DebServer64:/usr/NX/etc# /usr/NX/bin/nxserver –history

    Display Username Remote IP      Session ID                       Date                Status    Node           Type
    ——- ——– ————– ——————————– ——————- ——— ————– ———————
    1002    <me>    192.168.10.121 C83E52E2413B3C3A44087441788D4D9E 2019-05-20 10:23:31 Connected localhost:4000 physical-desktop
    1001    <me>    127.0.0.1      537BAD14602419F1A046F59F71B7EDA8 2019-05-20 10:23:16 Connected localhost:4000 nxvfb
    1001    <me>    127.0.0.1      1B899ABD747C0F4B2630D5537416A1A6 2019-05-19 17:47:37 Unknown   localhost:4000 nxvfb
    1002    <me>    192.168.10.121 547A00D1AE4DB49948A68D52C30A978D 2019-05-19 17:47:36 Finished  localhost:4000 physical-desktop
    1001    <me>    127.0.0.1      120334A8C4DD86401BE1A514790BE585 2019-05-19 17:42:08 Unknown   localhost:4000 nxvfb
    1002    <me>    192.168.10.121 AA20A4B78F52D06DA27A58B7B07578FE 2019-05-19 17:42:07 Finished  localhost:4000 physical-desktop
    1001    <me>    127.0.0.1      2D4B96A508E82A641D340E1282A89DFE 2019-05-19 17:40:41 Unknown   localhost:4000 nxvfb
    1002    <me>    192.168.10.121 121CC38040B6C77AB18F4E5AEFBE3617 2019-05-19 17:40:40 Finished  localhost:4000 physical-desktop
    1001    <me>    127.0.0.1      8B2721312B3CE930AFA99D14054D232E 2019-05-19 17:37:19 Finished  localhost:4000 nxvfb
    1002    <me>    192.168.10.121 E089A58AAB8B33AF1C77FD41AFCA26C9 2019-05-19 17:37:18 Finished  localhost:4000 physical-desktop
    1001    <me>    127.0.0.1      AE0EAB375E614FF4E336A7F312091148 2019-05-19 12:29:57 Unknown   localhost:4000 nxvfb
    1002    <me>    192.168.10.121 9885DF6930AC9CC4C19FF54CFA9AD775 2019-05-19 12:29:56 Finished  localhost:4000 physical-desktop
    1001    <me>    127.0.0.1      3E270F8277A0CB426AC70DA0D234CB31 2019-05-19 12:29:37 Unknown   localhost:4000 nxvfb
    1002    <me>    192.168.10.121 81FA83041818252EFF90B82F3EF2FC4A 2019-05-19 12:29:36 Finished  localhost:4000 physical-desktop
    1002    <me>    192.168.10.121 C7D056942A0A24009E7DFFC75C233A4B 2019-05-19 12:12:40 Finished  localhost:4000 physical-desktop
    1001    <me>    127.0.0.1      28ED4B6310C4A93B82A5F8D7AC67D2ED 2019-05-19 11:36:00 Unknown   localhost:4000 nxvfb
    1002    <me>    192.168.10.121 7C0236499F65EC1DEC42941D3ED56CA2 2019-05-19 11:35:59 Finished  localhost:4000 physical-desktop
    1001    <me>    127.0.0.1      C46EB1B5AF9510C9B05263E24D3230ED 2019-05-17 18:13:21 Unknown   localhost:4000 nxvfb
    1002    <me>    192.168.10.121 B725AC3DE242A8A79C65CED9A85231AB 2019-05-17 18:13:20 Finished  localhost:4000 physical-desktop
    1001    <me>    127.0.0.1      AE8D6FC2BDAE83167C003CBDA9E1469D 2019-05-17 17:36:42 Unknown   localhost:4000 nxvfb
    1002    <me>    192.168.10.121 FFD539233FE076A5B5DAFF1B1FDB5F17 2019-05-17 17:36:41 Finished  localhost:4000 physical-desktop
    1001    <me>    127.0.0.1      AF788CB8085A2459F606415124D0B1B5 2019-05-17 17:03:19 Unknown   localhost:4000 nxvfb
    1002    <me>    192.168.10.121 B3A7CC04EC614C84303E93EF0E1FD084 2019-05-17 17:03:18 Finished  localhost:4000 physical-desktop
    1002    <me>    192.168.10.121 2C0E73D69DD351036DD5BA3CB1320127 2019-05-17 15:29:10 Finished  localhost:4000 physical-desktop
    1002    <me>    192.168.10.121 918776577BAC26A31976B2FA5B6C868B 2019-05-17 11:25:46 Finished  localhost:4000 physical-desktop
    1002    <me>    192.168.10.121 5C032D100BC941880F94996199184D53 2019-05-17 11:17:57 Finished  localhost:4000 physical-desktop
    1002    <me>    192.168.10.121 625DB467FA813BD00267B3D9A32E70E2 2019-05-17 10:14:16 Finished  localhost:4000 physical-desktop
    1002    <me>    192.168.10.121 D3A47A0374DCA3AD55D01ED7020877D0 2019-05-16 17:34:14 Finished  localhost:4000 physical-desktop
    1002    <me>    192.168.10.121 97854D8175F0E2CE07E6D1F807187B76 2019-05-16 16:26:16 Finished  localhost:4000 physical-desktop
    1002    <me>    192.168.10.121 BE9DC3975836726533820AB397525EF7 2019-05-16 14:52:14 Finished  localhost:4000 physical-desktop
    1002    <me>    192.168.10.121 C5C940CE50933295D5F0F72FF6E1CF6F 2019-05-15 10:01:38 Finished  localhost:4000 physical-desktop
    1002    <me>    192.168.10.121 7515C23D01CAA1AE7EA9B2CC8B44692F 2019-05-14 17:19:46 Finished  localhost:4000 physical-desktop
    1002    <me>    192.168.10.121 653619E76F0FAD99C5220407F814370B 2019-05-14 10:45:01 Finished  localhost:4000 physical-desktop
    1002    <me>    192.168.10.121 D7CDB59E2986D57592607B8B14AB1806 2019-05-13 17:51:02 Finished  localhost:4000 physical-desktop
    1002    <me>    192.168.10.121 B91FCC2A0F093711FCC7C2E321D8B658 2019-05-08 14:03:01 Finished  localhost:4000 physical-desktop

     

    in reply to: Connecting to console oddity? #22181
    Jethro_uk
    Participant

    Touch wood, that’s done the trick …

    in reply to: NoMachine forgetting credentials after a while #19817
    Jethro_uk
    Participant

    Tx will get back to you 🙂

Viewing 7 posts - 1 through 7 (of 7 total)