<html><head>
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
</head>
<body bgcolor="#FFFFFF" text="#000000"><div id="fenix-user-content">
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px;"><span style=" font-family:'NokiaPureTextLight';">You could be really the only one experiencing the bug. My guess currently, it fails because it cannot go in specific directories as you did not start catfish as root.</span></p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px;"><span style=" font-family:'NokiaPureTextLight';">Is there any error when you use find or locate from the terminal and perform the same search ?</span></p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px;"><span style=" font-family:'NokiaPureTextLight';">If yes then you figured out its not a catfish bug in general but rather a normal behavior.<br><br>--<br></span></p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px;"><span style=" font-family:'NokiaPureTextLight';">Von meinem Nokia N9 gesendet<br></span></p></div><br><div id="fenix-reply-header"><p>John Hupp schrieb am 08.09.12 02:42:<br></p></div><div id="fenix-quoted-body">
<font size="-1"><font face="Arial">In the Lubuntu documentation,
Catfish is the currently recommended GUI search tool.<br>
<br>
But after installing it, on my very first search attempt
(looking for boot-repair, with search starting in the root), it
generated the result error "Fatal error, search was aborted."<br>
<br>
It does this when using either the Find or Locate backend. In
testing to date, it seems to display this error in the results
pane whenever it cannot find a match.<br>
<br>
Playing around with Find directly (I'm still a newbie), when it
cannot find a match, it simply shows no result. So on the face
of it, this would seem to be a bug with the current version.<br>
<br>
I can't be only one to have noticed this. Is there a solution?<br>
</font></font>
</div><br></body></html>