pdfTeX warning: destination with same identifier has been already used, duplicate ignored (weird behavior)











up vote
12
down vote

favorite
3












Here is a minimal example:



documentclass{amsart}

usepackage{amsthm}
usepackage[pdftex]{hyperref}

newtheoremstyle{myexercise}{baselineskip}{baselineskip}{}{}{bfseries}{.}{ }{thmname{#1}thmnumber{ #2}thmnote{ (#3)}}
newtheoremstyle{mypart}{baselineskip}{baselineskip}{}{}{bfseries}{}{newline}{thmname{#1}thmnumber{ #2}thmnote{ -- #3}}

theoremstyle{myexercise}
newtheorem{Exo}{Exercise}
theoremstyle{mypart}
newtheorem{Part}{Part}[Exo]
renewcommand*thePart{Roman{Part}}

begin{document}
begin{Exo}[A cool exercise]
begin{Part}
label{p:ex1:I}
Prove that $1=0$.
end{Part}
begin{Part}
Deduce from Part~ref{p:ex1:I} that this exercise is wrong.
end{Part}
end{Exo}

begin{Exo}
begin{Part}
Let $a=b$. Deduce that $0=0$.
end{Part}
begin{Part}
Let $a=42$. For what values of $b$ do we have $a=b$?
end{Part}
end{Exo}
end{document}


The warning I get is the following:




pdf TeX warning (ext4): destination
with the same identifier
(name{Part.1.1}) has b een already
used, duplicate ignored



AtBegShi@Output ...ipout box
AtBeginShipoutBox
fi fi l.35 end{document}
pdfTeX warning (ext4): destination with the same
identifier (name{Part.2.1}) has been
already used, duplicate ignored



AtBegShi@Output ...ipout box
AtBeginShipoutBox
fi fi l.35 end{document}
] (./TestHyperref.aux) )




This looks like a strange behavior to me. Or have I done anything wrong?



Besides, the error completely disappears if I use, e.g., enumerates inside the Part environment, as in



...
begin{Part}
begin{enumerate}
item Prove that $1=0$.
end{enumerate}
end{Part}
...


Also, there's no error if I remove the hyperref package. Unfortunately, I need to use hyperref.



Any idea?










share|improve this question
























  • Note that this is not an error, only a warning. Actually, as long as you have only one reference to a part, there won't be a problem. Only if you have a reference to e.g. Part I in Exercise 1 and Part I in Exercise 2, the hyperlinks that hyperref creates will point to the same target.
    – Michael Ummels
    Mar 10 '11 at 14:44












  • @Michael Indeed, and the weirdest is that the warnings disappear altogether when I put an enumerate environment inside the Part (which is what I almost always do, since there are usually numbered questions in Parts).
    – gniourf_gniourf
    Mar 10 '11 at 14:52















up vote
12
down vote

favorite
3












Here is a minimal example:



documentclass{amsart}

usepackage{amsthm}
usepackage[pdftex]{hyperref}

newtheoremstyle{myexercise}{baselineskip}{baselineskip}{}{}{bfseries}{.}{ }{thmname{#1}thmnumber{ #2}thmnote{ (#3)}}
newtheoremstyle{mypart}{baselineskip}{baselineskip}{}{}{bfseries}{}{newline}{thmname{#1}thmnumber{ #2}thmnote{ -- #3}}

theoremstyle{myexercise}
newtheorem{Exo}{Exercise}
theoremstyle{mypart}
newtheorem{Part}{Part}[Exo]
renewcommand*thePart{Roman{Part}}

begin{document}
begin{Exo}[A cool exercise]
begin{Part}
label{p:ex1:I}
Prove that $1=0$.
end{Part}
begin{Part}
Deduce from Part~ref{p:ex1:I} that this exercise is wrong.
end{Part}
end{Exo}

begin{Exo}
begin{Part}
Let $a=b$. Deduce that $0=0$.
end{Part}
begin{Part}
Let $a=42$. For what values of $b$ do we have $a=b$?
end{Part}
end{Exo}
end{document}


The warning I get is the following:




pdf TeX warning (ext4): destination
with the same identifier
(name{Part.1.1}) has b een already
used, duplicate ignored



AtBegShi@Output ...ipout box
AtBeginShipoutBox
fi fi l.35 end{document}
pdfTeX warning (ext4): destination with the same
identifier (name{Part.2.1}) has been
already used, duplicate ignored



AtBegShi@Output ...ipout box
AtBeginShipoutBox
fi fi l.35 end{document}
] (./TestHyperref.aux) )




This looks like a strange behavior to me. Or have I done anything wrong?



Besides, the error completely disappears if I use, e.g., enumerates inside the Part environment, as in



...
begin{Part}
begin{enumerate}
item Prove that $1=0$.
end{enumerate}
end{Part}
...


Also, there's no error if I remove the hyperref package. Unfortunately, I need to use hyperref.



Any idea?










share|improve this question
























  • Note that this is not an error, only a warning. Actually, as long as you have only one reference to a part, there won't be a problem. Only if you have a reference to e.g. Part I in Exercise 1 and Part I in Exercise 2, the hyperlinks that hyperref creates will point to the same target.
    – Michael Ummels
    Mar 10 '11 at 14:44












  • @Michael Indeed, and the weirdest is that the warnings disappear altogether when I put an enumerate environment inside the Part (which is what I almost always do, since there are usually numbered questions in Parts).
    – gniourf_gniourf
    Mar 10 '11 at 14:52













up vote
12
down vote

favorite
3









up vote
12
down vote

favorite
3






3





Here is a minimal example:



documentclass{amsart}

usepackage{amsthm}
usepackage[pdftex]{hyperref}

newtheoremstyle{myexercise}{baselineskip}{baselineskip}{}{}{bfseries}{.}{ }{thmname{#1}thmnumber{ #2}thmnote{ (#3)}}
newtheoremstyle{mypart}{baselineskip}{baselineskip}{}{}{bfseries}{}{newline}{thmname{#1}thmnumber{ #2}thmnote{ -- #3}}

theoremstyle{myexercise}
newtheorem{Exo}{Exercise}
theoremstyle{mypart}
newtheorem{Part}{Part}[Exo]
renewcommand*thePart{Roman{Part}}

begin{document}
begin{Exo}[A cool exercise]
begin{Part}
label{p:ex1:I}
Prove that $1=0$.
end{Part}
begin{Part}
Deduce from Part~ref{p:ex1:I} that this exercise is wrong.
end{Part}
end{Exo}

begin{Exo}
begin{Part}
Let $a=b$. Deduce that $0=0$.
end{Part}
begin{Part}
Let $a=42$. For what values of $b$ do we have $a=b$?
end{Part}
end{Exo}
end{document}


The warning I get is the following:




pdf TeX warning (ext4): destination
with the same identifier
(name{Part.1.1}) has b een already
used, duplicate ignored



AtBegShi@Output ...ipout box
AtBeginShipoutBox
fi fi l.35 end{document}
pdfTeX warning (ext4): destination with the same
identifier (name{Part.2.1}) has been
already used, duplicate ignored



AtBegShi@Output ...ipout box
AtBeginShipoutBox
fi fi l.35 end{document}
] (./TestHyperref.aux) )




This looks like a strange behavior to me. Or have I done anything wrong?



Besides, the error completely disappears if I use, e.g., enumerates inside the Part environment, as in



...
begin{Part}
begin{enumerate}
item Prove that $1=0$.
end{enumerate}
end{Part}
...


Also, there's no error if I remove the hyperref package. Unfortunately, I need to use hyperref.



Any idea?










share|improve this question















Here is a minimal example:



documentclass{amsart}

usepackage{amsthm}
usepackage[pdftex]{hyperref}

newtheoremstyle{myexercise}{baselineskip}{baselineskip}{}{}{bfseries}{.}{ }{thmname{#1}thmnumber{ #2}thmnote{ (#3)}}
newtheoremstyle{mypart}{baselineskip}{baselineskip}{}{}{bfseries}{}{newline}{thmname{#1}thmnumber{ #2}thmnote{ -- #3}}

theoremstyle{myexercise}
newtheorem{Exo}{Exercise}
theoremstyle{mypart}
newtheorem{Part}{Part}[Exo]
renewcommand*thePart{Roman{Part}}

begin{document}
begin{Exo}[A cool exercise]
begin{Part}
label{p:ex1:I}
Prove that $1=0$.
end{Part}
begin{Part}
Deduce from Part~ref{p:ex1:I} that this exercise is wrong.
end{Part}
end{Exo}

begin{Exo}
begin{Part}
Let $a=b$. Deduce that $0=0$.
end{Part}
begin{Part}
Let $a=42$. For what values of $b$ do we have $a=b$?
end{Part}
end{Exo}
end{document}


The warning I get is the following:




pdf TeX warning (ext4): destination
with the same identifier
(name{Part.1.1}) has b een already
used, duplicate ignored



AtBegShi@Output ...ipout box
AtBeginShipoutBox
fi fi l.35 end{document}
pdfTeX warning (ext4): destination with the same
identifier (name{Part.2.1}) has been
already used, duplicate ignored



AtBegShi@Output ...ipout box
AtBeginShipoutBox
fi fi l.35 end{document}
] (./TestHyperref.aux) )




This looks like a strange behavior to me. Or have I done anything wrong?



Besides, the error completely disappears if I use, e.g., enumerates inside the Part environment, as in



...
begin{Part}
begin{enumerate}
item Prove that $1=0$.
end{enumerate}
end{Part}
...


Also, there's no error if I remove the hyperref package. Unfortunately, I need to use hyperref.



Any idea?







hyperref environments counters amsart amsthm






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Mar 10 '11 at 14:54

























asked Mar 9 '11 at 21:05









gniourf_gniourf

1,04211020




1,04211020












  • Note that this is not an error, only a warning. Actually, as long as you have only one reference to a part, there won't be a problem. Only if you have a reference to e.g. Part I in Exercise 1 and Part I in Exercise 2, the hyperlinks that hyperref creates will point to the same target.
    – Michael Ummels
    Mar 10 '11 at 14:44












  • @Michael Indeed, and the weirdest is that the warnings disappear altogether when I put an enumerate environment inside the Part (which is what I almost always do, since there are usually numbered questions in Parts).
    – gniourf_gniourf
    Mar 10 '11 at 14:52


















  • Note that this is not an error, only a warning. Actually, as long as you have only one reference to a part, there won't be a problem. Only if you have a reference to e.g. Part I in Exercise 1 and Part I in Exercise 2, the hyperlinks that hyperref creates will point to the same target.
    – Michael Ummels
    Mar 10 '11 at 14:44












  • @Michael Indeed, and the weirdest is that the warnings disappear altogether when I put an enumerate environment inside the Part (which is what I almost always do, since there are usually numbered questions in Parts).
    – gniourf_gniourf
    Mar 10 '11 at 14:52
















Note that this is not an error, only a warning. Actually, as long as you have only one reference to a part, there won't be a problem. Only if you have a reference to e.g. Part I in Exercise 1 and Part I in Exercise 2, the hyperlinks that hyperref creates will point to the same target.
– Michael Ummels
Mar 10 '11 at 14:44






Note that this is not an error, only a warning. Actually, as long as you have only one reference to a part, there won't be a problem. Only if you have a reference to e.g. Part I in Exercise 1 and Part I in Exercise 2, the hyperlinks that hyperref creates will point to the same target.
– Michael Ummels
Mar 10 '11 at 14:44














@Michael Indeed, and the weirdest is that the warnings disappear altogether when I put an enumerate environment inside the Part (which is what I almost always do, since there are usually numbered questions in Parts).
– gniourf_gniourf
Mar 10 '11 at 14:52




@Michael Indeed, and the weirdest is that the warnings disappear altogether when I put an enumerate environment inside the Part (which is what I almost always do, since there are usually numbered questions in Parts).
– gniourf_gniourf
Mar 10 '11 at 14:52










4 Answers
4






active

oldest

votes

















up vote
10
down vote













It's possible to use nested theorems with article.cls and ntheorem, now the problem seems to come from a conflict between amsart and hyperref. ntheorem has an option to avoid compatibility with hyperref.



documentclass{article}
usepackage[pdftex]{hyperref}
usepackage[hyperref]{ntheorem}

newtheorem{Exo}{Exercise}
newtheorem{Part}{Part}[Exo]
renewcommand*thePart{Roman{Part}}

begin{document}
begin{Exo}[A cool exercise]
begin{Part}
label{p:ex1:I}
Prove that $1=0$.
end{Part}
begin{Part}
Deduce from Part~ref{p:ex1:I} that this exercise is wrong.
end{Part}
end{Exo}

begin{Exo}
begin{Part}
Let $a=b$. Deduce that $0=0$.
end{Part}
begin{Part}
Let $a=42$. For what values of $b$ do we have $a=b$?
end{Part}
end{Exo}
end{document}


The problem seems to be between amsartand hyperref.






share|improve this answer























  • Thanks for your answer. I'm actually using (a modification of) the amsbook class. I don't quite understand why nesting several theorem environments should be a problem, since these environments are (supposedly from what I read from the LaTeX Companion) lists...
    – gniourf_gniourf
    Mar 10 '11 at 14:34










  • @gniourf-gniourf: Yes it's possible to nested theorem environments. I try my example with amsart and I get the chaos. So I'm perplex, I don't know amsart.cls and I suppose this class defines some theorem environments. I try my example with scrartcl.cls and it's fine
    – Alain Matthes
    Mar 10 '11 at 14:51










  • @gniourf-gniourf: In amsart.clsyou can find this : renewcommand{newtheorem} .... The class modifies newtheorem and perhaps` there is a little conflict between the class and hyperref. It's only a warning but it would be good to know why !
    – Alain Matthes
    Mar 10 '11 at 14:59


















up vote
4
down vote













After a lot of search, I finally found a simple solution: load hyperref before any ams package. Replacing the amsart document class by article class and pulling the hyperref package above the amsthm one solved my problem.



It does not always work, though. It can reduce the number of such warnings, and in some cases make them disappear.



For those who do want to use the amsart class that is still not a solution, though...






share|improve this answer






























    up vote
    0
    down vote













    I had this problem (seemingly) and found that the cause was not having loaded the siunitx package. I don't know why it had that effect, but it did.






    share|improve this answer








    New contributor




    Eric Anderson is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
    Check out our Code of Conduct.


















    • Hello, loading the siunitx package does not solve this problem here :( Also, as a sidenote, have you noticed that the question is older than 7 years? :D
      – Tom
      3 hours ago


















    up vote
    -1
    down vote













    try



    usepackage[hypertexnames=false]{hyperref} 





    share|improve this answer























      Your Answer








      StackExchange.ready(function() {
      var channelOptions = {
      tags: "".split(" "),
      id: "85"
      };
      initTagRenderer("".split(" "), "".split(" "), channelOptions);

      StackExchange.using("externalEditor", function() {
      // Have to fire editor after snippets, if snippets enabled
      if (StackExchange.settings.snippets.snippetsEnabled) {
      StackExchange.using("snippets", function() {
      createEditor();
      });
      }
      else {
      createEditor();
      }
      });

      function createEditor() {
      StackExchange.prepareEditor({
      heartbeatType: 'answer',
      convertImagesToLinks: false,
      noModals: true,
      showLowRepImageUploadWarning: true,
      reputationToPostImages: null,
      bindNavPrevention: true,
      postfix: "",
      imageUploader: {
      brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
      contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
      allowUrls: true
      },
      onDemand: true,
      discardSelector: ".discard-answer"
      ,immediatelyShowMarkdownHelp:true
      });


      }
      });














      draft saved

      draft discarded


















      StackExchange.ready(
      function () {
      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f13083%2fpdftex-warning-destination-with-same-identifier-has-been-already-used-duplicat%23new-answer', 'question_page');
      }
      );

      Post as a guest















      Required, but never shown

























      4 Answers
      4






      active

      oldest

      votes








      4 Answers
      4






      active

      oldest

      votes









      active

      oldest

      votes






      active

      oldest

      votes








      up vote
      10
      down vote













      It's possible to use nested theorems with article.cls and ntheorem, now the problem seems to come from a conflict between amsart and hyperref. ntheorem has an option to avoid compatibility with hyperref.



      documentclass{article}
      usepackage[pdftex]{hyperref}
      usepackage[hyperref]{ntheorem}

      newtheorem{Exo}{Exercise}
      newtheorem{Part}{Part}[Exo]
      renewcommand*thePart{Roman{Part}}

      begin{document}
      begin{Exo}[A cool exercise]
      begin{Part}
      label{p:ex1:I}
      Prove that $1=0$.
      end{Part}
      begin{Part}
      Deduce from Part~ref{p:ex1:I} that this exercise is wrong.
      end{Part}
      end{Exo}

      begin{Exo}
      begin{Part}
      Let $a=b$. Deduce that $0=0$.
      end{Part}
      begin{Part}
      Let $a=42$. For what values of $b$ do we have $a=b$?
      end{Part}
      end{Exo}
      end{document}


      The problem seems to be between amsartand hyperref.






      share|improve this answer























      • Thanks for your answer. I'm actually using (a modification of) the amsbook class. I don't quite understand why nesting several theorem environments should be a problem, since these environments are (supposedly from what I read from the LaTeX Companion) lists...
        – gniourf_gniourf
        Mar 10 '11 at 14:34










      • @gniourf-gniourf: Yes it's possible to nested theorem environments. I try my example with amsart and I get the chaos. So I'm perplex, I don't know amsart.cls and I suppose this class defines some theorem environments. I try my example with scrartcl.cls and it's fine
        – Alain Matthes
        Mar 10 '11 at 14:51










      • @gniourf-gniourf: In amsart.clsyou can find this : renewcommand{newtheorem} .... The class modifies newtheorem and perhaps` there is a little conflict between the class and hyperref. It's only a warning but it would be good to know why !
        – Alain Matthes
        Mar 10 '11 at 14:59















      up vote
      10
      down vote













      It's possible to use nested theorems with article.cls and ntheorem, now the problem seems to come from a conflict between amsart and hyperref. ntheorem has an option to avoid compatibility with hyperref.



      documentclass{article}
      usepackage[pdftex]{hyperref}
      usepackage[hyperref]{ntheorem}

      newtheorem{Exo}{Exercise}
      newtheorem{Part}{Part}[Exo]
      renewcommand*thePart{Roman{Part}}

      begin{document}
      begin{Exo}[A cool exercise]
      begin{Part}
      label{p:ex1:I}
      Prove that $1=0$.
      end{Part}
      begin{Part}
      Deduce from Part~ref{p:ex1:I} that this exercise is wrong.
      end{Part}
      end{Exo}

      begin{Exo}
      begin{Part}
      Let $a=b$. Deduce that $0=0$.
      end{Part}
      begin{Part}
      Let $a=42$. For what values of $b$ do we have $a=b$?
      end{Part}
      end{Exo}
      end{document}


      The problem seems to be between amsartand hyperref.






      share|improve this answer























      • Thanks for your answer. I'm actually using (a modification of) the amsbook class. I don't quite understand why nesting several theorem environments should be a problem, since these environments are (supposedly from what I read from the LaTeX Companion) lists...
        – gniourf_gniourf
        Mar 10 '11 at 14:34










      • @gniourf-gniourf: Yes it's possible to nested theorem environments. I try my example with amsart and I get the chaos. So I'm perplex, I don't know amsart.cls and I suppose this class defines some theorem environments. I try my example with scrartcl.cls and it's fine
        – Alain Matthes
        Mar 10 '11 at 14:51










      • @gniourf-gniourf: In amsart.clsyou can find this : renewcommand{newtheorem} .... The class modifies newtheorem and perhaps` there is a little conflict between the class and hyperref. It's only a warning but it would be good to know why !
        – Alain Matthes
        Mar 10 '11 at 14:59













      up vote
      10
      down vote










      up vote
      10
      down vote









      It's possible to use nested theorems with article.cls and ntheorem, now the problem seems to come from a conflict between amsart and hyperref. ntheorem has an option to avoid compatibility with hyperref.



      documentclass{article}
      usepackage[pdftex]{hyperref}
      usepackage[hyperref]{ntheorem}

      newtheorem{Exo}{Exercise}
      newtheorem{Part}{Part}[Exo]
      renewcommand*thePart{Roman{Part}}

      begin{document}
      begin{Exo}[A cool exercise]
      begin{Part}
      label{p:ex1:I}
      Prove that $1=0$.
      end{Part}
      begin{Part}
      Deduce from Part~ref{p:ex1:I} that this exercise is wrong.
      end{Part}
      end{Exo}

      begin{Exo}
      begin{Part}
      Let $a=b$. Deduce that $0=0$.
      end{Part}
      begin{Part}
      Let $a=42$. For what values of $b$ do we have $a=b$?
      end{Part}
      end{Exo}
      end{document}


      The problem seems to be between amsartand hyperref.






      share|improve this answer














      It's possible to use nested theorems with article.cls and ntheorem, now the problem seems to come from a conflict between amsart and hyperref. ntheorem has an option to avoid compatibility with hyperref.



      documentclass{article}
      usepackage[pdftex]{hyperref}
      usepackage[hyperref]{ntheorem}

      newtheorem{Exo}{Exercise}
      newtheorem{Part}{Part}[Exo]
      renewcommand*thePart{Roman{Part}}

      begin{document}
      begin{Exo}[A cool exercise]
      begin{Part}
      label{p:ex1:I}
      Prove that $1=0$.
      end{Part}
      begin{Part}
      Deduce from Part~ref{p:ex1:I} that this exercise is wrong.
      end{Part}
      end{Exo}

      begin{Exo}
      begin{Part}
      Let $a=b$. Deduce that $0=0$.
      end{Part}
      begin{Part}
      Let $a=42$. For what values of $b$ do we have $a=b$?
      end{Part}
      end{Exo}
      end{document}


      The problem seems to be between amsartand hyperref.







      share|improve this answer














      share|improve this answer



      share|improve this answer








      edited Oct 6 '13 at 12:26









      Ludovic C.

      6,02222455




      6,02222455










      answered Mar 9 '11 at 22:18









      Alain Matthes

      72.1k7158292




      72.1k7158292












      • Thanks for your answer. I'm actually using (a modification of) the amsbook class. I don't quite understand why nesting several theorem environments should be a problem, since these environments are (supposedly from what I read from the LaTeX Companion) lists...
        – gniourf_gniourf
        Mar 10 '11 at 14:34










      • @gniourf-gniourf: Yes it's possible to nested theorem environments. I try my example with amsart and I get the chaos. So I'm perplex, I don't know amsart.cls and I suppose this class defines some theorem environments. I try my example with scrartcl.cls and it's fine
        – Alain Matthes
        Mar 10 '11 at 14:51










      • @gniourf-gniourf: In amsart.clsyou can find this : renewcommand{newtheorem} .... The class modifies newtheorem and perhaps` there is a little conflict between the class and hyperref. It's only a warning but it would be good to know why !
        – Alain Matthes
        Mar 10 '11 at 14:59


















      • Thanks for your answer. I'm actually using (a modification of) the amsbook class. I don't quite understand why nesting several theorem environments should be a problem, since these environments are (supposedly from what I read from the LaTeX Companion) lists...
        – gniourf_gniourf
        Mar 10 '11 at 14:34










      • @gniourf-gniourf: Yes it's possible to nested theorem environments. I try my example with amsart and I get the chaos. So I'm perplex, I don't know amsart.cls and I suppose this class defines some theorem environments. I try my example with scrartcl.cls and it's fine
        – Alain Matthes
        Mar 10 '11 at 14:51










      • @gniourf-gniourf: In amsart.clsyou can find this : renewcommand{newtheorem} .... The class modifies newtheorem and perhaps` there is a little conflict between the class and hyperref. It's only a warning but it would be good to know why !
        – Alain Matthes
        Mar 10 '11 at 14:59
















      Thanks for your answer. I'm actually using (a modification of) the amsbook class. I don't quite understand why nesting several theorem environments should be a problem, since these environments are (supposedly from what I read from the LaTeX Companion) lists...
      – gniourf_gniourf
      Mar 10 '11 at 14:34




      Thanks for your answer. I'm actually using (a modification of) the amsbook class. I don't quite understand why nesting several theorem environments should be a problem, since these environments are (supposedly from what I read from the LaTeX Companion) lists...
      – gniourf_gniourf
      Mar 10 '11 at 14:34












      @gniourf-gniourf: Yes it's possible to nested theorem environments. I try my example with amsart and I get the chaos. So I'm perplex, I don't know amsart.cls and I suppose this class defines some theorem environments. I try my example with scrartcl.cls and it's fine
      – Alain Matthes
      Mar 10 '11 at 14:51




      @gniourf-gniourf: Yes it's possible to nested theorem environments. I try my example with amsart and I get the chaos. So I'm perplex, I don't know amsart.cls and I suppose this class defines some theorem environments. I try my example with scrartcl.cls and it's fine
      – Alain Matthes
      Mar 10 '11 at 14:51












      @gniourf-gniourf: In amsart.clsyou can find this : renewcommand{newtheorem} .... The class modifies newtheorem and perhaps` there is a little conflict between the class and hyperref. It's only a warning but it would be good to know why !
      – Alain Matthes
      Mar 10 '11 at 14:59




      @gniourf-gniourf: In amsart.clsyou can find this : renewcommand{newtheorem} .... The class modifies newtheorem and perhaps` there is a little conflict between the class and hyperref. It's only a warning but it would be good to know why !
      – Alain Matthes
      Mar 10 '11 at 14:59










      up vote
      4
      down vote













      After a lot of search, I finally found a simple solution: load hyperref before any ams package. Replacing the amsart document class by article class and pulling the hyperref package above the amsthm one solved my problem.



      It does not always work, though. It can reduce the number of such warnings, and in some cases make them disappear.



      For those who do want to use the amsart class that is still not a solution, though...






      share|improve this answer



























        up vote
        4
        down vote













        After a lot of search, I finally found a simple solution: load hyperref before any ams package. Replacing the amsart document class by article class and pulling the hyperref package above the amsthm one solved my problem.



        It does not always work, though. It can reduce the number of such warnings, and in some cases make them disappear.



        For those who do want to use the amsart class that is still not a solution, though...






        share|improve this answer

























          up vote
          4
          down vote










          up vote
          4
          down vote









          After a lot of search, I finally found a simple solution: load hyperref before any ams package. Replacing the amsart document class by article class and pulling the hyperref package above the amsthm one solved my problem.



          It does not always work, though. It can reduce the number of such warnings, and in some cases make them disappear.



          For those who do want to use the amsart class that is still not a solution, though...






          share|improve this answer














          After a lot of search, I finally found a simple solution: load hyperref before any ams package. Replacing the amsart document class by article class and pulling the hyperref package above the amsthm one solved my problem.



          It does not always work, though. It can reduce the number of such warnings, and in some cases make them disappear.



          For those who do want to use the amsart class that is still not a solution, though...







          share|improve this answer














          share|improve this answer



          share|improve this answer








          edited Nov 30 '16 at 5:34

























          answered Apr 12 '16 at 15:29









          user4929

          57547




          57547






















              up vote
              0
              down vote













              I had this problem (seemingly) and found that the cause was not having loaded the siunitx package. I don't know why it had that effect, but it did.






              share|improve this answer








              New contributor




              Eric Anderson is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
              Check out our Code of Conduct.


















              • Hello, loading the siunitx package does not solve this problem here :( Also, as a sidenote, have you noticed that the question is older than 7 years? :D
                – Tom
                3 hours ago















              up vote
              0
              down vote













              I had this problem (seemingly) and found that the cause was not having loaded the siunitx package. I don't know why it had that effect, but it did.






              share|improve this answer








              New contributor




              Eric Anderson is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
              Check out our Code of Conduct.


















              • Hello, loading the siunitx package does not solve this problem here :( Also, as a sidenote, have you noticed that the question is older than 7 years? :D
                – Tom
                3 hours ago













              up vote
              0
              down vote










              up vote
              0
              down vote









              I had this problem (seemingly) and found that the cause was not having loaded the siunitx package. I don't know why it had that effect, but it did.






              share|improve this answer








              New contributor




              Eric Anderson is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
              Check out our Code of Conduct.









              I had this problem (seemingly) and found that the cause was not having loaded the siunitx package. I don't know why it had that effect, but it did.







              share|improve this answer








              New contributor




              Eric Anderson is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
              Check out our Code of Conduct.









              share|improve this answer



              share|improve this answer






              New contributor




              Eric Anderson is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
              Check out our Code of Conduct.









              answered 3 hours ago









              Eric Anderson

              1012




              1012




              New contributor




              Eric Anderson is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
              Check out our Code of Conduct.





              New contributor





              Eric Anderson is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
              Check out our Code of Conduct.






              Eric Anderson is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
              Check out our Code of Conduct.












              • Hello, loading the siunitx package does not solve this problem here :( Also, as a sidenote, have you noticed that the question is older than 7 years? :D
                – Tom
                3 hours ago


















              • Hello, loading the siunitx package does not solve this problem here :( Also, as a sidenote, have you noticed that the question is older than 7 years? :D
                – Tom
                3 hours ago
















              Hello, loading the siunitx package does not solve this problem here :( Also, as a sidenote, have you noticed that the question is older than 7 years? :D
              – Tom
              3 hours ago




              Hello, loading the siunitx package does not solve this problem here :( Also, as a sidenote, have you noticed that the question is older than 7 years? :D
              – Tom
              3 hours ago










              up vote
              -1
              down vote













              try



              usepackage[hypertexnames=false]{hyperref} 





              share|improve this answer



























                up vote
                -1
                down vote













                try



                usepackage[hypertexnames=false]{hyperref} 





                share|improve this answer

























                  up vote
                  -1
                  down vote










                  up vote
                  -1
                  down vote









                  try



                  usepackage[hypertexnames=false]{hyperref} 





                  share|improve this answer














                  try



                  usepackage[hypertexnames=false]{hyperref} 






                  share|improve this answer














                  share|improve this answer



                  share|improve this answer








                  edited Jul 24 '17 at 17:33









                  Stefan Pinnow

                  19.2k83175




                  19.2k83175










                  answered Jul 24 '17 at 16:23









                  Zhenyao Sun

                  1




                  1






























                      draft saved

                      draft discarded




















































                      Thanks for contributing an answer to TeX - LaTeX Stack Exchange!


                      • Please be sure to answer the question. Provide details and share your research!

                      But avoid



                      • Asking for help, clarification, or responding to other answers.

                      • Making statements based on opinion; back them up with references or personal experience.


                      To learn more, see our tips on writing great answers.





                      Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


                      Please pay close attention to the following guidance:


                      • Please be sure to answer the question. Provide details and share your research!

                      But avoid



                      • Asking for help, clarification, or responding to other answers.

                      • Making statements based on opinion; back them up with references or personal experience.


                      To learn more, see our tips on writing great answers.




                      draft saved


                      draft discarded














                      StackExchange.ready(
                      function () {
                      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f13083%2fpdftex-warning-destination-with-same-identifier-has-been-already-used-duplicat%23new-answer', 'question_page');
                      }
                      );

                      Post as a guest















                      Required, but never shown





















































                      Required, but never shown














                      Required, but never shown












                      Required, but never shown







                      Required, but never shown

































                      Required, but never shown














                      Required, but never shown












                      Required, but never shown







                      Required, but never shown







                      Popular posts from this blog

                      Accessing regular linux commands in Huawei's Dopra Linux

                      Can't connect RFCOMM socket: Host is down

                      Kernel panic - not syncing: Fatal Exception in Interrupt