Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#74977 - Blender. The menu suddenly disappears.

Attached to Project: Community Packages
Opened by Konstantin (imlegr) - Monday, 06 June 2022, 20:37 GMT
Last edited by Sven-Hendrik Haase (Svenstaro) - Friday, 11 November 2022, 00:00 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Sven-Hendrik Haase (Svenstaro)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

System Information
Operating system: Linux-5.18.1-zen1-1-zen-x86_64-with-glibc2.35 64 Bits
Graphics card: NVIDIA GeForce RTX 3070 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 515.48.07

Blender Version
Broken: version: 3.1.2, branch: makepkg (modified), commit date: 2022-03-31 17:40, hash: rBcc66d1020c3b
Worked: I don't remember.

Short description of error
In Arch Linux, the menu suddenly disappears.

Exact steps for others to reproduce the error
I don't know exactly how it arises. It just suddenly disappears from the menu when I'm working.
When I press CTRL+SPACE 2 times it will reappear.

Where there are a lot of pixels is just me blurring the name of the project.
This task depends upon

Closed by  Sven-Hendrik Haase (Svenstaro)
Friday, 11 November 2022, 00:00 GMT
Reason for closing:  Works for me
Comment by Konstantin (imlegr) - Monday, 06 June 2022, 20:41 GMT
Scr
   2022-06-06_11-18-23.png (29.1 KiB)
Comment by Sven-Hendrik Haase (Svenstaro) - Monday, 06 June 2022, 23:01 GMT
I have pretty similar hardware but I'm unable to reproduce the problem. Without further information on how to reliably trigger the problem I can't really work on this.
Comment by Konstantin (imlegr) - Monday, 06 June 2022, 23:26 GMT
This occurs most often when I work in the shading tab and run a renderer. Also the file itself is created in 2.93 (by the customer), and I work in 3.1. (I can not show the scene itself, I have signed an NDA).
Comment by Sven-Hendrik Haase (Svenstaro) - Tuesday, 21 June 2022, 20:02 GMT
Can you repro in Blender 3.2?
Comment by Konstantin (imlegr) - Tuesday, 21 June 2022, 21:15 GMT
Yes, unfortunately Blender 3.2 also has this problem. I don't understand what it has to do with it.
Comment by Sven-Hendrik Haase (Svenstaro) - Tuesday, 13 September 2022, 08:22 GMT
Still can't reproduce, I'm afraid. I'd try checking with upstream.
Comment by Sven-Hendrik Haase (Svenstaro) - Thursday, 10 November 2022, 23:59 GMT
I'm going to close this ticket here for now. I still can't reproduce it and we've had no other reports from users. I suggest you report this upstream and request the bug to be reopened if they tell you that the packaging is somehow at fault here.

Loading...