Bug 1270152 - pykig does no longer work
Summary: pykig does no longer work
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: kig
Version: 22
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Than Ngo
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-10-09 06:44 UTC by Maurizio Paolini
Modified: 2015-10-09 17:02 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-10-09 17:02:24 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
example of a pykig script (717 bytes, text/plain)
2015-10-09 06:44 UTC, Maurizio Paolini
no flags Details


Links
System ID Private Priority Status Summary Last Updated
KDE Software Compilation 353726 0 None None None Never

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.


Note You need to log in before you can comment on or make changes to this bug.