[Bug 972340] Re: burst aborts with null pointer exception

2012-12-01 Thread Rupert Levene
Here is a much smaller pdf file (also produced by Mac OS X 10.6.8 Quartz PDFContext) that seems to elicit the same behaviour from pdftk: $ pdftk test.pdf burst Unhandled Java Exception: Unhandled Java Exception: java.lang.NullPointerException at gnu.gcj.runtime.NameFinder.lookup(libgcj.so.12)

[Bug 1004569] Re: print to file fails silently if target directory is not writable

2012-08-16 Thread Rupert Levene
This issue is still present in firefox 14: $ apt-cache policy firefox | head -3 firefox: Installed: 14.0.1+build1-0ubuntu0.12.04.1 Candidate: 14.0.1+build1-0ubuntu0.12.04.1 ** Summary changed: - print to file fails silently if target directory is not writable + print to file defaults to

[Bug 1004569] Re: print to file fails silently if target directory is not writable

2012-06-14 Thread Rupert Levene
I upgraded to 12.04, and this issue remains. $ apt-cache policy firefox | head -3 firefox: Installed: 13.0+build1-0ubuntu0.12.04.1 Candidate: 13.0+build1-0ubuntu0.12.04.1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1004569] [NEW] print to file fails silently if target directory is not writable

2012-05-25 Thread Rupert Levene
Public bug reported: Steps to reproduce: 1. Load a web page in firefox and click File-Print. The Print dialog box appears. 2. Choose Print to File from the list of printers 3. Choose home under Save in folder. (This is always the default selection for me). 4. Type a name in the filename box,

[Bug 931976] Re: run in xpdfrc parsed incorrectly making arguments impossible

2012-03-08 Thread Rupert Levene
According to the upstream author, the correct way to do this is to use quotation marks as follows: bind c any run(ls -l) This does work for me (without my patch). However, this use of quotation marks does not seem to be mentioned in the xpdf man page. Hence I now think this is a documentation

[Bug 931976] Re: run in xpdfrc parsed incorrectly making arguments impossible

2012-02-16 Thread Rupert Levene
Here is a patch that fixes the bug for me. ** Patch added: xpdf-fix-parsing3.patch https://bugs.launchpad.net/ubuntu/+source/xpdf/+bug/931976/+attachment/2747062/+files/xpdf-fix-parsing3.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed

[Bug 931976] [NEW] run in xpdfrc parsed incorrectly making arguments impossible

2012-02-14 Thread Rupert Levene
Public bug reported: The following line in ~/.xpdfrc makes xpdf run ls (with the output in the console that xpdf was launched from): bind b any run(ls) This seems to be the correct behaviour. However, the following lines in ~/.xpdfrc don't work: bind c any run(ls -l) bind d any run(ls %f)

[Bug 932062] [NEW] window title does not change when new file is opened

2012-02-14 Thread Rupert Levene
Public bug reported: 1. Run xpdf foo.pdf from a console 2. Hit o and open bar.pdf with the GUI The titlebar of the xpdf window still says Xpdf: foo.pdf but it should say Xpdf: bar.pdf If I run xpdf.real foo.pdf instead, then the titlebar ends up saying /path/to/bar.pdf which I guess is an

[Bug 889077] [NEW] reftex-citation moves cursor and puts citation in the wrong place

2011-11-11 Thread Rupert Levene
Public bug reported: Problem: emacs erroneously repositions the cursor before inserting a reference when using reftex-citation. Steps to reproduce: 1. Run emacs -q --no-site-file 2. Load the attached file testref.tex 3. Hit M-x reftex-mode RET 4. Position the cursor somewhere and hit C-c [ ano

[Bug 889077] Re: reftex-citation moves cursor and puts citation in the wrong place

2011-11-11 Thread Rupert Levene
** Attachment added: testref.tex https://bugs.launchpad.net/bugs/889077/+attachment/2593098/+files/testref.tex -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/889077 Title: reftex-citation moves

[Bug 790212] Re: ! File ended while scanning use of error not handled correctly by TeX-next-error

2011-06-01 Thread Rupert Levene
Here is a simpler test case: \documentclass{article} \begin{document} \emph{ \end{document} The problem seems to be that TeX-next-error expects every error in the log file to have a line number attached to it. But the error here is ! File ended while scanning use of \emph . which doesn't

[Bug 790212] Re: missing } not handled correctly: Search failed: ^l\\. and mysterious Debian buffer

2011-05-30 Thread Rupert Levene
** Attachment added: empty *TeX Help* buffer, and the Debian buffer, and the Search failed message https://bugs.launchpad.net/bugs/790212/+attachment/2147775/+files/Screenshot-emacs%40levene-desktop.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is

[Bug 790212] [NEW] missing } not handled correctly: Search failed: ^l\\. and mysterious Debian buffer

2011-05-30 Thread Rupert Levene
Public bug reported: Binary package hint: auctex If I run emacs -q and load the following file, ~/test.tex: \documentclass{beamer} \begin{document} \begin{frame} $a_{b$ \end{frame} \end{document} and hit C-c C-c LaTeX RET, emacs says LaTeX errors in `*~/test output'. Use C-c ` to display.

[Bug 790212] Re: missing } not handled correctly: Search failed: ^l\\. and mysterious Debian buffer

2011-05-30 Thread Rupert Levene
Backtrace attached. ** Attachment added: backtrace https://bugs.launchpad.net/ubuntu/+source/auctex/+bug/790212/+attachment/2147907/+files/backtrace -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 790212] Re: missing } not handled correctly: Search failed: ^l\\. and mysterious Debian buffer

2011-05-30 Thread Rupert Levene
Here is the LaTeX log file. I imagine that the bug lies in the parsing of this file. ** Attachment added: LaTeX log file https://bugs.launchpad.net/ubuntu/+source/auctex/+bug/790212/+attachment/2147912/+files/test.log -- You received this bug notification because you are a member of Ubuntu

[Bug 790212] Re: missing } not handled correctly: Search failed: ^l\\. and mysterious Debian buffer

2011-05-30 Thread Rupert Levene
** Changed in: auctex (Ubuntu) Status: Incomplete = New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/790212 Title: missing } not handled correctly: Search failed: ^l\\. and mysterious