Version-Release number of selected component: plasma-systemsettings-5.4.3-1.fc22 Additional info: reporter: libreport-2.6.3 backtrace_rating: 3 cmdline: systemsettings5 crash_function: glGetIntegerv executable: /usr/bin/systemsettings5 global_pid: 5127 kernel: 4.2.8-200.fc22.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (4 frames) #0 glGetIntegerv #1 QSGRenderContext::initialize(QOpenGLContext*) at /usr/include/qt5/QtGui/qopenglfunctions.h:826 #3 QSGRenderThread::run() at /usr/src/debug/qtdeclarative-opensource-src-5.5.1/src/quick/scenegraph/qsgthreadedrenderloop.cpp:676 #4 QThreadPrivate::start(void*) at thread/qthread_unix.cpp:331
Created attachment 1109521 [details] File: backtrace
Created attachment 1109522 [details] File: cgroup
Created attachment 1109523 [details] File: core_backtrace
Created attachment 1109524 [details] File: dso_list
Created attachment 1109525 [details] File: environ
Created attachment 1109526 [details] File: limits
Created attachment 1109527 [details] File: maps
Created attachment 1109528 [details] File: mountinfo
Created attachment 1109529 [details] File: namespaces
Created attachment 1109530 [details] File: open_fds
Created attachment 1109531 [details] File: proc_pid_status
Created attachment 1109532 [details] File: var_log_messages
From the backtrace on retrace.fedoraproject.org : Frame # Function Binary Source or offset Line 1 glGetIntegerv /usr/lib64/nvidia/libGL.so.1 0xcc7e9 - So this is likely caused by a bad nvidia binary driver install (typically by using the nvidia libGL while using the nouveau driver. Brandon can you try removing all the rpmfusion nvidia pkgs, and then reboot and see if that fixes things?
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.