diff --git a/doc/bugs/git-annex__58_____60__stdout__62____58___hPutBuf__58___resource_vanished/comment_3_eaa0748eed9398ba59d49b3387ac4a82._comment b/doc/bugs/git-annex__58_____60__stdout__62____58___hPutBuf__58___resource_vanished/comment_3_eaa0748eed9398ba59d49b3387ac4a82._comment
new file mode 100644
index 0000000000..413b654eb7
--- /dev/null
+++ b/doc/bugs/git-annex__58_____60__stdout__62____58___hPutBuf__58___resource_vanished/comment_3_eaa0748eed9398ba59d49b3387ac4a82._comment
@@ -0,0 +1,11 @@
+[[!comment format=mdwn
+ username="pierreay"
+ avatar="http://cdn.libravatar.org/avatar/c1c640f9f581daaf2d9dedff2b84b614"
+ subject="comment 3"
+ date="2025-05-26T19:38:41Z"
+ content="""
+Thank you @joey and @mak for the hints.
+I was unable (even with strace) for chase down the particular system call that cause the issue, since it is highly random and generated by my shell prompt.
+However, mak seems right about the git_status module of starship. I increased my timeout from 500ms (default) to 1000ms (and will try slightly larger value if needed).
+If this mitigate the issue correctly, I will not comment anymore! But I suspect it to work. ;)
+"""]]