Summary: | kde-base/kdevplatform-1.6.0 - kdevelop fails to create new projects "Could not start process Unable to create io-slave:" | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Nanzikambe <bodhisattva> |
Component: | [OLD] KDE | Assignee: | Gentoo KDE team <kde> |
Status: | RESOLVED FIXED | ||
Severity: | normal | Keywords: | InVCS |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | http://commits.kde.org/kdevplatform/33b660dfefe02ecd4391a284f6fd6de9439b2b45 | ||
See Also: | https://bugs.kde.org/show_bug.cgi?id=329392 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
Fix appwizardplugin.cpp
ebuild that applies the patch |
Created attachment 381810 [details]
ebuild that applies the patch
ebuild that applies the patch
Upstream bug is: https://bugs.kde.org/show_bug.cgi?id=329392 Please dont not add arch teams by yourself. They do stable and keyword requests in general. Comment on attachment 381810 [details]
ebuild that applies the patch
Upstream patch will be added with PATCHES array and contains not needed comments.
Comment on attachment 381808 [details, diff]
Fix appwizardplugin.cpp
Will use upstream git patch with comment.
Thanks for reporting. This is fixed in cvs now. Please sync in some hours to get the changes. + + 29 Jul 2014; Johannes Huber <johu@gentoo.org> + +files/kdevplatform-1.6.0-appwizard.patch, +kdevplatform-1.6.0-r1.ebuild, + -kdevplatform-1.6.0.ebuild: + Revision bump adds upstream patch to fix new project creation with wizard + spotted by Nanzikambe <janus.nanzikambe+gentoobugs@gmail.com>, bug #518486. + |
Created attachment 381808 [details, diff] Fix appwizardplugin.cpp Starting a new project using the wizard in kdevelop-4.6.0 results in the following error "Could not start process Unable to create io-slave: klauncher said: Unknown protocol ''. ." Steps to reproduce: * Start kdevelop * Click New Project * Choose Python * Provide a project name * Click Next * Click Finish This happens even after running kbuildsycoca4 Upstream has a bug for this here, but as it prevents you testing out 4.6 properly I've created this bug & attached an ebuild + patch for it