recoll (desktop-search engine): error-message in a popup-window
when starting recoll (e.g. after booting up the computer) the GUI opens alright. After typing a search-term the search begins but I get an error-message in a popup:
Aufrund von Einschränkungen der Indizierungs-Bibliothek führt ein
Abbruch zur Beendigung des Programms
, which translates roughly into
Due to limitations of the indexing library, aborting causes the
program to terminate.
The search itself seems to work though and produces the desired results.
When closing recoll and then opening again this phenomenon cannot be observed any more. It works without complaints.
Curious thing though:
When using recoll a while afterwards (e.g. 2 hours later) the error-message pops up again.
BTW: terminal says: "'recoll' terminated by signal SIGSEGV (Adressbereichsfehler)"
Why is that and what could I do?
P.S.:
my system: Linux/Lubuntu 16.04 LTS, 64 bit
lubuntu recoll
add a comment |
when starting recoll (e.g. after booting up the computer) the GUI opens alright. After typing a search-term the search begins but I get an error-message in a popup:
Aufrund von Einschränkungen der Indizierungs-Bibliothek führt ein
Abbruch zur Beendigung des Programms
, which translates roughly into
Due to limitations of the indexing library, aborting causes the
program to terminate.
The search itself seems to work though and produces the desired results.
When closing recoll and then opening again this phenomenon cannot be observed any more. It works without complaints.
Curious thing though:
When using recoll a while afterwards (e.g. 2 hours later) the error-message pops up again.
BTW: terminal says: "'recoll' terminated by signal SIGSEGV (Adressbereichsfehler)"
Why is that and what could I do?
P.S.:
my system: Linux/Lubuntu 16.04 LTS, 64 bit
lubuntu recoll
add a comment |
when starting recoll (e.g. after booting up the computer) the GUI opens alright. After typing a search-term the search begins but I get an error-message in a popup:
Aufrund von Einschränkungen der Indizierungs-Bibliothek führt ein
Abbruch zur Beendigung des Programms
, which translates roughly into
Due to limitations of the indexing library, aborting causes the
program to terminate.
The search itself seems to work though and produces the desired results.
When closing recoll and then opening again this phenomenon cannot be observed any more. It works without complaints.
Curious thing though:
When using recoll a while afterwards (e.g. 2 hours later) the error-message pops up again.
BTW: terminal says: "'recoll' terminated by signal SIGSEGV (Adressbereichsfehler)"
Why is that and what could I do?
P.S.:
my system: Linux/Lubuntu 16.04 LTS, 64 bit
lubuntu recoll
when starting recoll (e.g. after booting up the computer) the GUI opens alright. After typing a search-term the search begins but I get an error-message in a popup:
Aufrund von Einschränkungen der Indizierungs-Bibliothek führt ein
Abbruch zur Beendigung des Programms
, which translates roughly into
Due to limitations of the indexing library, aborting causes the
program to terminate.
The search itself seems to work though and produces the desired results.
When closing recoll and then opening again this phenomenon cannot be observed any more. It works without complaints.
Curious thing though:
When using recoll a while afterwards (e.g. 2 hours later) the error-message pops up again.
BTW: terminal says: "'recoll' terminated by signal SIGSEGV (Adressbereichsfehler)"
Why is that and what could I do?
P.S.:
my system: Linux/Lubuntu 16.04 LTS, 64 bit
lubuntu recoll
lubuntu recoll
edited Jan 9 at 13:37
Rosika
asked Jan 9 at 13:25
RosikaRosika
739
739
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
O.K.,
seems I could sort it out with the help of medoc.
I posted a ticket here: https://opensourceprojects.eu/p/recoll1/tickets/68/
and got help from recoll support.
This actually isn´t an error:
This is not really an error. The important part is the first phrase
"Query in progress"
This message appears when a query does not return instantaneously
(takes more than a few seconds).
This is to warn the user that it is possible to abort the search, but
that the GUI will have to exit (because the Xapian developpers refuse
to implement cancellation points).
You don't get it the second time because the data is in the cache, so
the search goes faster.
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1108285%2frecoll-desktop-search-engine-error-message-in-a-popup-window%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
O.K.,
seems I could sort it out with the help of medoc.
I posted a ticket here: https://opensourceprojects.eu/p/recoll1/tickets/68/
and got help from recoll support.
This actually isn´t an error:
This is not really an error. The important part is the first phrase
"Query in progress"
This message appears when a query does not return instantaneously
(takes more than a few seconds).
This is to warn the user that it is possible to abort the search, but
that the GUI will have to exit (because the Xapian developpers refuse
to implement cancellation points).
You don't get it the second time because the data is in the cache, so
the search goes faster.
add a comment |
O.K.,
seems I could sort it out with the help of medoc.
I posted a ticket here: https://opensourceprojects.eu/p/recoll1/tickets/68/
and got help from recoll support.
This actually isn´t an error:
This is not really an error. The important part is the first phrase
"Query in progress"
This message appears when a query does not return instantaneously
(takes more than a few seconds).
This is to warn the user that it is possible to abort the search, but
that the GUI will have to exit (because the Xapian developpers refuse
to implement cancellation points).
You don't get it the second time because the data is in the cache, so
the search goes faster.
add a comment |
O.K.,
seems I could sort it out with the help of medoc.
I posted a ticket here: https://opensourceprojects.eu/p/recoll1/tickets/68/
and got help from recoll support.
This actually isn´t an error:
This is not really an error. The important part is the first phrase
"Query in progress"
This message appears when a query does not return instantaneously
(takes more than a few seconds).
This is to warn the user that it is possible to abort the search, but
that the GUI will have to exit (because the Xapian developpers refuse
to implement cancellation points).
You don't get it the second time because the data is in the cache, so
the search goes faster.
O.K.,
seems I could sort it out with the help of medoc.
I posted a ticket here: https://opensourceprojects.eu/p/recoll1/tickets/68/
and got help from recoll support.
This actually isn´t an error:
This is not really an error. The important part is the first phrase
"Query in progress"
This message appears when a query does not return instantaneously
(takes more than a few seconds).
This is to warn the user that it is possible to abort the search, but
that the GUI will have to exit (because the Xapian developpers refuse
to implement cancellation points).
You don't get it the second time because the data is in the cache, so
the search goes faster.
answered Jan 9 at 14:08
RosikaRosika
739
739
add a comment |
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1108285%2frecoll-desktop-search-engine-error-message-in-a-popup-window%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown