Full Disk Warning

Questions about Grub, UEFI,the liveCD and the installer
Forum rules
Before you post please read how to get help
User avatar
LanceM
Level 9
Level 9
Posts: 2665
Joined: Sun Jul 08, 2018 11:50 pm

Re: Full Disk Warning

Post by LanceM »

And and any low disk space warnings? Probably not. So see how it goes. When Mint 20 arrives in June or so, maybe you'll want to do a fresh install then.
You can keep an eye on /var/log by running Disk Usage Analyzer and see if it gets out of hand in size. It shouldn't. Mine is attached.
Var.jpg
Bear in mind, the things we did might not identify the cause of the problem in the first place, but it will probably get you by. It might have been caused by you deleting snapshots the wrong way, maybe, maybe not. I'm leaning toward that. Good luck!
To mark this issue solved, go to your original 1st post and click the edit pencil and add [Solved] at the beginning of the title and click Submit.
Mint accepts donations: https://linuxmint.com/donors.php

YoMan
Level 3
Level 3
Posts: 109
Joined: Sat Dec 03, 2016 12:38 pm

Re: Full Disk Warning

Post by YoMan »

No more "disc full" warnings as yet. The warning came long before I deleted the snapshots. At the time it ocurred I was doing some cutting and pasting in a LibreOffice document. Its seems strange that a common task like that would cause that problem but, what do I know :D

At some point during all of this, I was instructed to run the "tail" command and keep it running. Should I be still doing that and, if so, what should I be looking for?

My major concern was that the cause might be hardware related. This is a new to me refurbished model. It has a short warranty. So, if there is something wrong I would like to find out soon. Any suggestions? If there is no way to determine, I'll just keep on keeping on. :D

When I purchased my first ssd a few years ago, I learned that it was necessary to run something called "Trim". Can you tell me if Mint runs this by default or do I need to create a cron job?

User avatar
LanceM
Level 9
Level 9
Posts: 2665
Joined: Sun Jul 08, 2018 11:50 pm

Re: Full Disk Warning

Post by LanceM »

Ask the man that knows about that - smurmophs. He knows more about Mint than any five of me. To do that go to that post on page 2 and click the " quote marks. This will send him a notification that his comment was quoted and also opens a reply page. You can get his opinion when he answers.
To mark this issue solved, go to your original 1st post and click the edit pencil and add [Solved] at the beginning of the title and click Submit.
Mint accepts donations: https://linuxmint.com/donors.php

User avatar
LanceM
Level 9
Level 9
Posts: 2665
Joined: Sun Jul 08, 2018 11:50 pm

Re: Full Disk Warning

Post by LanceM »

When I purchased my first ssd a few years ago, I learned that it was necessary to run something called "Trim". Can you tell me if Mint runs this by default or do I need to create a cron job?
Trim schedule on Mint 19.x can be checked in terminal:

Code: Select all

systemctl status fstrim.timer
See when last done:

Code: Select all

journalctl | grep fstrim
By default it runs on system startup Monday morning. Or thereafter if the PC wasn't booted on Monday
To mark this issue solved, go to your original 1st post and click the edit pencil and add [Solved] at the beginning of the title and click Submit.
Mint accepts donations: https://linuxmint.com/donors.php

YoMan
Level 3
Level 3
Posts: 109
Joined: Sat Dec 03, 2016 12:38 pm

Re: Full Disk Warning

Post by YoMan »

Thanks again for all your help. I'll keep my fingers crossed.

User avatar
LanceM
Level 9
Level 9
Posts: 2665
Joined: Sun Jul 08, 2018 11:50 pm

Re: Full Disk Warning

Post by LanceM »

Something else I thought of to do. Start nemo file manager and click file system. Navigate to var and highlight it, right click and open as root. Now open the Timeshift folder. If there are multitudes of files in there, close it. Now start Timeshift and delete any snapshots. Now go back to var/log/Timeshift and open as root. Delete all files (not the folder of course). Now start Timeshift and create a new snapshot.
To mark this issue solved, go to your original 1st post and click the edit pencil and add [Solved] at the beginning of the title and click Submit.
Mint accepts donations: https://linuxmint.com/donors.php

YoMan
Level 3
Level 3
Posts: 109
Joined: Sat Dec 03, 2016 12:38 pm

Re: Full Disk Warning [solved]

Post by YoMan »

smurphos wrote:
Wed May 27, 2020 12:34 am
The timeshift snapshots are going to be huge, because they have been snapshoting the hugely inflated log files.

Yoman - you first priority should be identifying what is spamming your logs or you'll be back to a full disc again.

Run the command below and leaving it running in a terminal - it monitors new lines being added to syslog. Are there a rapidly repeating message(s)? If so what are they?

Code: Select all

tail -f /var/log/syslog
I have finished working with Lance to change settings regarding various logs. I also have properly deleted all snapshots and re-installed Timeshift. The new snapshot = 7.6 GB. Should I continue running /var/log/syslog? If so, should I watch for anything other than repeating messages?

YoMan
Level 3
Level 3
Posts: 109
Joined: Sat Dec 03, 2016 12:38 pm

Re: Full Disk Warning

Post by YoMan »

LanceM wrote:
Thu May 28, 2020 5:51 pm
Something else I thought of to do. Start nemo file manager and click file system. Navigate to var and highlight it, right click and open as root. Now open the Timeshift folder. If there are multitudes of files in there, close it. Now start Timeshift and delete any snapshots. Now go back to var/log/Timeshift and open as root. Delete all files (not the folder of course). Now start Timeshift and create a new snapshot.
Just curious. What does that do differently than what you described yesterday at 4:11pm?

User avatar
LanceM
Level 9
Level 9
Posts: 2665
Joined: Sun Jul 08, 2018 11:50 pm

Re: Full Disk Warning

Post by LanceM »

Just cleans up the old Timeshift logs so the history starts fresh with no old Timeshift baggage in the logs.
To mark this issue solved, go to your original 1st post and click the edit pencil and add [Solved] at the beginning of the title and click Submit.
Mint accepts donations: https://linuxmint.com/donors.php

User avatar
smurphos
Level 16
Level 16
Posts: 6859
Joined: Fri Sep 05, 2014 12:18 am
Location: Britisher
Contact:

Re: Full Disk Warning [solved]

Post by smurphos »

YoMan wrote:
Thu May 28, 2020 6:04 pm
I have finished working with Lance to change settings regarding various logs. I also have properly deleted all snapshots and re-installed Timeshift. The new snapshot = 7.6 GB. Should I continue running /var/log/syslog? If so, should I watch for anything other than repeating messages?
Are the files /var/log/syslog and /var/log/kern.log still growing in size at silly rate? If yes then you want to see what are the messages spamming the logs so we can try and guide you to fix whatever the problem is causing the logs to be spammed.

For reference - half an hour after a reboot my syslog is 5.3kb and my kern.log is 1MB
For custom Nemo actions, useful scripts for the Cinnamon desktop, and Cinnamox themes visit my Github pages.

YoMan
Level 3
Level 3
Posts: 109
Joined: Sat Dec 03, 2016 12:38 pm

Re: Full Disk Warning

Post by YoMan »


Are the files /var/log/syslog and /var/log/kern.log still growing in size at silly rate? If yes then you want to see what are the messages spamming the logs so we can try and guide you to fix whatever the problem is causing the logs to be spammed.

For reference - half an hour after a reboot my syslog is 5.3kb and my kern.log is 1MB
I have started it running again and I'll check to see how much it grows today.
Right after bootup, it was 887kb.

Edit:

2 hours later (10:30 am), size has increased to 950 kb. There are quit a few of repeats regarding [UFW BLOCK]. Here is the last page full. There are many more occurrances on previous pages:

Code: Select all

 PREC=0xC0 TTL=1 ID=3121 PROTO=2 
May 29 10:17:01 wiliam-Yoga CRON[3480]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
May 29 10:19:05 wiliam-Yoga kernel: [ 3433.288859] [UFW BLOCK] IN=wlp4s0 OUT= MAC=01:00:5e:00:00:01:5c:e3:0e:c2:84:12:08:00 SRC=10.0.0.1 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0xC0 TTL=1 ID=3122 PROTO=2 
May 29 10:21:10 wiliam-Yoga kernel: [ 3558.372034] [UFW BLOCK] IN=wlp4s0 OUT= MAC=01:00:5e:00:00:01:5c:e3:0e:c2:84:12:08:00 SRC=10.0.0.1 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0xC0 TTL=1 ID=3123 PROTO=2 
May 29 10:23:15 wiliam-Yoga kernel: [ 3683.299319] [UFW BLOCK] IN=wlp4s0 OUT= MAC=01:00:5e:00:00:01:5c:e3:0e:c2:84:12:08:00 SRC=10.0.0.1 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0xC0 TTL=1 ID=3124 PROTO=2 
May 29 10:23:44 wiliam-Yoga gvfsd-metadata[1622]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed
May 29 10:23:44 wiliam-Yoga gvfsd-metadata[1622]: message repeated 7 times: [ g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed]
May 29 10:25:20 wiliam-Yoga kernel: [ 3808.327542] [UFW BLOCK] IN=wlp4s0 OUT= MAC=01:00:5e:00:00:01:5c:e3:0e:c2:84:12:08:00 SRC=10.0.0.1 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0xC0 TTL=1 ID=3125 PROTO=2 
May 29 10:25:27 wiliam-Yoga rtkit-daemon[1454]: Supervising 3 threads of 1 processes of 1 users.
May 29 10:25:27 wiliam-Yoga rtkit-daemon[1454]: message repeated 3 times: [ Supervising 3 threads of 1 processes of 1 users.]
May 29 10:25:27 wiliam-Yoga rtkit-daemon[1454]: Successfully made thread 3614 of process 3548 (n/a) owned by '1000' RT at priority 10.
May 29 10:25:27 wiliam-Yoga rtkit-daemon[1454]: Supervising 4 threads of 2 processes of 1 users.
May 29 10:27:25 wiliam-Yoga kernel: [ 3933.289176] [UFW BLOCK] IN=wlp4s0 OUT= MAC=01:00:5e:00:00:01:5c:e3:0e:c2:84:12:08:00 SRC=10.0.0.1 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0xC0 TTL=1 ID=3126 PROTO=2 
May 29 10:29:30 wiliam-Yoga kernel: [ 4058.385644] [UFW BLOCK] IN=wlp4s0 OUT= MAC=01:00:5e:00:00:01:5c:e3:0e:c2:84:12:08:00 SRC=10.0.0.1 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0xC0 TTL=1 ID=3127 PROTO=2 
May 29 10:25:29 wiliam-Yoga rtkit-daemon[1454]: message repeated 6 times: [ Supervising 4 threads of 2 processes of 1 users.]
May 29 10:30:43 wiliam-Yoga gnome-terminal-[1810]: g_menu_insert_item: assertion 'G_IS_MENU_ITEM (item)' failed
 
2:30 pm Now have two files; Syslog.1=981kb, syslog=20kb. The later one appears to be active.

8:10 pm, syslog=133kb

Edit 2 June:
After watching the syslog file for a couple of days, it appear to grow in size until it reaches 1 MB. I think it is then copying itself into a second file syslog.1 and starting over. I've not seen any more "disk full" errors. I'm calling this one [solved]

YoMan
Level 3
Level 3
Posts: 109
Joined: Sat Dec 03, 2016 12:38 pm

Re: Full Disk Warning [solved]

Post by YoMan »

Trim schedule on Mint 19.x can be checked in terminal:

Code: Select all

systemctl status fstrim.timer
See when last done:

Code: Select all

journalctl | grep fstrim
By default it runs on system startup Monday morning. Or thereafter if the PC wasn't booted on Monday
I have installed nvme-cli. Following is the result of

Code: Select all

  sudo nvme smart-log /dev/nvme0n1 

Code: Select all

Smart Log for NVME device:nvme0n1 namespace-id:ffffffff
critical_warning                    : 0
temperature                         : 33 C
available_spare                     : 100%
available_spare_threshold           : 10%
percentage_used                     : 0%
data_units_read                     : 1,134,358
data_units_written                  : 2,642,483
host_read_commands                  : 12,369,252
host_write_commands                 : 15,041,432
controller_busy_time                : 82
power_cycles                        : 275
power_on_hours                      : 163
unsafe_shutdowns                    : 29
media_errors                        : 0
num_err_log_entries                 : 0
Warning Temperature Time            : 0
Critical Composite Temperature Time : 0
Temperature Sensor 1                : 33 C
Thermal Management T1 Trans Count   : 0
Thermal Management T2 Trans Count   : 0
Thermal Management T1 Total Time    : 0
Thermal Management T2 Total Time    : 0
 

User avatar
LanceM
Level 9
Level 9
Posts: 2665
Joined: Sun Jul 08, 2018 11:50 pm

Re: Full Disk Warning [solved]

Post by LanceM »

Looks okay, so probably can rule out drive problems. Guess it's just a mystery at this point. See how it goes.
To mark this issue solved, go to your original 1st post and click the edit pencil and add [Solved] at the beginning of the title and click Submit.
Mint accepts donations: https://linuxmint.com/donors.php

YoMan
Level 3
Level 3
Posts: 109
Joined: Sat Dec 03, 2016 12:38 pm

Re: Full Disk Warning [solved]

Post by YoMan »

LanceM wrote:
Fri Jun 05, 2020 3:05 pm
Looks okay, so probably can rule out drive problems. Guess it's just a mystery at this point. See how it goes.
OK. Again. I appreciate the help.

YoMan
Level 3
Level 3
Posts: 109
Joined: Sat Dec 03, 2016 12:38 pm

Re: Full Disk Warning

Post by YoMan »

My log files are growing still. Both kern.log and syslog files have grown to about 20GB each. I ran

Code: Select all

clean-log.sh
and the kern.log file is back to a minimal size. However, syslog is still at about 20GB. The following is the result of

Code: Select all

sudo du -h /var/log
:

Code: Select all

13M	/var/log/journal/aaa642a1efb049fba8d6ca0c8d22ff0a
13M	/var/log/journal
1.2M	/var/log/timeshift
20K	/var/log/cups
4.0K	/var/log/openvpn
4.0K	/var/log/samba
4.0K	/var/log/hp/tmp
8.0K	/var/log/hp
4.0K	/var/log/speech-dispatcher
16K	/var/log/lightdm
928K	/var/log/installer
144K	/var/log/apt
20G	/var/log
I have also run

Code: Select all

tail -f /var/log/syslog
. The following is the last about 2 hours of the run:

Code: Select all

tail -f /var/log/syslog
Jun 22 17:28:22 wiliam-Yoga rtkit-daemon[1600]: message repeated 3 times: [ Supervising 3 threads of 1 processes of 1 users.]
Jun 22 17:28:22 wiliam-Yoga rtkit-daemon[1600]: Successfully made thread 2408 of process 2340 (n/a) owned by '1000' RT at priority 10.
Jun 22 17:28:22 wiliam-Yoga rtkit-daemon[1600]: Supervising 4 threads of 2 processes of 1 users.
Jun 22 17:28:24 wiliam-Yoga rtkit-daemon[1600]: message repeated 8 times: [ Supervising 4 threads of 2 processes of 1 users.]
Jun 22 17:28:26 wiliam-Yoga systemd[1]: Starting Message of the Day...
Jun 22 17:28:26 wiliam-Yoga systemd[1]: Started Message of the Day.
Jun 22 17:28:28 wiliam-Yoga rtkit-daemon[1600]: Supervising 4 threads of 2 processes of 1 users.
Jun 22 17:28:55 wiliam-Yoga kernel: [  511.667737] [UFW BLOCK] IN=wlp4s0 OUT= MAC=01:00:5e:00:00:01:5c:e3:0e:c2:84:12:08:00 SRC=10.0.0.1 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0xC0 TTL=1 ID=4860 PROTO=2 
Jun 22 17:28:28 wiliam-Yoga rtkit-daemon[1600]: Supervising 4 threads of 2 processes of 1 users.
Jun 22 17:30:34 wiliam-Yoga gnome-terminal-[1916]: g_menu_insert_item: assertion 'G_IS_MENU_ITEM (item)' failed
Jun 22 17:31:00 wiliam-Yoga kernel: [  636.695702] [UFW BLOCK] IN=wlp4s0 OUT= MAC=01:00:5e:00:00:01:5c:e3:0e:c2:84:12:08:00 SRC=10.0.0.1 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0xC0 TTL=1 ID=4861 PROTO=2 
Jun 22 17:31:01 wiliam-Yoga systemd-resolved[772]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.
Jun 22 17:31:01 wiliam-Yoga systemd-resolved[772]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.
Jun 22 17:31:04 wiliam-Yoga dbus-daemon[885]: [system] Activating via systemd: service name='org.freedesktop.PackageKit' unit='packagekit.service' requested by ':1.81' (uid=0 pid=3131 comm="/usr/bin/gdbus call --system --dest org.freedeskto" label="unconfined")
Jun 22 17:31:04 wiliam-Yoga systemd[1]: Starting PackageKit Daemon...
Jun 22 17:31:04 wiliam-Yoga PackageKit: daemon start
Jun 22 17:31:04 wiliam-Yoga dbus-daemon[885]: [system] Successfully activated service 'org.freedesktop.PackageKit'
Jun 22 17:31:04 wiliam-Yoga systemd[1]: Started PackageKit Daemon.
Jun 22 17:35:10 wiliam-Yoga kernel: [  886.649467] [UFW BLOCK] IN=wlp4s0 OUT= MAC=01:00:5e:00:00:01:5c:e3:0e:c2:84:12:08:00 SRC=10.0.0.1 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0xC0 TTL=1 ID=4863 PROTO=2 
Jun 22 17:35:26 wiliam-Yoga systemd[1]: Starting Cleanup of Temporary Directories...
Jun 22 17:35:26 wiliam-Yoga systemd[1]: Started Cleanup of Temporary Directories.
Jun 22 17:35:27 wiliam-Yoga anacron[867]: Job `cron.monthly' started
Jun 22 17:35:27 wiliam-Yoga anacron[867]: Job `cron.monthly' terminated
Jun 22 17:35:27 wiliam-Yoga anacron[867]: Normal exit (2 jobs run)
Jun 22 17:37:15 wiliam-Yoga kernel: [ 1011.678228] [UFW BLOCK] IN=wlp4s0 OUT= MAC=01:00:5e:00:00:01:5c:e3:0e:c2:84:12:08:00 SRC=10.0.0.1 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0xC0 TTL=1 ID=4864 PROTO=2 
Jun 22 17:39:20 wiliam-Yoga kernel: [ 1136.605050] [UFW BLOCK] IN=wlp4s0 OUT= MAC=01:00:5e:00:00:01:5c:e3:0e:c2:84:12:08:00 SRC=10.0.0.1 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0xC0 TTL=1 ID=4865 PROTO=2 
Jun 22 17:43:30 wiliam-Yoga kernel: [ 1386.663235] [UFW BLOCK] IN=wlp4s0 OUT= MAC=01:00:5e:00:00:01:5c:e3:0e:c2:84:12:08:00 SRC=10.0.0.1 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0xC0 TTL=1 ID=4867 PROTO=2 
Jun 22 17:47:40 wiliam-Yoga kernel: [ 1636.618343] [UFW BLOCK] IN=wlp4s0 OUT= MAC=01:00:5e:00:00:01:5c:e3:0e:c2:84:12:08:00 SRC=10.0.0.1 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0xC0 TTL=1 ID=4869 PROTO=2 
Jun 22 17:51:50 wiliam-Yoga kernel: [ 1886.573764] [UFW BLOCK] IN=wlp4s0 OUT= MAC=01:00:5e:00:00:01:5c:e3:0e:c2:84:12:08:00 SRC=10.0.0.1 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0xC0 TTL=1 ID=4871 PROTO=2 
Jun 22 17:56:00 wiliam-Yoga kernel: [ 2136.529900] [UFW BLOCK] IN=wlp4s0 OUT= MAC=01:00:5e:00:00:01:5c:e3:0e:c2:84:12:08:00 SRC=10.0.0.1 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0xC0 TTL=1 ID=4873 PROTO=2 
Jun 22 18:00:01 wiliam-Yoga CRON[3309]: (root) CMD (timeshift --check --scripted)
Jun 22 18:00:01 wiliam-Yoga crontab[3342]: (root) LIST (root)
Jun 22 18:00:01 wiliam-Yoga crontab[3343]: (root) LIST (root)
Jun 22 18:00:01 wiliam-Yoga CRON[3308]: (CRON) info (No MTA installed, discarding output)
Jun 22 18:00:10 wiliam-Yoga kernel: [ 2386.588517] [UFW BLOCK] IN=wlp4s0 OUT= MAC=01:00:5e:00:00:01:5c:e3:0e:c2:84:12:08:00 SRC=10.0.0.1 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0xC0 TTL=1 ID=4875 PROTO=2 
Jun 22 18:02:15 wiliam-Yoga kernel: [ 2511.617789] [UFW BLOCK] IN=wlp4s0 OUT= MAC=01:00:5e:00:00:01:5c:e3:0e:c2:84:12:08:00 SRC=10.0.0.1 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0xC0 TTL=1 ID=4876 PROTO=2 
Jun 22 18:03:40 wiliam-Yoga systemd[1]: Started Run anacron jobs.
Jun 22 18:03:40 wiliam-Yoga anacron[3365]: Anacron 2.3 started on 2020-06-22
Jun 22 18:03:40 wiliam-Yoga anacron[3365]: Normal exit (0 jobs run)
Jun 22 18:06:25 wiliam-Yoga kernel: [ 2761.573182] [UFW BLOCK] IN=wlp4s0 OUT= MAC=01:00:5e:00:00:01:5c:e3:0e:c2:84:12:08:00 SRC=10.0.0.1 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0xC0 TTL=1 ID=4878 PROTO=2 
Jun 22 18:08:29 wiliam-Yoga kernel: [ 2886.499817] [UFW BLOCK] IN=wlp4s0 OUT= MAC=01:00:5e:00:00:01:5c:e3:0e:c2:84:12:08:00 SRC=10.0.0.1 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0xC0 TTL=1 ID=4879 PROTO=2 
Jun 22 18:10:34 wiliam-Yoga kernel: [ 3011.528928] [UFW BLOCK] IN=wlp4s0 OUT= MAC=01:00:5e:00:00:01:5c:e3:0e:c2:84:12:08:00 SRC=10.0.0.1 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0xC0 TTL=1 ID=4880 PROTO=2 
Jun 22 18:14:44 wiliam-Yoga kernel: [ 3261.484367] [UFW BLOCK] IN=wlp4s0 OUT= MAC=01:00:5e:00:00:01:5c:e3:0e:c2:84:12:08:00 SRC=10.0.0.1 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0xC0 TTL=1 ID=4882 PROTO=2 
Jun 22 18:17:01 wiliam-Yoga CRON[3445]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Jun 22 18:21:00 wiliam-Yoga kernel: [ 3636.875865] [UFW BLOCK] IN=wlp4s0 OUT= MAC=01:00:5e:00:00:01:5c:e3:0e:c2:84:12:08:00 SRC=10.0.0.1 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0xC0 TTL=1 ID=4885 PROTO=2 
Jun 22 18:21:25 wiliam-Yoga kernel: [ 3662.426524] wacom 0003:056A:5093.0005: wacom_wac_queue_insert: kfifo has filled, starting to drop events
Jun 22 18:21:25 wiliam-Yoga kernel: [ 3662.442530] wacom 0003:056A:5093.0005: wacom_wac_queue_insert: kfifo has filled, starting to drop events
Jun 22 18:21:25 wiliam-Yoga kernel: [ 3662.446523] wacom 0003:056A:5093.0005: wacom_wac_queue_insert: kfifo has filled, starting to drop events
Jun 22 18:21:25 wiliam-Yoga kernel: [ 3662.481458] wacom 0003:056A:5093.0005: wacom_wac_queue_insert: kfifo has filled, starting to drop events
Jun 22 18:21:25 wiliam-Yoga kernel: [ 3662.486523] wacom 0003:056A:5093.0005: wacom_wac_queue_insert: kfifo has filled, starting to drop events
Jun 22 18:21:25 wiliam-Yoga kernel: [ 3662.518524] wacom 0003:056A:5093.0005: wacom_wac_queue_insert: kfifo has filled, starting to drop events
Jun 22 18:21:25 wiliam-Yoga kernel: [ 3662.521497] wacom 0003:056A:5093.0005: wacom_wac_queue_insert: kfifo has filled, starting to drop events
Jun 22 18:21:25 wiliam-Yoga kernel: [ 3662.526523] wacom 0003:056A:5093.0005: wacom_wac_queue_insert: kfifo has filled, starting to drop events
Jun 22 18:21:25 wiliam-Yoga kernel: [ 3662.536457] wacom 0003:056A:5093.0005: wacom_wac_queue_insert: kfifo has filled, starting to drop events
Jun 22 18:21:25 wiliam-Yoga kernel: [ 3662.541531] wacom 0003:056A:5093.0005: wacom_wac_queue_insert: kfifo has filled, starting to drop events
Jun 22 18:21:25 wiliam-Yoga kernel: [ 3662.561535] wacom 0003:056A:5093.0005: wacom_wac_queue_insert: kfifo has filled, starting to drop events
Jun 22 18:21:25 wiliam-Yoga kernel: [ 3662.566538] wacom 0003:056A:5093.0005: wacom_wac_queue_insert: kfifo has filled, starting to drop events
Jun 22 18:21:25 wiliam-Yoga kernel: [ 3662.576500] wacom 0003:056A:5093.0005: wacom_wac_queue_insert: kfifo has filled, starting to drop events
Jun 22 18:21:25 wiliam-Yoga kernel: [ 3662.581499] wacom 0003:056A:5093.0005: wacom_wac_queue_insert: kfifo has filled, starting to drop events
Jun 22 18:21:25 wiliam-Yoga kernel: [ 3662.591452] wacom 0003:056A:5093.0005: wacom_wac_queue_insert: kfifo has filled, starting to drop events
Jun 22 18:21:25 wiliam-Yoga kernel: [ 3662.596486] wacom 0003:056A:5093.0005: wacom_wac_queue_insert: kfifo has filled, starting to drop events
Jun 22 18:21:25 wiliam-Yoga kernel: [ 3662.606457] wacom 0003:056A:5093.0005: wacom_wac_queue_insert: kfifo has filled, starting to drop events
Jun 22 18:21:25 wiliam-Yoga kernel: [ 3662.611494] wacom 0003:056A:5093.0005: wacom_wac_queue_insert: kfifo has filled, starting to drop events
Jun 22 18:21:37 wiliam-Yoga kernel: [ 3674.148797] [UFW BLOCK] IN=wlp4s0 OUT= MAC=01:00:5e:00:00:fb:5c:e3:0e:c2:84:12:08:00 SRC=10.0.0.1 DST=224.0.0.251 LEN=36 TOS=0x00 PREC=0xC0 TTL=1 ID=15159 PROTO=2 
Jun 22 18:24:17 wiliam-Yoga gnome-terminal-[1916]: g_menu_insert_item: assertion 'G_IS_MENU_ITEM (item)' failed
Jun 22 18:24:20 wiliam-Yoga zeitgeist-fts[1711]: Unable to get info on application://gnome-terminal-server.desktop
Jun 22 18:27:23 wiliam-Yoga gnome-terminal-[1916]: g_menu_insert_item: assertion 'G_IS_MENU_ITEM (item)' failed
Jun 22 18:27:26 wiliam-Yoga zeitgeist-fts[1711]: Unable to get info on application://gnome-terminal-server.desktop
Jun 22 18:29:03 wiliam-Yoga NetworkManager[927]: <info>  [1592868543.4159] manager: sleep: sleep requested (sleeping: no  enabled: yes)
Jun 22 18:29:03 wiliam-Yoga NetworkManager[927]: <info>  [1592868543.4163] manager: NetworkManager state is now ASLEEP
Jun 22 18:29:03 wiliam-Yoga NetworkManager[927]: <info>  [1592868543.4170] device (wlp4s0): state change: activated -> deactivating (reason 'sleeping', sys-iface-state: 'managed')
Jun 22 18:29:03 wiliam-Yoga NetworkManager[927]: <info>  [1592868543.4270] device (wlp4s0): state change: deactivating -> disconnected (reason 'sleeping', sys-iface-state: 'managed')
Jun 22 18:29:03 wiliam-Yoga avahi-daemon[883]: Withdrawing address record for 2601:4c4:c200:b940::85ea on wlp4s0.
Jun 22 18:29:03 wiliam-Yoga avahi-daemon[883]: Withdrawing address record for 2601:4c4:c200:b940:d5a:c2d3:2980:1621 on wlp4s0.
Jun 22 18:29:03 wiliam-Yoga avahi-daemon[883]: Withdrawing address record for 2601:4c4:c200:b940:74d6:d2c1:500:d178 on wlp4s0.
Jun 22 18:29:03 wiliam-Yoga avahi-daemon[883]: Leaving mDNS multicast group on interface wlp4s0.IPv6 with address 2601:4c4:c200:b940:74d6:d2c1:500:d178.
Jun 22 18:29:03 wiliam-Yoga avahi-daemon[883]: Joining mDNS multicast group on interface wlp4s0.IPv6 with address fe80::8944:3b61:7f9a:5006.
Jun 22 18:29:03 wiliam-Yoga dbus-daemon[885]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.14' (uid=0 pid=927 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined")
Jun 22 18:29:03 wiliam-Yoga avahi-daemon[883]: Registering new address record for fe80::8944:3b61:7f9a:5006 on wlp4s0.*.
Jun 22 18:29:03 wiliam-Yoga avahi-daemon[883]: Withdrawing address record for fe80::8944:3b61:7f9a:5006 on wlp4s0.
Jun 22 18:29:03 wiliam-Yoga avahi-daemon[883]: Leaving mDNS multicast group on interface wlp4s0.IPv6 with address fe80::8944:3b61:7f9a:5006.
Jun 22 18:29:03 wiliam-Yoga avahi-daemon[883]: Interface wlp4s0.IPv6 no longer relevant for mDNS.
Jun 22 18:29:03 wiliam-Yoga systemd[1]: Starting Network Manager Script Dispatcher Service...
Jun 22 18:29:03 wiliam-Yoga NetworkManager[927]: <info>  [1592868543.4818] dhcp4 (wlp4s0): canceled DHCP transaction, DHCP client pid 1245
Jun 22 18:29:03 wiliam-Yoga NetworkManager[927]: <info>  [1592868543.4819] dhcp4 (wlp4s0): state changed bound -> done
Jun 22 18:29:03 wiliam-Yoga dbus-daemon[885]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Jun 22 18:29:03 wiliam-Yoga systemd[1]: Started Network Manager Script Dispatcher Service.
Jun 22 18:29:03 wiliam-Yoga NetworkManager[927]: <info>  [1592868543.4884] dhcp6 (wlp4s0): canceled DHCP transaction, DHCP client pid 1336
Jun 22 18:29:03 wiliam-Yoga NetworkManager[927]: <info>  [1592868543.4885] dhcp6 (wlp4s0): state changed bound -> done
Jun 22 18:29:03 wiliam-Yoga nm-dispatcher: req:1 'connectivity-change': new request (1 scripts)
Jun 22 18:29:03 wiliam-Yoga nm-dispatcher: req:1 'connectivity-change': start running ordered scripts...
Jun 22 18:29:03 wiliam-Yoga avahi-daemon[883]: Withdrawing address record for 10.0.0.253 on wlp4s0.
Jun 22 18:29:03 wiliam-Yoga avahi-daemon[883]: Leaving mDNS multicast group on interface wlp4s0.IPv4 with address 10.0.0.253.
Jun 22 18:29:03 wiliam-Yoga kernel: [ 4120.170929] wlp4s0: deauthenticating from 5c:e3:0e:c2:84:10 by local choice (Reason: 3=DEAUTH_LEAVING)
Jun 22 18:29:03 wiliam-Yoga avahi-daemon[883]: Interface wlp4s0.IPv4 no longer relevant for mDNS.
Jun 22 18:29:03 wiliam-Yoga wpa_supplicant[904]: wlp4s0: CTRL-EVENT-DISCONNECTED bssid=5c:e3:0e:c2:84:10 reason=3 locally_generated=1
Jun 22 18:29:03 wiliam-Yoga wpa_supplicant[904]: wlp4s0: CTRL-EVENT-SIGNAL-CHANGE above=0 signal=0 noise=9999 txrate=0
Jun 22 18:29:03 wiliam-Yoga NetworkManager[927]: <info>  [1592868543.5209] device (wlp4s0): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
Jun 22 18:29:03 wiliam-Yoga nm-dispatcher: req:2 'down' [wlp4s0]: new request (1 scripts)
Jun 22 18:29:03 wiliam-Yoga nm-dispatcher: req:2 'down' [wlp4s0]: start running ordered scripts...
Jun 22 18:29:03 wiliam-Yoga wpa_supplicant[904]: wlp4s0: CTRL-EVENT-SCAN-FAILED ret=-100
Jun 22 18:29:03 wiliam-Yoga wpa_supplicant[904]: nl80211: deinit ifname=p2p-dev-wlp4s0 disabled_11b_rates=0
Jun 22 18:29:03 wiliam-Yoga wpa_supplicant[904]: nl80211: deinit ifname=wlp4s0 disabled_11b_rates=0
Jun 22 18:29:03 wiliam-Yoga systemd[1]: Reached target Sleep.
Jun 22 18:29:03 wiliam-Yoga systemd[1]: Starting Suspend...
Jun 22 18:29:03 wiliam-Yoga systemd-sleep[3636]: Suspending system...
Jun 22 18:29:03 wiliam-Yoga kernel: [ 4120.327905] PM: suspend entry (deep)
Jun 22 18:29:03 wiliam-Yoga kernel: [ 4120.338499] Filesystems sync: 0.010 seconds
Jun 22 19:13:04 wiliam-Yoga kernel: [ 4120.341139] Freezing user space processes ... (elapsed 0.006 seconds) done.
Jun 22 19:13:04 wiliam-Yoga kernel: [ 4120.347784] OOM killer disabled.
Jun 22 19:13:04 wiliam-Yoga kernel: [ 4120.347785] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
Jun 22 19:13:04 wiliam-Yoga kernel: [ 4120.349178] printk: Suspending console(s) (use no_console_suspend to debug)
Jun 22 19:13:04 wiliam-Yoga kernel: [ 4120.616329] e1000e: EEE TX LPI TIMER: 00000011
Jun 22 19:13:04 wiliam-Yoga kernel: [ 4120.757556] ACPI: EC: interrupt blocked
Jun 22 19:13:04 wiliam-Yoga kernel: [ 4120.804988] ACPI: Preparing to enter system sleep state S3
Jun 22 19:13:04 wiliam-Yoga kernel: [ 4120.811697] ACPI: EC: event blocked
Jun 22 19:13:04 wiliam-Yoga kernel: [ 4120.811698] ACPI: EC: EC stopped
Jun 22 19:13:04 wiliam-Yoga kernel: [ 4120.811700] PM: Saving platform NVS memory
Jun 22 19:13:04 wiliam-Yoga kernel: [ 4120.811709] Disabling non-boot CPUs ...
Jun 22 19:13:04 wiliam-Yoga kernel: [ 4120.814467] smpboot: CPU 1 is now offline
Jun 22 19:13:04 wiliam-Yoga kernel: [ 4120.815723] IRQ 143: no longer affine to CPU2
Jun 22 19:13:04 wiliam-Yoga kernel: [ 4120.817805] smpboot: CPU 2 is now offline
Jun 22 19:13:04 wiliam-Yoga kernel: [ 4120.818842] IRQ 123: no longer affine to CPU3
Jun 22 19:13:04 wiliam-Yoga kernel: [ 4120.818847] IRQ 127: no longer affine to CPU3
Jun 22 19:13:04 wiliam-Yoga kernel: [ 4120.819882] smpboot: CPU 3 is now offline
Jun 22 19:13:04 wiliam-Yoga kernel: [ 4120.823051] ACPI: Low-level resume complete
Jun 22 19:13:04 wiliam-Yoga kernel: [ 4120.823137] ACPI: EC: EC started
Jun 22 19:13:04 wiliam-Yoga kernel: [ 4120.823138] PM: Restoring platform NVS memory
Jun 22 19:13:04 wiliam-Yoga kernel: [ 4120.829556] Enabling non-boot CPUs ...
Jun 22 19:13:04 wiliam-Yoga kernel: [ 4120.829603] x86: Booting SMP configuration:
Jun 22 19:13:04 wiliam-Yoga kernel: [ 4120.829604] smpboot: Booting Node 0 Processor 1 APIC 0x2
Jun 22 19:13:04 wiliam-Yoga kernel: [ 4120.830376] CPU1 is up
Jun 22 19:13:04 wiliam-Yoga kernel: [ 4120.830405] smpboot: Booting Node 0 Processor 2 APIC 0x1
Jun 22 19:13:04 wiliam-Yoga kernel: [ 4120.831128] CPU2 is up
Jun 22 19:13:04 wiliam-Yoga kernel: [ 4120.831161] smpboot: Booting Node 0 Processor 3 APIC 0x3
Jun 22 19:13:04 wiliam-Yoga kernel: [ 4120.831827] CPU3 is up
Jun 22 19:13:04 wiliam-Yoga kernel: [ 4120.833288] ACPI: Waking up from system sleep state S3
Jun 22 19:13:04 wiliam-Yoga kernel: [ 4120.846128] ACPI: EC: interrupt unblocked
Jun 22 19:13:04 wiliam-Yoga kernel: [ 4120.890112] ACPI: EC: event unblocked
Jun 22 19:13:04 wiliam-Yoga kernel: [ 4121.001960] nvme nvme0: 4/0/0 default/read/poll queues
Jun 22 19:13:04 wiliam-Yoga kernel: [ 4121.180179] usb 1-9: reset full-speed USB device number 4 using xhci_hcd
Jun 22 19:13:04 wiliam-Yoga kernel: [ 4121.455317] usb 1-8: reset high-speed USB device number 3 using xhci_hcd
Jun 22 19:13:04 wiliam-Yoga kernel: [ 4121.612471] OOM killer enabled.
Jun 22 19:13:04 wiliam-Yoga kernel: [ 4121.612473] Restarting tasks ... done.
Jun 22 19:13:04 wiliam-Yoga kernel: [ 4121.621543] thermal thermal_zone2: failed to read out thermal zone (-61)
Jun 22 19:13:04 wiliam-Yoga systemd[1]: Started Run anacron jobs.
Jun 22 19:13:04 wiliam-Yoga anacron[3708]: Anacron 2.3 started on 2020-06-22
Jun 22 19:13:04 wiliam-Yoga anacron[3708]: Normal exit (0 jobs run)
Jun 22 19:13:04 wiliam-Yoga kernel: [ 4121.648101] psmouse serio1: synaptics: queried max coordinates: x [..5678], y [..4754]
Jun 22 19:13:04 wiliam-Yoga systemd-sleep[3636]: System resumed.
Jun 22 19:13:04 wiliam-Yoga kernel: [ 4121.655888] PM: suspend exit
Jun 22 19:13:04 wiliam-Yoga systemd[1]: Started Suspend.
Jun 22 19:13:04 wiliam-Yoga systemd[1]: sleep.target: Unit not needed anymore. Stopping.
Jun 22 19:13:04 wiliam-Yoga systemd[1]: Stopped target Sleep.
Jun 22 19:13:04 wiliam-Yoga systemd[1]: Reached target Suspend.
Jun 22 19:13:04 wiliam-Yoga systemd[1]: suspend.target: Unit not needed anymore. Stopping.
Jun 22 19:13:04 wiliam-Yoga systemd[1]: Stopped target Suspend.
Jun 22 19:13:04 wiliam-Yoga NetworkManager[927]: <info>  [1592871184.8441] manager: sleep: wake requested (sleeping: yes  enabled: yes)
Jun 22 19:13:04 wiliam-Yoga NetworkManager[927]: <info>  [1592871184.8442] device (enp0s31f6): state change: unavailable -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
Jun 22 19:13:04 wiliam-Yoga kernel: [ 4121.678987] psmouse serio1: synaptics: queried min coordinates: x [1262..], y [1098..]
Jun 22 19:13:04 wiliam-Yoga kernel: [ 4121.746584] e1000e: enp0s31f6 NIC Link is Down
Jun 22 19:13:04 wiliam-Yoga NetworkManager[927]: <info>  [1592871184.9234] device (enp0s31f6): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'managed')
Jun 22 19:13:05 wiliam-Yoga kernel: [ 4121.916418] mmc0: cannot verify signal voltage switch
Jun 22 19:13:05 wiliam-Yoga NetworkManager[927]: <info>  [1592871185.1172] device (wlp4s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'managed')
Jun 22 19:13:05 wiliam-Yoga NetworkManager[927]: <info>  [1592871185.3766] manager: NetworkManager state is now DISCONNECTED
Jun 22 19:13:05 wiliam-Yoga wpa_supplicant[904]: dbus: fill_dict_with_properties dbus_interface=fi.w1.wpa_supplicant1.Interface dbus_property=Stations getter failed
Jun 22 19:13:05 wiliam-Yoga wpa_supplicant[904]: dbus: wpa_dbus_get_object_properties: failed to get object properties: (none) none
Jun 22 19:13:05 wiliam-Yoga wpa_supplicant[904]: dbus: Failed to construct signal
Jun 22 19:13:05 wiliam-Yoga wpa_supplicant[904]: dbus: fill_dict_with_properties dbus_interface=fi.w1.wpa_supplicant1.Interface dbus_property=Stations getter failed
Jun 22 19:13:05 wiliam-Yoga NetworkManager[927]: <info>  [1592871185.4282] device (wlp4s0): supplicant interface state: starting -> ready
Jun 22 19:13:05 wiliam-Yoga NetworkManager[927]: <info>  [1592871185.4283] device (wlp4s0): state change: unavailable -> disconnected (reason 'supplicant-available', sys-iface-state: 'managed')
Jun 22 19:13:05 wiliam-Yoga kernel: [ 4122.536181] ish-hid {33AECD58-B679-4E54-9BD9-A04D34F0C226}: [hid-ish]: enum_devices_done OK, num_hid_devices=3
Jun 22 19:13:07 wiliam-Yoga ModemManager[865]: <info>  Couldn't check support for device '/sys/devices/pci0000:00/0000:00:1c.2/0000:04:00.0': not supported by any plugin
Jun 22 19:13:07 wiliam-Yoga ModemManager[865]: <info>  Couldn't check support for device '/sys/devices/pci0000:00/0000:00:1f.6': not supported by any plugin
Jun 22 19:13:08 wiliam-Yoga NetworkManager[927]: <info>  [1592871188.9122] policy: auto-activating connection 'A972-2.4'
Jun 22 19:13:08 wiliam-Yoga NetworkManager[927]: <info>  [1592871188.9134] device (wlp4s0): Activation: starting connection 'A972-2.4' (c0347b59-7d5c-423f-8aa2-1e5276f3a085)
Jun 22 19:13:08 wiliam-Yoga NetworkManager[927]: <info>  [1592871188.9138] device (wlp4s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Jun 22 19:13:08 wiliam-Yoga NetworkManager[927]: <info>  [1592871188.9142] manager: NetworkManager state is now CONNECTING
Jun 22 19:13:08 wiliam-Yoga NetworkManager[927]: <info>  [1592871188.9150] device (wlp4s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Jun 22 19:13:08 wiliam-Yoga NetworkManager[927]: <info>  [1592871188.9156] device (wlp4s0): Activation: (wifi) access point 'A972-2.4' has security, but secrets are required.
Jun 22 19:13:08 wiliam-Yoga NetworkManager[927]: <info>  [1592871188.9160] device (wlp4s0): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
Jun 22 19:13:08 wiliam-Yoga NetworkManager[927]: <info>  [1592871188.9164] sup-iface[0x557c8d72f630,wlp4s0]: wps: type pbc start...
Jun 22 19:13:08 wiliam-Yoga NetworkManager[927]: <info>  [1592871188.9207] device (wlp4s0): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
Jun 22 19:13:08 wiliam-Yoga NetworkManager[927]: <info>  [1592871188.9211] device (wlp4s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Jun 22 19:13:08 wiliam-Yoga NetworkManager[927]: <info>  [1592871188.9213] device (wlp4s0): Activation: (wifi) connection 'A972-2.4' has security, and secrets exist.  No new secrets needed.
Jun 22 19:13:08 wiliam-Yoga NetworkManager[927]: <info>  [1592871188.9213] Config: added 'ssid' value 'A972-2.4'
Jun 22 19:13:08 wiliam-Yoga NetworkManager[927]: <info>  [1592871188.9213] Config: added 'scan_ssid' value '1'
Jun 22 19:13:08 wiliam-Yoga NetworkManager[927]: <info>  [1592871188.9213] Config: added 'bgscan' value 'simple:30:-80:86400'
Jun 22 19:13:08 wiliam-Yoga NetworkManager[927]: <info>  [1592871188.9213] Config: added 'key_mgmt' value 'WPA-PSK'
Jun 22 19:13:08 wiliam-Yoga NetworkManager[927]: <info>  [1592871188.9214] Config: added 'auth_alg' value 'OPEN'
Jun 22 19:13:08 wiliam-Yoga NetworkManager[927]: <info>  [1592871188.9214] Config: added 'psk' value '<hidden>'
Jun 22 19:13:08 wiliam-Yoga wpa_supplicant[904]: wlp4s0: SME: Trying to authenticate with 5c:e3:0e:c2:84:10 (SSID='A972-2.4' freq=5220 MHz)
Jun 22 19:13:08 wiliam-Yoga kernel: [ 4125.755706] wlp4s0: authenticate with 5c:e3:0e:c2:84:10
Jun 22 19:13:08 wiliam-Yoga NetworkManager[927]: <info>  [1592871188.9404] device (wlp4s0): supplicant interface state: ready -> authenticating
Jun 22 19:13:08 wiliam-Yoga kernel: [ 4125.764013] wlp4s0: send auth to 5c:e3:0e:c2:84:10 (try 1/3)
Jun 22 19:13:08 wiliam-Yoga kernel: [ 4125.771203] wlp4s0: authenticated
Jun 22 19:13:08 wiliam-Yoga wpa_supplicant[904]: wlp4s0: Trying to associate with 5c:e3:0e:c2:84:10 (SSID='A972-2.4' freq=5220 MHz)
Jun 22 19:13:08 wiliam-Yoga NetworkManager[927]: <info>  [1592871188.9528] device (wlp4s0): supplicant interface state: authenticating -> associating
Jun 22 19:13:08 wiliam-Yoga kernel: [ 4125.775295] wlp4s0: associate with 5c:e3:0e:c2:84:10 (try 1/3)
Jun 22 19:13:08 wiliam-Yoga kernel: [ 4125.777536] wlp4s0: RX AssocResp from 5c:e3:0e:c2:84:10 (capab=0x1411 status=0 aid=4)
Jun 22 19:13:08 wiliam-Yoga wpa_supplicant[904]: wlp4s0: Associated with 5c:e3:0e:c2:84:10
Jun 22 19:13:08 wiliam-Yoga wpa_supplicant[904]: wlp4s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Jun 22 19:13:08 wiliam-Yoga kernel: [ 4125.779517] wlp4s0: associated
Jun 22 19:13:08 wiliam-Yoga NetworkManager[927]: <info>  [1592871188.9611] device (wlp4s0): supplicant interface state: associating -> associated
Jun 22 19:13:08 wiliam-Yoga NetworkManager[927]: <info>  [1592871188.9727] device (wlp4s0): supplicant interface state: associated -> 4-way handshake
Jun 22 19:13:08 wiliam-Yoga wpa_supplicant[904]: wlp4s0: WPA: Key negotiation completed with 5c:e3:0e:c2:84:10 [PTK=CCMP GTK=CCMP]
Jun 22 19:13:08 wiliam-Yoga wpa_supplicant[904]: wlp4s0: CTRL-EVENT-CONNECTED - Connection to 5c:e3:0e:c2:84:10 completed [id=0 id_str=]
Jun 22 19:13:08 wiliam-Yoga wpa_supplicant[904]: wlp4s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-38 noise=9999 txrate=6000
Jun 22 19:13:08 wiliam-Yoga kernel: [ 4125.805054] IPv6: ADDRCONF(NETDEV_CHANGE): wlp4s0: link becomes ready
Jun 22 19:13:08 wiliam-Yoga NetworkManager[927]: <info>  [1592871188.9858] device (wlp4s0): supplicant interface state: 4-way handshake -> completed
Jun 22 19:13:08 wiliam-Yoga NetworkManager[927]: <info>  [1592871188.9859] device (wlp4s0): Activation: (wifi) Stage 2 of 5 (Device Configure) successful.  Connected to wireless network 'A972-2.4'.
Jun 22 19:13:08 wiliam-Yoga NetworkManager[927]: <info>  [1592871188.9860] device (wlp4s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Jun 22 19:13:08 wiliam-Yoga NetworkManager[927]: <info>  [1592871188.9863] dhcp4 (wlp4s0): activation: beginning transaction (timeout in 45 seconds)
Jun 22 19:13:08 wiliam-Yoga NetworkManager[927]: <info>  [1592871188.9924] dhcp4 (wlp4s0): dhclient started with pid 3756
Jun 22 19:13:08 wiliam-Yoga avahi-daemon[883]: Joining mDNS multicast group on interface wlp4s0.IPv6 with address fe80::8944:3b61:7f9a:5006.
Jun 22 19:13:08 wiliam-Yoga avahi-daemon[883]: New relevant interface wlp4s0.IPv6 for mDNS.
Jun 22 19:13:08 wiliam-Yoga avahi-daemon[883]: Registering new address record for fe80::8944:3b61:7f9a:5006 on wlp4s0.*.
Jun 22 19:13:09 wiliam-Yoga dhclient[3756]: DHCPREQUEST of 10.0.0.253 on wlp4s0 to 255.255.255.255 port 67 (xid=0x1e9eeef9)
Jun 22 19:13:09 wiliam-Yoga wpa_supplicant[904]: wlp4s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-38 noise=9999 txrate=866700
Jun 22 19:13:09 wiliam-Yoga kernel: [ 4125.874072] wlp4s0: Limiting TX power to 27 (30 - 3) dBm as advertised by 5c:e3:0e:c2:84:10
Jun 22 19:13:09 wiliam-Yoga dhclient[3756]: DHCPACK of 10.0.0.253 from 10.0.0.1
Jun 22 19:13:09 wiliam-Yoga NetworkManager[927]: <info>  [1592871189.1054] dhcp4 (wlp4s0):   address 10.0.0.253
Jun 22 19:13:09 wiliam-Yoga NetworkManager[927]: <info>  [1592871189.1054] dhcp4 (wlp4s0):   plen 24 (255.255.255.0)
Jun 22 19:13:09 wiliam-Yoga NetworkManager[927]: <info>  [1592871189.1054] dhcp4 (wlp4s0):   gateway 10.0.0.1
Jun 22 19:13:09 wiliam-Yoga NetworkManager[927]: <info>  [1592871189.1055] dhcp4 (wlp4s0):   lease time 604800
Jun 22 19:13:09 wiliam-Yoga NetworkManager[927]: <info>  [1592871189.1055] dhcp4 (wlp4s0):   hostname 'wiliam-Yoga'
Jun 22 19:13:09 wiliam-Yoga NetworkManager[927]: <info>  [1592871189.1055] dhcp4 (wlp4s0):   nameserver '75.75.75.75'
Jun 22 19:13:09 wiliam-Yoga NetworkManager[927]: <info>  [1592871189.1055] dhcp4 (wlp4s0):   nameserver '75.75.76.76'
Jun 22 19:13:09 wiliam-Yoga NetworkManager[927]: <info>  [1592871189.1055] dhcp4 (wlp4s0):   domain name 'hsd1.al.comcast.net'
Jun 22 19:13:09 wiliam-Yoga NetworkManager[927]: <info>  [1592871189.1055] dhcp4 (wlp4s0): state changed unknown -> bound
Jun 22 19:13:09 wiliam-Yoga avahi-daemon[883]: Joining mDNS multicast group on interface wlp4s0.IPv4 with address 10.0.0.253.
Jun 22 19:13:09 wiliam-Yoga NetworkManager[927]: <info>  [1592871189.1074] device (wlp4s0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Jun 22 19:13:09 wiliam-Yoga NetworkManager[927]: <info>  [1592871189.1079] device (wlp4s0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Jun 22 19:13:09 wiliam-Yoga NetworkManager[927]: <info>  [1592871189.1081] device (wlp4s0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Jun 22 19:13:09 wiliam-Yoga avahi-daemon[883]: New relevant interface wlp4s0.IPv4 for mDNS.
Jun 22 19:13:09 wiliam-Yoga NetworkManager[927]: <info>  [1592871189.1082] manager: NetworkManager state is now CONNECTED_LOCAL
Jun 22 19:13:09 wiliam-Yoga avahi-daemon[883]: Registering new address record for 10.0.0.253 on wlp4s0.IPv4.
Jun 22 19:13:09 wiliam-Yoga dhclient[3756]: bound to 10.0.0.253 -- renewal in 261661 seconds.
Jun 22 19:13:09 wiliam-Yoga NetworkManager[927]: <info>  [1592871189.1138] manager: NetworkManager state is now CONNECTED_SITE
Jun 22 19:13:09 wiliam-Yoga NetworkManager[927]: <info>  [1592871189.1139] policy: set 'A972-2.4' (wlp4s0) as default for IPv4 routing and DNS
Jun 22 19:13:09 wiliam-Yoga NetworkManager[927]: <info>  [1592871189.1153] device (wlp4s0): Activation: successful, device activated.
Jun 22 19:13:09 wiliam-Yoga nm-dispatcher: req:3 'up' [wlp4s0]: new request (1 scripts)
Jun 22 19:13:09 wiliam-Yoga nm-dispatcher: req:3 'up' [wlp4s0]: start running ordered scripts...
Jun 22 19:13:09 wiliam-Yoga systemd-resolved[772]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.
Jun 22 19:13:09 wiliam-Yoga systemd-resolved[772]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.
Jun 22 19:13:10 wiliam-Yoga NetworkManager[927]: <info>  [1592871190.2620] manager: NetworkManager state is now CONNECTED_GLOBAL
Jun 22 19:13:10 wiliam-Yoga nm-dispatcher: req:4 'connectivity-change': new request (1 scripts)
Jun 22 19:13:10 wiliam-Yoga nm-dispatcher: req:4 'connectivity-change': start running ordered scripts...
Jun 22 19:13:10 wiliam-Yoga cinnamon-screensaver-pam-helper: pam_ecryptfs: seteuid error
Jun 22 19:13:11 wiliam-Yoga NetworkManager[927]: <info>  [1592871191.2007] dhcp6 (wlp4s0): activation: beginning transaction (timeout in 45 seconds)
Jun 22 19:13:11 wiliam-Yoga NetworkManager[927]: <info>  [1592871191.2032] dhcp6 (wlp4s0): dhclient started with pid 3854
Jun 22 19:13:11 wiliam-Yoga avahi-daemon[883]: Leaving mDNS multicast group on interface wlp4s0.IPv6 with address fe80::8944:3b61:7f9a:5006.
Jun 22 19:13:11 wiliam-Yoga avahi-daemon[883]: Joining mDNS multicast group on interface wlp4s0.IPv6 with address 2601:4c4:c200:b940:74d6:d2c1:500:d178.
Jun 22 19:13:11 wiliam-Yoga avahi-daemon[883]: Registering new address record for 2601:4c4:c200:b940:74d6:d2c1:500:d178 on wlp4s0.*.
Jun 22 19:13:11 wiliam-Yoga avahi-daemon[883]: Withdrawing address record for fe80::8944:3b61:7f9a:5006 on wlp4s0.
Jun 22 19:13:11 wiliam-Yoga NetworkManager[927]: <info>  [1592871191.2049] policy: set 'A972-2.4' (wlp4s0) as default for IPv6 routing and DNS
Jun 22 19:13:12 wiliam-Yoga dhclient[3854]: XMT: Confirm on wlp4s0, interval 970ms.
Jun 22 19:13:12 wiliam-Yoga dhclient[3854]: RCV: Reply message on wlp4s0 from fe80::5ee3:eff:fec2:8412.
Jun 22 19:13:12 wiliam-Yoga dhclient[3854]: message status code Success: "Your addresses are correct for this link! Yay!"
Jun 22 19:13:12 wiliam-Yoga NetworkManager[927]: <info>  [1592871192.1978] dhcp6 (wlp4s0):   valid_lft 604800
Jun 22 19:13:12 wiliam-Yoga NetworkManager[927]: <info>  [1592871192.1979] dhcp6 (wlp4s0):   preferred_lft 604800
Jun 22 19:13:12 wiliam-Yoga NetworkManager[927]: <info>  [1592871192.1979] dhcp6 (wlp4s0):   address 2601:4c4:c200:b940::85ea
Jun 22 19:13:12 wiliam-Yoga NetworkManager[927]: <info>  [1592871192.1980] dhcp6 (wlp4s0):   nameserver '2001:558:feed::1'
Jun 22 19:13:12 wiliam-Yoga NetworkManager[927]: <info>  [1592871192.1980] dhcp6 (wlp4s0):   nameserver '2001:558:feed::2'
Jun 22 19:13:12 wiliam-Yoga NetworkManager[927]: <info>  [1592871192.1981] dhcp6 (wlp4s0): state changed unknown -> bound, event ID="bf:62:82:c5|1592658860"
Jun 22 19:13:12 wiliam-Yoga avahi-daemon[883]: Registering new address record for 2601:4c4:c200:b940::85ea on wlp4s0.*.
Jun 22 19:13:12 wiliam-Yoga nm-dispatcher: req:5 'dhcp6-change' [wlp4s0]: new request (1 scripts)
Jun 22 19:13:12 wiliam-Yoga nm-dispatcher: req:5 'dhcp6-change' [wlp4s0]: start running ordered scripts...
Jun 22 19:13:13 wiliam-Yoga avahi-daemon[883]: Registering new address record for 2601:4c4:c200:b940:d5a:c2d3:2980:1621 on wlp4s0.*.
Jun 22 19:15:09 wiliam-Yoga kernel: [ 4246.705716] [UFW BLOCK] IN=wlp4s0 OUT= MAC=01:00:5e:00:00:01:5c:e3:0e:c2:84:12:08:00 SRC=10.0.0.1 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0xC0 TTL=1 ID=4911 PROTO=2 
Jun 22 19:15:23 wiliam-Yoga gnome-terminal-[1916]: g_menu_insert_item: assertion 'G_IS_MENU_ITEM (item)' failed
Jun 22 19:16:16 wiliam-Yoga gnome-terminal-[1916]: g_menu_insert_item: assertion 'G_IS_MENU_ITEM (item)' failed
Jun 22 19:16:19 wiliam-Yoga zeitgeist-fts[1711]: Unable to get info on application://gnome-terminal-server.desktop
Jun 22 19:17:01 wiliam-Yoga CRON[3889]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Jun 22 19:17:14 wiliam-Yoga kernel: [ 4371.735436] [UFW BLOCK] IN=wlp4s0 OUT= MAC=01:00:5e:00:00:01:5c:e3:0e:c2:84:12:08:00 SRC=10.0.0.1 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0xC0 TTL=1 ID=4912 PROTO=2 
Jun 22 19:19:19 wiliam-Yoga kernel: [ 4496.765239] [UFW BLOCK] IN=wlp4s0 OUT= MAC=01:00:5e:00:00:01:5c:e3:0e:c2:84:12:08:00 SRC=10.0.0.1 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0xC0 TTL=1 ID=4913 PROTO=2 
Jun 22 19:21:24 wiliam-Yoga kernel: [ 4621.692501] [UFW BLOCK] IN=wlp4s0 OUT= MAC=01:00:5e:00:00:01:5c:e3:0e:c2:84:12:08:00 SRC=10.0.0.1 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0xC0 TTL=1 ID=4914 PROTO=2 
Jun 22 19:22:28 wiliam-Yoga wpa_supplicant[904]: wlp4s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-33 noise=9999 txrate=866700
Jun 22 19:23:29 wiliam-Yoga kernel: [ 4746.722215] [UFW BLOCK] IN=wlp4s0 OUT= MAC=01:00:5e:00:00:01:5c:e3:0e:c2:84:12:08:00 SRC=10.0.0.1 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0xC0 TTL=1 ID=4915 PROTO=2 
Jun 22 19:25:34 wiliam-Yoga kernel: [ 4871.751913] [UFW BLOCK] IN=wlp4s0 OUT= MAC=01:00:5e:00:00:01:5c:e3:0e:c2:84:12:08:00 SRC=10.0.0.1 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0xC0 TTL=1 ID=4916 PROTO=2 
Jun 22 19:27:39 wiliam-Yoga kernel: [ 4996.679771] [UFW BLOCK] IN=wlp4s0 OUT= MAC=01:00:5e:00:00:01:5c:e3:0e:c2:84:12:08:00 SRC=10.0.0.1 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0xC0 TTL=1 ID=4917 PROTO=2 
Jun 22 19:29:44 wiliam-Yoga kernel: [ 5121.708363] [UFW BLOCK] IN=wlp4s0 OUT= MAC=01:00:5e:00:00:01:5c:e3:0e:c2:84:12:08:00 SRC=10.0.0.1 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0xC0 TTL=1 ID=4918 PROTO=2 
Jun 22 19:30:09 wiliam-Yoga systemd-timesyncd[777]: Synchronized to time server [2001:67c:1560:8003::c7]:123 (ntp.ubuntu.com).
Jun 22 19:31:50 wiliam-Yoga kernel: [ 5246.635349] [UFW BLOCK] IN=wlp4s0 OUT= MAC=01:00:5e:00:00:01:5c:e3:0e:c2:84:12:08:00 SRC=10.0.0.1 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0xC0 TTL=1 ID=4919 PROTO=2 
Jun 22 19:33:55 wiliam-Yoga kernel: [ 5371.664791] [UFW BLOCK] IN=wlp4s0 OUT= MAC=01:00:5e:00:00:01:5c:e3:0e:c2:84:12:08:00 SRC=10.0.0.1 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0xC0 TTL=1 ID=4920 PROTO=2 
Jun 22 19:36:00 wiliam-Yoga kernel: [ 5496.693812] [UFW BLOCK] IN=wlp4s0 OUT= MAC=01:00:5e:00:00:01:5c:e3:0e:c2:84:12:08:00 SRC=10.0.0.1 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0xC0 TTL=1 ID=4921 PROTO=2 
Jun 22 19:37:21 wiliam-Yoga kernel: [ 5577.538493] wacom 0003:056A:5093.0005: wacom_wac_queue_insert: kfifo has filled, starting to drop events
Jun 22 19:37:21 wiliam-Yoga kernel: [ 5577.543492] wacom 0003:056A:5093.0005: wacom_wac_queue_insert: kfifo has filled, starting to drop events
Jun 22 19:37:59 wiliam-Yoga kernel: [ 5615.487052] wacom 0003:056A:5093.0005: wacom_wac_queue_insert: kfifo has filled, starting to drop events
Jun 22 19:37:59 wiliam-Yoga kernel: [ 5615.496945] wacom 0003:056A:5093.0005: wacom_wac_queue_insert: kfifo has filled, starting to drop events
Jun 22 19:37:59 wiliam-Yoga kernel: [ 5615.501445] wacom 0003:056A:5093.0005: wacom_wac_queue_insert: kfifo has filled, starting to drop events
Jun 22 19:37:59 wiliam-Yoga kernel: [ 5615.506505] wacom 0003:056A:5093.0005: wacom_wac_queue_insert: kfifo has filled, starting to drop events
Jun 22 19:37:59 wiliam-Yoga kernel: [ 5615.516435] wacom 0003:056A:5093.0005: wacom_wac_queue_insert: kfifo has filled, starting to drop events
Jun 22 19:37:59 wiliam-Yoga kernel: [ 5615.521510] wacom 0003:056A:5093.0005: wacom_wac_queue_insert: kfifo has filled, starting to drop events
Jun 22 19:37:59 wiliam-Yoga kernel: [ 5615.531506] wacom 0003:056A:5093.0005: wacom_wac_queue_insert: kfifo has filled, starting to drop events
Jun 22 19:37:59 wiliam-Yoga kernel: [ 5615.536505] wacom 0003:056A:5093.0005: wacom_wac_queue_insert: kfifo has filled, starting to drop events
Jun 22 19:37:59 wiliam-Yoga kernel: [ 5615.548444] wacom 0003:056A:5093.0005: wacom_wac_queue_insert: kfifo has filled, starting to drop events
Jun 22 19:37:59 wiliam-Yoga kernel: [ 5615.551504] wacom 0003:056A:5093.0005: wacom_wac_queue_insert: kfifo has filled, starting to drop events
Jun 22 19:37:59 wiliam-Yoga kernel: [ 5615.561503] wacom 0003:056A:5093.0005: wacom_wac_queue_insert: kfifo has filled, starting to drop events
Jun 22 19:37:59 wiliam-Yoga kernel: [ 5615.566508] wacom 0003:056A:5093.0005: wacom_wac_queue_insert: kfifo has filled, starting to drop events
Jun 22 19:37:59 wiliam-Yoga kernel: [ 5615.576428] wacom 0003:056A:5093.0005: wacom_wac_queue_insert: kfifo has filled, starting to drop events
Jun 22 19:37:59 wiliam-Yoga kernel: [ 5615.581507] wacom 0003:056A:5093.0005: wacom_wac_queue_insert: kfifo has filled, starting to drop events
Jun 22 19:37:59 wiliam-Yoga kernel: [ 5615.591499] wacom 0003:056A:5093.0005: wacom_wac_queue_insert: kfifo has filled, starting to drop events
Jun 22 19:37:59 wiliam-Yoga kernel: [ 5615.596504] wacom 0003:056A:5093.0005: wacom_wac_queue_insert: kfifo has filled, starting to drop events
Jun 22 19:38:05 wiliam-Yoga kernel: [ 5621.621426] [UFW BLOCK] IN=wlp4s0 OUT= MAC=01:00:5e:00:00:01:5c:e3:0e:c2:84:12:08:00 SRC=10.0.0.1 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0xC0 TTL=1 ID=4922 PROTO=2 
Jun 22 19:38:14 wiliam-Yoga kernel: [ 5631.225512] wacom 0003:056A:5093.0005: wacom_wac_queue_insert: kfifo has filled, starting to drop events
Jun 22 19:38:14 wiliam-Yoga kernel: [ 5631.235513] wacom 0003:056A:5093.0005: wacom_wac_queue_insert: kfifo has filled, starting to drop events
Jun 22 19:38:14 wiliam-Yoga kernel: [ 5631.240537] wacom 0003:056A:5093.0005: wacom_wac_queue_insert: kfifo has filled, starting to drop events
Jun 22 19:38:14 wiliam-Yoga kernel: [ 5631.252447] wacom 0003:056A:5093.0005: wacom_wac_queue_insert: kfifo has filled, starting to drop events
Jun 22 19:38:14 wiliam-Yoga kernel: [ 5631.255461] wacom 0003:056A:5093.0005: wacom_wac_queue_insert: kfifo has filled, starting to drop events
Jun 22 19:38:14 wiliam-Yoga kernel: [ 5631.265519] wacom 0003:056A:5093.0005: wacom_wac_queue_insert: kfifo has filled, starting to drop events
Jun 22 19:38:15 wiliam-Yoga kernel: [ 5631.270459] wacom 0003:056A:5093.0005: wacom_wac_queue_insert: kfifo has filled, starting to drop events
Jun 22 19:38:15 wiliam-Yoga kernel: [ 5631.280528] wacom 0003:056A:5093.0005: wacom_wac_queue_insert: kfifo has filled, starting to drop events
Jun 22 19:38:15 wiliam-Yoga kernel: [ 5631.285454] wacom 0003:056A:5093.0005: wacom_wac_queue_insert: kfifo has filled, starting to drop events
Jun 22 19:38:15 wiliam-Yoga kernel: [ 5631.295519] wacom 0003:056A:5093.0005: wacom_wac_queue_insert: kfifo has filled, starting to drop events
Jun 22 19:38:15 wiliam-Yoga kernel: [ 5631.300515] wacom 0003:056A:5093.0005: wacom_wac_queue_insert: kfifo has filled, starting to drop events
Jun 22 19:38:15 wiliam-Yoga kernel: [ 5631.310517] wacom 0003:056A:5093.0005: wacom_wac_queue_insert: kfifo has filled, starting to drop events
Jun 22 19:38:15 wiliam-Yoga kernel: [ 5631.315494] wacom 0003:056A:5093.0005: wacom_wac_queue_insert: kfifo has filled, starting to drop events
Jun 22 19:38:15 wiliam-Yoga kernel: [ 5631.325445] wacom 0003:056A:5093.0005: wacom_wac_queue_insert: kfifo has filled, starting to drop events
Jun 22 19:38:15 wiliam-Yoga kernel: [ 5631.330515] wacom 0003:056A:5093.0005: wacom_wac_queue_insert: kfifo has filled, starting to drop events
Jun 22 19:38:15 wiliam-Yoga kernel: [ 5631.350545] wacom 0003:056A:5093.0005: wacom_wac_queue_insert: kfifo has filled, starting to drop events
Jun 22 19:38:15 wiliam-Yoga kernel: [ 5631.355453] wacom 0003:056A:5093.0005: wacom_wac_queue_insert: kfifo has filled, starting to drop events
Jun 22 19:39:51 wiliam-Yoga gnome-terminal-[1916]: g_menu_insert_item: assertion 'G_IS_MENU_ITEM (item)' failed
Jun 22 19:39:53 wiliam-Yoga zeitgeist-fts[1711]: Unable to get info on application://gnome-terminal-server.desktop
Jun 22 19:40:10 wiliam-Yoga kernel: [ 5746.649457] [UFW BLOCK] IN=wlp4s0 OUT= MAC=01:00:5e:00:00:01:5c:e3:0e:c2:84:12:08:00 SRC=10.0.0.1 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0xC0 TTL=1 ID=4923 PROTO=2 
Jun 22 19:42:15 wiliam-Yoga kernel: [ 5871.575966] [UFW BLOCK] IN=wlp4s0 OUT= MAC=01:00:5e:00:00:01:5c:e3:0e:c2:84:12:08:00 SRC=10.0.0.1 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0xC0 TTL=1 ID=4924 PROTO=2 
Jun 22 19:44:20 wiliam-Yoga kernel: [ 5996.605155] [UFW BLOCK] IN=wlp4s0 OUT= MAC=01:00:5e:00:00:01:5c:e3:0e:c2:84:12:08:00 SRC=10.0.0.1 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0xC0 TTL=1 ID=4925 PROTO=2 
Jun 22 19:45:57 wiliam-Yoga kernel: [ 6093.773116] wacom 0003:056A:5093.0005: wacom_wac_queue_insert: kfifo has filled, starting to drop events
Jun 22 19:45:57 wiliam-Yoga kernel: [ 6093.777833] wacom 0003:056A:5093.0005: wacom_wac_queue_insert: kfifo has filled, starting to drop events
Jun 22 19:45:57 wiliam-Yoga kernel: [ 6093.787678] wacom 0003:056A:5093.0005: wacom_wac_queue_insert: kfifo has filled, starting to drop events
Jun 22 19:45:57 wiliam-Yoga kernel: [ 6093.792605] wacom 0003:056A:5093.0005: wacom_wac_queue_insert: kfifo has filled, starting to drop events
Jun 22 19:45:57 wiliam-Yoga kernel: [ 6093.804604] wacom 0003:056A:5093.0005: wacom_wac_queue_insert: kfifo has filled, starting to drop events
Jun 22 19:45:57 wiliam-Yoga kernel: [ 6093.807671] wacom 0003:056A:5093.0005: wacom_wac_queue_insert: kfifo has filled, starting to drop events
Jun 22 19:45:57 wiliam-Yoga kernel: [ 6093.817668] wacom 0003:056A:5093.0005: wacom_wac_queue_insert: kfifo has filled, starting to drop events
Jun 22 19:45:57 wiliam-Yoga kernel: [ 6093.822685] wacom 0003:056A:5093.0005: wacom_wac_queue_insert: kfifo has filled, starting to drop events
Jun 22 19:45:57 wiliam-Yoga kernel: [ 6093.832636] wacom 0003:056A:5093.0005: wacom_wac_queue_insert: kfifo has filled, starting to drop events
Jun 22 19:45:57 wiliam-Yoga kernel: [ 6093.837635] wacom 0003:056A:5093.0005: wacom_wac_queue_insert: kfifo has filled, starting to drop events
Jun 22 19:45:57 wiliam-Yoga kernel: [ 6093.858680] wacom 0003:056A:5093.0005: wacom_wac_queue_insert: kfifo has filled, starting to drop events
Jun 22 19:45:57 wiliam-Yoga kernel: [ 6093.862676] wacom 0003:056A:5093.0005: wacom_wac_queue_insert: kfifo has filled, starting to drop events
Jun 22 19:45:57 wiliam-Yoga kernel: [ 6093.866677] wacom 0003:056A:5093.0005: wacom_wac_queue_insert: kfifo has filled, starting to drop events
Jun 22 19:45:57 wiliam-Yoga kernel: [ 6093.877676] wacom 0003:056A:5093.0005: wacom_wac_queue_insert: kfifo has filled, starting to drop events
Jun 22 19:45:57 wiliam-Yoga kernel: [ 6093.881678] wacom 0003:056A:5093.0005: wacom_wac_queue_insert: kfifo has filled, starting to drop events
Jun 22 19:45:57 wiliam-Yoga kernel: [ 6093.891687] wacom 0003:056A:5093.0005: wacom_wac_queue_insert: kfifo has filled, starting to drop events
Jun 22 19:45:57 wiliam-Yoga kernel: [ 6093.896644] wacom 0003:056A:5093.0005: wacom_wac_queue_insert: kfifo has filled, starting to drop events
Jun 22 19:45:57 wiliam-Yoga kernel: [ 6093.906677] wacom 0003:056A:5093.0005: wacom_wac_queue_insert: kfifo has filled, starting to drop events
Jun 22 19:45:57 wiliam-Yoga kernel: [ 6093.911678] wacom 0003:056A:5093.0005: wacom_wac_queue_insert: kfifo has filled, starting to drop events
Jun 22 19:45:57 wiliam-Yoga kernel: [ 6093.921676] wacom 0003:056A:5093.0005: wacom_wac_queue_insert: kfifo has filled, starting to drop events
Jun 22 19:45:57 wiliam-Yoga kernel: [ 6093.926676] wacom 0003:056A:5093.0005: wacom_wac_queue_insert: kfifo has filled, starting to drop events
Jun 22 19:45:57 wiliam-Yoga kernel: [ 6093.938601] wacom 0003:056A:5093.0005: wacom_wac_queue_insert: kfifo has filled, starting to drop events
Jun 22 19:45:57 wiliam-Yoga kernel: [ 6093.941681] wacom 0003:056A:5093.0005: wacom_wac_queue_insert: kfifo has filled, starting to drop events
Jun 22 19:45:57 wiliam-Yoga kernel: [ 6093.951676] wacom 0003:056A:5093.0005: wacom_wac_queue_insert: kfifo has filled, starting to drop events
Jun 22 19:46:25 wiliam-Yoga kernel: [ 6121.634414] [UFW BLOCK] IN=wlp4s0 OUT= MAC=01:00:5e:00:00:01:5c:e3:0e:c2:84:12:08:00 SRC=10.0.0.1 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0xC0 TTL=1 ID=4926 PROTO=2 
Jun 22 19:48:30 wiliam-Yoga kernel: [ 6246.561587] [UFW BLOCK] IN=wlp4s0 OUT= MAC=01:00:5e:00:00:01:5c:e3:0e:c2:84:12:08:00 SRC=10.0.0.1 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0xC0 TTL=1 ID=4927 PROTO=2 
Jun 22 19:50:35 wiliam-Yoga kernel: [ 6371.590991] [UFW BLOCK] IN=wlp4s0 OUT= MAC=01:00:5e:00:00:01:5c:e3:0e:c2:84:12:08:00 SRC=10.0.0.1 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0xC0 TTL=1 ID=4928 PROTO=2 
Jun 22 19:52:40 wiliam-Yoga kernel: [ 6496.619140] [UFW BLOCK] IN=wlp4s0 OUT= MAC=01:00:5e:00:00:01:5c:e3:0e:c2:84:12:08:00 SRC=10.0.0.1 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0xC0 TTL=1 ID=4929 PROTO=2 
Jun 22 19:53:24 wiliam-Yoga gnome-terminal-[1916]: g_menu_insert_item: assertion 'G_IS_MENU_ITEM (item)' failed
Jun 22 19:53:31 wiliam-Yoga zeitgeist-fts[1711]: Unable to get info on application://gnome-terminal-server.desktop
Jun 22 19:54:45 wiliam-Yoga kernel: [ 6621.545817] [UFW BLOCK] IN=wlp4s0 OUT= MAC=01:00:5e:00:00:01:5c:e3:0e:c2:84:12:08:00 SRC=10.0.0.1 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0xC0 TTL=1 ID=4930 PROTO=2 
I'm not sure exactly what we are looking for but, I do note that there are lots of lines pertaining to the kernel though not always exact repeats. If I open the syslog file in Nemo, I see lots more lines pertaining to the kernel and many are almost exact dupicates. Don't know if that is significant.

User avatar
LanceM
Level 9
Level 9
Posts: 2665
Joined: Sun Jul 08, 2018 11:50 pm

Re: Full Disk Warning

Post by LanceM »

My log files are growing still. Both kern.log and syslog files have grown to about 20GB each
Do you mean 20MB?
If 20MB don't worry. Only if it gets over 400MB
To mark this issue solved, go to your original 1st post and click the edit pencil and add [Solved] at the beginning of the title and click Submit.
Mint accepts donations: https://linuxmint.com/donors.php

YoMan
Level 3
Level 3
Posts: 109
Joined: Sat Dec 03, 2016 12:38 pm

Re: Full Disk Warning

Post by YoMan »

No. I mean 20 GB. However, since i posted, the system has created a new syslog file and the old 20GB one is named syslog.1. I assume that is the result of running clean-log or did it simply reach a max size? I also assume that I can delete syslog.1.

Code: Select all

sudo du -h /var/log
doesn't appear to include those two files for some reason. See following:

Code: Select all

bill@wiliam-Yoga:~$ sudo du -h /var/log/syslog
96K	/var/log/syslog
bill@wiliam-Yoga:~$ sudo du -h /var/log/syslog.1
20G	/var/log/syslog.1

User avatar
LanceM
Level 9
Level 9
Posts: 2665
Joined: Sun Jul 08, 2018 11:50 pm

Re: Full Disk Warning

Post by LanceM »

Yes you can delete syslog.1
Right click folder /log and highlight syslog.1 then right click it and choose delete.
Man, no wonder you were running out of space!
Before deleting it, right click it, choose Properties and verify it really is 20GB. Worse case of bloat I've ever imagined. Glad you caught it.
To mark this issue solved, go to your original 1st post and click the edit pencil and add [Solved] at the beginning of the title and click Submit.
Mint accepts donations: https://linuxmint.com/donors.php

User avatar
smurphos
Level 16
Level 16
Posts: 6859
Joined: Fri Sep 05, 2014 12:18 am
Location: Britisher
Contact:

Re: Full Disk Warning

Post by smurphos »

You can turn off UFW logging which will eliminate one source of log spam.

Code: Select all

sudo ufw logging off
There's a lot of these -

Code: Select all

wacom 0003:056A:5093.0005: wacom_wac_queue_insert: kfifo has filled, starting to drop events
Unfortunately other than it's related to your graphics tablet I can't really find any info via an internet search for the generic part of the string that talks about troubleshooting repeated instances of this message. I assume you do have a graphics tablet? Is it working OK?
For custom Nemo actions, useful scripts for the Cinnamon desktop, and Cinnamox themes visit my Github pages.

YoMan
Level 3
Level 3
Posts: 109
Joined: Sat Dec 03, 2016 12:38 pm

Re: Full Disk Warning

Post by YoMan »

Yes. Syslog.1 was 20 GB plus as was kern.log. Now deleted, both the Disk Usage Analyser and Gparted show / is a very happy 18GB and /var is down to about 2GB.
What does ufw logging do?
Yes. My computer does have a graphics tablet mode. It is the Thinkpad X1 Yoga with a screen that rotates a full 360 deg to become a tablet. It has a stylus that slips into a slot in the side for storage and charging. Very nifty. In computer mode, I frequently use it rather than my finger for pointing or scrolling as it is a bit more precise.
For the future, was it the running of clean-logs.sh that caused syslog to start over?
Is there any word yet about when the new version of Mint will be ready?

Post Reply

Return to “Installation & Boot”