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

            Bug ID: 388044
           Summary: Renku 0.4.1 is unusable on KDE Neon due to lack of
                    setup/documentation
           Product: zanshin
           Version: unspecified
          Platform: Other
                OS: Linux
            Status: UNCONFIRMED
          Severity: critical
          Priority: NOR
         Component: general
          Assignee: er...@kde.org
          Reporter: ironst...@gmail.com
                CC: mbe...@ipsquad.net
  Target Milestone: already done

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"

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to