Description of problem: In VirtualBox, M5, KDE, 64-bit Package(s) under test: blender default install of blender [root@localhost wilcal]# urpmi blender Package blender-2.73a-1.mga5.x86_64 is already installed In Vbox running blender from a terminal results in the following error: [wilcal@localhost ~]$ blender libGL error: pci id for fd 8: 80ee:beef, driver (null) libGL error: core dri or dri2 extension not found libGL error: failed to load driver: vboxvideo GLEW Error (0x0001): GLEW_ERROR_NO_GL_VERSION: Missing GL version Writing: /tmp/blender.crash.txt Segmentation fault Probably missing OpenGL 2.x support. Works fine on real hardware.
(In reply to William Kenney from comment #0) > GLEW Error (0x0001): GLEW_ERROR_NO_GL_VERSION: Missing GL version > Writing: /tmp/blender.crash.txt > Segmentation fault > > Probably missing OpenGL 2.x support. > It might be nice for the maintainer to be able to read your /tmp/blender.crash.txt Do you mind attaching it? (unless, of course, there was nothing more in it than in the paste from your terminal that you posted in comment #0 )
CC: (none) => marja11Assignee: bugsquad => geiger.david68210Source RPM: (none) => blender
I can reproduce this issue on a mga5 VM, but I don't know if it come from blender or rather from VirtualBox. Note that on a Cauldron (mga6) VM it works fine, no segfault. @tmb: what do you think about that?
CC: (none) => tmb
Hi Bill, Thank you for having taken the needed time to report this issue! (and DavidDavid for having reproduced and looked into it) Did this bug get fixed? If so, please change its status to RESOLVED - FIXED If it didn't, then we regret that we weren't able to fix it in Mageia 5. Mageia 5 has officially reached its End of Life on December 31st, 2017 https://blog.mageia.org/en/2017/11/07/mageia-5-eol-postponed/ It only continued to get important security updates since then, because we are waiting for a big Plasma5 update in Mageia 6, that'll fix many of the Mageia 5 => 6 upgrade issues. If you haven't seen that this bug got fixed, then please check whether this bug still exists in Mageia 6. If it does, then please change the Version (near the top, at the left) to "6". If you know it exists in Cauldron, then change Version to Cauldron. If you see it in both Cauldron and Mageia 6, then please set Version to Cauldron and add MGA6TOO on the Whiteboard. Thanks, Marja
Is it related to bug 22326 ?
CC: (none) => jyri2000
(In reply to Jüri Ivask from comment #4) > Is it related to bug 22326 ? Maybe not, because that was a Mageia7_cauldron issue, and, rereading this report, I see: (In reply to David GEIGER from comment #2) > I can reproduce this issue on a mga5 VM, but I don't know if it come from > blender or rather from VirtualBox. > > Note that on a Cauldron (mga6) VM it works fine, no segfault. > So back then Mageia 6_cauldron didn't have it. Closing this report as OLD, because Mageia 5 is no longer maintained. I assume it is better to reopen bug 22326 if that issue happens on Mageia 6, too.
Status: NEW => RESOLVEDResolution: (none) => OLD