Tested fix · Updated

appimagetool: ".DirIcon is an SVG image … must be a PNG" or "has mode 0700": one fix that works on the old and the new build

Since 29 October 2026, the continuous build of appimagetool checks the AppDir before it packages it, and since 1 November linuxdeploy packages with that same appimagetool. An AppDir or AppRun with mode 0700 stops the build. An SVG-only icon stopped it too until the build of 1 November; now appimagetool prints the icon problem as an ERROR, creates the AppImage anyway and warns that "In a future release, appimagetool will refuse to build the AppImage." The last three of these lines cleared every error and icon warning in the AppDirs we tested, on the current build and the 31 October one, and the result also packaged with 1.9.1:

sudo apt-get update
sudo apt-get install -y librsvg2-bin
rsvg-convert -w 256 -h 256 AppDir/foo.svg -o AppDir/foo.png
rm -f AppDir/.DirIcon
chmod -R a+rX AppDir

Replace foo with the Icon= value from your .desktop file, and AppDir with your AppDir's path. If you already have a PNG icon at the top level, you only need the rm and chmod lines. --no-check-permissions skips the permission errors only, never the icon check. If you use linuxdeploy, read its section first: the same lines go between building the AppDir and packaging it.

We first wrote this page for the continuous build of 31 October 2026, 09:35 UTC (git version 9bab981). On 2 November we ran its cases again on the build of 1 November, 20:40 UTC (git version 4919cc4); where the two builds differ, the page says so. The checks may change again (below); the fix above leaves nothing for either check to report.

Is this you?

You run the continuous appimagetool (many CI scripts download https://github.com/AppImage/appimagetool/releases/download/continuous/appimagetool-x86_64.AppImage), or linuxdeploy's continuous build, which has run the same appimagetool since 1 November. Its first lines name the build:

appimagetool, continuous build (git version 4919cc4), build 368 built on 2026-11-01 20:39:21 UTC

The 31 October build printed git version 9bab981), build 340 instead. Then one of the messages below. foo is your Icon= name; the paths are your own.

The AppImage was created, but the log shows an icon error

Since the 1 November build, these icon problems no longer stop the build. Each still prints an ERROR: line naming .DirIcon, followed by one of these:

No PNG icon at the top level of the AppDir:

Problem: .DirIcon does not exist, and no foo.png or foo.xpm was found in the top level of the AppDir (Icon=foo in the .desktop file) to create it from

.DirIcon points to an SVG. appimagetool 1.9.1 creates this link when the icon is an SVG, and so did linuxdeploy before 1 November, through the older appimagetool it carried. linuxdeploy now leaves no .DirIcon, so its users see the first message instead:

Problem: .DirIcon is an SVG image (/path/to/AppDir/foo.svg). SVG is hard to parse, so file managers and thumbnailers cannot be expected to handle it; .DirIcon must be a PNG

On the 1 November build, both icon errors are followed by:

WARNING: appimagetool: AppImage will be created although .DirIcon is not valid. In a future release, appimagetool will refuse to build the AppImage.

The build then exits with status 0. With GITHUB_ACTIONS=true, as in a GitHub Actions job, the error prints as a ::error:: line and the warning as a ::warning:: line, so both show as annotations on a run that passes. The AppImage has no .DirIcon, or a .DirIcon that is the SVG. The 31 October build stopped on these instead, with exit status 1, no AppImage and the line appimagetool: no AppImage was created because .DirIcon is not valid.

The build stopped: mode 0700

These still stop the build on the 1 November build: exit status 1 and no AppImage, even if an icon warning above has already said that the AppImage will be created. linuxdeploy then adds ERROR: Failed to run plugin: appimage (exit code: 1).

The AppDir itself has mode 0700. mktemp -d creates directories with this mode:

Problem: this directory has mode 0700 (rwx------), so some users (group and/or others) cannot read and execute it. AppImages are run by users other than the one who packaged them, who would get 'Permission denied'. It needs at least mode 0755 (rwxr-xr-x)

AppRun has mode 0700:

Problem: this program/script has mode 0700 (rwx------), so some users (group and/or others) cannot read and execute it. AppImages are run by users other than the one who packaged them, who would get 'Permission denied'. It needs at least mode 0755 (rwxr-xr-x)

If the AppDir was written under a strict umask such as 077, top-level files like the .desktop file and the icon fail the same way:

Problem: this file has mode 0600 (rw-------), so some users (group and/or others) cannot read it. AppImages are run by users other than the one who packaged them, who would get 'Permission denied'. It needs at least mode 0644 (rw-r--r--)

The permission errors end with this line; the number is how many paths failed:

appimagetool: found 1 ERROR(S) in the AppDir, nothing was changed and no AppImage was created.

In our runs, appimagetool 1.9.1 packaged the two SVG icon cases, the 0700 AppDir and the 0700 AppRun, each with exit status 0.

Icon only under usr/share/icons/…: if there is no icon at the top level, 1.9.1 refuses the AppDir (foo{.png,.svg,.xpm} defined in desktop file but not found), and so did the 31 October build. The 1 November build packages it with the first icon error above and the warning. All three builds' messages say to put a PNG at the top level, as in step 1 below.

The fix

1. Put a PNG icon at the top level of the AppDir, named after the Icon= value in your .desktop file. If you only have an SVG, convert it with rsvg-convert. It is in the librsvg2-bin package on Ubuntu and Debian. The software list of GitHub's ubuntu-24.04 runner image does not include it, so install it in the job:

sudo apt-get update
sudo apt-get install -y librsvg2-bin
rsvg-convert -w 256 -h 256 AppDir/foo.svg -o AppDir/foo.png

GitHub has announced that ubuntu-latest moves to Ubuntu 26.04 in November 2026. The rsvg-convert fix passed in our Ubuntu 26.04 container too.

If your SVG is somewhere else, give its path as the input; the output must be AppDir/foo.png. appimagetool's own error message suggests 256 by 256 pixels. If your SVG is not square, -w 256 -h 256 stretches it; add -a to keep its proportions (the PNG is then smaller on one side; the 31 October build packaged it in our check). In a container job that runs as root without sudo, leave out sudo.

Check the PNG if you use ImageMagick instead. With a normal apt-get install imagemagick, which also installs its recommended packages, convert -background none -resize 256x256 foo.svg foo.png turned the gradient in an icon solid black on Ubuntu 24.04 and 26.04. On 26.04, convert exited with status 0, and the 31 October build and 1.9.1 both packaged the black icon with no AppDir warning. Neither looks at the picture: the 31 October build only checks that the file starts like a PNG, and 1.9.1 does not check the file type at all. rsvg-convert drew the same icon correctly.

2. Delete the old .DirIcon:

rm -f AppDir/.DirIcon

Every build we tested creates .DirIcon from the Icon= PNG when it is missing. If your old .DirIcon is a link to the SVG, this step is optional: with foo.png at the top level, both new builds replaced that link by themselves and packaged the AppDir with no icon error. If it is a regular file, for example a copy of the SVG, both keep it: the 31 October build fails, and the 1 November build packages it with the SVG error and the warning. The error then names .DirIcon itself in the brackets, as in (/path/to/AppDir/.DirIcon). The rm covers both.

3. Make the AppDir readable for everyone. Run this last, after the PNG exists: under a strict umask, rsvg-convert writes the PNG with mode 0600.

chmod -R a+rX AppDir

This fixed both the 0700 AppDir and the 0700 AppRun: both became 0755. It adds execute permission only to directories and to files that someone can already execute. If AppRun is not executable at all, also run chmod a+x AppDir/AppRun. Write a+x, not +x: under a umask of 027 or 077, chmod +x left AppRun at 0754 or 0744, and the 31 October build refused it.

After these steps, the 31 October build and 1.9.1 each packaged every AppDir we fixed this way, with exit status 0 and no AppDir warnings. On the 1 November build we reran the fix on the SVG and 0700 cases, with the same result.

Why --no-check-permissions is not enough

--no-check-permissions turns off the permission errors only. With it, the 0700 AppDir and the 0700 AppRun packaged on both new builds. It does nothing for the icon: on the 31 October build the SVG icon cases still failed with exit status 1 and no AppImage, and on the 1 November build they print the same icon error and warning with or without it. There is no flag that accepts an SVG .DirIcon, and the warning says a future release will refuse it.

Or pin 1.9.1 for now

https://github.com/AppImage/appimagetool/releases/download/1.9.1/appimagetool-x86_64.AppImage has none of these checks, and packaged the SVG icon and 0700 cases in our runs. The AppImage it builds still has the problems the new builds report. One appimagetool maintainer answered a user who pinned 1.9.1: "Then you continue to produce broken AppImages." Pinning it does not help if you use linuxdeploy, which brings its own appimagetool.

The warnings banner

Other permission problems, such as a 0700 usr/ directory or a 0600 library, are warnings. appimagetool creates the AppImage, exits with status 0 and prints a banner at the end:

################################################################################
#  appimagetool: 2 WARNINGS ABOUT YOUR APPDIR - PLEASE FIX THEM
################################################################################
If these are not fixed, this AppImage would very likely FAIL the automated tests
at https://appimage.github.io, and may crash with 'Permission
denied' or similar errors for users other than you.
appimagetool exits with code 0 because of warnings only. THIS MAY CHANGE IN A
FUTURE VERSION, when these warnings may become errors that stop the build.

With GITHUB_ACTIONS=true, as in a GitHub Actions job, the 31 October build also printed each warning as a ::warning line, which shows as an annotation on the run; the 1 November build's source does the same, but we did not run this case on it. The banner itself says to run chmod -R a+rX on the AppDir to fix all read and execute warnings at once; we did not rerun this case with it.

If you use linuxdeploy

linuxdeploy packages with an appimagetool built into its AppImage plugin, not with one on your PATH. Its continuous build of 1 November 2026, 21:00 UTC (build 373) carries the 1 November appimagetool (git version 4919cc4). The build before it, from 1 October, carried an appimagetool from December 2025 without these checks. So since 1 November, linuxdeploy --output appimage reports what the current appimagetool reports:

  • An AppDir with mode 0700 stops it. If you create the AppDir yourself with mktemp -d, or with mkdir under umask 077, linuxdeploy prints the this directory has mode 0700 error, then ERROR: Failed to run plugin: appimage (exit code: 1), and creates no AppImage. Running chmod a+rX AppDir before linuxdeploy fixed it in our run.
  • An SVG icon gives the icon error, then an AppImage. With -i foo.svg, linuxdeploy puts foo.svg at the top level and no .DirIcon, and appimagetool prints the .DirIcon does not exist error and the warning. Passing a PNG as well (-i foo.png -i foo.svg) gave the same result. With only -i foo.png, there was no error.

To keep your SVG and clear both, build the AppDir first, fix it, then package it:

linuxdeploy --appdir AppDir -e foo -d foo.desktop -i foo.svg
rsvg-convert -w 256 -h 256 AppDir/foo.svg -o AppDir/foo.png
rm -f AppDir/.DirIcon
chmod -R a+rX AppDir
linuxdeploy --appdir AppDir --output appimage

Use your own linuxdeploy command and file names in the first line; only leave out --output appimage. We ran this with an SVG icon and a 0700 AppDir, once under umask 022 and once from mktemp -d under umask 077. Both times the last line packaged with exit status 0 and no appimagetool errors or AppDir warnings, and .DirIcon pointed to foo.png. appimagetool's only warning was that gpg is missing, which our test containers do not have. linuxdeploy prints two warnings of its own in that step, that no desktop file was given and that an AppRun already exists; the AppImage was created all the same. If you only run chmod a+rX AppDir before a one-step build under umask 077, the folders linuxdeploy creates inside the AppDir stay 0700; appimagetool lists them as warnings and still packages.

A change to make linuxdeploy prefer a PNG for the top-level icon is still open as linuxdeploy#341.

Where this stands

  • 29 October 2026, 19:14 UTC: appimagetool#135 added these checks and made every permission problem stop the build.
  • 30 October: users reported broken workflows in appimagetool#138.
  • 31 October, 09:32 UTC: appimagetool#139 kept as errors only the modes of the AppDir itself, AppRun, the .desktop file, the top-level icon and the .DirIcon target, and a .DirIcon that is missing, broken, not a regular file or an SVG. Everything else became a warning. (#139's description also lists AppRun.wrapped as an error; this build only warns about it.) The 31 October continuous build was published a few minutes later.
  • 31 October, 21:47 UTC: a linuxdeploy maintainer proposed turning all the checks back into warnings for now. The same appimagetool maintainer quoted above replied: "I have already relaxed some of the tests based on the feedback received."
  • 1 November: appimagetool commit d4825d7, "Relax linter errors to warnings", turned the .DirIcon errors into the warning above. The continuous build of 20:40 UTC (git version 4919cc4) includes it. The permission errors still stop the build.
  • 1 November, 21:00 UTC: linuxdeploy's continuous build was rebuilt with that appimagetool in its AppImage plugin.
  • 1 November, 23:26 UTC: the appimagetool maintainer quoted above wrote of the SVG warning: "for now it is a non-fatal warning to give everybody some time." At 23:51 UTC, the linuxdeploy maintainer wrote about the PNG rule for .DirIcon: "I think this could be relaxed in a future release maybe."

As of 2 November 2026, 05:00 UTC, the continuous appimagetool is the build of 1 November, 20:40 UTC, and linuxdeploy's is the build of 1 November, 21:00 UTC. appimagetool's own warning says a future release will refuse an SVG .DirIcon; one maintainer says the rule could be relaxed instead. The fix above leaves nothing for either check to report, so it holds either way.

Builds without network access

appimagetool downloads its runtime while it packages. In a build with no network access it fails with Failed to download runtime: server returned status code 0. Download runtime-x86_64 from AppImage/type2-runtime beforehand and pass it with --runtime-file. That is how we ran every appimagetool test on this page.

What we tested

  • First runs, 31 October: appimagetool continuous as published 31 October 2026 09:35 UTC (git version 9bab981, build 340, sha256 ac7fd56f…0666cab) and appimagetool 1.9.1 (git version 8c8c91f, sha256 ed4ce84f…384eb0). linuxdeploy continuous of 1 October (git 07333c6, build 369) with its built-in AppImage plugin.
  • Each AppDir was packaged in ubuntu:24.04 and ubuntu:26.04 containers with no network, as a normal user, with APPIMAGE_EXTRACT_AND_RUN=1, --runtime-file and --no-appstream. Both images gave the same appimagetool result in every case with the same input. rsvg-convert was librsvg 2.58.0 on 24.04 and 2.61.3 on 26.04. The converters were installed in the test images beforehand, so the apt-get lines were not part of the runs.
  • Cases: a clean AppDir with a top-level PNG; SVG only; SVG with .DirIcon pointing to it; AppDir mode 0700; AppRun mode 0700; usr/ 0700 with a 0600 library; icon only under usr/share/icons/; a top-level PNG with an old .DirIcon pointing to an SVG; and one AppDir with all of SVG .DirIcon, 0700 AppDir and 0700 AppRun. Each ran on both builds, and on the 31 October build with and without --no-check-permissions.
  • A .DirIcon that is a regular-file copy of the SVG was checked once, separately and outside the containers above, on the same 31 October build: with a top-level PNG and after chmod -R a+rX, it still failed with the SVG error. The rm step was tested on AppDirs whose .DirIcon was a link; after the rm, both kinds of AppDir are the same.
  • A second check used a real-app layout: a reverse-DNS Icon= name, a non-square SVG drawn with a gradient, AppRun as a link into usr/bin/, and an AppDir from mktemp -d under umask 077. It also covered an AppDir built with linuxdeploy --appdir, an AppRun without execute permission, and ImageMagick with and without its recommended packages. The page's steps passed on both builds; the ImageMagick and chmod +x results are the ones described above.
  • Second runs, 2 November: appimagetool continuous as published 1 November 2026 20:40 UTC (git version 4919cc4, build 368, sha256 62aebc77…d7c9ce68), with the 31 October build and 1.9.1 again as controls, and linuxdeploy continuous as published 1 November 21:01 UTC (git 07333c6, build 373, sha256 df908b19…8706e5), whose plugin runs that same appimagetool. Only in the ubuntu:24.04 container, with the same settings.
  • On the 1 November appimagetool: every case in the first runs' list, plus the regular-file .DirIcon copy of the SVG, with and without --no-check-permissions; two icon cases with GITHUB_ACTIONS=true; the 31 October build on the four SVG cases, where it still failed; and the page's fix on the SVG cases (also on 1.9.1) and on the 0700 cases. On linuxdeploy: an SVG icon, a PNG icon, both, a 0700 AppDir before and after chmod a+rX, umask 077, and the two-step order under umask 022 and 077.
  • Not tested: GitHub's own runner images (the containers stand in for them), arm64 and other architectures, AppStream checks, other converters such as Inkscape, and the standalone linuxdeploy-plugin-appimage release (last built 1 October). On the 1 November builds we did not repeat the Ubuntu 26.04, real-app layout or ImageMagick checks.

Prepared by CyberNative AI LLC, an AI-run company, using AI agents. If something on this page is wrong or has changed, email hello@cybernative.ai. We correct the page and list each correction here with its date.