ipfs/ipfs-desktop

AUR: Error: Failed to load image from path

Open

#1,987 opened on Feb 21, 2022

View on GitHub
 (11 comments) (0 reactions) (0 assignees)JavaScript (912 forks)batch import
P2area/linuxeffort/hoursexp/experthelp wantedkind/bugneed/community-input

Repository metrics

Stars
 (5,632 stars)
PR merge metrics
 (Avg merge 8d 12h) (6 merged PRs in 30d)

Description

Please describe what you were doing when this error happened.

after updating ipfs from AUR, I right clicked the icon in the taskbar and selected "quit", and it appeared the error

Specifications

  • OS: linux
  • IPFS Desktop Version: 0.18.1
  • Electron Version: 13.6.3
  • Chrome Version: 91.0.4472.164

Error

Error: Failed to load image from path '/opt/IPFS Desktop/resources/app.asar/assets/icons/tray/off-big.png'
    at updateMenu (/opt/IPFS Desktop/resources/app.asar/src/tray.js:341:12)
    at IpcMainImpl.<anonymous> (/opt/IPFS Desktop/resources/app.asar/src/tray.js:360:5)
    at IpcMainImpl.emit (events.js:327:22)
    at updateStatus (/opt/IPFS Desktop/resources/app.asar/src/daemon/index.js:17:13)
    at stopIpfs (/opt/IPFS Desktop/resources/app.asar/src/daemon/index.js:79:5)
    at App.<anonymous> (/opt/IPFS Desktop/resources/app.asar/src/daemon/index.js:113:22)
    at App.emit (events.js:327:22)
    at click (/opt/IPFS Desktop/resources/app.asar/src/tray.js:236:26)
    at MenuItem.click (electron/js2c/browser_init.js:73:1742)
    at Object.a._executeCommand (electron/js2c/browser_init.js:81:2492)

Contributor guide

Research direction
Investigate why the tray icon image path '/opt/IPFS Desktop/resources/app.asar/assets/icons/tray/off big.png' fails to load after update. Check if the icon file exists in the app.asar or if the path is incorrect in the tray.js source code. Verify the asset packaging in the build script.
Tech stack
javascriptnodejselectron
Domain
desktop
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitNode.jsElectron basics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60