** Description changed: New MATE 20.04 installation with all original settings for Power Management and Screensaver on desktop computer. After awakening computer from Screensaver, explosion of log entries in syslog fills up root partition (normal free space is 20GB). If explosion does not occur on first awakening from Screensaver then retry several more times. Here is sample from syslog: May 17 17:03:34 jim-pc org.mate.panel.applet.BriskMenuFactory[14549]: move 0 from 1 to 6 (-1) Prio: 104 May 17 17:03:34 jim-pc org.mate.panel.applet.BriskMenuFactory[14549]: move 0 from 2 to 3 (-1) Prio: 4 May 17 17:03:34 jim-pc org.mate.panel.applet.BriskMenuFactory[14549]: move 5 from 9 to 3 (-1) Prio: 9 May 17 17:03:34 jim-pc org.mate.panel.applet.BriskMenuFactory[14549]: move 0 from 6 to 2 (-1) Prio: 7 May 17 17:03:34 jim-pc org.mate.panel.applet.BriskMenuFactory[14549]: move 0 from 6 to 3 (-1) Prio: 49 May 17 17:03:34 jim-pc org.mate.panel.applet.BriskMenuFactory[14549]: move 1 from 6 to 3 (-1) Prio: 44 May 17 17:03:34 jim-pc org.mate.panel.applet.BriskMenuFactory[14549]: move 2 from 6 to 3 (-1) Prio: 39 May 17 17:03:34 jim-pc org.mate.panel.applet.BriskMenuFactory[14549]: move 3 from 6 to 3 (-1) Prio: 34 May 17 17:03:34 jim-pc org.mate.panel.applet.BriskMenuFactory[14549]: move 4 from 9 to 3 (-1) Prio: 14 May 17 17:03:34 jim-pc org.mate.panel.applet.BriskMenuFactory[14549]: move 4 from 6 to 3 (-1) Prio: 29 May 17 17:03:34 jim-pc org.mate.panel.applet.BriskMenuFactory[14549]: move 5 from 6 to 3 (-1) Prio: 24 May 17 17:03:34 jim-pc org.mate.panel.applet.BriskMenuFactory[14549]: move 6 from 6 to 3 (-1) Prio: 19 May 17 17:03:34 jim-pc org.mate.panel.applet.BriskMenuFactory[14549]: move 3 from 9 to 3 (-1) Prio: 19 May 17 17:03:34 jim-pc org.mate.panel.applet.BriskMenuFactory[14549]: move 7 from 6 to 3 (-1) Prio: 14 LATER: After a week of further testing, I believe my problem to be heat related. Specifically, the syslog - "jim-pc org.mate.panel.applet.BriskMenuFactory[14549]" - explosion occurs after 4 or 5 hours of the computer being turned on. If no one else is having this problem, I think it's safe to conclude that the problem is specific - to my hardware. Thanks, + to my hardware. + + Have run stress-ng. No errors showing up. Set up logrotate. Up to 3GB in + syslog after only 3 hours run time.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879322 Title: syslog filling up root partition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1879322/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
