Felix Miata wrote: > QOpenGLShader: could not create shader > QOpenGLShader: could not create shader > QOpenGLShader: could not create shader > QOpenGLShader: could not create shader > QQuickCustomMaterialShader: Shader compilation failed: > "" > QOpenGLShader: could not create shader > > Thread 1 "systemsettings5" received signal SIGSEGV, Segmentation fault. > 0x00000000 in ?? () > (gdb) thread apply all bt > > Thread 4 (Thread 0xacd01b40 (LWP 1492)): > #0 0xb7fd5d21 in __kernel_vsyscall () > Backtrace stopped: Cannot access memory at address 0xacd0100c > > Thread 3 (Thread 0xb0749b40 (LWP 1490)): > #0 0xb7fd5d21 in __kernel_vsyscall () > Backtrace stopped: Cannot access memory at address 0xb0748fec > > Thread 2 (Thread 0xb172fb40 (LWP 1488)): > #0 0xb7fd5d21 in __kernel_vsyscall () > Backtrace stopped: Cannot access memory at address 0xb172f07c > > Thread 1 (Thread 0xb1c34880 (LWP 1484)): > #0 0x00000000 in ?? () > Backtrace stopped: Cannot access memory at address 0xbfffd8ec > (gdb) quit > A debugging session is active. So, that all looks pretty bad, as if something very seriously wrong on this system. First major problem: QOpenGLShader: could not create shader video driver isn't functioning properly second: Thread 4 (Thread 0xacd01b40 (LWP 1492)): #0 0xb7fd5d21 in __kernel_vsyscall () Backtrace stopped: Cannot access memory at address 0xacd0100c never seen that before, but if kernel calls are failing preventing debugging, there's not much we can do. May be worth trying a fresh/clean f28 live image, and see how that works for you on this system. If better, may be worth re-installing. -- Rex _______________________________________________ kde mailing list -- kde@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to kde-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/kde@xxxxxxxxxxxxxxxxxxxxxxx
