User:Winterz: Difference between revisions

From KDE TechBase
Line 24: Line 24:
| kinit autostart
| kinit autostart
| strigidaemon not autostarted
| strigidaemon not autostarted
| ?
| probably needs an appropriate desktop file installed in share/autostart
|-
|-
| kinit autostart
| kinit autostart
| nepomukdaemon not autostarted
| nepomukdaemon not autostarted
| ?
| probably needs an appropriate desktop file installed in share/autostart
|-
|-
| strigiclient
| strigiclient
Line 39: Line 39:
|-
|-
| kbackgammon
| kbackgammon
| writes "KNotificationManager::notify:: error while contacting knotify server" to konsole. Perhaps must be ported from KDE3's KNotifyClient to KDE4's new KNotification
| writes "KNotificationManager::notify:: error while contacting knotify server" to konsole.
| ?
| probably must be ported from KDE3's KNotifyClient to KDE4's new KNotification
|-
|}
|}

Revision as of 01:23, 29 August 2007

My Lists and Tables of Stuff

Welcome to my world.

Minimum Requirements before a KDE 4.0.0 Release Candidate

* a functional workspace (i.e. Plasma)
* oxygen style working
* konqueror working
* dolphin working
* sound working
* kmail working
* kate working

"working" doesn't mean "bug free"; it means no known "grave bugs". "working" means using it doesn't make you want throw your computer out the window.

Bugs Encountered

Known Bugs
Application Issue Status
kinit autostart strigidaemon not autostarted probably needs an appropriate desktop file installed in share/autostart
kinit autostart nepomukdaemon not autostarted probably needs an appropriate desktop file installed in share/autostart
strigiclient thinks that strigidaemon is running when it isn't reported to Jos
strigiclient when creating index, cannot find any fields in .fieldproperties ontology database reported to Jos
kbackgammon writes "KNotificationManager::notify:: error while contacting knotify server" to konsole. probably must be ported from KDE3's KNotifyClient to KDE4's new KNotification