Bug 1177915 - Asciidoctor does not work
Summary: Asciidoctor does not work
Keywords:
Status: CLOSED DUPLICATE of bug 1174128
Alias: None
Product: Fedora
Classification: Fedora
Component: rubygem-asciidoctor
Version: 21
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: Ken Dreyer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-12-31 10:14 UTC by Fabio Alessandro Locati
Modified: 2015-01-02 13:10 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-01-02 13:10:04 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Fabio Alessandro Locati 2014-12-31 10:14:33 UTC 
Description of problem:
Running "asciidoctor" I receive a strange error (that seems Java!!).

Version-Release number of selected component (if applicable):
asciidoctor 1.5.2-1.fc21

Steps to Reproduce:
1. open terminal
2. run "asciidoctor"

Actual results:
OptoFactory.java:109:in `<clinit>': java.lang.NoClassDefFoundError: org/objectweb/asm/Opcodes
	from Ruby.java:4549:in `<init>'
	from Ruby.java:280:in `newInstance'
	from Main.java:262:in `internalRun'
	from Main.java:221:in `run'
	from Main.java:201:in `main'

Expected results:
I expected it to work properly as it did in F20
Comment 1 Ken Dreyer 2015-01-01 23:18:03 UTC 
Hi Fabio, Dan pointed out to me that this is probably a bug Fedora's jruby package, not rubygem-asciidoctor. The same backtrace is here: https://bugzilla.redhat.com/show_bug.cgi?id=1174128 .

I'd be curious to know whether you have the Ruby RPM installed? "rpm -q ruby"

If you do have the MRI ruby package installed, then you can tell rubypick to prefer MRI over JRuby by setting the RUBYPICK environment variable.

Please try running the following:

  RUBYPICK=_mri_ /usr/bin/asciidoctor

If that does not crash, and asciidoctor works as expected, please let us know.

Once we can could confirm that bug 1174128 is the issue, I can close this bug as a duplicate of that one. But I'd prefer to have your feedback if at all possible before Dan and I proceed :)
Comment 2 Fabio Alessandro Locati 2015-01-02 10:38:06 UTC 
Hi,

the "rpm -q ruby" returned that the ruby package is _NOT_ installed.

Executing "sudo dnf install ruby" it installed "ruby" and "rubygem-bigdecimal" and then the problem was solved.

Thank you :)
Comment 3 Ken Dreyer 2015-01-02 13:10:04 UTC 
Thanks Fabio! I'll go ahead and close this one so we can track the jruby issue in 1174128.

*** This bug has been marked as a duplicate of bug 1174128 ***
Note You need to log in before you can comment on or make changes to this bug.