Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#37664 - [luxblend25] luxrender crash on render

Attached to Project: Community Packages
Opened by Matti Hameister (-Nuke-) - Wednesday, 06 November 2013, 17:30 GMT
Last edited by Lukas Jirkovsky (6xx) - Thursday, 05 December 2013, 19:00 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Lukas Jirkovsky (6xx)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
luxrender crashes (segmentation fault) with the exported file from blender.

Steps to reproduce:
Install luxblend25, activate the plugin in Blender, set the path to the luxrender installation (/usr/bin), try to render the scene. The luxrender windows opens and closes with no result.


Additional info:
community/luxblend25 1.3-1
community/luxrender 1.3-1

Logs:

Blender says:

[Lux 2013-Nov-06 18:21:57] INFO: Creating LuxRender context
[Lux 2013-Nov-06 18:21:57] INFO: Exporting render settings
[Lux 2013-Nov-06 18:21:57] INFO: Exporting geometry
[Lux 2013-Nov-06 18:21:57] Binary PLY file written: /tmp//untitled/Scene/00001/Cube_0000_m000.ply
[Lux 2013-Nov-06 18:21:57] INFO: Exporting lights
[Lux 2013-Nov-06 18:21:57] INFO: Export finished
[Lux 2013-Nov-06 18:21:57] Wrote scene files
[Lux 2013-Nov-06 18:21:57] /tmp//untitled.Scene.00001.lxs
[Lux 2013-Nov-06 18:21:57] /tmp/untitled/Scene/00001/LuxRender-Materials.lxm
[Lux 2013-Nov-06 18:21:57] /tmp/untitled/Scene/00001/LuxRender-Geometry.lxo
[Lux 2013-Nov-06 18:21:57] /tmp/untitled/Scene/00001/LuxRender-Volumes.lxv
[Lux 2013-Nov-06 18:21:57] Starting LuxRender
luxrender_path: /usr/bin
[Lux 2013-Nov-06 18:21:57] Launching: ['/usr/bin/luxrender', '--logconsole', '/tmp/untitled.Scene.00001.lxs']
[Lux 2013-Nov-06 18:21:57 INFO : 0] Lux version 1.3 of Nov 1 2013 at 10:22:55
[Lux 2013-Nov-06 18:21:57 INFO : 0] Threads: 8
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
[Lux 2013-Nov-06 18:21:57 INFO : 0] Freeing resources.
[Lux 2013-Nov-06 18:21:57 INFO : 0] Freeing resources.
[Lux 2013-Nov-06 18:21:57 INFO : 0] Server requests interval: 180 seconds
[Lux 2013-Nov-06 18:21:57 INFO : 0] Loading scene file: '/tmp/untitled.Scene.00001.lxs'...
[Lux 2013-Nov-06 18:21:57 INFO : 0] Shape 'Cube': Loading PLY mesh file: 'untitled/Scene/00001/Cube_0000_m000.ply'...
[Lux 2013-Nov-06 18:21:57 INFO : 0] Shape 'Cube': Mesh: splitting 6 quads
[Lux 2013-Nov-06 18:21:57 INFO : 0] Metropolis cooldown during first 79115 samples
[Lux 2013-Nov-06 18:21:58] Final render result (960x540)
[Lux 2013-Nov-06 18:21:58] ERROR: Could not load render result from untitled.Scene.00001.png



If I run luxrender directly from console with gdb:

Starting program: /usr/bin/luxrender -l -t 1 untitled.Scene.00001.lxs
warning: no loadable sections found in added symbol-file system-supplied DSO at 0x7ffff7ffa000
warning: Could not load shared library symbols for linux-vdso.so.1.
Do you need "set solib-search-path" or "set sysroot"?
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Lux 2013-Nov-06 18:26:39 INFO : 0] Lux version 1.3 of Nov 1 2013 at 10:22:55
[Lux 2013-Nov-06 18:26:39 INFO : 0] Threads: 1
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
[Lux 2013-Nov-06 18:26:39 INFO : 0] Freeing resources.
[Lux 2013-Nov-06 18:26:39 INFO : 0] Freeing resources.
[Lux 2013-Nov-06 18:26:39 INFO : 0] Server requests interval: 180 seconds
[Lux 2013-Nov-06 18:26:39 INFO : 0] Loading scene file: '/tmp/untitled.Scene.00001.lxs'...
[New Thread 0x7fffe496f700 (LWP 16611)]
[Lux 2013-Nov-06 18:26:39 INFO : 0] Shape 'Cube': Loading PLY mesh file: 'untitled/Scene/00001/Cube_0000_m000.ply'...
[Lux 2013-Nov-06 18:26:39 INFO : 0] Shape 'Cube': Mesh: splitting 6 quads
[Lux 2013-Nov-06 18:26:39 INFO : 0] Metropolis cooldown during first 79115 samples
[New Thread 0x7fffde662700 (LWP 16612)]
[New Thread 0x7fffdde61700 (LWP 16613)]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffde662700 (LWP 16612)]
0x00007ffff70e9bfb in ?? () from /usr/lib/liblux.so
This task depends upon

Closed by  Lukas Jirkovsky (6xx)
Thursday, 05 December 2013, 19:00 GMT
Reason for closing:  Fixed
Additional comments about closing:  fixed in luxrender-1.3.1-3 in [testing]
Comment by Harri (episyron) - Thursday, 07 November 2013, 06:11 GMT
Confirmed. And this caught my eye when starting blender:

[Lux 2013-Nov-07 08:00:24] WARNING: Binary pylux module not available! Visit http://www.luxrender.net/ to obtain one for your system.
[Lux 2013-Nov-07 08:00:24] (ImportError was: /usr/lib/libboost_python.so.1.54.0: undefined symbol: PyClass_Type)
Comment by Matti Hameister (-Nuke-) - Monday, 11 November 2013, 23:34 GMT
Yeah, I have this message too, but I found a partial solution for this one.

with:
sed -i 's|python\ R| python3\ R|' cmake/Dependencies.cmake

I changed the Boost_Component in this cmake-File from python to python3, so that pylux.so is linked against libboost_python3 instead of libboost_python.

This seems to work, the error is gone, but Blender is now crashing, when it tries to load the material preview. I think this is because of luxrender crashes.

Also, simply upgrading to Luxrender 1.3.1 does not solve the problem.
Comment by Matti Hameister (-Nuke-) - Tuesday, 12 November 2013, 15:30 GMT
According to the bugtracker from luxrender, it may be a problem with boost. They support only boost <= 1.47. http://www.luxrender.net/mantis/view.php?id=1420
Comment by Lukas Jirkovsky (6xx) - Friday, 15 November 2013, 10:45 GMT
The pylux problem is unrelated, it's actually problem with boost, which should be rebuilt against new python. Regarding the boost support: they don't support boost > 1.47 officially, but it always worked until 1.3, so that is likely unrelated. Right now I'm in the process of trying to find the bug.
Comment by Lukas Jirkovsky (6xx) - Friday, 15 November 2013, 11:35 GMT
The crash has been reported upstream: http://www.luxrender.net/mantis/view.php?id=1443
Comment by Matti Hameister (-Nuke-) - Wednesday, 04 December 2013, 17:02 GMT
I compiled luxrender with clang and now it is running fine, as far as I can see. Boost seems to use clang in version 1.55 also.

I added
export CC=clang
export CPP=clang
export CXX=clang++

before the cmake call in the PKGBUILD.

Loading...