Unusable display with AMD driver errors. #109381
Labels
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#109381
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
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?
Operating system: Ubuntu 22.04.2 LTS/Kernel version 5.15.0.75/FOSS amdgpu driver(default)
Graphics card:MSI Radeon RX580 8GB
Broken: 3.5.1, 3.1.0
Worked: 3.1.0(Did not experience this until recently)
When editing UV GPU gets reset after errors, the compositor does not recover. Garbled image on the screen with displays unusable. Log data attached.
This happens when pressing .(dot) on the keypad, selecting or moving a UV.
This sounds very much like a driver issue. Have you tried using drivers from other sources? Also, are you running in X11 session or Wayland? Thanks!
This is under an X11 session, tried on XFCE, Cinnamon, KDE.
I had issues with the alternative proprietary AMD GPU drivers so I am unable to use those.
Also the problem seems a bit random, it does not always happen, but when it does it's persistent with a few reboots(or sudo service lightdm restart if in XFCE or Cinnamon) in between and then it goes away for a while.
This might be a coincidence, but the first time I encountered the problem, I managed to continue work with no issues for a longer period after I closed UV Editing and Shading workspaces, saved, restarted and re opened the mentioned workspaces.
Haven't really seen similar reports here. It might be helpful to report this to the open source driver developers and see if they have anything to say about it.
I tried on Fedora 38/kernel 6.2.9-300 with a save file on which I can reproduce this issue, with the same result. I'll see if I can get something running blender in the terminal with the debug mode enabled
Hi, any updates here? Is the bug still relevant for you @Borz0?
No activity for more than a week. As per the tracker policy we assume the issue is gone and can be closed.
Thanks again for the report. If the problem persists please open a new report with the required information.