Got stuck trying to reinstall broken packages.

gnomo

Hi, i got stuck in "reading password" trying to run the command sudo eopkg check | grep Broken | awk '{print $4}' | xargs sudo eopkg it --reinstall, i have some packages broken (could saw it when sudo eopkg check). Can i fix it ? Thanks in advance.

Justin

gnomo What do you mean by it got stuck reading password? Is it saying your password is incorrect?

gnomo

It takes a long time to read the password and finish cancelling the command because take to much time to read the password. Didn't have the same problem with any other command that uses sudo.

just

gnomo It takes a long time to read the password...

It doesn't sudo which takes a long time to read the password. The time is taken by eopkg check command. The latter takes about 10..15 min to finish here.

To estimate the time eopkg check takes on your hardware, run it without piping to other commands:

sudo eopkg check

You may interrupt it at any moment with Ctrl+C.

Girtablulu

what is your system language? English?

gnomo

Girtablulu It's portuguese

gnomo

just sudo eopkg check runs normal, but this gaven by the Help Center don't, just stuck on reading the password and, for some reason, it can't read and cancel the operation. Sorry for my english, maybe it gets dificult to understand. I want to re install the broken packages, but i don't no how. ;-;

Girtablulu

gnomo yea you would need to change the Broken in that line of code into the one it spits out for portugues, is the same in german won't work with the english name

just

gnomo Probably I don't understand what you're trying to say.

The "short" sudo eopkg check command checks all packages, and DOES display check's result for each package, one line per package. It takes about 15 min here.

The "long" sudo eopkg check | grep Broken | ... command also checks all packages, but does NOT displays anything for good packages. You may get a wrong impression that the command does nothing. The output will be displayed ONLY for broken packages, if any.

The long command takes either exactly the same time as the short one, if no broken packages are found, or a few more seconds, if it needs to re-install a few broken packages. While the long command runs, nothing is displayed for good packages.

gnomo

gnomo@gnomeu ~ $ sudo eopkg check | grep Broken | awk '{print $4}' | xargs sudo eopkg it --reinstall Senha: sudo: tempo limite esgotado lendo senha tradution: sudo: timeout reading password
But if i run any other command i run normally it not gave me this, just work without problems

Axios

I had that problem the other day with same command finally gave up but tried it 2 days later and it worked I have no Idea
what happened. the command is correct because when it works it works.

gnomo

So, i was looking on man eopkg and figure out a way to reinstall the broken packages, it's sudo eopkg it --reinstall, put this after check the packages. Thank you guys for all the support.

Justin

It's likely the second request for sudo not receiving the password in time and timing out.

gnomo

gnomo@gnomeu ~ $ sudo eopkg check udisks solus-sc gnome-session gnome-control-center budgie-desktop Checando a integridade do udisks Quebrado (broken) Arquivo corrompido: /usr/lib/tmpfiles.d/udisks2.conf how can i replace this file ?

just

gnomo

Brokenn udisks package is considered as a normal situation. Type in udisks in the Search filed at the top right part of the forum. You'll find a dozen of topics which explain that.

There's no need to re-install udisks package or replace udisks2.conf file.

gnomo

Thank you just, i read some same problems as mine, but i still with this doubt with this command in troubleshooting. Although i could replace the adwaita-icon-theme package that was broken, so any more problems here, i'm glad by knowing if there is any problems, i can come here and look for help and i'll have it. Thank you all for pay attention to a noob 😃