Cryptic error and unreliable daemon on linux after update to 0.10.2

[NerdyKyogre]

As of the latest version on my ubuntu 18.04.3 machine, starting IPFS Desktop at login results in a gray icon with the status "IPFS has errored." The daemon has failed to start, which may be related. As soon as I manually run ipfs daemon from a terminal, IPFS desktop seems to work happily. However, the gray icon and error message persist, and restarting IPFS Desktop has no effect. I should mention that I am running the deepin desktop environment and have installed IPFS Desktop as a snap.

[bertrandfalguiere]

Idem for Ubuntu 19.10, installed from sources.

[hacdias]

This is really weird because we did not update/change any dependencies or code related to the daemon logic. Looking at the changelog, I see I made a change I shouldn't have https://github.com/ipfs-shipyard/ipfs-desktop/compare/v0.10.1...v0.10.2#diff-bc78997f8a1c5c7e9e703382e4341c96R150: where is on it should be off. However, none of those changes should make the daemon fail to start.

Can I ask you to check the logs, please? I'm pretty sure that if there was an error, it must've been logged. Please check the last section of the README to know where to find the logs on each OS! :)

[bertrandfalguiere]

This issue might be older than that, unfortunately. I remember having a similar problem months ago, but that was before I understood IPFS well enough. I haven't used it in the interim, so I wouldn't know how it was since.
The issue of @NerdyKyogre reminded me of it.

I can check on older versions, but I don't know how to install versions from sources.

I'll check the logs in the next(ish) days.

[NerdyKyogre]

Sorry for late reply, spam filter decided this was spam.

In the logs, the error that seems to be causing this issue is the following:

2020-01-06T16:38:15.284Z error: [ipfsd] start daemon Error: Error: mkdir /home/colef/snap/ipfs-desktop/5/.ipfs: no such file or directory

Note that ~/snap/ipfs-desktop/5 does not exist on my system at all. This looks like some weirdness with how snaps work that I don't fully understand.

This is spammed every time IPFS desktop tried to start up and the daemon failed. I'm currently getting around this by starting the daemon and desktop separately (I have IPFS cli installed as well) with XDG autostart, which functions, but still shows "IPFS has errored."

There's also this from the updater, but I don't think that's related:

2020-01-06T16:38:08.861Z error: [updater] Error: ENOENT: no such file or directory, open '/snap/ipfs-desktop/7/resources/app-update.yml'

[lidel]

@NerdyKyogre are you able to set IPFS_PATH envronment variable to point at /home/colef/.ipfs when ipfs-destop starts?

[NerdyKyogre]

How would I go about that? The export command in terminal set it momentarily, but that didn't hold when I logged out and back in.

[lidel]

Try defining persistent environment variable at the end of ~/.profile (create it if it does not exists):

export IPFS_PATH=/home/colef/.ipfs

Then reboot (to ensure its applied) and see if it helped.

[hacdias]

Closing this due to inactivity. Please let us know if it happens again. We're releasing a new version soon too.