Mailinglist Archive: opensuse-bugs (3388 mails)

[bugzilla_noreply@xxxxxxxxxx]

https://bugzilla.novell.com/show_bug.cgi?id=746719

https://bugzilla.novell.com/show_bug.cgi?id=746719#c0


           Summary: TeX Live regression: \input tikz breaks plain TeX file
    Classification: openSUSE
           Product: openSUSE 12.1
           Version: Final
          Platform: x86-64
        OS/Version: openSUSE 12.1
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Update Problems
        AssignedTo: bnc-team-screening@xxxxxxxxxxxxxxxxxxxxxx
        ReportedBy: crmafra@xxxxxxxxx
         QAContact: jsrain@xxxxxxxx
          Found By: ---
           Blocker: ---


User-Agent:       Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/535.11 (KHTML,
like Gecko) Chrome/17.0.963.46 Safari/535.11

This problem happens after upgrading from 11.4 to 12.1 (which I did yesterday).

I always used pdftex with plain TeX and tikz.tex, and it worked great until
today. The paper I'm writing is long, so I reduced the problem to a simple
plain TeX file to show that there's a bug with tikz.tex:

%\input tikz
Some text\footnote*{A footnote}
\bye

First, compile with 'tex thisfile.tex' with the tikz line commented out. See
the footnote in the resulting dvi. Now compile again but this time including
the tikz line, and see how the footnote disappears!



Reproducible: Always

Steps to Reproduce:
1. Just compile the above 3-line file with \input tikz and without
2.
3.
Actual Results:  
The \input tikz line makes the footnote disappear from the dvi.

Expected Results:  
If no tikz command is used, just including tikz.tex should not break the
resulting output file. This used to work in openSUSE 11.4 and I rely on this
behavior to write my papers.

For me in particular this is bug with Severity: Major, because I rely deeply on
the tikz feature on plain Tex to write my papers. But I'm leaving it as
"Normal".

-- 
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.