Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[gui error report] Error: [ctx] Property tray-menu already exists #2591

Closed
Tracked by #2600
gov360 opened this issue Aug 19, 2023 · 1 comment · Fixed by #2594
Closed
Tracked by #2600

[gui error report] Error: [ctx] Property tray-menu already exists #2591

gov360 opened this issue Aug 19, 2023 · 1 comment · Fixed by #2594
Assignees
Labels
effort/hours Estimated to take one or several hours kind/bug A bug in existing code (including security flaws)

Comments

@gov360
Copy link

gov360 commented Aug 19, 2023

👉️ Please describe what you were doing when this error happened.

Specifications

  • OS: linux 5.10.0-25-amd64
  • IPFS Desktop Version: 0.30.0
  • Electron Version: 19.1.9
  • Chrome Version: 102.0.5005.167

Error

Error: [ctx] Property tray-menu already exists
    at Context.setProp (/tmp/.mount_ipfs-d7gMRej/resources/app.asar/src/context.js:59:13)
    at setupMenu (/tmp/.mount_ipfs-d7gMRej/resources/app.asar/src/tray.js:262:7)
    at process.processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async IpcMainImpl.<anonymous> (/tmp/.mount_ipfs-d7gMRej/resources/app.asar/src/tray.js:399:56)
@gov360 gov360 added kind/bug A bug in existing code (including security flaws) need/triage Needs initial labeling and prioritization labels Aug 19, 2023
@welcome
Copy link

welcome bot commented Aug 19, 2023

Thank you for submitting your first issue to this repository! A maintainer will be here shortly to triage and review.
In the meantime, please double-check that you have provided all the necessary information to make this process easy! Any information that can help save additional round trips is useful! We currently aim to give initial feedback within two business days. If this does not happen, feel free to leave a comment.
Please keep an eye on how this issue will be labeled, as labels give an overview of priorities, assignments and additional actions requested by the maintainers:

  • "Priority" labels will show how urgent this is for the team.
  • "Status" labels will show if this is ready to be worked on, blocked, or in progress.
  • "Need" labels will indicate if additional input or analysis is required.

Finally, remember to use https://discuss.ipfs.io if you just need general support.

@github-project-automation github-project-automation bot moved this to Needs Grooming in IPFS-GUI (PL EngRes) Aug 19, 2023
@whizzzkid whizzzkid self-assigned this Aug 22, 2023
@whizzzkid whizzzkid added effort/hours Estimated to take one or several hours and removed need/triage Needs initial labeling and prioritization labels Aug 22, 2023
@github-project-automation github-project-automation bot moved this from Needs Grooming to Done in IPFS-GUI (PL EngRes) Aug 22, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
effort/hours Estimated to take one or several hours kind/bug A bug in existing code (including security flaws)
Projects
No open projects
Status: Done
Development

Successfully merging a pull request may close this issue.

2 participants