Documentation:Unix Section 7 - Revision history

Clipka: /* Known Bugs */ version number

2017-07-01T09:02:51Z

Known Bugs: version number

2016-10-02T10:50:02Z

deleted obsolete entry

2016-10-01T11:20:02Z

link changes

2013-02-05T13:31:13Z

additional cleanup

2013-02-05T13:27:55Z

removed an unnecessary and one redundant section

2011-12-07T05:28:55Z

itc

2011-09-06T07:48:10Z

aditional information

2010-12-16T01:42:37Z

one bug solved before release

2010-12-14T17:00:50Z

Feature Requests are not bugs

2010-12-14T16:55:56Z

Known Bugs

@@ Line 17: / Line 17: @@
 ===Known Bugs===
-<p>These items are <em>known bugs</em> with the <em>version 3.7</em> release:</p>
+<p>These items are <em>known bugs</em> with the <em>version 3.8</em> release:</p>
 <ol>
 <li>Due to problems with <em>X11</em> libraries, some special command line parameters are not available. However, a preview display can still be enabled if building from source and the optional [http://www.libsdl.org SDL] library is available to link against.</li>

@@ Line 20: / Line 20: @@
 <ol>
 <li>Due to problems with <em>X11</em> libraries, some special command line parameters are not available. However, a preview display can still be enabled if building from source and the optional [http://www.libsdl.org SDL] library is available to link against.</li>
 </ol>

@@ Line 27: / Line 27: @@
 ===Bug Reporting via our Bug Tracking System===
-<p>
+<p>Bug reports may be lodged about povray by using the [https://github.com/POV-Ray/povray/issues issue tracker] on GitHub. The issue tracker is monitored regularly by the POV-Ray development team and they will address any properly-lodged bug reports in the most timely manner possible.</p>
-<p>
+<p>You may like to remember, however, that no matter where you end up getting assistance from, users who show that they have looked in the documentation and read the [http://wiki.povray.org/content/Knowledgebase:POV-Ray_Questions_and_Tips POV-Ray Questions and Tips] first, will be much more likely to receive the response they want than someone who obviously has not done their homework. It's also important to check that the bug hasn't already been reported - if it has, and is still open, don't add a new report - if you have relevant information not already in the existing report, consider adding a comment.</p>
 <p>Any messages or reports sent to us may (not necessarily will, but may) be re-posted in our newsgroups, on USENET, or on our web site, if we consider it appropriate to do so.</p>

@@ Line 49: / Line 49: @@
 try removing parts until you have the minimum scene file that will cause the problem.</li>
 </ol>
 <!--<wikinav>--->
 <br>

@@ Line 15: / Line 15: @@
 <p>We <strong>strongly recommend</strong> that you check out the online version of the [http://wiki.povray.org/content/Knowledgebase:POV-Ray_Questions_and_Tips POV-Ray Questions and Tips] before submitting a report.</p>
 ===Known Bugs===
@@ Line 25: / Line 22: @@
 <li>There are <em>configure</em> phase issues that can cause problems compiling POV-Ray on FreeBSD systems. See this [http://bugs.povray.org/task/195 bug report] for more information, and ways to mitigate this issue.</li>
 </ol>
 ===Bug Reporting via Email===

@@ Line 8: / Line 8: @@
 <!--</wikitalk>--->
 ==Bug Reports==
-<!--<indexentry "Bug Reports">--->
+{{#indexentry:unix, Bug Reports}}
 <p>Before submitting any bug reports, make sure that the bug is not in the list of known bugs below. Please remember that the POV-Ray users who provide assistance on our news server are volunteers who give their time for free so you can enjoy this program for no charge. Keep this in mind when wording your message.</p>

@@ Line 20: / Line 20: @@
 ===Known Bugs===
-<p>This release <em>version 3.7</em> has two known problems:</p>
+<p>This release <em>version 3.7</em> has one known problem:</p>
 <ol>
 <li>Due to problems with <em>X11</em> some special command line parameters are not available. However, a preview display can still be enabled if building from source and the optional [http://www.libsdl.org SDL] library is available to link against.</li>
 </ol>

@@ Line 17: / Line 17: @@
 ===Feature Requests are not bugs===
-<p>The above may seem to be an obvious statement, but it's not so obvious that this section is unnecessary. Numerous people had been sending feature requests to the bug reporting email address, and this is in part one of the reasons why we no longer provide email support. If you  want to request a feature, discuss it in one of the povray groups on our private [http://www.povray.org/groups.html news server].</p>
+<p>The above may seem to be an obvious statement, but it's not so obvious that this section is unnecessary. Numerous people had been sending feature requests to the bug reporting email address, and this is in part one of the reasons why we no longer provide email support. If you  want to request a feature, discuss it in one of the povray groups on our private [http://news.povray.org/ news server].</p>
 ===Known Bugs===

@@ Line 23: / Line 23: @@
 <ol>
 <li>Due to problems with <em>X11</em> some special command line parameters are not available. However, a preview display can still be enabled if building from source and the optional [http://www.libsdl.org SDL] library is available to link against.</li>
-<li>Writing <em>JPEG</em> output files <code>+fj</code> causes an error at the end of the render.</li>
+<li>Writing <em>JPEG</em> output files (<code>+fj</code>) [http://bugs.povray.org/task/161 causes an error at the end of the render] on some 32-bit systems, due to differences in structure alignment between the libjpeg shipped with the OS distribution and the POV-Ray binary.</li>
 </ol>