Half installation for a snap
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Snappy |
Fix Released
|
Critical
|
Unassigned |
Bug Description
I ran snap remove; got some busy messages; in the meantime did:
$ snap interfaces
Slot Plug
:firewall-control -
:home -
:locale-control -
:log-observe -
:mount-observe -
:network vscode
:network-bind vscode
:network-control -
:network-observe -
:opengl -
:snapd-control -
:system-observe -
:timeserver-control -
:timezone-control -
:unity7 vscode
:x11 -
- vscode:home
$ sudo snap connect vscode:home ubuntu-core:home
[\] Connect vscode:home to ubuntu-core:home
$ vscode
bash: /snap/bin/vscode: No such file or directory
$ ls /snap/bin/|wc -l
0
$ ls /snap/vscode/
100001
$ snap list
Name Version Developer
ubuntu-core 16.04+20160419.
vscode 1.0
$ snap changes
ID Status Spawn Ready Summary
1 Done 2016-04-
2 Done 2016-04-
3 Done 2016-04-
4 Error 2016-04-
5 Done 2016-04-
journalctl http://
Changed in snappy: | |
status: | In Progress → Fix Committed |
tags: |
added: verification-done removed: verification-needed |
Changed in snappy: | |
status: | Fix Committed → Fix Released |
The umount handling is not reliable yet: system/ snap-vscode- 100001. mount": [stop snap-vscode- 100001. mount] failed with exit status 1: Job for snap-vscode- 100001. mount failed. See "systemctl status snap-vscode- 100001. mount" and "journalctl -xe" for details.
, but continuing anyway.
"""
Failed to stop "/etc/systemd/
"""
This is leftover from the pre-state engine days. We will work on a fix.