Failed to start Rovo Dev CLI: The file lock 'C:\Users\myuser\.rovodev\config.yml.lock' could not be acquired.✗ Error: failed to execute the command
help me fix it please
Hey everyone!
We have a release going out soon to fix this!
Apologies for this!
Please try again in a couple of hours!
Updated to : v0.13.47
Welcome to Rovo Dev, Atlassian's AI coding agent.
Here are some quick tips:
• Ask Rovo Dev anything in your own words - from "explain this repository" to "add dark mode to this app".• Use /help for more information and /exit to quit.
────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────Claude Sonnet 4.6 is now available in Rovo Dev! 🚀
Sonnet 4.6 is now available for all users - try it out today by running /models────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────Working in C:\
✔ Using model: auto✔ Started 3 MCP serversWorking !
same here not working even on MAC. Seems like you are on windows.
Same here. its probably a BUG Atlassian needs to fix in Rovodev CLI.
same issue. This happened after recent rovodev cli update (v0.13.46). I have updated acli to latest version(1.3.13-stable).But issue still persist.
is there an alternative approach?
@Van Madhavan I couldn't find any.
Same here, deleting config.yaml.lock not helping
Same here
same here, not solved even with acli upgrade
I've tested on mac, windows and ubuntu, no luck
the same for me
i got the same issue
the same also
Did you find the solve or is it an acli problem
Mismo problema
Same thing, please help
guys thats a major problem , its not individual to anyone (btw no one paid me to write it)
almost 12 hours and still no fix,
thats rediculos to update it and break it for so long lol Atlassian customer service + quality is low
+1
Is Rovodev aware of the bug? I hope they fix this problem soon.
Workaround I found for the `config.yml.lock` / guard-lock issue (Linux/WSL)
This bypasses the file locking calls that seem to get stuck, by preloading a tiny shared lib that no-ops flock() and fcntl(F_SETLK/F_SETLKW). Not ideal, but it got me unblocked.
1) Clear any stuck processes + remove the global guard lockpkill -f "rovodev|acli" || truerm -f /tmp/rovodev_global.lock
2) Build the preload librarycat > /tmp/nolock.c <<'C'#define _GNU_SOURCE#include <dlfcn.h>#include <stdarg.h>#include <sys/file.h>#include <fcntl.h>#include <stddef.h> // for NULL
int flock(int fd, int operation) { (void)fd; (void)operation; return 0; }
int fcntl(int fd, int cmd, ...) {static int (*real_fcntl)(int,int,...) = NULL;if (!real_fcntl) real_fcntl = dlsym(RTLD_NEXT, "fcntl");
va_list ap; va_start(ap, cmd);void *arg = va_arg(ap, void*);va_end(ap);
if (cmd == F_SETLK || cmd == F_SETLKW) return 0;return real_fcntl(fd, cmd, arg);}C
gcc -shared -fPIC -o /tmp/nolock.so /tmp/nolock.c -ldlls -la /tmp/nolock.so
If `ls -la` shows the file exists, LD_PRELOAD should work.
3) Run Rovo Dev with the preload (test run)LD_PRELOAD=/tmp/nolock.so acli rovodev run
Notes:- This is a workaround (it disables locking), so use at your own risk.- Sharing in case it helps others while Atlassian investigates the root cause.
i think we will be forced to wait till monday for the official working days😒😒😒
Same problem , I reinstalled and install it in unbunto but nothing works , I hope they fix the problem soon
Thanks @Jovana Dunisijevic - it's working again.
Hey ya'll, Atlassian fixed the config.yml.lock could not be acquired issue in v0.13.47, and users confirmed updating resolved it. The best fix is to rerun/update to the latest Rovo Dev version and try again. Deleting the lock file alone usually did not help.
config.yml.lock could not be acquired
It looks like you're new here. Sign in or register to get started.
