Comment 2 for bug 1851898

Thank you for taking the time to report this bug and helping to make Ubuntu better.

You haven't provided any details as to what messages are being logged (I wonder if they aren't kpat messages, but something else that occurs during or due to game, eg. video or other driver messages etc).

I loaded a 'live' system (Lubuntu 20.04 because it was handy), installed `kpat` & tried playing a game (Klondike - you didn't provide game played; part of it was in 'demo' mode) watching via `du -hs /var/log` in a terminal for changes, but directory size remained static at 464K.

I booted the Kubuntu 19.10 ISO, and played another game of klondike. As before a good portion was in demo mode (more than half), but I reversed moves, and did other things players would likely do as in prior test. During this game (screen stopped at Congratulations! We have won) the size of /var/log/ didn't alter for either (using `du -hs` to monitor it during game in a terminal). I could not re-produce this issue. Possibly `kpat` is a trigger that causes messages from other packages to be created...

My ~/.xsession-errors did grow to 117M on Kubuntu 19.10 which does seem to relate to `kpat`, but it's not the 5GB you mentioned (you didn't specify a game, I chose my favorite Klondike)

I'm marking this "incomplete" as your report says you don't have `kpat` installed, thus no package details have been provided.

You've provided little detail as to what messages filled /var/log/; in fact neither my 19.10 Kubuntu test, nor Lubuntu 20.04 test output anything to /var/log/syslog so I suggest you look, and provide some detail. This will provide clues as to where the messages come from, if it's related to hardware (that differs from my own) and other packages that are involved.

Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures.

At a minimum, we need:
1. The specific steps or actions you took that caused you to encounter the problem.
2. The behavior you expected.
3. The behavior you actually encountered (in as much detail as possible).
Thanks!

When you provide these details, please change status back to "New". If you believe I'm in error, or have overlooked something - please likewise return status to "New" and leave a comment explaining why. Thank you again for helping to make Ubuntu better.