API tools faq
paste
SaleB

journalctl 23122022

SaleB
Dec 23rd, 2022
152
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 122.42 KB | None | 0 0
raw download clone embed print report
  1. -- Journal begins at Sat 2022-10-01 03:26:17 CEST, ends at Fri 2022-12-23 10:18:11 CET. --
  2. Dec 23 10:05:07 primary systemd[573]: run-docker-runtime\x2drunc-moby-8d91dce5794e433b9423e2386c56a1be8f2da6191722acf706983c25a82e049a-runc.zgMoaE.mount: Succeeded.
  3. Dec 23 10:05:37 primary systemd[573]: run-docker-runtime\x2drunc-moby-8d91dce5794e433b9423e2386c56a1be8f2da6191722acf706983c25a82e049a-runc.8qhzxK.mount: Succeeded.
  4. Dec 23 10:06:07 primary systemd[573]: run-docker-runtime\x2drunc-moby-8d91dce5794e433b9423e2386c56a1be8f2da6191722acf706983c25a82e049a-runc.hF1iZB.mount: Succeeded.
  5. Dec 23 10:06:07 primary systemd[573]: run-docker-runtime\x2drunc-moby-2da8ac201c0d22dd379334c69c3250743a4abef5cc683f97dc704df161f84f5a-runc.E5q4NM.mount: Succeeded.
  6. Dec 23 10:06:13 primary sudo[184789]: saleb : TTY=pts/0 ; PWD=/home/saleb/DockerData ; USER=root ; COMMAND=/usr/sbin/reboot
  7. Dec 23 10:06:13 primary sudo[184789]: pam_unix(sudo:session): session opened for user root(uid=0) by saleb(uid=1000)
  8. Dec 23 10:06:13 primary sudo[184789]: pam_unix(sudo:session): session closed for user root
  9. Dec 23 10:06:13 primary systemd[573]: Stopped target GNOME Wayland Session (session: gnome).
  10. Dec 23 10:06:13 primary systemd[573]: Stopped target Current graphical user session.
  11. Dec 23 10:06:13 primary systemd[573]: Stopped target GNOME Session.
  12. Dec 23 10:06:13 primary systemd[573]: Stopped target GNOME Wayland Session.
  13. Dec 23 10:06:13 primary systemd[573]: Stopped target GNOME session X11 services.
  14. Dec 23 10:06:13 primary systemd[573]: Stopped target GNOME Session (session: gnome).
  15. Dec 23 10:06:13 primary systemd[573]: Stopped target GNOME accessibility target.
  16. Dec 23 10:06:13 primary systemd[573]: Stopped target GNOME color management target.
  17. Dec 23 10:06:13 primary systemd[573]: Stopped target GNOME date & time target.
  18. Dec 23 10:06:13 primary systemd[573]: Stopped target GNOME maintenance of expirable data target.
  19. Dec 23 10:06:13 primary systemd[573]: Stopped target GNOME keyboard configuration target.
  20. Dec 23 10:06:13 primary systemd[573]: Stopped target GNOME keyboard shortcuts target.
  21. Dec 23 10:06:13 primary systemd[573]: Stopped target GNOME power management target.
  22. Dec 23 10:06:13 primary systemd[573]: Stopped target GNOME printer notifications target.
  23. Dec 23 10:06:13 primary systemd[573]: Stopped target GNOME RFKill support target.
  24. Dec 23 10:06:13 primary systemd[573]: Stopped target GNOME FreeDesktop screensaver target.
  25. Dec 23 10:06:13 primary systemd[573]: Stopped target GNOME file sharing target.
  26. Dec 23 10:06:13 primary systemd[573]: Stopped target GNOME smartcard target.
  27. Dec 23 10:06:13 primary systemd[573]: Stopped target GNOME sound sample caching target.
  28. Dec 23 10:06:13 primary systemd[573]: Stopped target GNOME USB protection target.
  29. Dec 23 10:06:13 primary systemd[573]: Stopped target GNOME Wacom tablet support target.
  30. Dec 23 10:06:13 primary systemd[573]: Stopped target GNOME XSettings target.
  31. Dec 23 10:06:13 primary systemd[573]: Stopping GNOME accessibility service...
  32. Dec 23 10:06:13 primary systemd[573]: Stopping GNOME color management service...
  33. Dec 23 10:06:13 primary systemd[573]: Stopping GNOME date & time service...
  34. Dec 23 10:06:13 primary systemd[573]: Stopping GNOME maintenance of expirable data service...
  35. Dec 23 10:06:13 primary systemd[573]: Stopping GNOME keyboard configuration service...
  36. Dec 23 10:06:13 primary systemd[573]: Stopping GNOME keyboard shortcuts service...
  37. Dec 23 10:06:13 primary systemd[573]: Stopping GNOME power management service...
  38. Dec 23 10:06:13 primary systemd[573]: Stopping GNOME printer notifications service...
  39. Dec 23 10:06:13 primary systemd[573]: Stopping GNOME RFKill support service...
  40. Dec 23 10:06:13 primary systemd[573]: Stopping GNOME FreeDesktop screensaver service...
  41. Dec 23 10:06:13 primary systemd[573]: Stopping GNOME file sharing service...
  42. Dec 23 10:06:13 primary systemd[573]: Stopping GNOME smartcard service...
  43. Dec 23 10:06:13 primary systemd[573]: Stopping GNOME sound sample caching service...
  44. Dec 23 10:06:13 primary systemd[573]: Stopping GNOME USB protection service...
  45. Dec 23 10:06:13 primary systemd[573]: Stopping GNOME Wacom tablet support service...
  46. Dec 23 10:06:13 primary systemd[573]: Stopping GNOME XSettings service...
  47. Dec 23 10:06:13 primary gnome-software[1688]: Error checking authorization for action id org.freedesktop.packagekit.trigger-offline-update: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name :1.5 was not provided by any .service files
  48. Dec 23 10:06:13 primary systemd[573]: org.gnome.SettingsDaemon.A11ySettings.service: Succeeded.
  49. Dec 23 10:06:13 primary systemd[573]: Stopped GNOME accessibility service.
  50. Dec 23 10:06:13 primary systemd[573]: org.gnome.SettingsDaemon.Datetime.service: Succeeded.
  51. Dec 23 10:06:13 primary systemd[573]: Stopped GNOME date & time service.
  52. Dec 23 10:06:13 primary systemd[573]: org.gnome.SettingsDaemon.Housekeeping.service: Succeeded.
  53. Dec 23 10:06:13 primary systemd[573]: Stopped GNOME maintenance of expirable data service.
  54. Dec 23 10:06:13 primary systemd[573]: org.gnome.SettingsDaemon.Housekeeping.service: Consumed 21.405s CPU time.
  55. Dec 23 10:06:13 primary systemd[573]: org.gnome.SettingsDaemon.Rfkill.service: Succeeded.
  56. Dec 23 10:06:13 primary systemd[573]: Stopped GNOME RFKill support service.
  57. Dec 23 10:06:13 primary systemd[573]: org.gnome.SettingsDaemon.Smartcard.service: Succeeded.
  58. Dec 23 10:06:13 primary systemd[573]: Stopped GNOME smartcard service.
  59. Dec 23 10:06:13 primary systemd[573]: org.gnome.SettingsDaemon.Sound.service: Succeeded.
  60. Dec 23 10:06:13 primary systemd[573]: Stopped GNOME sound sample caching service.
  61. Dec 23 10:06:13 primary systemd[573]: org.gnome.SettingsDaemon.Sharing.service: Succeeded.
  62. Dec 23 10:06:13 primary systemd[573]: Stopped GNOME file sharing service.
  63. Dec 23 10:06:13 primary systemd[573]: Stopping Application launched by gnome-session-binary.
  64. Dec 23 10:06:13 primary systemd[573]: Stopping Application launched by gnome-session-binary.
  65. Dec 23 10:06:13 primary systemd[573]: Stopping Application launched by gnome-session-binary.
  66. Dec 23 10:06:13 primary systemd[573]: Stopping Application launched by gnome-session-binary.
  67. Dec 23 10:06:13 primary systemd[573]: Stopped target Main User Target.
  68. Dec 23 10:06:13 primary systemd[573]: Stopping D-Bus User Message Bus...
  69. Dec 23 10:06:13 primary systemd[573]: Stopping Evolution address book service...
  70. Dec 23 10:06:13 primary systemd[573]: Stopping Evolution calendar service...
  71. Dec 23 10:06:13 primary systemd[573]: Stopping Evolution source registry...
  72. Dec 23 10:06:13 primary systemd[573]: Stopping Virtual filesystem service - Apple File Conduit monitor...
  73. Dec 23 10:06:13 primary systemd[573]: Stopping Virtual filesystem service...
  74. Dec 23 10:06:13 primary systemd[573]: Stopping Virtual filesystem service - GNOME Online Accounts monitor...
  75. Dec 23 10:06:13 primary systemd[573]: Stopping Virtual filesystem service - digital camera monitor...
  76. Dec 23 10:06:13 primary systemd[573]: Stopping Virtual filesystem metadata service...
  77. Dec 23 10:06:13 primary systemd[573]: Stopping Virtual filesystem service - Media Transfer Protocol monitor...
  78. Dec 23 10:06:13 primary systemd[573]: Stopping Virtual filesystem service - disk device monitor...
  79. Dec 23 10:06:13 primary systemd[573]: Stopping Multimedia Service...
  80. Dec 23 10:06:13 primary systemd[573]: Stopping Sound Service...
  81. Dec 23 10:06:13 primary systemd[573]: Stopping Tracker file system data miner...
  82. Dec 23 10:06:13 primary systemd[573]: Stopping sandboxed app permission store...
  83. Dec 23 10:06:13 primary systemd[573]: gvfs-gphoto2-volume-monitor.service: Succeeded.
  84. Dec 23 10:06:13 primary systemd[573]: Stopped Virtual filesystem service - digital camera monitor.
  85. Dec 23 10:06:13 primary systemd[573]: xdg-permission-store.service: Succeeded.
  86. Dec 23 10:06:13 primary systemd[573]: Stopped sandboxed app permission store.
  87. Dec 23 10:06:13 primary systemd[573]: app-gnome-at\x2dspi\x2ddbus\x2dbus-768.scope: Succeeded.
  88. Dec 23 10:06:13 primary systemd[573]: Stopped Application launched by gnome-session-binary.
  89. Dec 23 10:06:13 primary systemd[573]: app-gnome-org.gnome.SettingsDaemon.DiskUtilityNotify-1731.scope: Succeeded.
  90. Dec 23 10:06:13 primary systemd[573]: Stopped Application launched by gnome-session-binary.
  91. Dec 23 10:06:13 primary systemd[573]: gvfs-goa-volume-monitor.service: Succeeded.
  92. Dec 23 10:06:13 primary gnome-session-binary[741]: GnomeDesktop-WARNING: Could not create transient scope for PID 184838: The connection is closed
  93. Dec 23 10:06:13 primary gnome-session[741]: gnome-session-binary[741]: GnomeDesktop-WARNING: Could not create transient scope for PID 184838: The connection is closed
  94. Dec 23 10:06:13 primary gnome-session[741]: gnome-session-binary[741]: WARNING: Lost name on bus: org.gnome.SessionManager
  95. Dec 23 10:06:13 primary systemd[573]: Stopped Virtual filesystem service - GNOME Online Accounts monitor.
  96. Dec 23 10:06:13 primary gnome-session-binary[741]: WARNING: Lost name on bus: org.gnome.SessionManager
  97. Dec 23 10:06:13 primary systemd[573]: gvfs-mtp-volume-monitor.service: Succeeded.
  98. Dec 23 10:06:13 primary systemd[573]: Stopped Virtual filesystem service - Media Transfer Protocol monitor.
  99. Dec 23 10:06:13 primary systemd[573]: gvfs-metadata.service: Succeeded.
  100. Dec 23 10:06:13 primary systemd[573]: Stopped Virtual filesystem metadata service.
  101. Dec 23 10:06:13 primary systemd[573]: app-gnome-gnome\x2dsoftware\x2dservice-1688.scope: Succeeded.
  102. Dec 23 10:06:13 primary systemd[573]: Stopped Application launched by gnome-session-binary.
  103. Dec 23 10:06:13 primary systemd[573]: app-gnome-gnome\x2dsoftware\x2dservice-1688.scope: Consumed 2.397s CPU time.
  104. Dec 23 10:06:13 primary systemd[573]: gvfs-udisks2-volume-monitor.service: Succeeded.
  105. Dec 23 10:06:13 primary systemd[573]: Stopped Virtual filesystem service - disk device monitor.
  106. Dec 23 10:06:13 primary systemd[573]: gvfs-udisks2-volume-monitor.service: Consumed 32.575s CPU time.
  107. Dec 23 10:06:13 primary systemd[573]: gnome-session-monitor.service: Succeeded.
  108. Dec 23 10:06:13 primary systemd[573]: Stopped Monitor Session leader for GNOME Session.
  109. Dec 23 10:06:13 primary systemd[573]: gvfs-afc-volume-monitor.service: Succeeded.
  110. Dec 23 10:06:13 primary systemd[573]: Stopped Virtual filesystem service - Apple File Conduit monitor.
  111. Dec 23 10:06:13 primary systemd[573]: gvfs-afc-volume-monitor.service: Consumed 2.288s CPU time.
  112. Dec 23 10:06:13 primary systemd[573]: evolution-source-registry.service: Succeeded.
  113. Dec 23 10:06:13 primary systemd[573]: Stopped Evolution source registry.
  114. Dec 23 10:06:13 primary systemd[573]: evolution-calendar-factory.service: Succeeded.
  115. Dec 23 10:06:13 primary systemd[573]: Stopped Evolution calendar service.
  116. Dec 23 10:06:13 primary systemd[573]: evolution-addressbook-factory.service: Succeeded.
  117. Dec 23 10:06:13 primary systemd[573]: Stopped Evolution address book service.
  118. Dec 23 10:06:13 primary systemd[573]: app-gnome-org.gnome.Evolution\x2dalarm\x2dnotify-1708.scope: Succeeded.
  119. Dec 23 10:06:13 primary systemd[573]: Stopped Application launched by gnome-session-binary.
  120. Dec 23 10:06:13 primary systemd[573]: pipewire.service: Succeeded.
  121. Dec 23 10:06:13 primary systemd[573]: Stopped Multimedia Service.
  122. Dec 23 10:06:13 primary systemd[573]: pulseaudio.service: Succeeded.
  123. Dec 23 10:06:13 primary systemd[573]: Stopped Sound Service.
  124. Dec 23 10:06:13 primary systemd[573]: org.gnome.SettingsDaemon.UsbProtection.service: Succeeded.
  125. Dec 23 10:06:13 primary systemd[573]: Stopped GNOME USB protection service.
  126. Dec 23 10:06:13 primary systemd[573]: run-user-1000-gvfs.mount: Succeeded.
  127. Dec 23 10:06:13 primary systemd[573]: org.gnome.SettingsDaemon.XSettings.service: Succeeded.
  128. Dec 23 10:06:13 primary systemd[573]: Stopped GNOME XSettings service.
  129. Dec 23 10:06:13 primary systemd[573]: Stopped target GNOME session X11 services.
  130. Dec 23 10:06:13 primary systemd[573]: org.gnome.SettingsDaemon.ScreensaverProxy.service: Succeeded.
  131. Dec 23 10:06:13 primary systemd[573]: Stopped GNOME FreeDesktop screensaver service.
  132. Dec 23 10:06:13 primary systemd[573]: gvfs-daemon.service: Succeeded.
  133. Dec 23 10:06:13 primary systemd[573]: Stopped Virtual filesystem service.
  134. Dec 23 10:06:13 primary gnome-shell[769]: Could not release device (13,65): Cannot invoke method; proxy is for the well-known name org.freedesktop.login1 without an owner, and proxy was constructed with the G_DBUS_PROXY_FLAGS_DO_NOT_AUTO_START flag
  135. Dec 23 10:06:13 primary systemd[573]: org.gnome.SettingsDaemon.PrintNotifications.service: Succeeded.
  136. Dec 23 10:06:13 primary systemd[573]: Stopped GNOME printer notifications service.
  137. Dec 23 10:06:14 primary tracker-miner-fs[598]: Received signal:15->'Terminated'
  138. Dec 23 10:06:14 primary tracker-miner-f[598]: Error while sending AddMatch() message: The connection is closed
  139. Dec 23 10:06:14 primary tracker-miner-f[598]: Error while sending AddMatch() message: The connection is closed
  140. Dec 23 10:06:14 primary tracker-miner-f[598]: Error while sending AddMatch() message: The connection is closed
  141. Dec 23 10:06:14 primary gnome-shell[769]: Could not release device (13,69): Cannot invoke method; proxy is for the well-known name org.freedesktop.login1 without an owner, and proxy was constructed with the G_DBUS_PROXY_FLAGS_DO_NOT_AUTO_START flag
  142. Dec 23 10:06:14 primary tracker-miner-fs[598]: OK
  143. Dec 23 10:06:14 primary systemd[573]: dbus.service: Succeeded.
  144. Dec 23 10:06:14 primary systemd[573]: Stopped D-Bus User Message Bus.
  145. Dec 23 10:06:14 primary systemd[573]: dbus.service: Consumed 1.127s CPU time.
  146. Dec 23 10:06:14 primary at-spi-dbus-bus.desktop[184838]: Failed to launch bus: Failed to connect to session bus
  147. Dec 23 10:06:14 primary gnome-session-binary[741]: WARNING: App 'at-spi-dbus-bus.desktop' exited with code 1
  148. Dec 23 10:06:14 primary gnome-session[741]: gnome-session-binary[741]: WARNING: App 'at-spi-dbus-bus.desktop' exited with code 1
  149. Dec 23 10:06:14 primary systemd[573]: tracker-miner-fs.service: Succeeded.
  150. Dec 23 10:06:14 primary systemd[573]: Stopped Tracker file system data miner.
  151. Dec 23 10:06:14 primary gnome-shell[769]: Could not release device (13,64): Cannot invoke method; proxy is for the well-known name org.freedesktop.login1 without an owner, and proxy was constructed with the G_DBUS_PROXY_FLAGS_DO_NOT_AUTO_START flag
  152. Dec 23 10:06:14 primary gnome-shell[769]: Could not release device (13,67): Cannot invoke method; proxy is for the well-known name org.freedesktop.login1 without an owner, and proxy was constructed with the G_DBUS_PROXY_FLAGS_DO_NOT_AUTO_START flag
  153. Dec 23 10:06:14 primary gnome-shell[769]: Could not release device (13,66): Cannot invoke method; proxy is for the well-known name org.freedesktop.login1 without an owner, and proxy was constructed with the G_DBUS_PROXY_FLAGS_DO_NOT_AUTO_START flag
  154. Dec 23 10:06:14 primary gnome-shell[769]: Lost or failed to acquire name org.gnome.Mutter.ScreenCast
  155. Dec 23 10:06:14 primary gnome-shell[769]: Lost or failed to acquire name org.gnome.Mutter.RemoteDesktop
  156. Dec 23 10:06:14 primary gnome-shell[769]: Owner of volume monitor org.gtk.vfs.UDisks2VolumeMonitor disconnected from the bus; removing drives/volumes/mounts
  157. Dec 23 10:06:14 primary gnome-shell[769]: Owner of volume monitor org.gtk.vfs.GoaVolumeMonitor disconnected from the bus; removing drives/volumes/mounts
  158. Dec 23 10:06:14 primary gnome-shell[769]: Error checking authorization for action id org.freedesktop.bolt.enroll: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name :1.5 was not provided by any .service files
  159. Dec 23 10:06:14 primary gnome-shell[769]: Error checking authorization for action id org.freedesktop.packagekit.trigger-offline-update: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name :1.5 was not provided by any .service files
  160. Dec 23 10:06:14 primary gnome-shell[769]: Error while sending AddMatch() message: The connection is closed
  161. Dec 23 10:06:14 primary gnome-shell[769]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
  162. Dec 23 10:06:14 primary gnome-shell[769]: == Stack trace for context 0x55e5b0bb1120 ==
  163. Dec 23 10:06:14 primary gnome-shell[769]: == Stack trace for context 0x55e5b0bb1120 ==
  164. Dec 23 10:06:14 primary gnome-shell[769]: == Stack trace for context 0x55e5b0bb1120 ==
  165. Dec 23 10:06:14 primary gnome-shell[769]: == Stack trace for context 0x55e5b0bb1120 ==
  166. Dec 23 10:06:14 primary gnome-shell[769]: The offending signal was notify on NMDeviceEthernet 0x55e5b2c0c270.
  167. Dec 23 10:06:14 primary gnome-shell[769]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
  168. Dec 23 10:06:14 primary gnome-shell[769]: == Stack trace for context 0x55e5b0bb1120 ==
  169. Dec 23 10:06:14 primary gnome-shell[769]: == Stack trace for context 0x55e5b0bb1120 ==
  170. Dec 23 10:06:14 primary gnome-shell[769]: == Stack trace for context 0x55e5b0bb1120 ==
  171. Dec 23 10:06:14 primary gnome-shell[769]: == Stack trace for context 0x55e5b0bb1120 ==
  172. Dec 23 10:06:14 primary gnome-shell[769]: == Stack trace for context 0x55e5b0bb1120 ==
  173. Dec 23 10:06:14 primary gnome-shell[769]: The offending signal was notify on NMActiveConnection 0x55e5b2c10180.
  174. Dec 23 10:06:14 primary gnome-shell[769]: == Stack trace for context 0x55e5b0bb1120 ==
  175. Dec 23 10:06:14 primary gnome-shell[769]: == Stack trace for context 0x55e5b0bb1120 ==
  176. Dec 23 10:06:14 primary gnome-shell[769]: == Stack trace for context 0x55e5b0bb1120 ==
  177. Dec 23 10:06:14 primary gnome-shell[769]: == Stack trace for context 0x55e5b0bb1120 ==
  178. Dec 23 10:06:14 primary gnome-shell[769]: == Stack trace for context 0x55e5b0bb1120 ==
  179. Dec 23 10:06:14 primary gnome-shell[769]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
  180. Dec 23 10:06:14 primary gnome-shell[769]: == Stack trace for context 0x55e5b0bb1120 ==
  181. Dec 23 10:06:14 primary gnome-shell[769]: == Stack trace for context 0x55e5b0bb1120 ==
  182. Dec 23 10:06:14 primary gnome-shell[769]: The offending signal was notify on NMActiveConnection 0x55e5b2c10180.
  183. Dec 23 10:06:14 primary gnome-shell[769]: == Stack trace for context 0x55e5b0bb1120 ==
  184. Dec 23 10:06:14 primary gnome-shell[769]: == Stack trace for context 0x55e5b0bb1120 ==
  185. Dec 23 10:06:14 primary gnome-shell[769]: == Stack trace for context 0x55e5b0bb1120 ==
  186. Dec 23 10:06:14 primary gnome-shell[769]: == Stack trace for context 0x55e5b0bb1120 ==
  187. Dec 23 10:06:14 primary gnome-shell[769]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
  188. Dec 23 10:06:14 primary gnome-shell[769]: == Stack trace for context 0x55e5b0bb1120 ==
  189. Dec 23 10:06:14 primary gnome-shell[769]: == Stack trace for context 0x55e5b0bb1120 ==
  190. Dec 23 10:06:14 primary gnome-shell[769]: == Stack trace for context 0x55e5b0bb1120 ==
  191. Dec 23 10:06:14 primary gnome-shell[769]: == Stack trace for context 0x55e5b0bb1120 ==
  192. Dec 23 10:06:14 primary gnome-shell[769]: == Stack trace for context 0x55e5b0bb1120 ==
  193. Dec 23 10:06:14 primary gnome-shell[769]: The offending signal was state-changed on NMDeviceEthernet 0x55e5b2c0c270.
  194. Dec 23 10:06:14 primary gnome-shell[769]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
  195. Dec 23 10:06:14 primary gnome-shell[769]: == Stack trace for context 0x55e5b0bb1120 ==
  196. Dec 23 10:06:14 primary gnome-shell[769]: == Stack trace for context 0x55e5b0bb1120 ==
  197. Dec 23 10:06:14 primary gnome-shell[769]: == Stack trace for context 0x55e5b0bb1120 ==
  198. Dec 23 10:06:14 primary gnome-shell[769]: == Stack trace for context 0x55e5b0bb1120 ==
  199. Dec 23 10:06:14 primary gnome-shell[769]: == Stack trace for context 0x55e5b0bb1120 ==
  200. Dec 23 10:06:14 primary gnome-shell[769]: The offending signal was destroy on Gjs_ui_appDisplay_FolderGrid 0x55e5b2c8cc20.
  201. Dec 23 10:06:14 primary gnome-shell[769]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
  202. Dec 23 10:06:14 primary gnome-shell[769]: The offending signal was destroy on Gjs_ui_appDisplay_FolderGrid 0x55e5b2c8cc20.
  203. Dec 23 10:06:14 primary gnome-shell[769]: == Stack trace for context 0x55e5b0bb1120 ==
  204. Dec 23 10:06:14 primary gnome-shell[769]: == Stack trace for context 0x55e5b0bb1120 ==
  205. Dec 23 10:06:14 primary gnome-shell[769]: == Stack trace for context 0x55e5b0bb1120 ==
  206. Dec 23 10:06:14 primary gnome-shell[769]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
  207. Dec 23 10:06:14 primary gnome-shell[769]: == Stack trace for context 0x55e5b0bb1120 ==
  208. Dec 23 10:06:14 primary gnome-shell[769]: == Stack trace for context 0x55e5b0bb1120 ==
  209. Dec 23 10:06:14 primary gnome-shell[769]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55e5b2ca87d0.
  210. Dec 23 10:06:14 primary gnome-shell[769]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
  211. Dec 23 10:06:14 primary gnome-shell[769]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55e5b2ca87d0.
  212. Dec 23 10:06:14 primary gnome-shell[769]: == Stack trace for context 0x55e5b0bb1120 ==
  213. Dec 23 10:06:14 primary gnome-shell[769]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
  214. Dec 23 10:06:14 primary gnome-shell[769]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55e5b2ca87d0.
  215. Dec 23 10:06:14 primary gnome-shell[769]: == Stack trace for context 0x55e5b0bb1120 ==
  216. Dec 23 10:06:14 primary gnome-shell[769]: == Stack trace for context 0x55e5b0bb1120 ==
  217. Dec 23 10:06:14 primary gnome-shell[769]: == Stack trace for context 0x55e5b0bb1120 ==
  218. Dec 23 10:06:14 primary gnome-shell[769]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
  219. Dec 23 10:06:14 primary gnome-shell[769]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55e5b2caaa30.
  220. Dec 23 10:06:14 primary gnome-shell[769]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
  221. Dec 23 10:06:14 primary gnome-shell[769]: == Stack trace for context 0x55e5b0bb1120 ==
  222. Dec 23 10:06:14 primary gnome-shell[769]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x55e5b2c8cc20.
  223. Dec 23 10:06:14 primary gnome-shell[769]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
  224. Dec 23 10:06:14 primary gnome-shell[769]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55e5b2cb1340.
  225. Dec 23 10:06:14 primary gnome-shell[769]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
  226. Dec 23 10:06:14 primary gnome-shell[769]: == Stack trace for context 0x55e5b0bb1120 ==
  227. Dec 23 10:06:14 primary gnome-shell[769]: == Stack trace for context 0x55e5b0bb1120 ==
  228. Dec 23 10:06:14 primary gnome-shell[769]: == Stack trace for context 0x55e5b0bb1120 ==
  229. Dec 23 10:06:14 primary gnome-shell[769]: == Stack trace for context 0x55e5b0bb1120 ==
  230. Dec 23 10:06:14 primary gnome-shell[769]: == Stack trace for context 0x55e5b0bb1120 ==
  231. Dec 23 10:06:14 primary gnome-shell[769]: == Stack trace for context 0x55e5b0bb1120 ==
  232. Dec 23 10:06:14 primary gnome-shell[769]: == Stack trace for context 0x55e5b0bb1120 ==
  233. Dec 23 10:06:14 primary gnome-shell[769]: == Stack trace for context 0x55e5b0bb1120 ==
  234. Dec 23 10:06:14 primary gnome-shell[769]: == Stack trace for context 0x55e5b0bb1120 ==
  235. Dec 23 10:06:14 primary gnome-shell[769]: == Stack trace for context 0x55e5b0bb1120 ==
  236. Dec 23 10:06:14 primary gnome-shell[769]: == Stack trace for context 0x55e5b0bb1120 ==
  237. Dec 23 10:06:14 primary gnome-shell[769]: == Stack trace for context 0x55e5b0bb1120 ==
  238. Dec 23 10:06:14 primary gnome-shell[769]: == Stack trace for context 0x55e5b0bb1120 ==
  239. Dec 23 10:06:14 primary gnome-shell[769]: == Stack trace for context 0x55e5b0bb1120 ==
  240. Dec 23 10:06:14 primary gnome-shell[769]: == Stack trace for context 0x55e5b0bb1120 ==
  241. Dec 23 10:06:14 primary gnome-shell[769]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55e5b2cb1340.
  242. Dec 23 10:06:14 primary gnome-shell[769]: == Stack trace for context 0x55e5b0bb1120 ==
  243. Dec 23 10:06:14 primary gnome-shell[769]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
  244. Dec 23 10:06:14 primary gnome-shell[769]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55e5b2cb1340.
  245. Dec 23 10:06:14 primary gnome-shell[769]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
  246. Dec 23 10:06:14 primary gnome-shell[769]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55e5b2cb31c0.
  247. Dec 23 10:06:14 primary gnome-shell[769]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
  248. Dec 23 10:06:14 primary gnome-shell[769]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x55e5b2c8cc20.
  249. Dec 23 10:06:14 primary gnome-shell[769]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
  250. Dec 23 10:06:14 primary gnome-shell[769]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55e5b2c711b0.
  251. Dec 23 10:06:14 primary gnome-shell[769]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
  252. Dec 23 10:06:14 primary gnome-shell[769]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55e5b2c711b0.
  253. Dec 23 10:06:14 primary gnome-shell[769]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
  254. Dec 23 10:06:14 primary gnome-shell[769]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55e5b2c711b0.
  255. Dec 23 10:06:14 primary gnome-shell[769]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
  256. Dec 23 10:06:14 primary gnome-shell[769]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55e5b2c73070.
  257. Dec 23 10:06:14 primary gnome-shell[769]: == Stack trace for context 0x55e5b0bb1120 ==
  258. Dec 23 10:06:14 primary gnome-shell[769]: == Stack trace for context 0x55e5b0bb1120 ==
  259. Dec 23 10:06:14 primary gnome-shell[769]: == Stack trace for context 0x55e5b0bb1120 ==
  260. Dec 23 10:06:14 primary gnome-shell[769]: == Stack trace for context 0x55e5b0bb1120 ==
  261. Dec 23 10:06:14 primary gnome-shell[769]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
  262. Dec 23 10:06:14 primary gnome-shell[769]: == Stack trace for context 0x55e5b0bb1120 ==
  263. Dec 23 10:06:14 primary gnome-shell[769]: == Stack trace for context 0x55e5b0bb1120 ==
  264. Dec 23 10:06:14 primary gnome-shell[769]: == Stack trace for context 0x55e5b0bb1120 ==
  265. Dec 23 10:06:14 primary gnome-shell[769]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x55e5b2c8cc20.
  266. Dec 23 10:06:14 primary gnome-shell[769]: == Stack trace for context 0x55e5b0bb1120 ==
  267. Dec 23 10:06:14 primary gnome-shell[769]: == Stack trace for context 0x55e5b0bb1120 ==
  268. Dec 23 10:06:14 primary gnome-shell[769]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
  269. Dec 23 10:06:14 primary gnome-shell[769]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55e5b2c7a0c0.
  270. Dec 23 10:06:14 primary gnome-shell[769]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
  271. Dec 23 10:06:14 primary gnome-shell[769]: == Stack trace for context 0x55e5b0bb1120 ==
  272. Dec 23 10:06:14 primary gnome-shell[769]: == Stack trace for context 0x55e5b0bb1120 ==
  273. Dec 23 10:06:14 primary gnome-shell[769]: == Stack trace for context 0x55e5b0bb1120 ==
  274. Dec 23 10:06:14 primary gnome-shell[769]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55e5b2c7a0c0.
  275. Dec 23 10:06:14 primary gnome-shell[769]: == Stack trace for context 0x55e5b0bb1120 ==
  276. Dec 23 10:06:14 primary gnome-shell[769]: == Stack trace for context 0x55e5b0bb1120 ==
  277. Dec 23 10:06:14 primary gnome-shell[769]: == Stack trace for context 0x55e5b0bb1120 ==
  278. Dec 23 10:06:14 primary gnome-shell[769]: == Stack trace for context 0x55e5b0bb1120 ==
  279. Dec 23 10:06:14 primary gnome-shell[769]: == Stack trace for context 0x55e5b0bb1120 ==
  280. Dec 23 10:06:14 primary gnome-shell[769]: == Stack trace for context 0x55e5b0bb1120 ==
  281. Dec 23 10:06:14 primary gnome-shell[769]: == Stack trace for context 0x55e5b0bb1120 ==
  282. Dec 23 10:06:14 primary gnome-shell[769]: == Stack trace for context 0x55e5b0bb1120 ==
  283. Dec 23 10:06:14 primary gnome-shell[769]: == Stack trace for context 0x55e5b0bb1120 ==
  284. Dec 23 10:06:14 primary gnome-shell[769]: == Stack trace for context 0x55e5b0bb1120 ==
  285. Dec 23 10:06:14 primary gnome-shell[769]: == Stack trace for context 0x55e5b0bb1120 ==
  286. Dec 23 10:06:14 primary gnome-shell[769]: == Stack trace for context 0x55e5b0bb1120 ==
  287. Dec 23 10:06:14 primary gnome-shell[769]: == Stack trace for context 0x55e5b0bb1120 ==
  288. Dec 23 10:06:14 primary gnome-shell[769]: == Stack trace for context 0x55e5b0bb1120 ==
  289. Dec 23 10:06:14 primary gnome-shell[769]: == Stack trace for context 0x55e5b0bb1120 ==
  290. Dec 23 10:06:14 primary gnome-shell[769]: == Stack trace for context 0x55e5b0bb1120 ==
  291. Dec 23 10:06:14 primary gnome-shell[769]: == Stack trace for context 0x55e5b0bb1120 ==
  292. Dec 23 10:06:14 primary gnome-shell[769]: == Stack trace for context 0x55e5b0bb1120 ==
  293. Dec 23 10:06:14 primary gnome-shell[769]: == Stack trace for context 0x55e5b0bb1120 ==
  294. Dec 23 10:06:14 primary gnome-shell[769]: == Stack trace for context 0x55e5b0bb1120 ==
  295. Dec 23 10:06:14 primary gnome-shell[769]: == Stack trace for context 0x55e5b0bb1120 ==
  296. Dec 23 10:06:14 primary gnome-shell[769]: == Stack trace for context 0x55e5b0bb1120 ==
  297. Dec 23 10:06:14 primary gnome-shell[769]: == Stack trace for context 0x55e5b0bb1120 ==
  298. Dec 23 10:06:14 primary gnome-shell[769]: == Stack trace for context 0x55e5b0bb1120 ==
  299. Dec 23 10:06:14 primary gnome-shell[769]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
  300. Dec 23 10:06:14 primary gnome-shell[769]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55e5b2c7a0c0.
  301. Dec 23 10:06:14 primary gnome-shell[769]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
  302. Dec 23 10:06:14 primary gnome-shell[769]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55e5b2c7b910.
  303. Dec 23 10:06:14 primary gnome-shell[769]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
  304. Dec 23 10:06:14 primary gnome-shell[769]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x55e5b2c8cc20.
  305. Dec 23 10:06:14 primary gnome-shell[769]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
  306. Dec 23 10:06:14 primary gnome-shell[769]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55e5b2cbaca0.
  307. Dec 23 10:06:14 primary gnome-shell[769]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
  308. Dec 23 10:06:14 primary gnome-shell[769]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55e5b2cbaca0.
  309. Dec 23 10:06:14 primary gnome-shell[769]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
  310. Dec 23 10:06:14 primary gnome-shell[769]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55e5b2cbaca0.
  311. Dec 23 10:06:14 primary gnome-shell[769]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
  312. Dec 23 10:06:14 primary gnome-shell[769]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55e5b2cbda80.
  313. Dec 23 10:06:14 primary gnome-shell[769]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
  314. Dec 23 10:06:14 primary gnome-shell[769]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x55e5b2c8cc20.
  315. Dec 23 10:06:14 primary gnome-shell[769]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
  316. Dec 23 10:06:14 primary gnome-shell[769]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55e5b2cc4fd0.
  317. Dec 23 10:06:14 primary gnome-shell[769]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
  318. Dec 23 10:06:14 primary gnome-shell[769]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55e5b2cc4fd0.
  319. Dec 23 10:06:14 primary gnome-shell[769]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
  320. Dec 23 10:06:14 primary gnome-shell[769]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55e5b2cc4fd0.
  321. Dec 23 10:06:14 primary gnome-shell[769]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
  322. Dec 23 10:06:14 primary gnome-shell[769]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55e5b2cc67d0.
  323. Dec 23 10:06:14 primary gnome-shell[769]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
  324. Dec 23 10:06:14 primary gnome-shell[769]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x55e5b2c8cc20.
  325. Dec 23 10:06:14 primary gnome-shell[769]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
  326. Dec 23 10:06:14 primary gnome-shell[769]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55e5b2ccf0a0.
  327. Dec 23 10:06:14 primary gnome-shell[769]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
  328. Dec 23 10:06:14 primary gnome-shell[769]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55e5b2ccf0a0.
  329. Dec 23 10:06:14 primary gnome-shell[769]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
  330. Dec 23 10:06:14 primary gnome-shell[769]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55e5b2ccf0a0.
  331. Dec 23 10:06:14 primary gnome-shell[769]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
  332. Dec 23 10:06:14 primary gnome-shell[769]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55e5b2cd04a0.
  333. Dec 23 10:06:14 primary gnome-shell[769]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
  334. Dec 23 10:06:14 primary gnome-shell[769]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x55e5b2c8cc20.
  335. Dec 23 10:06:14 primary gnome-shell[769]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
  336. Dec 23 10:06:14 primary gnome-shell[769]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55e5b2cd88a0.
  337. Dec 23 10:06:14 primary gnome-shell[769]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
  338. Dec 23 10:06:14 primary gnome-shell[769]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55e5b2cd88a0.
  339. Dec 23 10:06:14 primary gnome-shell[769]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
  340. Dec 23 10:06:14 primary gnome-shell[769]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55e5b2cd88a0.
  341. Dec 23 10:06:14 primary gnome-shell[769]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
  342. Dec 23 10:06:14 primary gnome-shell[769]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55e5b2cdb180.
  343. Dec 23 10:06:14 primary gnome-shell[769]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
  344. Dec 23 10:06:14 primary gnome-shell[769]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x55e5b2c8cc20.
  345. Dec 23 10:06:14 primary gnome-shell[769]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
  346. Dec 23 10:06:14 primary gnome-shell[769]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55e5b2ce0db0.
  347. Dec 23 10:06:14 primary gnome-shell[769]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
  348. Dec 23 10:06:14 primary gnome-shell[769]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55e5b2ce0db0.
  349. Dec 23 10:06:14 primary gnome-shell[769]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
  350. Dec 23 10:06:14 primary gnome-shell[769]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55e5b2ce0db0.
  351. Dec 23 10:06:14 primary gnome-shell[769]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
  352. Dec 23 10:06:14 primary gnome-shell[769]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55e5b2ce5e40.
  353. Dec 23 10:06:14 primary gnome-shell[769]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
  354. Dec 23 10:06:14 primary gnome-shell[769]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x55e5b2c8cc20.
  355. Dec 23 10:06:14 primary gnome-shell[769]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
  356. Dec 23 10:06:14 primary gnome-shell[769]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55e5b2cf14b0.
  357. Dec 23 10:06:14 primary gnome-shell[769]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
  358. Dec 23 10:06:14 primary gnome-shell[769]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55e5b2cf14b0.
  359. Dec 23 10:06:14 primary gnome-shell[769]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
  360. Dec 23 10:06:14 primary gnome-shell[769]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55e5b2cf14b0.
  361. Dec 23 10:06:14 primary gnome-shell[769]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
  362. Dec 23 10:06:14 primary gnome-shell[769]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55e5b2cf8050.
  363. Dec 23 10:06:14 primary gnome-shell[769]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
  364. Dec 23 10:06:14 primary gnome-shell[769]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x55e5b2c8cc20.
  365. Dec 23 10:06:14 primary gnome-shell[769]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
  366. Dec 23 10:06:14 primary gnome-shell[769]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55e5b2d01ba0.
  367. Dec 23 10:06:14 primary gnome-shell[769]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
  368. Dec 23 10:06:14 primary gnome-shell[769]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55e5b2d01ba0.
  369. Dec 23 10:06:14 primary gnome-shell[769]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
  370. Dec 23 10:06:14 primary gnome-shell[769]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55e5b2d01ba0.
  371. Dec 23 10:06:14 primary gnome-shell[769]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
  372. Dec 23 10:06:14 primary gnome-shell[769]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55e5b2d05d30.
  373. Dec 23 10:06:14 primary gnome-shell[769]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
  374. Dec 23 10:06:14 primary gnome-shell[769]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x55e5b2c8cc20.
  375. Dec 23 10:06:14 primary gnome-shell[769]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
  376. Dec 23 10:06:14 primary gnome-shell[769]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55e5b2d0cce0.
  377. Dec 23 10:06:14 primary gnome-shell[769]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
  378. Dec 23 10:06:14 primary gnome-shell[769]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55e5b2d0cce0.
  379. Dec 23 10:06:14 primary gnome-shell[769]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
  380. Dec 23 10:06:14 primary gnome-shell[769]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55e5b2d0cce0.
  381. Dec 23 10:06:14 primary gnome-shell[769]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
  382. Dec 23 10:06:14 primary gnome-shell[769]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55e5b2d0ec20.
  383. Dec 23 10:06:14 primary gnome-shell[769]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
  384. Dec 23 10:06:14 primary gnome-shell[769]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x55e5b2c8cc20.
  385. Dec 23 10:06:14 primary gnome-shell[769]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
  386. Dec 23 10:06:14 primary gnome-shell[769]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55e5b2d14310.
  387. Dec 23 10:06:14 primary gnome-shell[769]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
  388. Dec 23 10:06:14 primary gnome-shell[769]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55e5b2d14310.
  389. Dec 23 10:06:14 primary gnome-shell[769]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
  390. Dec 23 10:06:14 primary gnome-shell[769]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55e5b2d14310.
  391. Dec 23 10:06:14 primary gnome-shell[769]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
  392. Dec 23 10:06:14 primary gnome-shell[769]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55e5b2d162a0.
  393. Dec 23 10:06:14 primary gnome-shell[769]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
  394. Dec 23 10:06:14 primary gnome-shell[769]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x55e5b2c8cc20.
  395. Dec 23 10:06:14 primary gnome-shell[769]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
  396. Dec 23 10:06:14 primary gnome-shell[769]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55e5b2d1c0e0.
  397. Dec 23 10:06:14 primary gnome-shell[769]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
  398. Dec 23 10:06:14 primary gnome-shell[769]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55e5b2d1c0e0.
  399. Dec 23 10:06:14 primary gnome-shell[769]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
  400. Dec 23 10:06:14 primary gnome-shell[769]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55e5b2d1c0e0.
  401. Dec 23 10:06:14 primary gnome-shell[769]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
  402. Dec 23 10:06:14 primary gnome-shell[769]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55e5b2d1dfb0.
  403. Dec 23 10:06:14 primary gnome-shell[769]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
  404. Dec 23 10:06:14 primary gnome-shell[769]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x55e5b2c8cc20.
  405. Dec 23 10:06:14 primary gnome-shell[769]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
  406. Dec 23 10:06:14 primary gnome-shell[769]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55e5b2d24650.
  407. Dec 23 10:06:14 primary gnome-shell[769]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
  408. Dec 23 10:06:14 primary gnome-shell[769]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55e5b2d24650.
  409. Dec 23 10:06:14 primary gnome-shell[769]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
  410. Dec 23 10:06:14 primary gnome-shell[769]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55e5b2d24650.
  411. Dec 23 10:06:14 primary gnome-shell[769]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
  412. Dec 23 10:06:14 primary gnome-shell[769]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55e5b2d268d0.
  413. Dec 23 10:06:14 primary gnome-shell[769]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
  414. Dec 23 10:06:14 primary gnome-shell[769]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x55e5b2c8cc20.
  415. Dec 23 10:06:14 primary gnome-shell[769]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
  416. Dec 23 10:06:14 primary gnome-shell[769]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55e5b2d2bb50.
  417. Dec 23 10:06:14 primary gnome-shell[769]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
  418. Dec 23 10:06:14 primary gnome-shell[769]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55e5b2d2bb50.
  419. Dec 23 10:06:14 primary gnome-shell[769]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
  420. Dec 23 10:06:14 primary gnome-shell[769]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55e5b2d2bb50.
  421. Dec 23 10:06:14 primary gnome-shell[769]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
  422. Dec 23 10:06:14 primary gnome-shell[769]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55e5b2d2ce00.
  423. Dec 23 10:06:14 primary gnome-shell[769]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
  424. Dec 23 10:06:14 primary gnome-shell[769]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x55e5b2c8cc20.
  425. Dec 23 10:06:14 primary gnome-shell[769]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
  426. Dec 23 10:06:14 primary gnome-shell[769]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55e5b2d35190.
  427. Dec 23 10:06:14 primary gnome-shell[769]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
  428. Dec 23 10:06:14 primary gnome-shell[769]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55e5b2d35190.
  429. Dec 23 10:06:14 primary gnome-shell[769]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
  430. Dec 23 10:06:14 primary gnome-shell[769]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55e5b2d35190.
  431. Dec 23 10:06:14 primary gnome-shell[769]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
  432. Dec 23 10:06:14 primary gnome-shell[769]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55e5b2d37580.
  433. Dec 23 10:06:14 primary gnome-shell[769]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
  434. Dec 23 10:06:14 primary gnome-shell[769]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x55e5b2c8cc20.
  435. Dec 23 10:06:14 primary gnome-shell[769]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked.
  436. Dec 23 10:06:14 primary gnome-shell[769]: The offending callback was set_container(), a vfunc.
  437. Dec 23 10:06:14 primary systemd[573]: run-docker-netns-2b8a30899f73.mount: Succeeded.
  438. Dec 23 10:06:14 primary systemd[573]: var-lib-docker-overlay2-5d6afe0c32b906027657440ad1e103105f4b7290f06918587b1a85ad8cb7a586-merged.mount: Succeeded.
  439. Dec 23 10:06:14 primary systemd[573]: org.gnome.SettingsDaemon.Power.service: Succeeded.
  440. Dec 23 10:06:14 primary systemd[573]: Stopped GNOME power management service.
  441. Dec 23 10:06:14 primary systemd[573]: org.gnome.SettingsDaemon.Keyboard.service: Succeeded.
  442. Dec 23 10:06:14 primary systemd[573]: Stopped GNOME keyboard configuration service.
  443. Dec 23 10:06:14 primary systemd[573]: org.gnome.SettingsDaemon.Wacom.service: Succeeded.
  444. Dec 23 10:06:14 primary systemd[573]: Stopped GNOME Wacom tablet support service.
  445. Dec 23 10:06:14 primary gnome-shell[1179]: (EE) failed to read Wayland events: Connection reset by peer
  446. Dec 23 10:06:14 primary gnome-session[184870]: Unable to init server: Could not connect: Connection refused
  447. Dec 23 10:06:14 primary gnome-session-f[184870]: Cannot open display:
  448. Dec 23 10:06:14 primary systemd[573]: org.gnome.SettingsDaemon.MediaKeys.service: Succeeded.
  449. Dec 23 10:06:14 primary systemd[573]: Stopped GNOME keyboard shortcuts service.
  450. Dec 23 10:06:14 primary systemd[573]: org.gnome.SettingsDaemon.Color.service: Succeeded.
  451. Dec 23 10:06:14 primary systemd[573]: Stopped GNOME color management service.
  452. Dec 23 10:06:14 primary systemd[573]: Stopped target GNOME Session is initialized.
  453. Dec 23 10:06:14 primary systemd[573]: Stopped target GNOME Shell.
  454. Dec 23 10:06:14 primary unknown[184969]: Couldn't connect to session bus: Error receiving data: Connection reset by peer
  455. Dec 23 10:06:14 primary systemd[573]: [email protected]: Succeeded.
  456. Dec 23 10:06:14 primary systemd[573]: Stopped GNOME Session Manager (session: gnome).
  457. Dec 23 10:06:14 primary systemd[573]: Removed slice app-gnome\x2dsession\x2dmanager.slice.
  458. Dec 23 10:06:14 primary systemd[573]: [email protected]: Succeeded.
  459. Dec 23 10:06:14 primary systemd[573]: Stopped GNOME Shell on Wayland.
  460. Dec 23 10:06:14 primary systemd[573]: [email protected]: Consumed 6min 6.950s CPU time.
  461. Dec 23 10:06:14 primary systemd[573]: Removed slice User Core Session Slice.
  462. Dec 23 10:06:14 primary systemd[573]: session.slice: Consumed 6min 29.422s CPU time.
  463. Dec 23 10:06:14 primary systemd[573]: Stopped target GNOME Session Manager is ready.
  464. Dec 23 10:06:14 primary systemd[573]: Stopped target Tasks to be run before GNOME Session starts.
  465. Dec 23 10:06:14 primary systemd[573]: Stopped target Session services which should run early before the graphical session is brought up.
  466. Dec 23 10:06:14 primary systemd[573]: Reached target Shutdown running GNOME Session.
  467. Dec 23 10:06:14 primary systemd[573]: Starting Restart DBus after GNOME Session shutdown...
  468. Dec 23 10:06:14 primary systemd[573]: Stopping OpenSSH Agent...
  469. Dec 23 10:06:14 primary systemd[573]: ssh-agent.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
  470. Dec 23 10:06:14 primary systemd[573]: Stopped target Shutdown running GNOME Session.
  471. Dec 23 10:06:14 primary systemd[573]: Started Restart DBus after GNOME Session shutdown.
  472. Dec 23 10:06:14 primary agent-launch[185009]: dbus-update-activation-environment: error: unable to connect to D-Bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
  473. Dec 23 10:06:14 primary systemd[573]: ssh-agent.service: Control process exited, code=exited, status=71/OSERR
  474. Dec 23 10:06:14 primary systemd[573]: ssh-agent.service: Failed with result 'exit-code'.
  475. Dec 23 10:06:14 primary systemd[573]: Stopped OpenSSH Agent.
  476. Dec 23 10:06:14 primary systemd[573]: Stopped target Basic System.
  477. Dec 23 10:06:14 primary systemd[573]: Stopped target Paths.
  478. Dec 23 10:06:14 primary systemd[573]: Stopped target Sockets.
  479. Dec 23 10:06:14 primary systemd[573]: Stopped target Timers.
  480. Dec 23 10:06:14 primary gnome-session-c[185006]: Couldn't connect to session bus: Error receiving data: Connection reset by peer
  481. Dec 23 10:06:14 primary systemd[573]: dbus.socket: Succeeded.
  482. Dec 23 10:06:14 primary systemd[573]: Closed D-Bus User Message Bus Socket.
  483. Dec 23 10:06:14 primary systemd[573]: dirmngr.socket: Succeeded.
  484. Dec 23 10:06:14 primary systemd[573]: Closed GnuPG network certificate management daemon.
  485. Dec 23 10:06:14 primary systemd[573]: gpg-agent-browser.socket: Succeeded.
  486. Dec 23 10:06:14 primary systemd[573]: Closed GnuPG cryptographic agent and passphrase cache (access for web browsers).
  487. Dec 23 10:06:14 primary systemd[573]: gpg-agent-extra.socket: Succeeded.
  488. Dec 23 10:06:14 primary systemd[573]: Closed GnuPG cryptographic agent and passphrase cache (restricted).
  489. Dec 23 10:06:14 primary systemd[573]: gpg-agent-ssh.socket: Succeeded.
  490. Dec 23 10:06:14 primary systemd[573]: Closed GnuPG cryptographic agent (ssh-agent emulation).
  491. Dec 23 10:06:14 primary systemd[573]: gpg-agent.socket: Succeeded.
  492. Dec 23 10:06:14 primary systemd[573]: Closed GnuPG cryptographic agent and passphrase cache.
  493. Dec 23 10:06:14 primary systemd[573]: pipewire.socket: Succeeded.
  494. Dec 23 10:06:14 primary systemd[573]: Closed Multimedia System.
  495. Dec 23 10:06:14 primary systemd[573]: pk-debconf-helper.socket: Succeeded.
  496. Dec 23 10:06:14 primary systemd[573]: Closed debconf communication socket.
  497. Dec 23 10:06:14 primary systemd[573]: pulseaudio.socket: Succeeded.
  498. Dec 23 10:06:14 primary systemd[573]: Closed Sound System.
  499. Dec 23 10:06:14 primary systemd[573]: Removed slice User Application Slice.
  500. Dec 23 10:06:14 primary systemd[573]: app.slice: Consumed 40.939s CPU time.
  501. Dec 23 10:06:14 primary systemd[573]: Reached target Shutdown.
  502. Dec 23 10:06:14 primary systemd[573]: systemd-exit.service: Succeeded.
  503. Dec 23 10:06:14 primary systemd[573]: Finished Exit the Session.
  504. Dec 23 10:06:14 primary systemd[573]: Reached target Exit the Session.
  505. -- Boot d5b743aeac3741289068c59f298f5cca --
  506. Dec 23 10:06:33 primary systemd[563]: Queued start job for default target Main User Target.
  507. Dec 23 10:06:33 primary systemd[563]: Created slice User Application Slice.
  508. Dec 23 10:06:33 primary systemd[563]: Reached target Paths.
  509. Dec 23 10:06:33 primary systemd[563]: Reached target Timers.
  510. Dec 23 10:06:33 primary systemd[563]: Starting D-Bus User Message Bus Socket.
  511. Dec 23 10:06:33 primary systemd[563]: Listening on GnuPG network certificate management daemon.
  512. Dec 23 10:06:33 primary systemd[563]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers).
  513. Dec 23 10:06:33 primary systemd[563]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
  514. Dec 23 10:06:33 primary systemd[563]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
  515. Dec 23 10:06:33 primary systemd[563]: Listening on GnuPG cryptographic agent and passphrase cache.
  516. Dec 23 10:06:33 primary systemd[563]: Listening on Multimedia System.
  517. Dec 23 10:06:33 primary systemd[563]: Listening on debconf communication socket.
  518. Dec 23 10:06:33 primary systemd[563]: Listening on Sound System.
  519. Dec 23 10:06:33 primary systemd[563]: Listening on D-Bus User Message Bus Socket.
  520. Dec 23 10:06:33 primary systemd[563]: Reached target Sockets.
  521. Dec 23 10:06:33 primary systemd[563]: Reached target Basic System.
  522. Dec 23 10:06:33 primary systemd[563]: Started Multimedia Service.
  523. Dec 23 10:06:33 primary systemd[563]: Starting Sound Service...
  524. Dec 23 10:06:33 primary systemd[563]: Starting Tracker metadata extractor...
  525. Dec 23 10:06:33 primary systemd[563]: Starting Tracker file system data miner...
  526. Dec 23 10:06:33 primary systemd[563]: Started D-Bus User Message Bus.
  527. Dec 23 10:06:33 primary tracker-miner-f[584]: Set scheduler policy to SCHED_IDLE
  528. Dec 23 10:06:33 primary tracker-miner-f[584]: Setting priority nice level to 19
  529. Dec 23 10:06:33 primary tracker-extract[583]: Set scheduler policy to SCHED_IDLE
  530. Dec 23 10:06:33 primary tracker-extract[583]: Setting priority nice level to 19
  531. Dec 23 10:06:33 primary pipewire[581]: Failed to receive portal pid: org.freedesktop.DBus.Error.NameHasNoOwner: Could not get PID of name 'org.freedesktop.portal.Desktop': no such name
  532. Dec 23 10:06:33 primary systemd[563]: Started Sound Service.
  533. Dec 23 10:06:33 primary dbus-daemon[593]: [session uid=1000 pid=593] Activating via systemd: service name='org.gtk.vfs.Daemon' unit='gvfs-daemon.service' requested by ':1.3' (uid=1000 pid=584 comm="/usr/libexec/tracker-miner-fs ")
  534. Dec 23 10:06:33 primary systemd[563]: Starting Virtual filesystem service...
  535. Dec 23 10:06:33 primary dbus-daemon[593]: [session uid=1000 pid=593] Successfully activated service 'org.gtk.vfs.Daemon'
  536. Dec 23 10:06:33 primary systemd[563]: Started Virtual filesystem service.
  537. Dec 23 10:06:33 primary dbus-daemon[593]: [session uid=1000 pid=593] Activating via systemd: service name='org.gtk.vfs.UDisks2VolumeMonitor' unit='gvfs-udisks2-volume-monitor.service' requested by ':1.3' (uid=1000 pid=584 comm="/usr/libexec/tracker-miner-fs ")
  538. Dec 23 10:06:33 primary systemd[563]: Starting Virtual filesystem service - disk device monitor...
  539. Dec 23 10:06:33 primary systemd[563]: Created slice app-gnome\x2dsession\x2dmanager.slice.
  540. Dec 23 10:06:33 primary systemd[563]: Created slice User Core Session Slice.
  541. Dec 23 10:06:33 primary systemd[563]: Reached target GNOME Wayland Session.
  542. Dec 23 10:06:33 primary systemd[563]: Reached target GNOME Shell.
  543. Dec 23 10:06:33 primary systemd[563]: Starting Monitor Session leader for GNOME Session...
  544. Dec 23 10:06:33 primary systemd[563]: Started OpenSSH Agent.
  545. Dec 23 10:06:33 primary systemd[563]: Reached target Session services which should run early before the graphical session is brought up.
  546. Dec 23 10:06:33 primary systemd[563]: Started Monitor Session leader for GNOME Session.
  547. Dec 23 10:06:33 primary systemd[563]: Reached target Tasks to be run before GNOME Session starts.
  548. Dec 23 10:06:33 primary systemd[563]: Starting GNOME Session Manager (session: gnome)...
  549. Dec 23 10:06:33 primary agent-launch[726]: dbus-update-activation-environment: setting SSH_AUTH_SOCK=/run/user/1000/openssh_agent
  550. Dec 23 10:06:33 primary agent-launch[726]: dbus-update-activation-environment: setting SSH_AGENT_LAUNCHER=openssh
  551. Dec 23 10:06:33 primary agent-launch[722]: SSH_AUTH_SOCK=/run/user/1000/openssh_agent; export SSH_AUTH_SOCK;
  552. Dec 23 10:06:33 primary agent-launch[722]: echo Agent pid 722;
  553. Dec 23 10:06:33 primary systemd[563]: app-gnome-gnome\x2dkeyring\x2dpkcs11-740.scope: Failed to add PIDs to scope's control group: No such process
  554. Dec 23 10:06:33 primary systemd[563]: app-gnome-gnome\x2dkeyring\x2dpkcs11-740.scope: Failed with result 'resources'.
  555. Dec 23 10:06:33 primary systemd[563]: Failed to start Application launched by gnome-session-binary.
  556. Dec 23 10:06:33 primary systemd[563]: Started Application launched by gnome-session-binary.
  557. Dec 23 10:06:33 primary systemd[563]: Started Application launched by gnome-session-binary.
  558. Dec 23 10:06:33 primary gnome-keyring-ssh.desktop[746]: SSH_AUTH_SOCK=/run/user/1000/keyring/ssh
  559. Dec 23 10:06:33 primary gnome-keyring-secrets.desktop[747]: SSH_AUTH_SOCK=/run/user/1000/keyring/ssh
  560. Dec 23 10:06:33 primary systemd[563]: Started GNOME Session Manager (session: gnome).
  561. Dec 23 10:06:33 primary systemd[563]: Reached target GNOME Session Manager is ready.
  562. Dec 23 10:06:33 primary systemd[563]: Starting GNOME Shell on Wayland...
  563. Dec 23 10:06:33 primary systemd[563]: Starting GNOME Shell on X11...
  564. Dec 23 10:06:33 primary systemd[563]: app-gnome-gnome\x2dkeyring\x2dsecrets-742.scope: Succeeded.
  565. Dec 23 10:06:33 primary systemd[563]: app-gnome-gnome\x2dkeyring\x2dssh-744.scope: Succeeded.
  566. Dec 23 10:06:33 primary gnome-session[724]: gnome-session-binary[724]: GnomeDesktop-WARNING: Could not create transient scope for PID 751: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Process with ID 751 does not exist.
  567. Dec 23 10:06:33 primary gnome-session-binary[724]: GnomeDesktop-WARNING: Could not create transient scope for PID 751: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Process with ID 751 does not exist.
  568. Dec 23 10:06:33 primary gnome-session[724]: gnome-session-binary[724]: GnomeDesktop-WARNING: Could not create transient scope for PID 757: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Process with ID 757 does not exist.
  569. Dec 23 10:06:33 primary gnome-session-binary[724]: GnomeDesktop-WARNING: Could not create transient scope for PID 757: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Process with ID 757 does not exist.
  570. Dec 23 10:06:33 primary systemd[563]: Started Application launched by gnome-session-binary.
  571. Dec 23 10:06:33 primary systemd[563]: [email protected]: Control process exited, code=exited, status=2/INVALIDARGUMENT
  572. Dec 23 10:06:33 primary systemd[563]: [email protected]: Skipped due to 'exec-condition'.
  573. Dec 23 10:06:33 primary systemd[563]: Condition check resulted in GNOME Shell on X11 being skipped.
  574. Dec 23 10:06:33 primary systemd[563]: [email protected]: Scheduled restart job, restart counter is at 1.
  575. Dec 23 10:06:33 primary systemd[563]: Stopped GNOME Shell on X11.
  576. Dec 23 10:06:33 primary systemd[563]: Starting GNOME Shell on X11...
  577. Dec 23 10:06:33 primary systemd[563]: [email protected]: Control process exited, code=exited, status=2/INVALIDARGUMENT
  578. Dec 23 10:06:33 primary systemd[563]: [email protected]: Skipped due to 'exec-condition'.
  579. Dec 23 10:06:33 primary systemd[563]: Condition check resulted in GNOME Shell on X11 being skipped.
  580. Dec 23 10:06:33 primary systemd[563]: [email protected]: Scheduled restart job, restart counter is at 2.
  581. Dec 23 10:06:33 primary systemd[563]: Stopped GNOME Shell on X11.
  582. Dec 23 10:06:33 primary systemd[563]: Starting GNOME Shell on X11...
  583. Dec 23 10:06:33 primary systemd[563]: [email protected]: Control process exited, code=exited, status=2/INVALIDARGUMENT
  584. Dec 23 10:06:33 primary systemd[563]: [email protected]: Skipped due to 'exec-condition'.
  585. Dec 23 10:06:33 primary systemd[563]: Condition check resulted in GNOME Shell on X11 being skipped.
  586. Dec 23 10:06:33 primary systemd[563]: [email protected]: Scheduled restart job, restart counter is at 3.
  587. Dec 23 10:06:33 primary systemd[563]: Stopped GNOME Shell on X11.
  588. Dec 23 10:06:33 primary systemd[563]: [email protected]: Start request repeated too quickly.
  589. Dec 23 10:06:33 primary systemd[563]: [email protected]: Skipped due to 'exec-condition'.
  590. Dec 23 10:06:33 primary systemd[563]: Condition check resulted in GNOME Shell on X11 being skipped.
  591. Dec 23 10:06:34 primary dbus-daemon[593]: [session uid=1000 pid=593] Successfully activated service 'org.gtk.vfs.UDisks2VolumeMonitor'
  592. Dec 23 10:06:34 primary systemd[563]: Started Virtual filesystem service - disk device monitor.
  593. Dec 23 10:06:34 primary dbus-daemon[593]: [session uid=1000 pid=593] Activating via systemd: service name='org.gtk.vfs.GoaVolumeMonitor' unit='gvfs-goa-volume-monitor.service' requested by ':1.3' (uid=1000 pid=584 comm="/usr/libexec/tracker-miner-fs ")
  594. Dec 23 10:06:34 primary systemd[563]: Starting Virtual filesystem service - GNOME Online Accounts monitor...
  595. Dec 23 10:06:34 primary dbus-daemon[593]: [session uid=1000 pid=593] Activating service name='org.gnome.OnlineAccounts' requested by ':1.24' (uid=1000 pid=772 comm="/usr/libexec/gvfs-goa-volume-monitor ")
  596. Dec 23 10:06:34 primary gnome-shell[756]: pci id for fd 9: 1234:1111, driver (null)
  597. Dec 23 10:06:34 primary gnome-shell[756]: MESA-LOADER: failed to open bochs-drm: /usr/lib/dri/bochs-drm_dri.so: cannot open shared object file: No such file or directory (search paths /usr/lib/x86_64-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri)
  598. Dec 23 10:06:34 primary gnome-shell[756]: failed to load driver: bochs-drm
  599. Dec 23 10:06:34 primary goa-daemon[789]: goa-daemon version 3.38.0 starting
  600. Dec 23 10:06:34 primary dbus-daemon[593]: [session uid=1000 pid=593] Activating service name='org.gnome.Identity' requested by ':1.26' (uid=1000 pid=789 comm="/usr/libexec/goa-daemon ")
  601. Dec 23 10:06:34 primary dbus-daemon[593]: [session uid=1000 pid=593] Successfully activated service 'org.gnome.OnlineAccounts'
  602. Dec 23 10:06:34 primary dbus-daemon[593]: [session uid=1000 pid=593] Successfully activated service 'org.gnome.Identity'
  603. Dec 23 10:06:34 primary dbus-daemon[593]: [session uid=1000 pid=593] Successfully activated service 'org.gtk.vfs.GoaVolumeMonitor'
  604. Dec 23 10:06:34 primary systemd[563]: Started Virtual filesystem service - GNOME Online Accounts monitor.
  605. Dec 23 10:06:34 primary dbus-daemon[593]: [session uid=1000 pid=593] Activating via systemd: service name='org.gtk.vfs.AfcVolumeMonitor' unit='gvfs-afc-volume-monitor.service' requested by ':1.3' (uid=1000 pid=584 comm="/usr/libexec/tracker-miner-fs ")
  606. Dec 23 10:06:34 primary systemd[563]: Starting Virtual filesystem service - Apple File Conduit monitor...
  607. Dec 23 10:06:34 primary dbus-daemon[593]: [session uid=1000 pid=593] Successfully activated service 'org.gtk.vfs.AfcVolumeMonitor'
  608. Dec 23 10:06:34 primary systemd[563]: Started Virtual filesystem service - Apple File Conduit monitor.
  609. Dec 23 10:06:34 primary dbus-daemon[593]: [session uid=1000 pid=593] Activating via systemd: service name='org.gtk.vfs.MTPVolumeMonitor' unit='gvfs-mtp-volume-monitor.service' requested by ':1.3' (uid=1000 pid=584 comm="/usr/libexec/tracker-miner-fs ")
  610. Dec 23 10:06:34 primary systemd[563]: Starting Virtual filesystem service - Media Transfer Protocol monitor...
  611. Dec 23 10:06:34 primary dbus-daemon[593]: [session uid=1000 pid=593] Successfully activated service 'org.gtk.vfs.MTPVolumeMonitor'
  612. Dec 23 10:06:34 primary systemd[563]: Started Virtual filesystem service - Media Transfer Protocol monitor.
  613. Dec 23 10:06:34 primary dbus-daemon[593]: [session uid=1000 pid=593] Activating via systemd: service name='org.gtk.vfs.GPhoto2VolumeMonitor' unit='gvfs-gphoto2-volume-monitor.service' requested by ':1.3' (uid=1000 pid=584 comm="/usr/libexec/tracker-miner-fs ")
  614. Dec 23 10:06:34 primary systemd[563]: Starting Virtual filesystem service - digital camera monitor...
  615. Dec 23 10:06:34 primary dbus-daemon[593]: [session uid=1000 pid=593] Successfully activated service 'org.gtk.vfs.GPhoto2VolumeMonitor'
  616. Dec 23 10:06:34 primary systemd[563]: Started Virtual filesystem service - digital camera monitor.
  617. Dec 23 10:06:34 primary systemd[563]: Started Tracker metadata extractor.
  618. Dec 23 10:06:34 primary gnome-shell[756]: Failed to initialize accelerated iGPU/dGPU framebuffer sharing: Do not want to use software renderer (llvmpipe (LLVM 11.0.1, 128 bits)), falling back to CPU copy path
  619. Dec 23 10:06:34 primary gnome-shell[756]: Boot VGA GPU /dev/dri/card0 selected as primary
  620. Dec 23 10:06:34 primary dbus-daemon[593]: [session uid=1000 pid=593] Activating via systemd: service name='org.freedesktop.Tracker1' unit='tracker-store.service' requested by ':1.3' (uid=1000 pid=584 comm="/usr/libexec/tracker-miner-fs ")
  621. Dec 23 10:06:34 primary systemd[563]: Starting Tracker metadata database store and lookup manager...
  622. Dec 23 10:06:34 primary dbus-daemon[593]: [session uid=1000 pid=593] Successfully activated service 'org.freedesktop.Tracker1'
  623. Dec 23 10:06:34 primary systemd[563]: Started Tracker metadata database store and lookup manager.
  624. Dec 23 10:06:34 primary systemd[563]: Started Tracker file system data miner.
  625. Dec 23 10:06:34 primary systemd[563]: Reached target Main User Target.
  626. Dec 23 10:06:34 primary gnome-shell[756]: Failed to set hardware cursor (drmModeSetCursor failed: No such device or address), using OpenGL from now on
  627. Dec 23 10:06:34 primary gnome-shell[756]: Disabling DMA buffer screen sharing for driver 'bochs-drm'.
  628. Dec 23 10:06:34 primary systemd[563]: run-docker-runtime\x2drunc-moby-7460e503a5e4fd5d5846075f46e3271ef00d423c2c1677d9c5c4304221502b7c-runc.3Xl9yW.mount: Succeeded.
  629. Dec 23 10:06:35 primary systemd[563]: run-docker-runtime\x2drunc-moby-2d1cc0753b7a34a7b07eb6ed9ae46c11666b826d854cb275b4a6061fe1fafe44-runc.m3MoGm.mount: Succeeded.
  630. Dec 23 10:06:35 primary systemd[563]: run-docker-runtime\x2drunc-moby-c465e4123ebd71cc813a5d6e059c110e5548e013beb3b222b043927ccc4ae8f5-runc.zvvxuc.mount: Succeeded.
  631. Dec 23 10:06:35 primary gnome-shell[756]: Getting parental controls for user 1000
  632. Dec 23 10:06:35 primary systemd[563]: run-docker-runtime\x2drunc-moby-2da8ac201c0d22dd379334c69c3250743a4abef5cc683f97dc704df161f84f5a-runc.fnXuGc.mount: Succeeded.
  633. Dec 23 10:06:35 primary systemd[563]: run-docker-runtime\x2drunc-moby-bb194427d601496df44691e5dc34fa92fe52cf2911479738a1a1a2543f6d7037-runc.pt0PaH.mount: Succeeded.
  634. Dec 23 10:06:35 primary systemd[563]: run-docker-runtime\x2drunc-moby-9e94c9d2fde8d868edb173f56ef62c3f608794a7bc42f4cd8d06b2afd67a59b7-runc.2Yt0HW.mount: Succeeded.
  635. Dec 23 10:06:35 primary gnome-shell[756]: Unset XDG_SESSION_ID, getCurrentSessionProxy() called outside a user session. Asking logind directly.
  636. Dec 23 10:06:35 primary gnome-shell[756]: Will monitor session 1
  637. Dec 23 10:06:35 primary gnome-shell[756]: Called enable_unredirect_for_display while unredirection is enabled.
  638. Dec 23 10:06:35 primary dbus-daemon[593]: [session uid=1000 pid=593] Activating service name='org.freedesktop.portal.IBus' requested by ':1.33' (uid=1000 pid=1476 comm="ibus-daemon --panel disable ")
  639. Dec 23 10:06:35 primary dbus-daemon[593]: [session uid=1000 pid=593] Successfully activated service 'org.freedesktop.portal.IBus'
  640. Dec 23 10:06:35 primary dbus-daemon[593]: [session uid=1000 pid=593] Activating via systemd: service name='org.freedesktop.impl.portal.PermissionStore' unit='xdg-permission-store.service' requested by ':1.25' (uid=1000 pid=756 comm="/usr/bin/gnome-shell ")
  641. Dec 23 10:06:35 primary systemd[563]: Starting sandboxed app permission store...
  642. Dec 23 10:06:35 primary dbus-daemon[593]: [session uid=1000 pid=593] Activating service name='org.gnome.Shell.CalendarServer' requested by ':1.25' (uid=1000 pid=756 comm="/usr/bin/gnome-shell ")
  643. Dec 23 10:06:35 primary dbus-daemon[593]: [session uid=1000 pid=593] Successfully activated service 'org.freedesktop.impl.portal.PermissionStore'
  644. Dec 23 10:06:35 primary systemd[563]: Started sandboxed app permission store.
  645. Dec 23 10:06:35 primary dbus-daemon[593]: [session uid=1000 pid=593] Activating via systemd: service name='org.gnome.evolution.dataserver.Sources5' unit='evolution-source-registry.service' requested by ':1.38' (uid=1000 pid=1531 comm="/usr/libexec/gnome-shell-calendar-server ")
  646. Dec 23 10:06:35 primary systemd[563]: Starting Evolution source registry...
  647. Dec 23 10:06:36 primary dbus-daemon[593]: [session uid=1000 pid=593] Successfully activated service 'org.gnome.evolution.dataserver.Sources5'
  648. Dec 23 10:06:36 primary systemd[563]: Started Evolution source registry.
  649. Dec 23 10:06:36 primary dbus-daemon[593]: [session uid=1000 pid=593] Activating via systemd: service name='org.gnome.evolution.dataserver.Calendar8' unit='evolution-calendar-factory.service' requested by ':1.38' (uid=1000 pid=1531 comm="/usr/libexec/gnome-shell-calendar-server ")
  650. Dec 23 10:06:36 primary systemd[563]: Starting Evolution calendar service...
  651. Dec 23 10:06:36 primary dbus-daemon[593]: [session uid=1000 pid=593] Successfully activated service 'org.gnome.Shell.CalendarServer'
  652. Dec 23 10:06:36 primary gnome-shell[756]: Telepathy is not available, chat integration will be disabled.
  653. Dec 23 10:06:36 primary gnome-shell[756]: Warning: Hiding app because parental controls not yet initialised: firefox-esr.desktop
  654. Dec 23 10:06:36 primary gnome-shell[756]: Warning: Hiding app because parental controls not yet initialised: org.gnome.Evolution.desktop
  655. Dec 23 10:06:36 primary gnome-shell[756]: Warning: Hiding app because parental controls not yet initialised: rhythmbox.desktop
  656. Dec 23 10:06:36 primary gnome-shell[756]: Warning: Hiding app because parental controls not yet initialised: libreoffice-writer.desktop
  657. Dec 23 10:06:36 primary gnome-shell[756]: Warning: Hiding app because parental controls not yet initialised: org.gnome.Nautilus.desktop
  658. Dec 23 10:06:36 primary gnome-shell[756]: Warning: Hiding app because parental controls not yet initialised: org.gnome.Software.desktop
  659. Dec 23 10:06:36 primary gnome-shell[756]: Warning: Hiding app because parental controls not yet initialised: yelp.desktop
  660. Dec 23 10:06:36 primary gnome-shell[756]: Warning: Hiding app because parental controls not yet initialised: org.gnome.Terminal.desktop
  661. Dec 23 10:06:36 primary dbus-daemon[593]: [session uid=1000 pid=593] Successfully activated service 'org.gnome.evolution.dataserver.Calendar8'
  662. Dec 23 10:06:36 primary systemd[563]: Started Evolution calendar service.
  663. Dec 23 10:06:36 primary gnome-shell[756]: Warning: Hiding app because parental controls not yet initialised: gnome-control-center.desktop
  664. Dec 23 10:06:36 primary gnome-shell[756]: Warning: Hiding app because parental controls not yet initialised: org.gnome.Contacts.desktop
  665. Dec 23 10:06:36 primary gnome-shell[756]: Warning: Hiding app because parental controls not yet initialised: org.gnome.Documents.desktop
  666. Dec 23 10:06:36 primary gnome-shell[756]: Warning: Hiding app because parental controls not yet initialised: org.gnome.Nautilus.desktop
  667. Dec 23 10:06:36 primary gnome-shell[756]: Warning: Hiding app because parental controls not yet initialised: org.gnome.Calculator.desktop
  668. Dec 23 10:06:36 primary gnome-shell[756]: Warning: Hiding app because parental controls not yet initialised: org.gnome.Calendar.desktop
  669. Dec 23 10:06:36 primary gnome-shell[756]: Warning: Hiding app because parental controls not yet initialised: org.gnome.Characters.desktop
  670. Dec 23 10:06:36 primary gnome-shell[756]: Warning: Hiding app because parental controls not yet initialised: org.gnome.clocks.desktop
  671. Dec 23 10:06:36 primary gnome-shell[756]: Warning: Hiding app because parental controls not yet initialised: org.gnome.seahorse.Application.desktop
  672. Dec 23 10:06:36 primary gnome-shell[756]: Warning: Hiding app because parental controls not yet initialised: org.gnome.Software.desktop
  673. Dec 23 10:06:36 primary gnome-shell[756]: Warning: Hiding app because parental controls not yet initialised: org.gnome.Terminal.desktop
  674. Dec 23 10:06:36 primary dbus-daemon[593]: [session uid=1000 pid=593] Activating service name='ca.desrt.dconf' requested by ':1.40' (uid=1000 pid=1580 comm="/usr/libexec/evolution-calendar-factory ")
  675. Dec 23 10:06:36 primary dbus-daemon[593]: [session uid=1000 pid=593] Activating via systemd: service name='org.gnome.evolution.dataserver.AddressBook10' unit='evolution-addressbook-factory.service' requested by ':1.40' (uid=1000 pid=1580 comm="/usr/libexec/evolution-calendar-factory ")
  676. Dec 23 10:06:36 primary systemd[563]: Starting Evolution address book service...
  677. Dec 23 10:06:36 primary dbus-daemon[593]: [session uid=1000 pid=593] Successfully activated service 'ca.desrt.dconf'
  678. Dec 23 10:06:36 primary dbus-daemon[593]: [session uid=1000 pid=593] Activating service name='org.gnome.Shell.Notifications' requested by ':1.25' (uid=1000 pid=756 comm="/usr/bin/gnome-shell ")
  679. Dec 23 10:06:36 primary at-spi-dbus-bus.desktop[762]: dbus-daemon[762]: Activating service name='org.a11y.atspi.Registry' requested by ':1.0' (uid=1000 pid=756 comm="/usr/bin/gnome-shell ")
  680. Dec 23 10:06:36 primary at-spi-dbus-bus.desktop[762]: dbus-daemon[762]: Successfully activated service 'org.a11y.atspi.Registry'
  681. Dec 23 10:06:36 primary at-spi-dbus-bus.desktop[1617]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
  682. Dec 23 10:06:36 primary systemd[563]: Started GNOME Shell on Wayland.
  683. Dec 23 10:06:36 primary systemd[563]: Reached target GNOME Session is initialized.
  684. Dec 23 10:06:36 primary systemd[563]: GNOME session X11 services is not active.
  685. Dec 23 10:06:36 primary systemd[563]: Dependency failed for GNOME XSettings service.
  686. Dec 23 10:06:36 primary systemd[563]: org.gnome.SettingsDaemon.XSettings.service: Job org.gnome.SettingsDaemon.XSettings.service/start failed with result 'dependency'.
  687. Dec 23 10:06:36 primary systemd[563]: gnome-session-x11-services-ready.target: Job gnome-session-x11-services-ready.target/verify-active failed with result 'dependency'.
  688. Dec 23 10:06:36 primary systemd[563]: Reached target GNOME Session (session: gnome).
  689. Dec 23 10:06:36 primary systemd[563]: Reached target GNOME XSettings target.
  690. Dec 23 10:06:36 primary systemd[563]: Starting Signal initialization done to GNOME Session Manager...
  691. Dec 23 10:06:36 primary systemd[563]: Starting GNOME accessibility service...
  692. Dec 23 10:06:36 primary systemd[563]: Starting GNOME color management service...
  693. Dec 23 10:06:36 primary systemd[563]: Starting GNOME date & time service...
  694. Dec 23 10:06:36 primary systemd[563]: Starting GNOME maintenance of expirable data service...
  695. Dec 23 10:06:36 primary systemd[563]: Starting GNOME keyboard configuration service...
  696. Dec 23 10:06:36 primary systemd[563]: Starting GNOME keyboard shortcuts service...
  697. Dec 23 10:06:36 primary systemd[563]: Starting GNOME power management service...
  698. Dec 23 10:06:36 primary dbus-daemon[593]: [session uid=1000 pid=593] Successfully activated service 'org.gnome.evolution.dataserver.AddressBook10'
  699. Dec 23 10:06:36 primary systemd[563]: Starting GNOME printer notifications service...
  700. Dec 23 10:06:36 primary systemd[563]: Starting GNOME RFKill support service...
  701. Dec 23 10:06:36 primary systemd[563]: Starting GNOME FreeDesktop screensaver service...
  702. Dec 23 10:06:36 primary systemd[563]: Starting GNOME file sharing service...
  703. Dec 23 10:06:36 primary systemd[563]: Starting GNOME smartcard service...
  704. Dec 23 10:06:36 primary systemd[563]: Starting GNOME sound sample caching service...
  705. Dec 23 10:06:36 primary systemd[563]: Starting GNOME USB protection service...
  706. Dec 23 10:06:36 primary systemd[563]: Starting GNOME Wacom tablet support service...
  707. Dec 23 10:06:36 primary systemd[563]: Started Evolution address book service.
  708. Dec 23 10:06:36 primary gnome-session-binary[724]: Entering running state
  709. Dec 23 10:06:36 primary at-spi2-registr[1617]: Failed to register client: GDBus.Error:org.gnome.SessionManager.AlreadyRegistered: Unable to register client
  710. Dec 23 10:06:36 primary at-spi2-registr[1617]: Unable to register client with session manager
  711. Dec 23 10:06:36 primary systemd[563]: gnome-session-signal-init.service: Succeeded.
  712. Dec 23 10:06:36 primary systemd[563]: Finished Signal initialization done to GNOME Session Manager.
  713. Dec 23 10:06:36 primary gnome-session[724]: gnome-session-binary[724]: GnomeDesktop-WARNING: Could not create transient scope for PID 1675: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Process with ID 1675 does not exist.
  714. Dec 23 10:06:36 primary gnome-session-binary[724]: GnomeDesktop-WARNING: Could not create transient scope for PID 1675: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Process with ID 1675 does not exist.
  715. Dec 23 10:06:36 primary systemd[563]: Started GNOME maintenance of expirable data service.
  716. Dec 23 10:06:36 primary systemd[563]: Started GNOME file sharing service.
  717. Dec 23 10:06:36 primary systemd[563]: Started GNOME FreeDesktop screensaver service.
  718. Dec 23 10:06:36 primary systemd[563]: Started GNOME smartcard service.
  719. Dec 23 10:06:36 primary systemd[563]: Started GNOME USB protection service.
  720. Dec 23 10:06:36 primary systemd[563]: Started GNOME RFKill support service.
  721. Dec 23 10:06:36 primary systemd[563]: Started Application launched by gnome-session-binary.
  722. Dec 23 10:06:36 primary systemd[563]: Started Application launched by gnome-session-binary.
  723. Dec 23 10:06:36 primary systemd[563]: Started Application launched by gnome-session-binary.
  724. Dec 23 10:06:36 primary systemd[563]: Started Application launched by gnome-session-binary.
  725. Dec 23 10:06:36 primary systemd[563]: Started Application launched by gnome-session-binary.
  726. Dec 23 10:06:36 primary systemd[563]: Reached target GNOME maintenance of expirable data target.
  727. Dec 23 10:06:36 primary systemd[563]: Reached target GNOME RFKill support target.
  728. Dec 23 10:06:36 primary systemd[563]: Reached target GNOME FreeDesktop screensaver target.
  729. Dec 23 10:06:36 primary systemd[563]: Reached target GNOME file sharing target.
  730. Dec 23 10:06:36 primary systemd[563]: Reached target GNOME smartcard target.
  731. Dec 23 10:06:36 primary systemd[563]: Reached target GNOME USB protection target.
  732. Dec 23 10:06:36 primary systemd[563]: Started GNOME sound sample caching service.
  733. Dec 23 10:06:36 primary systemd[563]: Reached target GNOME sound sample caching target.
  734. Dec 23 10:06:36 primary systemd[563]: app-gnome-user\x2ddirs\x2dupdate\x2dgtk-1691.scope: Succeeded.
  735. Dec 23 10:06:37 primary systemd[563]: Started GNOME accessibility service.
  736. Dec 23 10:06:37 primary systemd[563]: Reached target GNOME accessibility target.
  737. Dec 23 10:06:37 primary dbus-daemon[593]: [session uid=1000 pid=593] Successfully activated service 'org.gnome.Shell.Notifications'
  738. Dec 23 10:06:37 primary systemd[563]: Started GNOME date & time service.
  739. Dec 23 10:06:37 primary systemd[563]: Reached target GNOME date & time target.
  740. Dec 23 10:06:37 primary systemd[563]: app-gnome-im\x2dlaunch-1703.scope: Succeeded.
  741. Dec 23 10:06:37 primary systemd[563]: Started GNOME printer notifications service.
  742. Dec 23 10:06:37 primary systemd[563]: Reached target GNOME printer notifications target.
  743. Dec 23 10:06:37 primary gnome-shell[756]: Error looking up permission: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for geolocation
  744. Dec 23 10:06:37 primary gsd-usb-protect[1668]: Failed to fetch USBGuard parameters: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.usbguard1 was not provided by any .service files
  745. Dec 23 10:06:37 primary gnome-shell[756]: Removing a network device that was not added
  746. Dec 23 10:06:37 primary gnome-shell[1101]: glamor: 'wl_drm' not supported
  747. Dec 23 10:06:37 primary gnome-shell[1101]: Missing Wayland requirements for glamor GBM backend
  748. Dec 23 10:06:37 primary gnome-shell[1101]: Failed to initialize glamor, falling back to sw
  749. Dec 23 10:06:37 primary gnome-shell[756]: Removing a network device that was not added
  750. Dec 23 10:06:37 primary gnome-shell[756]: Removing a network device that was not added
  751. Dec 23 10:06:37 primary systemd[563]: Reached target GNOME session X11 services.
  752. Dec 23 10:06:37 primary systemd[563]: Starting GNOME XSettings service...
  753. Dec 23 10:06:38 primary ibus-daemon[1476]: GChildWatchSource: Exit status of a child process was requested but ECHILD was received by waitpid(). See the documentation of g_child_watch_source_new() for possible causes.
  754. Dec 23 10:06:38 primary systemd[563]: Started GNOME keyboard configuration service.
  755. Dec 23 10:06:38 primary systemd[563]: Reached target GNOME keyboard configuration target.
  756. Dec 23 10:06:38 primary systemd[563]: Started GNOME keyboard shortcuts service.
  757. Dec 23 10:06:38 primary systemd[563]: Reached target GNOME keyboard shortcuts target.
  758. Dec 23 10:06:38 primary systemd[563]: Started GNOME color management service.
  759. Dec 23 10:06:38 primary systemd[563]: Reached target GNOME color management target.
  760. Dec 23 10:06:38 primary dbus-daemon[593]: [session uid=1000 pid=593] Activating service name='org.gnome.Shell.Screencast' requested by ':1.62' (uid=1000 pid=1643 comm="/usr/libexec/gsd-media-keys ")
  761. Dec 23 10:06:38 primary systemd[563]: Started GNOME power management service.
  762. Dec 23 10:06:38 primary systemd[563]: Reached target GNOME power management target.
  763. Dec 23 10:06:38 primary systemd[563]: Started GNOME Wacom tablet support service.
  764. Dec 23 10:06:38 primary systemd[563]: Reached target GNOME Wacom tablet support target.
  765. Dec 23 10:06:38 primary dbus-daemon[593]: [session uid=1000 pid=593] Activating service name='org.freedesktop.portal.IBus' requested by ':1.75' (uid=1000 pid=1999 comm="ibus-daemon --panel disable -r --xim ")
  766. Dec 23 10:06:38 primary dbus-daemon[593]: [session uid=1000 pid=593] Successfully activated service 'org.freedesktop.portal.IBus'
  767. Dec 23 10:06:38 primary gsd-media-keys[1643]: Failed to grab accelerator for keybinding settings:rfkill
  768. Dec 23 10:06:38 primary gsd-media-keys[1643]: Failed to grab accelerator for keybinding settings:playback-random
  769. Dec 23 10:06:38 primary gsd-media-keys[1643]: Failed to grab accelerator for keybinding settings:playback-repeat
  770. Dec 23 10:06:38 primary gsd-media-keys[1643]: Failed to grab accelerator for keybinding settings:hibernate
  771. Dec 23 10:06:39 primary gnome-shell[756]: Failed to post KMS update: drmModePageFlip on CRTC 34 failed: Cannot allocate memory
  772. Dec 23 10:06:39 primary gnome-shell[756]: GNOME Shell started at Fri Dec 23 2022 10:06:36 GMT+0100 (CET)
  773. Dec 23 10:06:39 primary gnome-shell[756]: Registering session with GDM
  774. Dec 23 10:06:39 primary systemd[563]: Started GNOME XSettings service.
  775. Dec 23 10:06:39 primary systemd[563]: Reached target GNOME session X11 services.
  776. Dec 23 10:06:39 primary systemd[563]: Reached target GNOME Session.
  777. Dec 23 10:06:39 primary systemd[563]: Reached target GNOME Wayland Session (session: gnome).
  778. Dec 23 10:06:39 primary systemd[563]: Reached target Current graphical user session.
  779. Dec 23 10:06:39 primary systemd[563]: Startup finished in 6.120s.
  780. Dec 23 10:06:39 primary dbus-daemon[593]: [session uid=1000 pid=593] Successfully activated service 'org.gnome.Shell.Screencast'
  781. Dec 23 10:06:40 primary gnome-software[1652]: plugin fwupd took 1.6 seconds to do setup
  782. Dec 23 10:06:40 primary gnome-software[1652]: enabled plugins: desktop-categories, fwupd, os-release, packagekit, packagekit-local, packagekit-offline, packagekit-proxy, packagekit-refine-repos, packagekit-refresh, packagekit-upgrade, packagekit-url-to-app, appstream, desktop-menu-path, hardcoded-blocklist, hardcoded-popular, malcontent, modalias, odrs, packagekit-refine, rewrite-resource, packagekit-history, provenance, systemd-updates, generic-updates, provenance-license, icons, key-colors, key-colors-metadata
  783. Dec 23 10:06:40 primary gnome-software[1652]: disabled plugins: dpkg, dummy, repos
  784. Dec 23 10:06:41 primary gnome-shell[2457]: The XKEYBOARD keymap compiler (xkbcomp) reports:
  785. Dec 23 10:06:41 primary gnome-shell[2457]: > Warning: Unsupported maximum keycode 569, clipping.
  786. Dec 23 10:06:41 primary gnome-shell[2457]: > X11 cannot support keycodes above 255.
  787. Dec 23 10:06:41 primary gnome-shell[2457]: Errors from xkbcomp are not fatal to the X server
  788. Dec 23 10:06:42 primary gnome-software[1652]: Only 0 apps for recent list, hiding
  789. Dec 23 10:06:42 primary gnome-software[1652]: adding wildcard app */*/*/*/org.gnome.Builder.desktop/* to plugin cache
  790. Dec 23 10:06:42 primary gnome-software[1652]: adding wildcard app */*/*/*/org.gnome.Calculator.desktop/* to plugin cache
  791. Dec 23 10:06:42 primary gnome-software[1652]: adding wildcard app */*/*/*/org.gnome.clocks.desktop/* to plugin cache
  792. Dec 23 10:06:42 primary gnome-software[1652]: adding wildcard app */*/*/*/org.gnome.Dictionary.desktop/* to plugin cache
  793. Dec 23 10:06:42 primary gnome-software[1652]: adding wildcard app */*/*/*/org.gnome.Documents.desktop/* to plugin cache
  794. Dec 23 10:06:42 primary gnome-software[1652]: adding wildcard app */*/*/*/org.gnome.Evince/* to plugin cache
  795. Dec 23 10:06:42 primary gnome-software[1652]: adding wildcard app */*/*/*/org.gnome.gedit.desktop/* to plugin cache
  796. Dec 23 10:06:42 primary gnome-software[1652]: adding wildcard app */*/*/*/org.gnome.Maps.desktop/* to plugin cache
  797. Dec 23 10:06:42 primary gnome-software[1652]: adding wildcard app */*/*/*/org.gnome.Weather/* to plugin cache
  798. Dec 23 10:06:42 primary gnome-software[1652]: hiding category graphics featured applications: found only 0 to show, need at least 9
  799. Dec 23 10:06:42 primary gnome-software[1652]: hiding category games featured applications: found only 0 to show, need at least 9
  800. Dec 23 10:06:44 primary systemd[563]: tracker-extract.service: Succeeded.
  801. Dec 23 10:06:45 primary gnome-software[1652]: FIXME: Unknown progress handling is not yet implemented for GsProgressButton
  802. Dec 23 10:06:45 primary gnome-software[1652]: FIXME: Unknown progress handling is not yet implemented for GsProgressButton
  803. Dec 23 10:06:45 primary gnome-software[1652]: FIXME: Unknown progress handling is not yet implemented for GsProgressButton
  804. Dec 23 10:06:45 primary gnome-software[1652]: FIXME: Unknown progress handling is not yet implemented for GsProgressButton
  805. Dec 23 10:06:45 primary gnome-software[1652]: automatically prevented from changing kind on system/package/*/generic/org.gphoto.libgphoto2/* from generic to unknown!
  806. Dec 23 10:06:58 primary pulseaudio[582]: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
  807. Dec 23 10:06:59 primary gnome-software[1652]: Only 0 apps for recent list, hiding
  808. Dec 23 10:06:59 primary gnome-software[1652]: hiding category graphics featured applications: found only 0 to show, need at least 9
  809. Dec 23 10:06:59 primary gnome-software[1652]: hiding category games featured applications: found only 0 to show, need at least 9
  810. Dec 23 10:06:59 primary gnome-software[1652]: automatically prevented from changing kind on system/package/debian-stable-main/generic/org.gphoto.libgphoto2/* from generic to unknown!
  811. Dec 23 10:07:04 primary systemd[563]: run-docker-runtime\x2drunc-moby-8d91dce5794e433b9423e2386c56a1be8f2da6191722acf706983c25a82e049a-runc.taLrKY.mount: Succeeded.
  812. Dec 23 10:07:04 primary tracker-store[1023]: OK
  813. Dec 23 10:07:04 primary systemd[563]: tracker-store.service: Succeeded.
  814. Dec 23 10:07:05 primary gnome-software[1652]: Only 0 apps for recent list, hiding
  815. Dec 23 10:07:05 primary gnome-software[1652]: hiding category games featured applications: found only 0 to show, need at least 9
  816. Dec 23 10:07:05 primary gnome-software[1652]: hiding category graphics featured applications: found only 0 to show, need at least 9
  817. Dec 23 10:07:05 primary gnome-software[1652]: automatically prevented from changing kind on system/package/debian-stable-main/generic/org.gphoto.libgphoto2/* from generic to unknown!
  818. Dec 23 10:07:06 primary systemd[563]: run-docker-runtime\x2drunc-moby-2da8ac201c0d22dd379334c69c3250743a4abef5cc683f97dc704df161f84f5a-runc.6Ww4f1.mount: Succeeded.
  819. Dec 23 10:07:23 primary sudo[3236]: saleb : TTY=pts/0 ; PWD=/home/saleb ; USER=root ; COMMAND=/usr/bin/dmesg
  820. Dec 23 10:07:23 primary sudo[3236]: pam_unix(sudo:session): session opened for user root(uid=0) by saleb(uid=1000)
  821. Dec 23 10:07:23 primary sudo[3236]: pam_unix(sudo:session): session closed for user root
  822. Dec 23 10:07:34 primary systemd[563]: run-docker-runtime\x2drunc-moby-8d91dce5794e433b9423e2386c56a1be8f2da6191722acf706983c25a82e049a-runc.qPuciX.mount: Succeeded.
  823. Dec 23 10:07:35 primary dbus-daemon[593]: [session uid=1000 pid=593] Activating via systemd: service name='org.gtk.vfs.Metadata' unit='gvfs-metadata.service' requested by ':1.25' (uid=1000 pid=756 comm="/usr/bin/gnome-shell ")
  824. Dec 23 10:07:35 primary systemd[563]: Starting Virtual filesystem metadata service...
  825. Dec 23 10:07:35 primary dbus-daemon[593]: [session uid=1000 pid=593] Successfully activated service 'org.gtk.vfs.Metadata'
  826. Dec 23 10:07:35 primary systemd[563]: Started Virtual filesystem metadata service.
  827. Dec 23 10:07:39 primary systemd[563]: run-docker-runtime\x2drunc-moby-2da8ac201c0d22dd379334c69c3250743a4abef5cc683f97dc704df161f84f5a-runc.mwJfwE.mount: Succeeded.
  828. Dec 23 10:08:04 primary systemd[563]: run-docker-runtime\x2drunc-moby-8d91dce5794e433b9423e2386c56a1be8f2da6191722acf706983c25a82e049a-runc.foLFEk.mount: Succeeded.
  829. Dec 23 10:08:09 primary systemd[563]: run-docker-runtime\x2drunc-moby-2da8ac201c0d22dd379334c69c3250743a4abef5cc683f97dc704df161f84f5a-runc.nwTLvU.mount: Succeeded.
  830. Dec 23 10:08:39 primary systemd[563]: run-docker-runtime\x2drunc-moby-2da8ac201c0d22dd379334c69c3250743a4abef5cc683f97dc704df161f84f5a-runc.wqesdj.mount: Succeeded.
  831. Dec 23 10:09:01 primary sudo[3449]: saleb : TTY=pts/0 ; PWD=/home/saleb ; USER=root ; COMMAND=/usr/bin/dmesg
  832. Dec 23 10:09:01 primary sudo[3449]: pam_unix(sudo:session): session opened for user root(uid=0) by saleb(uid=1000)
  833. Dec 23 10:09:01 primary sudo[3449]: pam_unix(sudo:session): session closed for user root
  834. Dec 23 10:09:01 primary dbus-daemon[593]: [session uid=1000 pid=593] Activating via systemd: service name='org.freedesktop.Tracker1' unit='tracker-store.service' requested by ':1.3' (uid=1000 pid=584 comm="/usr/libexec/tracker-miner-fs ")
  835. Dec 23 10:09:01 primary systemd[563]: Starting Tracker metadata database store and lookup manager...
  836. Dec 23 10:09:01 primary dbus-daemon[593]: [session uid=1000 pid=593] Successfully activated service 'org.freedesktop.Tracker1'
  837. Dec 23 10:09:01 primary systemd[563]: Started Tracker metadata database store and lookup manager.
  838. Dec 23 10:09:01 primary dbus-daemon[593]: [session uid=1000 pid=593] Activating via systemd: service name='org.freedesktop.Tracker1.Miner.Extract' unit='tracker-extract.service' requested by ':1.3' (uid=1000 pid=584 comm="/usr/libexec/tracker-miner-fs ")
  839. Dec 23 10:09:01 primary systemd[563]: Starting Tracker metadata extractor...
  840. Dec 23 10:09:01 primary tracker-extract[3459]: Set scheduler policy to SCHED_IDLE
  841. Dec 23 10:09:01 primary tracker-extract[3459]: Setting priority nice level to 19
  842. Dec 23 10:09:01 primary dbus-daemon[593]: [session uid=1000 pid=593] Successfully activated service 'org.freedesktop.Tracker1.Miner.Extract'
  843. Dec 23 10:09:01 primary systemd[563]: Started Tracker metadata extractor.
  844. Dec 23 10:09:04 primary systemd[563]: run-docker-runtime\x2drunc-moby-8d91dce5794e433b9423e2386c56a1be8f2da6191722acf706983c25a82e049a-runc.ksC1kS.mount: Succeeded.
  845. Dec 23 10:09:09 primary systemd[563]: run-docker-runtime\x2drunc-moby-2da8ac201c0d22dd379334c69c3250743a4abef5cc683f97dc704df161f84f5a-runc.l43MNh.mount: Succeeded.
  846. Dec 23 10:09:11 primary systemd[563]: tracker-extract.service: Succeeded.
  847. Dec 23 10:09:22 primary sudo[3532]: saleb : TTY=pts/0 ; PWD=/home/saleb ; USER=root ; COMMAND=/usr/bin/mount -t cifs -o username=SaleB //192.168.0.3/PVEBridge ./PVEBridge
  848. Dec 23 10:09:22 primary sudo[3532]: pam_unix(sudo:session): session opened for user root(uid=0) by saleb(uid=1000)
  849. Dec 23 10:09:26 primary sudo[3532]: pam_unix(sudo:session): session closed for user root
  850. Dec 23 10:09:34 primary systemd[563]: run-docker-runtime\x2drunc-moby-8d91dce5794e433b9423e2386c56a1be8f2da6191722acf706983c25a82e049a-runc.t16n5G.mount: Succeeded.
  851. Dec 23 10:09:40 primary systemd[563]: run-docker-runtime\x2drunc-moby-2da8ac201c0d22dd379334c69c3250743a4abef5cc683f97dc704df161f84f5a-runc.JzBGCh.mount: Succeeded.
  852. Dec 23 10:09:56 primary tracker-store[3452]: OK
  853. Dec 23 10:09:56 primary systemd[563]: tracker-store.service: Succeeded.
  854. Dec 23 10:10:00 primary sudo[3605]: saleb : TTY=pts/0 ; PWD=/home/saleb ; USER=root ; COMMAND=/usr/bin/systemctl --failed
  855. Dec 23 10:10:00 primary sudo[3605]: pam_unix(sudo:session): session opened for user root(uid=0) by saleb(uid=1000)
  856. Dec 23 10:10:00 primary sudo[3605]: pam_unix(sudo:session): session closed for user root
  857. Dec 23 10:10:04 primary systemd[563]: run-docker-runtime\x2drunc-moby-8d91dce5794e433b9423e2386c56a1be8f2da6191722acf706983c25a82e049a-runc.8JMMRI.mount: Succeeded.
  858. Dec 23 10:10:10 primary systemd[563]: run-docker-runtime\x2drunc-moby-2da8ac201c0d22dd379334c69c3250743a4abef5cc683f97dc704df161f84f5a-runc.eun7Xi.mount: Succeeded.
  859. Dec 23 10:10:12 primary dbus-daemon[593]: [session uid=1000 pid=593] Activating via systemd: service name='org.freedesktop.Tracker1' unit='tracker-store.service' requested by ':1.3' (uid=1000 pid=584 comm="/usr/libexec/tracker-miner-fs ")
  860. Dec 23 10:10:12 primary systemd[563]: Starting Tracker metadata database store and lookup manager...
  861. Dec 23 10:10:12 primary dbus-daemon[593]: [session uid=1000 pid=593] Successfully activated service 'org.freedesktop.Tracker1'
  862. Dec 23 10:10:12 primary systemd[563]: Started Tracker metadata database store and lookup manager.
  863. Dec 23 10:10:12 primary dbus-daemon[593]: [session uid=1000 pid=593] Activating via systemd: service name='org.freedesktop.Tracker1.Miner.Extract' unit='tracker-extract.service' requested by ':1.3' (uid=1000 pid=584 comm="/usr/libexec/tracker-miner-fs ")
  864. Dec 23 10:10:12 primary systemd[563]: Starting Tracker metadata extractor...
  865. Dec 23 10:10:12 primary tracker-extract[3671]: Set scheduler policy to SCHED_IDLE
  866. Dec 23 10:10:12 primary tracker-extract[3671]: Setting priority nice level to 19
  867. Dec 23 10:10:12 primary dbus-daemon[593]: [session uid=1000 pid=593] Successfully activated service 'org.freedesktop.Tracker1.Miner.Extract'
  868. Dec 23 10:10:12 primary systemd[563]: Started Tracker metadata extractor.
  869. Dec 23 10:10:22 primary systemd[563]: tracker-extract.service: Succeeded.
  870. Dec 23 10:10:35 primary systemd[563]: run-docker-runtime\x2drunc-moby-8d91dce5794e433b9423e2386c56a1be8f2da6191722acf706983c25a82e049a-runc.KNOyPl.mount: Succeeded.
  871. Dec 23 10:10:40 primary systemd[563]: run-docker-runtime\x2drunc-moby-2da8ac201c0d22dd379334c69c3250743a4abef5cc683f97dc704df161f84f5a-runc.2Re4A5.mount: Succeeded.
  872. Dec 23 10:10:42 primary tracker-store[3664]: OK
  873. Dec 23 10:10:42 primary systemd[563]: tracker-store.service: Succeeded.
  874. Dec 23 10:11:05 primary systemd[563]: run-docker-runtime\x2drunc-moby-8d91dce5794e433b9423e2386c56a1be8f2da6191722acf706983c25a82e049a-runc.XppXf8.mount: Succeeded.
  875. Dec 23 10:11:10 primary systemd[563]: run-docker-runtime\x2drunc-moby-2da8ac201c0d22dd379334c69c3250743a4abef5cc683f97dc704df161f84f5a-runc.LyZOwR.mount: Succeeded.
  876. Dec 23 10:11:35 primary systemd[563]: run-docker-runtime\x2drunc-moby-8d91dce5794e433b9423e2386c56a1be8f2da6191722acf706983c25a82e049a-runc.YuO7OM.mount: Succeeded.
  877. Dec 23 10:11:40 primary systemd[563]: run-docker-runtime\x2drunc-moby-2da8ac201c0d22dd379334c69c3250743a4abef5cc683f97dc704df161f84f5a-runc.xa5vDl.mount: Succeeded.
  878. Dec 23 10:12:05 primary systemd[563]: run-docker-runtime\x2drunc-moby-8d91dce5794e433b9423e2386c56a1be8f2da6191722acf706983c25a82e049a-runc.Ls2Ozt.mount: Succeeded.
  879. Dec 23 10:12:10 primary systemd[563]: run-docker-runtime\x2drunc-moby-2da8ac201c0d22dd379334c69c3250743a4abef5cc683f97dc704df161f84f5a-runc.JRQ022.mount: Succeeded.
  880. Dec 23 10:12:35 primary systemd[563]: run-docker-runtime\x2drunc-moby-8d91dce5794e433b9423e2386c56a1be8f2da6191722acf706983c25a82e049a-runc.is4Uar.mount: Succeeded.
  881. Dec 23 10:12:40 primary systemd[563]: run-docker-runtime\x2drunc-moby-2da8ac201c0d22dd379334c69c3250743a4abef5cc683f97dc704df161f84f5a-runc.DE1Ib3.mount: Succeeded.
  882. Dec 23 10:13:05 primary systemd[563]: run-docker-runtime\x2drunc-moby-8d91dce5794e433b9423e2386c56a1be8f2da6191722acf706983c25a82e049a-runc.Nu0e97.mount: Succeeded.
  883. Dec 23 10:13:10 primary systemd[563]: run-docker-runtime\x2drunc-moby-2da8ac201c0d22dd379334c69c3250743a4abef5cc683f97dc704df161f84f5a-runc.VOoyVG.mount: Succeeded.
  884. Dec 23 10:13:35 primary systemd[563]: run-docker-runtime\x2drunc-moby-8d91dce5794e433b9423e2386c56a1be8f2da6191722acf706983c25a82e049a-runc.wQia3o.mount: Succeeded.
  885. Dec 23 10:13:40 primary systemd[563]: run-docker-runtime\x2drunc-moby-2da8ac201c0d22dd379334c69c3250743a4abef5cc683f97dc704df161f84f5a-runc.JoLGD2.mount: Succeeded.
  886. Dec 23 10:14:05 primary systemd[563]: run-docker-runtime\x2drunc-moby-8d91dce5794e433b9423e2386c56a1be8f2da6191722acf706983c25a82e049a-runc.kvQxnb.mount: Succeeded.
  887. Dec 23 10:14:10 primary systemd[563]: run-docker-runtime\x2drunc-moby-2da8ac201c0d22dd379334c69c3250743a4abef5cc683f97dc704df161f84f5a-runc.RpiiXT.mount: Succeeded.
  888. Dec 23 10:14:35 primary systemd[563]: run-docker-runtime\x2drunc-moby-8d91dce5794e433b9423e2386c56a1be8f2da6191722acf706983c25a82e049a-runc.JcC9Sv.mount: Succeeded.
  889. Dec 23 10:14:40 primary systemd[563]: run-docker-runtime\x2drunc-moby-2da8ac201c0d22dd379334c69c3250743a4abef5cc683f97dc704df161f84f5a-runc.gf96Aa.mount: Succeeded.
  890. Dec 23 10:15:05 primary systemd[563]: run-docker-runtime\x2drunc-moby-8d91dce5794e433b9423e2386c56a1be8f2da6191722acf706983c25a82e049a-runc.DRXBq8.mount: Succeeded.
  891. Dec 23 10:15:35 primary systemd[563]: run-docker-runtime\x2drunc-moby-8d91dce5794e433b9423e2386c56a1be8f2da6191722acf706983c25a82e049a-runc.SoptWR.mount: Succeeded.
  892. Dec 23 10:15:40 primary systemd[563]: run-docker-runtime\x2drunc-moby-2da8ac201c0d22dd379334c69c3250743a4abef5cc683f97dc704df161f84f5a-runc.OI0fAo.mount: Succeeded.
  893. Dec 23 10:16:05 primary systemd[563]: run-docker-runtime\x2drunc-moby-8d91dce5794e433b9423e2386c56a1be8f2da6191722acf706983c25a82e049a-runc.4655qp.mount: Succeeded.
  894. Dec 23 10:16:11 primary systemd[563]: run-docker-runtime\x2drunc-moby-2da8ac201c0d22dd379334c69c3250743a4abef5cc683f97dc704df161f84f5a-runc.jem9W0.mount: Succeeded.
  895. Dec 23 10:16:36 primary systemd[563]: run-docker-runtime\x2drunc-moby-8d91dce5794e433b9423e2386c56a1be8f2da6191722acf706983c25a82e049a-runc.uNV2V9.mount: Succeeded.
  896. Dec 23 10:16:41 primary systemd[563]: run-docker-runtime\x2drunc-moby-2da8ac201c0d22dd379334c69c3250743a4abef5cc683f97dc704df161f84f5a-runc.Ha53Wz.mount: Succeeded.
  897. Dec 23 10:17:36 primary systemd[563]: run-docker-runtime\x2drunc-moby-8d91dce5794e433b9423e2386c56a1be8f2da6191722acf706983c25a82e049a-runc.cmFC2e.mount: Succeeded.
  898. Dec 23 10:17:41 primary systemd[563]: run-docker-runtime\x2drunc-moby-2da8ac201c0d22dd379334c69c3250743a4abef5cc683f97dc704df161f84f5a-runc.hjJoFM.mount: Succeeded.
  899. Dec 23 10:18:06 primary systemd[563]: run-docker-runtime\x2drunc-moby-8d91dce5794e433b9423e2386c56a1be8f2da6191722acf706983c25a82e049a-runc.liHsN7.mount: Succeeded.
  900. Dec 23 10:18:11 primary systemd[563]: run-docker-runtime\x2drunc-moby-2da8ac201c0d22dd379334c69c3250743a4abef5cc683f97dc704df161f84f5a-runc.nRLzB0.mount: Succeeded.
  901.  
Advertisement
Add Comment
Please, Sign In to add comment
Public Pastes
We use cookies for various purposes including analytics. By continuing to use Pastebin, you agree to our use of cookies as described in the Cookies Policy.  OK, I Understand
Not a member of Pastebin yet?
Sign Up, it unlocks many cool features!