Failed to use export feature in Org-mode

Bug #1064024 reported by Fredrik Nyqvist
32
This bug affects 7 people
Affects Status Importance Assigned to Milestone
Fedora
Fix Released
Undecided
emacs24 (Debian)
Fix Released
Unknown
emacs24 (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

When I am trying to export my .org document to another format by using the command C-c C-e I get the response "Can't find library org".

 1) Ubuntu 12.10 Beta 2

 2) emacs24 24.1+1-2ubuntu3

 3) I want to export my .org file to pdf or other format using Emacs.

 4) I get the response "Can't find library org".

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: emacs24 24.1+1-2ubuntu3
ProcVersionSignature: Ubuntu 3.5.0-17.27-generic 3.5.5
Uname: Linux 3.5.0-17-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.6.1-0ubuntu1
Architecture: amd64
Date: Mon Oct 8 21:22:29 2012
InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1)
SourcePackage: emacs24
UpgradeStatus: Upgraded to quantal on 2012-09-30 (8 days ago)

Revision history for this message
In , Stefan (stefan-redhat-bugs) wrote :

Description of problem:

In particular, the clocking feature does not work. C-c C-x TAB (org-clock-in) causes this message to be displayed: "Can't find library org".

Version-Release number of selected component (if applicable):

24.0.95-1.fc17

Steps to Reproduce:
1. Open a lisp-interaction buffer
2. Type "(require 'org-clock)"
3. Press C-x C-e

Actual results:

Debugger entered--Lisp error: (error "Can't find library org")
  signal(error ("Can't find library org"))
  error("Can't find library %s" "org")
  find-library-name("org")
  (file-name-directory (find-library-name "org"))
  (expand-file-name "../contrib" (file-name-directory (find-library-name "org")))
  (file-name-as-directory (expand-file-name "../contrib" (file-name-directory (find-library-name "org"))))
  (expand-file-name "scripts" (file-name-as-directory (expand-file-name "../contrib" (file-name-directory (find-library-name "org")))))
  (file-name-as-directory (expand-file-name "scripts" (file-name-as-directory (expand-file-name "../contrib" (file-name-directory (find-library-name "org"))))))
  (expand-file-name "ditaa.jar" (file-name-as-directory (expand-file-name "scripts" (file-name-as-directory (expand-file-name "../contrib" (file-name-directory (find-library-name "org")))))))
  eval((expand-file-name "ditaa.jar" (file-name-as-directory (expand-file-name "scripts" (file-name-as-directory (expand-file-name "../contrib" (file-name-directory (find-library-name "org"))))))))
  custom-initialize-reset(org-ditaa-jar-path (expand-file-name "ditaa.jar" (file-name-as-directory (expand-file-name "scripts" (file-name-as-directory (expand-file-name "../contrib" (file-name-directory (find-library-name "org"))))))))
  custom-declare-variable(org-ditaa-jar-path (expand-file-name "ditaa.jar" (file-name-as-directory (expand-file-name "scripts" (file-name-as-directory (expand-file-name "../contrib" (file-name-directory (find-library-name "org"))))))) ("/usr/share/emacs/24.0.95/lisp/org/org-exp-blocks.elc" . 6097) :group org-babel :type string)
  require(org-exp-blocks)
  byte-code("\300\301!\210\300\302!\210\300\303!\210\300\304!\210\300\305!\210\300\306!\207" [require org org-macs org-agenda org-exp-blocks ob-exp org-src] 2)
  require(org-exp)
  byte-code("\300\301!\210\300\302!\210\303\304\305\306\307\310\311\312&\207" [require org org-exp custom-declare-group org-clock nil "Options concerning clocking working time in Org-mode." :tag "Org Clock" :group org-progress] 8)
  require(org-clock)
  eval((require (quote org-clock)) nil)
  eval-last-sexp-1(nil)
  eval-last-sexp(nil)
  call-interactively(eval-last-sexp nil nil)

Expected results:

org-clock is loaded

Additional info:

With the emacs-el package installed, it works as it should.

Revision history for this message
In , Mihkel (mihkel-redhat-bugs) wrote :

Any news on this one? Or is emacs-el package required now to be able to export org documents?

Revision history for this message
In , Jonathan (jonathan-redhat-bugs) wrote :

My personal feeling is that we should (in the spirit of the emacs add-on packaging guidelines) no longer bother to split out the .el[.gz] files into a sub-package, but rather install them with the main package - they're useful for debugging, doc strings etc. In many ways they're as useful as .py files from python packages.

As to this specific problem, I wonder why org-mode isn't able to use the byte-compiled files, though.

Revision history for this message
In , Karel (karel-redhat-bugs) wrote :

Thank you for such a good bug report.

The issue can be reproduced on emacs-24.1-1.fc17. The workaround (installing emacs-el) works.

Requiring org-clock results in requiring org-exp-blocks, which defines org-ditaa-jar-path. The definition results in evaluating (find-library-name "org"). The find-library-name function specifically looks for .el and .el.gz source code, deliberately ignoring .elc.

I think org-ditaa-jar-path could work with the locate-library function instead of find-library-name. I'm going to try that.

Jonathan, it is a good idea to merge emacs-el into emacs-common. Please, feel free to change the spec file if you want to do it. I think it should go to rawhide only.

Revision history for this message
In , Karel (karel-redhat-bugs) wrote :
Revision history for this message
In , Fedora (fedora-redhat-bugs) wrote :

emacs-24.1-3.fc17 has been submitted as an update for Fedora 17.
https://admin.fedoraproject.org/updates/emacs-24.1-3.fc17

Revision history for this message
In , Fedora (fedora-redhat-bugs) wrote :

Package emacs-24.1-3.fc17:
* should fix your issue,
* was pushed to the Fedora 17 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing emacs-24.1-3.fc17'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2012-10635/emacs-24.1-3.fc17
then log in and leave karma (feedback).

Revision history for this message
In , Fedora (fedora-redhat-bugs) wrote :

emacs-24.1-3.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.

Revision history for this message
Fredrik Nyqvist (fredrik-nyqvist) wrote :
description: updated
Revision history for this message
Egberto Fuentes (egberto-fuentes-deactivatedaccount) wrote :

I have installed the 12.10 (Quantal Quetzal) and have a "Can't find library org" message when "find-library-name" gets called.

Seems that "find-library-name" search for a source file (.el) and not a compiled one (.elc); so I install the "emacs24-el" package and the error gone.

Revision history for this message
era (era) wrote :

Marked as Confirmed; this is trivially reproducible out of the box. (Open a new file, enter org mode, enter some content, hit C-c C-e.)

Attaching the resulting Lisp backtrace.

Changed in emacs24 (Ubuntu):
status: New → Confirmed
Revision history for this message
era (era) wrote :

Perhaps the ditaa add-on, or even the entire scripts directory, should be shipped with emacs24, not with emacs24-el. Anyhow, this bug report belongs upstream. Will forward.

Changed in emacs24 (Debian):
status: Unknown → New
Revision history for this message
Andi Albrecht (andialbrecht) wrote :

I've seen the same issue. Installing the org-mode package solved it for me.

Revision history for this message
ilia (ilia) wrote :
Revision history for this message
Glenn Morris (rgm+lp) wrote :

I believe this is fixed in Emacs 24.3.

Changed in emacs24 (Debian):
status: New → Fix Released
Revision history for this message
era (era) wrote :

Upstream fixed this in 24.3 and we are on 24.4 already. Marking as Fix Released. Please reopen if you see a regression. Thanks.

Changed in emacs24 (Ubuntu):
status: Confirmed → Fix Released
Changed in fedora:
importance: Unknown → Undecided
status: Unknown → Fix Released
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.