Budgie 20.04 syslog grows into several GB

every time i delete the syslog it grows to several GB within days. With a 640 MB file, approx. 639 Mb were filled with something like this:
print-layout-begin
Apr 5 22:52:26 schulze-GA-78LMT-USB3-6-0 plank-1.desktop [6206]: Play0: | AS | JS | 9S | TS | TS AS
Apr 5 22:52:26 schulze-GA-78LMT-USB3-6-0 plank-1.desktop [6206]: Play1: | 4S | 4S | 9S | QS 7S
Apr 5 22:52:26 schulze-GA-78LMT-USB3-6-0 plank-1.desktop [6206]: Play2: | 3S | 2S | 5S | JS 7S 6S 5S 4S 3S
Apr 5 22:52:26 schulze-GA-78LMT-USB3-6-0 plank-1.desktop [6206]: Play3: | 3S | 5S | 6S 4S
Apr 5 22:52:26 schulze-GA-78LMT-USB3-6-0 plank-1.desktop [6206]: Play4: | 6S | AS | 5S TS 9S
Apr 5 22:52:26 schulze-GA-78LMT-USB3-6-0 plank-1.desktop [6206]: Play5: | 3S | JS 9S
Apr 5 22:52:26 schulze-GA-78LMT-USB3-6-0 plank-1.desktop [6206]: Play6: | 8S | 2S 5S 4S
Apr 5 22:52:26 schulze-GA-78LMT-USB3-6-0 plank-1.desktop [6206]: Play7: | 6S | KS | JS | 7S KS QS
Apr 5 22:52:26 schulze-GA-78LMT-USB3-6-0 plank-1.desktop [6206]: Play8: | JS | KS | 8S | 8S TS 9S 8S
Apr 5 22:52:26 schulze-GA-78LMT-USB3-6-0 plank-1.desktop [6206]: Play9: | 6S | 6S 3S 2S AS
Apr 5 22:52:26 schulze-GA-78LMT-USB3-6-0 plank-1.desktop [6206]: Deal0: | QS | 9S | 7S | QS | TS | 2S | 9S | AS | KS | KS
Apr 5 22:52:26 schulze-GA-78LMT-USB3-6-0 plank-1.desktop [6206]: Deal1: | 7S | JS | 4S | 6S | 3S | 8S | AS | AS | 7S | 4S
Apr 5 22:52:26 schulze-GA-78LMT-USB3-6-0 plank-1.desktop [6206]: Deal2: | QS | 9S | KS | JS | AS | 2S | KS | 5S | 3S | QS
Apr 5 22:52:26 schulze-GA-78LMT-USB3-6-0 plank-1.desktop [6206]: Deal3: | JS | 2S | 8S | 2S | 7S | 6S | TS | 8S | TS | QS
Apr 5 22:52:26 schulze-GA-78LMT-USB3-6-0 plank-1.desktop [6206]: Deal4: | 3S | 5S | 8S | 4S | 2S | 5S | QS | KS | 7S | TS
Apr 5 22:52:26 schulze-GA-78LMT-USB3-6-0 plank-1.desktop [6206]: Off:
Apr 5 22:52:26 schulze-GA-78LMT-USB3-6-0 plank-1.desktop [6206]: print-layout-end

Where is the mistake? What can I do?

don’t really know - I don’t recognise what “plank-1.desktop” is.

What changes to the plank configuration have you made?

Maybe resetting plank will help:

killall plank
rm -rf ~/.config/plank

logout and login.

Thank you for the fast answer. I will test and report

your solution seems to have helped. So far, the syslog has only been a few kb. Thanks a lot

Happy too early. last night the syslog was 3 GB again. Aslo I deleted the syslog, ended the plank and deleted it from the autostart and instead created an additional budgie panel as a dock at the bottom of the screen (only with the icon task list). After a few minutes the syslog was again 64 MB, but this time with “budgie-panel.desktop [2908]: print-layout-begin …”

Sorry - no idea. I cannot reproduce this. I’m using a couple of days old clean install.

The problem is still present. is there a possibility to prevent entries in the syslog?

please use paste.ubuntu.com and copy-paste the output of

journalctl -ae | grep plank

I don’t recognise the initial trace you gave - that above will be more meaningful.

i used https://paste.ubuntu.com/p/VYrZ8FBVbR/

umm … is that it? that’s very small.

yes, but the syslog is also very small at the moment because I only restarted the pc at 10 p.m. I will post a version tomorrow if the syslog is again several Gb in size.

Today after 45 Mintues using Budgie syslog grows up to 2.5 GB.
https://paste.ubuntu.com/p/Jf7PpczvqW/

what version of plank are you using?

dpkg -s plank | grep Version

dpkg -s plank | grep Version
Version: 0.11.89-1

Sorry - I’ve no idea what you have done to make plank to behave like that

it is not only plank. “budgie-panel.desktop [2908]: print-layout-begin …” if plank was not aktiv

It does look like you have turned on debugging somehow - no idea how though.

you can turn it off again?

dunno - the only google thread that I’ve found is this - I don’t speak french though

Similar trace - have you been fiddling with journald stuff? or systemd configurations?

https://forum.ubuntu-fr.org/viewtopic.php?id=2045783

the thread treats nearly the same problem. I will try the solution there. Many thanks for your effort

it is not nearly the same, it is the same. I also like to play with Kpatience in between and the program seems to be the culprit.

1 Like