Bug 1270152 - pykig does no longer work
pykig does no longer work
Product: Fedora
Classification: Fedora
Component: kig (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Ngo Than
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2015-10-09 02:44 EDT by Maurizio Paolini
Modified: 2015-10-09 13:02 EDT (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2015-10-09 13:02:24 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

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

External Trackers
Tracker ID Priority Status Summary Last Updated
KDE Software Compilation 353726 None None None Never

  None (edit)
Description Maurizio Paolini 2015-10-09 02:44:33 EDT
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):


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 13:00:43 EDT
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 13:02:24 EDT

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