### Enumeration

# Gio IOErrorEnum

since: 2.0

#### Declaration

    error-domain Gio.IOErrorEnum

#### Description

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 `G_IO_ERROR_FAILED` in cases that were not explicitly distinguished before. You should therefore avoid writing code like

    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 `G_IO_ERROR_FAILED`.

See also `GPollableReturn` for a cheaper way of returning `G_IO_ERROR_WOULD_BLOCK` to callers without allocating a `GError`.

Available since: 2.0

#### Members

`G_IO_ERROR_FAILED`

  Generic error condition for when an operation fails and no more specific `GIOErrorEnum` value is defined.

  - Value: `0`
  - Nickname: `failed`
  - Available since: 2.0
`G_IO_ERROR_NOT_FOUND`

  File not found.

  - Value: `1`
  - Nickname: `not-found`
  - Available since: 2.0
`G_IO_ERROR_EXISTS`

  File already exists.

  - Value: `2`
  - Nickname: `exists`
  - Available since: 2.0
`G_IO_ERROR_IS_DIRECTORY`

  File is a directory.

  - Value: `3`
  - Nickname: `is-directory`
  - Available since: 2.0
`G_IO_ERROR_NOT_DIRECTORY`

  File is not a directory.

  - Value: `4`
  - Nickname: `not-directory`
  - Available since: 2.0
`G_IO_ERROR_NOT_EMPTY`

  File is a directory that isn’t empty.

  - Value: `5`
  - Nickname: `not-empty`
  - Available since: 2.0
`G_IO_ERROR_NOT_REGULAR_FILE`

  File is not a regular file.

  - Value: `6`
  - Nickname: `not-regular-file`
  - Available since: 2.0
`G_IO_ERROR_NOT_SYMBOLIC_LINK`

  File is not a symbolic link.

  - Value: `7`
  - Nickname: `not-symbolic-link`
  - Available since: 2.0
`G_IO_ERROR_NOT_MOUNTABLE_FILE`

  File cannot be mounted.

  - Value: `8`
  - Nickname: `not-mountable-file`
  - Available since: 2.0
`G_IO_ERROR_FILENAME_TOO_LONG`

  Filename is too many characters.

  - Value: `9`
  - Nickname: `filename-too-long`
  - Available since: 2.0
`G_IO_ERROR_INVALID_FILENAME`

  Filename is invalid or contains invalid characters.

  - Value: `10`
  - Nickname: `invalid-filename`
  - Available since: 2.0
`G_IO_ERROR_TOO_MANY_LINKS`

  File contains too many symbolic links.

  - Value: `11`
  - Nickname: `too-many-links`
  - Available since: 2.0
`G_IO_ERROR_NO_SPACE`

  No space left on drive.

  - Value: `12`
  - Nickname: `no-space`
  - Available since: 2.0
`G_IO_ERROR_INVALID_ARGUMENT`

  Invalid argument.

  - Value: `13`
  - Nickname: `invalid-argument`
  - Available since: 2.0
`G_IO_ERROR_PERMISSION_DENIED`

  Permission denied.

  - Value: `14`
  - Nickname: `permission-denied`
  - Available since: 2.0
`G_IO_ERROR_NOT_SUPPORTED`

  Operation (or one of its parameters) not supported.

  - Value: `15`
  - Nickname: `not-supported`
  - Available since: 2.0
`G_IO_ERROR_NOT_MOUNTED`

  File isn’t mounted.

  - Value: `16`
  - Nickname: `not-mounted`
  - Available since: 2.0
`G_IO_ERROR_ALREADY_MOUNTED`

  File is already mounted.

  - Value: `17`
  - Nickname: `already-mounted`
  - Available since: 2.0
`G_IO_ERROR_CLOSED`

  File was closed.

  - Value: `18`
  - Nickname: `closed`
  - Available since: 2.0
`G_IO_ERROR_CANCELLED`

  Operation was cancelled. See `GCancellable`.

  - Value: `19`
  - Nickname: `cancelled`
  - Available since: 2.0
`G_IO_ERROR_PENDING`

  Operations are still pending.

  - Value: `20`
  - Nickname: `pending`
  - Available since: 2.0
`G_IO_ERROR_READ_ONLY`

  File is read only.

  - Value: `21`
  - Nickname: `read-only`
  - Available since: 2.0
`G_IO_ERROR_CANT_CREATE_BACKUP`

  Backup couldn’t be created.

  - Value: `22`
  - Nickname: `cant-create-backup`
  - Available since: 2.0
`G_IO_ERROR_WRONG_ETAG`

  File’s Entity Tag was incorrect.

  - Value: `23`
  - Nickname: `wrong-etag`
  - Available since: 2.0
`G_IO_ERROR_TIMED_OUT`

  Operation timed out.

  - Value: `24`
  - Nickname: `timed-out`
  - Available since: 2.0
`G_IO_ERROR_WOULD_RECURSE`

  Operation would be recursive.

  - Value: `25`
  - Nickname: `would-recurse`
  - Available since: 2.0
`G_IO_ERROR_BUSY`

  File is busy.

  - Value: `26`
  - Nickname: `busy`
  - Available since: 2.0
`G_IO_ERROR_WOULD_BLOCK`

  Operation would block.

  - Value: `27`
  - Nickname: `would-block`
  - Available since: 2.0
`G_IO_ERROR_HOST_NOT_FOUND`

  Host couldn’t be found (remote operations).

  - Value: `28`
  - Nickname: `host-not-found`
  - Available since: 2.0
`G_IO_ERROR_WOULD_MERGE`

  Operation would merge files.

  - Value: `29`
  - Nickname: `would-merge`
  - Available since: 2.0
`G_IO_ERROR_FAILED_HANDLED`

  Operation failed and a helper program has already interacted with the user. Do not display any error dialog.

  - Value: `30`
  - Nickname: `failed-handled`
  - Available since: 2.0
`G_IO_ERROR_TOO_MANY_OPEN_FILES`

  The current process has too many files open and can’t open any more. Duplicate descriptors do count toward this limit. Since 2.20

  - Value: `31`
  - Nickname: `too-many-open-files`
  - Available since: 2.0
`G_IO_ERROR_NOT_INITIALIZED`

  The object has not been initialized. Since 2.22

  - Value: `32`
  - Nickname: `not-initialized`
  - Available since: 2.0
`G_IO_ERROR_ADDRESS_IN_USE`

  The requested address is already in use. Since 2.22

  - Value: `33`
  - Nickname: `address-in-use`
  - Available since: 2.0
`G_IO_ERROR_PARTIAL_INPUT`

  Need more input to finish operation. Since 2.24

  - Value: `34`
  - Nickname: `partial-input`
  - Available since: 2.0
`G_IO_ERROR_INVALID_DATA`

  The input data was invalid. Since 2.24

  - Value: `35`
  - Nickname: `invalid-data`
  - Available since: 2.0
`G_IO_ERROR_DBUS_ERROR`

  A remote object generated an error that doesn’t correspond to a locally registered `GError` error domain. Use `g_dbus_error_get_remote_error()` to extract the D-Bus error name and `g_dbus_error_strip_remote_error()` to fix up the message so it matches what was received on the wire. Since 2.26.

  - Value: `36`
  - Nickname: `dbus-error`
  - Available since: 2.0
`G_IO_ERROR_HOST_UNREACHABLE`

  Host unreachable. Since 2.26

  - Value: `37`
  - Nickname: `host-unreachable`
  - Available since: 2.0
`G_IO_ERROR_NETWORK_UNREACHABLE`

  Network unreachable. Since 2.26

  - Value: `38`
  - Nickname: `network-unreachable`
  - Available since: 2.0
`G_IO_ERROR_CONNECTION_REFUSED`

  Connection refused. Since 2.26

  - Value: `39`
  - Nickname: `connection-refused`
  - Available since: 2.0
`G_IO_ERROR_PROXY_FAILED`

  Connection to proxy server failed. Since 2.26

  - Value: `40`
  - Nickname: `proxy-failed`
  - Available since: 2.0
`G_IO_ERROR_PROXY_AUTH_FAILED`

  Proxy authentication failed. Since 2.26

  - Value: `41`
  - Nickname: `proxy-auth-failed`
  - Available since: 2.0
`G_IO_ERROR_PROXY_NEED_AUTH`

  Proxy server needs authentication. Since 2.26

  - Value: `42`
  - Nickname: `proxy-need-auth`
  - Available since: 2.0
`G_IO_ERROR_PROXY_NOT_ALLOWED`

  Proxy connection is not allowed by ruleset. Since 2.26

  - Value: `43`
  - Nickname: `proxy-not-allowed`
  - Available since: 2.0
`G_IO_ERROR_BROKEN_PIPE`

  Broken pipe. Since 2.36

  - Value: `44`
  - Nickname: `broken-pipe`
  - Available since: 2.0
`G_IO_ERROR_CONNECTION_CLOSED`

  Connection closed by peer. Note that this is the same code as `G_IO_ERROR_BROKEN_PIPE`; before 2.44 some “connection closed” errors returned `G_IO_ERROR_BROKEN_PIPE`, but others returned `G_IO_ERROR_FAILED`. Now they should all return the same value, which has this more logical name. Since 2.44.

  - Value: `44`
  - Nickname: `connection-closed`
  - Available since: 2.0
`G_IO_ERROR_NOT_CONNECTED`

  Transport endpoint is not connected. Since 2.44

  - Value: `45`
  - Nickname: `not-connected`
  - Available since: 2.0
`G_IO_ERROR_MESSAGE_TOO_LARGE`

  Message too large. Since 2.48.

  - Value: `46`
  - Nickname: `message-too-large`
  - Available since: 2.0
`G_IO_ERROR_NO_SUCH_DEVICE`

  No such device found. Since 2.74

  - Value: `47`
  - Nickname: `no-such-device`
  - Available since: 2.0
`G_IO_ERROR_DESTINATION_UNSET`

  Destination address unset. Since 2.80

  - Value: `48`
  - Nickname: `destination-unset`
  - Available since: 2.0