BrokenPipeError when asking for Admin

[Rukur]

Explain what happens

1. After the last update Yesterday. I am having issues.
2. I am login into a server and everything works as a limited user. When I click to get Admin privileges. I
3. Received these error in logs and the Cockpit Client opens a window with "Problem becoming administrator Peer exited with status 1".
5. Process 5466 (cockpit-askpass) of user 1000 encountered an uncaught BrokenPipeError exception cockpit-askpass
6. Process 5055 (cockpit-bridge) of user 1000 encountered an uncaught cockpit.jsonutil.JsonError exception

Version of Cockpit

309

Where is the problem in Cockpit?

Unknown or not applicable

Server operating system

Fedora

Server operating system version

39

What browsers are you using?

Cockpit Client / Cockpit Desktop

System log

5:01 PM Process 5466 (cockpit-askpass) of user 1000 encountered an uncaught BrokenPipeError exception
cockpit-askpass

5:01 PM Process 5055 (cockpit-bridge) of user 1000 encountered an uncaught cockpit.jsonutil.JsonError exception
cockpit-bridge

5:01 PM pam_unix(sudo:auth): auth could not identify password for [tank]
sudo

5:01 PM pam_unix(sudo:auth): conversation failed
sudo

[spmfox]

Seeing something similar on CentOS Stream 9, cockpit terminates the session when asking for admin rights. I cannot find a useful log for some reason, but downgrading cockpit-system and cockpit-bridge from 310 -> 309 resolves the problem.

[spmfox]

Still having a hard time reproducing this. I was connecting to one host (EL9, cockpit* 309) and using that host to connect to other EL9 cockpit 310 machines via SSH key and it broke every time. I logged into cockpit directly on these machines and they were broken when trying to escalate to admin rights.

Then I made brand new EL8 and EL9 boxes with cockpit 310 and was unable to reproduce this. Upgrading my original jump box from 309->310 resolved all problems with that.

[Rukur]

I have been using the web browser and allowing http but I will check if flatpak has 310 now

On Fri, Feb 16, 2024 at 1:58 PM spmfox @.***> wrote:

Still having a hard time reproducing this. I was connecting to one host (EL9, cockpit* 309) and using that host to connect to other EL9 cockpit 310 machines via SSH key and it broke every time. I logged into cockpit directly on these machines and they were broken when trying to escalate to admin rights.

Then I made brand new EL8 and EL9 boxes with cockpit 310 and was unable to reproduce this. Upgrading my original jump box from 309->310 resolved all problems with that.

— Reply to this email directly, view it on GitHub https://github.com/cockpit-project/cockpit/issues/20008#issuecomment-1947682674, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADG5W57NEZJPFPJBHO6QSZTYT3DM3AVCNFSM6AAAAABDF5K7GGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNBXGY4DENRXGQ . You are receiving this because you authored the thread.Message ID: @.***>