Unable to open file: unknown opcode

Bug #604275 reported by Brooks Rabideau
4
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Keryx
In Progress
Medium
Unassigned

Bug Description

After successfully downloading latest package list get multiple messages of:
XXX lineno: 320, opcode:: 54
Unable to open file: unknown opcode

Revision history for this message
mac9416 (mac9416) wrote :

Hi, Brooks!

Thanks for the bug report. It's funny, I went to Google that error, and the first result was a blog post by Chris Oliver (the project leader): http://excid3.com/blog/2010/06/unable-to-open-file-unknown-opcode/

It appears that this is a problem has surfaced before on 64-bit Linux systems. Is that what you're running Keryx on when you get this error?

Revision history for this message
Chris Oliver (excid3) wrote :

Hey Brooks, like mac mentioned, it's a problem with running Keryx on 64bit. We compiled the linux executable on 32bit and keep having errors uploading the 64bit binary we built to fix the problem. We are going to try to upload the executable again. We don't see a whole lot of 64bit Linux users using the GUI at the moment so it hasn't been top priority but we will make make it one now. :)

You can run it from source (just have to install Python and wxPython) and it will work alright.

Changed in keryx:
importance: Undecided → Medium
status: New → In Progress
Revision history for this message
Alwynn (thalius) wrote :

What fixed this bug for me was to delete the Keryx folder and then to "re-install". Ran as administrator(in case of file permission errors), seemed to clear up the opcode issue for me.

Revision history for this message
Chris Oliver (excid3) wrote :

Interesting, I imagine that what really happened here was redownloading the list files. I think they may be corrupted or something, in which case it throws an opcode error.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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