core icon indicating copy to clipboard operation
core copied to clipboard

Midori armhf snap not starting on Ubuntu 16.04 under VNC

Open tjyrinki opened this issue 5 years ago • 2 comments

Not sure why, but I'm getting the following on my ARM server running Ubuntu 16.04:

$ /snap/bin/midori 
Failed to connect to Mir: Failed to connect to server socket: No such file or directory
Unable to init server: Could not connect: Connection refused

(midori:25278): Gtk-WARNING **: cannot open display: :1

Snaps installed are: core 16-2.38 6676 stable canonical# core midori v8.0 453 stable kalikiana -

The "desktop" setup is Xtightvnc + metacity + xterm. 'midori' from the deb archives works fine, and so does at least for example 'gedit' which is GTK+3 app.

tjyrinki avatar Apr 16 '19 13:04 tjyrinki

OTOH I just tried gedit --candidate snap:

core18             20190409                   942   stable     canonical#  base
gedit              3.32.0+git17.b8103e44a     242   candidate  canonical#  -
gnome-3-28-1804    3.28.0-9-gce87599.ce87599  25    stable     canonical#  -
gtk-common-themes  0.1-16-g2287c87            1198  stable     canonical#  -
$ /snap/bin/gedit 
Unable to init server: Could not connect: Connection refused

(org.gnome.gedit:26710): Gtk-WARNING **: 13:05:17.804: cannot open display: :1

So whatever the problem is, it's related to snapping, even though no Mir complaint in case of gedit.

tjyrinki avatar Apr 16 '19 13:04 tjyrinki

I ran into a similar situation trying to run Midori from a Snap install on Ubuntu 20.04 in XFCE4 over VNC. Apparently, I needed to add myself to xhost based on this rec:

xhost +si:localuser:$USER

yoda-vid avatar May 30 '22 08:05 yoda-vid