Errors in the daemon do not route to the web UI #52

New issue

Closed

opened 2026-10-25 00:01:36 +00:00 by TheComputerGuy · 0 comments

TheComputerGuy commented

2026-10-25 00:01:36 +00:00

Owner

For example, the daemon can say something like:

chock run: the credential for the provider ... could not be read: the secret service would not give the credential for ...: the default collection is locked and this session cannot unlock it: nobody is there to answer a prompt. A desktop login unlocks it, and so does secret-tool unlock --collection default. A machine reached only over ssh usually cannot.
chock daemon: session ... exited 1

This should show up as an error message on the web UI.

For example, the daemon can say something like: ``` chock run: the credential for the provider ... could not be read: the secret service would not give the credential for ...: the default collection is locked and this session cannot unlock it: nobody is there to answer a prompt. A desktop login unlocks it, and so does secret-tool unlock --collection default. A machine reached only over ssh usually cannot. chock daemon: session ... exited 1 ``` This should show up as an error message on the web UI.

TheComputerGuy added reference fix/web-daemon-errors

2026-10-25 11:48:38 +00:00

TheComputerGuy added the

bug

label

2026-10-25 11:49:21 +00:00

TheComputerGuy referenced this issue from a pull request that will close it,

2026-10-25 11:49:35 +00:00

fix: show daemon child errors in session UI #54

TheComputerGuy closed this issue

2026-10-25 14:14:13 +00:00