API tools faq
paste
Advertisement
Guest User

var-log-messages output starting gnome

a guest
Feb 19th, 2023
111
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 92.91 KB | None | 0 0
raw download clone embed print report
  1. Feb 19 01:36:36 zulu imsettings-daemon[2288]: imsettings_server_bus_method_call: sender[:1.33] path[/com/redhat/imsettings] iface[com.redhat.imsettings] method[GetVersion]
  2. Feb 19 01:36:36 zulu imsettings-daemon[2288]: imsettings_server_bus_method_call: sender[:1.33] path[/com/redhat/imsettings] iface[com.redhat.imsettings] method[IsSupportedDesktop]
  3. Feb 19 01:36:36 zulu imsettings-daemon[2288]: [ 36.532702]: IMSettings-Daemon[2288]: WARNING **: Child process exited with code 1
  4. Feb 19 01:36:36 zulu imsettings-daemon[2288]: imsettings_server_bus_method_call: sender[:1.36] path[/com/redhat/imsettings] iface[com.redhat.imsettings] method[GetVersion]
  5. Feb 19 01:36:36 zulu imsettings-daemon[2288]: imsettings_server_bus_method_call: sender[:1.36] path[/com/redhat/imsettings] iface[com.redhat.imsettings] method[DumpModuleSettings]
  6. Feb 19 01:36:36 zulu imsettings-daemon[2288]: imsettings_server_bus_method_call: sender[:1.37] path[/com/redhat/imsettings] iface[com.redhat.imsettings] method[GetVersion]
  7. Feb 19 01:36:36 zulu imsettings-daemon[2288]: imsettings_server_bus_method_call: sender[:1.37] path[/com/redhat/imsettings] iface[com.redhat.imsettings] method[DumpModuleSettings]
  8. Feb 19 01:36:36 zulu imsettings-daemon[2288]: imsettings_server_bus_method_call: sender[:1.43] path[/com/redhat/imsettings] iface[com.redhat.imsettings] method[GetVersion]
  9. Feb 19 01:36:36 zulu imsettings-daemon[2288]: imsettings_server_bus_method_call: sender[:1.43] path[/com/redhat/imsettings] iface[com.redhat.imsettings] method[DumpModuleSettings]
  10. Feb 19 01:36:36 zulu imsettings-daemon[2288]: imsettings_server_bus_method_call: sender[:1.44] path[/com/redhat/imsettings] iface[com.redhat.imsettings] method[GetVersion]
  11. Feb 19 01:36:36 zulu imsettings-daemon[2288]: imsettings_server_bus_method_call: sender[:1.44] path[/com/redhat/imsettings] iface[com.redhat.imsettings] method[DumpModuleSettings]
  12. Feb 19 01:36:37 zulu dbus-daemon[4647]: [session uid=1000 pid=4645] Activating service name='org.gtk.vfs.Daemon' requested by ':1.2' (uid=1000 pid=4650 comm="/usr/libexec/gnome-session-check-accelerated" label="kernel")
  13. Feb 19 01:36:37 zulu dbus-daemon[4647]: [session uid=1000 pid=4645] Successfully activated service 'org.gtk.vfs.Daemon'
  14. Feb 19 01:36:37 zulu dbus-daemon[4647]: [session uid=1000 pid=4645] Activating service name='org.a11y.Bus' requested by ':1.4' (uid=1000 pid=4650 comm="/usr/libexec/gnome-session-check-accelerated" label="kernel")
  15. Feb 19 01:36:37 zulu org.gtk.vfs.Daemon[4661]: fusermount3: failed to access mountpoint /run/user/1000/gvfs: Permission denied
  16. Feb 19 01:36:37 zulu dbus-daemon[4647]: [session uid=1000 pid=4645] Successfully activated service 'org.a11y.Bus'
  17. Feb 19 01:36:37 zulu gnome-session[4494]: gnome-session-binary[4494]: WARNING: Failed to upload environment to systemd: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.freedesktop.systemd1" does not exist
  18. Feb 19 01:36:37 zulu gnome-session-binary[4494]: WARNING: Failed to upload environment to systemd: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.freedesktop.systemd1" does not exist
  19. Feb 19 01:36:37 zulu gnome-session[4494]: gnome-session-binary[4494]: WARNING: Failed to reset failed state of units: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.freedesktop.systemd1" does not exist
  20. Feb 19 01:36:37 zulu gnome-session-binary[4494]: WARNING: Failed to reset failed state of units: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.freedesktop.systemd1" does not exist
  21. Feb 19 01:36:37 zulu gnome-session[4494]: gnome-session-binary[4494]: WARNING: Falling back to non-systemd startup procedure due to error: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.freedesktop.systemd1" does not exist
  22. Feb 19 01:36:37 zulu gnome-session-binary[4494]: WARNING: Falling back to non-systemd startup procedure due to error: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.freedesktop.systemd1" does not exist
  23. Feb 19 01:36:37 zulu gnome-session[4494]: gnome-session-binary[4494]: WARNING: Could not get session id for session. Check that logind is properly installed and pam_systemd is getting used at login.
  24. Feb 19 01:36:37 zulu gnome-session-binary[4494]: WARNING: Could not get session id for session. Check that logind is properly installed and pam_systemd is getting used at login.
  25. Feb 19 01:36:37 zulu gnome-keyring-daemon[4684]: couldn't access control socket: /run/user/1000/keyring/control: No such file or directory
  26. Feb 19 01:36:37 zulu gnome-keyring-daemon[4684]: discover_other_daemon: 0
  27. Feb 19 01:36:37 zulu journal[4684]: couldn't access control socket: /run/user/1000/keyring/control: No such file or directory
  28. Feb 19 01:36:37 zulu gnome-keyring-daemon[4685]: couldn't access control socket: /run/user/1000/keyring/control: No such file or directory
  29. Feb 19 01:36:37 zulu journal[4685]: couldn't access control socket: /run/user/1000/keyring/control: No such file or directory
  30. Feb 19 01:36:37 zulu gnome-keyring-daemon[4685]: discover_other_daemon: 0
  31. Feb 19 01:36:37 zulu gnome-keyring-secrets.desktop[4684]: discover_other_daemon: 0
  32. Feb 19 01:36:37 zulu gnome-keyring-pkcs11.desktop[4685]: discover_other_daemon: 0SSH_AUTH_SOCK=/run/user/1000/keyring/ssh
  33. Feb 19 01:36:37 zulu gnome-keyring-daemon[4691]: discover_other_daemon: 1
  34. Feb 19 01:36:37 zulu gnome-keyring-ssh.desktop[4691]: discover_other_daemon: 1SSH_AUTH_SOCK=/run/user/1000/keyring/ssh
  35. Feb 19 01:36:38 zulu journal[4692]: Running GNOME Shell (using mutter 43.3) as a X11 window and compositing manager
  36. Feb 19 01:36:38 zulu journal[4692]: Failed to migrate monitor configuration for default:???:0x0000:0x00000000: Monitor mode invalid
  37. Feb 19 01:36:38 zulu journal[4692]: ATK Bridge is disabled but a11y has already been enabled.
  38. Feb 19 01:36:39 zulu dbus-daemon[4647]: [session uid=1000 pid=4645] Activating service name='org.gnome.Shell.Screencast' requested by ':1.11' (uid=1000 pid=4692 comm="/usr/bin/gnome-shell" label="kernel")
  39. Feb 19 01:36:39 zulu dbus-daemon[4647]: [session uid=1000 pid=4645] Activating service name='org.freedesktop.impl.portal.PermissionStore' requested by ':1.11' (uid=1000 pid=4692 comm="/usr/bin/gnome-shell" label="kernel")
  40. Feb 19 01:36:39 zulu dbus-daemon[4647]: [session uid=1000 pid=4645] Activating service name='org.gnome.Shell.CalendarServer' requested by ':1.11' (uid=1000 pid=4692 comm="/usr/bin/gnome-shell" label="kernel")
  41. Feb 19 01:36:39 zulu dbus-daemon[4647]: [session uid=1000 pid=4645] Successfully activated service 'org.freedesktop.impl.portal.PermissionStore'
  42. Feb 19 01:36:39 zulu dbus-daemon[4647]: [session uid=1000 pid=4645] Activating service name='org.gnome.evolution.dataserver.Sources5' requested by ':1.14' (uid=1000 pid=4724 comm="/usr/libexec/gnome-shell-calendar-server" label="kernel")
  43. Feb 19 01:36:39 zulu journal[4692]: Failed to load shared library 'libgvc.so' referenced by the typelib: libgvc.so: cannot open shared object file: No such file or directory
  44. Feb 19 01:36:39 zulu journal[4692]: JS ERROR: Error: Unsupported type void, deriving from fundamental void#012getMixerControl@resource:///org/gnome/shell/ui/status/volume.js:23:5#012_init@resource:///org/gnome/shell/ui/status/volume.js:396:25#012SystemIndicator@resource:///org/gnome/shell/ui/quickSettings.js:692:1#012Indicator@resource:///org/gnome/shell/ui/status/volume.js:381:1#012_init@resource:///org/gnome/shell/ui/panel.js:358:24#012ButtonBox@resource:///org/gnome/shell/ui/panelMenu.js:11:1#012PanelMenuButton@resource:///org/gnome/shell/ui/panelMenu.js:97:4#012QuickSettings@resource:///org/gnome/shell/ui/panel.js:336:1#012_ensureIndicator@resource:///org/gnome/shell/ui/panel.js:681:25#012_updateBox@resource:///org/gnome/shell/ui/panel.js:692:34#012_updatePanel@resource:///org/gnome/shell/ui/panel.js:646:14#012_init@resource:///org/gnome/shell/ui/panel.js:463:14#012Panel@resource:///org/gnome/shell/ui/panel.js:424:1#012_initializeUI@resource:///org/gnome/shell/ui/main.js:248:13#012start@resource:///org/gnome/shell/ui/main.js:186:5#012@resource:///org/gnome/shell/ui/init.js:6:17
  45. Feb 19 01:36:39 zulu journal[4692]: Execution of main.js threw exception: Module resource:///org/gnome/shell/ui/init.js threw an exception
  46. Feb 19 01:36:39 zulu journal[4692]: 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.
  47. Feb 19 01:36:39 zulu org.gnome.Shell.desktop[4692]: == Stack trace for context 0x55c9a198b190 ==
  48. Feb 19 01:36:39 zulu org.gnome.Shell.desktop[4692]: == Stack trace for context 0x55c9a198b190 ==
  49. Feb 19 01:36:39 zulu org.gnome.Shell.desktop[4692]: == Stack trace for context 0x55c9a198b190 ==
  50. Feb 19 01:36:39 zulu org.gnome.Shell.desktop[4692]: == Stack trace for context 0x55c9a198b190 ==
  51. Feb 19 01:36:39 zulu org.gnome.Shell.desktop[4692]: == Stack trace for context 0x55c9a198b190 ==
  52. Feb 19 01:36:39 zulu org.gnome.Shell.desktop[4692]: == Stack trace for context 0x55c9a198b190 ==
  53. Feb 19 01:36:39 zulu org.gnome.Shell.desktop[4692]: == Stack trace for context 0x55c9a198b190 ==
  54. Feb 19 01:36:39 zulu org.gnome.Shell.desktop[4692]: == Stack trace for context 0x55c9a198b190 ==
  55. Feb 19 01:36:39 zulu org.gnome.Shell.desktop[4692]: == Stack trace for context 0x55c9a198b190 ==
  56. Feb 19 01:36:39 zulu org.gnome.Shell.desktop[4692]: == Stack trace for context 0x55c9a198b190 ==
  57. Feb 19 01:36:39 zulu org.gnome.Shell.desktop[4692]: == Stack trace for context 0x55c9a198b190 ==
  58. Feb 19 01:36:39 zulu org.gnome.Shell.desktop[4692]: == Stack trace for context 0x55c9a198b190 ==
  59. Feb 19 01:36:39 zulu org.gnome.Shell.desktop[4692]: == Stack trace for context 0x55c9a198b190 ==
  60. Feb 19 01:36:39 zulu org.gnome.Shell.desktop[4692]: == Stack trace for context 0x55c9a198b190 ==
  61. Feb 19 01:36:39 zulu org.gnome.Shell.desktop[4692]: == Stack trace for context 0x55c9a198b190 ==
  62. Feb 19 01:36:39 zulu org.gnome.Shell.desktop[4692]: == Stack trace for context 0x55c9a198b190 ==
  63. Feb 19 01:36:39 zulu journal[4692]: The offending signal was destroy on Gjs_ui_panel_QuickSettings 0x55c9a2d5b900.
  64. Feb 19 01:36:39 zulu org.gnome.Shell.desktop[4692]: == Stack trace for context 0x55c9a198b190 ==
  65. Feb 19 01:36:39 zulu org.gnome.Shell.desktop[4692]: == Stack trace for context 0x55c9a198b190 ==
  66. Feb 19 01:36:39 zulu org.gnome.Shell.desktop[4692]: == Stack trace for context 0x55c9a198b190 ==
  67. Feb 19 01:36:39 zulu org.gnome.Shell.desktop[4692]: == Stack trace for context 0x55c9a198b190 ==
  68. Feb 19 01:36:39 zulu org.gnome.Shell.desktop[4692]: == Stack trace for context 0x55c9a198b190 ==
  69. Feb 19 01:36:39 zulu org.gnome.Shell.desktop[4692]: == Stack trace for context 0x55c9a198b190 ==
  70. Feb 19 01:36:39 zulu org.gnome.Shell.desktop[4692]: == Stack trace for context 0x55c9a198b190 ==
  71. Feb 19 01:36:39 zulu org.gnome.Shell.desktop[4692]: == Stack trace for context 0x55c9a198b190 ==
  72. Feb 19 01:36:39 zulu org.gnome.Shell.desktop[4692]: == Stack trace for context 0x55c9a198b190 ==
  73. Feb 19 01:36:39 zulu journal[4692]: 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.
  74. Feb 19 01:36:39 zulu journal[4692]: The offending signal was destroy on Gjs_ui_panel_QuickSettings 0x55c9a2d5b900.
  75. Feb 19 01:36:39 zulu org.gnome.Shell.desktop[4692]: == Stack trace for context 0x55c9a198b190 ==
  76. Feb 19 01:36:39 zulu org.gnome.Shell.desktop[4692]: == Stack trace for context 0x55c9a198b190 ==
  77. Feb 19 01:36:39 zulu org.gnome.Shell.desktop[4692]: == Stack trace for context 0x55c9a198b190 ==
  78. Feb 19 01:36:39 zulu journal[4692]: 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.
  79. Feb 19 01:36:39 zulu org.gnome.Shell.desktop[4692]: == Stack trace for context 0x55c9a198b190 ==
  80. Feb 19 01:36:39 zulu org.gnome.Shell.desktop[4692]: == Stack trace for context 0x55c9a198b190 ==
  81. Feb 19 01:36:39 zulu org.gnome.Shell.desktop[4692]: == Stack trace for context 0x55c9a198b190 ==
  82. Feb 19 01:36:39 zulu journal[4692]: The offending signal was destroy on Gjs_ui_popupMenu_PopupSeparatorMenuItem 0x55c9a2d50d70.
  83. Feb 19 01:36:39 zulu journal[4692]: 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.
  84. Feb 19 01:36:39 zulu journal[4692]: The offending signal was destroy on Gjs_ui_popupMenu_PopupSeparatorMenuItem 0x55c9a2d50d70.
  85. Feb 19 01:36:39 zulu org.gnome.Shell.desktop[4692]: == Stack trace for context 0x55c9a198b190 ==
  86. Feb 19 01:36:39 zulu org.gnome.Shell.desktop[4692]: == Stack trace for context 0x55c9a198b190 ==
  87. Feb 19 01:36:39 zulu org.gnome.Shell.desktop[4692]: == Stack trace for context 0x55c9a198b190 ==
  88. Feb 19 01:36:39 zulu journal[4692]: 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.
  89. Feb 19 01:36:39 zulu journal[4692]: The offending signal was destroy on Gjs_ui_popupMenu_PopupSeparatorMenuItem 0x55c9a2d50d70.
  90. Feb 19 01:36:39 zulu journal[4692]: 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.
  91. Feb 19 01:36:39 zulu journal[4692]: The offending signal was destroy on Gjs_ui_popupMenu_PopupMenuItem 0x55c9a2d57300.
  92. Feb 19 01:36:39 zulu journal[4692]: 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.
  93. Feb 19 01:36:39 zulu journal[4692]: The offending signal was destroy on Gjs_ui_popupMenu_PopupMenuItem 0x55c9a2d57300.
  94. Feb 19 01:36:39 zulu journal[4692]: 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.
  95. Feb 19 01:36:39 zulu journal[4692]: The offending signal was destroy on Gjs_ui_popupMenu_PopupMenuItem 0x55c9a2d57300.
  96. Feb 19 01:36:39 zulu journal[4692]: 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.
  97. Feb 19 01:36:39 zulu journal[4692]: The offending signal was destroy on Gjs_ui_animation_Spinner 0x55c9a2dab3e0.
  98. Feb 19 01:36:39 zulu journal[4692]: 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.
  99. Feb 19 01:36:39 zulu journal[4692]: The offending signal was destroy on Gjs_ui_animation_Spinner 0x55c9a2dab3e0.
  100. Feb 19 01:36:39 zulu journal[4692]: 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.
  101. Feb 19 01:36:39 zulu journal[4692]: The offending signal was destroy on Gjs_ui_popupMenu_PopupSeparatorMenuItem 0x55c9a2da2370.
  102. Feb 19 01:36:39 zulu journal[4692]: 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.
  103. Feb 19 01:36:39 zulu journal[4692]: The offending signal was destroy on Gjs_ui_popupMenu_PopupSeparatorMenuItem 0x55c9a2da2370.
  104. Feb 19 01:36:39 zulu journal[4692]: 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.
  105. Feb 19 01:36:39 zulu journal[4692]: The offending signal was destroy on Gjs_ui_popupMenu_PopupSeparatorMenuItem 0x55c9a2da2370.
  106. Feb 19 01:36:39 zulu journal[4692]: 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.
  107. Feb 19 01:36:39 zulu journal[4692]: The offending signal was destroy on Gjs_ui_popupMenu_PopupMenuItem 0x55c9a2dafd50.
  108. Feb 19 01:36:39 zulu journal[4692]: 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.
  109. Feb 19 01:36:39 zulu journal[4692]: The offending signal was destroy on Gjs_ui_popupMenu_PopupMenuItem 0x55c9a2dafd50.
  110. Feb 19 01:36:39 zulu journal[4692]: 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.
  111. Feb 19 01:36:39 zulu journal[4692]: The offending signal was destroy on Gjs_ui_popupMenu_PopupMenuItem 0x55c9a2dafd50.
  112. Feb 19 01:36:39 zulu journal[4692]: 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.
  113. Feb 19 01:36:39 zulu journal[4692]: The offending signal was destroy on Gjs_ui_popupMenu_PopupSeparatorMenuItem 0x55c9a2dca020.
  114. Feb 19 01:36:39 zulu journal[4692]: 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.
  115. Feb 19 01:36:39 zulu journal[4692]: The offending signal was destroy on Gjs_ui_popupMenu_PopupSeparatorMenuItem 0x55c9a2dca020.
  116. Feb 19 01:36:39 zulu journal[4692]: 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.
  117. Feb 19 01:36:39 zulu journal[4692]: The offending signal was destroy on Gjs_ui_popupMenu_PopupSeparatorMenuItem 0x55c9a2dca020.
  118. Feb 19 01:36:39 zulu journal[4692]: 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.
  119. Feb 19 01:36:39 zulu journal[4692]: The offending signal was destroy on Gjs_ui_popupMenu_PopupMenuItem 0x55c9a2dd0e70.
  120. Feb 19 01:36:39 zulu journal[4692]: 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.
  121. Feb 19 01:36:39 zulu journal[4692]: The offending signal was destroy on Gjs_ui_popupMenu_PopupMenuItem 0x55c9a2dd0e70.
  122. Feb 19 01:36:39 zulu org.gnome.Shell.desktop[4692]: == Stack trace for context 0x55c9a198b190 ==
  123. Feb 19 01:36:39 zulu org.gnome.Shell.desktop[4692]: == Stack trace for context 0x55c9a198b190 ==
  124. Feb 19 01:36:39 zulu org.gnome.Shell.desktop[4692]: == Stack trace for context 0x55c9a198b190 ==
  125. Feb 19 01:36:39 zulu org.gnome.Shell.desktop[4692]: == Stack trace for context 0x55c9a198b190 ==
  126. Feb 19 01:36:39 zulu org.gnome.Shell.desktop[4692]: == Stack trace for context 0x55c9a198b190 ==
  127. Feb 19 01:36:39 zulu org.gnome.Shell.desktop[4692]: == Stack trace for context 0x55c9a198b190 ==
  128. Feb 19 01:36:39 zulu org.gnome.Shell.desktop[4692]: == Stack trace for context 0x55c9a198b190 ==
  129. Feb 19 01:36:39 zulu journal[4692]: 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.
  130. Feb 19 01:36:39 zulu org.gnome.Shell.desktop[4692]: == Stack trace for context 0x55c9a198b190 ==
  131. Feb 19 01:36:39 zulu org.gnome.Shell.desktop[4692]: == Stack trace for context 0x55c9a198b190 ==
  132. Feb 19 01:36:39 zulu org.gnome.Shell.desktop[4692]: == Stack trace for context 0x55c9a198b190 ==
  133. Feb 19 01:36:39 zulu org.gnome.Shell.desktop[4692]: == Stack trace for context 0x55c9a198b190 ==
  134. Feb 19 01:36:39 zulu org.gnome.Shell.desktop[4692]: == Stack trace for context 0x55c9a198b190 ==
  135. Feb 19 01:36:39 zulu org.gnome.Shell.desktop[4692]: == Stack trace for context 0x55c9a198b190 ==
  136. Feb 19 01:36:39 zulu org.gnome.Shell.desktop[4692]: == Stack trace for context 0x55c9a198b190 ==
  137. Feb 19 01:36:39 zulu journal[4692]: The offending signal was destroy on Gjs_ui_popupMenu_PopupMenuItem 0x55c9a2dd0e70.
  138. Feb 19 01:36:39 zulu org.gnome.Shell.desktop[4692]: == Stack trace for context 0x55c9a198b190 ==
  139. Feb 19 01:36:39 zulu org.gnome.Shell.desktop[4692]: == Stack trace for context 0x55c9a198b190 ==
  140. Feb 19 01:36:39 zulu org.gnome.Shell.desktop[4692]: == Stack trace for context 0x55c9a198b190 ==
  141. Feb 19 01:36:39 zulu org.gnome.Shell.desktop[4692]: == Stack trace for context 0x55c9a198b190 ==
  142. Feb 19 01:36:39 zulu org.gnome.Shell.desktop[4692]: == Stack trace for context 0x55c9a198b190 ==
  143. Feb 19 01:36:39 zulu journal[4692]: 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.
  144. Feb 19 01:36:39 zulu org.gnome.Shell.desktop[4692]: == Stack trace for context 0x55c9a198b190 ==
  145. Feb 19 01:36:39 zulu org.gnome.Shell.desktop[4692]: == Stack trace for context 0x55c9a198b190 ==
  146. Feb 19 01:36:39 zulu org.gnome.Shell.desktop[4692]: == Stack trace for context 0x55c9a198b190 ==
  147. Feb 19 01:36:39 zulu org.gnome.Shell.desktop[4692]: == Stack trace for context 0x55c9a198b190 ==
  148. Feb 19 01:36:39 zulu journal[4692]: The offending signal was destroy on Gjs_ui_popupMenu_PopupMenuItem 0x55c9a2dd6da0.
  149. Feb 19 01:36:39 zulu journal[4692]: 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.
  150. Feb 19 01:36:39 zulu journal[4692]: The offending signal was destroy on Gjs_ui_popupMenu_PopupMenuItem 0x55c9a2dd6da0.
  151. Feb 19 01:36:39 zulu journal[4692]: 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.
  152. Feb 19 01:36:39 zulu journal[4692]: The offending signal was destroy on Gjs_ui_popupMenu_PopupMenuItem 0x55c9a2dd6da0.
  153. Feb 19 01:36:39 zulu journal[4692]: 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.
  154. Feb 19 01:36:39 zulu journal[4692]: The offending signal was destroy on Gjs_ui_popupMenu_PopupSeparatorMenuItem 0x55c9a2df0dc0.
  155. Feb 19 01:36:39 zulu journal[4692]: 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.
  156. Feb 19 01:36:39 zulu journal[4692]: The offending signal was destroy on Gjs_ui_popupMenu_PopupSeparatorMenuItem 0x55c9a2df0dc0.
  157. Feb 19 01:36:39 zulu journal[4692]: 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.
  158. Feb 19 01:36:39 zulu journal[4692]: The offending signal was destroy on Gjs_ui_popupMenu_PopupSeparatorMenuItem 0x55c9a2df0dc0.
  159. Feb 19 01:36:39 zulu journal[4692]: 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.
  160. Feb 19 01:36:39 zulu journal[4692]: The offending signal was destroy on Gjs_ui_popupMenu_PopupMenuItem 0x55c9a29eac20.
  161. Feb 19 01:36:39 zulu journal[4692]: 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. Feb 19 01:36:39 zulu journal[4692]: The offending signal was destroy on Gjs_ui_popupMenu_PopupMenuItem 0x55c9a29eac20.
  163. Feb 19 01:36:39 zulu journal[4692]: 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.
  164. Feb 19 01:36:39 zulu journal[4692]: The offending signal was destroy on Gjs_ui_popupMenu_PopupMenuItem 0x55c9a29eac20.
  165. Feb 19 01:36:39 zulu journal[4692]: 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.
  166. Feb 19 01:36:39 zulu journal[4692]: The offending signal was destroy on Gjs_ui_popupMenu_PopupSeparatorMenuItem 0x55c9a2da8ce0.
  167. Feb 19 01:36:39 zulu journal[4692]: 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. Feb 19 01:36:39 zulu journal[4692]: The offending signal was destroy on Gjs_ui_popupMenu_PopupSeparatorMenuItem 0x55c9a2da8ce0.
  169. Feb 19 01:36:39 zulu journal[4692]: 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.
  170. Feb 19 01:36:39 zulu journal[4692]: The offending signal was destroy on Gjs_ui_popupMenu_PopupSeparatorMenuItem 0x55c9a2da8ce0.
  171. Feb 19 01:36:39 zulu journal[4692]: 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.
  172. Feb 19 01:36:39 zulu journal[4692]: The offending signal was destroy on Gjs_ui_popupMenu_PopupMenuItem 0x55c9a2d630a0.
  173. Feb 19 01:36:39 zulu journal[4692]: 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.
  174. Feb 19 01:36:39 zulu journal[4692]: The offending signal was destroy on Gjs_ui_popupMenu_PopupMenuItem 0x55c9a2d630a0.
  175. Feb 19 01:36:39 zulu journal[4692]: 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.
  176. Feb 19 01:36:39 zulu journal[4692]: The offending signal was destroy on Gjs_ui_popupMenu_PopupMenuItem 0x55c9a2d630a0.
  177. Feb 19 01:36:39 zulu journal[4692]: 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.
  178. Feb 19 01:36:39 zulu journal[4692]: The offending signal was destroy on Gjs_status_system_PowerToggle 0x55c9a2e556c0.
  179. Feb 19 01:36:39 zulu journal[4692]: 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. Feb 19 01:36:39 zulu journal[4692]: The offending signal was destroy on Gjs_status_system_SettingsItem 0x55c9a25a2080.
  181. Feb 19 01:36:39 zulu journal[4692]: 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.
  182. Feb 19 01:36:39 zulu journal[4692]: The offending signal was destroy on Gjs_ui_popupMenu_PopupMenuItem 0x55c9a2e97360.
  183. Feb 19 01:36:39 zulu journal[4692]: 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.
  184. Feb 19 01:36:39 zulu journal[4692]: The offending signal was destroy on Gjs_ui_popupMenu_PopupMenuItem 0x55c9a2e97360.
  185. Feb 19 01:36:39 zulu journal[4692]: 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.
  186. Feb 19 01:36:39 zulu journal[4692]: The offending signal was destroy on Gjs_ui_popupMenu_PopupMenuItem 0x55c9a2e97360.
  187. Feb 19 01:36:39 zulu journal[4692]: 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. Feb 19 01:36:39 zulu journal[4692]: The offending signal was destroy on Gjs_ui_popupMenu_PopupMenuItem 0x55c9a2e9c140.
  189. Feb 19 01:36:39 zulu journal[4692]: 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.
  190. Feb 19 01:36:39 zulu journal[4692]: The offending signal was destroy on Gjs_ui_popupMenu_PopupMenuItem 0x55c9a2e9c140.
  191. Feb 19 01:36:39 zulu journal[4692]: 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.
  192. Feb 19 01:36:39 zulu journal[4692]: The offending signal was destroy on Gjs_ui_popupMenu_PopupMenuItem 0x55c9a2e9c140.
  193. Feb 19 01:36:39 zulu journal[4692]: 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.
  194. Feb 19 01:36:39 zulu journal[4692]: The offending signal was destroy on Gjs_ui_popupMenu_PopupMenuItem 0x55c9a2ea0cf0.
  195. Feb 19 01:36:39 zulu journal[4692]: 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.
  196. Feb 19 01:36:39 zulu journal[4692]: The offending signal was destroy on Gjs_ui_popupMenu_PopupMenuItem 0x55c9a2ea0cf0.
  197. Feb 19 01:36:39 zulu journal[4692]: 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.
  198. Feb 19 01:36:39 zulu journal[4692]: The offending signal was destroy on Gjs_ui_popupMenu_PopupMenuItem 0x55c9a2ea0cf0.
  199. Feb 19 01:36:39 zulu journal[4692]: 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.
  200. Feb 19 01:36:39 zulu journal[4692]: The offending signal was destroy on Gjs_ui_popupMenu_PopupSeparatorMenuItem 0x55c9a2ea8290.
  201. Feb 19 01:36:39 zulu journal[4692]: 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. Feb 19 01:36:39 zulu journal[4692]: The offending signal was destroy on Gjs_ui_popupMenu_PopupSeparatorMenuItem 0x55c9a2ea8290.
  203. Feb 19 01:36:39 zulu journal[4692]: 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.
  204. Feb 19 01:36:39 zulu journal[4692]: The offending signal was destroy on Gjs_ui_popupMenu_PopupSeparatorMenuItem 0x55c9a2ea8290.
  205. Feb 19 01:36:39 zulu journal[4692]: 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.
  206. Feb 19 01:36:39 zulu journal[4692]: The offending signal was destroy on Gjs_ui_popupMenu_PopupMenuItem 0x55c9a2ead080.
  207. Feb 19 01:36:39 zulu journal[4692]: 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.
  208. Feb 19 01:36:39 zulu journal[4692]: The offending signal was destroy on Gjs_ui_popupMenu_PopupMenuItem 0x55c9a2ead080.
  209. Feb 19 01:36:39 zulu journal[4692]: 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.
  210. Feb 19 01:36:39 zulu journal[4692]: The offending signal was destroy on Gjs_ui_popupMenu_PopupMenuItem 0x55c9a2ead080.
  211. Feb 19 01:36:39 zulu journal[4692]: 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.
  212. Feb 19 01:36:39 zulu journal[4692]: The offending signal was destroy on Gjs_ui_popupMenu_PopupMenuItem 0x55c9a2eb2ac0.
  213. Feb 19 01:36:39 zulu journal[4692]: 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. Feb 19 01:36:39 zulu journal[4692]: The offending signal was destroy on Gjs_ui_popupMenu_PopupMenuItem 0x55c9a2eb2ac0.
  215. Feb 19 01:36:39 zulu journal[4692]: 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.
  216. Feb 19 01:36:39 zulu journal[4692]: The offending signal was destroy on Gjs_ui_popupMenu_PopupMenuItem 0x55c9a2eb2ac0.
  217. Feb 19 01:36:39 zulu dbus-daemon[4647]: [session uid=1000 pid=4645] Activating service name='org.gnome.OnlineAccounts' requested by ':1.15' (uid=1000 pid=4734 comm="/usr/libexec/evolution-source-registry" label="kernel")
  218. Feb 19 01:36:39 zulu dbus-daemon[4647]: [session uid=1000 pid=4645] Successfully activated service 'org.gnome.Shell.Screencast'
  219. Feb 19 01:36:39 zulu dbus-daemon[4647]: [session uid=1000 pid=4645] Successfully activated service 'org.gnome.evolution.dataserver.Sources5'
  220. Feb 19 01:36:39 zulu dbus-daemon[4647]: [session uid=1000 pid=4645] Successfully activated service 'org.gnome.Shell.CalendarServer'
  221. Feb 19 01:36:40 zulu dbus-daemon[4647]: [session uid=1000 pid=4645] Activating service name='org.gnome.evolution.dataserver.Calendar8' requested by ':1.14' (uid=1000 pid=4724 comm="/usr/libexec/gnome-shell-calendar-server" label="kernel")
  222. Feb 19 01:36:40 zulu gnome-session[4494]: gnome-session-binary[4494]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1
  223. Feb 19 01:36:40 zulu gnome-session-binary[4494]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1
  224. Feb 19 01:36:40 zulu journal[4760]: goa-daemon version 3.46.0 starting
  225. Feb 19 01:36:40 zulu dbus-daemon[4647]: [session uid=1000 pid=4645] Activating service name='org.gnome.Identity' requested by ':1.16' (uid=1000 pid=4760 comm="/usr/libexec/goa-daemon" label="kernel")
  226. Feb 19 01:36:40 zulu dbus-daemon[4647]: [session uid=1000 pid=4645] Successfully activated service 'org.gnome.OnlineAccounts'
  227. Feb 19 01:36:40 zulu dbus-daemon[4647]: [session uid=1000 pid=4645] Successfully activated service 'org.gnome.Identity'
  228. Feb 19 01:36:40 zulu journal[4766]: Running GNOME Shell (using mutter 43.3) as a X11 window and compositing manager
  229. Feb 19 01:36:40 zulu dbus-daemon[4647]: [session uid=1000 pid=4645] Successfully activated service 'org.gnome.evolution.dataserver.Calendar8'
  230. Feb 19 01:36:40 zulu journal[4777]: GoaKerberosIdentityManager: Using polling for change notification for credential cache type 'KCM'
  231. Feb 19 01:36:40 zulu dbus-daemon[4647]: [session uid=1000 pid=4645] Activating service name='org.gnome.evolution.dataserver.AddressBook10' requested by ':1.17' (uid=1000 pid=4765 comm="/usr/libexec/evolution-calendar-factory" label="kernel")
  232. Feb 19 01:36:40 zulu journal[4766]: Failed to migrate monitor configuration for default:???:0x0000:0x00000000: Monitor mode invalid
  233. Feb 19 01:36:40 zulu dbus-daemon[4647]: [session uid=1000 pid=4645] Successfully activated service 'org.gnome.evolution.dataserver.AddressBook10'
  234. Feb 19 01:36:40 zulu journal[4766]: ATK Bridge is disabled but a11y has already been enabled.
  235. Feb 19 01:36:41 zulu dbus-daemon[4647]: [session uid=1000 pid=4645] Activating service name='org.gnome.Shell.Screencast' requested by ':1.19' (uid=1000 pid=4766 comm="/usr/bin/gnome-shell" label="kernel")
  236. Feb 19 01:36:41 zulu journal[4766]: Failed to load shared library 'libgvc.so' referenced by the typelib: libgvc.so: cannot open shared object file: No such file or directory
  237. Feb 19 01:36:41 zulu journal[4766]: JS ERROR: Error: Unsupported type void, deriving from fundamental void#012getMixerControl@resource:///org/gnome/shell/ui/status/volume.js:23:5#012_init@resource:///org/gnome/shell/ui/status/volume.js:396:25#012SystemIndicator@resource:///org/gnome/shell/ui/quickSettings.js:692:1#012Indicator@resource:///org/gnome/shell/ui/status/volume.js:381:1#012_init@resource:///org/gnome/shell/ui/panel.js:358:24#012ButtonBox@resource:///org/gnome/shell/ui/panelMenu.js:11:1#012PanelMenuButton@resource:///org/gnome/shell/ui/panelMenu.js:97:4#012QuickSettings@resource:///org/gnome/shell/ui/panel.js:336:1#012_ensureIndicator@resource:///org/gnome/shell/ui/panel.js:681:25#012_updateBox@resource:///org/gnome/shell/ui/panel.js:692:34#012_updatePanel@resource:///org/gnome/shell/ui/panel.js:646:14#012_init@resource:///org/gnome/shell/ui/panel.js:463:14#012Panel@resource:///org/gnome/shell/ui/panel.js:424:1#012_initializeUI@resource:///org/gnome/shell/ui/main.js:248:13#012start@resource:///org/gnome/shell/ui/main.js:186:5#012@resource:///org/gnome/shell/ui/init.js:6:17
  238. Feb 19 01:36:41 zulu journal[4766]: Execution of main.js threw exception: Module resource:///org/gnome/shell/ui/init.js threw an exception
  239. Feb 19 01:36:41 zulu journal[4766]: 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.
  240. Feb 19 01:36:41 zulu journal[4766]: The offending signal was destroy on Gjs_ui_panel_QuickSettings 0x55aa8f4bd760.
  241. Feb 19 01:36:41 zulu org.gnome.Shell.desktop[4766]: == Stack trace for context 0x55aa8e27e180 ==
  242. Feb 19 01:36:41 zulu org.gnome.Shell.desktop[4766]: == Stack trace for context 0x55aa8e27e180 ==
  243. Feb 19 01:36:41 zulu journal[4766]: 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. Feb 19 01:36:41 zulu journal[4766]: The offending signal was destroy on Gjs_ui_panel_QuickSettings 0x55aa8f4bd760.
  245. Feb 19 01:36:41 zulu journal[4766]: 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. Feb 19 01:36:41 zulu org.gnome.Shell.desktop[4766]: == Stack trace for context 0x55aa8e27e180 ==
  247. Feb 19 01:36:41 zulu org.gnome.Shell.desktop[4766]: == Stack trace for context 0x55aa8e27e180 ==
  248. Feb 19 01:36:41 zulu org.gnome.Shell.desktop[4766]: == Stack trace for context 0x55aa8e27e180 ==
  249. Feb 19 01:36:41 zulu journal[4766]: The offending signal was destroy on Gjs_ui_popupMenu_PopupSeparatorMenuItem 0x55aa8f6369f0.
  250. Feb 19 01:36:41 zulu org.gnome.Shell.desktop[4766]: == Stack trace for context 0x55aa8e27e180 ==
  251. Feb 19 01:36:41 zulu org.gnome.Shell.desktop[4766]: == Stack trace for context 0x55aa8e27e180 ==
  252. Feb 19 01:36:41 zulu org.gnome.Shell.desktop[4766]: == Stack trace for context 0x55aa8e27e180 ==
  253. Feb 19 01:36:41 zulu journal[4766]: 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. Feb 19 01:36:41 zulu org.gnome.Shell.desktop[4766]: == Stack trace for context 0x55aa8e27e180 ==
  255. Feb 19 01:36:41 zulu journal[4766]: The offending signal was destroy on Gjs_ui_popupMenu_PopupSeparatorMenuItem 0x55aa8f6369f0.
  256. Feb 19 01:36:41 zulu journal[4766]: 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.
  257. Feb 19 01:36:41 zulu journal[4766]: The offending signal was destroy on Gjs_ui_popupMenu_PopupSeparatorMenuItem 0x55aa8f6369f0.
  258. Feb 19 01:36:41 zulu journal[4766]: 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.
  259. Feb 19 01:36:41 zulu journal[4766]: The offending signal was destroy on Gjs_ui_popupMenu_PopupMenuItem 0x55aa8f63da10.
  260. Feb 19 01:36:41 zulu journal[4766]: 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.
  261. Feb 19 01:36:41 zulu journal[4766]: The offending signal was destroy on Gjs_ui_popupMenu_PopupMenuItem 0x55aa8f63da10.
  262. Feb 19 01:36:41 zulu journal[4766]: 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.
  263. Feb 19 01:36:41 zulu journal[4766]: The offending signal was destroy on Gjs_ui_popupMenu_PopupMenuItem 0x55aa8f63da10.
  264. Feb 19 01:36:41 zulu journal[4766]: 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.
  265. Feb 19 01:36:41 zulu journal[4766]: The offending signal was destroy on Gjs_ui_animation_Spinner 0x55aa8f693440.
  266. Feb 19 01:36:41 zulu journal[4766]: 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.
  267. Feb 19 01:36:41 zulu org.gnome.Shell.desktop[4766]: == Stack trace for context 0x55aa8e27e180 ==
  268. Feb 19 01:36:41 zulu org.gnome.Shell.desktop[4766]: == Stack trace for context 0x55aa8e27e180 ==
  269. Feb 19 01:36:41 zulu org.gnome.Shell.desktop[4766]: == Stack trace for context 0x55aa8e27e180 ==
  270. Feb 19 01:36:41 zulu org.gnome.Shell.desktop[4766]: == Stack trace for context 0x55aa8e27e180 ==
  271. Feb 19 01:36:41 zulu org.gnome.Shell.desktop[4766]: == Stack trace for context 0x55aa8e27e180 ==
  272. Feb 19 01:36:41 zulu org.gnome.Shell.desktop[4766]: == Stack trace for context 0x55aa8e27e180 ==
  273. Feb 19 01:36:41 zulu org.gnome.Shell.desktop[4766]: == Stack trace for context 0x55aa8e27e180 ==
  274. Feb 19 01:36:41 zulu org.gnome.Shell.desktop[4766]: == Stack trace for context 0x55aa8e27e180 ==
  275. Feb 19 01:36:41 zulu org.gnome.Shell.desktop[4766]: == Stack trace for context 0x55aa8e27e180 ==
  276. Feb 19 01:36:41 zulu org.gnome.Shell.desktop[4766]: == Stack trace for context 0x55aa8e27e180 ==
  277. Feb 19 01:36:41 zulu org.gnome.Shell.desktop[4766]: == Stack trace for context 0x55aa8e27e180 ==
  278. Feb 19 01:36:41 zulu org.gnome.Shell.desktop[4766]: == Stack trace for context 0x55aa8e27e180 ==
  279. Feb 19 01:36:41 zulu org.gnome.Shell.desktop[4766]: == Stack trace for context 0x55aa8e27e180 ==
  280. Feb 19 01:36:41 zulu org.gnome.Shell.desktop[4766]: == Stack trace for context 0x55aa8e27e180 ==
  281. Feb 19 01:36:41 zulu org.gnome.Shell.desktop[4766]: == Stack trace for context 0x55aa8e27e180 ==
  282. Feb 19 01:36:41 zulu org.gnome.Shell.desktop[4766]: == Stack trace for context 0x55aa8e27e180 ==
  283. Feb 19 01:36:41 zulu journal[4766]: The offending signal was destroy on Gjs_ui_animation_Spinner 0x55aa8f693440.
  284. Feb 19 01:36:41 zulu journal[4766]: 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.
  285. Feb 19 01:36:41 zulu journal[4766]: The offending signal was destroy on Gjs_ui_popupMenu_PopupSeparatorMenuItem 0x55aa8f689f40.
  286. Feb 19 01:36:41 zulu journal[4766]: 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.
  287. Feb 19 01:36:41 zulu journal[4766]: The offending signal was destroy on Gjs_ui_popupMenu_PopupSeparatorMenuItem 0x55aa8f689f40.
  288. Feb 19 01:36:41 zulu journal[4766]: 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.
  289. Feb 19 01:36:41 zulu dbus-daemon[4647]: [session uid=1000 pid=4645] Successfully activated service 'org.gnome.Shell.Screencast'
  290. Feb 19 01:36:41 zulu journal[4766]: The offending signal was destroy on Gjs_ui_popupMenu_PopupSeparatorMenuItem 0x55aa8f689f40.
  291. Feb 19 01:36:41 zulu journal[4766]: 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.
  292. Feb 19 01:36:41 zulu journal[4766]: The offending signal was destroy on Gjs_ui_popupMenu_PopupMenuItem 0x55aa8f697050.
  293. Feb 19 01:36:41 zulu journal[4766]: 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.
  294. Feb 19 01:36:41 zulu journal[4766]: The offending signal was destroy on Gjs_ui_popupMenu_PopupMenuItem 0x55aa8f697050.
  295. Feb 19 01:36:41 zulu journal[4766]: 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.
  296. Feb 19 01:36:41 zulu org.gnome.Shell.desktop[4766]: == Stack trace for context 0x55aa8e27e180 ==
  297. Feb 19 01:36:41 zulu org.gnome.Shell.desktop[4766]: == Stack trace for context 0x55aa8e27e180 ==
  298. Feb 19 01:36:41 zulu org.gnome.Shell.desktop[4766]: == Stack trace for context 0x55aa8e27e180 ==
  299. Feb 19 01:36:41 zulu org.gnome.Shell.desktop[4766]: == Stack trace for context 0x55aa8e27e180 ==
  300. Feb 19 01:36:41 zulu org.gnome.Shell.desktop[4766]: == Stack trace for context 0x55aa8e27e180 ==
  301. Feb 19 01:36:41 zulu journal[4766]: The offending signal was destroy on Gjs_ui_popupMenu_PopupMenuItem 0x55aa8f697050.
  302. Feb 19 01:36:41 zulu org.gnome.Shell.desktop[4766]: == Stack trace for context 0x55aa8e27e180 ==
  303. Feb 19 01:36:41 zulu org.gnome.Shell.desktop[4766]: == Stack trace for context 0x55aa8e27e180 ==
  304. Feb 19 01:36:41 zulu org.gnome.Shell.desktop[4766]: == Stack trace for context 0x55aa8e27e180 ==
  305. Feb 19 01:36:41 zulu org.gnome.Shell.desktop[4766]: == Stack trace for context 0x55aa8e27e180 ==
  306. Feb 19 01:36:41 zulu org.gnome.Shell.desktop[4766]: == Stack trace for context 0x55aa8e27e180 ==
  307. Feb 19 01:36:41 zulu org.gnome.Shell.desktop[4766]: == Stack trace for context 0x55aa8e27e180 ==
  308. Feb 19 01:36:41 zulu org.gnome.Shell.desktop[4766]: == Stack trace for context 0x55aa8e27e180 ==
  309. Feb 19 01:36:41 zulu journal[4766]: 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. Feb 19 01:36:41 zulu journal[4766]: The offending signal was destroy on Gjs_ui_popupMenu_PopupSeparatorMenuItem 0x55aa8f6b2140.
  311. Feb 19 01:36:41 zulu journal[4766]: 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. Feb 19 01:36:41 zulu journal[4766]: The offending signal was destroy on Gjs_ui_popupMenu_PopupSeparatorMenuItem 0x55aa8f6b2140.
  313. Feb 19 01:36:41 zulu journal[4766]: 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. Feb 19 01:36:41 zulu journal[4766]: The offending signal was destroy on Gjs_ui_popupMenu_PopupSeparatorMenuItem 0x55aa8f6b2140.
  315. Feb 19 01:36:41 zulu journal[4766]: 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. Feb 19 01:36:41 zulu journal[4766]: The offending signal was destroy on Gjs_ui_popupMenu_PopupMenuItem 0x55aa8f6b9c60.
  317. Feb 19 01:36:41 zulu journal[4766]: 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. Feb 19 01:36:41 zulu journal[4766]: The offending signal was destroy on Gjs_ui_popupMenu_PopupMenuItem 0x55aa8f6b9c60.
  319. Feb 19 01:36:41 zulu journal[4766]: 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. Feb 19 01:36:41 zulu journal[4766]: The offending signal was destroy on Gjs_ui_popupMenu_PopupMenuItem 0x55aa8f6b9c60.
  321. Feb 19 01:36:41 zulu journal[4766]: 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. Feb 19 01:36:41 zulu journal[4766]: The offending signal was destroy on Gjs_ui_popupMenu_PopupMenuItem 0x55aa8f6bed90.
  323. Feb 19 01:36:41 zulu journal[4766]: 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. Feb 19 01:36:41 zulu journal[4766]: The offending signal was destroy on Gjs_ui_popupMenu_PopupMenuItem 0x55aa8f6bed90.
  325. Feb 19 01:36:41 zulu journal[4766]: 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. Feb 19 01:36:41 zulu journal[4766]: The offending signal was destroy on Gjs_ui_popupMenu_PopupMenuItem 0x55aa8f6bed90.
  327. Feb 19 01:36:41 zulu journal[4766]: 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. Feb 19 01:36:41 zulu journal[4766]: The offending signal was destroy on Gjs_ui_popupMenu_PopupSeparatorMenuItem 0x55aa8f6d6160.
  329. Feb 19 01:36:41 zulu journal[4766]: 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. Feb 19 01:36:41 zulu journal[4766]: The offending signal was destroy on Gjs_ui_popupMenu_PopupSeparatorMenuItem 0x55aa8f6d6160.
  331. Feb 19 01:36:41 zulu journal[4766]: 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. Feb 19 01:36:41 zulu journal[4766]: The offending signal was destroy on Gjs_ui_popupMenu_PopupSeparatorMenuItem 0x55aa8f6d6160.
  333. Feb 19 01:36:41 zulu journal[4766]: 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. Feb 19 01:36:41 zulu journal[4766]: The offending signal was destroy on Gjs_ui_popupMenu_PopupMenuItem 0x55aa8f2d3630.
  335. Feb 19 01:36:41 zulu journal[4766]: 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. Feb 19 01:36:41 zulu journal[4766]: The offending signal was destroy on Gjs_ui_popupMenu_PopupMenuItem 0x55aa8f2d3630.
  337. Feb 19 01:36:41 zulu journal[4766]: 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. Feb 19 01:36:41 zulu journal[4766]: The offending signal was destroy on Gjs_ui_popupMenu_PopupMenuItem 0x55aa8f2d3630.
  339. Feb 19 01:36:41 zulu journal[4766]: 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. Feb 19 01:36:41 zulu journal[4766]: The offending signal was destroy on Gjs_ui_popupMenu_PopupSeparatorMenuItem 0x55aa8f70c3c0.
  341. Feb 19 01:36:41 zulu org.gnome.Shell.desktop[4766]: == Stack trace for context 0x55aa8e27e180 ==
  342. Feb 19 01:36:41 zulu org.gnome.Shell.desktop[4766]: == Stack trace for context 0x55aa8e27e180 ==
  343. Feb 19 01:36:41 zulu org.gnome.Shell.desktop[4766]: == Stack trace for context 0x55aa8e27e180 ==
  344. Feb 19 01:36:41 zulu org.gnome.Shell.desktop[4766]: == Stack trace for context 0x55aa8e27e180 ==
  345. Feb 19 01:36:41 zulu org.gnome.Shell.desktop[4766]: == Stack trace for context 0x55aa8e27e180 ==
  346. Feb 19 01:36:41 zulu org.gnome.Shell.desktop[4766]: == Stack trace for context 0x55aa8e27e180 ==
  347. Feb 19 01:36:41 zulu org.gnome.Shell.desktop[4766]: == Stack trace for context 0x55aa8e27e180 ==
  348. Feb 19 01:36:41 zulu org.gnome.Shell.desktop[4766]: == Stack trace for context 0x55aa8e27e180 ==
  349. Feb 19 01:36:41 zulu org.gnome.Shell.desktop[4766]: == Stack trace for context 0x55aa8e27e180 ==
  350. Feb 19 01:36:41 zulu org.gnome.Shell.desktop[4766]: == Stack trace for context 0x55aa8e27e180 ==
  351. Feb 19 01:36:41 zulu org.gnome.Shell.desktop[4766]: == Stack trace for context 0x55aa8e27e180 ==
  352. Feb 19 01:36:41 zulu org.gnome.Shell.desktop[4766]: == Stack trace for context 0x55aa8e27e180 ==
  353. Feb 19 01:36:41 zulu org.gnome.Shell.desktop[4766]: == Stack trace for context 0x55aa8e27e180 ==
  354. Feb 19 01:36:41 zulu org.gnome.Shell.desktop[4766]: == Stack trace for context 0x55aa8e27e180 ==
  355. Feb 19 01:36:41 zulu org.gnome.Shell.desktop[4766]: == Stack trace for context 0x55aa8e27e180 ==
  356. Feb 19 01:36:41 zulu org.gnome.Shell.desktop[4766]: == Stack trace for context 0x55aa8e27e180 ==
  357. Feb 19 01:36:41 zulu org.gnome.Shell.desktop[4766]: == Stack trace for context 0x55aa8e27e180 ==
  358. Feb 19 01:36:41 zulu org.gnome.Shell.desktop[4766]: == Stack trace for context 0x55aa8e27e180 ==
  359. Feb 19 01:36:41 zulu org.gnome.Shell.desktop[4766]: == Stack trace for context 0x55aa8e27e180 ==
  360. Feb 19 01:36:41 zulu org.gnome.Shell.desktop[4766]: == Stack trace for context 0x55aa8e27e180 ==
  361. Feb 19 01:36:41 zulu journal[4766]: 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. Feb 19 01:36:41 zulu journal[4766]: The offending signal was destroy on Gjs_ui_popupMenu_PopupSeparatorMenuItem 0x55aa8f70c3c0.
  363. Feb 19 01:36:41 zulu journal[4766]: 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. Feb 19 01:36:41 zulu journal[4766]: The offending signal was destroy on Gjs_ui_popupMenu_PopupSeparatorMenuItem 0x55aa8f70c3c0.
  365. Feb 19 01:36:41 zulu journal[4766]: 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. Feb 19 01:36:41 zulu journal[4766]: The offending signal was destroy on Gjs_ui_popupMenu_PopupMenuItem 0x55aa8f4796c0.
  367. Feb 19 01:36:41 zulu journal[4766]: 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. Feb 19 01:36:41 zulu journal[4766]: The offending signal was destroy on Gjs_ui_popupMenu_PopupMenuItem 0x55aa8f4796c0.
  369. Feb 19 01:36:41 zulu journal[4766]: 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. Feb 19 01:36:41 zulu journal[4766]: The offending signal was destroy on Gjs_ui_popupMenu_PopupMenuItem 0x55aa8f4796c0.
  371. Feb 19 01:36:41 zulu journal[4766]: 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. Feb 19 01:36:41 zulu journal[4766]: The offending signal was destroy on Gjs_status_system_PowerToggle 0x55aa8f7469f0.
  373. Feb 19 01:36:41 zulu journal[4766]: 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. Feb 19 01:36:41 zulu journal[4766]: The offending signal was destroy on Gjs_status_system_SettingsItem 0x55aa8ee86090.
  375. Feb 19 01:36:41 zulu journal[4766]: 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. Feb 19 01:36:41 zulu journal[4766]: The offending signal was destroy on Gjs_ui_popupMenu_PopupMenuItem 0x55aa8f78a790.
  377. Feb 19 01:36:41 zulu journal[4766]: 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. Feb 19 01:36:41 zulu journal[4766]: The offending signal was destroy on Gjs_ui_popupMenu_PopupMenuItem 0x55aa8f78a790.
  379. Feb 19 01:36:41 zulu journal[4766]: 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. Feb 19 01:36:41 zulu journal[4766]: The offending signal was destroy on Gjs_ui_popupMenu_PopupMenuItem 0x55aa8f78a790.
  381. Feb 19 01:36:41 zulu journal[4766]: 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. Feb 19 01:36:41 zulu journal[4766]: The offending signal was destroy on Gjs_ui_popupMenu_PopupMenuItem 0x55aa8f78f4a0.
  383. Feb 19 01:36:41 zulu journal[4766]: 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. Feb 19 01:36:41 zulu journal[4766]: The offending signal was destroy on Gjs_ui_popupMenu_PopupMenuItem 0x55aa8f78f4a0.
  385. Feb 19 01:36:41 zulu journal[4766]: 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. Feb 19 01:36:41 zulu journal[4766]: The offending signal was destroy on Gjs_ui_popupMenu_PopupMenuItem 0x55aa8f78f4a0.
  387. Feb 19 01:36:41 zulu journal[4766]: 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. Feb 19 01:36:41 zulu journal[4766]: The offending signal was destroy on Gjs_ui_popupMenu_PopupMenuItem 0x55aa8f7946a0.
  389. Feb 19 01:36:41 zulu journal[4766]: 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. Feb 19 01:36:41 zulu journal[4766]: The offending signal was destroy on Gjs_ui_popupMenu_PopupMenuItem 0x55aa8f7946a0.
  391. Feb 19 01:36:41 zulu journal[4766]: 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. Feb 19 01:36:41 zulu journal[4766]: The offending signal was destroy on Gjs_ui_popupMenu_PopupMenuItem 0x55aa8f7946a0.
  393. Feb 19 01:36:41 zulu journal[4766]: 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. Feb 19 01:36:41 zulu journal[4766]: The offending signal was destroy on Gjs_ui_popupMenu_PopupSeparatorMenuItem 0x55aa8f799930.
  395. Feb 19 01:36:41 zulu journal[4766]: 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. Feb 19 01:36:41 zulu journal[4766]: The offending signal was destroy on Gjs_ui_popupMenu_PopupSeparatorMenuItem 0x55aa8f799930.
  397. Feb 19 01:36:41 zulu journal[4766]: 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. Feb 19 01:36:41 zulu journal[4766]: The offending signal was destroy on Gjs_ui_popupMenu_PopupSeparatorMenuItem 0x55aa8f799930.
  399. Feb 19 01:36:41 zulu journal[4766]: 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. Feb 19 01:36:41 zulu journal[4766]: The offending signal was destroy on Gjs_ui_popupMenu_PopupMenuItem 0x55aa8f79e690.
  401. Feb 19 01:36:41 zulu journal[4766]: 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. Feb 19 01:36:41 zulu journal[4766]: The offending signal was destroy on Gjs_ui_popupMenu_PopupMenuItem 0x55aa8f79e690.
  403. Feb 19 01:36:41 zulu journal[4766]: 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. Feb 19 01:36:41 zulu journal[4766]: The offending signal was destroy on Gjs_ui_popupMenu_PopupMenuItem 0x55aa8f79e690.
  405. Feb 19 01:36:41 zulu journal[4766]: 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. Feb 19 01:36:41 zulu journal[4766]: The offending signal was destroy on Gjs_ui_popupMenu_PopupMenuItem 0x55aa8f7a4b20.
  407. Feb 19 01:36:41 zulu journal[4766]: 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. Feb 19 01:36:41 zulu journal[4766]: The offending signal was destroy on Gjs_ui_popupMenu_PopupMenuItem 0x55aa8f7a4b20.
  409. Feb 19 01:36:41 zulu journal[4766]: 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. Feb 19 01:36:41 zulu journal[4766]: The offending signal was destroy on Gjs_ui_popupMenu_PopupMenuItem 0x55aa8f7a4b20.
  411. Feb 19 01:36:41 zulu gnome-session[4494]: gnome-session-binary[4494]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1
  412. Feb 19 01:36:41 zulu gnome-session[4494]: gnome-session-binary[4494]: WARNING: App 'org.gnome.Shell.desktop' respawning too quickly
  413. Feb 19 01:36:41 zulu gnome-session-binary[4494]: Unrecoverable failure in required component org.gnome.Shell.desktop
  414. Feb 19 01:36:41 zulu gnome-session-binary[4494]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1
  415. Feb 19 01:36:41 zulu gnome-session-binary[4494]: WARNING: App 'org.gnome.Shell.desktop' respawning too quickly
  416. Feb 19 01:36:41 zulu dbus-daemon[4647]: [session uid=1000 pid=4645] Activating service name='ca.desrt.dconf' requested by ':1.8' (uid=1000 pid=4494 comm="/usr/libexec/gnome-session-binary" label="kernel")
  417. Feb 19 01:36:41 zulu dbus-daemon[4647]: [session uid=1000 pid=4645] Successfully activated service 'ca.desrt.dconf'
  418. Feb 19 01:36:42 zulu org.gnome.SettingsDaemon.MediaKeys.desktop[4859]: /usr/libexec/gsd-media-keys: symbol lookup error: /lib64/libsndfile.so.1: undefined symbol: lame_encode_buffer_interleaved_int
  419. Feb 19 01:36:42 zulu gnome-session[4494]: gnome-session-binary[4494]: WARNING: App 'org.gnome.SettingsDaemon.MediaKeys.desktop' exited with code 127
  420. Feb 19 01:36:42 zulu gnome-session-binary[4494]: WARNING: App 'org.gnome.SettingsDaemon.MediaKeys.desktop' exited with code 127
  421. Feb 19 01:36:42 zulu audit: BPF prog-id=107 op=LOAD
  422. Feb 19 01:36:42 zulu audit: BPF prog-id=108 op=LOAD
  423. Feb 19 01:36:42 zulu audit: BPF prog-id=109 op=LOAD
  424. Feb 19 01:36:42 zulu kernel: audit: type=1334 audit(1676792202.412:441): prog-id=107 op=LOAD
  425. Feb 19 01:36:42 zulu kernel: audit: type=1334 audit(1676792202.412:442): prog-id=108 op=LOAD
  426. Feb 19 01:36:42 zulu kernel: audit: type=1334 audit(1676792202.412:443): prog-id=109 op=LOAD
  427. Feb 19 01:36:42 zulu systemd[1]: Starting systemd-hostnamed.service - Hostname Service...
  428. Feb 19 01:36:42 zulu org.gnome.SettingsDaemon.Sound.desktop[4897]: /usr/libexec/gsd-sound: symbol lookup error: /lib64/libsndfile.so.1: undefined symbol: lame_encode_buffer_interleaved_int
  429. Feb 19 01:36:42 zulu gnome-session[4494]: gnome-session-binary[4494]: WARNING: App 'org.gnome.SettingsDaemon.Sound.desktop' exited with code 127
  430. Feb 19 01:36:42 zulu gnome-session-binary[4494]: WARNING: App 'org.gnome.SettingsDaemon.Sound.desktop' exited with code 127
  431. Feb 19 01:36:42 zulu org.gnome.SettingsDaemon.MediaKeys.desktop[4899]: /usr/libexec/gsd-media-keys: symbol lookup error: /lib64/libsndfile.so.1: undefined symbol: lame_encode_buffer_interleaved_int
  432. Feb 19 01:36:42 zulu gnome-session[4494]: gnome-session-binary[4494]: WARNING: App 'org.gnome.SettingsDaemon.MediaKeys.desktop' exited with code 127
  433. Feb 19 01:36:42 zulu gnome-session-binary[4494]: WARNING: App 'org.gnome.SettingsDaemon.MediaKeys.desktop' exited with code 127
  434. Feb 19 01:36:42 zulu gnome-session-binary[4494]: Unrecoverable failure in required component org.gnome.SettingsDaemon.MediaKeys.desktop
  435. Feb 19 01:36:42 zulu gnome-session[4494]: gnome-session-binary[4494]: WARNING: App 'org.gnome.SettingsDaemon.MediaKeys.desktop' respawning too quickly
  436. Feb 19 01:36:42 zulu gnome-session-binary[4494]: WARNING: App 'org.gnome.SettingsDaemon.MediaKeys.desktop' respawning too quickly
  437. Feb 19 01:36:42 zulu org.a11y.Bus[4668]: dbus-daemon[4668]: Activating service name='org.a11y.atspi.Registry' requested by ':1.4' (uid=1000 pid=4866 comm="/usr/libexec/gsd-wacom" label="kernel")
  438. Feb 19 01:36:42 zulu dbus-daemon[4647]: [session uid=1000 pid=4645] Activating service name='org.freedesktop.systemd1' requested by ':1.28' (uid=1000 pid=4880 comm="/usr/libexec/gsd-sharing" label="kernel")
  439. Feb 19 01:36:42 zulu org.gnome.SettingsDaemon.Sound.desktop[4929]: /usr/libexec/gsd-sound: symbol lookup error: /lib64/libsndfile.so.1: undefined symbol: lame_encode_buffer_interleaved_int
  440. Feb 19 01:36:42 zulu dbus-daemon[4647]: [session uid=1000 pid=4645] Activating service name='org.gnome.ScreenSaver' requested by ':1.23' (uid=1000 pid=4856 comm="/usr/libexec/gsd-usb-protection" label="kernel")
  441. Feb 19 01:36:42 zulu dbus-daemon[4647]: [session uid=1000 pid=4645] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1
  442. Feb 19 01:36:42 zulu journal[4880]: Failed to StopUnit service: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.freedesktop.systemd1 exited with status 1
  443. Feb 19 01:36:42 zulu journal[4880]: Failed to StopUnit service: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.freedesktop.systemd1 exited with status 1
  444. Feb 19 01:36:42 zulu gnome-session[4494]: gnome-session-binary[4494]: WARNING: App 'org.gnome.SettingsDaemon.Sound.desktop' exited with code 127
  445. Feb 19 01:36:42 zulu gnome-session[4494]: gnome-session-binary[4494]: WARNING: App 'org.gnome.SettingsDaemon.Sound.desktop' respawning too quickly
  446. Feb 19 01:36:42 zulu gnome-session-binary[4494]: WARNING: App 'org.gnome.SettingsDaemon.Sound.desktop' exited with code 127
  447. Feb 19 01:36:42 zulu gnome-session-binary[4494]: Unrecoverable failure in required component org.gnome.SettingsDaemon.Sound.desktop
  448. Feb 19 01:36:42 zulu gnome-session-binary[4494]: WARNING: App 'org.gnome.SettingsDaemon.Sound.desktop' respawning too quickly
  449. Feb 19 01:36:42 zulu journal[4874]: Failed to get current display configuration state: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.gnome.Mutter.DisplayConfig" does not exist
  450. Feb 19 01:36:42 zulu org.a11y.Bus[4668]: dbus-daemon[4668]: Successfully activated service 'org.a11y.atspi.Registry'
  451. Feb 19 01:36:42 zulu org.a11y.Bus[4940]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
  452. Feb 19 01:36:42 zulu cupsd[1026]: REQUEST localhost - - "POST / HTTP/1.1" 200 361 Create-Printer-Subscriptions successful-ok
  453. Feb 19 01:36:42 zulu kernel: audit: type=1334 audit(1676792202.760:444): prog-id=110 op=LOAD
  454. Feb 19 01:36:42 zulu kernel: audit: type=1334 audit(1676792202.760:445): prog-id=111 op=LOAD
  455. Feb 19 01:36:42 zulu kernel: audit: type=1334 audit(1676792202.760:446): prog-id=112 op=LOAD
  456. Feb 19 01:36:42 zulu audit: BPF prog-id=110 op=LOAD
  457. Feb 19 01:36:42 zulu audit: BPF prog-id=111 op=LOAD
  458. Feb 19 01:36:42 zulu audit: BPF prog-id=112 op=LOAD
  459. Feb 19 01:36:42 zulu systemd[1]: Starting systemd-localed.service - Locale Service...
  460. Feb 19 01:36:42 zulu kernel: audit: type=1130 audit(1676792202.962:447): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=kernel msg='unit=systemd-hostnamed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
  461. Feb 19 01:36:42 zulu audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=kernel msg='unit=systemd-hostnamed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
  462. Feb 19 01:36:42 zulu systemd[1]: Started systemd-hostnamed.service - Hostname Service.
  463. Feb 19 01:36:43 zulu dbus-daemon[4647]: [session uid=1000 pid=4645] Successfully activated service 'org.gnome.ScreenSaver'
  464. Feb 19 01:36:43 zulu journal[4856]: Failed to get screen saver status: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: Object does not exist at path “/org/gnome/ScreenSaver”
  465. Feb 19 01:36:43 zulu journal[4856]: Failed to fetch USBGuard parameters: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name is not activatable
  466. Feb 19 01:36:43 zulu gnome-session[4494]: gnome-session-binary[4494]: WARNING: Could not retrieve current screensaver active state: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying
  467. Feb 19 01:36:43 zulu gnome-session-binary[4494]: WARNING: Could not retrieve current screensaver active state: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying
  468. Feb 19 01:36:43 zulu dbus-daemon[4647]: [session uid=1000 pid=4645] Activating service name='org.freedesktop.problems.applet' requested by ':1.8' (uid=1000 pid=4494 comm="/usr/libexec/gnome-session-binary" label="kernel")
  469. Feb 19 01:36:43 zulu vmware-user.desktop[5048]: vmware-user: could not open /proc/fs/vmblock/dev
  470. Feb 19 01:36:43 zulu kernel: audit: type=1130 audit(1676792203.559:448): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=kernel msg='unit=systemd-localed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
  471. Feb 19 01:36:43 zulu audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=kernel msg='unit=systemd-localed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
  472. Feb 19 01:36:43 zulu systemd[1]: Started systemd-localed.service - Locale Service.
  473. Feb 19 01:36:43 zulu dbus-daemon[4647]: [session uid=1000 pid=4645] Activating service name='com.redhat.imsettings' requested by ':1.44' (uid=1000 pid=5038 comm="imsettings-switch -n -q -x" label="kernel")
  474. Feb 19 01:36:43 zulu dbus-daemon[4647]: [session uid=1000 pid=4645] Successfully activated service 'com.redhat.imsettings'
  475. Feb 19 01:36:43 zulu dbus-daemon[4647]: [session uid=1000 pid=4645] Successfully activated service 'org.freedesktop.problems.applet'
  476. Feb 19 01:36:43 zulu org.freedesktop.problems.applet[5031]: Failed to rename ‘/home/tcarr/.abrt/spool’ to ‘/home/tcarr/.cache/abrt/spool’: No such file or directory
  477. Feb 19 01:36:43 zulu org.freedesktop.problems.applet[5031]: Failed to rename ‘/home/tcarr/.abrt/settings’ to ‘/home/tcarr/.config/abrt/settings’: No such file or directory
  478. Feb 19 01:36:43 zulu com.redhat.imsettings[5060]: [ 43.701316]: IMSettings-Daemon[5060]: INFO: Starting imsettings-daemon...
  479. Feb 19 01:36:43 zulu com.redhat.imsettings[5060]: [ 43.701545]: IMSettings-Daemon[5060]: INFO: [HOME=/home/tcarr/.config/imsettings]
  480. Feb 19 01:36:43 zulu com.redhat.imsettings[5060]: [ 43.701636]: IMSettings-Daemon[5060]: INFO: [XINPUTRCDIR=/etc/X11/xinit/]
  481. Feb 19 01:36:43 zulu com.redhat.imsettings[5060]: [ 43.701720]: IMSettings-Daemon[5060]: INFO: [XINPUTDIR=/etc/X11/xinit/xinput.d/]
  482. Feb 19 01:36:43 zulu com.redhat.imsettings[5060]: [ 43.701804]: IMSettings-Daemon[5060]: INFO: [MODULEDIR=/usr/lib64/imsettings]
  483. Feb 19 01:36:43 zulu com.redhat.imsettings[5060]: [ 43.701887]: IMSettings-Daemon[5060]: INFO: [MODULES=gsettings]
  484. Feb 19 01:36:43 zulu gnome-session-binary[4494]: Entering running state
  485. Feb 19 01:36:43 zulu com.redhat.imsettings[5060]: imsettings_server_bus_method_call: sender[:1.44] path[/com/redhat/imsettings] iface[com.redhat.imsettings] method[GetVersion]
  486. Feb 19 01:36:43 zulu com.redhat.imsettings[5060]: imsettings_server_bus_method_call: sender[:1.44] path[/com/redhat/imsettings] iface[com.redhat.imsettings] method[IsSupportedDesktop]
  487. Feb 19 01:36:43 zulu imsettings-start.desktop[5038]: Current desktop isn't supported by IMSettings. Please follow instructions on your desktop to enable Input Method.
  488. Feb 19 01:36:43 zulu libcanberra-login-sound.desktop[5040]: Failed to play sound: File or data not found
  489. Feb 19 01:36:44 zulu journal[5048]: gtk_disable_setlocale() must be called before gtk_init()
  490. Feb 19 01:36:44 zulu dbus-daemon[4647]: [session uid=1000 pid=4645] Activating service name='org.freedesktop.portal.Desktop' requested by ':1.49' (uid=1000 pid=5021 comm="/usr/bin/gnome-software --gapplication-service" label="kernel")
  491. Feb 19 01:36:44 zulu cupsd[1026]: REQUEST localhost - - "POST / HTTP/1.1" 200 153 Cancel-Subscription successful-ok
  492. Feb 19 01:36:44 zulu cupsd[1026]: REQUEST localhost - - "POST / HTTP/1.1" 200 153 Cancel-Subscription client-error-not-found
  493. Feb 19 01:36:44 zulu dbus-daemon[4647]: [session uid=1000 pid=4645] Activating service name='org.freedesktop.systemd1' requested by ':1.28' (uid=1000 pid=4880 comm="/usr/libexec/gsd-sharing" label="kernel")
  494. Feb 19 01:36:44 zulu org.freedesktop.portal.Desktop[5191]: error: No session bus: The connection is closed
  495. Feb 19 01:36:44 zulu org.gnome.Shell.CalendarServer[4724]: gnome-shell-calendar-server[4724]: Lost (or failed to acquire) the name org.gnome.Shell.CalendarServer - exiting
  496. Feb 19 01:36:44 zulu com.redhat.imsettings[5060]: [ 44.850496]: IMSettings-Daemon[5060]: INFO: Release the ownership of com.redhat.imsettings
  497. Feb 19 01:36:44 zulu com.redhat.imsettings[5060]: Exiting...
  498. Feb 19 01:36:44 zulu com.redhat.imsettings[5060]: [ 44.850858]: libnotify[5060]: DEBUG: SNAP app: (null)
  499. Feb 19 01:36:44 zulu journal[4798]: Error setting property 'ConnectionStatus' on interface org.gnome.evolution.dataserver.Source: The connection is closed (g-io-error-quark, 18)
  500. Feb 19 01:36:44 zulu org.gtk.vfs.Daemon[4654]: A connection to the bus can't be made
  501. Feb 19 01:36:44 zulu com.redhat.imsettings[5060]: [ 44.851037]: GLib-GIO[5060]: CRITICAL **: Error while sending AddMatch() message: The connection is closed
  502. Feb 19 01:36:44 zulu com.redhat.imsettings[5060]: [ 44.862155]: GLib-GIO[5060]: CRITICAL **: Error while sending AddMatch() message: The connection is closed
  503. Feb 19 01:36:44 zulu com.redhat.imsettings[5060]: [ 44.862367]: IMSettings-Daemon[5060]: INFO: Unloading imesttings module: gsettings
  504. Feb 19 01:36:44 zulu com.redhat.imsettings[5060]: [ 44.868163]: IMSettings-Daemon[5060]: INFO: imsettings-daemon is shut down.
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement
Public Pastes
Advertisement
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!