Bug 751054

Summary: nepomukcontroller appears to do nothing
Product: [Fedora] Fedora Reporter: Adam Williamson <awilliam>
Component: kdebase-runtimeAssignee: Than Ngo <than>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 16CC: alekcejk, jreznik, kevin, ltinkl, rdieter, rnovacek, ry, smparrish, than
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-11-03 11:50:03 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Adam Williamson 2011-11-03 11:24:44 UTC
There's a 'Nepomuk File Indexing Controller' entry in KDE (F16 RC5)'s System menu, which calls 'nepomukcontroller', which seems to do nothing. If you run it in a console it throws two warnings about 'session D-Bus connection created before QCoreApplication' (which seems to be a common complaint among KDE apps) then returns straight to the console. Doesn't seem like a crash, though, more like it short-circuits somehow.

kdebase-runtime 4.7.2-1.fc16.

Comment 1 Adam Williamson 2011-11-03 11:25:44 UTC
proposing as an F16 blocker per strict criteria interpretation "All applications listed under the Applications menu or category must start successfully", though I expect we can ask KDE team to waive this.

Comment 2 nucleo 2011-11-03 11:35:35 UTC
'Nepomuk File Indexing Controller' starts 'Nepomuk File Indexing' which appears in hidden icons in tray.

Comment 3 Adam Williamson 2011-11-03 11:50:03 UTC
indeed, that's easy to miss...the 'wallet manager' does the same thing, apparently. so, not really a bug. whew.



-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Comment 4 Kevin Kofler 2011-11-03 15:28:50 UTC
Right, it's not a real bug, just a very crappy UI. ;-)