FS#80306 - [blender] 17:4.0.1-2 various add-on problems

Attached to Project: Arch Linux
Opened by Rodrigo Ceccato de Freitas (fopor) - Monday, 20 November 2023, 20:49 GMT
Last edited by Toolybird (Toolybird) - Thursday, 23 November 2023, 07:30 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Sven-Hendrik Haase (Svenstaro)
freswa (frederik)
Filipe Laíns (FFY00)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 3
Private No

Details

Description:
Node Wrangler (built-in Blender add-on) not working after update to blender-17:4.0.1-2. Was working on 3.6.5.

Additional info:
* package version: blender-17:4.0.1-2
* config and/or log files: default configuration, happens at startup.
* link to upstream bug report: not a upstream bug. The add-on version that is packed is not compatible with the current version.

Additional info: https://projects.blender.org/blender/blender-addons/issues/105015


Steps to reproduce:
1. pacman -S blender
2. Open Blender
3. Go to Edit -> Preferences -> Add-ons -> Node Wrangler
4, Activate add-on
This task depends upon

Closed by  Toolybird (Toolybird)
Thursday, 23 November 2023, 07:30 GMT
Reason for closing:  Fixed
Additional comments about closing:  blender-17:4.0.1-4
Comment by loqs (loqs) - Monday, 20 November 2023, 22:07 GMT
Possibly the same cause as I suggested in  FS#79999  as both issues are caused by the Arch package being built with a mismatch of the addons repo.
Edit:
As with  FS#79999  I can not reproduce the issue with a locally built package [1] I was building for  FS#80301 .
Edit:
Attached rough outline of adding all repositories used by `make update` to sources array.

[1]: https://bugs.archlinux.org/task/80301#comment223818
   PKGBUILd.diff (2.5 KiB)
Comment by Clemens (celloclemens) - Tuesday, 21 November 2023, 11:30 GMT
The same issue occurs with the blender gltf exporter PlugIn
Comment by Konstantin (imlegr) - Tuesday, 21 November 2023, 12:54 GMT
I get the same error when turning on Node Wrangler.

It says this:
bpy.data.window_managers["WinMan"].addon_search = "Wrangler"
Traceback (most recent call last):
File "/usr/share/blender/4.0/scripts/modules/addon_utils.py", line 401, in enable
mod.register()
File "/usr/share/blender/4.0/scripts/addons/node_wrangler/__init__.py", line 45, in register
bpy.types.NodeSocketInterface.NWViewerSocket = BoolProperty(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
AttributeError: 'module' object has no attribute 'NodeSocketInterface'

Comment by loqs (loqs) - Tuesday, 21 November 2023, 13:17 GMT
@celloclemens what is the error message produced by gltf exporter?
Comment by Konstantin (imlegr) - Tuesday, 21 November 2023, 15:26 GMT
I assume that the Node Wrangler version in the assembly is not what is required.

The package contains Node Wrangler 3.44. You just need to update Node Wrangler to the latest version.
Comment by Clemens (celloclemens) - Tuesday, 21 November 2023, 17:02 GMT
For a description of the error with Gltf exporter see here: https://github.com/KhronosGroup/glTF-Blender-IO/issues/2064
Comment by Konstantin (imlegr) - Wednesday, 22 November 2023, 11:10 GMT
Tell me, does anyone solve the problem with the non-working "Node Wrangler" plugin? I want to switch to blender 4, this is one of the main plugins that I need to work with.
Comment by loqs (loqs) - Wednesday, 22 November 2023, 11:22 GMT
> Tell me, does anyone solve the problem with the non-working "Node Wrangler" plugin? I want to switch to blender 4, this is one of the main plugins that I need to work with.
Have you tried rebuilding blender locally or the built package from [1]?

[1]: https://bugs.archlinux.org/task/80301#comment223887
Comment by Konstantin (imlegr) - Wednesday, 22 November 2023, 11:29 GMT
I install from repositories.
paru -S blender
Comment by loqs (loqs) - Wednesday, 22 November 2023, 11:34 GMT
You want a workaround that does not involve replacing the blender package from the repositories or at least the mismatching plugin?
Comment by Konstantin (imlegr) - Wednesday, 22 November 2023, 11:35 GMT
I don't understand what you mean. I want to install a blender from the repositories and use it.
Comment by loqs (loqs) - Wednesday, 22 November 2023, 11:48 GMT
> I don't understand what you mean. I want to install a blender from the repositories and use it.
The only way to fix the issue that I know of is to replace the incompatible plugin version provided by the blender package with a compatible version. That can be done by either using a blender package that has been built with that change or manually replacing the module in /usr/share/blender/4.0/scripts/addons/.
Comment by Konstantin (imlegr) - Wednesday, 22 November 2023, 11:53 GMT
Is no one going to fix anything in the repository? Why would I download something additionally if it should work in the repository?

I downloaded the version from the website https://www.blender.org / and everything works there and nothing needs to be reassembled and pumped.

Can the maintainer solve the problem with the version in the repository?
Comment by loqs (loqs) - Wednesday, 22 November 2023, 12:01 GMT
> I want to switch to blender 4, this is one of the main plugins that I need to work with.
I was offering you a solution that did not involve waiting for the maintainer to address the issue.
> I downloaded the version from the website https://www.blender.org / and everything works there and nothing needs to be reassembled and pumped.
I did not know you already have such a solution
> Can the maintainer solve the problem with the version in the repository?
I believe so by making a new release with an adjusted PKGBUILD.
Comment by Toolybird (Toolybird) - Wednesday, 22 November 2023, 19:27 GMT
Merging  FS#80322  here.
Comment by Sven-Hendrik Haase (Svenstaro) - Thursday, 23 November 2023, 03:44 GMT
I used the patch by loqs for rel-4. Please check that.

Loading...