FS#67513 - [blender] 2.83.4 LTS freezes on GNOME

Attached to Project: Community Packages
Opened by Gerardo Gonzalez (gerardogc2378) - Thursday, 06 August 2020, 17:55 GMT
Last edited by freswa (frederik) - Tuesday, 22 September 2020, 16:44 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To No-one
Architecture x86_64
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

Blender crashes when you are in UV Editor

Additional info:

blender 17:2.83.4-1

Steps to reproduce:

With the default cube I tried to put a new image on UV Editor and blender freezes all my GNOME desktop. I don't know why it's happening this behavior. With blender 17:2.82.a-8 works pretty fine.
This task depends upon

Closed by  freswa (frederik)
Tuesday, 22 September 2020, 16:44 GMT
Reason for closing:  Upstream
Additional comments about closing:  Please report this upstream. Feel free to reopen if there's a useful patch
Comment by freswa (frederik) - Friday, 07 August 2020, 15:11 GMT
Please provide logs.
Thank you
Comment by Gerardo Gonzalez (gerardogc2378) - Friday, 07 August 2020, 15:54 GMT
I don't have any logs to show because I use blender from GNOME not from a shell, but if you have a way to get logs, please let me know.
Comment by freswa (frederik) - Friday, 07 August 2020, 15:55 GMT
Please start Blender from Shell, save the output in a file and upload the file to this report.
Comment by Gerardo Gonzalez (gerardogc2378) - Friday, 07 August 2020, 19:12 GMT
I tried this command under a shell:

$ blender 2> blender_log.txt

But there is no log, just my computer is freezed.
Comment by freswa (frederik) - Friday, 07 August 2020, 22:02 GMT
Try this:
blender --debug > blender-debug.log 2>&1
Comment by Gerardo Gonzalez (gerardogc2378) - Saturday, 08 August 2020, 00:25 GMT
I tried this last command, bit it doesn't work. No output, no errors.
Comment by Gerardo Gonzalez (gerardogc2378) - Saturday, 08 August 2020, 00:27 GMT
Or maybe is another problem with blender and my video card. This is my output from lspci command:

00:00.0 Host bridge: Intel Corporation 8th Gen Core Processor Host Bridge/DRAM Registers (rev 07)
00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 630 (Desktop)
00:08.0 System peripheral: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model
00:12.0 Signal processing controller: Intel Corporation Cannon Lake PCH Thermal Controller (rev 10)
00:14.0 USB controller: Intel Corporation Cannon Lake PCH USB 3.1 xHCI Host Controller (rev 10)
00:14.2 RAM memory: Intel Corporation Cannon Lake PCH Shared SRAM (rev 10)
00:16.0 Communication controller: Intel Corporation Cannon Lake PCH HECI Controller (rev 10)
00:17.0 SATA controller: Intel Corporation Cannon Lake PCH SATA AHCI Controller (rev 10)
00:1c.0 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port #6 (rev f0)
00:1c.6 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port #7 (rev f0)
00:1f.0 ISA bridge: Intel Corporation Device a308 (rev 10)
00:1f.3 Audio device: Intel Corporation Cannon Lake PCH cAVS (rev 10)
00:1f.4 SMBus: Intel Corporation Cannon Lake PCH SMBus Controller (rev 10)
00:1f.5 Serial bus controller [0c80]: Intel Corporation Cannon Lake PCH SPI Controller (rev 10)
01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 0c)
02:00.0 Network controller: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter (rev 31)


Comment by freswa (frederik) - Saturday, 08 August 2020, 09:23 GMT
We need a debug log to investigate this issue. If you need help to provide these logs, feel free to ask in the forum, the ML or in the IRC.
Maybe also the blender docs/man pages are of help.
Comment by Darrell (denns) - Friday, 21 August 2020, 21:30 GMT
Same issue here. There are multiple upstream bug reports of issues with Intel GPUs and Blender.

https://gitlab.freedesktop.org/drm/intel/-/issues/2075
https://gitlab.freedesktop.org/drm/intel/-/issues/2097

and several others on their tracker as well.
Comment by Chris (Cowhead) - Monday, 24 August 2020, 21:52 GMT
I am having the same issue. I tried using blender --debug > blender-debug.log 2>&1 to see if I can get anything. Nothing was recorded to the log when the program froze. I then checked my /tmp folder to see if there was a crash log and none existed. Admittedly, I was attempting to do this from a virtual terminal, but that should have not been an issue.

It seems to be acting as if there was a shutdown signal issued for the program, but it doesn't close completely, causing the appearance of freezing the computer. As I stated before, I was able to log in to another terminal (tty2), so the system isn't completely frozen. However, I did need to reboot the computer to regain functionality in tty1. I have found no apparent cause of the freezing, at this point. As a side note, I have only had this problem with 2.83. Every version below 2.83 has been stable on my computer.

Sorry for no logs. If you have another method that I can try, I will be glad to do so.
Comment by Darrell (denns) - Monday, 24 August 2020, 21:56 GMT
I can confirm that the issue is not present with the linux-lts (5.4) kernel. This was also noted upstream at https://gitlab.freedesktop.org/drm/intel/-/issues/2097.
Comment by Sven-Hendrik Haase (Svenstaro) - Tuesday, 22 September 2020, 16:42 GMT
There appears to be nothing to do here and we've got to wait for upstream to fix this in some capacity. I suggest closing this and then people can reopen if there's a useful patch.

Loading...