Addon install (Blender 4.0.1) - AttributeError: 'bpy.app.handlers' object has no attribute '__name__'

[traydog761]

Bug Description

After full restart (computer and app), when enabling the add-on, it errors out at:
AttributeError: 'bpy.app.handlers' object has no attribute 'name'

Environment Information - Bug happens on:

• BlenderKit version: v3.11.0.240207
• Blender 4.0.1
• Win10 x64
• No VPN enabled

Error Logs

AttributeError: 'bpy.app.handlers' object has no attribute 'name'

Steps to Reproduce

### Tasks

[agajdosi]

Hi @traydog761, could you please try with this pre-release?
https://github.com/agajdosi/blenderkit/releases/tag/v3.12.0.240319-prealpha4

[traydog761]

I get the same results, same error out

…

On Tue, Mar 19, 2024 at 10:06 AM Andreas Gajdosik ***@***.***> wrote: Hi @traydog761 <https://github.com/traydog761>, could you please try with this pre-release? https://github.com/agajdosi/blenderkit/releases/tag/v3.12.0.240319-prealpha4 — Reply to this email directly, view it on GitHub <#1038 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AVNJIHVHZM7WBUP3HUULQLDYZBPAHAVCNFSM6AAAAABE2Q4QMOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMBXGU4DENBXGQ> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[agajdosi]

Hi @traydog761, thanks for trying that out. Could you please send me screenshot or copied longer logs? I cannot reproduce and there are tens of places in which bpy.app.handlers are used. Also just to be on safer side of things, please make sure you do not have multiple directories with blenderkit add-on inside location where Blender installs add-on. People sometimes copy the old version and rename it to e.g. blenderkit-2 or blenderkit-old, which causes very esoteric bugs.

[traydog761]

I have tried all the suggested options and downloads and still get the same error. Have there been any developments on your end? Awaiting your reply.

…

On Sat, Apr 20, 2024 at 10:53 PM github-actions[bot] < ***@***.***> wrote: This issue is marked stale - inactive because it has been open for 30 days with no activity. It will be closed in 14 days if there is no activity. Please comment to prevent closing if this issue is still relevant and present in BlenderKit. — Reply to this email directly, view it on GitHub <#1038 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AVNJIHQ6VABMROPLFVMHPPLY6NA3XAVCNFSM6AAAAABE2Q4QMOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANRXHEYDGOJXHE> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[agajdosi]

Hi @traydog761, I am sorry for that. I would need more complete logs to locate the exact line where this error happens, I am sending you the how to below, please try it with v3.12.0.240423:

Windows

1. Locate Blender.exe and Client's log file:
   A. Client log is by default at: C:\Users\<your-username>\blenderkit_data\client\default.log.
   B. Blender.exe is by default located at: C:\Program Files\Blender Foundation\Blender 4.1\blender.exe
2. Click on the Start button and search for PowerShell. Launch the PowerShell application twice.
3. In first PowerShell window, type (or paste by right-clicking) the following command: Get-Content C:\Users\<your-username>\blenderkit_data\client\default.log -Wait, hit Enter to execute the command. PowerShell will then monitor the log file, we will use it later. Make sure the path to Client log is correct.
4. In second PowerShell window, type (or paste by right-clicking) the following command into the PowerShell window: & "C:\Program Files\Blender Foundation\Blender 4.1\blender.exe" (make sure the path is enclosed in quotes). Press "Enter" to run the command, which will start Blender. All errors which happen during the run will be printed into the PowerShell window.
5. Use Blender as usual until you encounter the problem. Then, copy and paste all of the text from both PowerShell windows into this issues. To select text, hold down the left mouse button and then copy it by pressing the right mouse button.

MacOS

1. Locate the Blender binary and the Client's log file:
   A. The Client log file is typically located at: /Users/<your-username>/blenderkit_data/client/default.log.
   B. The Blender binary is by default found at: /Applications/Blender.app/Contents/MacOS/Blender.
2. Open Spotlight and search for Terminal. Launch two instances of the Terminal application.
3. In the first Terminal window, type tail -f command followed by path from step 1A, e.g. tail -f /Users/<your-username>/blenderkit_data/client/default.log and press "Enter". Terminal will begin monitoring the log file. Make sure to replace <your-username> with your actual username and verify that the path to the Client log file is correct.
4. In the second Terminal window, type or paste the path from step 1B, e.g., /Applications/Blender.app/Contents/MacOS/Blender, and press "Enter". This will start Blender, and any errors will be displayed in the Terminal window.
5. Use Blender as you normally would until the problem occurs. Then, copy and paste all of the text from both Terminal windows into your reply to this issue.

Linux

1. Locate the Blender binary and the Client's log file:
   A. The Client log file is typically located at: /home/<your-username>/blenderkit_data/client/default.log.
   B. The Blender binary can be located by typing which blender in the terminal. If the blender binary is not on the PATH, search for its location and use the absolute path for the following steps.
2. Launch two instances of the "Terminal" application.
3. In the first Terminal window, type or paste the following command: tail -f /home/<your-username>/blenderkit_data/client/default.log and hit "Enter". Terminal will begin monitoring the log file. Make sure to replace <your-username> with your actual username and verify that the path to the Client log file is correct.
4. In the second Terminal window, type blender (or specify the absolute path to Blender binary if it's not on the PATH) and hit "Enter". This will start Blender and any errors will be printed into the Terminal window.
5. Use Blender as you normally would until the problem occurs. Then, copy and paste all of the text from both Terminal windows into your reply to this issue.

Looking forward to your response. Thank you!

[StuNewsub]

Hi @agajdosi I'm experiencing the same problem. Im running blender version 4.1.1.

This is the traceback report that comes up when trying to enable the add-on;

Just wondered if you have a fix available yet for this as I'm still paying. I've removed and reinstalled both the stable version and the prealpha 3.12.0 version and the same error occurs.

Any help you can offer would be appreciated.

Thanks

[agajdosi]

Hi @StuNewsub, @traydog761 if you could please send me the complete logs from the start of the Blender until the problem, I could take a look. I am not able to reproduce this, spent few hours in March, another in April, another now. No luck. I need the logs or some info about how to reproduce, otherwise we cannot do much in here.

Windows

1. Locate Blender.exe and Client's log file:
   A. Client log is by default at: C:\Users\<your-username>\blenderkit_data\client\default.log.
   B. Blender.exe is by default located at: C:\Program Files\Blender Foundation\Blender 4.1\blender.exe
2. Click on the Start button and search for PowerShell. Launch the PowerShell application twice.
3. In first PowerShell window, type (or paste by right-clicking) the following command: Get-Content C:\Users\<your-username>\blenderkit_data\client\default.log -Wait, hit Enter to execute the command. PowerShell will then monitor the log file, we will use it later. Make sure the path to Client log is correct.
4. In second PowerShell window, type (or paste by right-clicking) the following command into the PowerShell window: & "C:\Program Files\Blender Foundation\Blender 4.1\blender.exe" (make sure the path is enclosed in quotes). Press "Enter" to run the command, which will start Blender. All errors which happen during the run will be printed into the PowerShell window.
5. Use Blender as usual until you encounter the problem. Then, copy and paste all of the text from both PowerShell windows into this issues. To select text, hold down the left mouse button and then copy it by pressing the right mouse button.

MacOS

1. Locate the Blender binary and the Client's log file:
   A. The Client log file is typically located at: /Users/<your-username>/blenderkit_data/client/default.log.
   B. The Blender binary is by default found at: /Applications/Blender.app/Contents/MacOS/Blender.
2. Open Spotlight and search for Terminal. Launch two instances of the Terminal application.
3. In the first Terminal window, type tail -f command followed by path from step 1A, e.g. tail -f /Users/<your-username>/blenderkit_data/client/default.log and press "Enter". Terminal will begin monitoring the log file. Make sure to replace <your-username> with your actual username and verify that the path to the Client log file is correct.
4. In the second Terminal window, type or paste the path from step 1B, e.g., /Applications/Blender.app/Contents/MacOS/Blender, and press "Enter". This will start Blender, and any errors will be displayed in the Terminal window.
5. Use Blender as you normally would until the problem occurs. Then, copy and paste all of the text from both Terminal windows into your reply to this issue.

Linux

1. Locate the Blender binary and the Client's log file:
   A. The Client log file is typically located at: /home/<your-username>/blenderkit_data/client/default.log.
   B. The Blender binary can be located by typing which blender in the terminal. If the blender binary is not on the PATH, search for its location and use the absolute path for the following steps.
2. Launch two instances of the "Terminal" application.
3. In the first Terminal window, type or paste the following command: tail -f /home/<your-username>/blenderkit_data/client/default.log and hit "Enter". Terminal will begin monitoring the log file. Make sure to replace <your-username> with your actual username and verify that the path to the Client log file is correct.
4. In the second Terminal window, type blender (or specify the absolute path to Blender binary if it's not on the PATH) and hit "Enter". This will start Blender and any errors will be printed into the Terminal window.
5. Use Blender as you normally would until the problem occurs. Then, copy and paste all of the text from both Terminal windows into your reply to this issue.

Looking forward to your response. Thank you!

[BujusKrachus]

Fyi there is a similar issue active for the Poliigon addon on blenders addon repo: https://projects.blender.org/blender/blender-addons/issues/105356.

It seems like it's probably neither a blender nor a addon issue, more or less a users environment issue. Why though idk. Will update if more info pops up.