Re: KDEPIM ready to be more broadly tested
Hey, > I don´t know whats up with your system, but my system shows this: mmh interessting - but the search works forme fine ( i actually use the search quite often) Maybe I switched before the filepath was moved and it is saved somewhere. But with ps and ls we see the correct files for sure :D > > to enable debuging output for akonadi search use kdebugsettings. > > @martin kdebugdialog/ kdebugdialog5 are not more useful anymore for > > kdepim, > > because it has switched logging to qt logging categories. > > Thanks, I didn´t know this. Any other tool to use instead? Nearly all KF5 using qt logging categories fromthe kde applications i don't know. But qt logging categories are standard qt, so application will move to use it. Regards, sandro signature.asc Description: This is a digitally signed message part.
Re: KDEPIM ready to be more broadly tested
Am Dienstag, 26. Juli 2016, 19:13:40 CEST schrieb Sandro Knauß: > Hi, > > [snip] > > > Does this also happen when you remove ~/.local/share/akonadi/search_db? > > Move it out of the way and also have "initialIndexingDone=false" false > > set and then restart. > > wait my systems tells me that the files are still under > ~/.local/share/baloo/ contacts etc. > > % ps aux | grep akonadi_in > % ls -lsa /proc//fd I don´t know whats up with your system, but my system shows this: martin@merkaba:~> ls -l /proc/4329/fd | cut -c44- | grep .DB 13 -> /home/martin/.local/share/akonadi/search_db/email/record.DB 14 -> /home/martin/.local/share/akonadi/search_db/email/termlist.DB 15 -> /home/martin/.local/share/akonadi/search_db/email/postlist.DB 17 -> /home/martin/.local/share/akonadi/search_db/emailContacts/record.DB 18 -> /home/martin/.local/share/akonadi/search_db/emailContacts/termlist.DB 19 -> /home/martin/.local/share/akonadi/search_db/emailContacts/position.DB 20 -> /home/martin/.local/share/akonadi/search_db/emailContacts/postlist.DB 22 -> /home/martin/.local/share/akonadi/search_db/contacts/record.DB 23 -> /home/martin/.local/share/akonadi/search_db/contacts/termlist.DB 24 -> /home/martin/.local/share/akonadi/search_db/contacts/position.DB 25 -> /home/martin/.local/share/akonadi/search_db/contacts/postlist.DB 27 -> /home/martin/.local/share/akonadi/search_db/notes/record.DB 28 -> /home/martin/.local/share/akonadi/search_db/notes/termlist.DB 29 -> /home/martin/.local/share/akonadi/search_db/notes/postlist.DB 31 -> /home/martin/.local/share/akonadi/search_db/calendars/record.DB 32 -> /home/martin/.local/share/akonadi/search_db/calendars/termlist.DB 33 -> /home/martin/.local/share/akonadi/search_db/calendars/position.DB 34 -> /home/martin/.local/share/akonadi/search_db/calendars/postlist.DB 36 -> /home/martin/.local/share/akonadi/search_db/collections/record.DB 37 -> /home/martin/.local/share/akonadi/search_db/collections/termlist.DB 38 -> /home/martin/.local/share/akonadi/search_db/collections/position.DB 39 -> /home/martin/.local/share/akonadi/search_db/collections/postlist.DB > to enable debuging output for akonadi search use kdebugsettings. > @martin kdebugdialog/ kdebugdialog5 are not more useful anymore for kdepim, > because it has switched logging to qt logging categories. Thanks, I didn´t know this. Any other tool to use instead? Thanks, -- Martin
Re: KDEPIM ready to be more broadly tested
Hi, [snip] > Does this also happen when you remove ~/.local/share/akonadi/search_db? Move > it out of the way and also have "initialIndexingDone=false" false set and > then restart. wait my systems tells me that the files are still under ~/.local/share/baloo/ contacts etc. % ps aux | grep akonadi_in % ls -lsa /proc//fd > If that doesn´t work, I think I don´t have any idea anymore. Escept than to > watch ~/.xsession-errors, with relevant stuff in kdebugdialog dialog > enabled. Well we can first test the xapian db itself. You need xapian-tools installed: % delve ~/.local/share/baloo/email UUID = blablabla number of documents = 40123456 average document length = 1900.00 document length lower bound = 3 document length upper bound = 600 highest document id ever used = 705000 has positional information = false %xapian-cheeck ~/.local/share/baloo/email and you can ask the terms for a giving element in akonadi by: % delve ~/.local/share/baloo/email -r 297603 [see a list of all terms for this item] to enable debuging output for akonadi search use kdebugsettings. @martin kdebugdialog/ kdebugdialog5 are not more useful anymore for kdepim, because it has switched logging to qt logging categories. Regards, sandro signature.asc Description: This is a digitally signed message part.
Re: KDEPIM ready to be more broadly tested
Am Dienstag, 26. Juli 2016, 17:06:37 CEST schrieb Tim Ruehsen: > On Tuesday, July 26, 2016 4:51:14 PM CEST Tim Ruehsen wrote: > > On Tuesday, July 26, 2016 12:09:24 AM CEST Martin Steigerwald wrote: > > > Hi Tim, > > > > > > Am Montag, 25. Juli 2016, 22:10:36 CEST schrieb Tim Rühsen: > > > > On Montag, 25. Juli 2016 17:24:45 CEST Sandro Knauß wrote: > > > > > > It shows up with green Button and "Ready". > > > > > > > > > > did you tried to restart akonadi? akonadictl restart? Because only > > > > > with > > > > > that akonadi will recognize new agents etc. > > > > > > > > I even rebooted without effect. > > > > And I see absolutely the same issues at a different (much newer) Sid > > > > installation. Find Messages just doesn't work. The *akonadisearch* > > > > packets > > > > were also missing - I manually installed here as well. > > > > > > I think you need to tweak this one: > > > > > > martin@merkaba:~/.config> cat baloorc > > > [Akonadi] > > > aborted=false > > > agentIndexingVersion=4 > > > dirtyCollections= > > > initialIndexingDone=true > > > > > > I´d even just remove it, so it redos the initial indexing, cause if it > > > has > > > "initialIndexingDone=true" in it, it won´t index the whole collections > > > anymore. I bet it may have this in it from KDE SC 4 times… after > > > migration > > > of configuration, but I am not sure. > > > > > > It stores the index data it stores in ~/.local/share/akonadi/search_db – > > > this directory totals to 2 GiB on my system. In case that Xapian > > > database > > > is corrupted somehow, it may crash. So for a clean start, it may make > > > sense > > > to remove that directory as well. > > > > I removed package 'baloo-utils', stopped KMail, stopped akonadi, removed > > ~/.config/baloorc and removed ~/.local/share/akonadi/search_db. Than I > > rebooted. > > > > After reboot I started KMail and waited a few minutes... than > > > > $ cat ~/.config/baloorc > > [Akonadi] > > agentIndexingVersion=4 > > dirtyCollections= > > initialIndexingDone=true > > > > $ l ~/.local/share/akonadi/search_db > > total 32 > > drwxr-xr-x 8 oms users 4096 26-07-16 16:38:48 . > > drwxr-xr-x 8 oms users 4096 26-07-16 16:38:48 .. > > drwxr-xr-x 2 oms users 4096 26-07-16 16:38:48 calendars > > drwxr-xr-x 2 oms users 4096 26-07-16 16:40:00 collections > > drwxr-xr-x 2 oms users 4096 26-07-16 16:38:48 contacts > > drwxr-xr-x 2 oms users 4096 26-07-16 16:41:40 email > > drwxr-xr-x 2 oms users 4096 26-07-16 16:41:40 emailContacts > > drwxr-xr-x 2 oms users 4096 26-07-16 16:38:48 notes > > > > $ du ~/.local/share/akonadi/search_db > > 20 /usr/oms/.local/share/akonadi/search_db/calendars > > 20 /usr/oms/.local/share/akonadi/search_db/notes > > 312 /usr/oms/.local/share/akonadi/search_db/email > > 104 /usr/oms/.local/share/akonadi/search_db/emailContacts > > 20 /usr/oms/.local/share/akonadi/search_db/contacts > > 72 /usr/oms/.local/share/akonadi/search_db/collections > > 552 /usr/oms/.local/share/akonadi/search_db > > > > Tools/Find Messages in KMail still not working. > > > > $ ps -ef|grep akonadi > > oms 6056 1 0 16:38 ?00:00:00 /usr/bin/akonadi_control > > oms 6063 6056 0 16:38 ?00:00:00 akonadiserver > > oms 6067 6063 0 16:38 ?00:00:01 /usr/sbin/mysqld > > --defaults-file=/usr/oms/.local/share/akonadi/mysql.conf > > --datadir=/usr/oms/.local/share/akonadi/db_data/ > > --socket=/tmp/akonadi-oms.hwHVDb/mysql.socket oms 6119 6056 0 > > 16:38 > > ?00:00:00 /usr/bin/akonadi_akonotes_resource --identifier > > akonadi_akonotes_resource_0 oms 6120 6056 0 16:38 ? > > 00:00:00 > > /usr/bin/akonadi_akonotes_resource --identifier > > akonadi_akonotes_resource_1 > > oms 6121 6056 0 16:38 ?00:00:00 > > /usr/bin/akonadi_archivemail_agent --identifier akonadi_archivemail_agent > > oms 6122 6056 0 16:38 ?00:00:00 > > /usr/bin/akonadi_contacts_resource --identifier > > akonadi_contacts_resource_0 > > oms 6123 6056 0 16:38 ?00:00:00 > > /usr/bin/akonadi_followupreminder_agent --identifier > > akonadi_followupreminder_agent oms 6124 6056 0 16:38 ? > > 00:00:00 /usr/bin/akonadi_ical_resource --identifier > > akonadi_ical_resource_0 oms 6125 6056 0 16:38 ?00:00:00 > > /usr/bin/akonadi_ical_resource --identifier akonadi_ical_resource_1 oms > > > > 6128 6056 0 16:38 ?00:00:00 /usr/bin/akonadi_ical_resource > > > > --identifier akonadi_ical_resource_2 oms 6129 6056 0 16:38 ? > > 00:00:00 /usr/bin/akonadi_imap_resource --identifier > > akonadi_imap_resource_1 oms 6131 6056 0 16:38 ?00:00:00 > > /usr/bin/akonadi_indexing_agent --identifier akonadi_indexing_agent oms > > > > 6133 6056 0 16:38 ?00:00:00 /usr/bin/akonadi_maildir_resource > > > > --identifier akonadi_maildir_resource_1 oms 6137 6056 0 16:38 ? > > > >00:00:00 /usr/bin/akonadi_maildispatcher_agent
Am I wrong understanding akonadi won't go to testing?
Hi, I understand there: https://qa.debian.org/excuses.php?package=akonadi the only excuse remaining for akonadi to move to testing is: https://release.debian.org/testing/freeze_policy.html And I see no reason why this excuse should be removed, I don't see it would fit in "Changes which can be considered". Or am I mistaken there? Chris
Re: KDEPIM ready to be more broadly tested
On Tuesday, July 26, 2016 4:51:14 PM CEST Tim Ruehsen wrote: > On Tuesday, July 26, 2016 12:09:24 AM CEST Martin Steigerwald wrote: > > Hi Tim, > > > > Am Montag, 25. Juli 2016, 22:10:36 CEST schrieb Tim Rühsen: > > > On Montag, 25. Juli 2016 17:24:45 CEST Sandro Knauß wrote: > > > > > It shows up with green Button and "Ready". > > > > > > > > did you tried to restart akonadi? akonadictl restart? Because only > > > > with > > > > that akonadi will recognize new agents etc. > > > > > > I even rebooted without effect. > > > And I see absolutely the same issues at a different (much newer) Sid > > > installation. Find Messages just doesn't work. The *akonadisearch* > > > packets > > > were also missing - I manually installed here as well. > > > > I think you need to tweak this one: > > > > martin@merkaba:~/.config> cat baloorc > > [Akonadi] > > aborted=false > > agentIndexingVersion=4 > > dirtyCollections= > > initialIndexingDone=true > > > > I´d even just remove it, so it redos the initial indexing, cause if it has > > "initialIndexingDone=true" in it, it won´t index the whole collections > > anymore. I bet it may have this in it from KDE SC 4 times… after migration > > of configuration, but I am not sure. > > > > It stores the index data it stores in ~/.local/share/akonadi/search_db – > > this directory totals to 2 GiB on my system. In case that Xapian database > > is corrupted somehow, it may crash. So for a clean start, it may make > > sense > > to remove that directory as well. > > I removed package 'baloo-utils', stopped KMail, stopped akonadi, removed > ~/.config/baloorc and removed ~/.local/share/akonadi/search_db. Than I > rebooted. > > After reboot I started KMail and waited a few minutes... than > > $ cat ~/.config/baloorc > [Akonadi] > agentIndexingVersion=4 > dirtyCollections= > initialIndexingDone=true > > $ l ~/.local/share/akonadi/search_db > total 32 > drwxr-xr-x 8 oms users 4096 26-07-16 16:38:48 . > drwxr-xr-x 8 oms users 4096 26-07-16 16:38:48 .. > drwxr-xr-x 2 oms users 4096 26-07-16 16:38:48 calendars > drwxr-xr-x 2 oms users 4096 26-07-16 16:40:00 collections > drwxr-xr-x 2 oms users 4096 26-07-16 16:38:48 contacts > drwxr-xr-x 2 oms users 4096 26-07-16 16:41:40 email > drwxr-xr-x 2 oms users 4096 26-07-16 16:41:40 emailContacts > drwxr-xr-x 2 oms users 4096 26-07-16 16:38:48 notes > > $ du ~/.local/share/akonadi/search_db > 20 /usr/oms/.local/share/akonadi/search_db/calendars > 20 /usr/oms/.local/share/akonadi/search_db/notes > 312 /usr/oms/.local/share/akonadi/search_db/email > 104 /usr/oms/.local/share/akonadi/search_db/emailContacts > 20 /usr/oms/.local/share/akonadi/search_db/contacts > 72 /usr/oms/.local/share/akonadi/search_db/collections > 552 /usr/oms/.local/share/akonadi/search_db > > Tools/Find Messages in KMail still not working. > > $ ps -ef|grep akonadi > oms 6056 1 0 16:38 ?00:00:00 /usr/bin/akonadi_control > oms 6063 6056 0 16:38 ?00:00:00 akonadiserver > oms 6067 6063 0 16:38 ?00:00:01 /usr/sbin/mysqld > --defaults-file=/usr/oms/.local/share/akonadi/mysql.conf > --datadir=/usr/oms/.local/share/akonadi/db_data/ > --socket=/tmp/akonadi-oms.hwHVDb/mysql.socket oms 6119 6056 0 16:38 > ?00:00:00 /usr/bin/akonadi_akonotes_resource --identifier > akonadi_akonotes_resource_0 oms 6120 6056 0 16:38 ?00:00:00 > /usr/bin/akonadi_akonotes_resource --identifier akonadi_akonotes_resource_1 > oms 6121 6056 0 16:38 ?00:00:00 > /usr/bin/akonadi_archivemail_agent --identifier akonadi_archivemail_agent > oms 6122 6056 0 16:38 ?00:00:00 > /usr/bin/akonadi_contacts_resource --identifier akonadi_contacts_resource_0 > oms 6123 6056 0 16:38 ?00:00:00 > /usr/bin/akonadi_followupreminder_agent --identifier > akonadi_followupreminder_agent oms 6124 6056 0 16:38 ? > 00:00:00 /usr/bin/akonadi_ical_resource --identifier > akonadi_ical_resource_0 oms 6125 6056 0 16:38 ?00:00:00 > /usr/bin/akonadi_ical_resource --identifier akonadi_ical_resource_1 oms > 6128 6056 0 16:38 ?00:00:00 /usr/bin/akonadi_ical_resource > --identifier akonadi_ical_resource_2 oms 6129 6056 0 16:38 ? > 00:00:00 /usr/bin/akonadi_imap_resource --identifier > akonadi_imap_resource_1 oms 6131 6056 0 16:38 ?00:00:00 > /usr/bin/akonadi_indexing_agent --identifier akonadi_indexing_agent oms > 6133 6056 0 16:38 ?00:00:00 /usr/bin/akonadi_maildir_resource > --identifier akonadi_maildir_resource_1 oms 6137 6056 0 16:38 ? >00:00:00 /usr/bin/akonadi_maildispatcher_agent --identifier > akonadi_maildispatcher_agent oms 6141 6056 0 16:38 ? > 00:00:00 /usr/bin/akonadi_mailfilter_agent --identifier > akonadi_mailfilter_agent oms 6143 6056 0 16:38 ?00:00:00 > /usr/bin/akonadi_migration_agent --identifier akonadi_migration_agent oms >
Re: KDEPIM ready to be more broadly tested
On Tuesday, July 26, 2016 12:09:24 AM CEST Martin Steigerwald wrote: > Hi Tim, > > Am Montag, 25. Juli 2016, 22:10:36 CEST schrieb Tim Rühsen: > > On Montag, 25. Juli 2016 17:24:45 CEST Sandro Knauß wrote: > > > > It shows up with green Button and "Ready". > > > > > > did you tried to restart akonadi? akonadictl restart? Because only with > > > that akonadi will recognize new agents etc. > > > > I even rebooted without effect. > > And I see absolutely the same issues at a different (much newer) Sid > > installation. Find Messages just doesn't work. The *akonadisearch* packets > > were also missing - I manually installed here as well. > > I think you need to tweak this one: > > martin@merkaba:~/.config> cat baloorc > [Akonadi] > aborted=false > agentIndexingVersion=4 > dirtyCollections= > initialIndexingDone=true > > I´d even just remove it, so it redos the initial indexing, cause if it has > "initialIndexingDone=true" in it, it won´t index the whole collections > anymore. I bet it may have this in it from KDE SC 4 times… after migration > of configuration, but I am not sure. > > It stores the index data it stores in ~/.local/share/akonadi/search_db – > this directory totals to 2 GiB on my system. In case that Xapian database > is corrupted somehow, it may crash. So for a clean start, it may make sense > to remove that directory as well. I removed package 'baloo-utils', stopped KMail, stopped akonadi, removed ~/.config/baloorc and removed ~/.local/share/akonadi/search_db. Than I rebooted. After reboot I started KMail and waited a few minutes... than $ cat ~/.config/baloorc [Akonadi] agentIndexingVersion=4 dirtyCollections= initialIndexingDone=true $ l ~/.local/share/akonadi/search_db total 32 drwxr-xr-x 8 oms users 4096 26-07-16 16:38:48 . drwxr-xr-x 8 oms users 4096 26-07-16 16:38:48 .. drwxr-xr-x 2 oms users 4096 26-07-16 16:38:48 calendars drwxr-xr-x 2 oms users 4096 26-07-16 16:40:00 collections drwxr-xr-x 2 oms users 4096 26-07-16 16:38:48 contacts drwxr-xr-x 2 oms users 4096 26-07-16 16:41:40 email drwxr-xr-x 2 oms users 4096 26-07-16 16:41:40 emailContacts drwxr-xr-x 2 oms users 4096 26-07-16 16:38:48 notes $ du ~/.local/share/akonadi/search_db 20 /usr/oms/.local/share/akonadi/search_db/calendars 20 /usr/oms/.local/share/akonadi/search_db/notes 312 /usr/oms/.local/share/akonadi/search_db/email 104 /usr/oms/.local/share/akonadi/search_db/emailContacts 20 /usr/oms/.local/share/akonadi/search_db/contacts 72 /usr/oms/.local/share/akonadi/search_db/collections 552 /usr/oms/.local/share/akonadi/search_db Tools/Find Messages in KMail still not working. $ ps -ef|grep akonadi oms 6056 1 0 16:38 ?00:00:00 /usr/bin/akonadi_control oms 6063 6056 0 16:38 ?00:00:00 akonadiserver oms 6067 6063 0 16:38 ?00:00:01 /usr/sbin/mysqld --defaults-file=/usr/oms/.local/share/akonadi/mysql.conf --datadir=/usr/oms/.local/share/akonadi/db_data/ --socket=/tmp/akonadi-oms.hwHVDb/mysql.socket oms 6119 6056 0 16:38 ?00:00:00 /usr/bin/akonadi_akonotes_resource --identifier akonadi_akonotes_resource_0 oms 6120 6056 0 16:38 ?00:00:00 /usr/bin/akonadi_akonotes_resource --identifier akonadi_akonotes_resource_1 oms 6121 6056 0 16:38 ?00:00:00 /usr/bin/akonadi_archivemail_agent --identifier akonadi_archivemail_agent oms 6122 6056 0 16:38 ?00:00:00 /usr/bin/akonadi_contacts_resource --identifier akonadi_contacts_resource_0 oms 6123 6056 0 16:38 ?00:00:00 /usr/bin/akonadi_followupreminder_agent --identifier akonadi_followupreminder_agent oms 6124 6056 0 16:38 ?00:00:00 /usr/bin/akonadi_ical_resource --identifier akonadi_ical_resource_0 oms 6125 6056 0 16:38 ?00:00:00 /usr/bin/akonadi_ical_resource --identifier akonadi_ical_resource_1 oms 6128 6056 0 16:38 ?00:00:00 /usr/bin/akonadi_ical_resource --identifier akonadi_ical_resource_2 oms 6129 6056 0 16:38 ?00:00:00 /usr/bin/akonadi_imap_resource --identifier akonadi_imap_resource_1 oms 6131 6056 0 16:38 ?00:00:00 /usr/bin/akonadi_indexing_agent --identifier akonadi_indexing_agent oms 6133 6056 0 16:38 ?00:00:00 /usr/bin/akonadi_maildir_resource --identifier akonadi_maildir_resource_1 oms 6137 6056 0 16:38 ?00:00:00 /usr/bin/akonadi_maildispatcher_agent --identifier akonadi_maildispatcher_agent oms 6141 6056 0 16:38 ?00:00:00 /usr/bin/akonadi_mailfilter_agent --identifier akonadi_mailfilter_agent oms 6143 6056 0 16:38 ?00:00:00 /usr/bin/akonadi_migration_agent --identifier akonadi_migration_agent oms 6145 6056 0 16:38 ?00:00:00 /usr/bin/akonadi_mixedmaildir_resource --identifier akonadi_mixedmaildir_resource_0 oms 6147 6056 0 16:38 ?00:00:00 /usr/bin/akonadi_newmailnotifier_agent --identifier akonadi_newmailnotifier_agent om
Re: Akonadi indexing (was: Re: KDEPIM ready to be more broadly tested)
Am Dienstag, 26. Juli 2016, 13:14:14 CEST schrieb Tim Ruehsen: > On Tuesday, July 26, 2016 12:49:20 PM CEST Martin Steigerwald wrote: > > please no cc > > Please anyone use cc for me :-) > > Hi Martin, > > thanks for your extended answer though you are handicapped right now. > I wish you the best and a fast healing ! Thanks. Getting better every hour. > > Am Dienstag, 26. Juli 2016, 10:13:23 CEST schrieb Tim Ruehsen: > > > On Tuesday, July 26, 2016 12:09:24 AM CEST Martin Steigerwald wrote: > > […] > > > > > > It stores the index data it stores in ~/.local/share/akonadi/search_db > > > > – > > > > this directory totals to 2 GiB on my system. In case that Xapian > > > > database > > > > is corrupted somehow, it may crash. So for a clean start, it may make > > > > sense > > > > to remove that directory as well. > > > > > > This directory contained three subdirs and there was not much data (< > > > 1MB). > > > > > > > And well when I say remove, I rather suggest you move it out of the > > > > way, > > > > instead of removing it immediately. > > > > > > Removed both and restarted KDE (logout / login). > > > > > > Now I get crashes > > > Application: No such method 'agentName' in interface > > > 'org.freedesktop.Akonadi.AgentManager' at object path '/AgentManager' > > > (signature 'ss') (akonadi_baloo_indexer), signal: Aborted > > > > > > akonadi_baloo_indexer(13140)/libakonadi: Unable to register service > > > > AFAIK thats the old KDE SC 4 based indexer, which should not be running at > > all. > > Ohh. Ahh. Uhh. Ding dong. > > > martin@merkaba:~> ps aux | grep "[b]aloo" > > martin4104 0.0 1.8 5856360 298408 ? SNl Jul25 0:24 /usr/bin/ > > baloo_file > > > > That is file based desktop search > > > > martin@merkaba:~> ps aux | grep "[i]ndexing" > > martin4329 0.0 0.6 753312 104188 ? SNl Jul25 0:33 /usr/bin/ > > akonadi_indexing_agent --identifier akonadi_indexing_agent > > > > This is Akonadi indexing. > > > > I am not even sure how you can still have installed Akonadi baloo indexer > > when using Qt 5 based Akonadi and to my knowledge meanwhile if you have > > new > > qt5/kf5 based kdepim you will also have Qt5 based Akonadi. Maybe there is > > a > > breaks/ replaces missing. > > When I first run into the half-way update to 16.04, I had to forcefully > download/install packages from experimental. I definitely broke things but I > thought it was cleaned up by now. I still have package 'baloo-utils' > installed which contains akonadi_baloo_indexer. > > $ apt-file search akonadi_baloo_indexer > baloo-utils: /usr/bin/akonadi_baloo_indexer > > > I suggest the following: > > > > 1) report a bug with reportbug againsd akonadi-server or so, can still be > > reassigned. Give all necessary details including dpkg -l | egrep "akonadi| > > kdepim" | cut -c-72 > > > > Please also provide this output here to this list. > > First I check the dependencies with apt-cache show. Onyl if these aren't > correct, I'll file a bug. I saw your bug report. I suggest adding the backtrace that mentioned akonadi_baloo_indexer to the bug report. You can simply do that by mailing it to bugnum...@bugs.debian.org. > > 2) make sure akonadi_baloo_indexer is gone for good. something like > > > > apt purge $(which akonadi_baloo_indexer) > > > > 3) Move Akonadi indexing agent config + search_db out of the way once > > again > > and reboot. > > I'll do that after lunch (and after checking above) and report back. Great. Thanks, -- Martin signature.asc Description: This is a digitally signed message part.
Re: Akonadi indexing (was: Re: KDEPIM ready to be more broadly tested)
On Tuesday, July 26, 2016 12:49:20 PM CEST Martin Steigerwald wrote: > please no cc Please anyone use cc for me :-) Hi Martin, thanks for your extended answer though you are handicapped right now. I wish you the best and a fast healing ! > Am Dienstag, 26. Juli 2016, 10:13:23 CEST schrieb Tim Ruehsen: > > On Tuesday, July 26, 2016 12:09:24 AM CEST Martin Steigerwald wrote: > […] > > > > It stores the index data it stores in ~/.local/share/akonadi/search_db – > > > this directory totals to 2 GiB on my system. In case that Xapian > > > database > > > is corrupted somehow, it may crash. So for a clean start, it may make > > > sense > > > to remove that directory as well. > > > > This directory contained three subdirs and there was not much data (< > > 1MB). > > > > > And well when I say remove, I rather suggest you move it out of the way, > > > instead of removing it immediately. > > > > Removed both and restarted KDE (logout / login). > > > > Now I get crashes > > Application: No such method 'agentName' in interface > > 'org.freedesktop.Akonadi.AgentManager' at object path '/AgentManager' > > (signature 'ss') (akonadi_baloo_indexer), signal: Aborted > > > > akonadi_baloo_indexer(13140)/libakonadi: Unable to register service > > AFAIK thats the old KDE SC 4 based indexer, which should not be running at > all. Ohh. Ahh. Uhh. Ding dong. > martin@merkaba:~> ps aux | grep "[b]aloo" > martin4104 0.0 1.8 5856360 298408 ? SNl Jul25 0:24 /usr/bin/ > baloo_file > > That is file based desktop search > > martin@merkaba:~> ps aux | grep "[i]ndexing" > martin4329 0.0 0.6 753312 104188 ? SNl Jul25 0:33 /usr/bin/ > akonadi_indexing_agent --identifier akonadi_indexing_agent > > This is Akonadi indexing. > > I am not even sure how you can still have installed Akonadi baloo indexer > when using Qt 5 based Akonadi and to my knowledge meanwhile if you have new > qt5/kf5 based kdepim you will also have Qt5 based Akonadi. Maybe there is a > breaks/ replaces missing. When I first run into the half-way update to 16.04, I had to forcefully download/install packages from experimental. I definitely broke things but I thought it was cleaned up by now. I still have package 'baloo-utils' installed which contains akonadi_baloo_indexer. $ apt-file search akonadi_baloo_indexer baloo-utils: /usr/bin/akonadi_baloo_indexer > I suggest the following: > > 1) report a bug with reportbug againsd akonadi-server or so, can still be > reassigned. Give all necessary details including dpkg -l | egrep "akonadi| > kdepim" | cut -c-72 > > Please also provide this output here to this list. First I check the dependencies with apt-cache show. Onyl if these aren't correct, I'll file a bug. > 2) make sure akonadi_baloo_indexer is gone for good. something like > > apt purge $(which akonadi_baloo_indexer) > > 3) Move Akonadi indexing agent config + search_db out of the way once again > and reboot. I'll do that after lunch (and after checking above) and report back. signature.asc Description: This is a digitally signed message part.
Re: KDEPIM ready to be more broadly tested
Am Dienstag, 26. Juli 2016, 09:37:40 CEST schrieb Tim Ruehsen: > On Monday, July 25, 2016 10:55:45 PM CEST Diederik de Haas wrote: > > On maandag 25 juli 2016 22:08:23 CEST Tim Rühsen wrote: > > > BTW, I can't find such an option at all - maybe just for imap ? > > > > Probably. I almost exclusively use imap. > > > > > I really can't believe that this is a personal problem. I am just > > > sitting > > > at a much newer Sid installation and experience absolutely the same > > > problems. The question is: what did all of you do that I didn't ? And > > > are > > > you sure that indexing and "Tools/Find Messages" really work for you ? > > > > It's working fine here. I can go to a random mail, copy a word from it and > > put it in the search box and it'll find that mail again. > > Which database backend are you using for akonadi? > > It is the mysql backend. > In fact I see (output by akonadi) > Database "akonadi" opened using driver "QMYSQL" Folder search box does not only rely on Akonadi Indexing agent, AFAIK it also filters by subject. But for global kmail search + search folders basically work as well. Just removing a search folder can be an issue (crash). -- Martin
Re: Akonadi indexing (was: Re: KDEPIM ready to be more broadly tested)
Am Dienstag, 26. Juli 2016, 12:49:20 CEST schrieb Martin Steigerwald: > please no cc > > Am Dienstag, 26. Juli 2016, 10:13:23 CEST schrieb Tim Ruehsen: > > On Tuesday, July 26, 2016 12:09:24 AM CEST Martin Steigerwald wrote: > […] > > > > It stores the index data it stores in ~/.local/share/akonadi/search_db – > > > this directory totals to 2 GiB on my system. In case that Xapian > > > database > > > is corrupted somehow, it may crash. So for a clean start, it may make > > > sense > > > to remove that directory as well. > > > > This directory contained three subdirs and there was not much data (< > > 1MB). > > > > > And well when I say remove, I rather suggest you move it out of the way, > > > instead of removing it immediately. > > > > Removed both and restarted KDE (logout / login). > > > > Now I get crashes > > Application: No such method 'agentName' in interface > > 'org.freedesktop.Akonadi.AgentManager' at object path '/AgentManager' > > (signature 'ss') (akonadi_baloo_indexer), signal: Aborted > > > > akonadi_baloo_indexer(13140)/libakonadi: Unable to register service > > AFAIK thats the old KDE SC 4 based indexer, which should not be running at > all. > > martin@merkaba:~> ps aux | grep "[b]aloo" > martin4104 0.0 1.8 5856360 298408 ? SNl Jul25 0:24 /usr/bin/ > baloo_file > > That is file based desktop search > > martin@merkaba:~> ps aux | grep "[i]ndexing" > martin4329 0.0 0.6 753312 104188 ? SNl Jul25 0:33 /usr/bin/ > akonadi_indexing_agent --identifier akonadi_indexing_agent > > This is Akonadi indexing. > > I am not even sure how you can still have installed Akonadi baloo indexer > when using Qt 5 based Akonadi and to my knowledge meanwhile if you have new > qt5/kf5 based kdepim you will also have Qt5 based Akonadi. Maybe there is a > breaks/ replaces missing. > > I suggest the following: > > 1) report a bug with reportbug againsd akonadi-server or so, can still be > reassigned. Give all necessary details including dpkg -l | egrep "akonadi| > kdepim" | cut -c-72 > > Please also provide this output here to this list. > > 2) make sure akonadi_baloo_indexer is gone for good. something like > > apt purge $(which akonadi_baloo_indexer) > > 3) Move Akonadi indexing agent config + search_db out of the way once again > and reboot. > > But first please really contribute by making a bug report. > > > "org.freedesktop.Akonadi.Agent.akonadi_baloo_indexer" at dbus: "" > > Shutting down "0x1032bb0" ... > > KCrash: Application 'akonadi_baloo_indexer' crashing... > > KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi from kdeinit > > KCrash: Connect sock_file=/usr/oms/.kde/socket-blitz-lx/kdeinit4__0 > > Unable to start Dr. Konqi > > Not forwarding the crash to Apport. > > ProcessControl: Application '/usr/bin/akonadi_baloo_indexer' returned with > > exit code 255 (Unknown error) > > akonadi_baloo_indexer(13148)/libakonadi: Unable to register service > > "org.freedesktop.Akonadi.Agent.akonadi_baloo_indexer" at dbus: "" > > KCrash: Application 'akonadi_baloo_indexer' crashing... > > KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi from kdeinit > > Shutting down "0x1032bb0" ... > > KCrash: Connect sock_file=/usr/oms/.kde/socket-blitz-lx/kdeinit4__0 > > Unable to start Dr. Konqi > > Not forwarding the crash to Apport. > > ProcessControl: Application '/usr/bin/akonadi_baloo_indexer' returned with > > exit code 255 (Unknown error) > > akonadi_baloo_indexer(13156)/libakonadi: Unable to register service > > "org.freedesktop.Akonadi.Agent.akonadi_baloo_indexer" at dbus: "" > > KCrash: Application 'akonadi_baloo_indexer' crashing... > > KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi from kdeinit > > KCrash: Connect sock_file=/usr/oms/.kde/socket-blitz-lx/kdeinit4__0 > > > > > As Sandro told, it needs to be "akonadi_indexing_agent" being active. > > > Additionally to that: You can´t configure Akonadi Search with > > > Systemsettings, Systemsetting just configured the desktop file search. > > > Basically the mail and contact indexing part of Baloo has been split out > > > and is now Akonadi search. Almost unchanged, except for search database > > > location. > > > > Thanks, good to know. > > "akonadi_indexing_agent" can't be something complicated than... how can it > > crash at all (and I saw crash often in the past). I couldn't find any -dbg > > packages, so the backtrace is pretty worthless. > > It doesn´t crash. akonida_baloo_indexer crashes, not the indexing agent. > > > > There is a way in KMail to disable fulltext indexing for folders, but as > > > I > > > found out, Akonadi doesn´t respect that setting. > > > > > > I do think Akonadi Search doesn´t receive much love at the moment, and > > > it > > > shows. > > > > That renders KMail at least incomplete. It worked perfect for me until > > KDE4 > > came. From that point on it was getting worse and worse... If there was > > any > > easy way to convert all those emails from the last 15 ye
Re: KDEPIM ready to be more broadly tested
Am Mittwoch, 20. Juli 2016, 09:31:46 CEST schrieb Christian Hilberg: > Am Dienstag, 19. Juli 2016, 15:56:41 CEST schrieb Christian Hilberg: > > Am Dienstag 19 Juli 2016, 11:14:30 schrieb Christian Hilberg: > > > Am Dienstag 19 Juli 2016, 11:01:21 schrieb Christian Hilberg: > > > > [...] > > > > While syncing the IMAP folders, the process got stuck at 100% at one > > > > folder[...] Trying to resolve this now... > > > > [...] > > Well, allowed a second CPU core into my VM and the issue is gone... > That smells like timing/timeout issue. The missing feedback to the > user via the UI is already reported upstream, iirc. Christian, please consider researching, adding to or creating upstream bug report, then Debian bug report forwarding to it. -- Martin
Akonadi indexing (was: Re: KDEPIM ready to be more broadly tested)
please no cc Am Dienstag, 26. Juli 2016, 10:13:23 CEST schrieb Tim Ruehsen: > On Tuesday, July 26, 2016 12:09:24 AM CEST Martin Steigerwald wrote: […] > > It stores the index data it stores in ~/.local/share/akonadi/search_db – > > this directory totals to 2 GiB on my system. In case that Xapian database > > is corrupted somehow, it may crash. So for a clean start, it may make > > sense > > to remove that directory as well. > > This directory contained three subdirs and there was not much data (< 1MB). > > > And well when I say remove, I rather suggest you move it out of the way, > > instead of removing it immediately. > > Removed both and restarted KDE (logout / login). > > Now I get crashes > Application: No such method 'agentName' in interface > 'org.freedesktop.Akonadi.AgentManager' at object path '/AgentManager' > (signature 'ss') (akonadi_baloo_indexer), signal: Aborted > > akonadi_baloo_indexer(13140)/libakonadi: Unable to register service AFAIK thats the old KDE SC 4 based indexer, which should not be running at all. martin@merkaba:~> ps aux | grep "[b]aloo" martin4104 0.0 1.8 5856360 298408 ? SNl Jul25 0:24 /usr/bin/ baloo_file That is file based desktop search martin@merkaba:~> ps aux | grep "[i]ndexing" martin4329 0.0 0.6 753312 104188 ? SNl Jul25 0:33 /usr/bin/ akonadi_indexing_agent --identifier akonadi_indexing_agent This is Akonadi indexing. I am not even sure how you can still have installed Akonadi baloo indexer when using Qt 5 based Akonadi and to my knowledge meanwhile if you have new qt5/kf5 based kdepim you will also have Qt5 based Akonadi. Maybe there is a breaks/ replaces missing. I suggest the following: 1) report a bug with reportbug againsd akonadi-server or so, can still be reassigned. Give all necessary details including dpkg -l | egrep "akonadi| kdepim" | cut -c-72 Please also provide this output here to this list. 2) make sure akonadi_baloo_indexer is gone for good. something like apt purge $(which akonadi_baloo_indexer) 3) Move Akonadi indexing agent config + search_db out of the way once again and reboot. But first please really contribute by making a bug report. > "org.freedesktop.Akonadi.Agent.akonadi_baloo_indexer" at dbus: "" > Shutting down "0x1032bb0" ... > KCrash: Application 'akonadi_baloo_indexer' crashing... > KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi from kdeinit > KCrash: Connect sock_file=/usr/oms/.kde/socket-blitz-lx/kdeinit4__0 > Unable to start Dr. Konqi > Not forwarding the crash to Apport. > ProcessControl: Application '/usr/bin/akonadi_baloo_indexer' returned with > exit code 255 (Unknown error) > akonadi_baloo_indexer(13148)/libakonadi: Unable to register service > "org.freedesktop.Akonadi.Agent.akonadi_baloo_indexer" at dbus: "" > KCrash: Application 'akonadi_baloo_indexer' crashing... > KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi from kdeinit > Shutting down "0x1032bb0" ... > KCrash: Connect sock_file=/usr/oms/.kde/socket-blitz-lx/kdeinit4__0 > Unable to start Dr. Konqi > Not forwarding the crash to Apport. > ProcessControl: Application '/usr/bin/akonadi_baloo_indexer' returned with > exit code 255 (Unknown error) > akonadi_baloo_indexer(13156)/libakonadi: Unable to register service > "org.freedesktop.Akonadi.Agent.akonadi_baloo_indexer" at dbus: "" > KCrash: Application 'akonadi_baloo_indexer' crashing... > KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi from kdeinit > KCrash: Connect sock_file=/usr/oms/.kde/socket-blitz-lx/kdeinit4__0 > > > As Sandro told, it needs to be "akonadi_indexing_agent" being active. > > Additionally to that: You can´t configure Akonadi Search with > > Systemsettings, Systemsetting just configured the desktop file search. > > Basically the mail and contact indexing part of Baloo has been split out > > and is now Akonadi search. Almost unchanged, except for search database > > location. > > Thanks, good to know. > "akonadi_indexing_agent" can't be something complicated than... how can it > crash at all (and I saw crash often in the past). I couldn't find any -dbg > packages, so the backtrace is pretty worthless. It doesn´t crash. akonida_baloo_indexer crashes, not the indexing agent. > > There is a way in KMail to disable fulltext indexing for folders, but as I > > found out, Akonadi doesn´t respect that setting. > > > > I do think Akonadi Search doesn´t receive much love at the moment, and it > > shows. > > That renders KMail at least incomplete. It worked perfect for me until KDE4 > came. From that point on it was getting worse and worse... If there was any > easy way to convert all those emails from the last 15 years into a halfway > working mail client I would do that instead of wasting my time with unloved > and unsupported crap. But that is OT, and I am not giving up yet. Tim, I didn´t write that it doesn´t work at all. It basically works here. But its more rough than I think is good for an end user who wants to have it
Re: KDEPIM ready to be more broadly tested
On Tuesday, July 26, 2016 04:13:23 AM Tim Ruehsen wrote: > On Tuesday, July 26, 2016 12:09:24 AM CEST Martin Steigerwald wrote: > If there was any > easy way to convert all those emails from the last 15 years into a halfway > working mail client I would do that instead of wasting my time with unloved > and unsupported crap. But that is OT, and I am not giving up yet. I'm trying to remember--I guess you're using Imap and trying to store a local copy of your emails? I'm not sure about Imap, but if you were using mbox or maildir to store your emails, that's pretty standard across quite a few email clients (in other words, you could easily switch to some other email client and get access to old emails). I would think Imap would be similarly standardized?
Re: Kmail: "Save attachments" does not work
On Monday, July 25, 2016 5:22:08 PM CEST Sandro Knauß wrote: > Hey, > > no the sender client is wrong. > multipart/alternative is defined as the mail client should select ONLY one > part of the alternatives and ignore every other part, if one is selected. > See https://www.w3.org/Protocols/rfc1341/7_2_Multipart.html > > The corect type would be multipart/mixed Yes, that makes sense. > But unfortunatelly a mail client needs to work with broken senders, there > are already a lot of places with comments like "broken apple client" :D The > hard one here is to find a solution not to break the good clients, that > using multipart/alternative correctly. > > Can you create a upsteam bug for it and append the mail (and send me the > bugnumber)? Than I can have a deeper look and find a solution. I'm currently > reworking the messageviewer, so I'm deeply into the code... It would be much more time efficient to send a prepared mail to you. You decide to open a bug at KDE or just to fix it. I prepared a relatively small email that behaves like the original one. I send it to you via sendmail. Regards, Tim signature.asc Description: This is a digitally signed message part.
Re: KDEPIM ready to be more broadly tested
On Tuesday, July 26, 2016 12:09:24 AM CEST Martin Steigerwald wrote: > Hi Tim, > > Am Montag, 25. Juli 2016, 22:10:36 CEST schrieb Tim Rühsen: > > On Montag, 25. Juli 2016 17:24:45 CEST Sandro Knauß wrote: > > > > It shows up with green Button and "Ready". > > > > > > did you tried to restart akonadi? akonadictl restart? Because only with > > > that akonadi will recognize new agents etc. > > > > I even rebooted without effect. > > And I see absolutely the same issues at a different (much newer) Sid > > installation. Find Messages just doesn't work. The *akonadisearch* packets > > were also missing - I manually installed here as well. > > I think you need to tweak this one: > > martin@merkaba:~/.config> cat baloorc > [Akonadi] > aborted=false > agentIndexingVersion=4 > dirtyCollections= > initialIndexingDone=true > > > I´d even just remove it, so it redos the initial indexing, cause if it has > "initialIndexingDone=true" in it, it won´t index the whole collections > anymore. I bet it may have this in it from KDE SC 4 times… after migration > of configuration, but I am not sure. > > It stores the index data it stores in ~/.local/share/akonadi/search_db – > this directory totals to 2 GiB on my system. In case that Xapian database > is corrupted somehow, it may crash. So for a clean start, it may make sense > to remove that directory as well. This directory contained three subdirs and there was not much data (< 1MB). > And well when I say remove, I rather suggest you move it out of the way, > instead of removing it immediately. Removed both and restarted KDE (logout / login). Now I get crashes Application: No such method 'agentName' in interface 'org.freedesktop.Akonadi.AgentManager' at object path '/AgentManager' (signature 'ss') (akonadi_baloo_indexer), signal: Aborted akonadi_baloo_indexer(13140)/libakonadi: Unable to register service "org.freedesktop.Akonadi.Agent.akonadi_baloo_indexer" at dbus: "" Shutting down "0x1032bb0" ... KCrash: Application 'akonadi_baloo_indexer' crashing... KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi from kdeinit KCrash: Connect sock_file=/usr/oms/.kde/socket-blitz-lx/kdeinit4__0 Unable to start Dr. Konqi Not forwarding the crash to Apport. ProcessControl: Application '/usr/bin/akonadi_baloo_indexer' returned with exit code 255 (Unknown error) akonadi_baloo_indexer(13148)/libakonadi: Unable to register service "org.freedesktop.Akonadi.Agent.akonadi_baloo_indexer" at dbus: "" KCrash: Application 'akonadi_baloo_indexer' crashing... KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi from kdeinit Shutting down "0x1032bb0" ... KCrash: Connect sock_file=/usr/oms/.kde/socket-blitz-lx/kdeinit4__0 Unable to start Dr. Konqi Not forwarding the crash to Apport. ProcessControl: Application '/usr/bin/akonadi_baloo_indexer' returned with exit code 255 (Unknown error) akonadi_baloo_indexer(13156)/libakonadi: Unable to register service "org.freedesktop.Akonadi.Agent.akonadi_baloo_indexer" at dbus: "" KCrash: Application 'akonadi_baloo_indexer' crashing... KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi from kdeinit KCrash: Connect sock_file=/usr/oms/.kde/socket-blitz-lx/kdeinit4__0 > As Sandro told, it needs to be "akonadi_indexing_agent" being active. > Additionally to that: You can´t configure Akonadi Search with > Systemsettings, Systemsetting just configured the desktop file search. > Basically the mail and contact indexing part of Baloo has been split out > and is now Akonadi search. Almost unchanged, except for search database > location. Thanks, good to know. "akonadi_indexing_agent" can't be something complicated than... how can it crash at all (and I saw crash often in the past). I couldn't find any -dbg packages, so the backtrace is pretty worthless. > There is a way in KMail to disable fulltext indexing for folders, but as I > found out, Akonadi doesn´t respect that setting. > > I do think Akonadi Search doesn´t receive much love at the moment, and it > shows. That renders KMail at least incomplete. It worked perfect for me until KDE4 came. From that point on it was getting worse and worse... If there was any easy way to convert all those emails from the last 15 years into a halfway working mail client I would do that instead of wasting my time with unloved and unsupported crap. But that is OT, and I am not giving up yet. Regards, Tim signature.asc Description: This is a digitally signed message part.
Re: KDEPIM ready to be more broadly tested
On Monday, July 25, 2016 10:55:45 PM CEST Diederik de Haas wrote: > On maandag 25 juli 2016 22:08:23 CEST Tim Rühsen wrote: > > BTW, I can't find such an option at all - maybe just for imap ? > > Probably. I almost exclusively use imap. > > > I really can't believe that this is a personal problem. I am just sitting > > at a much newer Sid installation and experience absolutely the same > > problems. The question is: what did all of you do that I didn't ? And are > > you sure that indexing and "Tools/Find Messages" really work for you ? > > It's working fine here. I can go to a random mail, copy a word from it and > put it in the search box and it'll find that mail again. > Which database backend are you using for akonadi? It is the mysql backend. In fact I see (output by akonadi) Database "akonadi" opened using driver "QMYSQL" > I have to admit that akonadi is a difficult beast. But it's not really > surprising given the number of protocols it needs to support and workaround > faulty/different implementations of those protocols. > It can be that if sth didn't work right the first time that it doesn't fix > things properly afterwards when there were missing packages initially. > But I have no idea how to properly fix things. > > What you could try is: > akonadictl fsck > akonadictl vacuum Thanks, I am aware of these and executed them like a hundred times. They make no difference. Regards, Tim signature.asc Description: This is a digitally signed message part.
