Web browser not starting

Forums / NoMachine for Raspberry Pi / Web browser not starting

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #30887
    AvatarGregosh
    Participant

    Hello.

    I updated NoMachine to the version 7.0.211 which is running on Raspberry Pi 4 (Linux raspberrypi 5.4.79-v7l+ ).
    On the second computer I have Ubuntu 20.04.1 LTS with NoMachine 7.0.211.

    There is something strange, because when I connect to NoMachine in Raspberry Pi I’m not able to start browser.
    The chromium-browser gives me some strange error about bug, and the firefox-esr gives me nothing but the window is not opened.

    With earlier versions of NoMachine everything works smoothly without any problem. And it seems that the rest of applications are working correctly.

    And finally, when I connect to Raspberry monitor with HDMI cable everything works correctly and the  browsers are starting correctly – the window is shown.

    Does anybody have an idea what is the trouble? Or what I could try to find solution and be able to start browser over NoMachine connection?

    Thanks,
    Grzegorz

    #31006
    Avatarkroy
    Contributor

    Hi.

    We aren’t able to reproduce. It’s little looks like when you have monitor unplugged – desktop isn’t detected somehow and then you are creating a new desktop during connection. Because physical exists and you are created a new one with the same user – browser is opening on other display (or just cannot be open on this display). Is could be the case?

    Please try Tip 2: Connecting to a headless Raspberry from article: https://www.nomachine.com/tips-on-how-to-set-up-your-raspberry-pi-for-remote-access-via-nomachine

    Edit RPi config file sudo vim /boot/config.txt, find, uncomment and set key: hdmi_force_hotplug=1. Save the file and reboot device.

    #31009
    AvatarGregosh
    Participant

    Hello.

    Thank you foryYour response.
    There was something wrong with updating. Because I had no new installation of NoMachine but I updated existing one.
    I found that the NoMachine was connected to the DISPLAY:1003.0 and my Raspberry Pi enviroment DISPLAY was set as 1002.0.

    I didn’t know how to align the numbers of DISPLAY variable so I  applied the simplest solution. I removed existing configuration files and reinstalled NoMachine.

    And everything works as before. And I enjoy the remote pulpit of my Raspberry Pi with NoMachine.

    But Thank You again. And you are doing great work with this software!

    Regards.
    Grzegorz

    #31039
    AvatarBritgirl
    Keymaster

    Thanks for letting us know.

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

This topic was marked as solved, you can't post.