[SOLVED] Possible bug with raytracing workbench in daily

Post here for help on using FreeCAD's graphical user interface (GUI).
Forum rules
and Helpful information
IMPORTANT: Please click here and read this first, before asking for help

Also, be nice to others! Read the FreeCAD code of conduct!
mrwusel
Posts: 13
Joined: Tue Sep 12, 2017 6:01 am

[SOLVED] Possible bug with raytracing workbench in daily

Postby mrwusel » Fri Aug 31, 2018 9:46 am

Hi,
as soon as I switch to the raytracing workbench and and click on new project (doesn't matter if POV or Lux), freecad crashes:

Code: Select all

FreeCAD 0.18, Libs: 0.18R14498 (Git)
© Juergen Riegel, Werner Mayer, Yorik van Havre 2001-2018
  #####                 ####  ###   ####  
  #                    #      # #   #   # 
  #     ##  #### ####  #     #   #  #   # 
  ####  # # #  # #  #  #     #####  #   # 
  #     #   #### ####  #    #     # #   # 
  #     #   #    #     #    #     # #   #  ##  ##  ##
  #     #   #### ####   ### #     # ####   ##  ##  ##

QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: Datei oder Verzeichnis nicht gefunden
Program received signal SIGSEGV, Segmentation fault.
#0  /lib/x86_64-linux-gnu/libc.so.6(+0x3ef20) [0x7f1dde9aef20]
#1  0x7f1ddf4a5868 in QObject::property(char const*) const from /usr/lib/x86_64-linux-gnu/libQtCore.so.4+0x18
#2  0x7f1d10e4ba44 in CmdRaytracingNewPovrayProject::activated(int) from /usr/lib/freecad-daily/lib/RaytracingGui.so+0x194
#3  0x7f1de1634f3b in Gui::Command::invoke(int) from /usr/lib/freecad-daily/lib/libFreeCADGui.so+0x7b
#4  0x7f1de1623b23 in Gui::ActionGroup::onActivated() from /usr/lib/freecad-daily/lib/libFreeCADGui.so+0x43
#5  0x7f1ddf4a5f70 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) from /usr/lib/x86_64-linux-gnu/libQtCore.so.4+0x4d0
#6  0x7f1ddf9b7dc2 in QAction::triggered(bool) from /usr/lib/x86_64-linux-gnu/libQtGui.so.4+0x42
#7  0x7f1ddf9b9113 in QAction::activate(QAction::ActionEvent) from /usr/lib/x86_64-linux-gnu/libQtGui.so.4+0x83
#8  /usr/lib/x86_64-linux-gnu/libQtGui.so.4(+0x5a0fa3) [0x7f1ddfd99fa3]
#9  0x7f1ddfd9a0f4 in QAbstractButton::mouseReleaseEvent(QMouseEvent*) from /usr/lib/x86_64-linux-gnu/libQtGui.so.4+0x74
#10  0x7f1ddfe600aa in QToolButton::mouseReleaseEvent(QMouseEvent*) from /usr/lib/x86_64-linux-gnu/libQtGui.so.4+0xa
#11  0x7f1ddfa14930 in QWidget::event(QEvent*) from /usr/lib/x86_64-linux-gnu/libQtGui.so.4+0x2a0
#12  0x7f1ddf9be03c in QApplicationPrivate::notify_helper(QObject*, QEvent*) from /usr/lib/x86_64-linux-gnu/libQtGui.so.4+0x8c
#13  0x7f1ddf9c5136 in QApplication::notify(QObject*, QEvent*) from /usr/lib/x86_64-linux-gnu/libQtGui.so.4+0x476
#14  0x7f1de160a1d8 in Gui::GUIApplication::notify(QObject*, QEvent*) from /usr/lib/freecad-daily/lib/libFreeCADGui.so+0x88
#15  0x7f1ddf4918ad in QCoreApplication::notifyInternal(QObject*, QEvent*) from /usr/lib/x86_64-linux-gnu/libQtCore.so.4+0x8d
#16  0x7f1ddf9c473d in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer<QWidget>&, bool) from /usr/lib/x86_64-linux-gnu/libQtGui.so.4+0x14d
#17  /usr/lib/x86_64-linux-gnu/libQtGui.so.4(+0x249452) [0x7f1ddfa42452]
#18  0x7f1ddfa41ce3 in QApplication::x11ProcessEvent(_XEvent*) from /usr/lib/x86_64-linux-gnu/libQtGui.so.4+0x16b3
#19  /usr/lib/x86_64-linux-gnu/libQtGui.so.4(+0x272592) [0x7f1ddfa6b592]
#20  /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_dispatch+0x2e7) [0x7f1dd803c287]
#21  /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x4c4c0) [0x7f1dd803c4c0]
#22  /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_iteration+0x2c) [0x7f1dd803c54c]
#23  0x7f1ddf4c220e in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) from /usr/lib/x86_64-linux-gnu/libQtCore.so.4+0x7e
#24  /usr/lib/x86_64-linux-gnu/libQtGui.so.4(+0x272666) [0x7f1ddfa6b666]
#25  0x7f1ddf49012f in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) from /usr/lib/x86_64-linux-gnu/libQtCore.so.4+0x3f
#26  0x7f1ddf490495 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) from /usr/lib/x86_64-linux-gnu/libQtCore.so.4+0x1b5
#27  0x7f1ddf496459 in QCoreApplication::exec() from /usr/lib/x86_64-linux-gnu/libQtCore.so.4+0x99
#28  0x7f1de15bae45 in Gui::Application::runApplication() from /usr/lib/freecad-daily/lib/libFreeCADGui.so+0x1895
#29  freecad-daily(main+0x6db) [0x55efed23741b]
#30  /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xe7) [0x7f1dde991b97]
#31  freecad-daily(_start+0x2a) [0x55efed2385ca]
System information:

Code: Select all

OS: Ubuntu 18.04.1 LTS
Word size of OS: 64-bit
Word size of FreeCAD: 64-bit
Version: 0.18.14498 (Git)
Build type: Release
Branch: master
Hash: e381e6b739a6b83b5f476546b64569cfa03a4e3a
Python version: 2.7.15rc1
Qt version: 4.8.7
Coin version: 4.0.0a
OCC version: 7.3.0
Locale: German/Germany (de_DE)
Last edited by mrwusel on Thu Sep 13, 2018 11:15 am, edited 1 time in total.
triplus
Posts: 8605
Joined: Mon Dec 12, 2011 4:45 pm

Re: Possible bug with raytracing workbench in daily

Postby triplus » Mon Sep 03, 2018 10:01 pm

Hi @mrwusel.

I can confirm the crash (a regression was likely introduced in the past couple of days). Please report the issue on the issue tracker:

https://www.freecadweb.org/tracker
mrwusel
Posts: 13
Joined: Tue Sep 12, 2017 6:01 am

Re: Possible bug with raytracing workbench in daily

Postby mrwusel » Wed Sep 05, 2018 7:24 am

Thanks for confirming. Bug can be found here:
https://www.freecadweb.org/tracker/view.php?id=3583
triplus
Posts: 8605
Joined: Mon Dec 12, 2011 4:45 pm

Re: Possible bug with raytracing workbench in daily

Postby triplus » Wed Sep 05, 2018 10:34 am

Thanks.

P.S. There were some CMake improvements added a few days back. And likely that could be the culprit.
wmayer
Site Admin
Posts: 14614
Joined: Thu Feb 19, 2009 10:32 am

Re: Possible bug with raytracing workbench in daily

Postby wmayer » Mon Sep 10, 2018 6:35 pm

triplus wrote:
Wed Sep 05, 2018 10:34 am
Thanks.

P.S. There were some CMake improvements added a few days back. And likely that could be the culprit.
Are the templates for .pov and .lux not installed or in the wrong location?
mrwusel
Posts: 13
Joined: Tue Sep 12, 2017 6:01 am

Re: Possible bug with raytracing workbench in daily

Postby mrwusel » Tue Sep 11, 2018 5:58 am

wmayer wrote:
Mon Sep 10, 2018 6:35 pm
...
Are the templates for .pov and .lux not installed or in the wrong location?
Where should I find these templates on a unix system? I have the daily and stable version installed.

EDIT: I found them but why is the daily version telling me, it's not finding them?

Code: Select all

find / -name "*.pov"
/usr/share/freecad-daily/Mod/Raytracing/ProjectStd.pov
/usr/share/freecad-daily/Mod/Raytracing/RadiosityNormal.pov
/usr/share/freecad-daily/Mod/Raytracing/RadiosityOutdoorHQ.pov
/usr/share/freecad/Mod/Raytracing/Templates/ProjectStd.pov
/usr/share/freecad/Mod/Raytracing/Templates/RadiosityNormal.pov
/usr/share/freecad/Mod/Raytracing/Templates/RadiosityOutdoorHQ.pov
wmayer
Site Admin
Posts: 14614
Joined: Thu Feb 19, 2009 10:32 am

Re: Possible bug with raytracing workbench in daily

Postby wmayer » Tue Sep 11, 2018 6:18 am

EDIT: I found them but why is the daily version telling me, it's not finding them?
There is indeed a problem when running make install that the templates are in the wrong directory (while make for a local build works).
/usr/share/freecad-daily/Mod/Raytracing/ProjectStd.pov
The path should be:
/usr/share/freecad-daily/Mod/Raytracing/Templates/ProjectStd.pov
wmayer
Site Admin
Posts: 14614
Joined: Thu Feb 19, 2009 10:32 am

Re: Possible bug with raytracing workbench in daily

Postby wmayer » Tue Sep 11, 2018 8:19 am

Should be fixed now: git commit dcedf9a4a77e7
mrwusel
Posts: 13
Joined: Tue Sep 12, 2017 6:01 am

Re: Possible bug with raytracing workbench in daily

Postby mrwusel » Wed Sep 12, 2018 7:43 am

Can confirm that it is working now. Thank you!
User avatar
Kunda1
Posts: 5139
Joined: Thu Jan 05, 2017 9:03 pm

Re: Possible bug with raytracing workbench in daily

Postby Kunda1 » Wed Sep 12, 2018 11:06 am

mrwusel wrote:
Wed Sep 12, 2018 7:43 am
Can confirm that it is working now. Thank you!
Please mark the first post title of this thread as [Solved]
Thanks!
Want to contribute back to FC? Checkout:
#lowhangingfruit | Use the Source, Luke. | How to Help FreeCAD | How to report FC bugs and features