Unexpected Shutdowns

All Gurus once were Newbies
Forum rules
There are no such things as "stupid" questions. However if you think your question is a bit stupid, then this is the right place for you to post it. Please stick to easy to-the-point questions that you feel people can answer fast. For long and complicated questions prefer the other forums within the support section.
Before you post please read how to get help
antikythera
Level 6
Level 6
Posts: 1470
Joined: Thu Jul 02, 2020 12:52 pm
Contact:

Re: Unexpected Shutdowns

Post by antikythera »

Don't take life so seriously, nobody gets out alive anyway!
AMSTRAD CPC6128 - 128KB RAM, 3" Hitachi Floppy Diskette Drive, External Sony Cassette Recorder, Locomotive BASIC 1.1, CTM-644 Monitor
omg_me
Level 1
Level 1
Posts: 21
Joined: Thu Aug 27, 2020 9:16 pm

Re: Unexpected Shutdowns

Post by omg_me »

antikythera wrote:
Wed Sep 16, 2020 3:15 pm
Workaround (DuckDuckGo...):

https://bugs.launchpad.net/ubuntu/+sour ... ug/1521173
I've updated the GRUB_CMDLINE_LINUX_DEFAULT accordingly just now.

But from my point of view, this error should not cause the shutdowns, do you agree?
User avatar
SMG
Level 5
Level 5
Posts: 774
Joined: Sun Jul 26, 2020 6:15 pm
Location: USA

Re: Unexpected Shutdowns

Post by SMG »

omg_me wrote:
Wed Sep 16, 2020 3:41 pm
antikythera wrote:
Wed Sep 16, 2020 3:15 pm
Workaround (DuckDuckGo...):

https://bugs.launchpad.net/ubuntu/+sour ... ug/1521173
I've updated the GRUB_CMDLINE_LINUX_DEFAULT accordingly just now.

But from my point of view, this error should not cause the shutdowns, do you agree?
The research I was doing was bringing me to the same point as antikythera. It seems most people seeing those messages are having problems booting. You say this is the latest message before your system shuts down, but I'm wondering if your computer has already shutdown and is trying to reboot. Thus, whatever is causing the shutdown is upstream of the message you posted? Even if the grub change you made does not stop the shutdowns, it may clear the message queues enough that what is causing them will be more easily seen. That's my theory. :)
LM20.0 Cinnamon
1000
Level 3
Level 3
Posts: 127
Joined: Wed Jul 29, 2020 2:14 am

Re: Unexpected Shutdowns

Post by 1000 »

I have noticed most of the reboots is after segfault ( program memory error )
You can check log fast this way.

Code: Select all

journalctl  | grep "segfault"
https://askubuntu.com/questions/1104219 ... nomsi-mean
- Turning off bug reporting is not a very good idea.

https://bugs.launchpad.net/ubuntu/+sour ... omments/32
- If option will work

Code: Select all

pcie_aspm=off
Check if about https://en.wikipedia.org/wiki/Active_St ... Management
is something in Bios.

https://forums.lenovo.com/t5/ThinkCentr ... -p/3505516
- I suggest also ask Lenovo support for help.
omg_me
Level 1
Level 1
Posts: 21
Joined: Thu Aug 27, 2020 9:16 pm

Re: Unexpected Shutdowns

Post by omg_me »

SMG wrote:
Wed Sep 16, 2020 4:44 pm
omg_me wrote:
Wed Sep 16, 2020 3:41 pm
antikythera wrote:
Wed Sep 16, 2020 3:15 pm
Workaround (DuckDuckGo...):

https://bugs.launchpad.net/ubuntu/+sour ... ug/1521173
I've updated the GRUB_CMDLINE_LINUX_DEFAULT accordingly just now.

But from my point of view, this error should not cause the shutdowns, do you agree?
The research I was doing was bringing me to the same point as antikythera. It seems most people seeing those messages are having problems booting. You say this is the latest message before your system shuts down, but I'm wondering if your computer has already shutdown and is trying to reboot. Thus, whatever is causing the shutdown is upstream of the message you posted? Even if the grub change you made does not stop the shutdowns, it may clear the message queues enough that what is causing them will be more easily seen. That's my theory. :)
Completely agree.
Here is the log from the latest shutdown:

Code: Select all

Sep 17 12:05:01 gam0r-PC CRON[5166]: (grubi) CMD (date >> /home/grubi/Documents/Shutdown_investigation/sensors.log && sensors >> /home/grubi/Documents/Shutdown_investigation/sensors.log)
Sep 17 12:05:36 gam0r-PC wpa_supplicant[850]: wlp2s0: WPA: Group rekeying completed with 7c:ff:4d:3d:ee:0f [GTK=CCMP]
Sep 17 12:06:01 gam0r-PC CRON[5182]: (grubi) CMD (date >> /home/grubi/Documents/Shutdown_investigation/sensors.log && sensors >> /home/grubi/Documents/Shutdown_investigation/sensors.log)
Sep 17 12:07:01 gam0r-PC CRON[5193]: (grubi) CMD (date >> /home/grubi/Documents/Shutdown_investigation/sensors.log && sensors >> /home/grubi/Documents/Shutdown_investigation/sensors.log)
Sep 17 12:08:01 gam0r-PC CRON[5212]: (grubi) CMD (date >> /home/grubi/Documents/Shutdown_investigation/sensors.log && sensors >> /home/grubi/Documents/Shutdown_investigation/sensors.log)
Sep 17 12:09:01 gam0r-PC CRON[5224]: (grubi) CMD (date >> /home/grubi/Documents/Shutdown_investigation/sensors.log && sensors >> /home/grubi/Documents/Shutdown_investigation/sensors.log)
Sep 17 12:10:01 gam0r-PC CRON[5237]: (grubi) CMD (date >> /home/grubi/Documents/Shutdown_investigation/sensors.log && sensors >> /home/grubi/Documents/Shutdown_investigation/sensors.log)
Sep 17 12:11:01 gam0r-PC CRON[5251]: (grubi) CMD (date >> /home/grubi/Documents/Shutdown_investigation/sensors.log && sensors >> /home/grubi/Documents/Shutdown_investigation/sensors.log)
Sep 17 12:12:01 gam0r-PC CRON[5264]: (grubi) CMD (date >> /home/grubi/Documents/Shutdown_investigation/sensors.log && sensors >> /home/grubi/Documents/Shutdown_investigation/sensors.log)
Sep 17 12:13:01 gam0r-PC CRON[5285]: (grubi) CMD (date >> /home/grubi/Documents/Shutdown_investigation/sensors.log && sensors >> /home/grubi/Documents/Shutdown_investigation/sensors.log)
Sep 17 12:14:01 gam0r-PC CRON[5301]: (grubi) CMD (date >> /home/grubi/Documents/Shutdown_investigation/sensors.log && sensors >> /home/grubi/Documents/Shutdown_investigation/sensors.log)
Sep 17 12:15:01 gam0r-PC CRON[5320]: (grubi) CMD (date >> /home/grubi/Documents/Shutdown_investigation/sensors.log && sensors >> /home/grubi/Documents/Shutdown_investigation/sensors.log)
Sep 17 12:15:36 gam0r-PC wpa_supplicant[850]: wlp2s0: WPA: Group rekeying completed with 7c:ff:4d:3d:ee:0f [GTK=CCMP]
Sep 17 12:16:01 gam0r-PC CRON[5343]: (grubi) CMD (date >> /home/grubi/Documents/Shutdown_investigation/sensors.log && sensors >> /home/grubi/Documents/Shutdown_investigation/sensors.log)
Sep 17 12:17:01 gam0r-PC CRON[5364]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Sep 17 12:17:01 gam0r-PC CRON[5365]: (grubi) CMD (date >> /home/grubi/Documents/Shutdown_investigation/sensors.log && sensors >> /home/grubi/Documents/Shutdown_investigation/sensors.log)
Sep 17 12:17:40 gam0r-PC rtkit-daemon[1059]: Supervising 5 threads of 3 processes of 1 users.
Sep 17 12:17:40 gam0r-PC rtkit-daemon[1059]: Successfully made thread 5384 of process 1237 owned by '1000' RT at priority 5.
Sep 17 12:17:40 gam0r-PC rtkit-daemon[1059]: Supervising 6 threads of 3 processes of 1 users.
Sep 17 12:17:40 gam0r-PC rtkit-daemon[1059]: Supervising 5 threads of 3 processes of 1 users.
Sep 17 12:17:40 gam0r-PC rtkit-daemon[1059]: Successfully made thread 5385 of process 1237 owned by '1000' RT at priority 5.
Sep 17 12:17:40 gam0r-PC rtkit-daemon[1059]: Supervising 6 threads of 3 processes of 1 users.
Sep 17 12:18:01 gam0r-PC CRON[5389]: (grubi) CMD (date >> /home/grubi/Documents/Shutdown_investigation/sensors.log && sensors >> /home/grubi/Documents/Shutdown_investigation/sensors.log)
Sep 17 12:19:01 gam0r-PC CRON[5408]: (grubi) CMD (date >> /home/grubi/Documents/Shutdown_investigation/sensors.log && sensors >> /home/grubi/Documents/Shutdown_investigation/sensors.log)
Sep 17 12:20:01 gam0r-PC CRON[5426]: (grubi) CMD (date >> /home/grubi/Documents/Shutdown_investigation/sensors.log && sensors >> /home/grubi/Documents/Shutdown_investigation/sensors.log)
Sep 17 12:21:01 gam0r-PC CRON[5447]: (grubi) CMD (date >> /home/grubi/Documents/Shutdown_investigation/sensors.log && sensors >> /home/grubi/Documents/Shutdown_investigation/sensors.log)
Sep 17 13:51:49 gam0r-PC systemd-modules-load[524]: Inserted module 'lp'
Now it's just my cron cluttering the log. But I don't see anything obvious. Should i go back further?
1000 wrote:
Thu Sep 17, 2020 2:38 am
I have noticed most of the reboots is after segfault ( program memory error )
You can check log fast this way.

Code: Select all

journalctl  | grep "segfault"
https://askubuntu.com/questions/1104219 ... nomsi-mean
- Turning off bug reporting is not a very good idea.

https://bugs.launchpad.net/ubuntu/+sour ... omments/32
- If option will work

Code: Select all

pcie_aspm=off
Check if about https://en.wikipedia.org/wiki/Active_St ... Management
is something in Bios.

https://forums.lenovo.com/t5/ThinkCentr ... -p/3505516
- I suggest also ask Lenovo support for help.

Code: Select all

journalctl  | grep "segfault"

Sep 12 18:52:29 gam0r-PC kernel: csd-automount[1363]: segfault at 8 ip 000055f73ad5d430 sp 00007ffeb6c51120 error 4 in csd-automount[55f73ad5b000+5000]
Sep 12 19:48:03 gam0r-PC kernel: csd-automount[1342]: segfault at 8 ip 000055b0b755f430 sp 00007ffe24d2f460 error 4 in csd-automount[55b0b755d000+5000]
Not much there.

Turning off bug reporting is not a good idea, i see it only as a temporary solution to find the root of the problem (unless it is really the problem causing the shutdowns).

I wrote Lenovo another message, let's see if they know more.
User avatar
SMG
Level 5
Level 5
Posts: 774
Joined: Sun Jul 26, 2020 6:15 pm
Location: USA

Re: Unexpected Shutdowns

Post by SMG »

omg_me wrote:
Thu Sep 17, 2020 8:27 am
Here is the log from the latest shutdown:
...
Now it's just my cron cluttering the log. But I don't see anything obvious. Should i go back further?
Presuming the temp sensors aren't showing anything, I would think it must be further upstream. Those listed seem like they are still part of the reboot process.
omg_me wrote:
Thu Sep 17, 2020 8:27 am

Code: Select all

journalctl  | grep "segfault"

Sep 12 18:52:29 gam0r-PC kernel: csd-automount[1363]: segfault at 8 ip 000055f73ad5d430 sp 00007ffeb6c51120 error 4 in csd-automount[55f73ad5b000+5000]
Sep 12 19:48:03 gam0r-PC kernel: csd-automount[1342]: segfault at 8 ip 000055b0b755f430 sp 00007ffe24d2f460 error 4 in csd-automount[55b0b755d000+5000]
These segfaults are something I get on a regular, but not deliberately reproduce-able basis. They have already been reported 1304 (csd-automount) #291.
LM20.0 Cinnamon
omg_me
Level 1
Level 1
Posts: 21
Joined: Thu Aug 27, 2020 9:16 pm

Re: Unexpected Shutdowns

Post by omg_me »

The last sensors output looks all right:

Code: Select all

Thu 17 Sep 2020 12:21:01 PM CEST
coretemp-isa-0000
Adapter: ISA adapter
Package id 0:  +37.0°C  (high = +100.0°C, crit = +100.0°C)
Core 0:        +36.0°C  (high = +100.0°C, crit = +100.0°C)
Core 1:        +36.0°C  (high = +100.0°C, crit = +100.0°C)
Core 2:        +36.0°C  (high = +100.0°C, crit = +100.0°C)
Core 3:        +37.0°C  (high = +100.0°C, crit = +100.0°C)

BAT0-acpi-0
Adapter: ACPI interface
in0:           8.41 V  

iwlwifi_1-virtual-0
Adapter: Virtual device
temp1:        +32.0°C  

pch_skylake-virtual-0
Adapter: Virtual device
temp1:        +35.0°C  

acpitz-acpi-0
Adapter: ACPI interface
temp1:        +38.0°C  (crit = +98.0°C)
temp2:        +35.0°C  (crit = +126.0°C)
The highest up to one hour before was this:

Code: Select all

Thu 17 Sep 2020 11:46:01 AM CEST
coretemp-isa-0000
Adapter: ISA adapter
Package id 0:  +55.0°C  (high = +100.0°C, crit = +100.0°C)
Core 0:        +53.0°C  (high = +100.0°C, crit = +100.0°C)
Core 1:        +52.0°C  (high = +100.0°C, crit = +100.0°C)
Core 2:        +54.0°C  (high = +100.0°C, crit = +100.0°C)
Core 3:        +56.0°C  (high = +100.0°C, crit = +100.0°C)

BAT0-acpi-0
Adapter: ACPI interface
in0:           8.41 V  

iwlwifi_1-virtual-0
Adapter: Virtual device
temp1:        +35.0°C  

pch_skylake-virtual-0
Adapter: Virtual device
temp1:        +42.0°C  

acpitz-acpi-0
Adapter: ACPI interface
temp1:        +51.0°C  (crit = +98.0°C)
temp2:        +38.0°C  (crit = +126.0°C)
Some more logs

Code: Select all

Sep 17 11:35:48 gam0r-PC rsyslogd: [origin software="rsyslogd" swVersion="8.2001.0" x-pid="836" x-info="https://www.rsyslog.com"] rsyslogd was HUPed
Sep 17 11:35:48 gam0r-PC systemd[1]: Started Modem Manager.
Sep 17 11:35:48 gam0r-PC acpid: starting up with netlink and the input layer
Sep 17 11:35:48 gam0r-PC dbus-daemon[809]: [system] Successfully activated service 'org.freedesktop.hostname1'
Sep 17 11:35:48 gam0r-PC systemd[1]: Started Hostname Service.
Sep 17 11:35:48 gam0r-PC systemd[1]: Condition check resulted in Manage Sound Card State (restore and store) being skipped.
Sep 17 11:35:48 gam0r-PC systemd[1]: Starting Save/Restore Sound Card State...
Sep 17 11:35:48 gam0r-PC networkd-dispatcher[966]: WARNING: systemd-networkd is not running, output will be incomplete.
Sep 17 11:35:48 gam0r-PC NetworkManager[811]: <info>  [1600335348.4745] hostname: hostname: using hostnamed
Sep 17 11:35:48 gam0r-PC NetworkManager[811]: <info>  [1600335348.4745] hostname: hostname changed from (none) to "gam0r-PC"
Sep 17 11:35:48 gam0r-PC NetworkManager[811]: <info>  [1600335348.4748] dns-mgr[0x5603762ec290]: init: dns=systemd-resolved rc-manager=symlink, plugin=systemd-resolved
Sep 17 11:35:48 gam0r-PC NetworkManager[811]: <info>  [1600335348.4763] rfkill3: found Wi-Fi radio killswitch (at /sys/devices/pci0000:00/0000:00:1c.4/0000:02:00.0/ieee80211/phy0/rfkill3) (driver iwlwifi)
Sep 17 11:35:48 gam0r-PC NetworkManager[811]: <info>  [1600335348.4766] rfkill0: found Wi-Fi radio killswitch (at /sys/devices/pci0000:00/0000:00:1f.0/PNP0C09:00/VPC2004:00/rfkill/rfkill0) (platform driver ideapad_acpi)
Sep 17 11:35:48 gam0r-PC systemd[1]: Started Dispatcher daemon for systemd-networkd.
Sep 17 11:35:48 gam0r-PC NetworkManager[811]: <info>  [1600335348.4778] manager[0x5603762fe030]: rfkill: Wi-Fi hardware radio set enabled
Sep 17 11:35:48 gam0r-PC NetworkManager[811]: <info>  [1600335348.4779] manager[0x5603762fe030]: rfkill: WWAN hardware radio set enabled
Sep 17 11:35:48 gam0r-PC dbus-daemon[809]: [system] Successfully activated service 'org.freedesktop.login1'
Sep 17 11:35:48 gam0r-PC systemd[1]: Started Login Service.
Sep 17 11:35:48 gam0r-PC acpid: 8 rules loaded
Sep 17 11:35:48 gam0r-PC acpid: waiting for events: event logging is off
Sep 17 11:35:48 gam0r-PC systemd[1]: Received SIGRTMIN+21 from PID 283 (plymouthd).
Sep 17 11:35:48 gam0r-PC systemd[1]: plymouth-quit-wait.service: Succeeded.
Sep 17 11:35:48 gam0r-PC systemd[1]: Finished Hold until boot process finishes up.
Sep 17 11:35:48 gam0r-PC systemd[1]: Received SIGRTMIN+21 from PID 283 (plymouthd).
Sep 17 11:35:48 gam0r-PC systemd[1]: Starting Set console scheme...
Sep 17 11:35:48 gam0r-PC systemd[1]: Started Light Display Manager.
Sep 17 11:35:48 gam0r-PC systemd[1]: Finished Set console scheme.
Sep 17 11:35:48 gam0r-PC systemd[1]: Created slice system-getty.slice.
Sep 17 11:35:48 gam0r-PC systemd[1]: Started Getty on tty1.
Sep 17 11:35:48 gam0r-PC systemd[1]: Reached target Login Prompts.
Sep 17 11:35:48 gam0r-PC systemd[1]: Reached target Multi-User System.
Sep 17 11:35:48 gam0r-PC NetworkManager[811]: <info>  [1600335348.5695] Loaded device plugin: NMBluezManager (/usr/lib/x86_64-linux-gnu/NetworkManager/1.22.10/libnm-device-plugin-bluetooth.so)
Sep 17 11:35:48 gam0r-PC systemd-udevd[566]: Using default interface naming scheme 'v245'.
Sep 17 11:35:48 gam0r-PC NetworkManager[811]: <info>  [1600335348.5794] Loaded device plugin: NMWwanFactory (/usr/lib/x86_64-linux-gnu/NetworkManager/1.22.10/libnm-device-plugin-wwan.so)
Sep 17 11:35:48 gam0r-PC NetworkManager[811]: <info>  [1600335348.6030] Loaded device plugin: NMTeamFactory (/usr/lib/x86_64-linux-gnu/NetworkManager/1.22.10/libnm-device-plugin-team.so)
Sep 17 11:35:48 gam0r-PC systemd[1]: logrotate.service: Succeeded.
Sep 17 11:35:48 gam0r-PC systemd[1]: Finished Rotate log files.
Sep 17 11:35:48 gam0r-PC NetworkManager[811]: <info>  [1600335348.6050] Loaded device plugin: NMWifiFactory (/usr/lib/x86_64-linux-gnu/NetworkManager/1.22.10/libnm-device-plugin-wifi.so)
Sep 17 11:35:48 gam0r-PC NetworkManager[811]: <info>  [1600335348.6112] Loaded device plugin: NMAtmManager (/usr/lib/x86_64-linux-gnu/NetworkManager/1.22.10/libnm-device-plugin-adsl.so)
Sep 17 11:35:48 gam0r-PC NetworkManager[811]: <info>  [1600335348.6115] manager: rfkill: Wi-Fi enabled by radio killswitch; enabled by state file
Sep 17 11:35:48 gam0r-PC NetworkManager[811]: <info>  [1600335348.6116] manager: rfkill: WWAN enabled by radio killswitch; enabled by state file
Sep 17 11:35:48 gam0r-PC NetworkManager[811]: <info>  [1600335348.6117] manager: Networking is enabled by state file
Sep 17 11:35:48 gam0r-PC NetworkManager[811]: <info>  [1600335348.6118] dhcp-init: Using DHCP client 'internal'
Sep 17 11:35:48 gam0r-PC NetworkManager[811]: <info>  [1600335348.6135] settings: Loaded settings plugin: ifupdown ("/usr/lib/x86_64-linux-gnu/NetworkManager/1.22.10/libnm-settings-plugin-ifupdown.so")
Sep 17 11:35:48 gam0r-PC NetworkManager[811]: <info>  [1600335348.6136] settings: Loaded settings plugin: keyfile (internal)
Sep 17 11:35:48 gam0r-PC NetworkManager[811]: <info>  [1600335348.6136] ifupdown: management mode: unmanaged
Sep 17 11:35:48 gam0r-PC NetworkManager[811]: <info>  [1600335348.6136] ifupdown:       interface-parser: parsing file /etc/network/interfaces
Sep 17 11:35:48 gam0r-PC NetworkManager[811]: <info>  [1600335348.6136] ifupdown:       interface-parser: source line includes interfaces file(s) /etc/network/interfaces.d
Sep 17 11:35:48 gam0r-PC NetworkManager[811]: <info>  [1600335348.6137] ifupdown:       interface-parser: finished parsing file /etc/network/interfaces
Sep 17 11:35:48 gam0r-PC NetworkManager[811]: <info>  [1600335348.6184] device (lo): carrier: link connected
Sep 17 11:35:48 gam0r-PC dbus-daemon[809]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.13' (uid=0 pid=811 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined")
Sep 17 11:35:48 gam0r-PC NetworkManager[811]: <info>  [1600335348.6187] manager: (lo): new Generic device (/org/freedesktop/NetworkManager/Devices/1)
Sep 17 11:35:48 gam0r-PC NetworkManager[811]: <info>  [1600335348.6200] manager: (enp3s0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/2)
Sep 17 11:35:48 gam0r-PC systemd[1]: Starting Network Manager Script Dispatcher Service...
Sep 17 11:35:48 gam0r-PC NetworkManager[811]: <info>  [1600335348.6224] settings: (enp3s0): created default wired connection 'Wired connection 1'
Sep 17 11:35:48 gam0r-PC NetworkManager[811]: <info>  [1600335348.6233] device (enp3s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Sep 17 11:35:48 gam0r-PC kernel: [   16.924016] Generic FE-GE Realtek PHY r8169-300:00: attached PHY driver [Generic FE-GE Realtek PHY] (mii_bus:phy_addr=r8169-300:00, irq=IGNORE)
Sep 17 11:35:48 gam0r-PC dbus-daemon[809]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Sep 17 11:35:48 gam0r-PC systemd[1]: Started Network Manager Script Dispatcher Service.
Sep 17 11:35:48 gam0r-PC systemd[1]: Finished Save/Restore Sound Card State.
Sep 17 11:35:48 gam0r-PC systemd[1]: Reached target Sound Card.
Sep 17 11:35:48 gam0r-PC systemd[1]: Started Disk Manager.
Sep 17 11:35:48 gam0r-PC udisksd[848]: Acquired the name org.freedesktop.UDisks2 on the system message bus
Sep 17 11:35:48 gam0r-PC systemd[1]: Reached target Graphical Interface.
Sep 17 11:35:48 gam0r-PC systemd[1]: Starting Update UTMP about System Runlevel Changes...
Sep 17 11:35:48 gam0r-PC systemd[1]: systemd-update-utmp-runlevel.service: Succeeded.
Sep 17 11:35:48 gam0r-PC systemd[1]: Finished Update UTMP about System Runlevel Changes.
Sep 17 11:35:48 gam0r-PC systemd[1]: mintsystem.service: Succeeded.
Sep 17 11:35:48 gam0r-PC NetworkManager[811]: <info>  [1600335348.7399] device (wlp2s0): driver supports Access Point (AP) mode
Sep 17 11:35:48 gam0r-PC NetworkManager[811]: <info>  [1600335348.7402] manager: (wlp2s0): new 802.11 Wi-Fi device (/org/freedesktop/NetworkManager/Devices/3)
Sep 17 11:35:48 gam0r-PC kernel: [   17.037663] r8169 0000:03:00.0 enp3s0: Link is Down
Sep 17 11:35:48 gam0r-PC NetworkManager[811]: <info>  [1600335348.7438] device (wlp2s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Sep 17 11:35:48 gam0r-PC kernel: [   17.055705] iwlwifi 0000:02:00.0: Applying debug destination EXTERNAL_DRAM
Sep 17 11:35:48 gam0r-PC systemd[1]: man-db.service: Succeeded.
Sep 17 11:35:48 gam0r-PC systemd[1]: Finished Daily man-db regeneration.
Sep 17 11:35:48 gam0r-PC systemd[1]: Startup finished in 4.025s (firmware) + 3.977s (loader) + 15.293s (kernel) + 1.828s (userspace) = 25.124s.
Sep 17 11:35:48 gam0r-PC set-cpufreq[827]: Setting powersave scheduler for all CPUs
Sep 17 11:35:48 gam0r-PC systemd[1]: ondemand.service: Succeeded.
Sep 17 11:35:48 gam0r-PC kernel: [   17.131758] iwlwifi 0000:02:00.0: Applying debug destination EXTERNAL_DRAM
Sep 17 11:35:48 gam0r-PC kernel: [   17.132998] iwlwifi 0000:02:00.0: FW already configured (0) - re-configuring
Sep 17 11:35:48 gam0r-PC NetworkManager[811]: <info>  [1600335348.8414] modem-manager: ModemManager available
Sep 17 11:35:48 gam0r-PC kernel: [   17.138562] iwlwifi 0000:02:00.0: BIOS contains WGDS but no WRDS
Sep 17 11:35:48 gam0r-PC NetworkManager[811]: <info>  [1600335348.8422] supplicant: wpa_supplicant running
Sep 17 11:35:48 gam0r-PC NetworkManager[811]: <info>  [1600335348.8423] device (wlp2s0): supplicant interface state: init -> starting
Sep 17 11:35:48 gam0r-PC NetworkManager[811]: <info>  [1600335348.9607] sup-iface[0x560376313100,wlp2s0]: supports 5 scan SSIDs
Sep 17 11:35:48 gam0r-PC NetworkManager[811]: <info>  [1600335348.9626] device (wlp2s0): supplicant interface state: starting -> ready
Sep 17 11:35:48 gam0r-PC NetworkManager[811]: <info>  [1600335348.9629] Wi-Fi P2P device controlled by interface wlp2s0 created
Sep 17 11:35:48 gam0r-PC NetworkManager[811]: <info>  [1600335348.9635] manager: (p2p-dev-wlp2s0): new 802.11 Wi-Fi P2P device (/org/freedesktop/NetworkManager/Devices/4)
Sep 17 11:35:48 gam0r-PC NetworkManager[811]: <info>  [1600335348.9645] device (p2p-dev-wlp2s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Sep 17 11:35:48 gam0r-PC NetworkManager[811]: <info>  [1600335348.9669] device (p2p-dev-wlp2s0): state change: unavailable -> disconnected (reason 'none', sys-iface-state: 'managed')
Sep 17 11:35:48 gam0r-PC NetworkManager[811]: <info>  [1600335348.9677] device (wlp2s0): state change: unavailable -> disconnected (reason 'supplicant-available', sys-iface-state: 'managed')
Sep 17 11:35:48 gam0r-PC NetworkManager[811]: <warn>  [1600335348.9701] sup-iface: failed to cancel p2p connect: P2P cancel failed
Sep 17 11:35:49 gam0r-PC systemd[1]: dmesg.service: Succeeded.
Sep 17 11:35:49 gam0r-PC avahi-daemon[804]: Server startup complete. Host name is gam0r-PC.local. Local service cookie is 1364884483.
Sep 17 11:35:49 gam0r-PC kernel: [   18.228766] Bluetooth: hci0: command 0xfc8e tx timeout
Sep 17 11:35:50 gam0r-PC systemd[1]: Created slice User Slice of UID 120.
Sep 17 11:35:50 gam0r-PC systemd[1]: Starting User Runtime Directory /run/user/120...
Sep 17 11:35:50 gam0r-PC systemd[1]: Finished User Runtime Directory /run/user/120.
Sep 17 11:35:50 gam0r-PC systemd[1]: Starting User Manager for UID 120...
Sep 17 11:35:50 gam0r-PC systemd[1042]: Reached target Paths.
Sep 17 11:35:50 gam0r-PC systemd[1042]: Reached target Timers.
Sep 17 11:35:50 gam0r-PC systemd[1042]: Starting D-Bus User Message Bus Socket.
Sep 17 11:35:50 gam0r-PC systemd[1042]: Listening on GnuPG network certificate management daemon.
Sep 17 11:35:50 gam0r-PC systemd[1042]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers).
Sep 17 11:35:50 gam0r-PC systemd[1042]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
Sep 17 11:35:50 gam0r-PC systemd[1042]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
Sep 17 11:35:50 gam0r-PC systemd[1042]: Listening on GnuPG cryptographic agent and passphrase cache.
Sep 17 11:35:50 gam0r-PC systemd[1042]: Listening on debconf communication socket.
Sep 17 11:35:50 gam0r-PC systemd[1042]: Listening on Sound System.
Sep 17 11:35:50 gam0r-PC systemd[1042]: Listening on D-Bus User Message Bus Socket.
Sep 17 11:35:50 gam0r-PC systemd[1042]: Reached target Sockets.
Sep 17 11:35:50 gam0r-PC systemd[1042]: Reached target Basic System.
Sep 17 11:35:50 gam0r-PC systemd[1]: Started User Manager for UID 120.
Sep 17 11:35:50 gam0r-PC systemd[1042]: Starting Sound Service...
Sep 17 11:35:50 gam0r-PC systemd[1]: Started Session c1 of user lightdm.
Sep 17 11:35:50 gam0r-PC dbus-daemon[809]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.31' (uid=120 pid=1051 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined")
Sep 17 11:35:50 gam0r-PC systemd[1]: Starting RealtimeKit Scheduling Policy Service...
Sep 17 11:35:50 gam0r-PC dbus-daemon[809]: [system] Successfully activated service 'org.freedesktop.RealtimeKit1'
Sep 17 11:35:50 gam0r-PC systemd[1]: Started RealtimeKit Scheduling Policy Service.
Sep 17 11:35:50 gam0r-PC rtkit-daemon[1059]: Successfully called chroot.
Sep 17 11:35:50 gam0r-PC rtkit-daemon[1059]: Successfully dropped privileges.
Sep 17 11:35:50 gam0r-PC rtkit-daemon[1059]: Successfully limited resources.
Sep 17 11:35:50 gam0r-PC rtkit-daemon[1059]: Running.
Sep 17 11:35:50 gam0r-PC rtkit-daemon[1059]: Canary thread running.
Sep 17 11:35:50 gam0r-PC rtkit-daemon[1059]: Watchdog thread running.
Sep 17 11:35:50 gam0r-PC rtkit-daemon[1059]: Successfully made thread 1051 of process 1051 owned by '120' high priority at nice level -11.
Sep 17 11:35:50 gam0r-PC rtkit-daemon[1059]: Supervising 1 threads of 1 processes of 1 users.
Sep 17 11:35:50 gam0r-PC systemd[1042]: Started D-Bus User Message Bus.
Sep 17 11:35:50 gam0r-PC dbus-daemon[1065]: [session uid=120 pid=1065] AppArmor D-Bus mediation is enabled
Sep 17 11:35:50 gam0r-PC dbus-daemon[1065]: [session uid=120 pid=1065] Activating service name='ca.desrt.dconf' requested by ':1.2' (uid=120 pid=1058 comm="/usr/sbin/slick-greeter " label="unconfined")
Sep 17 11:35:50 gam0r-PC pulseaudio[1051]: No UCM verb is valid for hw:0
Sep 17 11:35:50 gam0r-PC dbus-daemon[1065]: [session uid=120 pid=1065] Successfully activated service 'ca.desrt.dconf'
Sep 17 11:35:50 gam0r-PC /slick-greeter-check-hidpi: Window scale: 1
Sep 17 11:35:50 gam0r-PC /slick-greeter-set-keyboard-layout: Current keyboard configuration: rules:      evdev#012model:      pc105#012layout:     ch
Sep 17 11:35:50 gam0r-PC /slick-greeter-set-keyboard-layout: Applying keyboard configuration: ['setxkbmap', '-model', 'pc105', '-layout', 'ch', '-variant', '', '-option', '', '-v']
Sep 17 11:35:50 gam0r-PC /slick-greeter-set-keyboard-layout: Result: Warning! Multiple definitions of keyboard model#012         Using command line, ignoring X server#012Warning! Multiple definitions of keyboard layout#012         Using command line, ignoring X server#012Trying to build keymap using the following components:#012keycodes:   evdev+aliases(qwerty)#012types:      complete#012compat:     complete#012symbols:    pc+ch+inet(evdev)#012geometry:   pc(pc105)
Sep 17 11:35:50 gam0r-PC /slick-greeter-set-keyboard-layout: New keyboard configuration: rules:      evdev#012model:      pc105#012layout:     ch
Sep 17 11:35:50 gam0r-PC dbus-daemon[1065]: [session uid=120 pid=1065] Activating via systemd: service name='org.a11y.Bus' unit='at-spi-dbus-bus.service' requested by ':1.4' (uid=120 pid=1058 comm="/usr/sbin/slick-greeter " label="unconfined")
Sep 17 11:35:50 gam0r-PC systemd[1042]: Starting Accessibility services bus...
Sep 17 11:35:50 gam0r-PC dbus-daemon[1065]: [session uid=120 pid=1065] Successfully activated service 'org.a11y.Bus'
Sep 17 11:35:50 gam0r-PC systemd[1042]: Started Accessibility services bus.
Sep 17 11:35:50 gam0r-PC dbus-daemon[1065]: [session uid=120 pid=1065] Activating via systemd: service name='org.gtk.vfs.Daemon' unit='gvfs-daemon.service' requested by ':1.2' (uid=120 pid=1058 comm="/usr/sbin/slick-greeter " label="unconfined")
Sep 17 11:35:50 gam0r-PC systemd[1042]: Starting Virtual filesystem service...
Sep 17 11:35:50 gam0r-PC dbus-daemon[1065]: [session uid=120 pid=1065] Successfully activated service 'org.gtk.vfs.Daemon'
Sep 17 11:35:50 gam0r-PC systemd[1042]: Started Virtual filesystem service.
Sep 17 11:35:50 gam0r-PC rtkit-daemon[1059]: Supervising 1 threads of 1 processes of 1 users.
Sep 17 11:35:50 gam0r-PC rtkit-daemon[1059]: Successfully made thread 1099 of process 1051 owned by '120' RT at priority 5.
Sep 17 11:35:50 gam0r-PC rtkit-daemon[1059]: Supervising 2 threads of 1 processes of 1 users.
Sep 17 11:35:50 gam0r-PC dbus-daemon[809]: [system] Activating via systemd: service name='org.freedesktop.UPower' unit='upower.service' requested by ':1.33' (uid=120 pid=1058 comm="/usr/sbin/slick-greeter " label="unconfined")
Sep 17 11:35:50 gam0r-PC rtkit-daemon[1059]: Supervising 2 threads of 1 processes of 1 users.
Sep 17 11:35:50 gam0r-PC systemd[1]: Starting Daemon for power management...
Sep 17 11:35:50 gam0r-PC rtkit-daemon[1059]: Successfully made thread 1100 of process 1051 owned by '120' RT at priority 5.
Sep 17 11:35:50 gam0r-PC rtkit-daemon[1059]: Supervising 3 threads of 1 processes of 1 users.
Sep 17 11:35:50 gam0r-PC systemd[1042]: Started Sound Service.
Sep 17 11:35:50 gam0r-PC systemd[1042]: Reached target Main User Target.
Sep 17 11:35:50 gam0r-PC systemd[1042]: Startup finished in 471ms.
Sep 17 11:35:50 gam0r-PC dbus-daemon[809]: [system] Successfully activated service 'org.freedesktop.UPower'
Sep 17 11:35:50 gam0r-PC systemd[1]: Started Daemon for power management.
Sep 17 11:35:50 gam0r-PC at-spi-bus-launcher[1086]: dbus-daemon[1086]: Activating service name='org.a11y.atspi.Registry' requested by ':1.0' (uid=120 pid=1058 comm="/usr/sbin/slick-greeter " label="unconfined")
Sep 17 11:35:50 gam0r-PC at-spi-bus-launcher[1086]: dbus-daemon[1086]: Successfully activated service 'org.a11y.atspi.Registry'
Sep 17 11:35:50 gam0r-PC at-spi-bus-launcher[1128]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
Sep 17 11:35:50 gam0r-PC ModemManager[904]: <info>  Couldn't check support for device '/sys/devices/pci0000:00/0000:00:1c.4/0000:02:00.0': not supported by any plugin
Sep 17 11:35:50 gam0r-PC ModemManager[904]: <info>  Couldn't check support for device '/sys/devices/pci0000:00/0000:00:1c.5/0000:03:00.0': not supported by any plugin
Sep 17 11:35:52 gam0r-PC wpa_supplicant[850]: wlp2s0: CTRL-EVENT-REGDOM-CHANGE init=DRIVER type=COUNTRY alpha2=CH
Sep 17 11:35:52 gam0r-PC NetworkManager[811]: <info>  [1600335352.4416] policy: auto-activating connection 'PROL4N_2' (9fd00be9-32ae-454d-9c72-9ec0882e0a1d)
Sep 17 11:35:52 gam0r-PC NetworkManager[811]: <info>  [1600335352.4421] device (wlp2s0): Activation: starting connection 'PROL4N_2' (9fd00be9-32ae-454d-9c72-9ec0882e0a1d)
Sep 17 11:35:52 gam0r-PC NetworkManager[811]: <info>  [1600335352.4422] device (wlp2s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Sep 17 11:35:52 gam0r-PC NetworkManager[811]: <info>  [1600335352.4425] manager: NetworkManager state is now CONNECTING
Sep 17 11:35:52 gam0r-PC NetworkManager[811]: <info>  [1600335352.4428] device (wlp2s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Sep 17 11:35:52 gam0r-PC NetworkManager[811]: <info>  [1600335352.4432] device (wlp2s0): Activation: (wifi) access point 'PROL4N_2' has security, but secrets are required.
Sep 17 11:35:52 gam0r-PC NetworkManager[811]: <info>  [1600335352.4432] device (wlp2s0): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
Sep 17 11:35:52 gam0r-PC NetworkManager[811]: <info>  [1600335352.4434] sup-iface[0x560376313100,wlp2s0]: wps: type pbc start...
Sep 17 11:35:52 gam0r-PC NetworkManager[811]: <info>  [1600335352.4454] device (wlp2s0): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
Sep 17 11:35:52 gam0r-PC NetworkManager[811]: <info>  [1600335352.4457] device (wlp2s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Sep 17 11:35:52 gam0r-PC NetworkManager[811]: <info>  [1600335352.4460] device (wlp2s0): Activation: (wifi) connection 'PROL4N_2' has security, and secrets exist.  No new secrets needed.
Sep 17 11:35:52 gam0r-PC NetworkManager[811]: <info>  [1600335352.4460] Config: added 'ssid' value 'PROL4N_2'
Sep 17 11:35:52 gam0r-PC NetworkManager[811]: <info>  [1600335352.4461] Config: added 'scan_ssid' value '1'
Sep 17 11:35:52 gam0r-PC NetworkManager[811]: <info>  [1600335352.4461] Config: added 'bgscan' value 'simple:30:-70:86400'
Sep 17 11:35:52 gam0r-PC NetworkManager[811]: <info>  [1600335352.4461] Config: added 'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 FT-PSK'
Sep 17 11:35:52 gam0r-PC NetworkManager[811]: <info>  [1600335352.4461] Config: added 'auth_alg' value 'OPEN'
Sep 17 11:35:52 gam0r-PC NetworkManager[811]: <info>  [1600335352.4461] Config: added 'psk' value '<hidden>'
Sep 17 11:35:52 gam0r-PC wpa_supplicant[850]: wlp2s0: SME: Trying to authenticate with 7c:ff:4d:3d:ee:0f (SSID='PROL4N_2' freq=2462 MHz)
Sep 17 11:35:52 gam0r-PC kernel: [   20.750191] wlp2s0: authenticate with 7c:ff:4d:3d:ee:0f
Sep 17 11:35:52 gam0r-PC NetworkManager[811]: <info>  [1600335352.4574] device (wlp2s0): supplicant interface state: ready -> authenticating
Sep 17 11:35:52 gam0r-PC kernel: [   20.753568] wlp2s0: send auth to 7c:ff:4d:3d:ee:0f (try 1/3)
Sep 17 11:35:52 gam0r-PC NetworkManager[811]: <info>  [1600335352.4575] device (p2p-dev-wlp2s0): supplicant management interface state: ready -> authenticating
Sep 17 11:35:52 gam0r-PC wpa_supplicant[850]: wlp2s0: Trying to associate with 7c:ff:4d:3d:ee:0f (SSID='PROL4N_2' freq=2462 MHz)
Sep 17 11:35:52 gam0r-PC kernel: [   20.759382] wlp2s0: authenticated
Sep 17 11:35:52 gam0r-PC NetworkManager[811]: <info>  [1600335352.4621] device (wlp2s0): supplicant interface state: authenticating -> associating
Sep 17 11:35:52 gam0r-PC NetworkManager[811]: <info>  [1600335352.4622] device (p2p-dev-wlp2s0): supplicant management interface state: authenticating -> associating
Sep 17 11:35:52 gam0r-PC kernel: [   20.764592] wlp2s0: associate with 7c:ff:4d:3d:ee:0f (try 1/3)
Sep 17 11:35:52 gam0r-PC kernel: [   20.772374] wlp2s0: RX AssocResp from 7c:ff:4d:3d:ee:0f (capab=0x1431 status=0 aid=3)
Sep 17 11:35:52 gam0r-PC wpa_supplicant[850]: wlp2s0: Associated with 7c:ff:4d:3d:ee:0f
Sep 17 11:35:52 gam0r-PC wpa_supplicant[850]: wlp2s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Sep 17 11:35:52 gam0r-PC kernel: [   20.778634] wlp2s0: associated
Sep 17 11:35:52 gam0r-PC NetworkManager[811]: <info>  [1600335352.4871] device (wlp2s0): supplicant interface state: associating -> 4-way handshake
Sep 17 11:35:52 gam0r-PC NetworkManager[811]: <info>  [1600335352.4872] device (p2p-dev-wlp2s0): supplicant management interface state: associating -> 4-way handshake
Sep 17 11:35:52 gam0r-PC kernel: [   20.839194] wlp2s0: Limiting TX power to 20 (20 - 0) dBm as advertised by 7c:ff:4d:3d:ee:0f
Sep 17 11:35:52 gam0r-PC kernel: [   20.840555] IPv6: ADDRCONF(NETDEV_CHANGE): wlp2s0: link becomes ready
Sep 17 11:35:52 gam0r-PC wpa_supplicant[850]: wlp2s0: WPA: Key negotiation completed with 7c:ff:4d:3d:ee:0f [PTK=CCMP GTK=CCMP]
Sep 17 11:35:52 gam0r-PC wpa_supplicant[850]: wlp2s0: CTRL-EVENT-CONNECTED - Connection to 7c:ff:4d:3d:ee:0f completed [id=0 id_str=]
Sep 17 11:35:52 gam0r-PC wpa_supplicant[850]: wlp2s0: CTRL-EVENT-SIGNAL-CHANGE above=0 signal=-57 noise=9999 txrate=1000
Sep 17 11:35:52 gam0r-PC NetworkManager[811]: <info>  [1600335352.5481] device (wlp2s0): supplicant interface state: 4-way handshake -> completed
Sep 17 11:35:52 gam0r-PC NetworkManager[811]: <info>  [1600335352.5482] device (wlp2s0): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to wireless network "PROL4N_2"
Sep 17 11:35:52 gam0r-PC NetworkManager[811]: <info>  [1600335352.5483] device (p2p-dev-wlp2s0): supplicant management interface state: 4-way handshake -> completed
Sep 17 11:35:52 gam0r-PC NetworkManager[811]: <info>  [1600335352.5487] device (wlp2s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Sep 17 11:35:52 gam0r-PC NetworkManager[811]: <info>  [1600335352.5502] dhcp4 (wlp2s0): activation: beginning transaction (timeout in 45 seconds)
Sep 17 11:35:52 gam0r-PC avahi-daemon[804]: Joining mDNS multicast group on interface wlp2s0.IPv6 with address fe80::74e4:6644:8d2b:b24d.
Sep 17 11:35:52 gam0r-PC avahi-daemon[804]: New relevant interface wlp2s0.IPv6 for mDNS.
Sep 17 11:35:52 gam0r-PC avahi-daemon[804]: Registering new address record for fe80::74e4:6644:8d2b:b24d on wlp2s0.*.
Sep 17 11:35:52 gam0r-PC NetworkManager[811]: <info>  [1600335352.5665] dhcp4 (wlp2s0): option dhcp_lease_time      => '864000'
Sep 17 11:35:52 gam0r-PC NetworkManager[811]: <info>  [1600335352.5666] dhcp4 (wlp2s0): option domain_name          => 'fritz.box'
Sep 17 11:35:52 gam0r-PC NetworkManager[811]: <info>  [1600335352.5666] dhcp4 (wlp2s0): option domain_name_servers  => '192.168.178.1'
Sep 17 11:35:52 gam0r-PC NetworkManager[811]: <info>  [1600335352.5666] dhcp4 (wlp2s0): option expiry               => '1601199352'
Sep 17 11:35:52 gam0r-PC NetworkManager[811]: <info>  [1600335352.5666] dhcp4 (wlp2s0): option ip_address           => '192.168.178.58'
Sep 17 11:35:52 gam0r-PC NetworkManager[811]: <info>  [1600335352.5667] dhcp4 (wlp2s0): option next_server          => '192.168.178.1'
Sep 17 11:35:52 gam0r-PC NetworkManager[811]: <info>  [1600335352.5667] dhcp4 (wlp2s0): option ntp_servers          => '192.168.178.1'
Sep 17 11:35:52 gam0r-PC NetworkManager[811]: <info>  [1600335352.5667] dhcp4 (wlp2s0): option requested_broadcast_address => '1'
Sep 17 11:35:52 gam0r-PC NetworkManager[811]: <info>  [1600335352.5667] dhcp4 (wlp2s0): option requested_domain_name => '1'
Sep 17 11:35:52 gam0r-PC NetworkManager[811]: <info>  [1600335352.5668] dhcp4 (wlp2s0): option requested_domain_name_servers => '1'
Sep 17 11:35:52 gam0r-PC avahi-daemon[804]: Joining mDNS multicast group on interface wlp2s0.IPv4 with address 192.168.178.58.
Sep 17 11:35:52 gam0r-PC NetworkManager[811]: <info>  [1600335352.5668] dhcp4 (wlp2s0): option requested_domain_search => '1'
Sep 17 11:35:52 gam0r-PC avahi-daemon[804]: New relevant interface wlp2s0.IPv4 for mDNS.
Sep 17 11:35:52 gam0r-PC NetworkManager[811]: <info>  [1600335352.5668] dhcp4 (wlp2s0): option requested_host_name  => '1'
Sep 17 11:35:52 gam0r-PC avahi-daemon[804]: Registering new address record for 192.168.178.58 on wlp2s0.IPv4.
Sep 17 11:35:52 gam0r-PC NetworkManager[811]: <info>  [1600335352.5668] dhcp4 (wlp2s0): option requested_interface_mtu => '1'
Sep 17 11:35:52 gam0r-PC NetworkManager[811]: <info>  [1600335352.5669] dhcp4 (wlp2s0): option requested_ms_classless_static_routes => '1'
Sep 17 11:35:52 gam0r-PC NetworkManager[811]: <info>  [1600335352.5669] dhcp4 (wlp2s0): option requested_nis_domain => '1'
Sep 17 11:35:52 gam0r-PC NetworkManager[811]: <info>  [1600335352.5669] dhcp4 (wlp2s0): option requested_nis_servers => '1'
Sep 17 11:35:52 gam0r-PC NetworkManager[811]: <info>  [1600335352.5669] dhcp4 (wlp2s0): option requested_ntp_servers => '1'
Sep 17 11:35:52 gam0r-PC NetworkManager[811]: <info>  [1600335352.5669] dhcp4 (wlp2s0): option requested_rfc3442_classless_static_routes => '1'
Sep 17 11:35:52 gam0r-PC NetworkManager[811]: <info>  [1600335352.5670] dhcp4 (wlp2s0): option requested_root_path  => '1'
Sep 17 11:35:52 gam0r-PC NetworkManager[811]: <info>  [1600335352.5670] dhcp4 (wlp2s0): option requested_routers    => '1'
Sep 17 11:35:52 gam0r-PC NetworkManager[811]: <info>  [1600335352.5670] dhcp4 (wlp2s0): option requested_static_routes => '1'
Sep 17 11:35:52 gam0r-PC NetworkManager[811]: <info>  [1600335352.5670] dhcp4 (wlp2s0): option requested_subnet_mask => '1'
Sep 17 11:35:52 gam0r-PC NetworkManager[811]: <info>  [1600335352.5671] dhcp4 (wlp2s0): option requested_time_offset => '1'
Sep 17 11:35:52 gam0r-PC NetworkManager[811]: <info>  [1600335352.5671] dhcp4 (wlp2s0): option requested_wpad       => '1'
Sep 17 11:35:52 gam0r-PC NetworkManager[811]: <info>  [1600335352.5671] dhcp4 (wlp2s0): option routers              => '192.168.178.1'
Sep 17 11:35:52 gam0r-PC NetworkManager[811]: <info>  [1600335352.5671] dhcp4 (wlp2s0): option subnet_mask          => '255.255.255.0'
Sep 17 11:35:52 gam0r-PC NetworkManager[811]: <info>  [1600335352.5672] dhcp4 (wlp2s0): state changed unknown -> bound
Sep 17 11:35:52 gam0r-PC NetworkManager[811]: <info>  [1600335352.5707] device (wlp2s0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Sep 17 11:35:52 gam0r-PC NetworkManager[811]: <info>  [1600335352.5762] device (wlp2s0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Sep 17 11:35:52 gam0r-PC NetworkManager[811]: <info>  [1600335352.5770] device (wlp2s0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Sep 17 11:35:52 gam0r-PC NetworkManager[811]: <info>  [1600335352.5785] manager: NetworkManager state is now CONNECTED_LOCAL
Sep 17 11:35:52 gam0r-PC NetworkManager[811]: <info>  [1600335352.5841] manager: NetworkManager state is now CONNECTED_SITE
Sep 17 11:35:52 gam0r-PC NetworkManager[811]: <info>  [1600335352.5846] policy: set 'PROL4N_2' (wlp2s0) as default for IPv4 routing and DNS
Sep 17 11:35:52 gam0r-PC NetworkManager[811]: <info>  [1600335352.5864] device (wlp2s0): Activation: successful, device activated.
Sep 17 11:35:52 gam0r-PC systemd-resolved[756]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.
Sep 17 11:35:52 gam0r-PC NetworkManager[811]: <info>  [1600335352.8993] manager: NetworkManager state is now CONNECTED_GLOBAL
Sep 17 11:35:53 gam0r-PC systemd[1]: systemd-rfkill.service: Succeeded.
Sep 17 11:35:54 gam0r-PC systemd-resolved[756]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.
Sep 17 11:35:54 gam0r-PC NetworkManager[811]: <info>  [1600335354.7397] manager: startup complete
Sep 17 11:35:58 gam0r-PC kernel: [   26.452810] Bluetooth: hci0: sending Intel patch command (0xfc8e) failed (-110)
Sep 17 11:35:58 gam0r-PC kernel: [   26.452898] Bluetooth: hci0: sending frame failed (-19)
Sep 17 11:35:58 gam0r-PC systemd-resolved[756]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.
Sep 17 11:36:00 gam0r-PC kernel: [   28.468806] Bluetooth: hci0: command 0xfc11 tx timeout
Sep 17 11:36:00 gam0r-PC kernel: [   28.468811] Bluetooth: hci0: Exiting manufacturer mode failed (-110)
Sep 17 11:36:00 gam0r-PC systemd[1]: Starting Load/Save RF Kill Switch Status...
Sep 17 11:36:00 gam0r-PC systemd[1]: Started Load/Save RF Kill Switch Status.
Sep 17 11:36:00 gam0r-PC systemd[1]: Stopped target Bluetooth.
Sep 17 11:36:02 gam0r-PC systemd-resolved[756]: Using degraded feature set (UDP) for DNS server 192.168.178.1.
Sep 17 11:36:02 gam0r-PC systemd[1]: NetworkManager-dispatcher.service: Succeeded.
Sep 17 11:36:05 gam0r-PC systemd[1]: systemd-rfkill.service: Succeeded.
Sep 17 11:36:14 gam0r-PC systemd[1]: Stopping Session c1 of user lightdm.
Sep 17 11:36:14 gam0r-PC systemd[1]: session-c1.scope: Succeeded.
Sep 17 11:36:14 gam0r-PC systemd[1]: Stopped Session c1 of user lightdm.
Sep 17 11:36:14 gam0r-PC systemd[1]: Created slice User Slice of UID 1000.
Sep 17 11:36:14 gam0r-PC systemd[1]: Starting User Runtime Directory /run/user/1000...
Sep 17 11:36:14 gam0r-PC systemd[1]: Finished User Runtime Directory /run/user/1000.
Sep 17 11:36:14 gam0r-PC systemd[1]: Starting User Manager for UID 1000...
Sep 17 11:36:14 gam0r-PC pulseaudio[1051]: Error opening PCM device front:0: No such file or directory
Sep 17 11:36:14 gam0r-PC pulseaudio[1051]: Error opening PCM device front:0: No such file or directory
Sep 17 11:36:14 gam0r-PC systemd[1042]: pulseaudio.service: Succeeded.
Sep 17 11:36:15 gam0r-PC systemd[1219]: Reached target Paths.
Sep 17 11:36:15 gam0r-PC systemd[1219]: Reached target Timers.
Sep 17 11:36:15 gam0r-PC systemd[1219]: Starting D-Bus User Message Bus Socket.
Sep 17 11:36:15 gam0r-PC systemd[1219]: Listening on GnuPG network certificate management daemon.
Sep 17 11:36:15 gam0r-PC systemd[1219]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers).
Sep 17 11:36:15 gam0r-PC systemd[1219]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
Sep 17 11:36:15 gam0r-PC systemd[1219]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
Sep 17 11:36:15 gam0r-PC systemd[1219]: Listening on GnuPG cryptographic agent and passphrase cache.
Sep 17 11:36:15 gam0r-PC systemd[1219]: Listening on debconf communication socket.
Sep 17 11:36:15 gam0r-PC systemd[1219]: Listening on Sound System.
Sep 17 11:36:15 gam0r-PC systemd[1219]: Listening on D-Bus User Message Bus Socket.
Sep 17 11:36:15 gam0r-PC systemd[1219]: Reached target Sockets.
Sep 17 11:36:15 gam0r-PC systemd[1219]: Reached target Basic System.
Sep 17 11:36:15 gam0r-PC systemd[1]: Started User Manager for UID 1000.
Sep 17 11:36:15 gam0r-PC systemd[1219]: Starting Sound Service...
Sep 17 11:36:15 gam0r-PC systemd[1]: Started Session c2 of user grubi.
Sep 17 11:36:15 gam0r-PC rtkit-daemon[1059]: Successfully made thread 1237 of process 1237 owned by '1000' high priority at nice level -11.
Sep 17 11:36:15 gam0r-PC rtkit-daemon[1059]: Supervising 1 threads of 1 processes of 1 users.
Sep 17 11:36:15 gam0r-PC systemd[1219]: Started D-Bus User Message Bus.
Sep 17 11:36:15 gam0r-PC dbus-daemon[1257]: [session uid=1000 pid=1257] AppArmor D-Bus mediation is enabled
Sep 17 11:36:15 gam0r-PC pulseaudio[1237]: No UCM verb is valid for hw:0
Sep 17 11:36:15 gam0r-PC dbus-daemon[1257]: [session uid=1000 pid=1257] Activating via systemd: service name='org.a11y.Bus' unit='at-spi-dbus-bus.service' requested by ':1.7' (uid=1000 pid=1243 comm="cinnamon-session --session cinnamon " label="unconfined")
Sep 17 11:36:15 gam0r-PC systemd[1219]: Starting Accessibility services bus...
Sep 17 11:36:15 gam0r-PC dbus-daemon[1257]: [session uid=1000 pid=1257] Successfully activated service 'org.a11y.Bus'
Sep 17 11:36:15 gam0r-PC systemd[1219]: Started Accessibility services bus.
Sep 17 11:36:15 gam0r-PC at-spi-bus-launcher[1328]: dbus-daemon[1328]: Activating service name='org.a11y.atspi.Registry' requested by ':1.0' (uid=1000 pid=1243 comm="cinnamon-session --session cinnamon " label="unconfined")
Sep 17 11:36:15 gam0r-PC at-spi-bus-launcher[1328]: dbus-daemon[1328]: Successfully activated service 'org.a11y.atspi.Registry'
Sep 17 11:36:15 gam0r-PC at-spi-bus-launcher[1331]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
Sep 17 11:36:15 gam0r-PC rtkit-daemon[1059]: Supervising 1 threads of 1 processes of 1 users.
Sep 17 11:36:15 gam0r-PC rtkit-daemon[1059]: Successfully made thread 1354 of process 1237 owned by '1000' RT at priority 5.
Sep 17 11:36:15 gam0r-PC dbus-daemon[1257]: [session uid=1000 pid=1257] Activating via systemd: service name='org.gtk.vfs.Daemon' unit='gvfs-daemon.service' requested by ':1.13' (uid=1000 pid=1344 comm="/usr/lib/x86_64-linux-gnu/cinnamon-settings-daemon" label="unconfined")
Sep 17 11:36:15 gam0r-PC rtkit-daemon[1059]: Supervising 2 threads of 1 processes of 1 users.
Sep 17 11:36:15 gam0r-PC systemd[1219]: Starting Virtual filesystem service...
Sep 17 11:36:15 gam0r-PC rtkit-daemon[1059]: Supervising 2 threads of 1 processes of 1 users.
Sep 17 11:36:15 gam0r-PC rtkit-daemon[1059]: Successfully made thread 1370 of process 1237 owned by '1000' RT at priority 5.
Sep 17 11:36:15 gam0r-PC rtkit-daemon[1059]: Supervising 3 threads of 1 processes of 1 users.
Sep 17 11:36:15 gam0r-PC dbus-daemon[1257]: [session uid=1000 pid=1257] Successfully activated service 'org.gtk.vfs.Daemon'
Sep 17 11:36:15 gam0r-PC systemd[1219]: Started Virtual filesystem service.
Sep 17 11:36:15 gam0r-PC systemd[1219]: Started Sound Service.
Sep 17 11:36:15 gam0r-PC systemd[1219]: Reached target Main User Target.
Sep 17 11:36:15 gam0r-PC systemd[1219]: Startup finished in 407ms.
omg_me
Level 1
Level 1
Posts: 21
Joined: Thu Aug 27, 2020 9:16 pm

Re: Unexpected Shutdowns

Post by omg_me »

And even more logs:

Code: Select all

Sep 17 11:36:15 gam0r-PC dbus-daemon[1257]: [session uid=1000 pid=1257] Activating service name='ca.desrt.dconf' requested by ':1.22' (uid=1000 pid=1357 comm="/usr/lib/x86_64-linux-gnu/cinnamon-settings-daemon" label="unconfined")
Sep 17 11:36:15 gam0r-PC dbus-daemon[809]: [system] Activating via systemd: service name='org.freedesktop.ColorManager' unit='colord.service' requested by ':1.53' (uid=1000 pid=1343 comm="/usr/lib/x86_64-linux-gnu/cinnamon-settings-daemon" label="unconfined")
Sep 17 11:36:15 gam0r-PC systemd[1]: Starting Manage, Install and Generate Color Profiles...
Sep 17 11:36:15 gam0r-PC dbus-daemon[1257]: [session uid=1000 pid=1257] Successfully activated service 'ca.desrt.dconf'
Sep 17 11:36:15 gam0r-PC dbus-daemon[809]: [system] Successfully activated service 'org.freedesktop.ColorManager'
Sep 17 11:36:15 gam0r-PC systemd[1]: Started Manage, Install and Generate Color Profiles.
Sep 17 11:36:15 gam0r-PC dbus-daemon[1257]: [session uid=1000 pid=1257] Activating via systemd: service name='org.gtk.vfs.UDisks2VolumeMonitor' unit='gvfs-udisks2-volume-monitor.service' requested by ':1.29' (uid=1000 pid=1373 comm="/usr/lib/x86_64-linux-gnu/cinnamon-settings-daemon" label="unconfined")
Sep 17 11:36:15 gam0r-PC systemd[1219]: Starting Virtual filesystem service - disk device monitor...
Sep 17 11:36:15 gam0r-PC dbus-daemon[1257]: [session uid=1000 pid=1257] Successfully activated service 'org.gtk.vfs.UDisks2VolumeMonitor'
Sep 17 11:36:15 gam0r-PC systemd[1219]: Started Virtual filesystem service - disk device monitor.
Sep 17 11:36:15 gam0r-PC dbus-daemon[1257]: [session uid=1000 pid=1257] Activating via systemd: service name='org.gtk.vfs.GPhoto2VolumeMonitor' unit='gvfs-gphoto2-volume-monitor.service' requested by ':1.29' (uid=1000 pid=1373 comm="/usr/lib/x86_64-linux-gnu/cinnamon-settings-daemon" label="unconfined")
Sep 17 11:36:15 gam0r-PC systemd[1219]: Starting Virtual filesystem service - digital camera monitor...
Sep 17 11:36:15 gam0r-PC dbus-daemon[1257]: [session uid=1000 pid=1257] Successfully activated service 'org.gtk.vfs.GPhoto2VolumeMonitor'
Sep 17 11:36:15 gam0r-PC systemd[1219]: Started Virtual filesystem service - digital camera monitor.
Sep 17 11:36:15 gam0r-PC dbus-daemon[1257]: [session uid=1000 pid=1257] Activating via systemd: service name='org.gtk.vfs.GoaVolumeMonitor' unit='gvfs-goa-volume-monitor.service' requested by ':1.29' (uid=1000 pid=1373 comm="/usr/lib/x86_64-linux-gnu/cinnamon-settings-daemon" label="unconfined")
Sep 17 11:36:15 gam0r-PC systemd[1219]: Starting Virtual filesystem service - GNOME Online Accounts monitor...
Sep 17 11:36:15 gam0r-PC dbus-daemon[1257]: [session uid=1000 pid=1257] Activating service name='org.gnome.OnlineAccounts' requested by ':1.39' (uid=1000 pid=1480 comm="/usr/libexec/gvfs-goa-volume-monitor " label="unconfined")
Sep 17 11:36:15 gam0r-PC goa-daemon[1489]: goa-daemon version 3.36.0 starting
Sep 17 11:36:15 gam0r-PC dbus-daemon[1257]: [session uid=1000 pid=1257] Activating service name='org.gnome.Identity' requested by ':1.40' (uid=1000 pid=1489 comm="/usr/libexec/goa-daemon " label="unconfined")
Sep 17 11:36:15 gam0r-PC dbus-daemon[1257]: [session uid=1000 pid=1257] Successfully activated service 'org.gnome.OnlineAccounts'
Sep 17 11:36:15 gam0r-PC dbus-daemon[1257]: [session uid=1000 pid=1257] Successfully activated service 'org.gtk.vfs.GoaVolumeMonitor'
Sep 17 11:36:15 gam0r-PC systemd[1219]: Started Virtual filesystem service - GNOME Online Accounts monitor.
Sep 17 11:36:15 gam0r-PC dbus-daemon[1257]: [session uid=1000 pid=1257] Successfully activated service 'org.gnome.Identity'
Sep 17 11:36:15 gam0r-PC dbus-daemon[1257]: [session uid=1000 pid=1257] Activating via systemd: service name='org.gtk.vfs.AfcVolumeMonitor' unit='gvfs-afc-volume-monitor.service' requested by ':1.29' (uid=1000 pid=1373 comm="/usr/lib/x86_64-linux-gnu/cinnamon-settings-daemon" label="unconfined")
Sep 17 11:36:15 gam0r-PC systemd[1219]: Starting Virtual filesystem service - Apple File Conduit monitor...
Sep 17 11:36:15 gam0r-PC dbus-daemon[1257]: [session uid=1000 pid=1257] Successfully activated service 'org.gtk.vfs.AfcVolumeMonitor'
Sep 17 11:36:15 gam0r-PC systemd[1219]: Started Virtual filesystem service - Apple File Conduit monitor.
Sep 17 11:36:15 gam0r-PC dbus-daemon[1257]: [session uid=1000 pid=1257] Activating via systemd: service name='org.gtk.vfs.MTPVolumeMonitor' unit='gvfs-mtp-volume-monitor.service' requested by ':1.29' (uid=1000 pid=1373 comm="/usr/lib/x86_64-linux-gnu/cinnamon-settings-daemon" label="unconfined")
Sep 17 11:36:15 gam0r-PC systemd[1219]: Starting Virtual filesystem service - Media Transfer Protocol monitor...
Sep 17 11:36:15 gam0r-PC dbus-daemon[1257]: [session uid=1000 pid=1257] Successfully activated service 'org.gtk.vfs.MTPVolumeMonitor'
Sep 17 11:36:15 gam0r-PC systemd[1219]: Started Virtual filesystem service - Media Transfer Protocol monitor.
Sep 17 11:36:17 gam0r-PC NetworkManager[811]: <info>  [1600335377.4610] agent-manager: agent[5c5adc0098c06a6d,:1.65/org.freedesktop.nm-applet/1000]: agent registered
Sep 17 11:36:17 gam0r-PC /cinnamon-killer-daemon: Bound Cinnamon restart to <Control><Alt>Escape.
Sep 17 11:36:17 gam0r-PC dbus-daemon[1257]: [session uid=1000 pid=1257] Activating via systemd: service name='org.bluez.obex' unit='dbus-org.bluez.obex.service' requested by ':1.57' (uid=1000 pid=1567 comm="blueberry-obex-agent                              " label="unconfined")
Sep 17 11:36:17 gam0r-PC systemd[1219]: Starting Bluetooth OBEX service...
Sep 17 11:36:17 gam0r-PC obexd[1633]: OBEX daemon 5.53
Sep 17 11:36:17 gam0r-PC dbus-daemon[1257]: [session uid=1000 pid=1257] Successfully activated service 'org.bluez.obex'
Sep 17 11:36:17 gam0r-PC systemd[1219]: Started Bluetooth OBEX service.
Sep 17 11:36:17 gam0r-PC dbus-daemon[1257]: [session uid=1000 pid=1257] Activating via systemd: service name='org.gnome.evolution.dataserver.Sources5' unit='evolution-source-registry.service' requested by ':1.55' (uid=1000 pid=1581 comm="/usr/libexec/evolution-data-server/evolution-alarm" label="unconfined")
Sep 17 11:36:17 gam0r-PC systemd[1219]: Starting Evolution source registry...
Sep 17 11:36:17 gam0r-PC dbus-daemon[1257]: [session uid=1000 pid=1257] Successfully activated service 'org.gnome.evolution.dataserver.Sources5'
Sep 17 11:36:17 gam0r-PC systemd[1219]: Started Evolution source registry.
Sep 17 11:36:17 gam0r-PC dbus-daemon[1257]: [session uid=1000 pid=1257] Activating via systemd: service name='org.gnome.evolution.dataserver.Calendar8' unit='evolution-calendar-factory.service' requested by ':1.55' (uid=1000 pid=1581 comm="/usr/libexec/evolution-data-server/evolution-alarm" label="unconfined")
Sep 17 11:36:17 gam0r-PC systemd[1219]: Starting Evolution calendar service...
Sep 17 11:36:17 gam0r-PC dbus-daemon[1257]: [session uid=1000 pid=1257] Successfully activated service 'org.gnome.evolution.dataserver.Calendar8'
Sep 17 11:36:17 gam0r-PC systemd[1219]: Started Evolution calendar service.
Sep 17 11:36:17 gam0r-PC dbus-daemon[1257]: [session uid=1000 pid=1257] Activating via systemd: service name='org.gnome.evolution.dataserver.AddressBook10' unit='evolution-addressbook-factory.service' requested by ':1.61' (uid=1000 pid=1643 comm="/usr/libexec/evolution-calendar-factory " label="unconfined")
Sep 17 11:36:17 gam0r-PC systemd[1219]: Starting Evolution address book service...
Sep 17 11:36:17 gam0r-PC dbus-daemon[1257]: [session uid=1000 pid=1257] Successfully activated service 'org.gnome.evolution.dataserver.AddressBook10'
Sep 17 11:36:17 gam0r-PC systemd[1219]: Started Evolution address book service.
Sep 17 11:36:18 gam0r-PC systemd-timesyncd[760]: Initial synchronization to time server 91.189.89.199:123 (ntp.ubuntu.com).
Sep 17 11:36:18 gam0r-PC dbus-daemon[1257]: [session uid=1000 pid=1257] Activating via systemd: service name='org.gtk.vfs.Metadata' unit='gvfs-metadata.service' requested by ':1.52' (uid=1000 pid=1571 comm="nemo-desktop " label="unconfined")
Sep 17 11:36:18 gam0r-PC systemd[1219]: Starting Virtual filesystem metadata service...
Sep 17 11:36:18 gam0r-PC dbus-daemon[1257]: [session uid=1000 pid=1257] Successfully activated service 'org.gtk.vfs.Metadata'
Sep 17 11:36:18 gam0r-PC systemd[1219]: Started Virtual filesystem metadata service.
Sep 17 11:36:18 gam0r-PC systemd[1]: systemd-hostnamed.service: Succeeded.
Sep 17 11:36:18 gam0r-PC systemd[1]: systemd-fsckd.service: Succeeded.
Sep 17 11:36:22 gam0r-PC cinnamon-session[1243]: WARNING: t+7.65605s: Detected that screensaver has appeared on the bus
Sep 17 11:36:25 gam0r-PC systemd[1]: Stopping User Manager for UID 120...
Sep 17 11:36:25 gam0r-PC systemd[1042]: Stopped target Main User Target.
Sep 17 11:36:25 gam0r-PC systemd[1042]: Stopping Accessibility services bus...
Sep 17 11:36:25 gam0r-PC gvfsd[1087]: A connection to the bus can't be made
Sep 17 11:36:25 gam0r-PC systemd[1042]: Stopping D-Bus User Message Bus...
Sep 17 11:36:25 gam0r-PC systemd[1042]: Stopping Virtual filesystem service...
Sep 17 11:36:25 gam0r-PC systemd[1042]: dbus.service: Succeeded.
Sep 17 11:36:25 gam0r-PC systemd[1042]: Stopped D-Bus User Message Bus.
Sep 17 11:36:25 gam0r-PC systemd[1042]: at-spi-dbus-bus.service: Succeeded.
Sep 17 11:36:25 gam0r-PC systemd[1042]: Stopped Accessibility services bus.
Sep 17 11:36:25 gam0r-PC systemd[1]: run-user-120-gvfs.mount: Succeeded.
Sep 17 11:36:25 gam0r-PC systemd[1219]: run-user-120-gvfs.mount: Succeeded.
Sep 17 11:36:25 gam0r-PC systemd[1042]: run-user-120-gvfs.mount: Succeeded.
Sep 17 11:36:25 gam0r-PC systemd[1042]: gvfs-daemon.service: Succeeded.
Sep 17 11:36:25 gam0r-PC systemd[1042]: Stopped Virtual filesystem service.
Sep 17 11:36:25 gam0r-PC systemd[1042]: Stopped target Basic System.
Sep 17 11:36:25 gam0r-PC systemd[1042]: Stopped target Paths.
Sep 17 11:36:25 gam0r-PC systemd[1042]: Stopped target Sockets.
Sep 17 11:36:25 gam0r-PC systemd[1042]: Stopped target Timers.
Sep 17 11:36:25 gam0r-PC systemd[1042]: dbus.socket: Succeeded.
Sep 17 11:36:25 gam0r-PC systemd[1042]: Closed D-Bus User Message Bus Socket.
Sep 17 11:36:25 gam0r-PC systemd[1042]: dirmngr.socket: Succeeded.
Sep 17 11:36:25 gam0r-PC systemd[1042]: Closed GnuPG network certificate management daemon.
Sep 17 11:36:25 gam0r-PC systemd[1042]: gpg-agent-browser.socket: Succeeded.
Sep 17 11:36:25 gam0r-PC systemd[1042]: Closed GnuPG cryptographic agent and passphrase cache (access for web browsers).
Sep 17 11:36:25 gam0r-PC systemd[1042]: gpg-agent-extra.socket: Succeeded.
Sep 17 11:36:25 gam0r-PC systemd[1042]: Closed GnuPG cryptographic agent and passphrase cache (restricted).
Sep 17 11:36:25 gam0r-PC systemd[1042]: gpg-agent-ssh.socket: Succeeded.
Sep 17 11:36:25 gam0r-PC systemd[1042]: Closed GnuPG cryptographic agent (ssh-agent emulation).
Sep 17 11:36:25 gam0r-PC systemd[1042]: gpg-agent.socket: Succeeded.
Sep 17 11:36:25 gam0r-PC systemd[1042]: Closed GnuPG cryptographic agent and passphrase cache.
Sep 17 11:36:25 gam0r-PC systemd[1042]: pk-debconf-helper.socket: Succeeded.
Sep 17 11:36:25 gam0r-PC systemd[1042]: Closed debconf communication socket.
Sep 17 11:36:25 gam0r-PC systemd[1042]: pulseaudio.socket: Succeeded.
Sep 17 11:36:25 gam0r-PC systemd[1042]: Closed Sound System.
Sep 17 11:36:25 gam0r-PC systemd[1042]: Reached target Shutdown.
Sep 17 11:36:25 gam0r-PC systemd[1042]: systemd-exit.service: Succeeded.
Sep 17 11:36:25 gam0r-PC systemd[1042]: Finished Exit the Session.
Sep 17 11:36:25 gam0r-PC systemd[1042]: Reached target Exit the Session.
Sep 17 11:36:25 gam0r-PC systemd[1]: user@120.service: Succeeded.
Sep 17 11:36:25 gam0r-PC systemd[1]: Stopped User Manager for UID 120.
Sep 17 11:36:25 gam0r-PC systemd[1]: Stopping User Runtime Directory /run/user/120...
Sep 17 11:36:25 gam0r-PC systemd[1219]: run-user-120.mount: Succeeded.
Sep 17 11:36:25 gam0r-PC systemd[1]: run-user-120.mount: Succeeded.
Sep 17 11:36:25 gam0r-PC systemd[1]: user-runtime-dir@120.service: Succeeded.
Sep 17 11:36:25 gam0r-PC systemd[1]: Stopped User Runtime Directory /run/user/120.
Sep 17 11:36:25 gam0r-PC systemd[1]: Removed slice User Slice of UID 120.
Sep 17 11:36:38 gam0r-PC dbus-daemon[809]: [system] Activating via systemd: service name='org.freedesktop.locale1' unit='dbus-org.freedesktop.locale1.service' requested by ':1.74' (uid=1000 pid=1735 comm="flatpak update -y " label="unconfined")
Sep 17 11:36:38 gam0r-PC systemd[1]: Starting Locale Service...
Sep 17 11:36:39 gam0r-PC dbus-daemon[809]: [system] Successfully activated service 'org.freedesktop.locale1'
Sep 17 11:36:39 gam0r-PC systemd[1]: Started Locale Service.
Sep 17 11:36:39 gam0r-PC dbus-daemon[809]: [system] Activating via systemd: service name='org.freedesktop.Flatpak.SystemHelper' unit='flatpak-system-helper.service' requested by ':1.74' (uid=1000 pid=1735 comm="flatpak update -y " label="unconfined")
Sep 17 11:36:39 gam0r-PC systemd[1]: Starting flatpak system helper...
Sep 17 11:36:39 gam0r-PC dbus-daemon[809]: [system] Successfully activated service 'org.freedesktop.Flatpak.SystemHelper'
Sep 17 11:36:39 gam0r-PC systemd[1]: Started flatpak system helper.
Sep 17 11:36:40 gam0r-PC flatpak[1735]: libostree pull from 'flathub' for runtime/org.freedesktop.Platform.GL.default/x86_64/20.08 complete#012security: GPG: summary+commit http: TLS#012non-delta: meta: 2 content: 0#012transfer: secs: 1 size: 1.6 kB
Sep 17 11:36:48 gam0r-PC wpa_supplicant[850]: wlp2s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-56 noise=9999 txrate=65000
Sep 17 11:36:52 gam0r-PC flatpak[1735]: libostree pull from 'flathub' for runtime/org.freedesktop.Platform.GL.default/x86_64/20.08 complete#012security: GPG: summary+commit http: TLS#012delta: parts: 1 loose: 15#012transfer: secs: 11 size: 42.1 MB
Sep 17 11:36:52 gam0r-PC flatpak[1735]: /var/tmp/flatpak-cache-NW71Q0/org.freedesktop.Platform.GL.default-YV71Q0/repo-1eJtAE: Pulled runtime/org.freedesktop.Platform.GL.default/x86_64/20.08 from flathub
Sep 17 11:36:52 gam0r-PC systemd[1]: var-tmp-flatpak\x2dcache\x2dNW71Q0-org.freedesktop.Platform.GL.default\x2dYV71Q0.mount: Succeeded.
Sep 17 11:36:52 gam0r-PC systemd[1219]: var-tmp-flatpak\x2dcache\x2dNW71Q0-org.freedesktop.Platform.GL.default\x2dYV71Q0.mount: Succeeded.
Sep 17 11:36:53 gam0r-PC flatpak-system-helper[1782]: system: Pulled runtime/org.freedesktop.Platform.GL.default/x86_64/20.08 from /var/lib/flatpak/repo/tmp/flatpak-cache-VN31Q0/repo-1eJtAE
Sep 17 11:36:53 gam0r-PC flatpak-system-helper[1782]: system: Installed runtime/org.freedesktop.Platform.GL.default/x86_64/20.08 from flathub
Sep 17 11:36:54 gam0r-PC flatpak[1735]: libostree pull from 'flathub' for runtime/org.freedesktop.Platform.Locale/x86_64/20.08 complete#012security: GPG: summary+commit http: TLS#012non-delta: meta: 2 content: 0#012transfer: secs: 1 size: 1.5 kB
Sep 17 11:36:57 gam0r-PC flatpak[1735]: libostree pull from 'flathub' for runtime/org.freedesktop.Platform.Locale/x86_64/20.08 complete#012security: GPG: summary+commit http: TLS#012non-delta: meta: 25 content: 56#012transfer: secs: 2 size: 1.8 MB
Sep 17 11:36:57 gam0r-PC flatpak[1735]: /var/tmp/flatpak-cache-NW71Q0/org.freedesktop.Platform.Locale-99W1Q0/repo-xboQIN: Pulled runtime/org.freedesktop.Platform.Locale/x86_64/20.08 from flathub
Sep 17 11:36:57 gam0r-PC systemd[1]: var-tmp-flatpak\x2dcache\x2dNW71Q0-org.freedesktop.Platform.Locale\x2d99W1Q0.mount: Succeeded.
Sep 17 11:36:57 gam0r-PC systemd[1219]: var-tmp-flatpak\x2dcache\x2dNW71Q0-org.freedesktop.Platform.Locale\x2d99W1Q0.mount: Succeeded.
Sep 17 11:36:57 gam0r-PC flatpak-system-helper[1782]: system: Pulled runtime/org.freedesktop.Platform.Locale/x86_64/20.08 from /var/lib/flatpak/repo/tmp/flatpak-cache-63I1Q0/repo-xboQIN
Sep 17 11:36:57 gam0r-PC flatpak-system-helper[1782]: system: Installed runtime/org.freedesktop.Platform.Locale/x86_64/20.08 from flathub
Sep 17 11:36:59 gam0r-PC flatpak[1735]: libostree pull from 'flathub' for runtime/org.freedesktop.Platform.VAAPI.Intel/x86_64/20.08 complete#012security: GPG: summary+commit http: TLS#012non-delta: meta: 2 content: 0#012transfer: secs: 1 size: 1.6 kB
Sep 17 11:37:04 gam0r-PC flatpak[1735]: libostree pull from 'flathub' for runtime/org.freedesktop.Platform.VAAPI.Intel/x86_64/20.08 complete#012security: GPG: summary+commit http: TLS#012delta: parts: 1 loose: 3#012transfer: secs: 5 size: 11.1 MB
Sep 17 11:37:04 gam0r-PC flatpak[1735]: /var/tmp/flatpak-cache-NW71Q0/org.freedesktop.Platform.VAAPI.Intel-YFHCR0/repo-v9aug5: Pulled runtime/org.freedesktop.Platform.VAAPI.Intel/x86_64/20.08 from flathub
Sep 17 11:37:04 gam0r-PC systemd[1]: var-tmp-flatpak\x2dcache\x2dNW71Q0-org.freedesktop.Platform.VAAPI.Intel\x2dYFHCR0.mount: Succeeded.
Sep 17 11:37:04 gam0r-PC systemd[1219]: var-tmp-flatpak\x2dcache\x2dNW71Q0-org.freedesktop.Platform.VAAPI.Intel\x2dYFHCR0.mount: Succeeded.
Sep 17 11:37:04 gam0r-PC flatpak-system-helper[1782]: system: Pulled runtime/org.freedesktop.Platform.VAAPI.Intel/x86_64/20.08 from /var/lib/flatpak/repo/tmp/flatpak-cache-UZZBR0/repo-v9aug5
Sep 17 11:37:04 gam0r-PC flatpak-system-helper[1782]: system: Installed runtime/org.freedesktop.Platform.VAAPI.Intel/x86_64/20.08 from flathub
Sep 17 11:37:06 gam0r-PC flatpak[1735]: libostree pull from 'flathub' for runtime/org.freedesktop.Platform/x86_64/20.08 complete#012security: GPG: summary+commit http: TLS#012non-delta: meta: 2 content: 0#012transfer: secs: 1 size: 3.3 kB
Sep 17 11:37:09 gam0r-PC systemd[1]: systemd-localed.service: Succeeded.
Sep 17 11:37:34 gam0r-PC rtkit-daemon[1059]: Supervising 3 threads of 1 processes of 1 users.
Sep 17 11:37:34 gam0r-PC rtkit-daemon[1059]: message repeated 3 times: [ Supervising 3 threads of 1 processes of 1 users.]
Sep 17 11:37:34 gam0r-PC rtkit-daemon[1059]: Successfully made thread 2129 of process 2040 owned by '1000' RT at priority 10.
Sep 17 11:37:34 gam0r-PC rtkit-daemon[1059]: Supervising 4 threads of 2 processes of 1 users.
Sep 17 11:37:39 gam0r-PC rtkit-daemon[1059]: message repeated 14 times: [ Supervising 4 threads of 2 processes of 1 users.]
Sep 17 11:37:49 gam0r-PC flatpak[1735]: libostree pull from 'flathub' for runtime/org.freedesktop.Platform/x86_64/20.08 complete#012security: GPG: summary+commit http: TLS#012delta: parts: 8 loose: 63#012transfer: secs: 42 size: 205.1 MB
Sep 17 11:37:49 gam0r-PC flatpak[1735]: /var/tmp/flatpak-cache-NW71Q0/org.freedesktop.Platform-2CGIR0/repo-OZcC9z: Pulled runtime/org.freedesktop.Platform/x86_64/20.08 from flathub
Sep 17 11:37:49 gam0r-PC systemd[1219]: var-tmp-flatpak\x2dcache\x2dNW71Q0-org.freedesktop.Platform\x2d2CGIR0.mount: Succeeded.
Sep 17 11:37:49 gam0r-PC systemd[1]: var-tmp-flatpak\x2dcache\x2dNW71Q0-org.freedesktop.Platform\x2d2CGIR0.mount: Succeeded.
Sep 17 11:37:51 gam0r-PC flatpak-system-helper[1782]: system: Pulled runtime/org.freedesktop.Platform/x86_64/20.08 from /var/lib/flatpak/repo/tmp/flatpak-cache-8JPKR0/repo-OZcC9z
Sep 17 11:37:51 gam0r-PC flatpak-system-helper[1782]: system: Installed runtime/org.freedesktop.Platform/x86_64/20.08 from flathub
Sep 17 11:37:53 gam0r-PC flatpak[1735]: libostree pull from 'flathub' for app/com.getpostman.Postman/x86_64/stable complete#012security: GPG: summary+commit http: TLS#012non-delta: meta: 2 content: 0#012transfer: secs: 1 size: 2.2 kB
Sep 17 11:37:55 gam0r-PC flatpak[1735]: libostree pull from 'flathub' for app/com.getpostman.Postman/x86_64/stable complete#012security: GPG: summary+commit http: TLS#012delta: parts: 1 loose: 1#012transfer: secs: 1 size: 220.7 kB
Sep 17 11:38:16 gam0r-PC flatpak[1735]: /var/tmp/flatpak-cache-NW71Q0/com.getpostman.Postman-GTVIR0/repo-0GOCDK: Pulled app/com.getpostman.Postman/x86_64/stable from flathub
Sep 17 11:38:16 gam0r-PC systemd[1219]: var-tmp-flatpak\x2dcache\x2dNW71Q0-com.getpostman.Postman\x2dGTVIR0.mount: Succeeded.
Sep 17 11:38:16 gam0r-PC systemd[1]: var-tmp-flatpak\x2dcache\x2dNW71Q0-com.getpostman.Postman\x2dGTVIR0.mount: Succeeded.
Sep 17 11:38:17 gam0r-PC kernel: [  165.643316] mce: CPU0: Core temperature above threshold, cpu clock throttled (total events = 1)
Sep 17 11:38:17 gam0r-PC kernel: [  165.643317] mce: CPU4: Core temperature above threshold, cpu clock throttled (total events = 1)
Sep 17 11:38:17 gam0r-PC kernel: [  165.643318] mce: CPU0: Package temperature above threshold, cpu clock throttled (total events = 1)
Sep 17 11:38:17 gam0r-PC kernel: [  165.643319] mce: CPU4: Package temperature above threshold, cpu clock throttled (total events = 1)
Sep 17 11:38:17 gam0r-PC kernel: [  165.643366] mce: CPU1: Package temperature above threshold, cpu clock throttled (total events = 1)
Sep 17 11:38:17 gam0r-PC kernel: [  165.643367] mce: CPU5: Package temperature above threshold, cpu clock throttled (total events = 1)
Sep 17 11:38:17 gam0r-PC kernel: [  165.643368] mce: CPU3: Package temperature above threshold, cpu clock throttled (total events = 1)
Sep 17 11:38:17 gam0r-PC kernel: [  165.643368] mce: CPU7: Package temperature above threshold, cpu clock throttled (total events = 1)
Sep 17 11:38:17 gam0r-PC kernel: [  165.643369] mce: CPU2: Package temperature above threshold, cpu clock throttled (total events = 1)
Sep 17 11:38:17 gam0r-PC kernel: [  165.643370] mce: CPU6: Package temperature above threshold, cpu clock throttled (total events = 1)
Sep 17 11:38:17 gam0r-PC kernel: [  165.644319] mce: CPU0: Core temperature/speed normal
Sep 17 11:38:17 gam0r-PC kernel: [  165.644320] mce: CPU4: Core temperature/speed normal
Sep 17 11:38:17 gam0r-PC kernel: [  165.644321] mce: CPU0: Package temperature/speed normal
Sep 17 11:38:17 gam0r-PC kernel: [  165.644321] mce: CPU4: Package temperature/speed normal
Sep 17 11:38:17 gam0r-PC kernel: [  165.644354] mce: CPU1: Package temperature/speed normal
Sep 17 11:38:17 gam0r-PC kernel: [  165.644355] mce: CPU5: Package temperature/speed normal
Sep 17 11:38:17 gam0r-PC kernel: [  165.644356] mce: CPU6: Package temperature/speed normal
Sep 17 11:38:17 gam0r-PC kernel: [  165.644356] mce: CPU2: Package temperature/speed normal
Sep 17 11:38:17 gam0r-PC kernel: [  165.644357] mce: CPU7: Package temperature/speed normal
Sep 17 11:38:17 gam0r-PC kernel: [  165.644358] mce: CPU3: Package temperature/speed normal
Sep 17 11:38:18 gam0r-PC flatpak-system-helper[1782]: system: Pulled app/com.getpostman.Postman/x86_64/stable from /var/lib/flatpak/repo/tmp/flatpak-cache-DORIR0/repo-0GOCDK
Sep 17 11:38:18 gam0r-PC flatpak-system-helper[2621]: tar: Postman/Postman: Cannot change ownership to uid 999, gid 999: Operation not permitted
Sep 17 11:38:21 gam0r-PC flatpak-system-helper[2621]: tar: Postman/app: Cannot change ownership to uid 999, gid 999: Operation not permitted
Sep 17 11:38:21 gam0r-PC flatpak-system-helper[2621]: tar: Postman: Cannot change ownership to uid 999, gid 999: Operation not permitted
Sep 17 11:38:21 gam0r-PC flatpak-system-helper[2621]: tar: Exiting with failure status due to previous errors
Sep 17 11:38:22 gam0r-PC flatpak-system-helper[1782]: system: Updated app/com.getpostman.Postman/x86_64/stable from flathub
Sep 17 11:38:26 gam0r-PC flatpak[1735]: libostree pull from 'flathub' for appstream2/x86_64 complete#012security: GPG: summary+commit http: TLS#012non-delta: meta: 6 content: 7#012transfer: secs: 2 size: 3.3 MB
Sep 17 11:38:26 gam0r-PC flatpak[1735]: /var/tmp/flatpak-cache-NW71Q0/repo-8Wynpc: Pulled appstream2/x86_64 from flathub
Sep 17 11:38:26 gam0r-PC flatpak-system-helper[1782]: system: Pulled appstream2/x86_64 from /var/tmp/flatpak-cache-NW71Q0/repo-8Wynpc
Sep 17 11:39:15 gam0r-PC dbus-daemon[1257]: [session uid=1000 pid=1257] Activating via systemd: service name='org.gnome.Terminal' unit='gnome-terminal-server.service' requested by ':1.84' (uid=1000 pid=2733 comm="/usr/bin/gnome-terminal.real " label="unconfined")
Sep 17 11:39:15 gam0r-PC systemd[1219]: Created slice apps.slice.
Sep 17 11:39:15 gam0r-PC systemd[1219]: Created slice apps-org.gnome.Terminal.slice.
Sep 17 11:39:15 gam0r-PC systemd[1219]: Starting GNOME Terminal Server...
Sep 17 11:39:15 gam0r-PC dbus-daemon[1257]: [session uid=1000 pid=1257] Successfully activated service 'org.gnome.Terminal'
Sep 17 11:39:15 gam0r-PC systemd[1219]: Started GNOME Terminal Server.
Sep 17 11:39:16 gam0r-PC systemd[1219]: Started VTE child process 2744 launched by gnome-terminal-server process 2736.
Sep 17 11:40:48 gam0r-PC anacron[803]: Job `cron.daily' started
Sep 17 11:40:48 gam0r-PC anacron[3204]: Updated timestamp for job `cron.daily' to 2020-09-17
Sep 17 11:40:48 gam0r-PC cracklib: no dictionary update necessary.
Sep 17 11:40:48 gam0r-PC systemd[1219]: Started VTE child process 3372 launched by gnome-terminal-server process 2736.
Sep 17 11:41:04 gam0r-PC anacron[803]: Job `cron.daily' terminated
Sep 17 11:41:04 gam0r-PC anacron[803]: Normal exit (1 job run)
Sep 17 11:41:04 gam0r-PC systemd[1]: anacron.service: Succeeded.
Sep 17 11:41:42 gam0r-PC systemd[1219]: Started VTE child process 3423 launched by gnome-terminal-server process 2736.
Sep 17 11:42:02 gam0r-PC rtkit-daemon[1059]: Supervising 4 threads of 2 processes of 1 users.
Sep 17 11:42:02 gam0r-PC rtkit-daemon[1059]: message repeated 3 times: [ Supervising 4 threads of 2 processes of 1 users.]
Sep 17 11:42:02 gam0r-PC rtkit-daemon[1059]: Successfully made thread 3455 of process 2267 owned by '1000' RT at priority 10.
Sep 17 11:42:02 gam0r-PC rtkit-daemon[1059]: Supervising 5 threads of 3 processes of 1 users.
Sep 17 11:44:56 gam0r-PC rtkit-daemon[1059]: Supervising 5 threads of 3 processes of 1 users.
Sep 17 11:44:56 gam0r-PC rtkit-daemon[1059]: Supervising 5 threads of 3 processes of 1 users.
Sep 17 11:45:36 gam0r-PC wpa_supplicant[850]: wlp2s0: WPA: Group rekeying completed with 7c:ff:4d:3d:ee:0f [GTK=CCMP]
Sep 17 11:45:44 gam0r-PC rtkit-daemon[1059]: Supervising 5 threads of 3 processes of 1 users.
Sep 17 11:45:45 gam0r-PC rtkit-daemon[1059]: message repeated 3 times: [ Supervising 5 threads of 3 processes of 1 users.]
Sep 17 11:45:59 gam0r-PC systemd[1]: Starting Message of the Day...
Sep 17 11:45:59 gam0r-PC systemd[1]: motd-news.service: Succeeded.
Sep 17 11:45:59 gam0r-PC systemd[1]: Finished Message of the Day.
Sep 17 11:46:12 gam0r-PC NetworkManager[811]: <info>  [1600335972.7025] manager: NetworkManager state is now CONNECTED_SITE
Sep 17 11:46:12 gam0r-PC dbus-daemon[809]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.13' (uid=0 pid=811 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined")
Sep 17 11:46:12 gam0r-PC systemd[1]: Starting Network Manager Script Dispatcher Service...
Sep 17 11:46:12 gam0r-PC dbus-daemon[809]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Sep 17 11:46:12 gam0r-PC systemd[1]: Started Network Manager Script Dispatcher Service.
Sep 17 11:46:13 gam0r-PC NetworkManager[811]: <info>  [1600335973.0008] manager: NetworkManager state is now CONNECTED_GLOBAL
Sep 17 11:46:23 gam0r-PC systemd[1]: NetworkManager-dispatcher.service: Succeeded.
Sep 17 11:46:39 gam0r-PC dbus-daemon[809]: [system] Activating via systemd: service name='org.freedesktop.PackageKit' unit='packagekit.service' requested by ':1.101' (uid=0 pid=4622 comm="/usr/bin/gdbus call --system --dest org.freedeskto" label="unconfined")
Sep 17 11:46:39 gam0r-PC systemd[1]: Starting PackageKit Daemon...
Sep 17 11:46:39 gam0r-PC PackageKit: daemon start
Sep 17 11:46:39 gam0r-PC dbus-daemon[809]: [system] Successfully activated service 'org.freedesktop.PackageKit'
Sep 17 11:46:39 gam0r-PC systemd[1]: Started PackageKit Daemon.
Sep 17 11:48:26 gam0r-PC systemd[1]: flatpak-system-helper.service: Succeeded.
Sep 17 11:50:50 gam0r-PC systemd[1]: Starting Cleanup of Temporary Directories...
Sep 17 11:50:50 gam0r-PC systemd[1]: systemd-tmpfiles-clean.service: Succeeded.
Sep 17 11:50:50 gam0r-PC systemd[1]: Finished Cleanup of Temporary Directories.
Sep 17 11:51:27 gam0r-PC systemd[1]: Starting Daily apt upgrade and clean activities...
Sep 17 11:51:29 gam0r-PC systemd[1]: apt-daily-upgrade.service: Succeeded.
Sep 17 11:51:29 gam0r-PC systemd[1]: Finished Daily apt upgrade and clean activities.
Sep 17 11:51:44 gam0r-PC PackageKit: daemon quit
Sep 17 11:51:44 gam0r-PC systemd[1]: packagekit.service: Succeeded.
Sep 17 11:55:36 gam0r-PC wpa_supplicant[850]: wlp2s0: WPA: Group rekeying completed with 7c:ff:4d:3d:ee:0f [GTK=CCMP]
Sep 17 11:56:32 gam0r-PC NetworkManager[811]: <info>  [1600336592.7023] manager: NetworkManager state is now CONNECTED_SITE
Sep 17 11:56:32 gam0r-PC dbus-daemon[809]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.13' (uid=0 pid=811 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined")
Sep 17 11:56:32 gam0r-PC systemd[1]: Starting Network Manager Script Dispatcher Service...
Sep 17 11:56:32 gam0r-PC dbus-daemon[809]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Sep 17 11:56:32 gam0r-PC systemd[1]: Started Network Manager Script Dispatcher Service.
Sep 17 11:56:33 gam0r-PC NetworkManager[811]: <info>  [1600336593.1272] manager: NetworkManager state is now CONNECTED_GLOBAL
Sep 17 11:56:43 gam0r-PC systemd[1]: NetworkManager-dispatcher.service: Succeeded.
Sep 17 12:00:01 gam0r-PC CRON[5047]: (root) CMD (timeshift --check --
Sep 17 12:00:01 gam0r-PC crontab[5090]: (root) LIST (root)
Sep 17 12:00:01 gam0r-PC crontab[5091]: (root) LIST (root)
Sep 17 12:05:36 gam0r-PC wpa_supplicant[850]: wlp2s0: WPA: Group rekeying completed with 7c:ff:4d:3d:ee:0f [GTK=CCMP]
Sep 17 12:15:36 gam0r-PC wpa_supplicant[850]: wlp2s0: WPA: Group rekeying completed with 7c:ff:4d:3d:ee:0f [GTK=CCMP]
Sep 17 12:17:01 gam0r-PC CRON[5364]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Sep 17 12:17:40 gam0r-PC rtkit-daemon[1059]: Supervising 5 threads of 3 processes of 1 users.
Sep 17 12:17:40 gam0r-PC rtkit-daemon[1059]: Successfully made thread 5384 of process 1237 owned by '1000' RT at priority 5.
Sep 17 12:17:40 gam0r-PC rtkit-daemon[1059]: Supervising 6 threads of 3 processes of 1 users.
Sep 17 12:17:40 gam0r-PC rtkit-daemon[1059]: Supervising 5 threads of 3 processes of 1 users.
Sep 17 12:17:40 gam0r-PC rtkit-daemon[1059]: Successfully made thread 5385 of process 1237 owned by '1000' RT at priority 5.
Sep 17 12:17:40 gam0r-PC rtkit-daemon[1059]: Supervising 6 threads of 3 processes of 1 users.
Sep 17 13:51:49 gam0r-PC systemd-modules-load[524]: Inserted module 'lp'
Hope it is not too much. I alredy took out my Cronjobs and ~17k lines like

Code: Select all

Sep 17 11:38:21 gam0r-PC flatpak-system-helper[2621]: tar: Postman/app/resources: Cannot change ownership to uid 999, gid 999: Operation not permitted
Might also be interesting:

Code: Select all

Sep 17 11:38:17 gam0r-PC kernel: [  165.643316] mce: CPU0: Core temperature above threshold, cpu clock throttled (total events = 1)
I got to go now, but I can check later if there are many Postman-Logs before the other shutdowns as well.
antikythera
Level 6
Level 6
Posts: 1470
Joined: Thu Jul 02, 2020 12:52 pm
Contact:

Re: Unexpected Shutdowns

Post by antikythera »

There's either a dust clogged heatsink, a dirty or dead fan on your CPU or you need to replace the thermal interface material. Either way, that thermal issue is most likely behind some of the random shutdowns.
Don't take life so seriously, nobody gets out alive anyway!
AMSTRAD CPC6128 - 128KB RAM, 3" Hitachi Floppy Diskette Drive, External Sony Cassette Recorder, Locomotive BASIC 1.1, CTM-644 Monitor
User avatar
SMG
Level 5
Level 5
Posts: 774
Joined: Sun Jul 26, 2020 6:15 pm
Location: USA

Re: Unexpected Shutdowns

Post by SMG »

General guidelines for cpu temps are to keep them below 50C. The numbers you posted are just above that. However, the message that core temp being above threshold and throttling happening seems to indicate there is a spike happening. I just do not know what the threshold value is.

Sep 17 11:38:17 gam0r-PC kernel: [ 165.643317] mce: CPU4: Core temperature above threshold, cpu clock throttled (total events = 1)
Sep 17 11:38:17 gam0r-PC kernel: [ 165.643318] mce: CPU0: Package temperature above threshold, cpu clock throttled (total events = 1)
omg_me wrote:
Thu Sep 17, 2020 1:20 pm
I got to go now, but I can check later if there are many Postman-Logs before the other shutdowns as well.
The Postman references were after the temp messages, BUT they were part of the restart process. Shutdown happened at 11:36. And it appeared to be an orderly shutdown. Then the system restarted and went looking for all your flatpacks.

Sep 17 11:36:25 gam0r-PC systemd[1042]: Reached target Shutdown.
Sep 17 11:36:25 gam0r-PC systemd[1042]: systemd-exit.service: Succeeded.
Sep 17 11:36:25 gam0r-PC systemd[1042]: Finished Exit the Session.
Sep 17 11:36:25 gam0r-PC systemd[1042]: Reached target Exit the Session.

My eyes are starting to go buggy from looking at these logs, so I'm taking a break. I see a lot of references to Wifi and network, but I'm not really seeing anything that is pointing to a "crash" cause. What I see is an orderly shutdown and restart.
LM20.0 Cinnamon
omg_me
Level 1
Level 1
Posts: 21
Joined: Thu Aug 27, 2020 9:16 pm

Re: Unexpected Shutdowns

Post by omg_me »

antikythera wrote:
Thu Sep 17, 2020 1:28 pm
There's either a dust clogged heatsink, a dirty or dead fan on your CPU or you need to replace the thermal interface material. Either way, that thermal issue is most likely behind some of the random shutdowns.
Thanks! Do you know a way of checking if the CPU fans are working correctly? I will also try to clean any clogged fan with some compressed air.
SMG wrote:
Thu Sep 17, 2020 2:59 pm
General guidelines for cpu temps are to keep them below 50C. The numbers you posted are just above that. However, the message that core temp being above threshold and throttling happening seems to indicate there is a spike happening. I just do not know what the threshold value is.

Sep 17 11:38:17 gam0r-PC kernel: [ 165.643317] mce: CPU4: Core temperature above threshold, cpu clock throttled (total events = 1)
Sep 17 11:38:17 gam0r-PC kernel: [ 165.643318] mce: CPU0: Package temperature above threshold, cpu clock throttled (total events = 1)
Oh, I thought that the high and crit values indicated how high the temps can go with no problems. Good to know they should be under 50°C. Here temperature logs around 11:38:17:

Code: Select all

Thu 17 Sep 2020 11:38:01 AM CEST
coretemp-isa-0000
Adapter: ISA adapter
Package id 0:  +43.0°C  (high = +100.0°C, crit = +100.0°C)
Core 0:        +41.0°C  (high = +100.0°C, crit = +100.0°C)
Core 1:        +43.0°C  (high = +100.0°C, crit = +100.0°C)
Core 2:        +40.0°C  (high = +100.0°C, crit = +100.0°C)
Core 3:        +43.0°C  (high = +100.0°C, crit = +100.0°C)

BAT0-acpi-0
Adapter: ACPI interface
in0:           8.41 V  

iwlwifi_1-virtual-0
Adapter: Virtual device
temp1:        +39.0°C  

pch_skylake-virtual-0
Adapter: Virtual device
temp1:        +39.0°C  

acpitz-acpi-0
Adapter: ACPI interface
temp1:        +51.0°C  (crit = +98.0°C)
temp2:        +34.0°C  (crit = +126.0°C)

Thu 17 Sep 2020 11:39:01 AM CEST
coretemp-isa-0000
Adapter: ISA adapter
Package id 0:  +39.0°C  (high = +100.0°C, crit = +100.0°C)
Core 0:        +37.0°C  (high = +100.0°C, crit = +100.0°C)
Core 1:        +39.0°C  (high = +100.0°C, crit = +100.0°C)
Core 2:        +37.0°C  (high = +100.0°C, crit = +100.0°C)
Core 3:        +39.0°C  (high = +100.0°C, crit = +100.0°C)

BAT0-acpi-0
Adapter: ACPI interface
in0:           8.41 V  

iwlwifi_1-virtual-0
Adapter: Virtual device
temp1:        +32.0°C  

pch_skylake-virtual-0
Adapter: Virtual device
temp1:        +35.5°C  

acpitz-acpi-0
Adapter: ACPI interface
temp1:        +40.0°C  (crit = +98.0°C)
temp2:        +35.0°C  (crit = +126.0°C)
They are below 50C, but I can't tell what happened between 11:38:01 and 11:38:17...

What confuses me is that

Code: Select all

Sep 17 11:38:17 gam0r-PC kernel: [  165.643316] mce: CPU0: Core temperature above threshold, cpu clock throttled (total events = 1)
and

Code: Select all

Sep 17 11:38:17 gam0r-PC kernel: [  165.644319] mce: CPU0: Core temperature/speed normal
is logged in the same second. Does the core temperature cool down that quickly?
SMG wrote:
Thu Sep 17, 2020 2:59 pm
omg_me wrote:
Thu Sep 17, 2020 1:20 pm
I got to go now, but I can check later if there are many Postman-Logs before the other shutdowns as well.
The Postman references were after the temp messages, BUT they were part of the restart process. Shutdown happened at 11:36. And it appeared to be an orderly shutdown. Then the system restarted and went looking for all your flatpacks.

Sep 17 11:36:25 gam0r-PC systemd[1042]: Reached target Shutdown.
Sep 17 11:36:25 gam0r-PC systemd[1042]: systemd-exit.service: Succeeded.
Sep 17 11:36:25 gam0r-PC systemd[1042]: Finished Exit the Session.
Sep 17 11:36:25 gam0r-PC systemd[1042]: Reached target Exit the Session.

My eyes are starting to go buggy from looking at these logs, so I'm taking a break. I see a lot of references to Wifi and network, but I'm not really seeing anything that is pointing to a "crash" cause. What I see is an orderly shutdown and restart.
Hm. I think I started my machine shortly before 11:36, because my sensors-cron started recording at
Thu 17 Sep 2020 11:36:01 AM CEST
and then continously logs until
Thu 17 Sep 2020 12:21:01 PM CEST,
which is why I assumed the shutdown to be somewhen between 12:21 and 12:22. First log after that is Thu 17 Sep 2020 01:52:01 PM CEST (which also shows from when to when I'm having lunch :lol:)
antikythera
Level 6
Level 6
Posts: 1470
Joined: Thu Jul 02, 2020 12:52 pm
Contact:

Re: Unexpected Shutdowns

Post by antikythera »

If you don't have hearing problems, you should hear the fan(s) running or at least feel warm air being expelled from the vent(s) on the laptop.
Don't take life so seriously, nobody gets out alive anyway!
AMSTRAD CPC6128 - 128KB RAM, 3" Hitachi Floppy Diskette Drive, External Sony Cassette Recorder, Locomotive BASIC 1.1, CTM-644 Monitor
omg_me
Level 1
Level 1
Posts: 21
Joined: Thu Aug 27, 2020 9:16 pm

Re: Unexpected Shutdowns

Post by omg_me »

I feel so dumb right now :lol: I was only thinking about some fancy command which checks the state of the fans.

But I might need to run some expensive computations, so the CPU has a reason to warm up...
senjoz
Level 3
Level 3
Posts: 149
Joined: Tue Jun 09, 2020 3:55 am

Re: Unexpected Shutdowns

Post by senjoz »

omg_me wrote:
Fri Sep 18, 2020 6:45 am
But I might need to run some expensive computations, so the CPU has a reason to warm up...
For testing the computer under the stress you can open four terminals, one with

Code: Select all

htop
one with

Code: Select all

watch sensors
one with

Code: Select all

watch -n.1 "cat /proc/cpuinfo | grep \"^[c]pu MHz\""
and one with a stress application, for instance

Code: Select all

stress -t 600 -c 4
or 
stress -t 600 -c 8
(600 seconds, 4 or 8 threads). You can install stress application with Synaptic Package Manager.

Observe outputs of sensors and CPU frequency and listen to the cooling fans. If the temperature would become extremely high and the CPU frequency would drop very low, cooling is not optimal for CPU capabilities.

Application stress can also stress memory, I/O and disk. Another similar application, stress-ng, has many additional features.

Regards, Jože
1000
Level 3
Level 3
Posts: 127
Joined: Wed Jul 29, 2020 2:14 am

Re: Unexpected Shutdowns

Post by 1000 »

omg_me much is up to you because only you know when "Unexpected Shutdowns" was.

For example:

Code: Select all

journalctl  | grep "segfault"

Sep 12 18:52:29 gam0r-PC kernel: csd-automount[1363]: segfault at 8 ip 000055f73ad5d430 sp 00007ffeb6c51120 error 4 in csd-automount[55f73ad5b000+5000]
Sep 12 19:48:03 gam0r-PC kernel: csd-automount[1342]: segfault at 8 ip 000055b0b755f430 sp 00007ffe24d2f460 error 4 in csd-automount[55b0b755d000+5000]
Recently you showed a log above, but it's not complete, it was only from one day.
This is from other day, so I can't check for you.
For example my have 328 570 lines.

Code: Select all

$ journalctl  | wc -l
328570
However ...
1. If you read about journalctl, you can open part log with date

Code: Select all

sudo journalctl -S "2020-09-12 18:50:00" -U "2020-09-12 18:58:00"
and
- if you see something like this
-- Reboot --
lip 31 14:47:25 user kernel: microcode: microcode updated early to revision 0xdc, date = 2020-04-27
lip 31 14:47:25 user kernel: Linux version 5.4.0-42-generic (buildd@lgw01-amd64-038) (gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)) #46-Ubu>
lip 31 14:47:25 user kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=3763a969-08c3-4ac6-af04-a5159c3d18b3 ro qu>
And if you remember "Unexpected Shutdowns" at this time. This could be place where is the cause.
The error should be visible above " -- Reboot -- ".
- but if can not find and you don't remember, it means it's not the problem.


SMG above is right that it is something other.
Because most users with this error complain about problems mounting usb, for example viewtopic.php?p=1881202#p1881202

I have an idea.
Check the Bios log if it exists.
If the processor was overheated and the BIOS shut down the computer, there should be information there as well.
Especially if it's a hardware problem.

I think how can you still help find this situation in the log.

Code: Select all

last | head -n 20
Command "last" will show last logged user, that is, there is computer boot time.
Similar way I can find for example

Code: Select all

journalctl  | grep "Command line: BOOT_IMAGE" | tail
Now if you remember when last "Unexpected Shutdown" was, then you can check log by time.
Anyway if last "Unexpected Shutdown" was half hour ago, you also know the time
and you can check the log for the last hour.
Info: If the error exists it should be visible before booting the computer.

Similar way you can check time and how many times you get

Code: Select all

journalctl  | grep "Core temperature above threshold"
If you want send the entire log

Code: Select all

journalctl > File.1.log
The file should be in your home directory ( /home/your_user_name/File.1.log )
- The log may include your username and sometimes your IP address. You can find and delete it if you want.
Then save the file to the archive, for example .zip
and add on the forum as an attachment.

Other way

Code: Select all

journalctl  | xz -c > File.1.log.xz
This command will pack log to File.1.log.xz archive.

To find "Unexpected Shutdowns" we need to know when they were.
Of course, you don't need to send the entire log.
You can only send one day when it was.

Some time ago I had a similar problem and journalctl should also log
system.journal corrupted or uncleanly shut down, renaming and replacing.
This is after "Unexpected Shutdown" and after next boot systemd-journald trying fix log.
but I can not find this in journalctl.
This is only in dmesg log.
This command show list last dmesg logs

Code: Select all

ls -l /var/log/dmesg*
My log has been removed long time ago.
You can open all and see them all at once :mrgreen:

Code: Select all

zcat -f /var/log/dmesg* 
Time is counted a little differently, because from the start of the computer.

If we assume it's temperature fault.
And nowhere will there be an error about it.
It's a good idea to monitor the temperature.
I don't know a program that logs and shows warnings.
I heard about Netdata but I don't used, so I don't know how configure to log temperature.
Most users like I, have installed Conky https://en.wikipedia.org/wiki/Conky_%28software%29
or have "system monitor" / "sensor monitor" on the taskbar ( I can not similar inside Cinnamon )
and they watch the temperature change.

Good luck.

Edited about "-- Reboot --"
User avatar
SMG
Level 5
Level 5
Posts: 774
Joined: Sun Jul 26, 2020 6:15 pm
Location: USA

Re: Unexpected Shutdowns

Post by SMG »

omg_me wrote:
Fri Sep 18, 2020 3:03 am
Oh, I thought that the high and crit values indicated how high the temps can go with no problems. Good to know they should be under 50°C.
How high they can go for short periods of time is different from how high you would want them to be on a sustained basis. The 50C number I mentioned is a sustained basis temperature. The high and critically high should be well above where you would normally run. A computer with a dirty or poorly running fan is likely to run sustained temperatures higher than a computer with a brand new fan.
omg_me wrote:
Fri Sep 18, 2020 3:03 am
Here temperature logs around 11:38:17:
acpitz-acpi-0
Adapter: ACPI interface
temp1: +51.0°C (crit = +98.0°C)
temp2: +34.0°C (crit = +126.0°C)
Odd that the critical temp for temp2 is higher than temp1's critical temperature yet your temp1 is much hotter than temp2.
omg_me wrote:
Fri Sep 18, 2020 3:03 am
acpitz-acpi-0
Adapter: ACPI interface
temp1: +40.0°C (crit = +98.0°C)
temp2: +35.0°C (crit = +126.0°C)
It is much cooler just a very short time later, so it appears it is changing that quickly and we may not know how high it really went (if it cools down that fast!). The log file mentioned cpu temps being high, so I'm hypothesizing that is what temp1 is.
LM20.0 Cinnamon
1000
Level 3
Level 3
Posts: 127
Joined: Wed Jul 29, 2020 2:14 am

Re: Unexpected Shutdowns

Post by 1000 »

Only Info:
I installed yesterday netdata from Synaptic package manager.

Code: Select all

sudo systemctl restart netdata

Code: Select all

 sudo  netstat -tulpn
...
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name    
tcp        0      0 127.0.0.1:8125          0.0.0.0:*               LISTEN      5676/netdata        
tcp        0      0 127.0.0.1:19999         0.0.0.0:*               LISTEN      5676/netdata        
udp        0      0 127.0.0.1:8125          0.0.0.0:*                           5676/netdata   
I copied IP with port 127.0.0.1:19999 to web browser and working.
And I see today that it remembers my temperatures from yesterday.
So it can be used for temperature monitoring.

How use:
- On the left side there is a tab "Sensors"
- Shift + mouse wheel you can reduce or enlarge the graph.
- If you hover the cursor over the graph at a specific time, you will see on the left exact temperature.
- On the left with Shift key and mouse, you can check or uncheck a certain temperature.
User avatar
Larry78723
Level 8
Level 8
Posts: 2108
Joined: Wed Jan 09, 2019 7:01 pm
Location: Jasper County, SC, USA

Re: Unexpected Shutdowns

Post by Larry78723 »

Everyone seems focused on temperatures, what if it's something else? Why not use:

Code: Select all

[code]journalctl -b | grep -i "error\|warn\|fail" | tee >(gzip --stdout > journalctl_$USER.gz)
This command will write the current system log problems to the file journalctl_(yourname).gz. The file will be located in your /home/login_name directory

Attach this file to your next reply, please.
Image
antikythera
Level 6
Level 6
Posts: 1470
Joined: Thu Jul 02, 2020 12:52 pm
Contact:

Re: Unexpected Shutdowns

Post by antikythera »

SMG wrote:
Fri Sep 18, 2020 4:09 pm
omg_me wrote:
Fri Sep 18, 2020 3:03 am
Oh, I thought that the high and crit values indicated how high the temps can go with no problems. Good to know they should be under 50°C.
How high they can go for short periods of time is different from how high you would want them to be on a sustained basis. The 50C number I mentioned is a sustained basis temperature. The high and critically high should be well above where you would normally run. A computer with a dirty or poorly running fan is likely to run sustained temperatures higher than a computer with a brand new fan.
omg_me wrote:
Fri Sep 18, 2020 3:03 am
Here temperature logs around 11:38:17:
acpitz-acpi-0
Adapter: ACPI interface
temp1: +51.0°C (crit = +98.0°C)
temp2: +34.0°C (crit = +126.0°C)
Odd that the critical temp for temp2 is higher than temp1's critical temperature yet your temp1 is much hotter than temp2.
omg_me wrote:
Fri Sep 18, 2020 3:03 am
acpitz-acpi-0
Adapter: ACPI interface
temp1: +40.0°C (crit = +98.0°C)
temp2: +35.0°C (crit = +126.0°C)
It is much cooler just a very short time later, so it appears it is changing that quickly and we may not know how high it really went (if it cools down that fast!). The log file mentioned cpu temps being high, so I'm hypothesizing that is what temp1 is.
run the following:

Code: Select all

sudo sensors-detect
Press ENTER all the way to the last decision to accept defaults. It will however prompt you to modify a file at the end. Check the contents first (open it in xed read-only, check for the suggested additions and close it straight after) and if the lines it wants to add are missing, allow the sensors-detect script to add them.
Don't take life so seriously, nobody gets out alive anyway!
AMSTRAD CPC6128 - 128KB RAM, 3" Hitachi Floppy Diskette Drive, External Sony Cassette Recorder, Locomotive BASIC 1.1, CTM-644 Monitor
antikythera
Level 6
Level 6
Posts: 1470
Joined: Thu Jul 02, 2020 12:52 pm
Contact:

Re: Unexpected Shutdowns

Post by antikythera »

Larry78723 wrote:
Sat Sep 19, 2020 11:06 am
Everyone seems focused on temperatures, what if it's something else? Why not use:

Code: Select all

[code]journalctl -b | grep -i "error\|warn\|fail" | tee >(gzip --stdout > journalctl_$USER.gz)
This command will write the current system log problems to the file journalctl_(yourname).gz. The file will be located in your /home/login_name directory

Attach this file to your next reply, please.
The warnings already posted in this thread that stood out like a sore thumb repeatedly were for critical temperatures on processor cores. If your thing turns something else up then great ;)
Don't take life so seriously, nobody gets out alive anyway!
AMSTRAD CPC6128 - 128KB RAM, 3" Hitachi Floppy Diskette Drive, External Sony Cassette Recorder, Locomotive BASIC 1.1, CTM-644 Monitor
Post Reply

Return to “Newbie Questions”