You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Bug]: Lack of icons for AppImage, Flatpak, on GNOME #1652
Review date: 30 October 2026. Disposition: the implementation is merged and included in a prerelease; the customer's native GNOME outcome is not yet verified.
PR #1717 merged as cf4f2f28207f97422fed9aa59d498c923b9e57ea. Its change is explicitly included in v1.25.0-beta.7 and remains in beta.8. The latest stable release is still v1.24.0, the version reported here. Therefore, an unchanged v1.24.0 installation should not be expected to contain this fix.
Direct AppImage execution did not install a permanent launcher.
A first-launch offer and Settings actions add/update/remove a user-local launcher and icon. The launcher targets the permanent AppImage file. Whole-file and icon ownership checks preserve foreign or edited integrations.
DEB/RPM retain the packaged theme name devsy-desktop; Flatpak and the owned AppImage integration use sh.devsy.app. These are deliberate mappings. Do not rename every icon to the same value without checking its desktop entry.
Existing structural evidence covers actual DEB, RPM, AppImage and Flatpak contents, including Flatpak import/export: package verification ledger. That ledger is scoped to the package source it names, not all subsequent release bytes. The precision correction clarifies that the AppImage extraction runtime ran, while the Devsy application did not.
The PR's recorded native GNOME attempts did not establish a visible-window pass. Its source and automated reviews are evidence for the implementation, not a substitute for the graphical matrix below.
Reuse hack/release_artifacts verify-linux-desktop and the existing release workflow's extraction/import procedure for those actual bytes. Check the expected desktop filename, StartupWMClass, Icon value, decoded 32px/128px theme PNGs and bundled runtime icon.
Check the application version inside the packaged ASAR and the actual exported Flatpak desktop/icon files. A release-note entry alone does not prove a specific local download is the matching artifact.
Keep packaging checks separate from GUI results in the issue evidence. A package that extracts successfully has not yet demonstrated launch/grouping behavior.
No new verifier framework is needed. If a published artifact fails an existing invariant, fix the producing location: desktop/electron-builder.yml for Electron/Linux content, desktop/flatpak/sh.devsy.app.yml/Devsy.desktop for Flatpak exports, or .github/workflows/release.yml for packaging/versioning. Add the failing artifact case to the existing verifier tests before changing production code.
T2. Validate native GNOME behavior with the customer topology
Use Fedora 44 / GNOME 50 / AMD64 where available, matching the report. Record session type and Electron backend for each run. A different GNOME version is useful supplemental evidence but does not establish this exact environment.
Case
Concrete procedure
Passing result
Flatpak, native Wayland
Install the selected bundle in an isolated test profile; launch from Applications; open, close, reopen and pin it.
Correct icon in Applications, overview, running dock and pin; one application grouping; reopening returns the expected window.
Integrated AppImage, native Wayland
Put the AppImage at a permanent path; launch directly; accept Add to applications; quit and relaunch from the installed menu entry.
Launcher points at the permanent file, matching icon remains after the temporary mount is gone, and the running app groups with the same entry.
First-launch decline
Decline integration; relaunch; then use Settings > Applications menu > Add.
Offer follows the documented once-per-profile behavior; Settings remains the recovery path.
Existing integration
Preinstall a Flatpak/system/user/third-party launcher, then launch the AppImage.
Existing integration is detected; no duplicate or overwritten launcher/URI handler.
AppImage move and removal
Move the AppImage, launch the new path, inspect/update the owned entry; exercise Settings Remove and Add again.
Owned entry follows the new absolute path; removal affects only files the integration owns; relaunch remains usable.
Edited/shared files
Edit an owned launcher or replace/share its icon before Update/Remove.
Existing ownership checks report/preserve the conflict; no user/foreign file is deleted or overwritten.
X11/XWayland
Launch the installed AppImage and Flatpak routes under the actual tested backend.
Runtime icon and WM_CLASS/application grouping resolve correctly. Record whether the run was X11, XWayland or native Wayland.
DEB/RPM
Install and launch each package in its suitable native environment.
Installed menu entry and running-window icon match the package mapping, with no AppImage integration prompt.
Upgrade
Start with v1.24.0 and an old pinned entry; upgrade to the fixed artifact.
New launcher works; documented unpin/repin recovery addresses the old pin without deleting foreign entries.
Capture screenshots of the application menu, running overview/dock and reopened state, plus the actual desktop entry identity. Merely finding a process, mounting an AppImage, starting GNOME Shell or running under Xvfb does not satisfy those observations.
A directly executed, unintegrated AppImage is a documented boundary: without a matching installed entry, GNOME Wayland may still show a generic/ungrouped icon. The product fix supplies an integration path; it cannot require the application to overwrite an existing installation automatically. Preserve this behavior and explain it in the test result.
T3. Use failures to select a narrow correction
If T2 fails, record the first incorrect identity/path and use this mapping:
Correct package contents but wrong launch identity/grouping
desktop/package.json, packaged desktop entry and actual Electron backend; inspect measured WM_CLASS/app_id before selecting a fix.
Flatpak menu icon missing
Actual Flatpak exports, desktop/flatpak/sh.devsy.app.yml and Devsy.desktop; preserve the app-id/theme-name mapping.
AppImage integration fails or uses a mount path
linux-desktop-integration.ts and its existing tests; reproduce with actual APPIMAGE/XDG paths and keep ownership checks.
Settings/prompt state differs from filesystem
Existing integration IPC, SettingsPage.svelte, AppImageIntegrationPrompt.svelte and their tests; refresh state after the completed operation and reject stale UI assumptions.
Old pin only
Follow the documented upgrade recovery first; do not introduce destructive launcher cleanup for stale shell state.
This is a diagnostic routing table, not a request to modify all of these files. No additional production defect is established by the current evidence.
T4. Deliver and close
Link the completed graphical matrix and the exact artifact/commit tested here.
Record any supported-case failure as a narrowly scoped follow-up under this issue, with the observed boundary, regression test and proposed file changes. New fixes use signed commits and Draft PRs.
Confirm the original AppImage and Flatpak customer flows show the expected icon. Close only when the supported cases have evidence, with the direct unintegrated AppImage boundary documented.
Answer to “is it fixed?”: the code fix is delivered in beta.7 and newer; native customer confirmation and stable-channel delivery remain. This review did not run GNOME or install release packages.
Activity
fix(desktop): complete ownership-safe AppImage desktop integration
fix(desktop): complete ownership-safe AppImage desktop integration
fix(desktop): preserve customized AppImage launchers and icons
skevetter commentedon Oct 31, 2026
Fix status and remaining acceptance plan
Review date: 30 October 2026. Disposition: the implementation is merged and included in a prerelease; the customer's native GNOME outcome is not yet verified.
PR #1717 merged as cf4f2f28207f97422fed9aa59d498c923b9e57ea. Its change is explicitly included in v1.25.0-beta.7 and remains in beta.8. The latest stable release is still v1.24.0, the version reported here. Therefore, an unchanged v1.24.0 installation should not be expected to contain this fix.
Reviewed main baseline: 9bc12ee041ca854c6f81de95fd8c6e49d7cc028c. Keep this issue as the acceptance tracker. Do not create another implementation ticket duplicating #1717.
1. Verified code changes already present
desktopName: sh.devsy.app.desktop; Linux packaging synchronizes the desktop filename withappId: sh.devsy.app.app-icon.png;linuxWindowIconsupplies its packaged path when creating the window.hicolor/.../apps/sh.devsy.app.png; the desktop entry uses the same theme name.DEB/RPM retain the packaged theme name
devsy-desktop; Flatpak and the owned AppImage integration usesh.devsy.app. These are deliberate mappings. Do not rename every icon to the same value without checking its desktop entry.Existing structural evidence covers actual DEB, RPM, AppImage and Flatpak contents, including Flatpak import/export: package verification ledger. That ledger is scoped to the package source it names, not all subsequent release bytes. The precision correction clarifies that the AppImage extraction runtime ran, while the Devsy application did not.
The PR's recorded native GNOME attempts did not establish a visible-window pass. Its source and automated reviews are evidence for the implementation, not a substitute for the graphical matrix below.
2. Remaining work, in execution order
T1. Bind acceptance to the released artifacts
hack/release_artifacts verify-linux-desktopand the existing release workflow's extraction/import procedure for those actual bytes. Check the expected desktop filename, StartupWMClass, Icon value, decoded 32px/128px theme PNGs and bundled runtime icon.No new verifier framework is needed. If a published artifact fails an existing invariant, fix the producing location:
desktop/electron-builder.ymlfor Electron/Linux content,desktop/flatpak/sh.devsy.app.yml/Devsy.desktopfor Flatpak exports, or.github/workflows/release.ymlfor packaging/versioning. Add the failing artifact case to the existing verifier tests before changing production code.T2. Validate native GNOME behavior with the customer topology
Use Fedora 44 / GNOME 50 / AMD64 where available, matching the report. Record session type and Electron backend for each run. A different GNOME version is useful supplemental evidence but does not establish this exact environment.
Capture screenshots of the application menu, running overview/dock and reopened state, plus the actual desktop entry identity. Merely finding a process, mounting an AppImage, starting GNOME Shell or running under Xvfb does not satisfy those observations.
A directly executed, unintegrated AppImage is a documented boundary: without a matching installed entry, GNOME Wayland may still show a generic/ungrouped icon. The product fix supplies an integration path; it cannot require the application to overwrite an existing installation automatically. Preserve this behavior and explain it in the test result.
T3. Use failures to select a narrow correction
If T2 fails, record the first incorrect identity/path and use this mapping:
desktop/electron-builder.yml,linux-desktop-identity.ts,index.ts:createWindow; extendlinux-desktop-identity.test.ts/package verifier coverage.desktop/package.json, packaged desktop entry and actual Electron backend; inspect measured WM_CLASS/app_id before selecting a fix.desktop/flatpak/sh.devsy.app.ymlandDevsy.desktop; preserve the app-id/theme-name mapping.linux-desktop-integration.tsand its existing tests; reproduce with actual APPIMAGE/XDG paths and keep ownership checks.SettingsPage.svelte,AppImageIntegrationPrompt.svelteand their tests; refresh state after the completed operation and reject stale UI assumptions.This is a diagnostic routing table, not a request to modify all of these files. No additional production defect is established by the current evidence.
T4. Deliver and close
The existing installation guidance and Linux icon troubleshooting already describe the new integration and recovery. Update only where actual acceptance finds a mismatch.
Answer to “is it fixed?”: the code fix is delivered in beta.7 and newer; native customer confirmation and stable-channel delivery remain. This review did not run GNOME or install release packages.