IPFS Desktop Error: cannot acquire lock: can't lock file "C:\\Users\\Алексей\\.ipfs\\repo.lock": has non-zero size about ipfs-desktop HOT 6 CLOSED

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 additiona 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.tech if you just need general support.

from ipfs-desktop.

This is nearly identical to the problems I had. Keep in mind though, the initial problem of getting ipfs commands to run and spawn my node were about a year ago. And it took me a month or two to work through it. The lock issue is still a mystery at this point for me, but since you haven't gotten off the ground yet, just delete the lock file while it's (not) firing up, and shut it down from the task bar. It mentions that in the ipfs desktop troubleshooting. But you'be got other issues here to tackle anyway. I assumed you were on winDOHz (8+) reading your discription lol. And here's where there's two big things.. WinDOHz built this huge user control system over top of the same ole windows essentially. So the path they show to C:\Users\you isn't the true path, it's just the only one that allegedly works in file explorer for software that is "okay" per the user account control settings. I'm guessing your powershell also doesn't do.... drumroll, anything at all that requires moving around the file system or reaching out your gateway. THey say it's to keep users from grenading themselves, but it's to force feed you a bunch of shiny new apps from the store. Not to mention your network traffic is nice and neat for data collection.

So at the least, make sure you're launching your command line as an admin, even though that's not required for kubo anymore. If you have the onedrive app, shut that down just in case too. (I threw mine in the Cuyahoga River by the waste treatment center where it belongs, but that's up to you. Now, you MIGHT need to also log in to your powershell with a windows account, like dev account you create perhaps, if your node still isn't building at this point. It's come a long way though, so it might work from here. (check user account control settings in the OLD windows security section, or you're gonna blow up like the challenger) :-D

But for me, none of this worked, in ipfs-go's younger days. I had to get rolling with node.js and npm which wasn't too painful. I also have a music server, and Unified Remote, I mention this because those are potential conflicts at the gateway if they're using the ports you've got designated there. Gaming servers, streaming services, anything like that needs checked. Windohz is also wanting to phase out file explorer, and use edge for everything, so any crazy high security there may bone ya too if you're on 11. I use openIN to break out of that prison cell, and of course brave browser, opera, whatever. It comes with Node.js too, it's the best extension there is.

next up, in app and browser control, reputation based ""protection"" , and under that potentially unwanted app blocking. Too see if it blocked your favorite app, go to history there. Next up, under virus protection, ransomware protection, controlled folder access is good for blocking stuff that's trying to mind it's own bussness in say "C:\Users\User..." because we're supposed to pretend that's your root directory now or whatever. Luckily instead of notifying you when they block an app, they'll make you journey to the center of the earth where that setting is first, and then let ya know they ruined your good time yesterday, and the day before that.

Don't let this stuff discourage you, these are selling points for the distributed web. Just don't let Bing find out there's fun going on, neural network means she can be everywhere at once. Microphone off, webcam covered or removed permanantly, and you'll be walking on the move through the apollo archives before ya know it. And beleive it or not, the xbox network process has to either work, or be disabled and they will never tell you about this.

from ipfs-desktop.

@Tuzemooner what are the contents of the C:\Users\Алексей\.ipfs\repo.lock file?

from ipfs-desktop.

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.

from ipfs-desktop.

Oops, seems like we needed more information for this issue, please comment with more details or this issue will be closed in 7 days.

from ipfs-desktop.

This issue was closed because it is missing author input.

from ipfs-desktop.