Bug submission guidelines

[mkment]

Tried to write some bug report. However, I always got a message the FreeCAD information field was empty. Still, it wasn't empy as I pasted the information directly copied from FreeCAD. I also filled in all the other fields marked as mandatory. What else could be wrong?

[Kunda1]

Tried to write some bug report. However, I always got a message the FreeCAD information field was empty. Still, it wasn't empy as I pasted the information directly copied from FreeCAD. I also filled in all the other fields marked as mandatory. What else could be wrong?

Did you add something that looks like this in to the FreeCAD Information field ?

Code: Select all

OS: Manjaro Linux (XFCE/xfce)
Word size of OS: 64-bit
Word size of FreeCAD: 64-bit
Version: 0.19.18522 (Git) AppImage
Build type: Release
Branch: master
Hash: e0bb5701f6cb3936501afe59527cbce03017beda
Python version: 3.7.3
Qt version: 5.12.5
Coin version: 4.0.0a
OCC version: 7.3.0
Locale: English/United States (en_US)

[Naheulf]

5. Include all possible FreeCAD error messages. When something wrong happens in FreeCAD, error messages are often printed, that can give precious information to the developer about what happened. The two places you should check for such error messages in FreeCAD are the Report window (menu View->Views->Report view), the python console (menu View->Views->Python console). Make sure to include as much error text as possible.

The "Report view" is no longer in View->Views->Report view but in View->Panels->Report view.
It's same for Python console.

Yorik can you edit your first message accordingly ?

OS: Linux (Ubuntu)
Version: 0.18.16093 (Git)
Hash: 690774c0effe4fd7b8d2b5e2fb2b8c8d145e21ce
Locale: English/UnitedStates (en_US)

[_Vi]

Can't register at bug tracker (e-mails don't arrive), so dumping a crash just here:

Code: Select all

Program received signal SIGSEGV, Segmentation fault.
#0  /lib/x86_64-linux-gnu/libc.so.6(+0x37840) [0x7f4565fc9840]
#1  0x7f44d8f05bba in CmdSketcherConstrainAngle::activated(int) from /tmp/.mount_FreeCAUaJh6s/usr/lib/SketcherGui.so+0x97a
#2  0x7f456b7b614c in Gui::Command::invoke(int) from /tmp/.mount_FreeCAUaJh6s/usr/bin/../lib/libFreeCADGui.so+0x4c
#3  0x7f4566d628d1 in QMetaObject::activate(QObject*, int, int, void**) from /tmp/.mount_FreeCAUaJh6s/usr/bin/../lib/libQt5Core.so.5+0x2c1
#4  0x7f45676dd372 in QAction::triggered(bool) from /tmp/.mount_FreeCAUaJh6s/usr/bin/../lib/libQt5Widgets.so.5+0x32
#5  0x7f45676e009d in QAction::activate(QAction::ActionEvent) from /tmp/.mount_FreeCAUaJh6s/usr/bin/../lib/libQt5Widgets.so.5+0x5d
#6  /tmp/.mount_FreeCAUaJh6s/usr/bin/../lib/libQt5Widgets.so.5(+0x25952d) [0x7f45677e252d]
#7  0x7f45677e2664 in QAbstractButton::mouseReleaseEvent(QMouseEvent*) from /tmp/.mount_FreeCAUaJh6s/usr/bin/../lib/libQt5Widgets.so.5+0xd4
#8  0x7f45678a964a in QToolButton::mouseReleaseEvent(QMouseEvent*) from /tmp/.mount_FreeCAUaJh6s/usr/bin/../lib/libQt5Widgets.so.5+0xa
#9  0x7f456772973a in QWidget::event(QEvent*) from /tmp/.mount_FreeCAUaJh6s/usr/bin/../lib/libQt5Widgets.so.5+0x96a
#10  0x7f45678a9729 in QToolButton::event(QEvent*) from /tmp/.mount_FreeCAUaJh6s/usr/bin/../lib/libQt5Widgets.so.5+0x69
#11  0x7f45676e6c6c in QApplicationPrivate::notify_helper(QObject*, QEvent*) from /tmp/.mount_FreeCAUaJh6s/usr/bin/../lib/libQt5Widgets.so.5+0x9c
#12  0x7f45676ebb5d in QApplication::notify(QObject*, QEvent*) from /tmp/.mount_FreeCAUaJh6s/usr/bin/../lib/libQt5Widgets.so.5+0xc6d
#13  0x7f456b78d371 in Gui::GUIApplication::notify(QObject*, QEvent*) from /tmp/.mount_FreeCAUaJh6s/usr/bin/../lib/libFreeCADGui.so+0x41
#14  0x7f4566d38425 in QCoreApplication::notifyInternal2(QObject*, QEvent*) from /tmp/.mount_FreeCAUaJh6s/usr/bin/../lib/libQt5Core.so.5+0x75
#15  0x7f45676ea860 in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer<QWidget>&, bool) from /tmp/.mount_FreeCAUaJh6s/usr/bin/../lib/libQt5Widgets.so.5+0x1a0
#16  /tmp/.mount_FreeCAUaJh6s/usr/bin/../lib/libQt5Widgets.so.5(+0x1b9cd1) [0x7f4567742cd1]
#17  /tmp/.mount_FreeCAUaJh6s/usr/bin/../lib/libQt5Widgets.so.5(+0x1bc2c3) [0x7f45677452c3]
#18  0x7f45676e6c6c in QApplicationPrivate::notify_helper(QObject*, QEvent*) from /tmp/.mount_FreeCAUaJh6s/usr/bin/../lib/libQt5Widgets.so.5+0x9c
#19  0x7f45676eb2ea in QApplication::notify(QObject*, QEvent*) from /tmp/.mount_FreeCAUaJh6s/usr/bin/../lib/libQt5Widgets.so.5+0x3fa
#20  0x7f456b78d371 in Gui::GUIApplication::notify(QObject*, QEvent*) from /tmp/.mount_FreeCAUaJh6s/usr/bin/../lib/libFreeCADGui.so+0x41
#21  0x7f4566d38425 in QCoreApplication::notifyInternal2(QObject*, QEvent*) from /tmp/.mount_FreeCAUaJh6s/usr/bin/../lib/libQt5Core.so.5+0x75
#22  0x7f45670dc7db in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) from /tmp/.mount_FreeCAUaJh6s/usr/bin/../lib/libQt5Gui.so.5+0x40b
#23  0x7f45670ddf75 in QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*) from /tmp/.mount_FreeCAUaJh6s/usr/bin/../lib/libQt5Gui.so.5+0x115
#24  0x7f45670bf74b in QWindowSystemInterface::sendWindowSystemEvents(QFlags<QEventLoop::ProcessEventsFlag>) from /tmp/.mount_FreeCAUaJh6s/usr/bin/../lib/libQt5Gui.so.5+0x7b
#25  /tmp/.mount_FreeCAUaJh6s/usr/lib/libQt5XcbQpa.so.5(+0xa05d0) [0x7f45601895d0]
#26  /tmp/.mount_FreeCAUaJh6s/usr/lib/libglib-2.0.so.0(+0x569be) [0x7f45632c59be]
#27  /tmp/.mount_FreeCAUaJh6s/usr/lib/libglib-2.0.so.0(g_main_context_dispatch+0x33) [0x7f45632c6826]
#28  /tmp/.mount_FreeCAUaJh6s/usr/lib/libglib-2.0.so.0(+0x57a0b) [0x7f45632c6a0b]
#29  /tmp/.mount_FreeCAUaJh6s/usr/lib/libglib-2.0.so.0(g_main_context_iteration+0x4a) [0x7f45632c6acf]
#30  0x7f4566d8998c in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) from /tmp/.mount_FreeCAUaJh6s/usr/bin/../lib/libQt5Core.so.5+0x5c
#31  0x7f4566d3653b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) from /tmp/.mount_FreeCAUaJh6s/usr/bin/../lib/libQt5Core.so.5+0xfb
#32  0x7f4566d3e466 in QCoreApplication::exec() from /tmp/.mount_FreeCAUaJh6s/usr/bin/../lib/libQt5Core.so.5+0x86
#33  0x7f456b72a25c in Gui::Application::runApplication() from /tmp/.mount_FreeCAUaJh6s/usr/bin/../lib/libFreeCADGui.so+0x16bc
#34  /tmp/.mount_FreeCAUaJh6s/usr/bin/FreeCAD(main+0x6c9) [0x403829]
#35  /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xeb) [0x7f4565fb609b]
#36  /tmp/.mount_FreeCAUaJh6s/usr/bin/FreeCAD() [0x404699]

When trying to add an angle constraint to this project: https://vi-server.org/pub/freecadtest.FCStd

Version is FreeCAD_0.18-16146-Linux-Conda_Py3Qt5_glibc2.12-x86_64.AppImage

[chrisb]

Hi and welcome to the forum!

Can't register at bug tracker (e-mails don't arrive), so dumping a crash just here:

That's good to hear, because you should have opened a topic here anyway to discuss your issue before creating a ticket.

When trying to add an angle constraint to this project: https://vi-server.org/pub/freecadtest.FCStd

Please retry with a current 0.19 version. I tried here and had no issues. If the problem persists
- check if you can add other dimensions
- tell us if it happens on all angles, if not between which lines did you apply it
- attach your full FreeCAD info as described in the IMPORTANT forum rules linked above.

[dapineau]

I reinstall completely FreeCad,
go to Préférence,
click on CFD at left,
click on Install blueCFD-Core................it appears to install may be, correctly
click on Install cfMesh:..................massage.......can't open file ...etc
click on Install HiSA:..................same thing...message: can't open files

OK in some forum, some say, ...not a problem it works.

But no.: I can't see OpenFOAM in the model window, I only see CfdSolver, and I can't run this solver, nothing can do with that.

I don't see on the web any example using CfdSolver....

Daniel
(excuse my English I am french)

[pilat66]

Just add the "forum topic" field to the bugtracker and there will be no error messages without discussion.

[Smiling_user]

After several unsuccessful "bug" submissions and discussions here on forum, came to conclusion:

Recognizing a bug - presupposes the knowledge of correct functioning, unless there is an obvious program crash, halt, file destruction etc.

While reading the documentation - noticed, that majority of tools are described from the side of goals and outcomes, not from application prerequisites. So if you get a weired result there is no ground to judge of mistake or bug.

So the general conclusion is: The description of tool should include
1. Outcomes
2. usage conditions
3. limitations
4. possible precautions
5. Sequence of steps to use.

Example:
PartDesign>Sweep
1. results in a detail formed along guide-line( profile, spiral and others)
2. 2D shape and guide inside active (highlighted) "Body-container" of PartDesign WB.
3. If the path contains several sections - they must be connected as start-to-end
4. ??????? 2D-shape and guide must be inside the same body??
5. WB-PartDesign:
-> make / activate a body
-> in either sequence make a 2D shape and prepare a guide line.
-> select the 2D-shape, press [sweep], select-add the guide line to the list of guides.
-> press enter

// If the data of this kind is not present - what the way could be to judge the bug?

[chrisb]

This topic is the wrong place to discuss the documentation, so if this discussion continues it may better be moved to the wiki forum.

So the general conclusion is: The description of tool should include
1. Outcomes
2. usage conditions
3. limitations
4. possible precautions
5. Sequence of steps to use.

Example:
PartDesign>Sweep
1. results in a detail formed along guide-line( profile, spiral and others)
2. 2D shape and guide inside active (highlighted) "Body-container" of PartDesign WB.
3. If the path contains several sections - they must be connected as start-to-end
4. ??????? 2D-shape and guide must be inside the same body??

1. It's all there. Have a look at the very clear image.
2. The wiki is no tutorial. So the information may be spread over several pages, in this case e.g. in the docs of a Body. This could be improved, but it's not wrong or missing.
3. I don't understand what you mean by "they must be connected as start-to-end". Neither has the first section to be at the start nor the last section at the end of the path - although they will be in most cases.
4. Seems to be included in number 2 (except for the bulk of question marks)

[BIM Bo]

With all due respect, I have to state that neither yorick, nor Kunda1, nor chrisb et al. are qualified enough to set up a FreeCAD bug reporting process.

And why is that? It's simple: You guys are way too knowledgeable with FreeCAD, know your ways and therefore probably already intuitively are able to re-route your way around problems that do occur with this extremely complex application. And/or have set up local environments that somehow magically work and are not even able to reproduce many problems occuring with the plebs.

I am stumbling over FreeCAD bugs at every 3rd click of the mouse, but am extremely reluctant reporting them via the "defined process" which is tiresome and wrong right from the beginning.

e.g. "search tracker and forum" evidently is not the 1st step. The 1st step seems to be "make sure you use the 0.19 development version and not the 0.18 'stable' version". Still, on the webpage, the 0.18 version is the default that is presented. As is the package e.g. in the (Linux) distributions.

I know it would be nice and ideal to have a stable branch and a development branch, but for the time being it seems development is the new stable, so might as well adapt to that. At some point I thought about simply catching a screencast of me working with FreeCAD and cut it together and post on YouTube so devs would have some action movie to watch with their friends and a bowl of popcorn.

----

So in this case "not qualified enough" == "way too knowledgeable". Sometimes also translated as "project blindness". I have therefore decided to make my own bug reporting process: I will set up an own thread in Users > Open Discussion simply ad hoc showing what I - the Newb - consider to be bugs. I do not expect that they will get fixed in a timely manner (or at all), but I need to get them a) off my chest b) have at least the feeling that I did contribute with some testing.

Testing done by the - still - untainted. Because even if from the point of view of the upper echelons here it is me who might be using FreeCAD "the wrong way", the feedback actually still might be valuable. As a newbie I most certainly do not intuitively work around pitfalls and bugs that do exist. And devs might have an interest in seeing those pitfalls lurking there exposed with someone elses eyes.