Created attachment 15136 [details] terminal output Hello ALT Linux team, I am using the technical preview for loongarch64 in qemu (xfce 2023.11.18). When I use apt-get install/upgrade, it's stuck at the last step, showing `egrep: warning: egrep is obsolescent; using egrep -E`. But actually, the packages are successfully installed, and when I do apt-get in a separate terminal, it does not give me "Unable to lock the list directory" prompt. I've attached a screenshot showing some outputs of apt-get and some of my system information. (Although it's showing "Done" and quick, it took quite a long time) Thanks!
Hi, and thanks for your report. > When I use apt-get install/upgrade, it's stuck at the last step, > showing `egrep: warning: egrep is obsolescent; using egrep -E`. Most of the time, the updates are not really stuck; they are running additional stuff (posttrans filetriggers), some of which take quite some time, especially on qemu which, depending on your host, is ether slow or very slow compared to the real hardware. So, when this happens, can you check what's really happening? E.g. run pstree -ap on a second terminal window and attach the output here? Probably there will be something like mandb running. > and when I do apt-get in a separate terminal, it does not give me "Unable to lock the list directory" prompt. This is the correct behavior. Only one instance of package manager can do things at any given moment in time.
Ah, and one more thing. > I've attached a screenshot showing some outputs of apt-get and some of my system information. (Although it's showing "Done" and quick, it took quite a long time). Did I understand it correctly: after all, the update has completed succesfully?
Update: It's no longer stuck now, at least it doesn't take as much time as before. I think it's fixed? And the "egrep: warning: egrep is obsolescent; using egrep -E" warning still shows up. Thanks!
> I think it's fixed? We've improved a few thinks, but since I don't know what exactly was happening, I can't say for sure that *that* thing is fixed. But sure, good to know that things work for you now. I'll mark this as resolved.
