This is not a bug. It means another apt-get process is running on system, probably a cron-triggered 'apt-get update'. You might want to kill that process.
Another possibility is that you have killed previous apt-get process with SIGKILL, and now you need to remove lockfile manually.
This is not a bug. It means another apt-get process is running on system, probably a cron-triggered 'apt-get update'. You might want to kill that process.
Another possibility is that you have killed previous apt-get process with SIGKILL, and now you need to remove lockfile manually.