Suggestion for discoverability improvement of finding Blender logs in system console.
Operating system: Fedora Workstation 42
Blender Version 4.5.2
Currently, it's hard to discover the place where Blender saves logs on Linux, to be able to copy paste logs of things happening in Blender.
To reproduce, open Blender, do something that causes "Errors during render. See system console". Then try to find a way and learn how to see system console (hard), and then learn how to find Blender logs in there (hard). On Windows, I open the "toggle system console" feature from the blender, and I can see i.e. that "Error: Shadow buffer full, may result in missing shadows and lower performance. (2473 / 2048)", which helps me learn that I can fix it by going into Render Properties and under Performance I increase the shadow pool from 512MB to 1GB.
On the other hand, on Linux after I get the graphical "See system console" message, I cannot find any way to launch it in Blender. Without having to resort to checking the system journal in the terminal, an advanced user knows they can open a graphical app for viewing system logs, i.e. GNOME Logs, and search for Blender there, however, I think there may be some room for discoverability improvement of this, especially for users coming from Windows that expect the "Toggle System Console" feature. The improvement to the discoverability doesn't have to be exactly that - I think it could be anything that makes it easier to discover the real error message.
Moved here from projects.blender.org/blender/blender/issues/146209
1 Comment
Do the errors not also print to the Info Editor window?