New issue by MechDR on void-packages repository

https://github.com/void-linux/void-packages/issues/49763

Description:
### Is this a new report?

Yes

### System Info

Void 6.6.25_1 x86_64 GenuineIntel notuptodate rrrmFFFFFFFFF

### Package(s) Affected

blender-4.0.2_2

### Does a report exist for this bug with the project's home (upstream) and/or another distro?

_No response_

### Expected behaviour

Start up... or at least spit out something regarding the GPU not being compatible, because I have no idea if it is (AMD Radeon HD 4650).

But, I also tested it on 2 other PCs, both with older Intel onboard graphics (one has a 2nd gen i3, the other has a G41 GPU, Dual/Quad core era), it just crashes there as well

### Actual behaviour

Her is what `tmp\blender.crash.txt` holds.

````
# Blender 4.0.2, Unknown revision

# backtrace
blender(+0xf43dd3) [0x555c3770edd3]
blender(+0x862ea9) [0x555c3702dea9]
/usr/lib/libc.so.6(+0x3f8c0) [0x7fe78a3738c0]
blender(+0xf8a15c) [0x555c3775515c]
blender(+0xf8a1bd) [0x555c377551bd]
blender(+0xf53d04) [0x555c3771ed04]
blender(+0xf6998e) [0x555c3773498e]
blender(+0xf6f124) [0x555c3773a124]
blender(+0x8385e8) [0x555c370035e8]
/usr/lib/libc.so.6(+0x29c4c) [0x7fe78a35dc4c]
/usr/lib/libc.so.6(__libc_start_main+0x85) [0x7fe78a35dd05]
blender(+0x85e8b1) [0x555c370298b1]

# Python backtrace
````

### Steps to reproduce

Try running it on unsupported hardware (in a VM for example, with no GPU passthrough), because I think that is the actual problem, since no one has filed a bug report yet, which means for people with newer hardware and use it, it works just fine.