Can't get snap gui apps (notepadqq and firefox) to run in LXD/LXC container

Bug #1773044 reported by Bill Wood
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Snappy
Invalid
Undecided
Unassigned

Bug Description

When starting notepadqq or firefox I get ln errors such as:
ln: failed to create symbolic link '/home/ubuntu/snap/notepadqq/841/snap/notepadqq/841/Documents': No such file or directory
ln: failed to create symbolic link '/home/ubuntu/snap/notepadqq/841/snap/notepadqq/841/Desktop': No such file or directory
ln: failed to create symbolic link '/home/ubuntu/snap/notepadqq/841/snap/notepadqq/841/Downloads': No such file or directory
ln: failed to create symbolic link '/home/ubuntu/snap/notepadqq/841/snap/notepadqq/841/Music': No such file or directory
ln: failed to create symbolic link '/home/ubuntu/snap/notepadqq/841/snap/notepadqq/841/Pictures': No such file or directory
ln: failed to create symbolic link '/home/ubuntu/snap/notepadqq/841/snap/notepadqq/841/Videos': No such file or directory
ln: failed to create symbolic link '/home/ubuntu/snap/notepadqq/841/snap/notepadqq/841/Templates': No such file or directory

Then the gui window does not display but the app keeps running, eventually getting this error:
QXcbConnection: Could not connect to display :0
Aborted (core dumped)

x11 apps (such as firefox) work fine if installed with apt.

The host is running Ubuntu 18.04 and so is the container.

dmesg shows this error for notepadqq:

[349363.925230] audit: type=1107 audit(1527123518.868:1456): pid=516 uid=103 auid=4294967295 ses=4294967295 msg='apparmor="DENIED" operation="dbus_signal" bus="system" path="/org/freedesktop/NetworkManager/ActiveConnection/7" interface="org.freedesktop.NetworkManager.Connection.Active" member="PropertiesChanged" name=":1.10" mask="receive" pid=25488 label="snap.notepadqq.notepadqq" peer_pid=545 peer_label="unconfined"

description: updated
description: updated
description: updated
description: updated
Revision history for this message
Zygmunt Krynicki (zyga) wrote :

NOTE: the apparmor denial is not relate dto the problem.

I don't think this is something strictly related to snapd. If anything I suspect that LXD needs to support this use case and extend its own sandbox accordingly. I'm adding a lxd task to track this.

Revision history for this message
Zygmunt Krynicki (zyga) wrote :

Hmm, LXD is using github for bug tracking. Not sure what to do.

Changed in snappy:
status: New → Invalid
Revision history for this message
Zygmunt Krynicki (zyga) wrote :

I'm marking this bug as invalid. I'll let LXD developers know to have a look and mirror this bug on their side.

Revision history for this message
Stéphane Graber (stgraber) wrote :

How did you configure your container to talk to X11 in the first place?

The error suggests that the X11 abstract Unix socket isn't available in your container.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.