Difference between revisions of "Documentation:Unix Section 7"

From POV-Wiki
Jump to navigation Jump to search
m (Protected "Documentation:Unix Section 7" [edit=sysop:move=sysop])
(→‎Known Bugs: version number)
 
(24 intermediate revisions by 2 users not shown)
Line 7: Line 7:
 
<br>
 
<br>
 
<!--</wikitalk>--->
 
<!--</wikitalk>--->
===Bug Reports===
+
==Bug Reports==
<!--<indexentry "Bug Reports">--->
+
{{#indexentry:unix, Bug Reports}}
  
<p>
+
<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>
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>
 
<p>
 
MAKE ABSOLUTELY SURE that the subject of your report isn't already covered in this document.
 
Questions that are already answered either in this help file, any README's, installation
 
notes, FAQ's, or other files supplied with this program will most likely not get the reply
 
you expect.
 
</p>
 
  
<p>
+
<p>MAKE ABSOLUTELY SURE that the subject of your report isn't already covered in this document. Questions that are already answered either in this help file, any README's, installation notes, FAQ's, or other files supplied with this program will most likely not get the reply you expect.</p>
We <strong>strongly recommend</strong> that you check out the
 
[http://www.povray.org/search/redirect?VFAQ|_new <span title="Opens A New Window!">online version of the POV-Ray Questions and Tips</span>]
 
before submitting a report. This is also a <!--<linkto "Questions and Tips">copy of the Questions and Tips included in this help file</linkto>--->[[Documentation:Tutorial Table of Contents#Questions and Tips|copy of the Questions and Tips included in this help file]]
 
but we recommend viewing the online version if possible as it's being continually updated.
 
</p>
 
  
===Feature Requests are not bugs===
+
<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>
<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
 
[http://www.povray.org/groups.html|_new <span title="Opens A New Window!">our private news server</span>].
 
</p>
 
  
 
===Known Bugs===
 
===Known Bugs===
<p>
+
<p>These items are <em>known bugs</em> with the <em>version 3.8</em> release:</p>
There are currently no known bugs specific for the Unix version.
+
<ol>
</p>
+
<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>
 +
 
 +
===Bug Reporting via Email===
 +
<p>Unfortunately, email bug reporting is no longer available due to the abuse of this facility by a number of users. You may only report bugs in POV-Ray by using the bugtracker mentioned in the next section.</p>
 +
 
 +
===Bug Reporting via our Bug Tracking System===
 +
<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>
Other known issues can be found in the [http://www.povray.org/search/redirect?VFAQ|_new <span title="Opens A New Window!">POV-Ray Questions and Tips</span>].
 
There is a <!--<linkto "Questions and Tips">copy of the 'Questions and Tips' included in this help file</linkto>--->[[Documentation:Tutorial Table of Contents#Questions and Tips|copy of the 'Questions and Tips' included in this help file]] but we
 
recommend viewing the online version if possible as it's being continually updated.
 
</p>
 
  
===Spelling===
+
<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>
<p>
 
As stated in the introduction, we use international English spelling in many parts of POV-Ray
 
for Unix. This means that many words that are normally spelt with a 'z' in American English
 
(such as minimized) are spelt with the English 's' (e.g. minimised). (We have actually received
 
flame email from folks who told us we couldn't spell).
 
</p>
 
  
===Bug Reporting via Email===
+
<p>You should not expect any reply to bug reports. If you wish to follow the progress of a bug, it's best to use the bug tracker (be sure to configure your account to receive notifications of replies to your bug). You can also request to be emailed when there are replies to an existing bug report.</p>
<p>
 
Unfortunately, email bug reporting is no longer available due to the abuse of this facility by
 
a number of users. You may only report bugs in POV-Ray by using the newsgroups mentioned in the
 
next section.
 
</p>
 
  
===Bug Reporting via our News Server===
+
<p>The minimum information to include in your bug report is:</p>
<p>
 
Bug reports may be lodged about POV-Ray by posting them in the appropriate group on
 
[http://news.povray.org/|_new <span title="Opens A New Window!">our news server</span>]. See
 
[http://www.povray.org/groups.html|_new <span title="Opens A New Window!">our list of groups</span>] for
 
information about the server, and particularly for
 
information as to which group to use. The newsgroups are monitored by a dedicated group of
 
folks known as the POV-Ray [http://tag.povray.org|_new <span title="Opens A New Window!">Technical Assistance Group</span>], or 'TAG' for short. The TAG will take note of any properly-lodged bug reports and
 
pass them on to the developers. They, and other users, will often lend new users a hand in
 
getting up to speed.
 
</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 docs and read the VFAQ etc will be much more
 
likely to receive the response they want than someone who obviously has not done so.
 
</p>
 
<p>
 
Any messages or reports sent to us may (not necessarily will, but may) be reposted by us in
 
our newsgroups, on USENET, or on our web site. If you do not wish your communication to be
 
posted in this manner, please do not send us any.
 
</p>
 
<p>
 
You should not expect any reply to bug reports.
 
</p>
 
<p>
 
The minimum information to include in your bug report is
 
  
 
<ol>
 
<ol>
 
<li>The version number of POV-Ray for Unix.</li>
 
<li>The version number of POV-Ray for Unix.</li>
 
+
<li>Your operating system or GNU/Linux distribution and version. It's surprising how many people fail to provide this basic piece of information. We need to know what version of Unix you are running.</li>
<li>Your operating system or GNU/Linux distribution and version. It's surprising how many people
 
fail to provide this basic piece of information. We need to know what version of Unix you are
 
running.</li>
 
 
 
 
<li>Your computer; what processor and how much memory.</li>
 
<li>Your computer; what processor and how much memory.</li>
 
 
<li>A complete description of the problem and what led up to it. It will make it a lot easier to
 
<li>A complete description of the problem and what led up to it. It will make it a lot easier to
 
track down if you can include a scene file that will cause the problem. If the file is large,
 
track down if you can include a scene file that will cause the problem. If the file is large,
 
try removing parts until you have the minimum scene file that will cause the problem.</li>
 
try removing parts until you have the minimum scene file that will cause the problem.</li>
 
</ol>
 
</ol>
</p>
 
 
<p class="Warning">
 
<strong>Note:</strong> If posting on the news group or emailing someone for support, <em>never, ever</em>
 
include file attachments without asking first. The only exception is posting to a specifically-
 
designated binaries group on the POV-Ray news server.</p>
 
 
<!--<wikinav>--->
 
<!--<wikinav>--->
 
<br>
 
<br>

Latest revision as of 09:02, 1 July 2017

This document is protected, so submissions, corrections and discussions should be held on this documents talk page.


Bug Reports

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.

MAKE ABSOLUTELY SURE that the subject of your report isn't already covered in this document. Questions that are already answered either in this help file, any README's, installation notes, FAQ's, or other files supplied with this program will most likely not get the reply you expect.

We strongly recommend that you check out the online version of the POV-Ray Questions and Tips before submitting a report.

Known Bugs

These items are known bugs with the version 3.8 release:

  1. Due to problems with X11 libraries, some special command line parameters are not available. However, a preview display can still be enabled if building from source and the optional SDL library is available to link against.

Bug Reporting via Email

Unfortunately, email bug reporting is no longer available due to the abuse of this facility by a number of users. You may only report bugs in POV-Ray by using the bugtracker mentioned in the next section.

Bug Reporting via our Bug Tracking System

Bug reports may be lodged about povray by using the 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.

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 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.

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.

You should not expect any reply to bug reports. If you wish to follow the progress of a bug, it's best to use the bug tracker (be sure to configure your account to receive notifications of replies to your bug). You can also request to be emailed when there are replies to an existing bug report.

The minimum information to include in your bug report is:

  1. The version number of POV-Ray for Unix.
  2. Your operating system or GNU/Linux distribution and version. It's surprising how many people fail to provide this basic piece of information. We need to know what version of Unix you are running.
  3. Your computer; what processor and how much memory.
  4. A complete description of the problem and what led up to it. It will make it a lot easier to track down if you can include a scene file that will cause the problem. If the file is large, try removing parts until you have the minimum scene file that will cause the problem.


Benchmark Rendering Mode Speed Considerations


This document is protected, so submissions, corrections and discussions should be held on this documents talk page.