Screen flickering

Forum / NoMachine for Linux / Screen flickering

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • #26210
    majster
    Participant

    Hello!
    Recently our company started to work remotely (cause is kind of obvious :)), and one user has a screen flickering problem.
    I’ve search for similar problems but found no solution.
    Can you help me with that?

    Server is based on Ubuntu 18.04 Desktop, host is a Windows 10.

    lspci
    00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Host Bridge/DRAM Registers (rev 07)
    00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor PCIe Controller (x16) (rev 07)
    00:14.0 USB controller: Intel Corporation 100 Series/C230 Series Chipset Family USB 3.0 xHCI Controller (rev 31)
    00:16.0 Communication controller: Intel Corporation 100 Series/C230 Series Chipset Family MEI Controller #1 (rev 31)
    00:17.0 SATA controller: Intel Corporation Q170/Q150/B150/H170/H110/Z170/CM236 Chipset SATA Controller [AHCI Mode] (rev 31)
    00:1c.0 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #6 (rev f1)
    00:1f.0 ISA bridge: Intel Corporation H110 Chipset LPC/eSPI Controller (rev 31)
    00:1f.2 Memory controller: Intel Corporation 100 Series/C230 Series Chipset Family Power Management Controller (rev 31)
    00:1f.3 Audio device: Intel Corporation 100 Series/C230 Series Chipset Family HD Audio Controller (rev 31)
    00:1f.4 SMBus: Intel Corporation 100 Series/C230 Series Chipset Family SMBus (rev 31)
    01:00.0 VGA compatible controller: NVIDIA Corporation GM107 [GeForce GTX 750 Ti] (rev a2)
    01:00.1 Audio device: NVIDIA Corporation Device 0fbc (rev a1)
    02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 0c)

    lshw -C display
    WARNING: you should run this program as super-user.
    *-display
    description: VGA compatible controller
    product: GM107 [GeForce GTX 750 Ti]
    vendor: NVIDIA Corporation
    physical id: 0
    bus info: pci@0000:01:00.0
    version: a2
    width: 64 bits
    clock: 33MHz
    capabilities: vga_controller bus_master cap_list rom
    configuration: driver=nvidia latency=0
    resources: irq:127 memory:de000000-deffffff memory:c0000000-cfffffff memory:d0000000-d1ffffff ioport:e000(size=128) memory:c0000-dffff
    WARNING: output may be incomplete or inaccurate, you should run this program as super-user.

    nvidia-smi
    Thu Mar 26 10:50:33 2020
    +—————————————————————————–+
    | NVIDIA-SMI 390.116 Driver Version: 390.116 |
    |——————————-+———————-+———————-+
    | GPU Name Persistence-M| Bus-Id Disp.A | Volatile Uncorr. ECC |
    | Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. |
    |===============================+======================+======================|
    | 0 GeForce GTX 750 Ti Off | 00000000:01:00.0 On | N/A |
    | 42% 40C P0 2W / 38W | 1410MiB / 1999MiB | 4% Default |
    +——————————-+———————-+———————-++—————————————————————————–+
    | Processes: GPU Memory |
    | GPU PID Type Process name Usage |
    |=============================================================================|
    | 0 2370 G /snap/phpstorm/151/jbr/bin/java 11MiB |
    | 0 4088 G /usr/lib/xorg/Xorg 16MiB |
    | 0 7772 G /usr/bin/gnome-shell 49MiB |
    | 0 10524 C /usr/NX/bin/nxnode.bin 56MiB |
    | 0 15937 G /usr/lib/xorg/Xorg 429MiB |
    | 0 16136 G /usr/bin/gnome-shell 244MiB |
    | 0 16816 G …uest-channel-token=14058340162527162229 507MiB |
    | 0 18191 G …quest-channel-token=2206300300918407767 41MiB |
    | 0 26281 G …-token=138A3096CA93E1CB67539B3EA77AC965 43MiB |
    +—————————————————————————–+

    #26222
    fra81
    Moderator

    Hi,

    please try to edit the /usr/NX/etc/node.cfg file on the server machine by adding the following line:

    EnableHardwareEncoding 0

    Then restart the NoMachine service:

    /usr/NX/bin/nxserver --restart

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

Closed because the user did not provide further feedback. Please notify us if you confirm that it is resolved or open a new topic if you have the same problem.