System Crash While Using pi-top

Hey all, I just had my first crash today. I did an update last night, and I’m not sure what happened. I’ll post the log of everything in the few seconds leading up to the crash. I did have it running for nearly 8 hours today while I was working on a project, but idk if this would really be the cause. I am seeing the broken atomic error… What does this mean and is it related?

If anyone can identify why this crash may have occurred based on the syslog, please let me know! Thanks :confused:

Feb 28 13:18:32 raspberrypi pt-firmware-checker[731]: [13:18:32.924793 I] Nothing to wait for - continuing…
Feb 28 13:18:32 raspberrypi pt-device-manager[390]: [13:18:32.986629 I] Recv: REQ_GET_DEVICE_ID - Send: RSP_GET_DEVICE_ID 3
Feb 28 13:18:32 raspberrypi pt-device-manager[390]: [13:18:32.989070 I] Recv: REQ_GET_OLED_SPI_BUS - Send: RSP_GET_OLED_SPI_BUS 1
Feb 28 13:18:33 raspberrypi kernel: [ 14.543304] broken atomic modeset userspace detected, disabling atomic
Feb 28 13:18:33 raspberrypi pt-firmware-checker[731]: [13:18:33.241651 W] pt4_hub - Firmware file ‘/lib/firmware/pi-top/pt4_hub/pt4_hub-v5.3-sch8-release.bin’ schematic version ‘8’ does not match current device ‘9’. Skipping…
Feb 28 13:18:33 raspberrypi pt-firmware-checker[731]: [13:18:33.242159 W] pt4_hub - Firmware file ‘/lib/firmware/pi-top/pt4_hub/pt4_hub-v5.4-sch8-release.bin’ schematic version ‘8’ does not match current device ‘9’. Skipping…
Feb 28 13:18:33 raspberrypi pt-firmware-checker[731]: [13:18:33.242279 I] Latest firmware available is version 5.4
Feb 28 13:18:33 raspberrypi pt-firmware-checker[731]: [13:18:33.242444 I] Running command: /usr/bin/pt-firmware-updater --path /lib/firmware/pi-top/pt4_hub/pt4_hub-v5.4-sch9-release.bin --notify-user pt4_hub
Feb 28 13:18:33 raspberrypi kernel: [ 15.021572] broken atomic modeset userspace detected, disabling atomic
Feb 28 13:18:33 raspberrypi systemd[1]: lightdm.service: Main process exited, code=exited, status=1/FAILURE
Feb 28 13:18:33 raspberrypi systemd[1]: lightdm.service: Failed with result ‘exit-code’.
Feb 28 13:18:33 raspberrypi pt-device-manager[390]: [13:18:33.516310 I] Setting OLED Pi control state to 1
Feb 28 13:18:33 raspberrypi pt-device-manager[390]: [13:18:33.530946 I] Recv: REQ_SET_OLED_CONTROL 1 - Send: RSP_SET_OLED_CONTROL
Feb 28 13:18:33 raspberrypi pt-device-manager[390]: [13:18:33.565210 I] Publishing message: PUB_OLED_CONTROL_CHANGED 1
Feb 28 13:18:33 raspberrypi systemd[1]: lightdm.service: Service RestartSec=100ms expired, scheduling restart.
Feb 28 13:18:33 raspberrypi systemd[1]: lightdm.service: Scheduled restart job, restart counter is at 2.
Feb 28 13:18:33 raspberrypi systemd[1]: Stopped Light Display Manager.
Feb 28 13:18:33 raspberrypi systemd[1]: Starting Light Display Manager…
Feb 28 13:18:33 raspberrypi lightdm[777]: Error getting user list from org.freedesktop.Accounts: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Accounts was not provided by any .service files
Feb 28 13:18:33 raspberrypi systemd[1]: Started Light Display Manager.
Feb 28 13:18:34 raspberrypi kernel: [ 15.530144] Bluetooth: Core ver 2.22
Feb 28 13:18:34 raspberrypi kernel: [ 15.531530] NET: Registered protocol family 31
Feb 28 13:18:34 raspberrypi kernel: [ 15.531541] Bluetooth: HCI device and connection manager initialized
Feb 28 13:18:34 raspberrypi kernel: [ 15.531555] Bluetooth: HCI socket layer initialized
Feb 28 13:18:34 raspberrypi kernel: [ 15.531561] Bluetooth: L2CAP socket layer initialized
Feb 28 13:18:34 raspberrypi kernel: [ 15.531582] Bluetooth: SCO socket layer initialized
Feb 28 13:18:34 raspberrypi kernel: [ 15.543646] Bluetooth: HCI UART driver ver 2.3
Feb 28 13:18:34 raspberrypi kernel: [ 15.543659] Bluetooth: HCI UART protocol H4 registered
Feb 28 13:18:34 raspberrypi kernel: [ 15.545680] Bluetooth: HCI UART protocol Three-wire (H5) registered
Feb 28 13:18:34 raspberrypi kernel: [ 15.549093] Bluetooth: HCI UART protocol Broadcom registered
Feb 28 13:18:34 raspberrypi btuart[379]: bcm43xx_init
Feb 28 13:18:34 raspberrypi btuart[379]: Flash firmware /lib/firmware/brcm/BCM4345C0.hcd
Feb 28 13:18:34 raspberrypi btuart[379]: Set Controller UART speed to 3000000 bit/s
Feb 28 13:18:34 raspberrypi btuart[379]: Device setup complete
Feb 28 13:18:34 raspberrypi systemd[1]: Started Configure Bluetooth Modems connected by UART.
Feb 28 13:18:34 raspberrypi systemd[1]: Reached target Multi-User System.
Feb 28 13:18:34 raspberrypi systemd[1]: Reached target Graphical Interface.
Feb 28 13:18:34 raspberrypi systemd[1]: Starting Update UTMP about System Runlevel Changes…
Feb 28 13:18:34 raspberrypi systemd[1]: Starting Load/Save RF Kill Switch Status…
Feb 28 13:18:34 raspberrypi pt-device-manager[390]: [13:18:34.083663 I] Recv: REQ_GET_DEVICE_ID - Send: RSP_GET_DEVICE_ID 3
Feb 28 13:18:34 raspberrypi systemd[1]: Started Load/Save RF Kill Switch Status.
Feb 28 13:18:34 raspberrypi pt-sys-oled[726]: [13:18:34.085857 I] Not played boot animation this session
Feb 28 13:18:34 raspberrypi pt-sys-oled[726]: [13:18:34.086022 I] Starting startup animation
Feb 28 13:18:34 raspberrypi /usr/bin/pt-firmware-updater[769]: Logger created.
Feb 28 13:18:34 raspberrypi systemd[1]: Starting Bluetooth service…
Feb 28 13:18:34 raspberrypi systemd[1]: Created slice system-bthelper.slice.
Feb 28 13:18:34 raspberrypi systemd[1]: systemd-update-utmp-runlevel.service: Succeeded.
Feb 28 13:18:34 raspberrypi systemd[1]: Started Update UTMP about System Runlevel Changes.
Feb 28 13:18:34 raspberrypi bluetoothd[794]: Bluetooth daemon 5.50
Feb 28 13:18:34 raspberrypi systemd[1]: Started Bluetooth service.
Feb 28 13:18:34 raspberrypi systemd[1]: Reached target Bluetooth.
Feb 28 13:18:34 raspberrypi systemd[1]: Started Raspberry Pi bluetooth helper.
Feb 28 13:18:34 raspberrypi systemd[1]: Startup finished in 3.527s (kernel) + 12.157s (userspace) = 15.685s.
Feb 28 13:18:34 raspberrypi bluetoothd[794]: Starting SDP server
Feb 28 13:18:34 raspberrypi bthelper[807]: Can’t init device hci0: Operation not possible due to RF-kill (132)
Feb 28 13:18:34 raspberrypi systemd[1]: bthelper@hci0.service: Main process exited, code=exited, status=1/FAILURE
Feb 28 13:18:34 raspberrypi systemd[1]: bthelper@hci0.service: Failed with result ‘exit-code’.
Feb 28 13:18:34 raspberrypi kernel: [ 15.706521] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Feb 28 13:18:34 raspberrypi kernel: [ 15.706531] Bluetooth: BNEP filters: protocol multicast
Feb 28 13:18:34 raspberrypi kernel: [ 15.706544] Bluetooth: BNEP socket layer initialized
Feb 28 13:18:34 raspberrypi bluetoothd[794]: Bluetooth management interface 1.18 initialized
Feb 28 13:18:34 raspberrypi dbus-daemon[376]: [system] Activating via systemd: service name=‘org.freedesktop.hostname1’ unit=‘dbus-org.freedesktop.hostname1.service’ requested by ‘:1.20’ (uid=0 pid=794 comm="/usr/lib/bluetooth/bluetoothd$
Feb 28 13:18:34 raspberrypi bluetoothd[794]: Sap driver initialization failed.
Feb 28 13:18:34 raspberrypi bluetoothd[794]: sap-server: Operation not permitted (1)
Feb 28 13:18:34 raspberrypi bluetoothd[794]: Failed to set mode: Blocked through rfkill (0x12)
Feb 28 13:18:34 raspberrypi systemd[1]: Starting Hostname Service…
Feb 28 13:18:34 raspberrypi dbus-daemon[376]: [system] Successfully activated service ‘org.freedesktop.hostname1’
Feb 28 13:18:34 raspberrypi systemd[1]: Started Hostname Service.
Feb 28 13:18:34 raspberrypi systemd[1]: Created slice User Slice of UID 1000.
Feb 28 13:18:34 raspberrypi systemd[1]: Starting User Runtime Directory /run/user/1000…
Feb 28 13:18:34 raspberrypi systemd[1]: Started User Runtime Directory /run/user/1000.
Feb 28 13:18:34 raspberrypi systemd[1]: Starting User Manager for UID 1000…
Feb 28 13:18:34 raspberrypi kernel: [ 15.843307] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Feb 28 13:18:34 raspberrypi dhcpcd[467]: wlan0: carrier acquired
Feb 28 13:18:34 raspberrypi dhcpcd[467]: wlan0: connected to Access Point `It hurts when IP’
Feb 28 13:18:34 raspberrypi dhcpcd[467]: DUID 00:01:00:01:27:5a:51:4a:dc:a6:32:ce:43:36
Feb 28 13:18:34 raspberrypi dhcpcd[467]: wlan0: IAID 32:ce:43:36
Feb 28 13:18:34 raspberrypi dhcpcd[467]: wlan0: adding address fe80::97e1:f891:5b5b:e551
Feb 28 13:18:34 raspberrypi avahi-daemon[385]: Joining mDNS multicast group on interface wlan0.IPv6 with address fe80::97e1:f891:5b5b:e551.
Feb 28 13:18:34 raspberrypi avahi-daemon[385]: New relevant interface wlan0.IPv6 for mDNS.
Feb 28 13:18:34 raspberrypi avahi-daemon[385]: Registering new address record for fe80::97e1:f891:5b5b:e551 on wlan0.*.
Feb 28 13:18:34 raspberrypi dhcpcd[467]: wlan0: soliciting an IPv6 router
Feb 28 13:18:34 raspberrypi /usr/bin/pt-firmware-updater[769]: pt4_hub - Firmware Versions: Current = 5.4, Candidate = 5.4
Feb 28 13:18:34 raspberrypi /usr/bin/pt-firmware-updater[769]: pt4_hub - Candidate firmware version matches current firmware version. Checking build metadata to determine if candidate is a newer build.
Feb 28 13:18:34 raspberrypi /usr/bin/pt-firmware-updater[769]: pt4_hub - Candidate firmware is not newer. Skipping…
Feb 28 13:18:34 raspberrypi /usr/bin/pt-firmware-updater[769]: Skipping update: no valid candidate firmware
Feb 28 13:18:34 raspberrypi /usr/bin/pt-firmware-updater[769]: /lib/firmware/pi-top/pt4_hub/pt4_hub-v5.4-sch9-release.bin is not a valid candidate firmware file
Feb 28 13:18:34 raspberrypi kernel: [ 16.005575] broken atomic modeset userspace detected, disabling atomic
Feb 28 13:18:34 raspberrypi dhcpcd[467]: wlan0: rebinding lease of 192.168.1.15
Feb 28 13:18:34 raspberrypi dhcpcd[467]: wlan0: probing address 192.168.1.15/24
Feb 28 13:18:34 raspberrypi pt-firmware-checker[731]: [13:18:34.623357 E] Command ‘[’/usr/bin/pt-firmware-updater’, ‘–path’, ‘/lib/firmware/pi-top/pt4_hub/pt4_hub-v5.4-sch9-release.bin’, ‘–notify-user’, ‘pt4_hub’]’ returned non-zero ex$
Feb 28 13:18:34 raspberrypi pt-firmware-checker[731]: [13:18:34.623565 W] pt4_hub error: Command ‘[’/usr/bin/pt-firmware-updater’, ‘–path’, ‘/lib/firmware/pi-top/pt4_hub/pt4_hub-v5.4-sch9-release.bin’, ‘–notify-user’, ‘pt4_hub’]’ retur$
Feb 28 13:18:34 raspberrypi systemd[817]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
Feb 28 13:18:34 raspberrypi systemd[817]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers).
Feb 28 13:18:34 raspberrypi systemd[817]: Listening on GnuPG cryptographic agent and passphrase cache.
Feb 28 13:18:34 raspberrypi systemd[817]: Listening on Sound System.
Feb 28 13:18:34 raspberrypi systemd[817]: Listening on GnuPG network certificate management daemon.
Feb 28 13:18:34 raspberrypi systemd[817]: Reached target Paths.
Feb 28 13:18:34 raspberrypi systemd[817]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
Feb 28 13:18:34 raspberrypi systemd[817]: Starting D-Bus User Message Bus Socket.
Feb 28 13:18:34 raspberrypi systemd[817]: Reached target Timers.
Feb 28 13:18:34 raspberrypi systemd[817]: Listening on D-Bus User Message Bus Socket.
Feb 28 13:18:34 raspberrypi systemd[817]: Reached target Sockets.
Feb 28 13:18:34 raspberrypi systemd[817]: Reached target Basic System.
Feb 28 13:18:34 raspberrypi systemd[1]: Started User Manager for UID 1000.
Feb 28 13:18:34 raspberrypi systemd[1]: Started Session 1 of user pi.
Feb 28 13:18:34 raspberrypi systemd[817]: Reached target Default.
Feb 28 13:18:34 raspberrypi systemd[817]: Startup finished in 343ms.
Feb 28 13:18:35 raspberrypi kernel: [ 16.561865] broken atomic modeset userspace detected, disabling atomic
Feb 28 13:18:35 raspberrypi systemd[1]: lightdm.service: Main process exited, code=exited, status=1/FAILURE
Feb 28 13:18:35 raspberrypi systemd[1]: lightdm.service: Failed with result ‘exit-code’.
Feb 28 13:18:35 raspberrypi systemd[1]: lightdm.service: Service RestartSec=100ms expired, scheduling restart.
Feb 28 13:18:35 raspberrypi systemd[1]: lightdm.service: Scheduled restart job, restart counter is at 3.
Feb 28 13:18:35 raspberrypi systemd[1]: Stopped Light Display Manager.
Feb 28 13:18:35 raspberrypi systemd[1]: Starting Light Display Manager…
Feb 28 13:18:35 raspberrypi lightdm[845]: Error getting user list from org.freedesktop.Accounts: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Accounts was not provided by any .service files
Feb 28 13:18:35 raspberrypi systemd[1]: Started Light Display Manager.
Feb 28 13:18:35 raspberrypi kernel: [ 17.430356] broken atomic modeset userspace detected, disabling atomic
Feb 28 13:18:36 raspberrypi kernel: [ 17.901882] broken atomic modeset userspace detected, disabling atomic
Feb 28 13:18:36 raspberrypi systemd[1]: lightdm.service: Main process exited, code=exited, status=1/FAILURE
Feb 28 13:18:36 raspberrypi systemd[1]: lightdm.service: Failed with result ‘exit-code’.
Feb 28 13:18:36 raspberrypi systemd[1]: lightdm.service: Service RestartSec=100ms expired, scheduling restart.
Feb 28 13:18:36 raspberrypi systemd[1]: lightdm.service: Scheduled restart job, restart counter is at 4.
Feb 28 13:18:36 raspberrypi systemd[1]: Stopped Light Display Manager.
Feb 28 13:18:36 raspberrypi systemd[1]: Starting Light Display Manager…
Feb 28 13:18:36 raspberrypi lightdm[854]: Error getting user list from org.freedesktop.Accounts: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Accounts was not provided by any .service files
Feb 28 13:18:36 raspberrypi systemd[1]: Started Light Display Manager.
Feb 28 13:18:37 raspberrypi kernel: [ 18.769832] broken atomic modeset userspace detected, disabling atomic
Feb 28 13:18:37 raspberrypi kernel: [ 19.246547] broken atomic modeset userspace detected, disabling atomic
Feb 28 13:18:37 raspberrypi systemd[1]: lightdm.service: Main process exited, code=exited, status=1/FAILURE
Feb 28 13:18:37 raspberrypi systemd[1]: lightdm.service: Failed with result ‘exit-code’.
Feb 28 13:18:38 raspberrypi systemd[1]: lightdm.service: Service RestartSec=100ms expired, scheduling restart.
Feb 28 13:18:38 raspberrypi systemd[1]: lightdm.service: Scheduled restart job, restart counter is at 5.
Feb 28 13:18:38 raspberrypi systemd[1]: Stopped Light Display Manager.
Feb 28 13:18:38 raspberrypi systemd[1]: lightdm.service: Start request repeated too quickly.
Feb 28 13:18:38 raspberrypi systemd[1]: lightdm.service: Failed with result ‘exit-code’.
Feb 28 13:18:38 raspberrypi systemd[1]: Failed to start Light Display Manager.
Feb 28 13:18:38 raspberrypi systemd[1]: lightdm.service: Triggering OnFailure= dependencies.
Feb 28 13:18:38 raspberrypi systemd[1]: Starting Terminate Plymouth Boot Screen…
Feb 28 13:18:38 raspberrypi systemd[1]: plymouth-quit.service: Succeeded.
Feb 28 13:18:38 raspberrypi systemd[1]: Started Terminate Plymouth Boot Screen.
Feb 28 13:18:39 raspberrypi systemd[1]: systemd-rfkill.service: Succeeded.
Feb 28 13:18:39 raspberrypi pt-device-manager[390]: [13:18:39.159078 I] Setting OLED Pi control state to 1
Feb 28 13:18:39 raspberrypi pt-device-manager[390]: [13:18:39.173052 I] Recv: REQ_SET_OLED_CONTROL 1 - Send: RSP_SET_OLED_CONTROL
Feb 28 13:18:39 raspberrypi dhcpcd[467]: wlan0: leased 192.168.1.15 for 86400 seconds
Feb 28 13:18:39 raspberrypi avahi-daemon[385]: Joining mDNS multicast group on interface wlan0.IPv4 with address 192.168.1.15.
Feb 28 13:18:39 raspberrypi avahi-daemon[385]: New relevant interface wlan0.IPv4 for mDNS.
Feb 28 13:18:39 raspberrypi avahi-daemon[385]: Registering new address record for 192.168.1.15 on wlan0.IPv4.
Feb 28 13:18:39 raspberrypi dhcpcd[467]: wlan0: adding route to 192.168.1.0/24
Feb 28 13:18:39 raspberrypi dhcpcd[467]: wlan0: adding default route via 192.168.1.1
Feb 28 13:18:39 raspberrypi pt-sys-oled[726]: [13:18:39.222719 I] Finished startup animation
Feb 28 13:18:39 raspberrypi pt-sys-oled[726]: [13:18:39.222828 I] Setting up application
Feb 28 13:18:39 raspberrypi pt-sys-oled[726]: [13:18:39.799778 I] Changing menu from to Menus.SYS_INFO
Feb 28 13:18:39 raspberrypi pt-sys-oled[726]: [13:18:39.825414 I] Starting application
Feb 28 13:18:40 raspberrypi systemd[1]: rclone.service: Service RestartSec=10s expired, scheduling restart.
Feb 28 13:18:40 raspberrypi systemd[1]: rclone.service: Scheduled restart job, restart counter is at 1.
Feb 28 13:18:40 raspberrypi systemd[1]: Stopped Google Drive (rclone).
Feb 28 13:18:40 raspberrypi systemd[1]: Started Google Drive (rclone).
Feb 28 13:18:41 raspberrypi rclone[958]: 2021/02/28 13:18:41 NOTICE: Time may be set wrong - time from “www.googleapis.com” is -1h39m40.626295009s different from this computer
Feb 28 13:18:41 raspberrypi rclone[958]: 2021/02/28 13:18:41 Failed to create file system for “google-drive:”: couldn’t find root directory ID: googleapi: Error 401: Invalid Credentials, authError
Feb 28 13:18:41 raspberrypi systemd[1]: rclone.service: Main process exited, code=exited, status=1/FAILURE
Feb 28 13:18:41 raspberrypi systemd[1]: rclone.service: Failed with result ‘exit-code’.
Feb 28 13:18:46 raspberrypi pt-device-manager[390]: [13:18:46.037898 I] Starting main idletime check thread…
Feb 28 13:18:46 raspberrypi pt-device-manager[390]: Exception in thread Thread-6:
Feb 28 13:18:46 raspberrypi pt-device-manager[390]: Traceback (most recent call last):
Feb 28 13:18:46 raspberrypi pt-device-manager[390]: File “/usr/lib/python3.7/threading.py”, line 917, in _bootstrap_inner
Feb 28 13:18:46 raspberrypi pt-device-manager[390]: self.run()
Feb 28 13:18:46 raspberrypi pt-device-manager[390]: File “/usr/lib/python3.7/threading.py”, line 865, in run
Feb 28 13:18:46 raspberrypi pt-device-manager[390]: self._target(*self._args, **self._kwargs)
Feb 28 13:18:46 raspberrypi pt-device-manager[390]: File “/usr/lib/pt-device-manager/ptdm_idle_monitor.py”, line 114, in _main_thread_loop
Feb 28 13:18:46 raspberrypi pt-device-manager[390]: xprintidle_resp = check_output([“xprintidle”], stderr=FNULL)
Feb 28 13:18:46 raspberrypi pt-device-manager[390]: File “/usr/lib/python3.7/subprocess.py”, line 395, in check_output
Feb 28 13:18:46 raspberrypi pt-device-manager[390]: **kwargs).stdout
Feb 28 13:18:46 raspberrypi pt-device-manager[390]: File “/usr/lib/python3.7/subprocess.py”, line 472, in run
Feb 28 13:18:46 raspberrypi pt-device-manager[390]: with Popen(*popenargs, **kwargs) as process:
Feb 28 13:18:46 raspberrypi pt-device-manager[390]: File “/usr/lib/python3.7/subprocess.py”, line 775, in init
Feb 28 13:18:46 raspberrypi pt-device-manager[390]: restore_signals, start_new_session)
Feb 28 13:18:46 raspberrypi pt-device-manager[390]: File “/usr/lib/python3.7/subprocess.py”, line 1522, in _execute_child
Feb 28 13:18:46 raspberrypi pt-device-manager[390]: raise child_exception_type(errno_num, err_msg, err_filename)
Feb 28 13:18:46 raspberrypi pt-device-manager[390]: FileNotFoundError: [Errno 2] No such file or directory: ‘xprintidle’: ‘xprintidle’
Feb 28 13:18:47 raspberrypi dhcpcd[467]: wlan0: no IPv6 Routers available
Feb 28 13:18:51 raspberrypi systemd[1]: rclone.service: Service RestartSec=10s expired, scheduling restart.
Feb 28 13:18:51 raspberrypi systemd[1]: rclone.service: Scheduled restart job, restart counter is at 2.
Feb 28 13:18:51 raspberrypi systemd[1]: Stopped Google Drive (rclone).
Feb 28 13:18:51 raspberrypi systemd[1]: Started Google Drive (rclone).
Feb 28 13:18:52 raspberrypi rclone[1083]: 2021/02/28 13:18:52 NOTICE: Time may be set wrong - time from “www.googleapis.com” is -1h39m40.943424682s different from this computer
Feb 28 13:18:52 raspberrypi rclone[1083]: 2021/02/28 13:18:52 Failed to create file system for “google-drive:”: couldn’t find root directory ID: googleapi: Error 401: Invalid Credentials, authError
Feb 28 13:18:52 raspberrypi systemd[1]: rclone.service: Main process exited, code=exited, status=1/FAILURE
Feb 28 13:18:52 raspberrypi systemd[1]: rclone.service: Failed with result ‘exit-code’.
Feb 28 13:18:56 raspberrypi systemd[1]: systemd-fsckd.service: Succeeded.

Potentially a really stupid question so please don’t take this as condescending (as it’s not meant to be and I’ve found myself guilty of it), but is your system time set to your actual local time?

it is when it updates OTA from the online time services. I wondered why it was rechecking the time and saying it was over an hour off. It had been displaying the correct time when I checked at about 1:14 :confused:

Update:

Just crashed again. I was switching tabs on chromium when this one happened. I started manipulating another page. In the system log, I have discovered that nearly the same sequence of events transpired before this crash too. Not sure if it’s causation, but there is correlation now.

It does seem that it starts happening when trying to update the system time

:confused:

Feb 28 17:53:38 raspberrypi systemd[752]: Started Virtual filesystem service - Apple File Conduit monitor.
Feb 28 17:53:39 raspberrypi kernel: [ 17.815059] v3d fec00000.v3d: MMU error from client L2T (0) at 0x2b21000, pte invalid
Feb 28 17:53:41 raspberrypi systemd[1]: systemd-rfkill.service: Succeeded.
Feb 28 17:53:42 raspberrypi pt-device-manager[455]: [17:53:42.399193 I] Setting OLED Pi control state to 1
Feb 28 17:53:42 raspberrypi pt-device-manager[455]: [17:53:42.413358 I] Recv: REQ_SET_OLED_CONTROL 1 - Send: RSP_SET_OLED_CONTROL
Feb 28 17:53:42 raspberrypi pt-sys-oled[721]: [17:53:42.462552 I] Finished startup animation
Feb 28 17:53:42 raspberrypi pt-sys-oled[721]: [17:53:42.463991 I] Setting up application
Feb 28 17:53:43 raspberrypi pt-sys-oled[721]: [17:53:43.016283 I] Changing menu from to Menus.SYS_INFO
Feb 28 17:53:43 raspberrypi pt-sys-oled[721]: [17:53:43.033128 I] Starting application
Feb 28 17:53:43 raspberrypi dhcpcd[472]: wlan0: leased 192.168.1.15 for 86400 seconds
Feb 28 17:53:43 raspberrypi avahi-daemon[438]: Joining mDNS multicast group on interface wlan0.IPv4 with address 192.168.1.15.
Feb 28 17:53:43 raspberrypi dhcpcd[472]: wlan0: adding route to 192.168.1.0/24
Feb 28 17:53:43 raspberrypi dhcpcd[472]: wlan0: adding default route via 192.168.1.1
Feb 28 17:53:43 raspberrypi avahi-daemon[438]: New relevant interface wlan0.IPv4 for mDNS.
Feb 28 17:53:43 raspberrypi avahi-daemon[438]: Registering new address record for 192.168.1.15 on wlan0.IPv4.
Feb 28 17:53:43 raspberrypi systemd[1]: rclone.service: Service RestartSec=10s expired, scheduling restart.
Feb 28 17:53:43 raspberrypi systemd[1]: rclone.service: Scheduled restart job, restart counter is at 1.
Feb 28 17:53:43 raspberrypi systemd[1]: Stopped Google Drive (rclone).
Feb 28 17:53:43 raspberrypi systemd[1]: Started Google Drive (rclone).
Feb 28 17:53:43 raspberrypi rclone[1141]: 2021/02/28 17:53:43 NOTICE: Time may be set wrong - time from “www.googleapis.com” is -14m9.023247324s different from this computer
Feb 28 17:53:44 raspberrypi rclone[1141]: 2021/02/28 17:53:44 ERROR : Failed to create vfs cache - disabling: failed to make cache directory: make cache directory failed: mkdir /home/pi/gcache/vfs/google-drive: permission denied
Feb 28 17:53:45 raspberrypi dbus-daemon[771]: [session uid=1000 pid=771] Activating via systemd: service name=‘org.gtk.vfs.Metadata’ unit=‘gvfs-metadata.service’ requested by ‘:1.7’ (uid=1000 pid=892 comm="pcmanfm --desktop --profile LXD$
Feb 28 17:53:45 raspberrypi systemd[752]: Starting Virtual filesystem metadata service…
Feb 28 17:53:45 raspberrypi dbus-daemon[771]: [session uid=1000 pid=771] Successfully activated service ‘org.gtk.vfs.Metadata’
Feb 28 17:53:45 raspberrypi systemd[752]: Started Virtual filesystem metadata service.
Feb 28 17:53:48 raspberrypi pt-device-manager[455]: [17:53:48.831945 I] Starting main idletime check thread…
Feb 28 17:53:48 raspberrypi pt-device-manager[455]: Exception in thread Thread-6:
Feb 28 17:53:48 raspberrypi pt-device-manager[455]: Traceback (most recent call last):
Feb 28 17:53:48 raspberrypi pt-device-manager[455]: File “/usr/lib/python3.7/threading.py”, line 917, in _bootstrap_inner
Feb 28 17:53:48 raspberrypi pt-device-manager[455]: self.run()
Feb 28 17:53:48 raspberrypi pt-device-manager[455]: File “/usr/lib/python3.7/threading.py”, line 865, in run
Feb 28 17:53:48 raspberrypi pt-device-manager[455]: self._target(*self._args, **self._kwargs)
Feb 28 17:53:48 raspberrypi pt-device-manager[455]: File “/usr/lib/pt-device-manager/ptdm_idle_monitor.py”, line 114, in _main_thread_loop
Feb 28 17:53:48 raspberrypi pt-device-manager[455]: xprintidle_resp = check_output([“xprintidle”], stderr=FNULL)
Feb 28 17:53:48 raspberrypi pt-device-manager[455]: File “/usr/lib/python3.7/subprocess.py”, line 395, in check_output
Feb 28 17:53:48 raspberrypi pt-device-manager[455]: **kwargs).stdout
Feb 28 17:53:48 raspberrypi pt-device-manager[455]: File “/usr/lib/python3.7/subprocess.py”, line 472, in run
Feb 28 17:53:48 raspberrypi pt-device-manager[455]: with Popen(*popenargs, **kwargs) as process:
Feb 28 17:53:48 raspberrypi pt-device-manager[455]: File “/usr/lib/python3.7/subprocess.py”, line 775, in init
Feb 28 17:53:48 raspberrypi pt-device-manager[455]: restore_signals, start_new_session)
Feb 28 17:53:48 raspberrypi pt-device-manager[455]: File “/usr/lib/python3.7/subprocess.py”, line 1522, in _execute_child
Feb 28 17:53:48 raspberrypi pt-device-manager[455]: raise child_exception_type(errno_num, err_msg, err_filename)
Feb 28 17:53:48 raspberrypi pt-device-manager[455]: FileNotFoundError: [Errno 2] No such file or directory: ‘xprintidle’: ‘xprintidle’
Feb 28 17:53:50 raspberrypi dhcpcd[472]: wlan0: no IPv6 Routers available
Feb 28 17:53:58 raspberrypi systemd[1]: systemd-fsckd.service: Succeeded.
Feb 28 18:08:09 raspberrypi systemd-timesyncd[342]: Synchronized to time server for the first time 137.190.2.4:123 (2.debian.pool.ntp.org).
Feb 28 18:08:16 raspberrypi systemd[1]: systemd-hostnamed.service: Succeeded.
Feb 28 18:10:26 raspberrypi kernel: [ 175.011206] logitech-hidpp-device 0003:046D:1017.0008: HID++ 1.0 device connected.

Have you tried a fresh install of the os?

1 Like

hey @Supernovali … it appears that you’re missing the xprintidle package… you can install it via apt with sudo apt install xprintidle -y

2 Likes

ok, I’ll give that a go here in just a minute. @CAProjects, not yet, but I will eventually. I usually prefer troubleshooting an issue before resorting to cleaning up and trying again. In this case, it’ll help the devs figure things out :slight_smile: Or I can figure them out and report what I found. I don’t have anything vitally important on it that I don’t also back up to my google drive