[Akonadi] [Bug 318110] New: akonadi-nepomuk-feeder isn't detecting Nepomuk properly when system boots.

[Alejandro Nova]

https://bugs.kde.org/show_bug.cgi?id=318110

            Bug ID: 318110
           Summary: akonadi-nepomuk-feeder isn't detecting Nepomuk
                    properly when system boots.
    Classification: Unclassified
           Product: Akonadi
           Version: unspecified
          Platform: Chakra
                OS: Linux
            Status: UNCONFIRMED
          Severity: major
          Priority: NOR
         Component: Nepomuk Feeder Agents
          Assignee: kdepim-bugs at kde.org
          Reporter: alejandronova at gmail.com
                CC: me at vhanda.in, vkrause at kde.org

The Akonadi Nepomuk Feeder will always fail to detect Nepomuk after a
successful boot. It won't start, unless you restart Akonadi, or restart the
Nepomuk Feeder through the Akonadi Console.

This bug has the potential to mask other bugs, so it must be quashed quickly.

Reproducible: Always

Steps to Reproduce:
1. Boot the system and wait a bit until Nepomuk and Akonadi initialize properly
2. Open the Akonadi Console
3. The Akonadi Nepomuk Feeder reports "Nepomuk is not operational", even though
Nepomuk IS operational.
Actual Results:  
The Akonadi Nepomuk Feeder waits until Nepomuk is properly initialized, and
doesn't get a signal from Nepomuk telling the feeder that Nepomuk is
operational. The feeder never starts, unless the user restarts Nepomuk and/or
the feeder

Expected Results:  
The Akonadi Nepomuk Feeder waits until Nepomuk is properly initialized, and
gets a signal from Nepomuk telling the feeder that Nepomuk is operational. The
feeder then start.

Whatever impact Akonadi Nepomuk Feeder has on the performance of the system is
displayed.

This is a major bug, since this entirely breaks the e-mail indexing, unless an
informed user restarts the Akonadi Nepomuk Feeder. It seems to be also an
easily fixable bug.

-- 
You are receiving this mail because:
You are the assignee for the bug.