Sep 25 06:43:16 hostname gnome-shell[1606]: 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. Sep 25 06:43:16 hostname gnome-shell[1606]: The offending signal was destroy on Gjs_ui_panel_AppMenuButton 0x562041f2e670. Sep 25 06:43:16 hostname gnome-shell[1606]: 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. Sep 25 06:43:16 hostname gnome-shell[1606]: The offending signal was destroy on Gjs_ui_panel_AppMenuButton 0x562041f2e670. Sep 25 06:43:16 hostname gnome-shell[1606]: 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. Sep 25 06:43:16 hostname gnome-shell[1606]: The offending signal was destroy on Gjs_ui_panel_AppMenuButton 0x562041f2e670. Sep 25 06:43:16 hostname gnome-shell[1606]: 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. Sep 25 06:43:16 hostname gnome-shell[1606]: The offending signal was destroy on Gjs_ui_panel_AppMenuButton 0x562041f2e670. Sep 25 06:43:16 hostname gnome-shell[1606]: 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. Sep 25 06:43:16 hostname gnome-shell[1606]: The offending signal was destroy on Gjs_ui_panel_AppMenuButton 0x562041f2e670. Sep 25 06:43:16 hostname gnome-shell[1606]: 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. Sep 25 06:43:16 hostname gnome-shell[1606]: The offending signal was destroy on Gjs_ui_panel_AppMenuButton 0x562041f2e670. Sep 25 06:43:16 hostname gnome-shell[1606]: 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. Sep 25 06:43:16 hostname gnome-shell[1606]: The offending signal was destroy on Gjs_ui_panel_AppMenuButton 0x562041f2e670. Sep 25 06:43:16 hostname gnome-shell[1606]: 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. Sep 25 06:43:16 hostname gnome-shell[1606]: The offending signal was destroy on Gjs_ui_animation_Spinner 0x562042970570. Sep 25 06:43:16 hostname gnome-shell[1606]: 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. Sep 25 06:43:16 hostname gnome-shell[1606]: The offending signal was destroy on Gjs_ui_animation_Spinner 0x562042970570. Sep 25 06:43:16 hostname tracker-miner-f[1482]: Owner of volume monitor org.gtk.vfs.AfcVolumeMonitor disconnected from the bus; removing drives/volumes/mounts Sep 25 06:43:16 hostname tracker-miner-f[1482]: Owner of volume monitor org.gtk.vfs.GoaVolumeMonitor disconnected from the bus; removing drives/volumes/mounts Sep 25 06:43:16 hostname tracker-miner-f[1482]: Owner of volume monitor org.gtk.vfs.GPhoto2VolumeMonitor disconnected from the bus; removing drives/volumes/mounts Sep 25 06:43:16 hostname tracker-miner-f[1482]: Owner of volume monitor org.gtk.vfs.MTPVolumeMonitor disconnected from the bus; removing drives/volumes/mounts Sep 25 06:43:16 hostname tracker-miner-f[1482]: Owner of volume monitor org.gtk.vfs.UDisks2VolumeMonitor disconnected from the bus; removing drives/volumes/mounts Sep 25 06:43:16 hostname gnome-shell[1606]: 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. Sep 25 06:43:16 hostname gnome-shell[1606]: The offending signal was access-point-removed on NMDeviceWifi 0x562043d60320. Sep 25 06:43:16 hostname gnome-shell[1606]: 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. Sep 25 06:43:16 hostname gnome-shell[1606]: The offending signal was access-point-removed on NMDeviceWifi 0x562043d60320. Sep 25 06:43:16 hostname gnome-shell[1606]: 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. Sep 25 06:43:16 hostname gnome-shell[1606]: The offending signal was access-point-removed on NMDeviceWifi 0x562043d60320. Sep 25 06:43:16 hostname gnome-shell[1606]: 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. Sep 25 06:43:16 hostname gnome-shell[1606]: The offending signal was notify on NMDeviceEthernet 0x562043d5e240. Sep 25 06:43:16 hostname gnome-shell[1606]: 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. Sep 25 06:43:16 hostname gnome-shell[1606]: The offending signal was notify on NMDeviceEthernet 0x562043d5e240. Sep 25 06:43:16 hostname gnome-shell[1606]: 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. Sep 25 06:43:16 hostname gnome-shell[1606]: The offending signal was notify on NMAccessPoint 0x7fbd8c001f40. Sep 25 06:43:16 hostname gnome-shell[1606]: 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. Sep 25 06:43:16 hostname gnome-shell[1606]: The offending signal was notify on NMAccessPoint 0x7fbd8c001f40. Sep 25 06:43:16 hostname gnome-shell[1606]: 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. Sep 25 06:43:16 hostname gnome-shell[1606]: The offending signal was notify on NMAccessPoint 0x7fbd8c001f40. Sep 25 06:43:16 hostname gnome-shell[1606]: 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. Sep 25 06:43:16 hostname gnome-shell[1606]: The offending signal was notify on NMAccessPoint 0x562043d5b020. Sep 25 06:43:16 hostname gnome-shell[1606]: 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. Sep 25 06:43:16 hostname gnome-shell[1606]: The offending signal was notify on NMDeviceWifi 0x562043d60320. Sep 25 06:43:16 hostname gnome-shell[1606]: 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. Sep 25 06:43:16 hostname gnome-shell[1606]: The offending signal was notify on NMDeviceWifi 0x562043d60320. Sep 25 06:43:16 hostname gnome-shell[1606]: 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. Sep 25 06:43:16 hostname gnome-shell[1606]: The offending signal was notify on NMDeviceWifi 0x562043d60320. Sep 25 06:43:16 hostname gnome-shell[1606]: 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. Sep 25 06:43:16 hostname gnome-shell[1606]: The offending signal was notify on NMActiveConnection 0x562043d67180. Sep 25 06:43:16 hostname gnome-shell[1606]: 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. Sep 25 06:43:16 hostname gnome-shell[1606]: The offending signal was notify on NMActiveConnection 0x562043d67180. Sep 25 06:43:16 hostname gnome-shell[1606]: 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. Sep 25 06:43:16 hostname gnome-shell[1606]: The offending signal was notify on NMAccessPoint 0x5620460ebf10. Sep 25 06:43:16 hostname gnome-shell[1606]: 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. Sep 25 06:43:16 hostname gnome-shell[1606]: The offending signal was state-changed on NMDeviceEthernet 0x562043d5e240. Sep 25 06:43:16 hostname gnome-shell[1606]: 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. Sep 25 06:43:16 hostname gnome-shell[1606]: The offending signal was state-changed on NMDeviceWifi 0x562043d60320. Sep 25 06:43:16 hostname gnome-shell[1606]: 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. Sep 25 06:43:16 hostname gnome-shell[1606]: The offending signal was state-changed on NMDeviceWifi 0x562043d60320. Sep 25 06:43:16 hostname gnome-shell[1606]: 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. Sep 25 06:43:16 hostname gnome-shell[1606]: The offending signal was destroy on Gjs_ui_appDisplay_FolderGrid 0x562043e159a0. Sep 25 06:43:16 hostname gnome-shell[1606]: 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. Sep 25 06:43:16 hostname gnome-shell[1606]: The offending signal was destroy on Gjs_ui_appDisplay_FolderGrid 0x562043e159a0. Sep 25 06:43:16 hostname gnome-shell[1606]: 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. Sep 25 06:43:16 hostname gnome-shell[1606]: The offending signal was destroy on Gjs_ui_appDisplay_FolderGrid 0x562043e159a0. Sep 25 06:43:16 hostname gnome-shell[1606]: 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. Sep 25 06:43:16 hostname gnome-shell[1606]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x562043c71bd0. Sep 25 06:43:16 hostname gnome-shell[1606]: 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. Sep 25 06:43:16 hostname gnome-shell[1606]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x562043c71bd0. Sep 25 06:43:16 hostname gnome-shell[1606]: 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. Sep 25 06:43:16 hostname gnome-shell[1606]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x562043c71bd0. Sep 25 06:43:16 hostname gnome-shell[1606]: 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. Sep 25 06:43:16 hostname gnome-shell[1606]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x562043c71bd0. Sep 25 06:43:16 hostname gnome-shell[1606]: 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. Sep 25 06:43:16 hostname gnome-shell[1606]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x562043c8c6d0. Sep 25 06:43:16 hostname gnome-shell[1606]: 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. Sep 25 06:43:16 hostname gnome-shell[1606]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x562043e159a0. Sep 25 06:43:16 hostname gnome-shell[1606]: 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. Sep 25 06:43:16 hostname gnome-shell[1606]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x56204671e140. Sep 25 06:43:16 hostname gnome-shell[1606]: 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. Sep 25 06:43:16 hostname gnome-shell[1606]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x56204671e140. Sep 25 06:43:16 hostname gnome-shell[1606]: 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. Sep 25 06:43:16 hostname gnome-shell[1606]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x56204671e140. Sep 25 06:43:16 hostname gnome-shell[1606]: 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. Sep 25 06:43:16 hostname gnome-shell[1606]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x56204671e140. Sep 25 06:43:16 hostname gnome-shell[1606]: 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. Sep 25 06:43:16 hostname gnome-shell[1606]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x562043c74340. Sep 25 06:43:16 hostname gnome-shell[1606]: 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. Sep 25 06:43:16 hostname gnome-shell[1606]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x562043e159a0. Sep 25 06:43:16 hostname gnome-shell[1606]: 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. Sep 25 06:43:16 hostname gnome-shell[1606]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x56204409b4f0. Sep 25 06:43:16 hostname gnome-shell[1606]: 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. Sep 25 06:43:16 hostname gnome-shell[1606]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x56204409b4f0. Sep 25 06:43:16 hostname gnome-shell[1606]: 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. Sep 25 06:43:16 hostname gnome-shell[1606]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x56204409b4f0. Sep 25 06:43:16 hostname gnome-shell[1606]: 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. Sep 25 06:43:16 hostname gnome-shell[1606]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x56204409b4f0. Sep 25 06:43:16 hostname gnome-shell[1606]: 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. Sep 25 06:43:16 hostname gnome-shell[1606]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x562043c5f990. Sep 25 06:43:16 hostname gnome-shell[1606]: 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. Sep 25 06:43:16 hostname gnome-shell[1606]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x562043e159a0. Sep 25 06:43:16 hostname gnome-shell[1606]: 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. Sep 25 06:43:16 hostname gnome-shell[1606]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x562043d9a490. Sep 25 06:43:16 hostname gnome-shell[1606]: 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. Sep 25 06:43:16 hostname gnome-shell[1606]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x562043d9a490. Sep 25 06:43:16 hostname gnome-shell[1606]: 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. Sep 25 06:43:16 hostname gnome-shell[1606]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x562043d9a490. Sep 25 06:43:16 hostname gnome-shell[1606]: 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. Sep 25 06:43:16 hostname gnome-shell[1606]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x562043d9a490. Sep 25 06:43:16 hostname gnome-shell[1606]: 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. Sep 25 06:43:16 hostname gnome-shell[1606]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x562043c4a2b0. Sep 25 06:43:16 hostname gnome-shell[1606]: 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. Sep 25 06:43:16 hostname gnome-shell[1606]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x562043e159a0. Sep 25 06:43:16 hostname gnome-shell[1606]: 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. Sep 25 06:43:16 hostname gnome-shell[1606]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x562043d97560. Sep 25 06:43:16 hostname gdm3[775]: Gdm: Failed to contact accountsservice: Error calling StartServiceByName for org.freedesktop.Accounts: Transaction for accounts-daemon.service/start is destructive (sysinit.target has 'stop' job queued, but 'start' is included in transaction). Sep 25 06:43:16 hostname gnome-shell[1606]: 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. Sep 25 06:43:16 hostname gnome-shell[1606]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x562043d97560. Sep 25 06:43:16 hostname gnome-shell[1606]: 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. Sep 25 06:43:16 hostname gnome-shell[1606]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x562043d97560. Sep 25 06:43:16 hostname gnome-shell[1606]: 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. Sep 25 06:43:16 hostname gnome-shell[1606]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x562043d97560. Sep 25 06:43:16 hostname gnome-shell[1606]: 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. Sep 25 06:43:16 hostname gnome-shell[1606]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x562043c42c40. Sep 25 06:43:16 hostname gnome-shell[1606]: 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. Sep 25 06:43:16 hostname gnome-shell[1606]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x562043e159a0. Sep 25 06:43:16 hostname gnome-shell[1606]: 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. Sep 25 06:43:16 hostname gnome-shell[1606]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x562043d94bc0. Sep 25 06:43:16 hostname gnome-shell[1606]: 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. Sep 25 06:43:16 hostname gnome-shell[1606]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x562043d94bc0. Sep 25 06:43:16 hostname gnome-shell[1606]: 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. Sep 25 06:43:16 hostname gnome-shell[1606]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x562043d94bc0. Sep 25 06:43:16 hostname gnome-shell[1606]: 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. Sep 25 06:43:16 hostname gnome-shell[1606]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x562043d94bc0. Sep 25 06:43:16 hostname gnome-shell[1606]: 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. Sep 25 06:43:16 hostname gnome-shell[1606]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x562043c243c0. Sep 25 06:43:16 hostname gnome-shell[1606]: 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. Sep 25 06:43:16 hostname gnome-shell[1606]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x562043e159a0. Sep 25 06:43:16 hostname gnome-shell[1606]: 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. Sep 25 06:43:16 hostname gnome-shell[1606]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x562043d936f0. Sep 25 06:43:16 hostname gnome-shell[1606]: 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. Sep 25 06:43:16 hostname gnome-shell[1606]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x562043d936f0. Sep 25 06:43:16 hostname gnome-shell[1606]: 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. Sep 25 06:43:16 hostname gnome-shell[1606]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x562043d936f0. Sep 25 06:43:16 hostname gnome-shell[1606]: 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. Sep 25 06:43:16 hostname gnome-shell[1606]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x562043d936f0. Sep 25 06:43:16 hostname gnome-shell[1606]: 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. Sep 25 06:43:16 hostname gnome-shell[1606]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x5620436cd840. Sep 25 06:43:16 hostname gnome-shell[1606]: 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. Sep 25 06:43:16 hostname gnome-shell[1606]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x562043e159a0. Sep 25 06:43:16 hostname gnome-shell[1606]: 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. Sep 25 06:43:16 hostname gnome-shell[1606]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x562043d91a10. Sep 25 06:43:16 hostname gnome-shell[1606]: 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. Sep 25 06:43:16 hostname gnome-shell[1606]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x562043d91a10. Sep 25 06:43:16 hostname gnome-shell[1606]: 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. Sep 25 06:43:16 hostname gnome-shell[1606]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x562043d91a10. Sep 25 06:43:16 hostname gnome-shell[1606]: 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. Sep 25 06:43:16 hostname gnome-shell[1606]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x562043d91a10. Sep 25 06:43:16 hostname gnome-shell[1606]: 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. Sep 25 06:43:16 hostname gnome-shell[1606]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x56204338d080. Sep 25 06:43:16 hostname gnome-shell[1606]: 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. Sep 25 06:43:16 hostname gnome-shell[1606]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x562043e159a0. Sep 25 06:43:16 hostname gnome-shell[1606]: 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. Sep 25 06:43:16 hostname gnome-shell[1606]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x562043d8f870. Sep 25 06:43:16 hostname gnome-shell[1606]: 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. Sep 25 06:43:16 hostname gnome-shell[1606]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x562043d8f870. Sep 25 06:43:16 hostname gnome-shell[1606]: 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. Sep 25 06:43:16 hostname gnome-shell[1606]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x562043d8f870. Sep 25 06:43:16 hostname gnome-shell[1606]: 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. Sep 25 06:43:16 hostname gnome-shell[1606]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x562043d8f870. Sep 25 06:43:16 hostname gnome-shell[1606]: 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. Sep 25 06:43:16 hostname gnome-shell[1606]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x562043a06010. Sep 25 06:43:16 hostname gnome-shell[1606]: 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. Sep 25 06:43:16 hostname gnome-shell[1606]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x562043e159a0. Sep 25 06:43:16 hostname gnome-shell[1606]: 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. Sep 25 06:43:16 hostname gnome-shell[1606]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x562043cc5470. Sep 25 06:43:16 hostname gnome-shell[1606]: 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. Sep 25 06:43:16 hostname gnome-shell[1606]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x562043cc5470. Sep 25 06:43:16 hostname gnome-shell[1606]: 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. Sep 25 06:43:16 hostname gnome-shell[1606]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x562043cc5470. Sep 25 06:43:16 hostname gnome-shell[1606]: 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. Sep 25 06:43:16 hostname gnome-shell[1606]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x562043cc5470. Sep 25 06:43:16 hostname gnome-shell[1606]: 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. Sep 25 06:43:16 hostname gnome-shell[1606]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x5620439203b0. Sep 25 06:43:16 hostname gnome-shell[1606]: 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. Sep 25 06:43:16 hostname gnome-shell[1606]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x562043e159a0. Sep 25 06:43:16 hostname gnome-shell[1606]: 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. Sep 25 06:43:16 hostname gnome-shell[1606]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x562043d8b020. Sep 25 06:43:16 hostname gnome-shell[1606]: 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. Sep 25 06:43:16 hostname gnome-shell[1606]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x562043d8b020. Sep 25 06:43:16 hostname gnome-shell[1606]: 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. Sep 25 06:43:16 hostname gnome-shell[1606]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x562043d8b020. Sep 25 06:43:16 hostname gnome-shell[1606]: 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. Sep 25 06:43:16 hostname gnome-shell[1606]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x562043d8b020. Sep 25 06:43:16 hostname gnome-shell[1606]: 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. Sep 25 06:43:16 hostname gnome-shell[1606]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x56204281ecd0. Sep 25 06:43:16 hostname gnome-shell[1606]: 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. Sep 25 06:43:16 hostname gnome-shell[1606]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x562043e159a0. Sep 25 06:43:16 hostname gnome-shell[1606]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. Sep 25 06:43:16 hostname gnome-shell[1606]: The offending callback was set_container(), a vfunc. Sep 25 06:43:16 hostname gnome-shell[1606]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. Sep 25 06:43:16 hostname gnome-shell[1606]: The offending callback was set_container(), a vfunc. Sep 25 06:43:16 hostname systemd[1]: gdm.service: Failed with result 'exit-code'. Sep 25 06:43:16 hostname systemd[1]: gdm.service: Failed to enqueue OnFailure= job, ignoring: Transaction for plymouth-quit.service/start is destructive (sysinit.target has 'stop' job queued, but 'start' is included in transaction). Sep 25 06:43:16 hostname systemd[1402]: xdg-document-portal.service: Failed with result 'exit-code'. Sep 25 06:43:16 hostname systemd[1402]: xdg-permission-store.service: Failed with result 'exit-code'. Sep 25 06:43:16 hostname gnome-session-c[6618]: Couldn't connect to session bus: Error receiving data: Connection reset by peer Sep 25 06:43:16 hostname systemd[1402]: ssh-agent.service: Failed with result 'exit-code'. Sep 25 06:43:17 hostname NetworkManager[668]: [1664077397.0120] dispatcher: (7) failed (after 0.004 sec): Transaction for NetworkManager-dispatcher.service/start is destructive (systemd-tmpfiles-setup.service has 'stop' job queued, but 'start' is included in transaction). -- Boot 44fd7b55d3904700b06207c2991c34ad -- Sep 25 06:43:18 hostname systemd-oomd[456]: Swap is currently not detected; memory pressure usage will be degraded Sep 25 06:43:18 hostname systemd[554]: ConfigurationDirectory 'bluetooth' already exists but the mode is different. (File system: 755 ConfigurationDirectoryMode: 555) Sep 25 06:43:19 hostname kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SBRG.HEC.CFSP], AE_NOT_FOUND (20220331/psargs-330) Sep 25 06:43:19 hostname kernel: Sep 25 06:43:19 hostname kernel: No Local Variables are initialized for Method [_FST] Sep 25 06:43:19 hostname kernel: Sep 25 06:43:19 hostname kernel: No Arguments are initialized for method [_FST] Sep 25 06:43:19 hostname kernel: Sep 25 06:43:19 hostname kernel: ACPI Error: Aborting method \_SB.TFN1._FST due to previous error (AE_NOT_FOUND) (20220331/psparse-529) Sep 25 06:43:19 hostname kernel: acpi INT3404:00: Get fan state failed Sep 25 06:43:19 hostname udisksd[610]: failed to load module mdraid: libbd_mdraid.so.2: cannot open shared object file: No such file or directory Sep 25 06:43:19 hostname udisksd[610]: Failed to load the 'mdraid' libblockdev plugin Sep 25 06:43:19 hostname kernel: Dev loop11: unable to read RDB block 8 Sep 25 06:43:19 hostname kernel: loop11: partition table beyond EOD, truncated Sep 25 06:43:20 hostname pipewire[841]: mod.rt: Can't find xdg-portal: (null) Sep 25 06:43:20 hostname pipewire[841]: mod.rt: found session bus but no portal Sep 25 06:43:20 hostname pipewire-pulse[842]: mod.rt: Can't find xdg-portal: (null) Sep 25 06:43:20 hostname pipewire-pulse[842]: mod.rt: found session bus but no portal Sep 25 06:43:20 hostname pipewire-pulse[909]: pw.conf: execvp error 'pactl': No such file or directory Sep 25 06:43:20 hostname pipewire-pulse[842]: mod.rt: RTKit error: org.freedesktop.DBus.Error.AccessDenied Sep 25 06:43:20 hostname pipewire-pulse[842]: mod.rt: could not make thread 910 realtime using RTKit: Permission denied Sep 25 06:43:20 hostname pipewire[841]: mod.rt: RTKit error: org.freedesktop.DBus.Error.AccessDenied Sep 25 06:43:20 hostname pipewire[841]: mod.rt: could not make thread 911 realtime using RTKit: Permission denied Sep 25 06:43:20 hostname gnome-session-binary[872]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed Sep 25 06:43:20 hostname gnome-session-binary[872]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed Sep 25 06:43:20 hostname wireplumber[845]: Failed to set scheduler settings: Operation not permitted Sep 25 06:43:20 hostname systemd[821]: snap.snapd-desktop-integration.snapd-desktop-integration.service: Failed with result 'exit-code'. Sep 25 06:43:21 hostname tracker-miner-f[933]: Unable to get XDG user directory path for special directory &DOCUMENTS. Ignoring this location. Sep 25 06:43:21 hostname tracker-miner-f[933]: Unable to get XDG user directory path for special directory &MUSIC. Ignoring this location. Sep 25 06:43:21 hostname tracker-miner-f[933]: Unable to get XDG user directory path for special directory &PICTURES. Ignoring this location. Sep 25 06:43:21 hostname tracker-miner-f[933]: Unable to get XDG user directory path for special directory &VIDEOS. Ignoring this location. Sep 25 06:43:21 hostname tracker-miner-f[933]: Unable to get XDG user directory path for special directory &DOWNLOAD. Ignoring this location. Sep 25 06:43:21 hostname tracker-miner-f[933]: Unable to get XDG user directory path for special directory &DOCUMENTS. Ignoring this location. Sep 25 06:43:21 hostname tracker-miner-f[933]: Unable to get XDG user directory path for special directory &MUSIC. Ignoring this location. Sep 25 06:43:21 hostname tracker-miner-f[933]: Unable to get XDG user directory path for special directory &PICTURES. Ignoring this location. Sep 25 06:43:21 hostname tracker-miner-f[933]: Unable to get XDG user directory path for special directory &VIDEOS. Ignoring this location. Sep 25 06:43:21 hostname systemd[821]: snap.snapd-desktop-integration.snapd-desktop-integration.service: Failed with result 'exit-code'. Sep 25 06:43:21 hostname systemd[821]: snap.snapd-desktop-integration.snapd-desktop-integration.service: Failed with result 'exit-code'. Sep 25 06:43:21 hostname systemd[821]: snap.snapd-desktop-integration.snapd-desktop-integration.service: Failed with result 'exit-code'. Sep 25 06:43:21 hostname systemd[821]: snap.snapd-desktop-integration.snapd-desktop-integration.service: Failed with result 'exit-code'. Sep 25 06:43:22 hostname systemd[821]: snap.snapd-desktop-integration.snapd-desktop-integration.service: Start request repeated too quickly. Sep 25 06:43:22 hostname systemd[821]: snap.snapd-desktop-integration.snapd-desktop-integration.service: Failed with result 'exit-code'. Sep 25 06:43:22 hostname systemd[821]: Failed to start Service for snap application snapd-desktop-integration.snapd-desktop-integration. Sep 25 06:43:22 hostname /usr/libexec/gdm-wayland-session[867]: dbus-daemon[867]: [session uid=126 pid=867] Activating service name='org.a11y.Bus' requested by ':1.4' (uid=126 pid=921 comm="/usr/bin/gnome-shell" label="unconfined") Sep 25 06:43:22 hostname /usr/libexec/gdm-wayland-session[867]: dbus-daemon[867]: [session uid=126 pid=867] Successfully activated service 'org.a11y.Bus' Sep 25 06:43:24 hostname gnome-session-binary[872]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 11 Sep 25 06:43:24 hostname gnome-session-binary[872]: Unrecoverable failure in required component org.gnome.Shell.desktop Sep 25 06:43:24 hostname /usr/libexec/gdm-wayland-session[867]: dbus-daemon[867]: [session uid=126 pid=867] Activating service name='ca.desrt.dconf' requested by ':1.2' (uid=126 pid=872 comm="/usr/libexec/gnome-session-binary --autostart /usr" label="unconfined") Sep 25 06:43:24 hostname /usr/libexec/gdm-wayland-session[867]: dbus-daemon[867]: [session uid=126 pid=867] Successfully activated service 'ca.desrt.dconf' Sep 25 06:43:24 hostname gdm-launch-environment][801]: GLib-GObject: g_object_unref: assertion 'G_IS_OBJECT (object)' failed Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (--) Log file renamed from "/var/lib/gdm3/.local/share/xorg/Xorg.pid-1164.log" to "/var/lib/gdm3/.local/share/xorg/Xorg.0.log" Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: X.Org X Server 1.21.1.4 Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: X Protocol Version 11, Revision 0 Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: Current Operating System: Linux hostname 5.19.0-15-generic #15-Ubuntu SMP PREEMPT_DYNAMIC Tue Aug 2 07:35:59 UTC 2022 x86_64 Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.19.0-15-generic root=UUID=d49f9deb-0df6-41f5-8c93-deb0765380eb ro quiet splash loglevel=3 vt.handoff=7 Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: xorg-server 2:21.1.4-2ubuntu1 (For technical support please see http://www.ubuntu.com/support) Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: Current version of pixman: 0.40.0 Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: Before reporting problems, check http://wiki.x.org Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: to make sure that you have the latest version. Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: Markers: (--) probed, (**) from config file, (==) default setting, Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (++) from command line, (!!) notice, (II) informational, Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (WW) warning, (EE) error, (NI) not implemented, (??) unknown. Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (==) Log file: "/var/lib/gdm3/.local/share/xorg/Xorg.0.log", Time: Sun Sep 25 06:43:25 2022 Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (==) Using system config directory "/usr/share/X11/xorg.conf.d" Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (==) No Layout section. Using the first Screen section. Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (==) No screen section available. Using defaults. Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (**) |-->Screen "Default Screen Section" (0) Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (**) | |-->Monitor "" Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (==) No monitor specified for screen "Default Screen Section". Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: Using a default monitor configuration. Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (==) Automatically adding devices Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (==) Automatically enabling devices Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (==) Automatically adding GPU devices Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (==) Automatically binding GPU devices Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (==) Max clients allowed: 256, resource mask: 0x1fffff Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist. Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: Entry deleted from font path. Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (WW) The directory "/usr/share/fonts/X11/100dpi/" does not exist. Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: Entry deleted from font path. Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (WW) The directory "/usr/share/fonts/X11/75dpi/" does not exist. Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: Entry deleted from font path. Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (WW) The directory "/usr/share/fonts/X11/100dpi" does not exist. Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: Entry deleted from font path. Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (WW) The directory "/usr/share/fonts/X11/75dpi" does not exist. Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: Entry deleted from font path. Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (==) FontPath set to: Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: /usr/share/fonts/X11/misc, Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: /usr/share/fonts/X11/Type1, Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: built-ins Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (==) ModulePath set to "/usr/lib/xorg/modules" Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) The server relies on udev to provide the list of input devices. Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: If no devices become available, reconfigure udev or disable AutoAddDevices. Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) Loader magic: 0x5597c0abf020 Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) Module ABI versions: Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: X.Org ANSI C Emulation: 0.4 Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: X.Org Video Driver: 25.2 Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: X.Org XInput driver : 24.4 Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: X.Org Server Extension : 10.0 Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (++) using VT number 1 Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) systemd-logind: took control of session /org/freedesktop/login1/session/c2 Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) xfree86: Adding drm device (/dev/dri/card0) Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) Platform probe for /sys/devices/pci0000:00/0000:00:02.0/drm/card0 Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) systemd-logind: got fd for /dev/dri/card0 226:0 fd 14 paused 0 Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (--) PCI:*(0@0:2:0) 8086:3185:0000:0000 rev 3, Mem @ 0xa0000000/16777216, 0x90000000/268435456, I/O @ 0x0000f000/64, BIOS @ 0x????????/131072 Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) LoadModule: "glx" Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) Loading /usr/lib/xorg/modules/extensions/libglx.so Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) Module glx: vendor="X.Org Foundation" Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: compiled for 1.21.1.4, module version = 1.0.0 Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: ABI class: X.Org Server Extension, version 10.0 Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (==) Matched modesetting as autoconfigured driver 0 Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (==) Matched fbdev as autoconfigured driver 1 Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (==) Matched vesa as autoconfigured driver 2 Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (==) Assigned the driver to the xf86ConfigLayout Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) LoadModule: "modesetting" Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) Module modesetting: vendor="X.Org Foundation" Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: compiled for 1.21.1.4, module version = 1.21.1 Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: Module class: X.Org Video Driver Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: ABI class: X.Org Video Driver, version 25.2 Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) LoadModule: "fbdev" Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) Module fbdev: vendor="X.Org Foundation" Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: compiled for 1.21.1.3, module version = 0.5.0 Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: Module class: X.Org Video Driver Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: ABI class: X.Org Video Driver, version 25.2 Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) LoadModule: "vesa" Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) Module vesa: vendor="X.Org Foundation" Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: compiled for 1.21.1.3, module version = 2.5.0 Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: Module class: X.Org Video Driver Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: ABI class: X.Org Video Driver, version 25.2 Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) modesetting: Driver for Modesetting Kernel Drivers: kms Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) FBDEV: driver for framebuffer: fbdev Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) VESA: driver for VESA chipsets: vesa Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: xf86EnableIO: failed to enable I/O ports 0000-03ff (Operation not permitted) Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) modeset(0): using drv /dev/dri/card0 Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (WW) Falling back to old probe method for fbdev Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) Loading sub module "fbdevhw" Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) LoadModule: "fbdevhw" Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) Loading /usr/lib/xorg/modules/libfbdevhw.so Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) Module fbdevhw: vendor="X.Org Foundation" Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: compiled for 1.21.1.4, module version = 0.0.2 Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: ABI class: X.Org Video Driver, version 25.2 Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (EE) open /dev/fb0: Permission denied Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) modeset(0): Creating default Display subsection in Screen section Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: "Default Screen Section" for depth/fbbpp 24/32 Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (==) modeset(0): Depth 24, (==) framebuffer bpp 32 Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (==) modeset(0): RGB weight 888 Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (==) modeset(0): Default visual is TrueColor Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) Loading sub module "glamoregl" Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) LoadModule: "glamoregl" Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) Loading /usr/lib/xorg/modules/libglamoregl.so Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) Module glamoregl: vendor="X.Org Foundation" Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: compiled for 1.21.1.4, module version = 1.0.1 Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: ABI class: X.Org ANSI C Emulation, version 0.4 Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) modeset(0): glamor X acceleration enabled on Mesa Intel(R) UHD Graphics 600 (GLK 2) Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) modeset(0): glamor initialized Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (==) modeset(0): VariableRefresh: disabled Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (==) modeset(0): AsyncFlipSecondaries: disabled Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) modeset(0): Output HDMI-1 has no monitor section Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) modeset(0): Output HDMI-2 has no monitor section Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) modeset(0): EDID for output HDMI-1 Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) modeset(0): Manufacturer: SNY Model: 9d03 Serial#: 16843009 Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) modeset(0): Year: 2015 Week: 1 Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) modeset(0): EDID Version: 1.3 Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) modeset(0): Digital Display Input Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) modeset(0): Max Image Size [cm]: horiz.: 111 vert.: 62 Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) modeset(0): Gamma: 2.20 Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) modeset(0): No DPMS capabilities specified Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) modeset(0): Supported color encodings: RGB 4:4:4 YCrCb 4:4:4 Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) modeset(0): First detailed timing is preferred mode Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) modeset(0): redX: 0.625 redY: 0.340 greenX: 0.280 greenY: 0.595 Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) modeset(0): blueX: 0.155 blueY: 0.070 whiteX: 0.283 whiteY: 0.298 Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) modeset(0): Supported established timings: Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) modeset(0): 640x480@60Hz Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) modeset(0): 800x600@60Hz Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) modeset(0): 1024x768@60Hz Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) modeset(0): Manufacturer's mask: 0 Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) modeset(0): Supported standard timings: Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) modeset(0): #0: hsize: 1280 vsize 1024 refresh: 60 vid: 32897 Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) modeset(0): #1: hsize: 1600 vsize 900 refresh: 60 vid: 49321 Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) modeset(0): #2: hsize: 1152 vsize 864 refresh: 75 vid: 20337 Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) modeset(0): #3: hsize: 1680 vsize 1050 refresh: 60 vid: 179 Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) modeset(0): Supported detailed timing: Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) modeset(0): clock: 148.5 MHz Image Size: 1107 x 623 mm Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) modeset(0): h_active: 1920 h_sync: 2008 h_sync_end 2052 h_blank_end 2200 h_border: 0 Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) modeset(0): v_active: 1080 v_sync: 1084 v_sync_end 1089 v_blanking: 1125 v_border: 0 Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) modeset(0): Supported detailed timing: Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) modeset(0): clock: 74.2 MHz Image Size: 1107 x 623 mm Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) modeset(0): h_active: 1280 h_sync: 1390 h_sync_end 1430 h_blank_end 1650 h_border: 0 Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) modeset(0): v_active: 720 v_sync: 725 v_sync_end 730 v_blanking: 750 v_border: 0 Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) modeset(0): Monitor name: SONY TV *00 Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) modeset(0): Ranges: V min: 48 V max: 62 Hz, H min: 15 H max: 70 kHz, PixClock max 155 MHz Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) modeset(0): Supported detailed timing: Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) modeset(0): clock: 148.5 MHz Image Size: 1107 x 623 mm Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) modeset(0): h_active: 1920 h_sync: 2448 h_sync_end 2492 h_blank_end 2640 h_border: 0 Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) modeset(0): v_active: 1080 v_sync: 1084 v_sync_end 1089 v_blanking: 1125 v_border: 0 Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) modeset(0): Supported detailed timing: Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) modeset(0): clock: 74.2 MHz Image Size: 1107 x 623 mm Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) modeset(0): h_active: 1280 h_sync: 1720 h_sync_end 1760 h_blank_end 1980 h_border: 0 Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) modeset(0): v_active: 720 v_sync: 725 v_sync_end 730 v_blanking: 750 v_border: 0 Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) modeset(0): Number of EDID sections to follow: 1 Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) modeset(0): EDID (in hex): Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) modeset(0): 00ffffffffffff004dd9039d01010101 Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) modeset(0): 01190103806f3e780a0dc9a057479827 Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) modeset(0): 12484c2108008180a9c0714fb3000101 Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) modeset(0): 010101010101023a801871382d40582c Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) modeset(0): 4500536f4200001e011d007251d01e20 Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) modeset(0): 6e285500536f4200001e000000fc0053 Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) modeset(0): 4f4e5920545620202a30300a000000fd Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) modeset(0): 00303e0f460f000a202020202020019a Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) modeset(0): 02034cf4511f10140513042022121603 Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) modeset(0): 07111502060138097f070f7f07150750 Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) modeset(0): 3e1fc04d02005706006754005f540183 Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) modeset(0): 5f000075030c004200b82d2fd00b0100 Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) modeset(0): 007306162636762030e200fb023a80d0 Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) modeset(0): 72382d40102c4580536f4200001e011d Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) modeset(0): 00bc52d01e20b8285540536f4200001e Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) modeset(0): 000000000000000000000000000000ab Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (--) modeset(0): HDMI max TMDS frequency 225000KHz Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) modeset(0): Printing probed modes for output HDMI-1 Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) modeset(0): Modeline "1920x1080"x60.0 148.50 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync (67.5 kHz eP) Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) modeset(0): Modeline "1920x1080"x50.0 148.50 1920 2448 2492 2640 1080 1084 1089 1125 +hsync +vsync (56.2 kHz e) Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) modeset(0): Modeline "1920x1080"x59.9 148.35 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync (67.4 kHz e) Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) modeset(0): Modeline "1920x1080i"x60.0 74.25 1920 2008 2052 2200 1080 1084 1094 1125 interlace +hsync +vsync (33.8 kHz e) Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) modeset(0): Modeline "1920x1080i"x50.0 74.25 1920 2448 2492 2640 1080 1084 1094 1125 interlace +hsync +vsync (28.1 kHz e) Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) modeset(0): Modeline "1920x1080"x30.0 74.25 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync (33.8 kHz e) Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) modeset(0): Modeline "1920x1080"x24.0 74.25 1920 2558 2602 2750 1080 1084 1089 1125 +hsync +vsync (27.0 kHz e) Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) modeset(0): Modeline "1920x1080i"x59.9 74.18 1920 2008 2052 2200 1080 1084 1094 1125 interlace +hsync +vsync (33.7 kHz e) Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) modeset(0): Modeline "1920x1080"x30.0 74.18 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync (33.7 kHz e) Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) modeset(0): Modeline "1920x1080"x24.0 74.18 1920 2558 2602 2750 1080 1084 1089 1125 +hsync +vsync (27.0 kHz e) Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) modeset(0): Modeline "1680x1050"x59.9 119.00 1680 1728 1760 1840 1050 1053 1059 1080 +hsync -vsync (64.7 kHz e) Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) modeset(0): Modeline "1600x900"x60.0 108.00 1600 1624 1704 1800 900 901 904 1000 +hsync +vsync (60.0 kHz e) Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) modeset(0): Modeline "1280x1024"x60.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz e) Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) modeset(0): Modeline "1152x864"x75.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz e) Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) modeset(0): Modeline "1280x720"x60.0 74.25 1280 1390 1430 1650 720 725 730 750 +hsync +vsync (45.0 kHz e) Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) modeset(0): Modeline "1280x720"x50.0 74.25 1280 1720 1760 1980 720 725 730 750 +hsync +vsync (37.5 kHz e) Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) modeset(0): Modeline "1280x720"x59.9 74.18 1280 1390 1430 1650 720 725 730 750 +hsync +vsync (45.0 kHz e) Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) modeset(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e) Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) modeset(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e) Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) modeset(0): Modeline "720x576"x50.0 27.00 720 732 796 864 576 581 586 625 -hsync -vsync (31.2 kHz e) Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) modeset(0): Modeline "720x576i"x50.0 13.50 720 732 795 864 576 580 586 625 interlace -hsync -vsync (15.6 kHz e) Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) modeset(0): Modeline "720x480"x60.0 27.03 720 736 798 858 480 489 495 525 -hsync -vsync (31.5 kHz e) Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) modeset(0): Modeline "720x480"x59.9 27.00 720 736 798 858 480 489 495 525 -hsync -vsync (31.5 kHz e) Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) modeset(0): Modeline "720x480i"x60.0 13.51 720 739 801 858 480 488 494 525 interlace -hsync -vsync (15.8 kHz e) Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) modeset(0): Modeline "720x480i"x59.9 13.50 720 739 801 858 480 488 494 525 interlace -hsync -vsync (15.7 kHz e) Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) modeset(0): Modeline "640x480"x60.0 25.20 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e) Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) modeset(0): Modeline "640x480"x59.9 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e) Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) modeset(0): EDID for output HDMI-2 Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) modeset(0): Output HDMI-1 connected Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) modeset(0): Output HDMI-2 disconnected Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) modeset(0): Using exact sizes for initial modes Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) modeset(0): Output HDMI-1 using initial mode 1920x1080 +0+0 Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (==) modeset(0): Using gamma correction (1.0, 1.0, 1.0) Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (==) modeset(0): DPI set to (96, 96) Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) Loading sub module "fb" Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) LoadModule: "fb" Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) Module "fb" already built-in Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) UnloadModule: "fbdev" Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) Unloading fbdev Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) UnloadSubModule: "fbdevhw" Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) Unloading fbdevhw Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) UnloadModule: "vesa" Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) Unloading vesa Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (==) modeset(0): Backing store enabled Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (==) modeset(0): Silken mouse enabled Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) modeset(0): Initializing kms color map for depth 24, 8 bpc. Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (==) modeset(0): DPMS enabled Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) modeset(0): [DRI2] Setup complete Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) modeset(0): [DRI2] DRI driver: iris Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) modeset(0): [DRI2] VDPAU driver: va_gl Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) Initializing extension Generic Event Extension Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) Initializing extension SHAPE Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) Initializing extension MIT-SHM Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) Initializing extension XInputExtension Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) Initializing extension XTEST Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) Initializing extension BIG-REQUESTS Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) Initializing extension SYNC Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) Initializing extension XKEYBOARD Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) Initializing extension XC-MISC Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) Initializing extension SECURITY Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) Initializing extension XFIXES Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) Initializing extension RENDER Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) Initializing extension RANDR Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) Initializing extension COMPOSITE Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) Initializing extension DAMAGE Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) Initializing extension MIT-SCREEN-SAVER Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) Initializing extension DOUBLE-BUFFER Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) Initializing extension RECORD Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) Initializing extension DPMS Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) Initializing extension Present Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) Initializing extension DRI3 Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) Initializing extension X-Resource Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) Initializing extension XVideo Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) Initializing extension XVideo-MotionCompensation Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) Initializing extension SELinux Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) SELinux: Disabled on system Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) Initializing extension GLX Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) AIGLX: Loaded and initialized iris Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) GLX: Initialized DRI2 GL provider for screen 0 Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) Initializing extension XFree86-VidModeExtension Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) Initializing extension XFree86-DGA Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) Initializing extension XFree86-DRI Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) Initializing extension DRI2 Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) modeset(0): Damage tracking initialized Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) modeset(0): Setting screen physical size to 508 x 285 Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) config/udev: Adding input device Video Bus (/dev/input/event8) Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (**) Video Bus: Applying InputClass "libinput keyboard catchall" Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) LoadModule: "libinput" Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) Loading /usr/lib/xorg/modules/input/libinput_drv.so Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) Module libinput: vendor="X.Org Foundation" Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: compiled for 1.20.14, module version = 1.2.1 Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: Module class: X.Org XInput Driver Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: ABI class: X.Org XInput driver, version 24.1 Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) Using input driver 'libinput' for 'Video Bus' Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) systemd-logind: got fd for /dev/input/event8 13:72 fd 30 paused 0 Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (**) Video Bus: always reports core events Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (**) Option "Device" "/dev/input/event8" Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) event8 - Video Bus: is tagged by udev as: Keyboard Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) event8 - Video Bus: device is a keyboard Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) event8 - Video Bus: device removed Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input9/event8" Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD, id 6) Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (**) Option "xkb_model" "pc105" Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (**) Option "xkb_layout" "us" Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) event8 - Video Bus: is tagged by udev as: Keyboard Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) event8 - Video Bus: device is a keyboard Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) config/udev: Adding input device Power Button (/dev/input/event0) Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (**) Power Button: Applying InputClass "libinput keyboard catchall" Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) Using input driver 'libinput' for 'Power Button' Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) systemd-logind: got fd for /dev/input/event0 13:64 fd 33 paused 0 Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (**) Power Button: always reports core events Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (**) Option "Device" "/dev/input/event0" Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) event0 - Power Button: is tagged by udev as: Keyboard Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) event0 - Power Button: device is a keyboard Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) event0 - Power Button: device removed Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input0/event0" Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 7) Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (**) Option "xkb_model" "pc105" Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (**) Option "xkb_layout" "us" Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) event0 - Power Button: is tagged by udev as: Keyboard Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) event0 - Power Button: device is a keyboard Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) config/udev: Adding input device HDA Intel PCH Mic (/dev/input/event9) Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) No input driver specified, ignoring this device. Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) This device may have been added with another device file. Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) config/udev: Adding input device HDA Intel PCH Front Headphone (/dev/input/event10) Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) No input driver specified, ignoring this device. Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) This device may have been added with another device file. Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) config/udev: Adding input device HDA Intel PCH HDMI/DP,pcm=3 (/dev/input/event11) Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) No input driver specified, ignoring this device. Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) This device may have been added with another device file. Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) config/udev: Adding input device HDA Intel PCH HDMI/DP,pcm=7 (/dev/input/event12) Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) No input driver specified, ignoring this device. Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) This device may have been added with another device file. Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) config/udev: Adding input device HDA Intel PCH HDMI/DP,pcm=8 (/dev/input/event13) Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) No input driver specified, ignoring this device. Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) This device may have been added with another device file. Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) config/udev: Adding input device HDA Intel PCH HDMI/DP,pcm=9 (/dev/input/event14) Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) No input driver specified, ignoring this device. Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) This device may have been added with another device file. Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) config/udev: Adding input device HDA Intel PCH HDMI/DP,pcm=10 (/dev/input/event15) Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) No input driver specified, ignoring this device. Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) This device may have been added with another device file. Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) config/udev: Adding input device Microsoft Microsoft® Nano Transceiver v2.0 (/dev/input/event1) Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (**) Microsoft Microsoft® Nano Transceiver v2.0: Applying InputClass "libinput keyboard catchall" Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) Using input driver 'libinput' for 'Microsoft Microsoft® Nano Transceiver v2.0' Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) systemd-logind: got fd for /dev/input/event1 13:65 fd 34 paused 0 Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (**) Microsoft Microsoft® Nano Transceiver v2.0: always reports core events Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (**) Option "Device" "/dev/input/event1" Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) event1 - Microsoft Microsoft® Nano Transceiver v2.0: is tagged by udev as: Keyboard Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) event1 - Microsoft Microsoft® Nano Transceiver v2.0: device is a keyboard Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) event1 - Microsoft Microsoft® Nano Transceiver v2.0: device removed Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:15.0/usb1/1-6/1-6:1.0/0003:045E:0800.0001/input/input1/event1" Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) XINPUT: Adding extended input device "Microsoft Microsoft® Nano Transceiver v2.0" (type: KEYBOARD, id 8) Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (**) Option "xkb_model" "pc105" Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (**) Option "xkb_layout" "us" Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) event1 - Microsoft Microsoft® Nano Transceiver v2.0: is tagged by udev as: Keyboard Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) event1 - Microsoft Microsoft® Nano Transceiver v2.0: device is a keyboard Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) config/udev: Adding input device Microsoft Microsoft® Nano Transceiver v2.0 Mouse (/dev/input/event2) Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (**) Microsoft Microsoft® Nano Transceiver v2.0 Mouse: Applying InputClass "libinput pointer catchall" Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) Using input driver 'libinput' for 'Microsoft Microsoft® Nano Transceiver v2.0 Mouse' Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) systemd-logind: got fd for /dev/input/event2 13:66 fd 35 paused 0 Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (**) Microsoft Microsoft® Nano Transceiver v2.0 Mouse: always reports core events Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (**) Option "Device" "/dev/input/event2" Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) event2 - Microsoft Microsoft® Nano Transceiver v2.0 Mouse: is tagged by udev as: Mouse Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) event2 - Microsoft Microsoft® Nano Transceiver v2.0 Mouse: device is a pointer Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) event2 - Microsoft Microsoft® Nano Transceiver v2.0 Mouse: device removed Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:15.0/usb1/1-6/1-6:1.1/0003:045E:0800.0002/input/input2/event2" Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) XINPUT: Adding extended input device "Microsoft Microsoft® Nano Transceiver v2.0 Mouse" (type: MOUSE, id 9) Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (**) Option "AccelerationScheme" "none" Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (**) Microsoft Microsoft® Nano Transceiver v2.0 Mouse: (accel) selected scheme none/0 Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (**) Microsoft Microsoft® Nano Transceiver v2.0 Mouse: (accel) acceleration factor: 2.000 Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (**) Microsoft Microsoft® Nano Transceiver v2.0 Mouse: (accel) acceleration threshold: 4 Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) event2 - Microsoft Microsoft® Nano Transceiver v2.0 Mouse: is tagged by udev as: Mouse Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) event2 - Microsoft Microsoft® Nano Transceiver v2.0 Mouse: device is a pointer Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) config/udev: Adding input device Microsoft Microsoft® Nano Transceiver v2.0 Mouse (/dev/input/mouse0) Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) No input driver specified, ignoring this device. Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) This device may have been added with another device file. Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) config/udev: Adding input device Microsoft Microsoft® Nano Transceiver v2.0 Consumer Control (/dev/input/event3) Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (**) Microsoft Microsoft® Nano Transceiver v2.0 Consumer Control: Applying InputClass "libinput keyboard catchall" Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) Using input driver 'libinput' for 'Microsoft Microsoft® Nano Transceiver v2.0 Consumer Control' Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) systemd-logind: got fd for /dev/input/event3 13:67 fd 36 paused 0 Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (**) Microsoft Microsoft® Nano Transceiver v2.0 Consumer Control: always reports core events Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (**) Option "Device" "/dev/input/event3" Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) event3 - Microsoft Microsoft® Nano Transceiver v2.0 Consumer Control: is tagged by udev as: Keyboard Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) event3 - Microsoft Microsoft® Nano Transceiver v2.0 Consumer Control: device is a keyboard Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) event3 - Microsoft Microsoft® Nano Transceiver v2.0 Consumer Control: device removed Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) libinput: Microsoft Microsoft® Nano Transceiver v2.0 Consumer Control: needs a virtual subdevice Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:15.0/usb1/1-6/1-6:1.1/0003:045E:0800.0002/input/input3/event3" Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) XINPUT: Adding extended input device "Microsoft Microsoft® Nano Transceiver v2.0 Consumer Control" (type: MOUSE, id 10) Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (**) Option "AccelerationScheme" "none" Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (**) Microsoft Microsoft® Nano Transceiver v2.0 Consumer Control: (accel) selected scheme none/0 Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (**) Microsoft Microsoft® Nano Transceiver v2.0 Consumer Control: (accel) acceleration factor: 2.000 Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (**) Microsoft Microsoft® Nano Transceiver v2.0 Consumer Control: (accel) acceleration threshold: 4 Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) event3 - Microsoft Microsoft® Nano Transceiver v2.0 Consumer Control: is tagged by udev as: Keyboard Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) event3 - Microsoft Microsoft® Nano Transceiver v2.0 Consumer Control: device is a keyboard Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) config/udev: Adding input device Microsoft Microsoft® Nano Transceiver v2.0 Consumer Control (/dev/input/event4) Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (**) Microsoft Microsoft® Nano Transceiver v2.0 Consumer Control: Applying InputClass "libinput keyboard catchall" Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) Using input driver 'libinput' for 'Microsoft Microsoft® Nano Transceiver v2.0 Consumer Control' Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) systemd-logind: got fd for /dev/input/event4 13:68 fd 37 paused 0 Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (**) Microsoft Microsoft® Nano Transceiver v2.0 Consumer Control: always reports core events Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (**) Option "Device" "/dev/input/event4" Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) event4 - Microsoft Microsoft® Nano Transceiver v2.0 Consumer Control: is tagged by udev as: Keyboard Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) event4 - Microsoft Microsoft® Nano Transceiver v2.0 Consumer Control: device is a keyboard Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) event4 - Microsoft Microsoft® Nano Transceiver v2.0 Consumer Control: device removed Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) libinput: Microsoft Microsoft® Nano Transceiver v2.0 Consumer Control: needs a virtual subdevice Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:15.0/usb1/1-6/1-6:1.2/0003:045E:0800.0003/input/input4/event4" Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) XINPUT: Adding extended input device "Microsoft Microsoft® Nano Transceiver v2.0 Consumer Control" (type: MOUSE, id 11) Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (**) Option "AccelerationScheme" "none" Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (**) Microsoft Microsoft® Nano Transceiver v2.0 Consumer Control: (accel) selected scheme none/0 Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (**) Microsoft Microsoft® Nano Transceiver v2.0 Consumer Control: (accel) acceleration factor: 2.000 Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (**) Microsoft Microsoft® Nano Transceiver v2.0 Consumer Control: (accel) acceleration threshold: 4 Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) event4 - Microsoft Microsoft® Nano Transceiver v2.0 Consumer Control: is tagged by udev as: Keyboard Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) event4 - Microsoft Microsoft® Nano Transceiver v2.0 Consumer Control: device is a keyboard Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) config/udev: Adding input device Microsoft Microsoft® Nano Transceiver v2.0 System Control (/dev/input/event5) Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (**) Microsoft Microsoft® Nano Transceiver v2.0 System Control: Applying InputClass "libinput keyboard catchall" Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) Using input driver 'libinput' for 'Microsoft Microsoft® Nano Transceiver v2.0 System Control' Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) systemd-logind: got fd for /dev/input/event5 13:69 fd 38 paused 0 Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (**) Microsoft Microsoft® Nano Transceiver v2.0 System Control: always reports core events Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (**) Option "Device" "/dev/input/event5" Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) event5 - Microsoft Microsoft® Nano Transceiver v2.0 System Control: is tagged by udev as: Keyboard Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) event5 - Microsoft Microsoft® Nano Transceiver v2.0 System Control: device is a keyboard Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) event5 - Microsoft Microsoft® Nano Transceiver v2.0 System Control: device removed Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:15.0/usb1/1-6/1-6:1.2/0003:045E:0800.0003/input/input6/event5" Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) XINPUT: Adding extended input device "Microsoft Microsoft® Nano Transceiver v2.0 System Control" (type: KEYBOARD, id 12) Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (**) Option "xkb_model" "pc105" Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (**) Option "xkb_layout" "us" Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) event5 - Microsoft Microsoft® Nano Transceiver v2.0 System Control: is tagged by udev as: Keyboard Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) event5 - Microsoft Microsoft® Nano Transceiver v2.0 System Control: device is a keyboard Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) config/udev: Adding input device Intel HID events (/dev/input/event6) Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (**) Intel HID events: Applying InputClass "libinput keyboard catchall" Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) Using input driver 'libinput' for 'Intel HID events' Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) systemd-logind: got fd for /dev/input/event6 13:70 fd 39 paused 0 Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (**) Intel HID events: always reports core events Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (**) Option "Device" "/dev/input/event6" Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) event6 - Intel HID events: is tagged by udev as: Keyboard Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) event6 - Intel HID events: device is a keyboard Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) event6 - Intel HID events: device removed Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (**) Option "config_info" "udev:/sys/devices/platform/INT33D5:00/input/input7/event6" Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) XINPUT: Adding extended input device "Intel HID events" (type: KEYBOARD, id 13) Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (**) Option "xkb_model" "pc105" Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (**) Option "xkb_layout" "us" Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) event6 - Intel HID events: is tagged by udev as: Keyboard Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) event6 - Intel HID events: device is a keyboard Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) config/udev: Adding input device Intel HID 5 button array (/dev/input/event7) Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (**) Intel HID 5 button array: Applying InputClass "libinput keyboard catchall" Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) Using input driver 'libinput' for 'Intel HID 5 button array' Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) systemd-logind: got fd for /dev/input/event7 13:71 fd 40 paused 0 Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (**) Intel HID 5 button array: always reports core events Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (**) Option "Device" "/dev/input/event7" Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) event7 - Intel HID 5 button array: is tagged by udev as: Keyboard Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) event7 - Intel HID 5 button array: device is a keyboard Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) event7 - Intel HID 5 button array: device removed Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (**) Option "config_info" "udev:/sys/devices/platform/INT33D5:00/input/input8/event7" Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) XINPUT: Adding extended input device "Intel HID 5 button array" (type: KEYBOARD, id 14) Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (**) Option "xkb_model" "pc105" Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (**) Option "xkb_layout" "us" Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) event7 - Intel HID 5 button array: is tagged by udev as: Keyboard Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) event7 - Intel HID 5 button array: device is a keyboard Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (**) Microsoft Microsoft® Nano Transceiver v2.0 Consumer Control: Applying InputClass "libinput keyboard catchall" Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) Using input driver 'libinput' for 'Microsoft Microsoft® Nano Transceiver v2.0 Consumer Control' Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) systemd-logind: returning pre-existing fd for /dev/input/event3 13:67 Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (**) Microsoft Microsoft® Nano Transceiver v2.0 Consumer Control: always reports core events Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (**) Option "Device" "/dev/input/event3" Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) libinput: Microsoft Microsoft® Nano Transceiver v2.0 Consumer Control: is a virtual subdevice Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:15.0/usb1/1-6/1-6:1.1/0003:045E:0800.0002/input/input3/event3" Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) XINPUT: Adding extended input device "Microsoft Microsoft® Nano Transceiver v2.0 Consumer Control" (type: KEYBOARD, id 15) Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (**) Option "xkb_model" "pc105" Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (**) Option "xkb_layout" "us" Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (**) Microsoft Microsoft® Nano Transceiver v2.0 Consumer Control: Applying InputClass "libinput keyboard catchall" Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) Using input driver 'libinput' for 'Microsoft Microsoft® Nano Transceiver v2.0 Consumer Control' Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) systemd-logind: returning pre-existing fd for /dev/input/event4 13:68 Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (**) Microsoft Microsoft® Nano Transceiver v2.0 Consumer Control: always reports core events Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (**) Option "Device" "/dev/input/event4" Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) libinput: Microsoft Microsoft® Nano Transceiver v2.0 Consumer Control: is a virtual subdevice Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:15.0/usb1/1-6/1-6:1.2/0003:045E:0800.0003/input/input4/event4" Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (II) XINPUT: Adding extended input device "Microsoft Microsoft® Nano Transceiver v2.0 Consumer Control" (type: KEYBOARD, id 16) Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (**) Option "xkb_model" "pc105" Sep 25 06:43:25 hostname /usr/libexec/gdm-x-session[1164]: (**) Option "xkb_layout" "us" Sep 25 06:43:25 hostname systemd[1]: kerneloops.service: Found left-over process 1187 (kerneloops) in control group while starting unit. Ignoring. Sep 25 06:43:25 hostname systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies. Sep 25 06:43:26 hostname kernel: kauditd_printk_skb: 43 callbacks suppressed Sep 25 06:43:26 hostname /usr/libexec/gdm-x-session[1180]: dbus-daemon[1180]: [session uid=126 pid=1180] Activating service name='org.a11y.Bus' requested by ':1.0' (uid=126 pid=1186 comm="/usr/libexec/gnome-session-check-accelerated" label="unconfined") Sep 25 06:43:26 hostname /usr/libexec/gdm-x-session[1180]: dbus-daemon[1180]: [session uid=126 pid=1180] Successfully activated service 'org.a11y.Bus' Sep 25 06:43:26 hostname gnome-session-binary[1181]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed Sep 25 06:43:26 hostname gnome-session-binary[1181]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed Sep 25 06:43:26 hostname /usr/libexec/gdm-x-session[1164]: (II) modeset(0): EDID vendor "SNY", prod id 40195 Sep 25 06:43:26 hostname /usr/libexec/gdm-x-session[1164]: (II) modeset(0): Using EDID range info for horizontal sync Sep 25 06:43:26 hostname /usr/libexec/gdm-x-session[1164]: (II) modeset(0): Using EDID range info for vertical refresh Sep 25 06:43:26 hostname /usr/libexec/gdm-x-session[1164]: (II) modeset(0): Printing DDC gathered Modelines: Sep 25 06:43:26 hostname /usr/libexec/gdm-x-session[1164]: (II) modeset(0): Modeline "1920x1080"x0.0 148.50 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync (67.5 kHz eP) Sep 25 06:43:26 hostname /usr/libexec/gdm-x-session[1164]: (II) modeset(0): Modeline "1280x720"x0.0 74.25 1280 1390 1430 1650 720 725 730 750 +hsync +vsync (45.0 kHz e) Sep 25 06:43:26 hostname /usr/libexec/gdm-x-session[1164]: (II) modeset(0): Modeline "1920x1080"x0.0 148.50 1920 2448 2492 2640 1080 1084 1089 1125 +hsync +vsync (56.2 kHz e) Sep 25 06:43:26 hostname /usr/libexec/gdm-x-session[1164]: (II) modeset(0): Modeline "1280x720"x0.0 74.25 1280 1720 1760 1980 720 725 730 750 +hsync +vsync (37.5 kHz e) Sep 25 06:43:26 hostname /usr/libexec/gdm-x-session[1164]: (II) modeset(0): Modeline "1920x1080i"x0.0 74.25 1920 2448 2492 2640 1080 1084 1094 1125 interlace +hsync +vsync (28.1 kHz e) Sep 25 06:43:26 hostname /usr/libexec/gdm-x-session[1164]: (II) modeset(0): Modeline "1920x1080i"x0.0 74.25 1920 2008 2052 2200 1080 1084 1094 1125 interlace +hsync +vsync (33.8 kHz e) Sep 25 06:43:26 hostname /usr/libexec/gdm-x-session[1164]: (II) modeset(0): Modeline "1920x1080"x0.0 74.25 1920 2558 2602 2750 1080 1084 1089 1125 +hsync +vsync (27.0 kHz e) Sep 25 06:43:26 hostname /usr/libexec/gdm-x-session[1164]: (II) modeset(0): Modeline "1920x1080"x0.0 74.25 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync (33.8 kHz e) Sep 25 06:43:26 hostname /usr/libexec/gdm-x-session[1164]: (II) modeset(0): Modeline "720x576"x0.0 27.00 720 732 796 864 576 581 586 625 -hsync -vsync (31.2 kHz e) Sep 25 06:43:26 hostname /usr/libexec/gdm-x-session[1164]: (II) modeset(0): Modeline "1440x576i"x0.0 27.00 1440 1464 1590 1728 576 580 586 625 interlace -hsync -vsync (15.6 kHz e) Sep 25 06:43:26 hostname /usr/libexec/gdm-x-session[1164]: (II) modeset(0): Modeline "720x480"x0.0 27.00 720 736 798 858 480 489 495 525 -hsync -vsync (31.5 kHz e) Sep 25 06:43:26 hostname /usr/libexec/gdm-x-session[1164]: (II) modeset(0): Modeline "1440x480i"x0.0 27.00 1440 1478 1602 1716 480 488 494 525 interlace -hsync -vsync (15.7 kHz e) Sep 25 06:43:26 hostname /usr/libexec/gdm-x-session[1164]: (II) modeset(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e) Sep 25 06:43:26 hostname /usr/libexec/gdm-x-session[1164]: (II) modeset(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e) Sep 25 06:43:26 hostname /usr/libexec/gdm-x-session[1164]: (II) modeset(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e) Sep 25 06:43:26 hostname /usr/libexec/gdm-x-session[1164]: (II) modeset(0): Modeline "1280x1024"x0.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz e) Sep 25 06:43:26 hostname /usr/libexec/gdm-x-session[1164]: (II) modeset(0): Modeline "1600x900"x60.0 119.00 1600 1696 1864 2128 900 901 904 932 -hsync +vsync (55.9 kHz e) Sep 25 06:43:26 hostname /usr/libexec/gdm-x-session[1164]: (II) modeset(0): Modeline "1152x864"x0.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz e) Sep 25 06:43:26 hostname /usr/libexec/gdm-x-session[1164]: (II) modeset(0): Modeline "1680x1050"x0.0 119.00 1680 1728 1760 1840 1050 1053 1059 1080 +hsync -vsync (64.7 kHz e) Sep 25 06:43:26 hostname /usr/libexec/gdm-x-session[1164]: (--) modeset(0): HDMI max TMDS frequency 225000KHz Sep 25 06:43:27 hostname gnome-shell[1224]: ATK Bridge is disabled but a11y has already been enabled. Sep 25 06:43:28 hostname /usr/libexec/gdm-x-session[1180]: dbus-daemon[1180]: [session uid=126 pid=1180] Activating service name='org.freedesktop.impl.portal.PermissionStore' requested by ':1.5' (uid=126 pid=1224 comm="/usr/bin/gnome-shell" label="unconfined") Sep 25 06:43:28 hostname /usr/libexec/gdm-x-session[1180]: dbus-daemon[1180]: [session uid=126 pid=1180] Successfully activated service 'org.freedesktop.impl.portal.PermissionStore' Sep 25 06:43:28 hostname /usr/libexec/gdm-x-session[1180]: dbus-daemon[1180]: [session uid=126 pid=1180] Activating service name='org.gnome.Shell.Notifications' requested by ':1.5' (uid=126 pid=1224 comm="/usr/bin/gnome-shell" label="unconfined") Sep 25 06:43:28 hostname geoclue[1258]: No feature manager for feature of type 'GProxyResolver' Sep 25 06:43:28 hostname geoclue[1258]: No feature manager for feature of type 'GProxyResolver' Sep 25 06:43:28 hostname /usr/libexec/gdm-x-session[1208]: dbus-daemon[1208]: Activating service name='org.a11y.atspi.Registry' requested by ':1.1' (uid=126 pid=1224 comm="/usr/bin/gnome-shell" label="unconfined") Sep 25 06:43:28 hostname /usr/libexec/gdm-x-session[1208]: dbus-daemon[1208]: Successfully activated service 'org.a11y.atspi.Registry' Sep 25 06:43:28 hostname /usr/libexec/gdm-x-session[1180]: dbus-daemon[1180]: [session uid=126 pid=1180] Successfully activated service 'org.gnome.Shell.Notifications' Sep 25 06:43:28 hostname /usr/libexec/gdm-x-session[1180]: dbus-daemon[1180]: [session uid=126 pid=1180] Activating service name='org.gtk.vfs.Daemon' requested by ':1.12' (uid=126 pid=1300 comm="ibus-daemon --panel disable --xim" label="unconfined") Sep 25 06:43:28 hostname /usr/libexec/gdm-x-session[1180]: dbus-daemon[1180]: [session uid=126 pid=1180] Successfully activated service 'org.gtk.vfs.Daemon' Sep 25 06:43:28 hostname /usr/libexec/gdm-x-session[1180]: dbus-daemon[1180]: [session uid=126 pid=1180] Activating service name='org.freedesktop.systemd1' requested by ':1.9' (uid=126 pid=1284 comm="/usr/libexec/gsd-sharing" label="unconfined") Sep 25 06:43:28 hostname /usr/libexec/gdm-x-session[1180]: dbus-daemon[1180]: [session uid=126 pid=1180] Activating service name='org.freedesktop.portal.IBus' requested by ':1.12' (uid=126 pid=1300 comm="ibus-daemon --panel disable --xim" label="unconfined") Sep 25 06:43:28 hostname /usr/libexec/gdm-x-session[1180]: dbus-daemon[1180]: [session uid=126 pid=1180] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1 Sep 25 06:43:28 hostname gsd-sharing[1284]: Failed to StopUnit service: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.freedesktop.systemd1 exited with status 1 Sep 25 06:43:28 hostname gsd-sharing[1284]: Failed to StopUnit service: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.freedesktop.systemd1 exited with status 1 Sep 25 06:43:28 hostname /usr/libexec/gdm-x-session[1180]: dbus-daemon[1180]: [session uid=126 pid=1180] Successfully activated service 'org.freedesktop.portal.IBus' Sep 25 06:43:29 hostname /usr/libexec/gdm-x-session[1180]: dbus-daemon[1180]: [session uid=126 pid=1180] Activating service name='org.gnome.ScreenSaver' requested by ':1.25' (uid=126 pid=1331 comm="/usr/libexec/gsd-power" label="unconfined") Sep 25 06:43:29 hostname gsd-media-keys[1310]: Failed to grab accelerator for keybinding settings:playback-repeat Sep 25 06:43:29 hostname gsd-media-keys[1310]: Failed to grab accelerator for keybinding settings:rotate-video-lock Sep 25 06:43:29 hostname gsd-media-keys[1310]: Failed to grab accelerator for keybinding settings:playback-random Sep 25 06:43:29 hostname gsd-media-keys[1310]: Failed to grab accelerator for keybinding settings:hibernate Sep 25 06:43:29 hostname /usr/libexec/gdm-x-session[1180]: dbus-daemon[1180]: [session uid=126 pid=1180] Successfully activated service 'org.gnome.ScreenSaver' Sep 25 06:43:30 hostname gnome-shell[1224]: JS ERROR: Gio.IOErrorEnum: GDBus.Error:net.reactivated.Fprint.Error.NoSuchDevice: No devices available asyncCallback@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:114:23