Summary: | kmymoney cannot open any file, on start it says: kf5.kio.core: couldn't create slave: "Unknown protocol 'file'.". | ||
---|---|---|---|
Product: | [Applications] kmymoney | Reporter: | Kostiantyn Lysenko <gshaud> |
Component: | file | Assignee: | KMyMoney Devel Mailing List <kmymoney-devel> |
Status: | RESOLVED WORKSFORME | ||
Severity: | major | CC: | yurii.kolesnykov |
Priority: | NOR | ||
Version: | 5.0.3 | ||
Target Milestone: | --- | ||
Platform: | Homebrew (macOS) | ||
OS: | macOS | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Kostiantyn Lysenko
2019-03-20 14:25:31 UTC
*** This bug has been marked as a duplicate of bug 400761 *** in https://bugs.kde.org/show_bug.cgi?id=400761 errors are: Couldn't start kuiserver from org.kde.kuiserver.service: QDBusError("org.freedesktop.DBus.Error.Disconnected", "Not connected to D-Bus server") kf5.kio.core: couldn't create slave: "Can not find 'kioslave' executable at '/Users/myzinsky/.Trash/kmymoney.app/Contents/MacOS, /Users/myzinsky/.Trash/kmymoney.app/Contents/libexec, /Users/packaging/Craft/BinaryCache/macos-64-clang/lib/libexec/kf5'" in https://bugs.kde.org/show_bug.cgi?id=405689 errors are: kf5.kio.core: couldn't create slave: "Unknown protocol 'file'." kf5.kio.core: couldn't create slave: "Unknown protocol 'file'." kf5.kio.core: couldn't create slave: "Unknown protocol 'file'." kf5.kio.core: couldn't create slave: "Unknown protocol 'file'." kf5.kio.core: couldn't create slave: "Unknown protocol 'file'." kf5.kio.core: couldn't create slave: "Unknown protocol 'file'." kf5.kio.core: couldn't create slave: "Unknown protocol 'file'." kf5.kio.core: couldn't create slave: "Unknown protocol 'file'." kf5.kio.core: couldn't create slave: "Unknown protocol 'file'." kf5.kio.core: couldn't create slave: "Unknown protocol 'file'." Can not find 'kioslave' executable and "Unknown protocol 'file'. seems like different issues for me. Though using Qt standard functions to open files instead of KIO as specified in https://bugs.kde.org/show_bug.cgi?id=400761 can be a workaround for both issues. Is this still an issue? Plenty has changed in three and a half years. Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |