Blender crashes on latest build and bug filer gives error

havealoha · September 6, 2023, 4:54am

Bug filer reports error:

— Running report_uReport —

Server responded with an error: 'Element 'os' is invalid: Element 'name' is invalid: Only the following values are allowed: centos, fedora'
('report_uReport' exited with 1)

Blender crashes:

blender

BLT_lang_init: 'locale' data path for translations not found, continuing
EGL Error (0x3009): EGL_BAD_MATCH: Arguments are inconsistent (for example, a valid context requires buffers n
ot supplied by a valid surface).
EGL Error (0x3009): EGL_BAD_MATCH: Arguments are inconsistent (for example, a valid context requires buffers n
ot supplied by a valid surface).
EGL Error (0x3009): EGL_BAD_MATCH: Arguments are inconsistent (for example, a valid context requires buffers n
ot supplied by a valid surface).
EGL Error (0x3009): EGL_BAD_MATCH: Arguments are inconsistent (for example, a valid context requires buffers n
ot supplied by a valid surface).
EGL Error (0x3009): EGL_BAD_MATCH: Arguments are inconsistent (for example, a valid context requires buffers n
ot supplied by a valid surface).
EGL Error (0x3009): EGL_BAD_MATCH: Arguments are inconsistent (for example, a valid context requires buffers n
ot supplied by a valid surface).
EGL Error (0x3009): EGL_BAD_MATCH: Arguments are inconsistent (for example, a valid context requires buffers n
ot supplied by a valid surface).
EGL Error (0x3009): EGL_BAD_MATCH: Arguments are inconsistent (for example, a valid context requires buffers n
ot supplied by a valid surface).
Warning: No OpenGL vendor detected.
blender: ../src/dispatch_common.c:872: epoxy_get_proc_address: Assertion `0 && "Couldn't find current GLX or E
GL context.\n"' failed.
Aborted (core dumped)

marcan · September 6, 2023, 10:24am

Blender requires a newer OpenGL version than is supported right now, see here.

However, that crash/error is really, really bad. You should file a bug in the Fedora bug tracker to improve it. It should clearly tell the user that their GPU does not meet the minimum requirements.

havealoha · September 7, 2023, 3:52am

Done

github.com/AsahiLinux/linux

[TRACKER] GPU rendering issues / app crashes

opened 03:36AM - 07 Dec 22 UTC

asahilina

This is a tracker bug for general GPU issues, like: * Apps that crash after s…tartup * Rendering glitches * GPU fault/timeout errors When making a comment on this bug, please run the `asahi-diagnose` command and attach the file it saves to your comment. Please tell us what you were doing when the problem happened, what desktop environment and window system you use, and any other details about the issue. The purpose of this bug is to collect reports of app issues in one place, so we have somewhere to look when figuring out what to work on. Since the driver is still a work-in-progress and lots of things are not expected to work, please don't expect a timely response to reports. We're working on it! **Before reporting something, please check that the issue has not been reported already. Duplicate reports just clutter up the bug and will be marked as duplicate. --marcan** * **If you are having shader errors with Chromium/Electron-based apps after an update, delete your shader cache: `rm -rf ~/.config/chromium/Default/GPUCache` (or similar paths for other apps).** [Upstream bug](https://bugs.chromium.org/p/chromium/issues/detail?id=1442633&q=component%3AInternals%3ESkia&can=2&sort=-opened). This is not a driver bug. * If you find a *regression* in the GPU driver (an app does not work or has rendering problems where it previously worked *with the GPU driver enabled* on a previous version), please file a bug directly on the [asahi/mesa bug tracker](https://gitlab.freedesktop.org/asahi/mesa/-/issues). Regressions only, please! * If you run into a *GPU lockup or crash* (all GPU apps stop working, but you can still SSH into the machine), please open a new bug in this repo, tell us what you were doing when the GPU locked up, and attach the `asahi-diagnose` log. * If you get *GPU fault* or *GPU timeout* messages in dmesg (probably together with rendering issues), but the GPU keeps working in general, this tracker bug is the right place to report that. * If you have `linux-asahi-edge` issues *unrelated to the GPU*, please report them [here](https://github.com/AsahiLinux/linux/issues/70). This includes display output/controller related issues, like screen resolution switching and backlight control, which are unrelated to the GPU driver. * If you are seeing *single-pixel-wide glitches*, please set your screen scale to 100%, log out and back in, and try to reproduce it again. These kinds of glitches are likely to be compositor/desktop environment bugs related to fractional scaling, rather than driver issues. ## If you see magenta Magenta is the error color on Apple GPUs. It is what you get when you sample an uninitialized compressed texture. This often happens with driver bugs that break rendering, but there are also many apps that have bugs that transiently display uninitialized buffer contents. These will often show up as black or transparent on other GPUs or with software rendering, which stands out less but it indicates the same bug. If you see magenta glitches, please try running the app with `ASAHI_MESA_DEBUG=nocompress`. If you see the same problems but they are now black, try `LIBGL_ALWAYS_SOFTWARE=true` to force software rendering. If you get the same results (still black regions where previously there was magenta), then it is likely an app bug or an upstream Mesa bug, not a driver issue. Another common issue is apps that have [rendering feedback loops](https://www.khronos.org/opengl/wiki/Memory_Model#Framebuffer_objects), which are undefined behavior in OpenGL. These often result in 4x2 pixel shaped corruption regions. You can work around this with `ASAHI_MESA_DEBUG=nocompress`, which should fix the issue (at least if it wouldn't normally break on all GPUs). This could also be caused by a driver bug, though, so please do report anything that is fixed with `nocompress` so we can take a look and determine whether it's an app bug or a driver bug! ## Known issues * [ ] When GPU timeouts/faults occur, rarely the firmware can lock up (see #79) * [ ] Complex shaders do not work due to missing register spilling ([example](https://www.shadertoy.com/view/4dK3zc)) * [ ] Google Maps on Firefox is slow/jerky ## Resolved issues * [x] System Monitor glitches in the History tab * [x] Plasmashell sometimes shows magenta areas or missing rendering * [x] Portraits render incorrectly or cause faults in Darwinia * [x] Geometry edges render poorly/jagged in Darwinia * [x] WebGL Aquarium faults above 10000 fish * [x] Xorg sometimes flashes black while switching windows in KWin * [x] gl_FragDepth is not implemented * [x] three.js scenes (and other complex renders) with MSAA glitch on Pro/Max/Ultra machines * [x] Discard regressed with the OpenGL 3.1 update (breaking Darwinia) * [x] MSRTT wrongly advertised when not properly supported (making Darwinia MSAA not work) * [x] Texture barriers wrongly advertised when not properly supported (X11/Emacs glitching) * [x] Water glitches near screen edges in Darwinia if you get up really close. * [x] (6.2/explicit sync regression) KWin flashes magenta rectangles when starting up, or right before going to sleep. * [x] Nautilus is pink with Adwaita * [x] Google Maps & PDF viewer on Firefox use too much memory * [x] Corrupted X11 apps on GNOME/XWayland * [x] Rendering with some render targets disabled regressed (Inochi2D, KiCad 3D glitching) * [x] Figma rendering is glitchy * [x] CSS transforms in Firefox render incorrectly * [x] Complex GTK apps (GIMP, etc.) under XWayland sometimes glitch magenta ## Issues that aren't driver bugs * [ ] gnome-terminal has a glitchy background ([upstream bug](https://gitlab.gnome.org/GNOME/vte/-/issues/284) from 2 years ago, they don't seem interested in fixing it...) * [ ] Moving the mouse above blurred backgrounds in KWin/Wayland causes artifacts ([upstream bug](https://bugs.kde.org/show_bug.cgi?id=462811)) * [x] KWin has single-pixel glitches when fractional scaling is enabled (Fixed in plasma 5.27.7) * [x] OBS screen sharing does not work (PipeWire regression, [fixed in 0.3.62](https://gitlab.freedesktop.org/pipewire/pipewire/-/releases/0.3.62), plus [KWin bug](https://invent.kde.org/plasma/kwin/-/merge_requests/3345) (merged for 5.26.5, ETA Jan 3), plus [core Mesa bug](https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/20397)) * [x] Some WebGL apps on Firefox (like Plex and QuakeJS) can hang/fail to render ([upstream bug](https://bugzilla.mozilla.org/show_bug.cgi?id=1805626), fixed for Firefox 110) * [ ] Firefox sometimes flashes magenta on startup ([upstream bug](https://bugzilla.mozilla.org/show_bug.cgi?id=1831051)) * [x] SuperTuxKart sometimes has rectangular black glitches ([upstream bug](https://github.com/supertuxkart/stk-code/issues/4863)) (worked around in driver for now) * [x] QuakeJS has jittery geometry ([emscripten bug](https://github.com/emscripten-core/emscripten/pull/8628), fixed years ago but they need to update). Probably applies to any WebGL apps with similar issues too. * [ ] Window corruption / magenta regions with Java OpenGL rendering enabled (Java does not double buffer its OpenGL visual so it will always tear/break on any modern system from this decade, just worse on Apple with compression.) * [x] Google Sheets gets blurry on scroll (~~Google Sheets bug~~ [Firefox bug](https://bugzilla.mozilla.org/show_bug.cgi?id=1845309)) (workaround: `ASAHI_MESA_DEBUG=no16`)

havealoha · September 7, 2023, 5:23am

Ah figured out how to submit Fedora bug

https://bugzilla.redhat.com/show_bug.cgi?id=2237821

bwibking · September 10, 2023, 9:37pm

I’ve opened a bug report for the automatic bug reporting tool (ABRT) not being able to upload the crash report: 2238248 – ABRT can't submit crash report: processing failed.