diff --git a/doc/bugs/whereis_shouldn__39__t_just_crash_if_one_of_the_special_remotes___34__drivers__34___is_not_available/comment_1_3f8100a4d9e6ab4302c89eeafd0f843e._comment b/doc/bugs/whereis_shouldn__39__t_just_crash_if_one_of_the_special_remotes___34__drivers__34___is_not_available/comment_1_3f8100a4d9e6ab4302c89eeafd0f843e._comment
new file mode 100644
index 0000000000..40f5b4cba3
--- /dev/null
+++ b/doc/bugs/whereis_shouldn__39__t_just_crash_if_one_of_the_special_remotes___34__drivers__34___is_not_available/comment_1_3f8100a4d9e6ab4302c89eeafd0f843e._comment
@@ -0,0 +1,13 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 1"""
+ date="2018-09-12T18:16:49Z"
+ content="""
+Hmm, but the special remote can add urls to the whereis output, indeed it
+is doing so in your example. So if the repository has the special remote
+enabled it seems it ought to need it to be in working order.
+
+External special remote programs are only spun up on demand, so the only
+way to get to this crash is when it's actually being used for something,
+AFAICS.
+"""]]