Re: KDEPIM ready to be more broadly tested (libkpim.*4)
On Friday, July 29, 2016 8:40:31 PM CEST you wrote: > Kopete is still developed and being ported to Frameworks. I must have mistaken it for something else (my bad anyway). > kde-standard is a Debian-specific metapackage, which probably has no sense > given the evolution of the meaning of "KDE". > > Ciao
Re: KDEPIM ready to be more broadly tested (libkpim.*4)
Il 29 luglio 2016 20:30:43 CEST, inkbottle ha scritto: >Hi, > >So I did eventually upgraded to new KDEPIM. > >When doing my upgrade I saw some "libkpimindent.*4" and more generally >"libkpim.*4" things. I resolved to remove them for the sake of >cleanness... > >Hence I had to remove "kopete" and hence kde-standard too. > >I understood kopete is something of the past (?); if so it could be >removed >from kde-standard: is kde-standard a Debian thing? Kopete is still developed and being ported to Frameworks. kde-standard is a Debian-specific metapackage, which probably has no sense given the evolution of the meaning of "KDE". Ciao -- Luigi
Re: [KDEPIM Kmail] Wrongly displayed message
On venerdì 29 luglio 2016 10:24:58 CEST you wrote:
> Hi,
>
> to better understand what's happening, you can try to:
>
> 1- View the message structure ("Visualizza -> Mostra la struttura del
> messaggio" in Italian or something like "View -> Message structure" in the
> default English menus). This should show you whether there are other parts
> of the message that you are not seeing (and allow you to select and see
> them).
>
> 2- If that does not work, you can view the message source ("Visualizza ->
> Mostra sorgente" in Italian or something like "View -> Show source" in
> English). This should also allow you to see if the message contains
> something else that you are not able to see in the default view.
>
> Hope that helps!
> Mario
>
> P.S: I apologize for non-Italian speakers, but I don't know the exact names
> of the above options in the standard English menus.
>
> In data venerdì 29 luglio 2016 00:39:20 CEST, Valerio Passini ha scritto:
> > On giovedì 28 luglio 2016 11:33:29 CEST Martin Steigerwald wrote:
> > > Am Donnerstag, 28. Juli 2016, 10:58:03 CEST schrieb Valerio Passini:
> > > > Today I've discovered that some messages from Amazon where not shown,
> > > > I
> > > > mean: there was the subject, the sender, but no message inside. The
> > > > message
> > > > looks like HTML stuff to me, but other messages of this kind are
> > > > visible
> > > > simply by clicking on "enable html" string. The only hint I've is on
> > > > the
> > > > left side of the message and it says "No html message", while the
> > > > working
> > > > messages reports either "HTML message" or "Plain message". When
> > > > replying,
> > > > at least the text part of the invisible message is embedded in, what's
> > > > wrong then?
> > >
> > > The HTML stuff may be in another part of the message that you can select
> > > and then view the HTML.
> >
> > Here is how it's displayed: just a white page.
> >
> > Valerio
Thanks Mario, for your hint.
I recall that option to be enabled in the previous versions of Kontact/Kmail,
I don't know what (who) disabled it and when, anyhow with that option set, I
could see there is a "html document" in the "body part" and after some
clicking it was possible to display the full message.
Is this some kind of security feature? Isn't it too much? Personally I would
agree to not allow the downloading of external links, but concealing the text
might be a little confusing.
Valerio
Re: KDEPIM ready to be more broadly tested (libkpim.*4)
Hi, So I did eventually upgraded to new KDEPIM. When doing my upgrade I saw some "libkpimindent.*4" and more generally "libkpim.*4" things. I resolved to remove them for the sake of cleanness... Hence I had to remove "kopete" and hence kde-standard too. I understood kopete is something of the past (?); if so it could be removed from kde-standard: is kde-standard a Debian thing? Chris
Re: KDEPIM ready to be more broadly tested
On Thursday, July 28, 2016 16:54:43 Tim Ruehsen wrote:
> So, you are on Sid/unstable ?
> And you did
> apt-get update && apt-get dist-upgrade before ?
>
> okular never stopped working here and I use it quite often.
>
> $ dpkg -l '*okular*'
> ii libokularcore6 4:15.08.3-1 amd64
> libraries for the Okular document viewer
> ii libokularcore7 4:16.04.2-1 amd64
> libraries for the Okular document viewer
> ii okular 4:16.04.2-1 amd64
> universal document viewer
> ii okular-extra-backends 4:16.04.2-1 amd64
> additional document format support for Okular
Looking at the messages here, and also at
https://qa.debian.org/developer.php?login=debian-qt-kde%40lists.debian.org,
I was a bit overenthusiastic, and thought version numbers beginning with "4:4|
4:15" was mostly something of the past.
The output output of:
aptitude search -F"%p; %V; %d" -t sid '?installed(?version("4:4|
4:15")?maintainer(debian-qt-kde))'|egrep "4:4|4:15"|wc -l
might not be so relevant, but it yields a "surprising?" 132 on my system.
Chris
>
> But I guess libokularcore6 is orphaned and could be purged.
>
> What exactly is your problem now ?
>
> Tim
Re: KDEPIM ready to be more broadly tested
Am Freitag, 29. Juli 2016, 13:13:45 CEST schrieb Tim Ruehsen: > On Friday, July 29, 2016 10:08:52 AM CEST Volker Groll wrote: > > Am Donnerstag, 28. Juli 2016, 21:26:03 CEST schrieb Tim Rühsen: > > > On Donnerstag, 28. Juli 2016 17:27:25 CEST Volker Groll wrote: > > > > Am Donnerstag, 28. Juli 2016, 16:54:43 CEST schrieb Tim Ruehsen: > > > > > On Thursday, July 28, 2016 4:35:12 PM CEST Volker Groll wrote: > > > > > > Hello Tim, > > > > > > > > > > > > Am Donnerstag, 28. Juli 2016, 14:06:14 CEST schrieb Tim Ruehsen: > > > > > > > On Thursday, July 28, 2016 1:46:55 PM CEST Volker Groll wrote: > > > > > > > > Hi everybody, > > > > > > > > > > > > > > > > I followed Tim's journey through akonadi the last days and > > > > > > > > reproduced > > > > > > > > the steps here with no success. Last night I removed > > > > > > > > (hopefully) > > > > > > > > all > > > > > > > > stuff > > > > > > > > from .config, .local, .kde which seems to me connected to > > > > > > > > baloo > > > > > > > > or > > > > > > > > akonadi > > > > > > > > or any parts of kontact modules. > > > > > > > > Then I recreated every mail stuff again => no success, the > > > > > > > > normal > > > > > > > > search > > > > > > > > above the mai list is working, akonadi search gives either > > > > > > > > nothing > > > > > > > > or > > > > > > > > stupid results not connected to the search. > > > > > > > > > > > > > > > > I also throwed 4:4.14 packages with help of deborphan out of > > > > > > > > my > > > > > > > > system > > > > > > > > but especially libakonadi stuff is at 4:4.14.10-5? > > > > > > > > > > > > > > Here we talked about Sid/unstable having 16.04.x. > > > > > > > > > > > > > > $ dpkg -l|egrep 'akonadi|baloo|kdepim' > > > > > > > > > > > > > > I can't say anything about the 4.14. stuff except that it was > > > > > > > working > > > > > > > before I went to 16.04. > > > > > > > > > > > > > > Regards, Tim > > > > > > > > > > > > Thanks for your answer. > > > > > > > > > > > > I removed now all 4.14 stuff related to akondi|baloo|kdepim. > > > > > > Both digikam and kde-utils (and kde-full!) pulled the old stuff, > > > > > > while > > > > > > installing libakonadi-kf5 won't complain, so I thought it is ok. > > > > > > Now all akonadi stuff is 4:16.04.x or 16.04.x. > > > > > > BTW: what means the leading '4'? > > > > > > > > > > No idea. > > > > > > > > > > > Also agentIndexingVersion=4 in baloorc gives a hint to version 4? > > > > > > > > > > No, it is some internal protocol version. > > > > > > > > > > > Proceedings are of course: > > > > > > stop akonadi and baloo, remove search_db, changed baloorc > > > > > > initialIndexingDone=false and reboot. > > > > > > The hell: No change. > > > > > > > > > > > > And yes, with 4.14 it worked with minor flaws on display. > > > > > > > > > > > > There is also more old stuff of kde around, also parts of 15.x > > > > > > But I need at least okular. > > > > > > > > > > So, you are on Sid/unstable ? > > > > > And you did > > > > > apt-get update && apt-get dist-upgrade before ? > > > > > > > > Yes, I came from stretch, and honestly I used aptitude dist-upgrade. > > > > apt-get dist-upgrade does not want apply any changes right now > > > > > > > > > okular never stopped working here and I use it quite often. > > > > > > > > > > $ dpkg -l '*okular*' > > > > > ii libokularcore6 4:15.08.3-1 amd64 > > > > > libraries for the Okular document viewer > > > > > ii libokularcore7 4:16.04.2-1 amd64 > > > > > libraries for the Okular document viewer > > > > > ii okular 4:16.04.2-1 amd64 > > > > > universal document viewer > > > > > ii okular-extra-backends 4:16.04.2-1 amd64 > > > > > additional document format support for Okular > > > > > > > > > > But I guess libokularcore6 is orphaned and could be purged. > > > > > > > > Sorry misleading you. > > > > I checked most of my installed kde packages to be on 16.04 > > > > and started to throw away everything older. > > > > I of course installed the needed packages again. > > > > By this: For me okular is working without libokularcore7. > > > > > > okular 16.04.2-1 has a dependency: libokularcore7 (= 4:16.04.2-1) > > > You can see this via > > > $ apt-cache show okular > > > > > > > Both baloo and akonadi are not working as expected: > > > > On baloo when I try to index file contents it hangs indefinitely > > > > and I cannot find any open file handler within baloo_indexer or > > > > baloo_file_extractor hinting to a file causing this.
Re: KDEPIM ready to be more broadly tested
On Friday, July 29, 2016 10:08:52 AM CEST Volker Groll wrote: > Am Donnerstag, 28. Juli 2016, 21:26:03 CEST schrieb Tim Rühsen: > > On Donnerstag, 28. Juli 2016 17:27:25 CEST Volker Groll wrote: > > > Am Donnerstag, 28. Juli 2016, 16:54:43 CEST schrieb Tim Ruehsen: > > > > On Thursday, July 28, 2016 4:35:12 PM CEST Volker Groll wrote: > > > > > Hello Tim, > > > > > > > > > > Am Donnerstag, 28. Juli 2016, 14:06:14 CEST schrieb Tim Ruehsen: > > > > > > On Thursday, July 28, 2016 1:46:55 PM CEST Volker Groll wrote: > > > > > > > Hi everybody, > > > > > > > > > > > > > > I followed Tim's journey through akonadi the last days and > > > > > > > reproduced > > > > > > > the steps here with no success. Last night I removed (hopefully) > > > > > > > all > > > > > > > stuff > > > > > > > from .config, .local, .kde which seems to me connected to baloo > > > > > > > or > > > > > > > akonadi > > > > > > > or any parts of kontact modules. > > > > > > > Then I recreated every mail stuff again => no success, the > > > > > > > normal > > > > > > > search > > > > > > > above the mai list is working, akonadi search gives either > > > > > > > nothing > > > > > > > or > > > > > > > stupid results not connected to the search. > > > > > > > > > > > > > > I also throwed 4:4.14 packages with help of deborphan out of my > > > > > > > system > > > > > > > but especially libakonadi stuff is at 4:4.14.10-5? > > > > > > > > > > > > Here we talked about Sid/unstable having 16.04.x. > > > > > > > > > > > > $ dpkg -l|egrep 'akonadi|baloo|kdepim' > > > > > > > > > > > > I can't say anything about the 4.14. stuff except that it was > > > > > > working > > > > > > before I went to 16.04. > > > > > > > > > > > > Regards, Tim > > > > > > > > > > Thanks for your answer. > > > > > > > > > > I removed now all 4.14 stuff related to akondi|baloo|kdepim. > > > > > Both digikam and kde-utils (and kde-full!) pulled the old stuff, > > > > > while > > > > > installing libakonadi-kf5 won't complain, so I thought it is ok. > > > > > Now all akonadi stuff is 4:16.04.x or 16.04.x. > > > > > BTW: what means the leading '4'? > > > > > > > > No idea. > > > > > > > > > Also agentIndexingVersion=4 in baloorc gives a hint to version 4? > > > > > > > > No, it is some internal protocol version. > > > > > > > > > Proceedings are of course: > > > > > stop akonadi and baloo, remove search_db, changed baloorc > > > > > initialIndexingDone=false and reboot. > > > > > The hell: No change. > > > > > > > > > > And yes, with 4.14 it worked with minor flaws on display. > > > > > > > > > > There is also more old stuff of kde around, also parts of 15.x > > > > > But I need at least okular. > > > > > > > > So, you are on Sid/unstable ? > > > > And you did > > > > apt-get update && apt-get dist-upgrade before ? > > > > > > Yes, I came from stretch, and honestly I used aptitude dist-upgrade. > > > apt-get dist-upgrade does not want apply any changes right now > > > > > > > okular never stopped working here and I use it quite often. > > > > > > > > $ dpkg -l '*okular*' > > > > ii libokularcore6 4:15.08.3-1 amd64 > > > > libraries for the Okular document viewer > > > > ii libokularcore7 4:16.04.2-1 amd64 > > > > libraries for the Okular document viewer > > > > ii okular 4:16.04.2-1 amd64 > > > > universal document viewer > > > > ii okular-extra-backends 4:16.04.2-1 amd64 > > > > additional document format support for Okular > > > > > > > > But I guess libokularcore6 is orphaned and could be purged. > > > > > > Sorry misleading you. > > > I checked most of my installed kde packages to be on 16.04 > > > and started to throw away everything older. > > > I of course installed the needed packages again. > > > By this: For me okular is working without libokularcore7. > > > > okular 16.04.2-1 has a dependency: libokularcore7 (= 4:16.04.2-1) > > You can see this via > > $ apt-cache show okular > > > > > Both baloo and akonadi are not working as expected: > > > On baloo when I try to index file contents it hangs indefinitely > > > and I cannot find any open file handler within baloo_indexer or > > > baloo_file_extractor hinting to a file causing this. > > > BTW: with dolphin4 I can search (and find) the content of files! > > > > baloo does file indexing, akonadi does email indexing (and some more). > > I think I understand the basic purpose, but I miss tools and/or instructions > to track down errors from a user perspective. > Which (config) files to check / remove, access akonadi from command line, > check caching stuff, databases? Then it would be possible to ask more > precise for assistance. Exaggregated I can only say: Search does not work. I can currently 'akonadictl restart' without (serious) errors. One type of error that I just fixed: "AgentManager::agentInstanceSynchronizeCollection" Agent instance "akonadi_mixedmaildir_resource_0" has no re
Re: KDEPIM ready to be more broadly tested
On Friday, July 29, 2016 10:08:52 AM CEST Volker Groll wrote: > Am Donnerstag, 28. Juli 2016, 21:26:03 CEST schrieb Tim Rühsen: > > On Donnerstag, 28. Juli 2016 17:27:25 CEST Volker Groll wrote: > > > Am Donnerstag, 28. Juli 2016, 16:54:43 CEST schrieb Tim Ruehsen: > > > > On Thursday, July 28, 2016 4:35:12 PM CEST Volker Groll wrote: > > > > > Hello Tim, > > > > > > > > > > Am Donnerstag, 28. Juli 2016, 14:06:14 CEST schrieb Tim Ruehsen: > > > > > > On Thursday, July 28, 2016 1:46:55 PM CEST Volker Groll wrote: > > > > > > > Hi everybody, > > > > > > > > > > > > > > I followed Tim's journey through akonadi the last days and > > > > > > > reproduced > > > > > > > the steps here with no success. Last night I removed (hopefully) > > > > > > > all > > > > > > > stuff > > > > > > > from .config, .local, .kde which seems to me connected to baloo > > > > > > > or > > > > > > > akonadi > > > > > > > or any parts of kontact modules. > > > > > > > Then I recreated every mail stuff again => no success, the > > > > > > > normal > > > > > > > search > > > > > > > above the mai list is working, akonadi search gives either > > > > > > > nothing > > > > > > > or > > > > > > > stupid results not connected to the search. > > > > > > > > > > > > > > I also throwed 4:4.14 packages with help of deborphan out of my > > > > > > > system > > > > > > > but especially libakonadi stuff is at 4:4.14.10-5? > > > > > > > > > > > > Here we talked about Sid/unstable having 16.04.x. > > > > > > > > > > > > $ dpkg -l|egrep 'akonadi|baloo|kdepim' > > > > > > > > > > > > I can't say anything about the 4.14. stuff except that it was > > > > > > working > > > > > > before I went to 16.04. > > > > > > > > > > > > Regards, Tim > > > > > > > > > > Thanks for your answer. > > > > > > > > > > I removed now all 4.14 stuff related to akondi|baloo|kdepim. > > > > > Both digikam and kde-utils (and kde-full!) pulled the old stuff, > > > > > while > > > > > installing libakonadi-kf5 won't complain, so I thought it is ok. > > > > > Now all akonadi stuff is 4:16.04.x or 16.04.x. > > > > > BTW: what means the leading '4'? > > > > > > > > No idea. > > > > > > > > > Also agentIndexingVersion=4 in baloorc gives a hint to version 4? > > > > > > > > No, it is some internal protocol version. > > > > > > > > > Proceedings are of course: > > > > > stop akonadi and baloo, remove search_db, changed baloorc > > > > > initialIndexingDone=false and reboot. > > > > > The hell: No change. > > > > > > > > > > And yes, with 4.14 it worked with minor flaws on display. > > > > > > > > > > There is also more old stuff of kde around, also parts of 15.x > > > > > But I need at least okular. > > > > > > > > So, you are on Sid/unstable ? > > > > And you did > > > > apt-get update && apt-get dist-upgrade before ? > > > > > > Yes, I came from stretch, and honestly I used aptitude dist-upgrade. > > > apt-get dist-upgrade does not want apply any changes right now > > > > > > > okular never stopped working here and I use it quite often. > > > > > > > > $ dpkg -l '*okular*' > > > > ii libokularcore6 4:15.08.3-1 amd64 > > > > libraries for the Okular document viewer > > > > ii libokularcore7 4:16.04.2-1 amd64 > > > > libraries for the Okular document viewer > > > > ii okular 4:16.04.2-1 amd64 > > > > universal document viewer > > > > ii okular-extra-backends 4:16.04.2-1 amd64 > > > > additional document format support for Okular > > > > > > > > But I guess libokularcore6 is orphaned and could be purged. > > > > > > Sorry misleading you. > > > I checked most of my installed kde packages to be on 16.04 > > > and started to throw away everything older. > > > I of course installed the needed packages again. > > > By this: For me okular is working without libokularcore7. > > > > okular 16.04.2-1 has a dependency: libokularcore7 (= 4:16.04.2-1) > > You can see this via > > $ apt-cache show okular > > > > > Both baloo and akonadi are not working as expected: > > > On baloo when I try to index file contents it hangs indefinitely > > > and I cannot find any open file handler within baloo_indexer or > > > baloo_file_extractor hinting to a file causing this. > > > BTW: with dolphin4 I can search (and find) the content of files! > > > > baloo does file indexing, akonadi does email indexing (and some more). > > I think I understand the basic purpose, but I miss tools and/or instructions > to track down errors from a user perspective. > Which (config) files to check / remove, access akonadi from command line, > check caching stuff, databases? Then it would be possible to ask more > precise for assistance. Exaggregated I can only say: Search does not work. And I have to say: Yes, you are right :-( I am back in the office with that machine where I thought searching now works, the machine that this discussion was about ... Now... - searching in a specific folder give
Re: [KDEPIM Kmail] Wrongly displayed message
Hi,
to better understand what's happening, you can try to:
1- View the message structure ("Visualizza -> Mostra la struttura del
messaggio" in Italian or something like "View -> Message structure" in the
default English menus). This should show you whether there are other parts of
the message that you are not seeing (and allow you to select and see them).
2- If that does not work, you can view the message source ("Visualizza ->
Mostra sorgente" in Italian or something like "View -> Show source" in
English). This should also allow you to see if the message contains something
else that you are not able to see in the default view.
Hope that helps!
Mario
P.S: I apologize for non-Italian speakers, but I don't know the exact names of
the above options in the standard English menus.
In data venerdì 29 luglio 2016 00:39:20 CEST, Valerio Passini ha scritto:
> On giovedì 28 luglio 2016 11:33:29 CEST Martin Steigerwald wrote:
> > Am Donnerstag, 28. Juli 2016, 10:58:03 CEST schrieb Valerio Passini:
> > > Today I've discovered that some messages from Amazon where not shown, I
> > > mean: there was the subject, the sender, but no message inside. The
> > > message
> > > looks like HTML stuff to me, but other messages of this kind are visible
> > > simply by clicking on "enable html" string. The only hint I've is on the
> > > left side of the message and it says "No html message", while the
> > > working
> > > messages reports either "HTML message" or "Plain message". When
> > > replying,
> > > at least the text part of the invisible message is embedded in, what's
> > > wrong then?
> >
> > The HTML stuff may be in another part of the message that you can select
> > and then view the HTML.
>
> Here is how it's displayed: just a white page.
>
> Valerio
Re: KDEPIM ready to be more broadly tested
Am Donnerstag, 28. Juli 2016, 21:26:03 CEST schrieb Tim Rühsen: > On Donnerstag, 28. Juli 2016 17:27:25 CEST Volker Groll wrote: > > Am Donnerstag, 28. Juli 2016, 16:54:43 CEST schrieb Tim Ruehsen: > > > On Thursday, July 28, 2016 4:35:12 PM CEST Volker Groll wrote: > > > > Hello Tim, > > > > > > > > Am Donnerstag, 28. Juli 2016, 14:06:14 CEST schrieb Tim Ruehsen: > > > > > On Thursday, July 28, 2016 1:46:55 PM CEST Volker Groll wrote: > > > > > > Hi everybody, > > > > > > > > > > > > I followed Tim's journey through akonadi the last days and > > > > > > reproduced > > > > > > the steps here with no success. Last night I removed (hopefully) > > > > > > all > > > > > > stuff > > > > > > from .config, .local, .kde which seems to me connected to baloo or > > > > > > akonadi > > > > > > or any parts of kontact modules. > > > > > > Then I recreated every mail stuff again => no success, the normal > > > > > > search > > > > > > above the mai list is working, akonadi search gives either nothing > > > > > > or > > > > > > stupid results not connected to the search. > > > > > > > > > > > > I also throwed 4:4.14 packages with help of deborphan out of my > > > > > > system > > > > > > but especially libakonadi stuff is at 4:4.14.10-5? > > > > > > > > > > Here we talked about Sid/unstable having 16.04.x. > > > > > > > > > > $ dpkg -l|egrep 'akonadi|baloo|kdepim' > > > > > > > > > > I can't say anything about the 4.14. stuff except that it was > > > > > working > > > > > before I went to 16.04. > > > > > > > > > > Regards, Tim > > > > > > > > Thanks for your answer. > > > > > > > > I removed now all 4.14 stuff related to akondi|baloo|kdepim. > > > > Both digikam and kde-utils (and kde-full!) pulled the old stuff, while > > > > installing libakonadi-kf5 won't complain, so I thought it is ok. > > > > Now all akonadi stuff is 4:16.04.x or 16.04.x. > > > > BTW: what means the leading '4'? > > > > > > No idea. > > > > > > > Also agentIndexingVersion=4 in baloorc gives a hint to version 4? > > > > > > No, it is some internal protocol version. > > > > > > > Proceedings are of course: > > > > stop akonadi and baloo, remove search_db, changed baloorc > > > > initialIndexingDone=false and reboot. > > > > The hell: No change. > > > > > > > > And yes, with 4.14 it worked with minor flaws on display. > > > > > > > > There is also more old stuff of kde around, also parts of 15.x > > > > But I need at least okular. > > > > > > So, you are on Sid/unstable ? > > > And you did > > > apt-get update && apt-get dist-upgrade before ? > > > > Yes, I came from stretch, and honestly I used aptitude dist-upgrade. > > apt-get dist-upgrade does not want apply any changes right now > > > > > okular never stopped working here and I use it quite often. > > > > > > $ dpkg -l '*okular*' > > > ii libokularcore6 4:15.08.3-1 amd64 > > > libraries for the Okular document viewer > > > ii libokularcore7 4:16.04.2-1 amd64 > > > libraries for the Okular document viewer > > > ii okular 4:16.04.2-1 amd64 > > > universal document viewer > > > ii okular-extra-backends 4:16.04.2-1 amd64 > > > additional document format support for Okular > > > > > > But I guess libokularcore6 is orphaned and could be purged. > > > > Sorry misleading you. > > I checked most of my installed kde packages to be on 16.04 > > and started to throw away everything older. > > I of course installed the needed packages again. > > By this: For me okular is working without libokularcore7. > > okular 16.04.2-1 has a dependency: libokularcore7 (= 4:16.04.2-1) > You can see this via > $ apt-cache show okular > > > Both baloo and akonadi are not working as expected: > > On baloo when I try to index file contents it hangs indefinitely > > and I cannot find any open file handler within baloo_indexer or > > baloo_file_extractor hinting to a file causing this. > > BTW: with dolphin4 I can search (and find) the content of files! > > baloo does file indexing, akonadi does email indexing (and some more). I think I understand the basic purpose, but I miss tools and/or instructions to track down errors from a user perspective. Which (config) files to check / remove, access akonadi from command line, check caching stuff, databases? Then it would be possible to ask more precise for assistance. Exaggregated I can only say: Search does not work.
