Ubuntu
pakcs package

pakcs fails to start

Bug #1721977 reported by Yusuke Endoh
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
pakcs (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

I couldn't start pakcs and runcurry commands in 17.10 beta 2.

$ pakcs
[FATAL ERROR: at Sun Oct 8 01:16:58 2017
 Saved state has incompatible VM signature]

$ runcurry
[FATAL ERROR: at Sun Oct 8 01:17:01 2017
 Saved state has incompatible VM signature]

I'm unsure but I guess swi-prolog version was updated?

Thank you,

Tags: artful
Revision history for this message
Hans Joachim Desserud (hjd) wrote :

Thanks for taking your time to report this issue and help making Ubuntu better.

I get the same error message when attempting to run pakcs from pakcs 1.14.2-1 on Ubuntu 17.10. I was not able to reproduce this on Debian Sid, but then again they have a newer version of the package, 1.14.3-1 (https://tracker.debian.org/pkg/pakcs)

Changed in pakcs (Ubuntu):
status: New → Confirmed
tags: added: artful
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.