Renku installs and starts on KDE Neon, however it is completely unusable because it seems to require a storage/resource backend or something that does not exist on a default install (akonadi? ldap?). The app sits there looking pretty, if you click "New item" it tells you to type something in the box and hit enter to create an item. When the user does this nothing happens, the item is not created, there is no error message, the textbox is just cleared to indicate the input was accepted and seemingly just discarded. There's a Settings->Configure Renku screen that seems to suggest a resource might be required to act as backend storage, but there's no information on what RESOURCE or what format is expected in the "Add resource" field. Requiring users to have developer knowledge of Renku in order to get it to work is a surefire reason why nobody is going to use it no matter how cool it is. Here's the output to the console while running Renku: helix:~$ renku org.kde.pim.akonadicore: "QLocalSocket::connectToServer: Invalid name" "/home/user/.local/share/akonadi/akonadiserver-cmd.socket" Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) org.kde.pim.akonadicore: "QLocalSocket::connectToServer: Invalid name" "/home/user/.local/share/akonadi/akonadiserver-cmd.socket" org.kde.pim.akonadiserver: Did not find MySQL server default configuration (mysql-global.conf) org.kde.pim.akonadiserver: Failed to remove runtime connection config file org.kde.pim.akonadicontrol: Application 'akonadiserver' exited normally... kf5.kio.core: Refilling KProtocolInfoFactory cache in the hope to find "ldap" org.kde.pim.akonadicore: Socket error occurred: "QLocalSocket::connectToServer: Invalid name" org.kde.pim.akonadicore: Socket error occurred: "QLocalSocket::connectToServer: Invalid name"
This is the original console output before I installed akonadi and akonadi-mysql-backend in an effort to get this to work: org.kde.pim.akonadicore: Unable to execute akonadi_control, falling back to D-Bus auto-launch org.kde.pim.akonadicore: "QLocalSocket::connectToServer: Invalid name" "/home/user/.local/share/akonadi/akonadiserver-cmd.socket" org.kde.pim.akonadicore: Unable to execute akonadi_control, falling back to D-Bus auto-launch org.kde.pim.akonadicore: "QLocalSocket::connectToServer: Invalid name" "/home/user/.local/share/akonadi/akonadiserver-cmd.socket" kf5.kio.core: Refilling KProtocolInfoFactory cache in the hope to find "ldap" org.kde.pim.akonadicore: Socket error occurred: "QLocalSocket::connectToServer: Invalid name" org.kde.pim.akonadicore: Socket error occurred: "QLocalSocket::connectToServer: Invalid name"
Git commit 09a7e2dad9b5c130d9e1573c4b546e051612a0f6 by Kevin Ottens. Committed on 03/01/2018 at 08:38. Pushed by ervin into branch 'master'. Don't hardcode the settings dialog to todos Summary: This made Renku unusable since users couldn't set it up properly. They'd get an inappropriate selection of resources to pick from which would be completely confusing. Reviewers: bensi, dfaure, franckarrecot Differential Revision: https://phabricator.kde.org/D9629 M +18 -5 src/akonadi/akonadiconfigdialog.cpp M +7 -1 src/akonadi/akonadiconfigdialog.h M +5 -3 src/akonadi/akonadidatasourcerepository.cpp M +3 -1 src/akonadi/akonadidatasourcerepository.h M +5 -3 src/renku/app/dependencies.cpp M +5 -3 src/zanshin/app/dependencies.cpp M +2 -1 tests/units/akonadi/akonadidatasourcerepositorytest.cpp https://commits.kde.org/zanshin/09a7e2dad9b5c130d9e1573c4b546e051612a0f6