Kile's log parser appears to be vulnerable to the same bug as TeXStudio's. The issue is diagnosed on TeX SE at http://tex.stackexchange.com/questions/358990/all-warnings-and-errors-of-my-document-refer-to-forest-sty/359152#359152. Like TeXStudio, if the log contains an empty parentheses pair (i.e. '()'), of the kind routinely output by xparse, all errors, warnings etc. will be attributed to the package, class or file responsible. For example, in the example posted initially on TeX SE, everything is attributed to Forest. In the minimised version in the answer, everything is attributed to the minimal package. The following code can be used to demonstrate the bug. \begin{filecontents}{demobug.sty} \ProvidesPackage{demobug} \typeout{()} \end{filecontents} \documentclass{article} \usepackage{demobug} %\typeout{)} \begin{document} xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx \sewt \end{document} The log parser attributes both the overfull box and the undefined control sequence to demobug.sty, opening that package in the editor for inspection. Uncommenting the following line %\typeout{)} is a workaround which enables at least some messages to be correctly attributed. (I have tested only minimally, so I don't know how robust the workaround is.) TeXStudio has identified the bug in their parser and will include a fix in 2.12.4 (http://tex.stackexchange.com/a/359098/). I don't know if the bug in Kile's parser is the same, but hope that it can be fixed also.
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!