Closed IngwiePhoenix closed 2 years ago
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:
Finally, remember to use https://discuss.ipfs.io if you just need general support.
@IngwiePhoenix Thanks for bringing this to our attention. Could you also attach the combined.log
file?
It looks like you're on the latest version of IPFS desktop, so that's great. However, it sounds like you're saying that when you start IPFS Desktop, you have to start the ipfs daemon manually, or is it that you need to start the IPFS Desktop application manually?
IPFS Desktop is supposed to enable launch on startup automatically, as you can see at https://github.com/ipfs/ipfs-desktop/blob/e16b1e7374b0d614c4bd2416b7b75cd58f45d85e/src/auto-launch.js#L86. We should be able to see what's happening once we get your combined.log
file.
Is IPFS Desktop listed as a startup app? Could you share a screenshot showing as much? Or you could provide the full terminal output of running either of the below commands:
Windows cmd/batch
wmic startup get caption,command
Powershell
Get-CimInstance Win32_StartupCommand | Select-Object Name, command, Location, User | Format-List
If IPFS Desktop is not listed there, you may need to add it to your list of startup applications manually for now.
you have to start the ipfs daemon manually
Yes - unless I do that, IPFS Desktop stays in the "Errord" state.
Is IPFS Desktop listed as a startup app
You probably mean this?
This is from the task manager.
And, here is the combined.log
:)
combined.log
Thanks for providing the combined.log. It looks like this code is being called multiple times, which means the configuration isn't being saved properly. We will need to investigate this further.
C:/Windows/Users/$user/AppData/Local/Programs/IPFS Desktop/
should contain the binaries (file locations are called out here: https://github.com/ipfs/ipfs-desktop/issues/1656#issuecomment-704979096) @IngwiePhoenix we don't have the bandwidth to investigate this further at this moment but if you can provide further information so it can be looked into when someone has time that would be very helpful.
Oops, seems like we needed more information for this issue, please comment with more details or this issue will be closed in 7 days.
Describe the bug I have had the IPFS Desktop installed for a while, and was wondering how I could make it start IPFS on login. Turns out that this is supposed to be an actual feature. Well, it never worked unless I manually started the daemon. Meaning, that IPFS Desktop on my Windows maschine has thus far never brought up IPFS itself ever.
To Reproduce I honestly wish I knew what led to this bug. All I did was to install it via Chocolatey and whilst installing an update, I selected "Only for myself".
Expected behavior I expected to have an IPFS node running whenever I log into my Windows.
Screenshots None, except the "IPFS has errored" message.
Additional context None that comes to mind.
error.log