You can do this as a command, or by adding this line to a profile (such as ~/.bash_profile) so that it gets read automatically at the start of each session. If you check your local DISPLAY variable (with echo $DISPLAY), you may see an equally strange value: echo $DISPLAYĮssentially, you need to do the exact inverse of the above fix: explicitly set the value of DISPLAY in your environment before launching an X app on a remote host: export DISPLAY=localhost:0 X connection to localhost:39.0 broken (explicit kill or server shutdown). (nodename nor servname provided, or not known) Inversely, in the version of X native to OS X 10.5.2, you may see a wacky-looking error like the following when launching an X application on a remote host: /tmp/launch-rkTZqq/: unknown host. You’ll also need to not launch X11 explicitly: let the OS launch it for you on its own when you request an X application (test by running xterm or xclock from a terminal). Try removing any commands that export a DISPLAY value to your environment (such as ‘ export DISPLAY=something‘), logging out of your current sessions, and see if you can successfully launch your X app. … it’s probably the case that you need to un-set your DISPLAY variable. … or like this on a remote host: connect localhost port 6000: Connection refused If you’re seeing errors like this on your side when launching an X application: Error: Can't open display: localhost:0 But if you’re running the latest version of Leopard (10.5.3), X11 (2.2.1), and Xquartz (1.3.0), doing so is not only unnecessary, but it can keep your X sessions from launching properly. It used to be the case that in order to get X working remotely from an OS X machine, you needed to set your DISPLAY system variable to something that made sense to non-Mac systems (such as “ localhost:0“). Getting these two to work in concert once one of them, or the operating system itself, has been upgraded can be frustrating. OS X employs a combination of the X.org package and Xquartz, a component included in Mac’s X (or X11) to help it run on OS X. Not sure how this is related, but seems connected, somehow.Here are two of the biggest problems I’ve come across in using X11 with SSH connections, and how to get around them. I was unable to get virt-viewer working over the LAN into the 21.10 system, but it does work find on the same physical system. On the LAN, I use ssh -X almost always, but for play, I'll use virt-viewer with QXL drivers. My normal remote desktop over the internet is x2go, which doesn't support Wayland at all. I know the ~/.Xauthority file stuff worked in 20.04 for Chromium. When they did the same with Chromium in 20.04, other people created a deb package and multiple PPAs became available. I don't know if other versions will be possible or not from Canonical. My ssh -X test above was into a Wayland running 21.10, btw.įirefox in 21.10 **is** using a snap package. Looks like Wayland users may have to use WayVNC - or am I misreading that? This is a 21.10 regression.Is your 21.10 using Wayland or X11? The browser works fine in VNC server now. I reverted to 21.04 from an Acronis backup. Last edited by guiverc October 17th, 2021 at 10:48 PM. If using the deb package I'd not expect any changes.įYI: N0rbert has documented that you can stop `update-manager` from converting the deb package to snap if you mark the package as manually-installed, ie. `update-manager` is not installed for all flavors but tends to be there for GTK+ flavors (so it won't be found in Lubuntu, Kubuntu, Ubuntu Studio). There are some known issues with the snap package the reported ones are being worked on so issues get fixed (before 22.04/ jammy at a minimum).įor flavors the firefox package remains a deb package however it'll change to snap also if `update-manager` is run for any reason. If you run `update-manager`, or performed `do-release-upgrade` from mid- beta cycle or later (with Ubuntu Desktop not flavors), the deb package of `firefox` gets removed and replaced by a snap package. Last edited by madbrain October 17th, 2021 at 01:23 PM.Īre (or were?) you using the `firefox` as a deb or snap package? Just won't run on remote display anymore. Tigervnc-standalone-server/impish,now 1.11.0+dfsg-2ubuntu1 amd64 there a workaround for this ? Not being able to run a browser is pretty bad.įirefox does run fine on the local display. Tigervnc-common/impish,now 1.11.0+dfsg-2ubuntu1 amd64 WARNING: apt does not have a stable CLI interface. Other X programs such as xcalc or gnome-terminal do firefoxĮrror: cannot open display: cat serverĮxecStartPre=-/usr/bin/vncserver -kill :1 > /dev/null 2>&1ĮxecStart=/usr/bin/vncserver -geometry 3840x2160 -localhost no :%iĮxecStop=/usr/bin/vncserver -kill cat ~/.vnc/xstartupĭbus-launch apt list -installed | grep -i vnc
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |