Bug 315985 - Akonadi nepomuk Feeder not detecting nepomukserver on startup
Summary: Akonadi nepomuk Feeder not detecting nepomukserver on startup
Status: RESOLVED FIXED
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: Nepomuk Feeder Agents (show other bugs)
Version: 4.10
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
: 318110 319230 (view as bug list)
Depends on:
Blocks:
 
Reported: 2013-03-01 22:33 UTC by Blackpaw
Modified: 2013-06-13 03:40 UTC (History)
14 users (show)

See Also:
Latest Commit:
Version Fixed In: 4.11


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Blackpaw 2013-03-01 22:33:50 UTC
On booting my pc and starting akonadiconsole the status of the nepomuk feeder is:

  "Waiting for Nepomuk Server to start..."

However "ps -e|grep nepo" shows that nepomukserver is running, plus all the other nepomuk related facilities are working.

Its stays this way for a few minutes then changes to:

  "Nepomuk is not operation: Nepomuk is not running"

If I then restart the feeder resource it finds Nepomuk immediately and starts indexing.

Reproducible: Always

Steps to Reproduce:
1. Boot KDE
2. Start akonadiconsole
3. Observe the nepomuk feeder status
Actual Results:  
The feeder  fails to find the nepomuk server, after a few minutes it errors out.

Expected Results:  
The nepomuk feeder should find the server almost immediately.

My google calendar and contacts resources are occasionally off-line - maybe a similar problem?
Comment 1 Blackpaw 2013-03-06 12:11:03 UTC
Still happening in 4.10.1
Comment 2 Blackpaw 2013-03-09 22:09:10 UTC
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.
Comment 3 Blackpaw 2013-03-25 10:08:43 UTC
This no longer happens for me - nepomuk and akonadi built from master. Feeder starts and recognises the nepomukservice.
Comment 4 Allen Winter 2013-03-25 15:31:35 UTC
I will resolve then.  reopen as needed
Comment 5 Hrvoje Senjan 2013-04-02 20:43:05 UTC
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.
Comment 6 Blackpaw 2013-04-06 21:48:30 UTC
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.
Comment 7 Vesa Muhonen 2013-04-16 20:32:38 UTC
I'm seeing the same issue here. KDE 4.10.2 on Arch Linux.
Comment 8 Alejandro Nova 2013-04-17 14:52:39 UTC
*** Bug 318110 has been marked as a duplicate of this bug. ***
Comment 9 Alejandro Nova 2013-04-17 14:53:43 UTC
Please, see my comments on my duplicate bug report.
Comment 10 Blackpaw 2013-04-17 21:05:34 UTC
(In reply to comment #9)
> Please, see my comments on my duplicate bug report.

Which duplicate bug report is that?
Comment 11 Alejandro Nova 2013-04-17 21:14:02 UTC
(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
Comment 12 Josh Liberty 2013-05-02 21:39:06 UTC
*** Bug 319230 has been marked as a duplicate of this bug. ***
Comment 13 Philipp 2013-05-06 07:11:16 UTC
same problem here Kubuntu 13.04 KDE 4.10.2.
I already tried deleting all nepomuk and akonadi directories and settings, problem persists
Comment 14 mail 2013-05-11 08:46:19 UTC
on 4.10.3 the akonadi nepomuk feeder starts seems to start up correctly
Comment 15 A. Sala 2013-05-16 13:34:23 UTC
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.
Comment 16 A. Sala 2013-05-16 13:42:09 UTC
Just in case, I came here googling from blank Kmail searches... After the restart thing, imap searches in kmail didn't work, either.
Comment 17 Hrvoje Senjan 2013-06-09 12:02:39 UTC
I think we can close this now. Works correctly with master/what will be 4.11
Comment 18 Alejandro Nova 2013-06-09 13:49:51 UTC
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
Comment 19 Alejandro Nova 2013-06-13 03:40:41 UTC
Edit: packaging error, with Soprano 2.9.2 (my report + another Chakra user) this works. So, this bug is fixed.