Bug 2420140
| Summary: | FBX exporter does not work | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | snuutti | ||||||
| Component: | blender | Assignee: | Luya Tshimbalanga <luya_tfz> | ||||||
| Status: | ASSIGNED --- | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | high | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 43 | CC: | code, design-devel, epel-packagers-sig, gang65, kitlith, luya_tfz, negativo17 | ||||||
| Target Milestone: | --- | Keywords: | Upstream | ||||||
| Target Release: | --- | ||||||||
| Hardware: | x86_64 | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | --- | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | Type: | --- | |||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Attachments: |
|
||||||||
|
Description
snuutti
2025-12-08 19:43:14 UTC
Created attachment 2118023 [details]
FBX exporter traceback
I confirm the reproduction of the traceback which seems affecting all operating systems running version 5.0.0. according to upstream bug report: https://projects.blender.org/blender/blender/issues/151290 I suspect that the upstream bug report is not related. The upstream bug has a specific cause (can't export when in X state), with tracebacks of the form `AttributeError: 'NoneType' object has no attribute 'nodes'`. This bug produces tracebaks of the form `AttributeError: 'ExportFBX' object has no attribute 'path_mode'`, I can trigger this bug with the default blender scene, and it also causes the FBX export settings to be absent when you are selecting where to export to. Workaround: I was able to export an FBX using Blender 5.0.0 from the flathub flatpak, instead of Blender 5.0.1 from the (non-flatpak) fedora package repository. (This workaround is another reason why I suspect that this is not an upstream bug.) The bug also affected Windows version as highlighted on comment #2. Upstream provided a patch which resolved the issue. The scratch build is available at the time of writing for testing: https://koji.fedoraproject.org/koji/taskinfo?taskID=140999365 I tried the scratch build on my system but nothing's changed, I'm still getting the same list of errors. I've also tested the latest Blender version 5.0.1 on Ubuntu 24.04 and Windows 10, and neither system has this issue which also makes me believe this is unrelated to the upstream bug. The workaround of using the Blender flatpak won't work for me as my use case requires Blender's Python API. Could you show a screenshot of that error? Try to clean install Fedora Blender with https://bodhi.fedoraproject.org/updates/FEDORA-2026-71de399b02 and enable updates-testing repository. Note that version includes both MaterialX and manifold3d. Created attachment 2121920 [details]
Screenshot of error
I've tried a clean install with the update, no difference. It turned out the issue is the compatibility between Blender Python API and Python 3.14. While it is possible to use Python 3.11, other python packaged componenet line numpy are built on Python 3.14 on both Fedora 43 and onward which increases the complexity of the maintenance. Upstream is willing to address the issue as highlighted on https://projects.blender.org/blender/blender/issues/152809#issuecomment-1813202 |