Classic snap fails to run

Bug #1668349 reported by Alan Pope 🍺🐧🐱 🦄
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
snapd
Incomplete
Undecided
Jamie Strandboge

Bug Description

$ snap version
snap 2.22.7
snapd 2.22.7
series 16
ubuntu 16.04
kernel 4.4.0-64-generic

git clone https://github.com/popey/hollywood.git
cd hollywood
snapcraft
sudo snap install hollywood_1.12_amd64.snap --dangerous --classic

hollywood

What should happen is the multi-window entertaining ascii art stuff should appear

What actually happens:-

runtime/cgo: runtime/cgo: runtime/cgo: pthread_create failed: Resource temporarily unavailable
runtime/cgo: pthread_create failed: Resource temporarily unavailable
runtime/cgo: pthread_create failed: Resource temporarily unavailable
runtime/cgo: pthread_create failed: Resource temporarily unavailable

[lun feb 27 18:27:03 2017] audit: type=1400 audit(1488216423.507:1173): apparmor="DENIED" operation="file_inherit" profile="/usr/lib/snapd/snap-confine" name="/dev/tty" pid=24928 comm="snap-confine" requested_mask="wr" denied_mask="wr" fsuid=1000 ouid=0

Revision history for this message
Leo Arias (elopio) wrote :

Hey popey, are you running from ssh into a remote machine?
This sounds like bug #1664427, and they are blaming ssh in the comments there.

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

Jamie I assigned this to you while I'm on holidays, it looks like a simple profile change for snap-confine so that it can work when invoked remotely over ssh. Feel free to re-assign this with clear instructions as to how to proceed wrt security.

Changed in snappy:
assignee: nobody → Jamie Strandboge (jdstrand)
Revision history for this message
Alan Pope 🍺🐧🐱 🦄 (popey) wrote : Re: [Bug 1668349] Re: Classic snap fails to run

No. I did this hands on to the physical machine.

On 27 Feb 2017 23:31, "Leo Arias" <email address hidden> wrote:

> Hey popey, are you running from ssh into a remote machine?
> This sounds like bug #1664427, and they are blaming ssh in the comments
> there.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1668349
>
> Title:
> Classic snap fails to run
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/snappy/+bug/1668349/+subscriptions
>

Revision history for this message
Jamie Strandboge (jdstrand) wrote :

I'm unable to reproduce this with snapd 2.22.6 (not sure where you got 2.22.7) on series 16 with kernel 4.4.0-64.85-generic. It works fine logged into a console, in unity7 in a gnome terminal (under the terminal, screen, tmux and byobu) and in ssh. Are you able to reproduce reliably? If so, can you add this to /etc/apparmor.d/usr.lib.snapd.snap-confine:

/dev/tty rw,

then do:
$ sudo apparmor_parser -r /etc/apparmor.d/usr.lib.snapd.snap-confine

Then run the command and report back any stdout/stderr from the invocation? (I suspect something else is failing and snap-confine may be trying to display something somewhere)

Changed in snappy:
status: New → Incomplete
Revision history for this message
Ian Johnson (anonymouse67) wrote :

I tried building and running this snap and it doesn't display anything in the terminal for me on bionic desktop through a X11 session. It just hangs without any output, but I also don't see any denials in the journal.

Michael Vogt (mvo)
affects: snappy → snapd
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.