giobaxx

Forum Replies Created

Viewing 8 posts - 1 through 8 (of 8 total)
  • Author
    Posts
  • in reply to: NoMachine issue with Ubuntu 18.04 #27045
    Avatargiobaxx
    Participant

    I think is the session with problems affecting my collegue: (attachment)

    in reply to: NoMachine issue with Ubuntu 18.04 #27015
    Avatargiobaxx
    Participant

    Thanks again

    I will try to collect but I don’t know if I can sent depends on the information he collects. There are data that I cannot share, username, ip address…

    However is very strange.

    We are remoting to the same Physical Ubuntu 18.04  from a Virtual Windows 2012 remote server that is used as Remote Desktop Gateway.

    Basically we connect via rdp to Windows and within Windows we run NoMachine.

    I don’t have any problems with my session, while he has problems with his session. We remote to the same physical Ubuntu Workstation from a Windows 2012 that for sure has the same configuration. Basically it is the same VM for everyone.

    I don’t know if the user did something who can breaks the configuration, however it worked smoothly at the beginning and now there isn’t way to make it work at least at least for him. It worked also before I modified the WayLand configuration.

    Maybe reinstalling NoMachine in the Ubuntu Ws can solve?

     

    ūüôĀ

    in reply to: NoMachine issue with Ubuntu 18.04 #27011
    Avatargiobaxx
    Participant

    It is Standard Ubuntu 18.04 Gnome. Today I have uncommented the line WaylandEnable=False and I have rebooted the system.

    It works fine for me, I tried few times and I didn’t have any problems but not for the user that have to work remotely.

    He connect to the login screen of Ubuntu but it didn’t appear any login name or a box where to login and if it click on the screen¬† he become black.

     

    in reply to: NoMachine issue with Ubuntu 18.04 #26987
    Avatargiobaxx
    Participant

    update

    It seems to be better but now the user seems to have duplicated Icon over the desktop

    in reply to: NoMachine issue with Ubuntu 18.04 #26979
    Avatargiobaxx
    Participant

    For the moment i’ve tried to update Ubuntu ed I’m testing now if it works with some stability or not. If it is not stable I will uncomment¬† ¬†WaylandEnable=False and I will reboot the system, previously i restarted only the gdm service:

    I run the command you told me below the result:

    Kernel Used:  4.15.0-96-generic

    lshw -C display:

    *-display

    description: VGA compatible controller

    product: Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller

    vendor: Intel Corporation

    physical id: 2

    bus info: pci@0000:00:02.0

    version: 06

    width: 64 bits

    clock: 33MHz

    capabilities: msi pm vga_controller bus_master cap_list rom

    configuration: driver=i915 latency=0

    resources: irq:32 memory:f7800000-f7bfffff memory:e0000000-efffffff ioport:f000(size=64) memory:c0000-dffff

     

    Thanks! I will give update after few test

    in reply to: NoMachine issue with Ubuntu 18.04 #26966
    Avatargiobaxx
    Participant

    First thanks to all

    Yes after a reboot  it works,  sometimes i just need to restart the service and kill all the process but if i disconnect and reconnect most of the time i have the white screen, not always but often.

    • PhysicalDesktopMode and VirtualDesktopMode are both commented in the server.cfg
    • I have also tried to uncomment the wayland=false on the¬†¬†/etc/gdm3/custom.conf and the I have restarted gdm3 services, the result it is not a white page but it not working fine. Maybe I need restart?

    In One of the session log, the one owned by gdm I found this error:

    Info: Agent running with pid 7343.

    Info: Slave server running with pid 7355.

    Info: Display running with pid 7356.

    Info: Listening to slave connections on port 12001.

    Info: Audio server started with pid 7369.

    Info: Audio client started with pid 7370.

    Info: Display server started with pid 7371.

    Session: Session started at Wed Apr 22 17:51:28 2020.

    7343 7356 17:52:01 331.448 DrmGrabber: ERROR! Failed to get fb info.

    7343 7356 17:52:01 331.470 DrmGrabber: ERROR! FbInfo init failed.

    7343 7356 17:52:01 331.474 WaylandPoller: Init failed.

    7343 7356 17:52:01 332.324 WaylandPoller: WARNING! Failed to restore screen info without having DBus connection.

    nxagentShadowInit: ERROR! Failed to initialize the shadow display.

    Info: RT handler running with pid 7523.

    Info: Display server for 3162E3853F7D555722428812693C4E0C connected on Wed Apr 22 17:52:01 2020.

    Info: Audio server for 3162E3853F7D555722428812693C4E0C connected on Wed Apr 22 17:52:01 2020.

    Info: Audio client for 3162E3853F7D555722428812693C4E0C connected on Wed Apr 22 17:52:01 2020.

    Info: Audio reader running with pid 7556.

     

    Just for info the Video Diver is an Intel i915 I need to remove the driver enabling nouveau?

     

     

    in reply to: NoMachine issue with Ubuntu 18.04 #26950
    Avatargiobaxx
    Participant

    Thanks for you reply I started to look under that folder but now i need to understand what to look for

    There are some folder where i’m the owner but some others as gdm as owner.¬† Basically i have 5 subfolder under the path in two i’m the owner and the other are owned by gdm.

    • one name folder start with C-hostname-1001-…..
    • the rest of the others folders is named with F-C-hostname-1001-….

    This five folder correspond to five issue?  Within the folders i need to check the session file for the errors?

    in reply to: Login loop Ubuntu 18.04 #24297
    Avatargiobaxx
    Participant

    РIs trying to connect with  a Windows 10 Workstation to an Ubuntu VM using NoMachine. He is able to connect with the Ubuntu VM with the NoMachine Player, but when he try to authenticate in Ubuntu no way to login.

    i’m new on the NoMachine so just to have a first good connection we needed to change some file in the

    1. Uncomment the following row   WaylandEnable=false   in the configuration file /etc/gdm3/custom.conf  and restarted the service
    2. Uncomment the following row PhisicalDesktopAuthorization 0 in the configuration file /usr/NX/server.cfg and restarted the service
    3. If i try to connect to the VM with my account from my Windows 7 Workstation i don’t have problems apart some strange behaviour during the login phase. Whe he tried form his Windows 10 Workstation

    I tried to connect via VMware Console and the problem is the same, probably i need to reboot the VM after disabling Wayland, and restarting the service is not the enough?

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