IOError package:gi-gio

Error codes returned by GIO functions. Note that this domain may be extended in future GLib releases. In general, new error codes either only apply to new APIs, or else replace IOErrorEnumFailed in cases that were not explicitly distinguished before. You should therefore avoid writing code like

C code

if (g_error_matches (error, G_IO_ERROR, G_IO_ERROR_FAILED))
{
// Assume that this is EPRINTERONFIRE
...
}
but should instead treat all unrecognized error codes the same as IOErrorEnumFailed. See also PollableReturn for a cheaper way of returning IOErrorEnumWouldBlock to callers without allocating a GError.
The requested address is already in use. Since 2.22
File is already mounted.
Broken pipe. Since 2.36
File is busy.
Operation was cancelled. See Cancellable.
Backup couldn't be created.
File was closed.
Connection closed by peer. Note that this is the same code as IOErrorEnumBrokenPipe; before 2.44 some "connection closed" errors returned IOErrorEnumBrokenPipe, but others returned IOErrorEnumFailed. Now they should all return the same value, which has this more logical name. Since 2.44.
Connection refused. Since 2.26
A remote object generated an error that doesn't correspond to a locally registered GError error domain. Use dbusErrorGetRemoteError to extract the D-Bus error name and dbusErrorStripRemoteError to fix up the message so it matches what was received on the wire. Since 2.26.
Destination address unset. Since 2.80
File already exists.
Generic error condition for when an operation fails and no more specific IOErrorEnum value is defined.
Operation failed and a helper program has already interacted with the user. Do not display any error dialog.
Filename is too many characters.
Host couldn't be found (remote operations).
Host unreachable. Since 2.26
Invalid argument.
The input data was invalid. Since 2.24
Filename is invalid or contains invalid characters.
File is a directory.
Message too large. Since 2.48.
Network unreachable. Since 2.26
No space left on drive.