Bug 1270152

Summary: pykig does no longer work
Product: [Fedora] Fedora Reporter: Maurizio Paolini <paolini>
Component: kigAssignee: Than Ngo <than>
Status: CLOSED UPSTREAM QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 22CC: jreznik, kevin, ltinkl, rdieter, rnovacek, than
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-10-09 17:02:24 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
example of a pykig script none

Description Maurizio Paolini 2015-10-09 06:44:33 UTC
Created attachment 1081195 [details]
example of a pykig script

Description of problem:

pykig external scripting exits with an error

Version-Release number of selected component (if applicable):

kig-15.04.3-1.fc22.i686

How reproducible:

call pykig with any existing pykig script

Steps to Reproduce:
1. locate a pykig script, e.g. tree.kpy [in the kig source tree, also
   attached to this bug report]
2. execute: "$ pykig.py tree.kpy"

Actual results:
ends with error: Unknown option 'nofork'.


Expected results:
should open a kig window with the required construction

Additional info:

clearly now kig by default does not fork into the background and
the --nofork option is now invalid.  The
pykig.py python script should be modified to reflect this.

Comment 1 Maurizio Paolini 2015-10-09 17:00:43 UTC
Oops, I guess the correct place for this bug is upstream.  I just reported the
bug upstream in bugs.kde.org

Comment 2 Rex Dieter 2015-10-09 17:02:24 UTC
Thanks.