Description of problem: open simple low poly test scene, enable Lux addon, change renderer to "Luxrender", hit "Redner", got error about wrong path (seems default is windows with C:\blablabla), change it to /usr/bin, press "Render" again, it start do something, preparing data etc, then for a moment pop external Luxrender window and immediately disappear with abrt notification. Version-Release number of selected component: LuxRender-1.0-11.fc19 Additional info: reporter: libreport-2.1.5 backtrace_rating: 4 cmdline: /usr/bin/luxrender --logconsole /tmp/my_psorcube_Cycles_spectral_mlt_example_white_err.Scene.00001.lxs crash_function: lux::Lambertian::F executable: /usr/bin/luxrender kernel: 3.9.9-301.fc19.x86_64 runlevel: N 5 uid: 1000 var_log_messages: Jul 9 16:33:49 localhost abrt[11222]: Saved core dump of pid 11211 (/usr/bin/luxrender) to /var/tmp/abrt/ccpp-2013-07-09-16:33:49-11211 (153362432 bytes) Truncated backtrace: Thread no. 1 (7 frames) #0 lux::Lambertian::F at /usr/src/debug/lux-a041e87b9732/core/reflection/bxdf/lambertian.cpp:33 #1 lux::SingleBSDF::F at /usr/src/debug/lux-a041e87b9732/core/reflection/bsdf/singlebsdf.cpp:82 #2 lux::BidirIntegrator::EvalPath at /usr/src/debug/lux-a041e87b9732/integrators/bidirectional.cpp:240 #3 lux::BidirIntegrator::GetDirectLight at /usr/src/debug/lux-a041e87b9732/integrators/bidirectional.cpp:230 #4 lux::BidirIntegrator::Li at /usr/src/debug/lux-a041e87b9732/integrators/bidirectional.cpp:561 #5 lux::SamplerRenderer::RenderThread::RenderImpl at /usr/src/debug/lux-a041e87b9732/renderers/samplerrenderer.cpp:364 #6 boost::(anonymous namespace)::thread_proxy at libs/thread/src/pthread/thread.cpp:165
Created attachment 771042 [details] File: backtrace
Created attachment 771043 [details] File: cgroup
Created attachment 771044 [details] File: core_backtrace
Created attachment 771045 [details] File: dso_list
Created attachment 771046 [details] File: environ
Created attachment 771047 [details] File: limits
Created attachment 771048 [details] File: maps
Created attachment 771049 [details] File: open_fds
Created attachment 771050 [details] File: proc_pid_status
open very simple scene, enavle LUxrender addon, hit F12 to render reporter: libreport-2.1.6 backtrace_rating: 4 cmdline: /home/storm/../../usr/bin/luxrender --logconsole /tmp/my_cornellbox2.Scene.00001.lxs crash_function: lux::Lambertian::F executable: /usr/bin/luxrender kernel: 3.11.0-0.rc3.git2.2.fc20.x86_64 package: LuxRender-1.0-12.fc19 reason: Process /usr/bin/luxrender was killed by signal 11 (SIGSEGV) runlevel: N 5 uid: 1000
Used LuxRender to Render the Blender default scene. Upon render the LuxRender window pops up and immeadiately closes again. Nothing is rendered. reporter: libreport-2.1.9 backtrace_rating: 4 cmdline: /usr/bin/luxrender --logconsole /tmp/untitled.Scene.00001.lxs crash_function: lux::Lambertian::F executable: /usr/bin/luxrender kernel: 3.11.8-200.fc19.x86_64 package: LuxRender-1.0-12.fc19 reason: Process /usr/bin/luxrender was killed by signal 11 (SIGSEGV) runlevel: N 5 type: CCpp uid: 1000
JFYI, it seems well known issue (more then 6 months ), reported in Lixrender forums, related to recent Boost used in Fedora 19, not sure who blame exactly. In fact, Luxrender unisable at least on x86_64 all that time. Seems that Fedora user base shrinking a lot, as no one care.
That been said, none forwarded the patch here. I've attempted to update to 1.3.1 yesterday, but that's still need works. I'm not sure to be able to work on this anytime soon. If you want to help: fedpkg clone LuxRender -a
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
bug still exist in F21, https://bugzilla.redhat.com/show_bug.cgi?id=1165742
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.