noframenumbering does not seem to work [closed]

I have an issue in Kile 2.0.85 (It's my institute's computer, so I can't update it myself).

I have a beamer project for a presentation. I write:

\begin{frame}[noframenumbering]{2 Inputs}


and it seems to work (I don't see any errors or warning marking the option as unknown), but in the pdf presentation the counter of the slides increases nevertheless.

Anyone knows what the problem is? Outdated version of Kile or any other package? Maybe I have to include some extra package? Any other ideas?

Thanks.

(Note: I'm very new to the site. If the title, content, or tags of this question are inappropriate, feel free to edit, or to ask me additional information!)

Edit: Here is a minimal example. (Did I do it correctly?)

\documentclass{beamer}
\usepackage[utf8x]{inputenc}
\usepackage{default}

\begin{document}
\begin{frame}{2 Inputs}
These should look like
\end{frame}

These should look like the same page
\end{frame}

\end{document}


When I compile this example, the counters at the bottom right corner are increasing:

closed as off-topic by user36296, Stefan Pinnow, Zarko, Stefan Kottwitz♦Dec 26 '16 at 21:22

• This question does not fall within the scope of TeX, LaTeX or related typesetting systems as defined in the help center.
If this question can be reworded to fit the rules in the help center, please edit the question.

• Welcome to TeX.SX. Please provide a Minimal Working Example, otherwise it will be difficult to users to answer your question. Please see meta.tex.stackexchange.com/questions/228/… – RicoRally Nov 24 '14 at 10:33
• Is it just an issue of Kile? Does your tex-File compile as expected converting it without Kile? – crixstox Nov 24 '14 at 10:53
• @crixstox No, also pdflatex (from terminal) does the same. – geodude Nov 24 '14 at 14:34
• @geodude Your MWE works fine and gives the expected result. Have you compiled it twice? If so, I guess that your beamer packages is too old. (I think that the option nuoframenumber was introduce in version 3.08)- – crixstox Nov 24 '14 at 18:02
• I'm voting to close this question as probably caused by old package version – user36296 Dec 26 '16 at 20:55