Triager-bot/blender-bug-reports
1
0
Code Issues 53 Packages Projects Wiki

Python error on opening the navigation pie menu on the asset browser #55

New Issue
Open
opened 2026-04-12 17:56:38 +00:00 by Triager-bot · 7 comments
Triager-bot commented 2026-04-12 17:56:38 +00:00
Owner
Copy Link

Original bug report: https://projects.blender.org/blender/blender/issues/157236

System Information
Operating system: Linux-6.17.0-20-generic-x86_64-with-glibc2.42 64 Bits, X11 UI
Graphics card: NVIDIA GeForce RTX 5070 NVIDIA Corporation NVIDIA 590.48.01 Vulkan Backend

Blender Version
Broken: version: 5.2.0 Alpha, branch: main, commit date: 2026-04-10 23:18, hash: 2229dfdf760c
Worked: (newest version of Blender that worked as expected)

Short description of error
Error on opening the navigation pie menu on the asset browser

Exact steps for others to reproduce the error
Open the asset browser
Press the tilde key

UILayout.prop_enum(): enum property value not found: LIST_VERTICAL
/home/pataz/.steam/debian-installation/steamapps/common/Blender/5.2/scripts/startup/bl_ui/space_filebrowser.py:588
Original bug report: https://projects.blender.org/blender/blender/issues/157236 **System Information** Operating system: Linux-6.17.0-20-generic-x86_64-with-glibc2.42 64 Bits, X11 UI Graphics card: NVIDIA GeForce RTX 5070 NVIDIA Corporation NVIDIA 590.48.01 Vulkan Backend **Blender Version** Broken: version: 5.2.0 Alpha, branch: main, commit date: 2026-04-10 23:18, hash: `2229dfdf760c` Worked: (newest version of Blender that worked as expected) **Short description of error** Error on opening the navigation pie menu on the asset browser **Exact steps for others to reproduce the error** Open the asset browser Press the tilde key ``` UILayout.prop_enum(): enum property value not found: LIST_VERTICAL /home/pataz/.steam/debian-installation/steamapps/common/Blender/5.2/scripts/startup/bl_ui/space_filebrowser.py:588 ```
Triager-bot added the
Status
Needs review
 label 2026-04-12 17:56:38 +00:00
Triager-bot commented 2026-04-12 17:56:50 +00:00
Author
Owner
Copy Link

Report is clear

LLM Reasoning

Got it, let's see. The bug report has a title, body with system info (but we ignore that), Blender version, short description, and steps to reproduce plus the error message. The question is if it clearly describes the issue. The steps are clear: open asset browser, press tilde key. The error is given. So yes, it's clear. Wait, but let me check again. The user wants to know if the bug report clearly describes the issue. The steps are present, the error is there. So the answer should be Yes? Wait, no, wait. Wait, the steps: "Open the asset browser Press the tilde key" and then the error. Is that clear enough? Let me think. The title says Python error on opening navigation pie menu on asset browser. The body has short description, steps, error. So yes, it's clear. So the answer is Yes.

JSON Data

{
"llm_judgement": true,
"processing_time": 10.955086
}

<!-- ID: CLARITY_CHECK --> ### Report is clear <details> <summary>LLM Reasoning</summary> Got it, let's see. The bug report has a title, body with system info (but we ignore that), Blender version, short description, and steps to reproduce plus the error message. The question is if it clearly describes the issue. The steps are clear: open asset browser, press tilde key. The error is given. So yes, it's clear. Wait, but let me check again. The user wants to know if the bug report clearly describes the issue. The steps are present, the error is there. So the answer should be Yes? Wait, no, wait. Wait, the steps: "Open the asset browser Press the tilde key" and then the error. Is that clear enough? Let me think. The title says Python error on opening navigation pie menu on asset browser. The body has short description, steps, error. So yes, it's clear. So the answer is Yes. </details> <details> <summary>JSON Data</summary> { "llm_judgement": true, "processing_time": 10.955086 } </details>
👍 1
Triager-bot commented 2026-04-12 17:57:17 +00:00
Author
Owner
Copy Link

Report is specific

LLM Reasoning

Got it, let's analyze this bug report. The title is "Python error on opening the navigation pie menu on the asset browser". The body mentions a specific error when pressing tilde in the asset browser, with exact steps (open asset browser, press tilde) and an error message about a specific enum property ("LIST_VERTICAL"). So it's about a specific issue because it's tied to a particular action (opening navigation pie menu on asset browser) and has detailed reproduction steps. Wait, but let me check the definitions again. The example for specific is "Crashing while using a specific feature while rendering"—here, the specific feature is the navigation pie menu in the asset browser. So yes, it's specific. But wait, the user said to ignore system info unless relevant. The error message is about a specific enum, so that's part of the specific issue. So the answer should be 'Specific'? Wait, no, wait. Wait the example for generic is "Crashing while rendering"—vague. Here, the bug is when opening the navigation pie menu on the asset browser, which is a specific feature. So yes, it's specific. But let me confirm. The bug report has exact steps: open asset browser, press tilde. That's specific. So the answer is 'Specific'? Wait, but maybe I'm overcomplicating. Let me recheck the question. The user says "specific issue" is about a specific feature (like rendering while using a specific feature). Here, the specific feature is the navigation pie menu in the asset browser. So yes, it's specific. But wait, the error message is a Python error with a specific enum. So I think it's specific. Wait, but maybe the answer is 'Specific'? Or is it generic? Wait, no—generic would be like "crashing while rendering" without specifying which feature. Here, it's about opening the navigation pie menu on the asset browser, which is a specific action. So yes, specific. But let me check again. The bug report title is specific: "Python error on opening the navigation pie menu on the asset browser". The body has exact steps. So yes, specific. Therefore, the answer is 'Specific'. Wait, but wait—the user said if uncertain, respond with 'Generic'. But I think this is specific. Let me confirm once more. The example for specific: "Crashing while using a specific feature while rendering"—here, the specific feature is the navigation pie menu in the asset browser. So yes, that's a specific issue. So the answer is 'Specific'.

JSON Data

{
"llm_judgement": true,
"processing_time": 27.07773
}

<!-- ID: SPECIFIC_REPORT --> ### Report is specific <details> <summary>LLM Reasoning</summary> Got it, let's analyze this bug report. The title is "Python error on opening the navigation pie menu on the asset browser". The body mentions a specific error when pressing tilde in the asset browser, with exact steps (open asset browser, press tilde) and an error message about a specific enum property ("LIST_VERTICAL"). So it's about a specific issue because it's tied to a particular action (opening navigation pie menu on asset browser) and has detailed reproduction steps. Wait, but let me check the definitions again. The example for specific is "Crashing while using a specific feature while rendering"—here, the specific feature is the navigation pie menu in the asset browser. So yes, it's specific. But wait, the user said to ignore system info unless relevant. The error message is about a specific enum, so that's part of the specific issue. So the answer should be 'Specific'? Wait, no, wait. Wait the example for generic is "Crashing while rendering"—vague. Here, the bug is when opening the navigation pie menu on the asset browser, which is a specific feature. So yes, it's specific. But let me confirm. The bug report has exact steps: open asset browser, press tilde. That's specific. So the answer is 'Specific'? Wait, but maybe I'm overcomplicating. Let me recheck the question. The user says "specific issue" is about a specific feature (like rendering while using a specific feature). Here, the specific feature is the navigation pie menu in the asset browser. So yes, it's specific. But wait, the error message is a Python error with a specific enum. So I think it's specific. Wait, but maybe the answer is 'Specific'? Or is it generic? Wait, no—generic would be like "crashing while rendering" without specifying which feature. Here, it's about opening the navigation pie menu on the asset browser, which is a specific action. So yes, specific. But let me check again. The bug report title is specific: "Python error on opening the navigation pie menu on the asset browser". The body has exact steps. So yes, specific. Therefore, the answer is 'Specific'. Wait, but wait—the user said if uncertain, respond with 'Generic'. But I think this is specific. Let me confirm once more. The example for specific: "Crashing while using a specific feature while rendering"—here, the specific feature is the navigation pie menu in the asset browser. So yes, that's a specific issue. So the answer is 'Specific'. </details> <details> <summary>JSON Data</summary> { "llm_judgement": true, "processing_time": 27.07773 } </details>
👍 1
Triager-bot commented 2026-04-12 17:57:34 +00:00
Author
Owner
Copy Link

Report flagged as NOT a duplicate by LLM

Pie Menu in 'IMAGE_EDITOR' space tries to access wrong EnumProperty identifiers

https://projects.blender.org/blender/blender/issues/153553

System Information
Operating system: Windows-10-10.0.19045-SP0 64 Bits
Graphics card: GeForce GT 750M/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 419.35 Opengl Backend

Blender Version
Broken: version: 5.0.1, branch: blender-v5.0-release, commit date: 2025-12-15 16:36, hash: a3db93c5b259
Worked: seems like be broken from 2.80 version

Short description of error
When IMAGE_EDITOR space is in the PAINT ui_mode - errors appear in console:

  • D:\Blender\5.0.1\5.0\scripts\startup\bl_ui\space_image.py:619
    uiLayout::prop_enum: enum property value not found: CENTER

  • D:\Blender\5.0.1\5.0\scripts\startup\bl_ui\space_image.py:622
    1uiLayout::prop_enum: enum property value not found: MEDIAN

That happens on the pressed F3 and on the pressed dot (dot invokes 'pivot_point' pie menu)

Exact steps for others to reproduce the error (look at the gif):

errors.gif

In both cases errors are caused by the IMAGE_MT_pivot_pie(Menu) trying to access 'CENTER' and 'MEDIAN' identifiers of SpaceImageEditor.pivot_point EnumProperty.

Nowadays the .pivot_point identifiers are ['BOUNDING_BOX_CENTER', 'CURSOR', 'INDIVIDUAL_ORIGINS', 'MEDIAN_POINT', 'ACTIVE_ELEMENT'] *not containing either MEDIAN or CENTER

The identifiers which the pie menu is trying to access were changed to the modern ones when Blender updated from 2.7 to 2.8

So it's a VERY old bug :-)

LLM Reasoning

Got it, let's analyze the two bug reports. First, look at the descriptions and steps to reproduce.

Bug Report 1: The error is when opening the navigation pie menu in the asset browser (using tilde key). The traceback mentions "LIST_VERTICAL" not found in a prop_enum call, related to the asset browser's UI.

Bug Report 2: The error happens in IMAGE_EDITOR space (PAINT ui_mode) when using F3 or dot key. The errors are about "CENTER" and "MEDIAN" not being found in the pivot_point EnumProperty of SpaceImageEditor. The issue is that old identifiers are used instead of new ones from Blender 2.8+.

Now, check if they're the same issue. The first is about asset browser pie menu (LIST_VERTICAL), the second is about IMAGE_EDITOR's pivot_pie menu (CENTER/MEDIAN). Different contexts (asset browser vs image editor) and different enum properties (LIST_VERTICAL vs CENTER/MEDIAN). So they're not the same. Therefore, the answer is No.

JSON Data

{
"llm_judgement": false,
"processing_time": 15.672139,
"duplicate_report_number": "153553"
}

<!-- ID: CHECK_DUPLICATE --> ### Report flagged as NOT a duplicate by LLM <details> <summary>Pie Menu in 'IMAGE_EDITOR' space tries to access wrong EnumProperty identifiers</summary> https://projects.blender.org/blender/blender/issues/153553 **System Information** Operating system: Windows-10-10.0.19045-SP0 64 Bits Graphics card: GeForce GT 750M/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 419.35 Opengl Backend **Blender Version** Broken: version: 5.0.1, branch: blender-v5.0-release, commit date: 2025-12-15 16:36, hash: `a3db93c5b259` Worked: seems like be broken from 2.80 version **Short description of error** When `IMAGE_EDITOR` space is in the `PAINT` ui_mode - errors appear in console: - `D:\Blender\5.0.1\5.0\scripts\startup\bl_ui\space_image.py:619` `uiLayout::prop_enum: enum property value not found: CENTER` - `D:\Blender\5.0.1\5.0\scripts\startup\bl_ui\space_image.py:622` `1uiLayout::prop_enum: enum property value not found: MEDIAN` That happens on the pressed <kbd>F3</kbd> and on the pressed <kbd>dot</kbd> (dot invokes 'pivot_point' pie menu) **Exact steps for others to reproduce the error (look at the gif):** ___ ![errors.gif](/attachments/8ac8da76-c6e9-4e9a-ab46-ce774e6a2f6c) ___ In both cases errors are caused by the `IMAGE_MT_pivot_pie(Menu)` trying to access 'CENTER' and 'MEDIAN' identifiers of `SpaceImageEditor.pivot_point` EnumProperty. Nowadays the .pivot_point identifiers are ['BOUNDING_BOX_CENTER', 'CURSOR', 'INDIVIDUAL_ORIGINS', 'MEDIAN_POINT', 'ACTIVE_ELEMENT'] *not containing either `MEDIAN` or `CENTER` The identifiers which the pie menu is trying to access were changed to the modern ones when Blender updated from [2.7](https://docs.blender.org/api/2.70/bpy.types.SpaceImageEditor.html#bpy.types.SpaceImageEditor.pivot_point) to [2.8](https://docs.blender.org/api/2.80/bpy.types.SpaceImageEditor.html#bpy.types.SpaceImageEditor.pivot_point) So it's a VERY old bug :-) </details> <details> <summary>LLM Reasoning</summary> Got it, let's analyze the two bug reports. First, look at the descriptions and steps to reproduce. Bug Report 1: The error is when opening the navigation pie menu in the asset browser (using tilde key). The traceback mentions "LIST_VERTICAL" not found in a prop_enum call, related to the asset browser's UI. Bug Report 2: The error happens in IMAGE_EDITOR space (PAINT ui_mode) when using F3 or dot key. The errors are about "CENTER" and "MEDIAN" not being found in the pivot_point EnumProperty of SpaceImageEditor. The issue is that old identifiers are used instead of new ones from Blender 2.8+. Now, check if they're the same issue. The first is about asset browser pie menu (LIST_VERTICAL), the second is about IMAGE_EDITOR's pivot_pie menu (CENTER/MEDIAN). Different contexts (asset browser vs image editor) and different enum properties (LIST_VERTICAL vs CENTER/MEDIAN). So they're not the same. Therefore, the answer is No. </details> <details> <summary>JSON Data</summary> { "llm_judgement": false, "processing_time": 15.672139, "duplicate_report_number": "153553" } </details>
👍 1
Triager-bot commented 2026-04-12 17:57:34 +00:00
Author
Owner
Copy Link

Encountered error when checking if these reports were duplicates.

Top Bar of Menu Preferences Missing

https://projects.blender.org/blender/blender/issues/{duplicate_report_number}

{duplicate_report_data['body']}

Encountered error when checking if these reports were duplicates. <details> <summary>Top Bar of Menu Preferences Missing</summary> https://projects.blender.org/blender/blender/issues/{duplicate_report_number} {duplicate_report_data['body']} </details>
Triager-bot commented 2026-04-12 17:57:48 +00:00
Author
Owner
Copy Link

Report flagged as NOT a duplicate by LLM

Python error when right clicking in image editor

https://projects.blender.org/blender/blender/issues/154898

System Information
Operating system: Linux-6.17.0-14-generic-x86_64-with-glibc2.42 64 Bits, X11 UI
Graphics card: AMD Radeon RX 6800 (RADV NAVI21) Advanced Micro Devices radv Mesa 26.0.0 - kisak-mesa PPA Vulkan Backend

Blender Version
Broken: version: 5.2.0 Alpha, branch: main, commit date: 2026-02-22 04:18, hash: d7a5d66edcc8
Broken: 5.1 beta
Broken: 5.0.1
Worked: 4.5

Short description of error
When right clicking in image editor, you get this in console:

Traceback (most recent call last):
  File "/home/me/Desktop/next/blender-5.2.0-alpha+main.d7a5d66edcc8-linux.x86_64-release/5.2/scripts/startup/bl_ui/space_view3d.py", line 8740, in draw
    UnifiedPaintPanel.prop_unified_color(split, context, brush, "color", text="")
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/me/Desktop/next/blender-5.2.0-alpha+main.d7a5d66edcc8-linux.x86_64-release/5.2/scripts/startup/bl_ui/properties_paint_common.py", line 314, in prop_unified_color
    ups = UnifiedPaintPanel.paint_settings(context).unified_paint_settings
          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
AttributeError: 'NoneType' object has no attribute 'unified_paint_settings'
01:10.613  bpy.rna          | ERROR Python script error in VIEW3D_PT_paint_texture_context_menu.draw

Exact steps for others to reproduce the error

  • Open Blender in terminal
  • Open General template
  • Go to Texture Paint workspace
  • Change image editor mode to View
  • Right click in image editor
LLM Reasoning

Got it, let's analyze these two bug reports. First, look at the description and steps for each.

Bug Report 1: The issue is about a Python error when opening the navigation pie menu on the asset browser by pressing tilde. The error message mentions "UILayout.prop_enum(): enum property value not found: LIST_VERTICAL" in space_filebrowser.py.

Bug Report 2: The issue is a Python error when right-clicking in the image editor, with an AttributeError related to UnifiedPaintPanel and paint_settings. The steps involve opening Blender, going to Texture Paint workspace, changing image editor mode, then right-clicking.

The key here is that the errors are different (one about enum not found, another about attribute error), and the reproduction steps are completely different (asset browser vs image editor). So they're not the same issue. Therefore, the answer is No.

JSON Data

{
"llm_judgement": false,
"processing_time": 13.479182000000002,
"duplicate_report_number": "154898"
}

<!-- ID: CHECK_DUPLICATE --> ### Report flagged as NOT a duplicate by LLM <details> <summary>Python error when right clicking in image editor</summary> https://projects.blender.org/blender/blender/issues/154898 **System Information** Operating system: Linux-6.17.0-14-generic-x86_64-with-glibc2.42 64 Bits, X11 UI Graphics card: AMD Radeon RX 6800 (RADV NAVI21) Advanced Micro Devices radv Mesa 26.0.0 - kisak-mesa PPA Vulkan Backend **Blender Version** Broken: version: 5.2.0 Alpha, branch: main, commit date: 2026-02-22 04:18, hash: `d7a5d66edcc8` Broken: 5.1 beta Broken: 5.0.1 Worked: 4.5 **Short description of error** When right clicking in image editor, you get this in console: ``` Traceback (most recent call last): File "/home/me/Desktop/next/blender-5.2.0-alpha+main.d7a5d66edcc8-linux.x86_64-release/5.2/scripts/startup/bl_ui/space_view3d.py", line 8740, in draw UnifiedPaintPanel.prop_unified_color(split, context, brush, "color", text="") ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/home/me/Desktop/next/blender-5.2.0-alpha+main.d7a5d66edcc8-linux.x86_64-release/5.2/scripts/startup/bl_ui/properties_paint_common.py", line 314, in prop_unified_color ups = UnifiedPaintPanel.paint_settings(context).unified_paint_settings ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ AttributeError: 'NoneType' object has no attribute 'unified_paint_settings' 01:10.613 bpy.rna | ERROR Python script error in VIEW3D_PT_paint_texture_context_menu.draw ``` **Exact steps for others to reproduce the error** - Open Blender in terminal - Open General template - Go to Texture Paint workspace - Change image editor mode to View - Right click in image editor </details> <details> <summary>LLM Reasoning</summary> Got it, let's analyze these two bug reports. First, look at the description and steps for each. Bug Report 1: The issue is about a Python error when opening the navigation pie menu on the asset browser by pressing tilde. The error message mentions "UILayout.prop_enum(): enum property value not found: LIST_VERTICAL" in space_filebrowser.py. Bug Report 2: The issue is a Python error when right-clicking in the image editor, with an AttributeError related to UnifiedPaintPanel and paint_settings. The steps involve opening Blender, going to Texture Paint workspace, changing image editor mode, then right-clicking. The key here is that the errors are different (one about enum not found, another about attribute error), and the reproduction steps are completely different (asset browser vs image editor). So they're not the same issue. Therefore, the answer is No. </details> <details> <summary>JSON Data</summary> { "llm_judgement": false, "processing_time": 13.479182000000002, "duplicate_report_number": "154898" } </details>
👍 1
Triager-bot commented 2026-04-12 17:58:06 +00:00
Author
Owner
Copy Link

Report flagged as NOT a duplicate by LLM

`Region Toggle Pie` option doesn't work in the file browser

https://projects.blender.org/blender/blender/issues/150419

System Information
Operating system: Windows-10-10.0.26100-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 4090/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 581.80 Opengl Backend

Blender Version
Broken: version: 5.0.0, branch: blender-v5.0-release, commit date: 2025-11-18 09:54, hash: a37564c4df7a
Worked: N/A as it's a new feature in Blender 5.0

Short description of error
In Blender 5.0 a new feature was added to the keymap called Region Toggle Pie that allows you to press N to open a pie menu to controll the visibility of headers, toolbars, sidebars, etc.

This option does not work with the file browser.

Exact steps for others to reproduce the error

  • Open Blender and select the video editing startup file
  • Open preferences and go to the Keymap section and enable the Region Toggle Pie option in the Preferences section at the top of the keymap editor
  • Place your cursor in the file browser and press N to activate the Region Toggle Pie feature
    • Notice it doesn't work
  • Press T to try and open the side bar and notice it doesn't work because when you enabled the Region Toggle Pie feature, the T shortcut was removed.
LLM Reasoning

Got it, let's analyze these two bug reports. First, look at the descriptions and steps.

Bug Report 1: The issue is about a Python error when opening the navigation pie menu on the asset browser using the tilde key. The error message mentions "enum property value not found: LIST_VERTICAL" in the filebrowser.py script.

Bug Report 2: The issue is that the Region Toggle Pie option (which uses N key) doesn't work in the file browser, and also T shortcut is affected. The steps involve enabling a keymap option and pressing N in the file browser.

Now, check if they're the same. Bug 1 is about an error when using tilde (~) on asset browser's pie menu. Bug 2 is about Region Toggle Pie (N key) not working in file browser. Different keys (tilde vs N), different contexts (asset browser vs file browser? Wait, asset browser and file browser—are they the same? Wait, Blender's asset browser is part of the file browser maybe? But the steps are different: Bug 1 uses tilde, Bug 2 uses N after enabling a keymap. The error messages are different too. So they're not the same issue. Therefore, answer is No.

JSON Data

{
"llm_judgement": false,
"processing_time": 16.834753,
"duplicate_report_number": "150419"
}

<!-- ID: CHECK_DUPLICATE --> ### Report flagged as NOT a duplicate by LLM <details> <summary>`Region Toggle Pie` option doesn't work in the file browser</summary> https://projects.blender.org/blender/blender/issues/150419 **System Information** Operating system: Windows-10-10.0.26100-SP0 64 Bits Graphics card: NVIDIA GeForce RTX 4090/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 581.80 Opengl Backend **Blender Version** Broken: version: 5.0.0, branch: blender-v5.0-release, commit date: 2025-11-18 09:54, hash: `a37564c4df7a` Worked: N/A as it's a new feature in Blender 5.0 **Short description of error** In Blender 5.0 a new feature was added to the keymap called `Region Toggle Pie` that allows you to press `N` to open a pie menu to controll the visibility of headers, toolbars, sidebars, etc. This option does not work with the file browser. **Exact steps for others to reproduce the error** - Open Blender and select the video editing startup file - Open preferences and go to the `Keymap` section and enable the `Region Toggle Pie` option in the `Preferences` section at the top of the keymap editor - Place your cursor in the file browser and press `N` to activate the `Region Toggle Pie` feature - Notice it doesn't work - Press `T` to try and open the side bar and notice it doesn't work because when you enabled the `Region Toggle Pie` feature, the `T` shortcut was removed. </details> <details> <summary>LLM Reasoning</summary> Got it, let's analyze these two bug reports. First, look at the descriptions and steps. Bug Report 1: The issue is about a Python error when opening the navigation pie menu on the asset browser using the tilde key. The error message mentions "enum property value not found: LIST_VERTICAL" in the filebrowser.py script. Bug Report 2: The issue is that the `Region Toggle Pie` option (which uses N key) doesn't work in the file browser, and also T shortcut is affected. The steps involve enabling a keymap option and pressing N in the file browser. Now, check if they're the same. Bug 1 is about an error when using tilde (~) on asset browser's pie menu. Bug 2 is about Region Toggle Pie (N key) not working in file browser. Different keys (tilde vs N), different contexts (asset browser vs file browser? Wait, asset browser and file browser—are they the same? Wait, Blender's asset browser is part of the file browser maybe? But the steps are different: Bug 1 uses tilde, Bug 2 uses N after enabling a keymap. The error messages are different too. So they're not the same issue. Therefore, answer is No. </details> <details> <summary>JSON Data</summary> { "llm_judgement": false, "processing_time": 16.834753, "duplicate_report_number": "150419" } </details>
👍 1
Triager-bot commented 2026-04-12 17:58:16 +00:00
Author
Owner
Copy Link

Report flagged as NOT a duplicate by LLM

Missing attribute is_valid in FileBrowserFSMenuEntry when building in debug mode

https://projects.blender.org/blender/blender/issues/144559

Blender Version
Broken: 5.0 last source code

`AttributeError: 'FileBrowserFSMenuEntry' object has no attribute 'is_valid'

Traceback (most recent call last):
File "C:\Users\user\Desktop\BSource\build_windows_x64_vc17_Debug\bin\Debug\5.0\scripts\startup\bl_ui\space_filebrowser.py", line 214, in draw_item
row.enabled = direntry.is_valid
^^^^^^^^^^^^^^^^^^^^
AttributeError: 'FileBrowserFSMenuEntry' object has no attribute 'is_valid'`

Exact steps for others to reproduce the error
Open File Viewer in debug mode

LLM Reasoning

Got it, let's analyze these two bug reports. First, look at the descriptions and steps.

Bug report 1 is about a Python error when opening the navigation pie menu on the asset browser by pressing tilde. The error mentions "enum property value not found: LIST_VERTICAL" in space_filebrowser.py.

Bug report 2 is about a missing 'is_valid' attribute in FileBrowserFSMenuEntry when building in debug mode, with steps to open File Viewer in debug mode. The traceback points to space_filebrowser.py line 214.

The key here is the different error messages and reproduction steps. Report 1 involves the tilde key and enum issue, report 2 is about a missing attribute in debug mode. So they're not the same issue. Therefore, the answer is No.

JSON Data

{
"llm_judgement": false,
"processing_time": 10.429847000000002,
"duplicate_report_number": "144559"
}

<!-- ID: CHECK_DUPLICATE --> ### Report flagged as NOT a duplicate by LLM <details> <summary>Missing attribute is_valid in FileBrowserFSMenuEntry when building in debug mode</summary> https://projects.blender.org/blender/blender/issues/144559 **Blender Version** Broken: 5.0 last source code `AttributeError: 'FileBrowserFSMenuEntry' object has no attribute 'is_valid' Traceback (most recent call last): File "C:\Users\user\Desktop\BSource\build_windows_x64_vc17_Debug\bin\Debug\5.0\scripts\startup\bl_ui\space_filebrowser.py", line 214, in draw_item row.enabled = direntry.is_valid ^^^^^^^^^^^^^^^^^^^^ AttributeError: 'FileBrowserFSMenuEntry' object has no attribute 'is_valid'` **Exact steps for others to reproduce the error** Open File Viewer in debug mode </details> <details> <summary>LLM Reasoning</summary> Got it, let's analyze these two bug reports. First, look at the descriptions and steps. Bug report 1 is about a Python error when opening the navigation pie menu on the asset browser by pressing tilde. The error mentions "enum property value not found: LIST_VERTICAL" in space_filebrowser.py. Bug report 2 is about a missing 'is_valid' attribute in FileBrowserFSMenuEntry when building in debug mode, with steps to open File Viewer in debug mode. The traceback points to space_filebrowser.py line 214. The key here is the different error messages and reproduction steps. Report 1 involves the tilde key and enum issue, report 2 is about a missing attribute in debug mode. So they're not the same issue. Therefore, the answer is No. </details> <details> <summary>JSON Data</summary> { "llm_judgement": false, "processing_time": 10.429847000000002, "duplicate_report_number": "144559" } </details>
👍 1
Triager-bot added
Status
Good judgement
 and removed
Status
Needs review
 labels 2026-04-13 14:20:32 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Status
Bad Judgement
Status
Good judgement
Status
Needs review
Status
Uncertain Judgement
Trager-Bot Will Send Comment
No Label
Status
Good judgement
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
Triager-bot
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Triager-bot/blender-bug-reports#55
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?