Objects in viewport become white after consecutive sleep and wake. Fedora, NVIDIA drivers installed) #58774

Closed
opened 2018-12-05 10:17:04 +01:00 by Sina · 11 comments

System Information
Asus Laptop N550JK. Intel® Core™ i7-4700HQ
Operating system: Fedora 28, Kernel ->4.19.4-200.fc28.x86_64
Gnome: Version 3.28.2
OS Type: 64-bit
Graphics card: GeForce GTX 850M/PCIe/SSE2, (add. info. It has Optimus)

Blender Version
Broken:
blender 2.8, 26d5a3625e, 2018-11-29
blender 2.79b also has the similar problem.

Short description of error
Having nvidia drivers installed as described by negative 17 , after waking from a OS sleep while blender is opened, blender kind of looses its connection with graphics driver and all the functionality of blender associated with NVIDIA graphics driver becomes corrupted. Thus making the color of objects in view port null, when bpy.data.screens["Layout"].shading.type is set to "LookDev" or "Rendered". If I change the render engine from Evee or Cycles to Workbench or in Cycles change the Device to CPU, the view port colors becomes functional but the remains for the GPU Device or Evee selected. Before sleeping the OS, CyclesPreferences.compute_device_type shows both CPU and GPU for selection, but after waking system it disappears.
PS: I have tried all other graphics driver repositories except direct installation of the files downloadable from NVIDIA website.
Closing and reopening or killing the blender process in terminal doesn't bring back the GPU support but solves the white color problem.
Exact steps for others to reproduce the error
Making the problem:
From the default startup -> change view port display method to LookDev or Rendered -> sleep the fedora by fn+F1 keystroke -> wake the computer
My current work around:
Close blender and open it again.

**System Information** Asus Laptop N550JK. Intel® Core™ i7-4700HQ Operating system: Fedora 28, Kernel ->4.19.4-200.fc28.x86_64 Gnome: Version 3.28.2 OS Type: 64-bit Graphics card: GeForce GTX 850M/PCIe/SSE2, (add. info. It has Optimus) **Blender Version** Broken: blender 2.8, 26d5a3625ed, 2018-11-29 blender 2.79b also has the similar problem. **Short description of error** Having nvidia drivers installed as described by [negative 17 ](https://negativo17.org/nvidia-driver/), after waking from a OS sleep while blender is opened, blender kind of looses its connection with graphics driver and all the functionality of blender associated with NVIDIA graphics driver becomes corrupted. Thus making the color of objects in view port null, when bpy.data.screens["Layout"].shading.type is set to "LookDev" or "Rendered". If I change the render engine from Evee or Cycles to Workbench or in Cycles change the Device to CPU, the view port colors becomes functional but the remains for the GPU Device or Evee selected. Before sleeping the OS, CyclesPreferences.compute_device_type shows both CPU and GPU for selection, but after waking system it disappears. PS: I have tried all other graphics driver repositories except direct installation of the files downloadable from NVIDIA website. Closing and reopening or killing the blender process in terminal doesn't bring back the GPU support but solves the white color problem. **Exact steps for others to reproduce the error** Making the problem: From the default startup -> change view port display method to LookDev or Rendered -> sleep the fedora by fn+F1 keystroke -> wake the computer My current work around: Close blender and open it again.
Author

Added subscriber: @SinaBlender

Added subscriber: @SinaBlender

#62645 was marked as duplicate of this issue

#62645 was marked as duplicate of this issue

Added subscriber: @brecht

Added subscriber: @brecht

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
Brecht Van Lommel self-assigned this 2018-12-05 23:52:26 +01:00

This is almost certainly a bug in the graphics driver stack. We don't do anything on sleep/wake, nor can I think of anything that we should be doing. This is really the operating system and graphics driver responsibility, we don't have control over this in Blender.

You can report a bug to NVIDIA if you want.

This is almost certainly a bug in the graphics driver stack. We don't do anything on sleep/wake, nor can I think of anything that we should be doing. This is really the operating system and graphics driver responsibility, we don't have control over this in Blender. You can report a bug to NVIDIA if you want.
Author

Thanks Brecht for your response. But other GPU intensive applications and games behave normally.
After a series of try and error I've found a temporary solution until NVIDIA resolves this bug. If you encounter white shaded view port object after sleep and wake of fedora and you don't want to restart display server: set 3D view to Solid -> quit Blender -> put fedora in sleep -> wake fedora -> open Blender.
PS: If 3D view be on Solid when OS sleep is triggered after waking up there will be no problem.

Thanks Brecht for your response. But other GPU intensive applications and games behave normally. After a series of try and error I've found a temporary solution until NVIDIA resolves this bug. If you encounter white shaded view port object after sleep and wake of fedora and you don't want to restart display server: set 3D view to Solid -> quit Blender -> put fedora in sleep -> wake fedora -> open Blender. PS: If 3D view be on Solid when OS sleep is triggered after waking up there will be no problem.

Added subscriber: @abchauhan

Added subscriber: @abchauhan

In #58774#570734, @SinaBlender wrote:
Thanks Brecht for your response. But other GPU intensive applications and games behave normally.
After a series of try and error I've found a temporary solution until NVIDIA resolves this bug. If you encounter white shaded view port object after sleep and wake of fedora and you don't want to restart display server: set 3D view to Solid -> quit Blender -> put fedora in sleep -> wake fedora -> open Blender.
PS: If 3D view be on Solid when OS sleep is triggered after waking up there will be no problem.

Hi Sina,

I am trying to recreate this issue. I see objects turn white only with the 2.80 Beta version. Are there any error messages reported when this happens?

> In #58774#570734, @SinaBlender wrote: > Thanks Brecht for your response. But other GPU intensive applications and games behave normally. > After a series of try and error I've found a temporary solution until NVIDIA resolves this bug. If you encounter white shaded view port object after sleep and wake of fedora and you don't want to restart display server: set 3D view to Solid -> quit Blender -> put fedora in sleep -> wake fedora -> open Blender. > PS: If 3D view be on Solid when OS sleep is triggered after waking up there will be no problem. Hi Sina, I am trying to recreate this issue. I see objects turn white only with the 2.80 Beta version. Are there any error messages reported when this happens?
Author

Hi Abhishek,
The problem still persists, and no it doesn't pop up any errors. I think there is something wrong with the graphics driver and XServer services. Because Icons on the desktop become white as well, and need to be drag released to redraw correctly. I think kde plasma refreshes its XServer connection instantaneously but Blender keeps going with the old connection of before sleep.

Hi Abhishek, The problem still persists, and no it doesn't pop up any errors. I think there is something wrong with the graphics driver and XServer services. Because Icons on the desktop become white as well, and need to be drag released to redraw correctly. I think kde plasma refreshes its XServer connection instantaneously but Blender keeps going with the old connection of before sleep.

Thank you for the update Sina.

Can you please send me an email at abchauhan[at]nvidia[dot]com for follow-up questions about your system configuration?

Thank you for the update Sina. Can you please send me an email at abchauhan[at]nvidia[dot]com for follow-up questions about your system configuration?

Added subscriber: @Delle

Added subscriber: @Delle
Sign in to join this conversation.
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
4 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#58774
No description provided.