Translations by Anthony Harrington

snap package %q is being refreshed, please wait

please wait...

snap package cannot be used now: %s

%q snap has been refreshed

WARNING: pressing ctrl-c will abort the running change.

Now available to launch

Close the app to update now

The install command installs the named snaps on the system. To install multiple instances of the same snap, append an underscore and a unique identifier (for each instance) to a snap's name. With no further options, the snaps are installed tracking the stable channel, with strict security confinement. All available channels of a snap are listed in its 'snap info' output. When --revision is used, a later refresh will typically undo the revision override, taking the snap back to the current revision of the channel it's tracking. Use --name to set the instance name when installing from snap file.

The reboot command reboots the system into a particular mode of the selected recovery system. When called without a system label and without a mode it will just trigger a regular reboot. When called without a system label but with a mode it will use the current system to enter the given mode. Note that "recover" and "run" modes are only available for the current system.

Name Version Rev Publisher%s Notes

The services command lists information about the services specified, or about the services in all currently installed snaps.

The login command authenticates the user to snapd and the snap store, and saves credentials into the ~/.snap/auth.json file. Further communication with snapd will then be made using those credentials. It's not necessary to log in to interact with snapd. Doing so, however, enables purchasing of snaps using 'snap buy', as well as some some developer-oriented features as detailed in the help for the find, install and refresh commands. An account can be set up at https://login.ubuntu.com

The aliases command lists all aliases available in the system and their status. $ snap aliases <snap> Lists only the aliases defined by the specified snap. An alias noted as undefined means it was explicitly enabled or disabled but is not defined in the current revision of the snap, possibly temporarily (e.g. because of a revert). This can cleared with 'snap alias --reset'.

Run the command with gdb

Refresh to the given revision, to which you must have developer access

cannot %s without a context

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

Stopped.

Started.

Restarted.

The get command prints configuration and interface connection settings.

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".

Changes configuration options

Install the given revision of a snap, to which you must have developer access

Install %q snap from file

Install %q snap from file %q

Download the given revision of a snap, to which you must have developer access

Export a snapshot to the given filename.

If the first argument passed into unset is an aspect identifier matching the format <account-id>/<bundle>/<aspect>, unset will use the aspects configuration API. In this case, the command removes the data stored in the provided dot-separated aspect paths.

Provide a search term for more specific results.

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

The ack command tries to add an assertion to the system assertion database. The assertion may also be a newer revision of a pre-existing assertion that it will replace. To succeed the assertion must be valid, its signature verified with a known public key and the assertion consistent with and its prerequisite in the database.

The advise-snap command searches for and suggests the installation of snaps. If --command is given, it suggests snaps that provide the given command. Otherwise it suggests snaps with the given name.

The alias command aliases the given snap application to the given alias. Once this manual alias is setup the respective application command can be invoked just using the alias.

The auto-import command searches available mounted devices looking for assertions that are signed by trusted authorities, and potentially performs system changes based on them. If one or more device paths are provided via --mount, these are temporarily mounted to be inspected as well. Even in that case the command will still consider all available mounted devices for inspection. Assertions to be imported must be made available in the auto-import.assert file in the root of the filesystem.

The buy command buys a snap from the store.

The changes command displays a summary of system changes performed recently.

The confinement command will print the confinement mode (strict, partial or none) the system operates in.

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 console-conf-start command starts synchronization with console-conf This command is used by console-conf when it starts up. It delays refreshes if there are none currently ongoing, and exits with a specific error code if there are ongoing refreshes which console-conf should wait for before prompting the user to begin configuring the device.

The create-key command creates a cryptographic key pair that can be used for signing assertions.

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 delete-key command deletes the local cryptographic key pair with the given name.

The disable command disables a snap. The binaries and services of the snap will no longer be available, but all the data is still available and the snap can easily be enabled again.

The download command downloads the given snap and its supporting assertions to the current directory with .snap and .assert file extensions, respectively.

The enable command enables a snap that was previously disabled.

The export-key command exports a public key assertion body that may be imported by other systems.

The find command queries the store for available packages. With the --private flag, which requires the user to be logged-in to the store (see 'snap help login'), it instead searches for private snaps that the user has developer access to, either directly or through the store's collaboration feature. A green check mark (given color and unicode support) after a publisher name indicates that the publisher has been verified.