Description of problem: Closing display settings window. Version-Release number of selected component: plasma-systemsettings-5.3.2-1.fc22 Additional info: reporter: libreport-2.6.1 backtrace_rating: 4 cmdline: /usr/bin/systemsettings5 crash_function: QQuickItemPrivate::addToDirtyList() executable: /usr/bin/systemsettings5 global_pid: 1912 kernel: 4.0.8-300.fc22.x86_64 runlevel: N 5 type: CCpp uid: 1000
Created attachment 1057665 [details] File: backtrace
Created attachment 1057666 [details] File: cgroup
Created attachment 1057667 [details] File: core_backtrace
Created attachment 1057668 [details] File: dso_list
Created attachment 1057669 [details] File: environ
Created attachment 1057670 [details] File: limits
Created attachment 1057671 [details] File: maps
Created attachment 1057672 [details] File: mountinfo
Created attachment 1057673 [details] File: namespaces
Created attachment 1057674 [details] File: open_fds
Created attachment 1057675 [details] File: proc_pid_status
Created attachment 1057676 [details] File: var_log_messages
Another user experienced a similar problem: After booting up and logging in to a plasma session: * the same things were displayed on both monitors of my 2-monitor system. * there were 3 xeyes on each monitor. I tried to re-configure to a 2-monitor system. That's when the problem occurred. I don't know if the problem can be reproduced. This (and other problems, both in plasma and gnome) started showing up after upgrading to f22 three days ago. reporter: libreport-2.6.2 backtrace_rating: 4 cmdline: /usr/bin/systemsettings5 crash_function: QQuickItemPrivate::addToDirtyList() executable: /usr/bin/systemsettings5 global_pid: 2729 kernel: 4.1.6-201.fc22.x86_64 package: plasma-systemsettings-5.4.1-1.fc22 reason: systemsettings5 killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1001
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.