Description of problem: I wished to start a new program at startup, and had clicked the add button for programs in the Startup and Shutdown window. I typed in the program (with arguments) in the bar above the KDE menus and clicked OK. A properties window opened with the base program as the name. That was not what I wanted, so I changed the name, and checked that the full command line would be executed. Then I clicked OK. A new line appeared in the startup list, but it did not have my changed name, and it did not show the command line at all. I clicked on the properties button, changed the name there, and when I clicked OK, a window popup saying the decktop file did not exist in in the autostart directory. Then the crash occurred. I realize now that I had mis-typed part of the command line path, and perhaps that was the problem. Version-Release number of selected component: plasma-systemsettings-5.5.3-1.fc23 Additional info: reporter: libreport-2.6.3 backtrace_rating: 4 cmdline: /usr/bin/systemsettings5 crash_function: QMetaObject::invokeMethod executable: /usr/bin/systemsettings5 global_pid: 21167 kernel: 4.3.3-300.fc23.x86_64 runlevel: 3 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 QMetaObject::invokeMethod at kernel/qmetaobject.cpp:1464 #2 KDialogJobUiDelegate::Private::next at ../../src/kdialogjobuidelegate.cpp:82 #3 QObject::event at kernel/qobject.cpp:1239 #4 QApplicationPrivate::notify_helper at kernel/qapplication.cpp:3716 #5 QApplication::notify at kernel/qapplication.cpp:3499 #6 QCoreApplication::notifyInternal at kernel/qcoreapplication.cpp:965 #7 QCoreApplication::sendEvent at kernel/qcoreapplication.h:224 #8 QCoreApplicationPrivate::sendPostedEvents at kernel/qcoreapplication.cpp:1593 #9 QCoreApplication::sendPostedEvents at kernel/qcoreapplication.cpp:1451 #10 postEventSourceDispatch at kernel/qeventdispatcher_glib.cpp:271
Created attachment 1115626 [details] File: backtrace
Created attachment 1115627 [details] File: cgroup
Created attachment 1115628 [details] File: core_backtrace
Created attachment 1115629 [details] File: dso_list
Created attachment 1115630 [details] File: environ
Created attachment 1115631 [details] File: exploitable
Created attachment 1115632 [details] File: limits
Created attachment 1115633 [details] File: maps
Created attachment 1115634 [details] File: mountinfo
Created attachment 1115635 [details] File: namespaces
Created attachment 1115636 [details] File: open_fds
Created attachment 1115637 [details] File: proc_pid_status
Created attachment 1115638 [details] File: var_log_messages
This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '23'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 23 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 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.