GitLab

Previously, the only indication that no terminal was configured for
command alarms was a misleading error message "Failure to execute
command" when the alarm triggered. Now a warning is given when the
alarm is created, and the error message is improved at trigger time.

If the file didn't exist, its path wouldn't be expanded.

In case of conflict in i18n, keep the version of the branch "ours"
To resolve a particular conflict, "git checkout --ours path/to/file.desktop"

remove entities kappname + package, not used in kf5
bump date + releaseinfo
remove obsolete options
add missing option --triggerEvent
replace Help options with qt5options + kf5options
remove KResources related stuff
remove &reporting.bugs; + &updating.documentation;, not used in kf5
fix path for kalarm files
remove appendix installation, outdated
update screenshots
REVIEW:129621

The QCoreApplication instance wasn't deleted before libraries
were unloaded, which resulted in a crash during clean-up. See
https://github.com/lxde/lxqt/issues/1193#issuecomment-260337417.

The QCoreApplication instance wasn't deleted before libraries
were unloaded, which resulted in a crash during clean-up. See
https://github.com/lxde/lxqt/issues/1193#issuecomment-260337417.

KDBusService doesn't supply any command line arguments in its
activateRequested() signal unless there is at least one command
line option (in addition to the program name) in the command
invocation.

Forward port of Applications/16.08 commit
6bd68f98d675e30fab24713e63dfe72cdfd6f4f5.

The file path in the resource config file was being set to a local
path, whereas it must be set to a URL.

Forward port of 72b42951fc44bccf5dcbfa0a986f39e6e3b3e86e (16.08 branch)