Translations by JungHee Lee

The abort command attempts to abort a change that still has pending tasks.

The buy command buys a snap from the store.

The connect command connects a plug to a slot. It may be called in the following ways: $ snap connect <snap>:<plug> <snap>:<slot> Connects the provided plug to the given slot. $ snap connect <snap>:<plug> <snap> Connects the specific plug to the only slot in the provided snap that matches the connected interface. If more than one potential slot exists, the command fails. $ snap connect <snap>:<plug> Connects the provided plug to the slot in the core snap with a name matching the plug name.

The create-user command creates a local system user with the username and SSH keys registered on the store account identified by the provided email address. An account can be setup at https://login.ubuntu.com.

The debug command contains a selection of additional sub-commands. Debug commands can be removed without notice and may not work on non-development systems.

The get command prints configuration options for the current snap. $ snapctl get username frank If multiple option names are provided, a document is returned: $ snapctl get username password { "username": "frank", "password": "..." } Nested values may be retrieved via a dotted path: $ snapctl get author.name frank Values of interface connection settings may be printed with: $ snapctl get :myplug usb-vendor $ snapctl get :myslot path This will return the named setting from the local interface endpoint, whether a plug or a slot. Returning the setting from the connected snap's endpoint is also possible by explicitly requesting that via the --plug and --slot command line options: $ snapctl get :myplug --slot usb-vendor This requests the "usb-vendor" setting from the slot that is connected to "myplug".

The interface command shows details of snap interfaces. If no interface name is provided, a list of interface names with at least one connection is shown, or a list of all interfaces if --all is provided.

The known command shows known assertions of the provided type. If header=value pairs are provided after the assertion type, the assertions shown must also have the specified headers matching the provided values.

The managed command will print true or false informing whether snapd has registered users.

The stop command stops the given services of the snap. If executed from the "configure" hook, the services will be stopped after the hook finishes.

The stop command stops, and optionally disables, the given services.

The switch command switches the given snap to a different channel without doing a refresh.

The version command displays the versions of the running client, server, and operating system.

%q switched to the %q channel

%s %s mounted from %s

%s (delta)

%s (try with sudo)

%s already installed

%s disabled

%s enabled

%s not installed

%s removed

%s reverted to %s

%s%s %s installed

%s%s %s refreshed

-r can only be used with --hook

<alias-or-snap>

<alias>

<assertion file>

<assertion type>

<change-id>

<conf value>

<email>

<filename>

<header filter>

<key-name>

<key>

<model-assertion>

<query>

<service>

<snap>:<slot or plug>

A service specification, which can be just a snap name (for all services in the snap), or <snap>.<app> for a single service.

Abort a pending change

Added