Bug 283865 - Error message about nepomuk not working when manually disabled
Summary: Error message about nepomuk not working when manually disabled
Status: RESOLVED DUPLICATE of bug 271558
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: Nepomuk Feeder Agents (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR normal
Target Milestone: ---
Assignee: Sebastian Trueg
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-10-12 15:26 UTC by ash
Modified: 2011-10-17 22:35 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description ash 2011-10-12 15:26:13 UTC
Version:           unspecified (using KDE 4.7.1) 
OS:                Linux

When Nepomuk and Strigi are disabled manually in SystemSettings (due to not needing that functionality), notification about a problem in Nepomuk shows up in every startup, despite there being no problem and Nepomuk was intentionaly disabled

Depending on the use of the computer (as in : public library, classroom etc ...) I may not want Nepomuk functionality at all, since the data is irrelevant after the user gone away from the computer (leaving it logged in), and it can inhibit the user's privacy if the next user can fetch data from Nepomuk

Reproducible: Always

Steps to Reproduce:
Disable Strigi and Nepomuk in Systemsettings. Log out+in or reboot

Actual Results:  
Get notification (in the Plasma notifications) that there is a problem that prevents Nepomuk from starting

Expected Results:  
Nepomuk not working, no notifications about it
Comment 1 Sebastian Trueg 2011-10-12 18:24:28 UTC
This is not a bug. The message comes from Akonadi which actually depends on Nepomuk.
Comment 2 ash 2011-10-13 08:36:36 UTC
This is a bug. The notification should be suppressed when Nepomuk was intentionally disabled, or be displayed once and not after every reboot
Comment 3 Sebastian Trueg 2011-10-13 09:23:29 UTC
Reassigning to Akonadi then.
Comment 4 Christophe Marin 2011-10-17 22:35:36 UTC

*** This bug has been marked as a duplicate of bug 271558 ***