Powerlevel10k: bad file descriptor console output from _p9k_worker_start

Created on 19 May 2020  路  6Comments  路  Source: romkatv/powerlevel10k

I just updated and now I am getting a warning with the instant prompt, and I am on macOS.
I think this is related to source ~/.p10k.zsh because if I commented that out, there is no warnings anymore. I am not sure if this is a problem because of the recent changes in this repo.

console output produced during zsh initialization follows

_p9k_worker_start:8: failed to close file descriptor 13: bad file descriptor
_p9k_worker_start:9: failed to close file descriptor 14: bad file descriptor
_p9k_worker_start:10: failed to close file descriptor 15: bad file descriptor

Most helpful comment

Thanks for the reports, everyone. I've reverted the bad commit. Sorry for the breakage. Never a good idea to push late at night.

All 6 comments

I get the same message, but on debian 10, with instant prompt enabled. The errors don't appear when disabling instant prompt in .zshrc.

_p9k_worker_start:8: failed to close file descriptor 13: bad file descriptor
_p9k_worker_start:9: failed to close file descriptor 14: bad file descriptor
_p9k_worker_start:10: failed to close file descriptor 15: bad file descriptor

If I disable instant prompt the errors don't appear

I reverted the change for now by going into ~/.zinit/plugins/romkatv---powerlevel10k and do a git checkout fb9bc2d3.

Disabling disk_usage and ran segments also helps with this issue

Getting the same issue on WSL 2 Ubuntu 18.04 LTS
image
Commenting out instant prompt in .zshrc fixes the issue for me as well.

Thanks for the reports, everyone. I've reverted the bad commit. Sorry for the breakage. Never a good idea to push late at night.

Was this page helpful?
0 / 5 - 0 ratings