If that doesn’t tell us enough, you could try running it through a debugger particularly if it is indeed a genuine segmentation fault, that should give us some information regarding where the fault is coming from. You could try running mrview with the -debug option, and see if that provides us with any more information. AMD have a long history of driver issues that they’ve never really been able to shake, and I’m not personally aware of anybody who has installed MRtrix3 on a Windows system with a Radeon card (though there’s been issues with them on Linux in the past). However it does raise concerns regarding the state of the installed drivers. It’s not impossible for mrview to run despite encountering this warning. it is only mrview that fails to run?Īnd a warning message about not being able to determine OpenGL configuration. Can you confirm that non-GUI applications run fine, i.e.
0 kommentar(er)
