Summary: | Akonadi nepomuk Feeder not detecting nepomukserver on startup | ||
---|---|---|---|
Product: | [Frameworks and Libraries] Akonadi | Reporter: | Blackpaw <lindsay.mathieson> |
Component: | Nepomuk Feeder Agents | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | alejandronova, asala, hrvoje.senjan, josh+tech, lbeltrame, lindsay.mathieson, mail, mail, philipp_foerster, srv, sven.burmeister, thomas, vkrause, winter |
Priority: | NOR | ||
Version: | 4.10 | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | 4.11 | |
Sentry Crash Report: |
Description
Blackpaw
2013-03-01 22:33:50 UTC
Still happening in 4.10.1 Just to check I hadn't bolloxed my system with various updates and tests etc I created a Clean Kubuntu 13.04 VM + all updates (to 4.10.1) and then added my Gmail account. Problem reoccurs on every boot. This no longer happens for me - nepomuk and akonadi built from master. Feeder starts and recognises the nepomukservice. I will resolve then. reopen as needed I also already thought it got fixed, as for a few days it started correctly, but on this boot it didn't. Using up to date master, akonadi + rest of the KDE SC stack. I'm afraid I'm going to have to withdraw my Comment #3 - I forgot that I had a script installed to restart the feeder on kde startup. The feeder is still failing to detect nepomuk on startup, this is in 4.10.2 and master. I'm seeing the same issue here. KDE 4.10.2 on Arch Linux. *** Bug 318110 has been marked as a duplicate of this bug. *** Please, see my comments on my duplicate bug report. (In reply to comment #9) > Please, see my comments on my duplicate bug report. Which duplicate bug report is that? (In reply to comment #10) > (In reply to comment #9) > > Please, see my comments on my duplicate bug report. > > Which duplicate bug report is that? bug 318110 *** Bug 319230 has been marked as a duplicate of this bug. *** same problem here Kubuntu 13.04 KDE 4.10.2. I already tried deleting all nepomuk and akonadi directories and settings, problem persists on 4.10.3 the akonadi nepomuk feeder starts seems to start up correctly I have 4.10.3 and Akonadi Nepomuk feeder in Akonadi console is, too "Waiting for Nepomuk Server to start..." whereas actually: asala@pitblau3:~$ ps -e | grep nepo 23346 ? 00:00:00 nepomukserver 23350 ? 00:00:35 nepomukservices 23478 ? 00:00:00 nepomukcontroll 23779 ? 00:00:00 akonadi_nepomuk 24033 ? 00:00:01 nepomukservices 24037 ? 00:00:43 nepomukservices Restarting agent, it did it. So, seems that some 4.10.3 configurations may be still broken. Just in case, I came here googling from blank Kmail searches... After the restart thing, imap searches in kmail didn't work, either. I think we can close this now. Works correctly with master/what will be 4.11 If you can backport the fix to the stable branch, it would be great. Otherwise, you will force me to use 4.11 beta 1 Edit: packaging error, with Soprano 2.9.2 (my report + another Chakra user) this works. So, this bug is fixed. |