=== start test Sun Jul 25 09:56:56 PM PDT 2021 === Jul 25 21:56:59 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): EDID vendor "NEC", prod id 26342 Jul 25 21:56:59 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Using hsync ranges from config file Jul 25 21:56:59 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Using vrefresh ranges from config file Jul 25 21:56:59 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Printing DDC gathered Modelines: Jul 25 21:56:59 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Modeline "1920x1200"x0.0 154.00 1920 1968 2000 2080 1200 1203 1209 1235 +hsync -vsync (74.0 kHz eP) Jul 25 21:56:59 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Modeline "1680x1050"x0.0 146.25 1680 1784 1960 2240 1050 1053 1059 1089 -hsync +vsync (65.3 kHz e) Jul 25 21:56:59 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Modeline "720x480"x0.0 27.00 720 736 798 858 480 489 495 525 -hsync -vsync (31.5 kHz e) Jul 25 21:56:59 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Modeline "720x576"x0.0 27.00 720 732 796 864 576 581 586 625 -hsync -vsync (31.2 kHz e) Jul 25 21:56:59 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Modeline "1280x720"x0.0 74.25 1280 1390 1430 1650 720 725 730 750 +hsync +vsync (45.0 kHz e) Jul 25 21:56:59 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Modeline "1280x720"x0.0 74.25 1280 1720 1760 1980 720 725 730 750 +hsync +vsync (37.5 kHz e) Jul 25 21:56:59 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Modeline "1920x1080"x0.0 148.50 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync (67.5 kHz e) Jul 25 21:56:59 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Modeline "1920x1080"x0.0 148.50 1920 2448 2492 2640 1080 1084 1089 1125 +hsync +vsync (56.2 kHz e) Jul 25 21:56:59 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Modeline "1920x1080i"x0.0 74.25 1920 2008 2052 2200 1080 1084 1094 1125 interlace +hsync +vsync (33.8 kHz e) Jul 25 21:56:59 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Modeline "1920x1080i"x0.0 74.25 1920 2448 2492 2640 1080 1084 1094 1125 interlace +hsync +vsync (28.1 kHz e) Jul 25 21:56:59 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Modeline "1920x1080"x0.0 74.25 1920 2558 2602 2750 1080 1084 1089 1125 +hsync +vsync (27.0 kHz e) Jul 25 21:56:59 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e) Jul 25 21:56:59 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Modeline "800x600"x0.0 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz e) Jul 25 21:56:59 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e) Jul 25 21:56:59 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Modeline "640x480"x0.0 31.50 640 664 704 832 480 489 492 520 -hsync -vsync (37.9 kHz e) Jul 25 21:56:59 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Modeline "640x480"x0.0 30.24 640 704 768 864 480 483 486 525 -hsync -vsync (35.0 kHz e) Jul 25 21:56:59 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e) Jul 25 21:56:59 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Modeline "720x400"x0.0 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e) Jul 25 21:56:59 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Modeline "1280x1024"x0.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz e) Jul 25 21:56:59 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Modeline "1024x768"x0.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz e) Jul 25 21:56:59 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Modeline "1024x768"x0.0 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync (56.5 kHz e) Jul 25 21:56:59 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e) Jul 25 21:56:59 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Modeline "832x624"x0.0 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz e) Jul 25 21:56:59 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Modeline "800x600"x0.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e) Jul 25 21:56:59 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Modeline "800x600"x0.0 50.00 800 856 976 1040 600 637 643 666 +hsync +vsync (48.1 kHz e) Jul 25 21:56:59 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Modeline "1152x864"x0.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz e) Jul 25 21:56:59 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Modeline "1280x1024"x0.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz e) Jul 25 21:56:59 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Modeline "1400x1050"x0.0 101.00 1400 1448 1480 1560 1050 1053 1057 1080 +hsync -vsync (64.7 kHz e) Jul 25 21:56:59 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Modeline "1366x768"x59.8 84.75 1366 1431 1567 1776 768 771 781 798 -hsync +vsync (47.7 kHz e) Jul 25 21:56:59 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Modeline "1440x900"x0.0 88.75 1440 1488 1520 1600 900 903 909 926 +hsync -vsync (55.5 kHz e) Jul 25 21:56:59 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Modeline "1600x1200"x0.0 162.00 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync (75.0 kHz e) Jul 25 21:56:59 lxjima gsd-media-keys[2267]: Failed to grab accelerators: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface “org.gnome.Shell” on object at path /org/gnome/Shell Jul 25 21:56:59 lxjima gnome-shell[1989]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise:#012 _checkGC@/usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com/iconCache.js:110:1#012 add@/usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com/iconCache.js:62:14#012 _cacheOrCreateIconByName@/usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com/appIndicator.js:452:37#012 async*_updateIconByType@/usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com/appIndicator.js:702:36#012 _updateIcon@/usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com/appIndicator.js:731:14#012 _invalidateIcon@/usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com/appIndicator.js:755:14#012 _init@/usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com/appIndicator.js:407:18#012 _init@/usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com/indicatorStatusIcon.js:44:25#012 _registerItem@/usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com/statusNotifierWatcher.js:102:32#012 async*_ensureItemRegistered@/usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com/statusNotifierWatcher.js:127:14#012 RegisterStatusNotifierItemAsync@/usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com/statusNotifierWatcher.js:185:14#012 _handleMethodCall@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:354:35#012 _wrapJSObject/<@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:387:34 Jul 25 21:56:59 lxjima gnome-shell[1989]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Jul 25 21:56:59 lxjima gnome-shell[1989]: == Stack trace for context 0x564cceda7190 == Jul 25 21:56:59 lxjima gnome-shell[1989]: message repeated 5 times: [ == Stack trace for context 0x564cceda7190 ==] Jul 25 21:56:59 lxjima gnome-shell[1989]: The offending signal was destroy on Gjs_ui_appDisplay_FolderGrid 0x564cd1bf3000. Jul 25 21:56:59 lxjima gnome-shell[1989]: == Stack trace for context 0x564cceda7190 == Jul 25 21:56:59 lxjima gnome-shell[1989]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Jul 25 21:56:59 lxjima gnome-shell[1989]: == Stack trace for context 0x564cceda7190 == Jul 25 21:56:59 lxjima gnome-shell[1989]: message repeated 4 times: [ == Stack trace for context 0x564cceda7190 ==] Jul 25 21:56:59 lxjima gnome-shell[1989]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564cd1c66940. Jul 25 21:56:59 lxjima gnome-shell[1989]: == Stack trace for context 0x564cceda7190 == Jul 25 21:56:59 lxjima gnome-shell[1989]: message repeated 5 times: [ == Stack trace for context 0x564cceda7190 ==] Jul 25 21:56:59 lxjima gnome-shell[1989]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Jul 25 21:56:59 lxjima gnome-shell[1989]: == Stack trace for context 0x564cceda7190 == Jul 25 21:56:59 lxjima gnome-shell[1989]: message repeated 8 times: [ == Stack trace for context 0x564cceda7190 ==] Jul 25 21:56:59 lxjima gnome-shell[1989]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564cd1c66940. Jul 25 21:56:59 lxjima gnome-shell[1989]: == Stack trace for context 0x564cceda7190 == Jul 25 21:56:59 lxjima gnome-shell[1989]: message repeated 10 times: [ == Stack trace for context 0x564cceda7190 ==] Jul 25 21:56:59 lxjima gnome-shell[1989]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Jul 25 21:56:59 lxjima gnome-shell[1989]: == Stack trace for context 0x564cceda7190 == Jul 25 21:56:59 lxjima gnome-shell[1989]: message repeated 13 times: [ == Stack trace for context 0x564cceda7190 ==] Jul 25 21:56:59 lxjima gnome-shell[1989]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564cd1c66940. Jul 25 21:56:59 lxjima gnome-shell[1989]: == Stack trace for context 0x564cceda7190 == Jul 25 21:56:59 lxjima gnome-shell[1989]: message repeated 11 times: [ == Stack trace for context 0x564cceda7190 ==] Jul 25 21:56:59 lxjima gnome-shell[1989]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Jul 25 21:56:59 lxjima gnome-shell[1989]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564cd1c33120. Jul 25 21:56:59 lxjima gnome-shell[1989]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Jul 25 21:56:59 lxjima gnome-shell[1989]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x564cd1bf3000. Jul 25 21:56:59 lxjima gnome-shell[1989]: 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. Jul 25 21:56:59 lxjima gnome-shell[1989]: The offending callback was set_container(), a vfunc. Jul 25 21:56:59 lxjima gnome-shell[1989]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Jul 25 21:56:59 lxjima gnome-shell[1989]: The offending signal was destroy on Gjs_ui_appDisplay_FolderGrid 0x564cd1e00270. Jul 25 21:56:59 lxjima gnome-shell[1989]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Jul 25 21:56:59 lxjima gnome-shell[1989]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564cd1c4e5e0. Jul 25 21:56:59 lxjima gnome-shell[1989]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Jul 25 21:56:59 lxjima gnome-shell[1989]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564cd1c4e5e0. Jul 25 21:56:59 lxjima gnome-shell[1989]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Jul 25 21:56:59 lxjima gnome-shell[1989]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564cd1c4e5e0. Jul 25 21:56:59 lxjima gnome-shell[1989]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Jul 25 21:56:59 lxjima gnome-shell[1989]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564cd1dfd9e0. Jul 25 21:56:59 lxjima gnome-shell[1989]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Jul 25 21:56:59 lxjima gnome-shell[1989]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x564cd1e00270. Jul 25 21:56:59 lxjima gnome-shell[1989]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Jul 25 21:56:59 lxjima gnome-shell[1989]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564cd1c6c590. Jul 25 21:56:59 lxjima gnome-shell[1989]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Jul 25 21:56:59 lxjima gnome-shell[1989]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564cd1c6c590. Jul 25 21:56:59 lxjima gnome-shell[1989]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Jul 25 21:56:59 lxjima gnome-shell[1989]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564cd1c6c590. Jul 25 21:56:59 lxjima gnome-shell[1989]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Jul 25 21:56:59 lxjima gnome-shell[1989]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564cd0a7e4d0. Jul 25 21:56:59 lxjima gnome-shell[1989]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Jul 25 21:56:59 lxjima gnome-shell[1989]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x564cd1e00270. Jul 25 21:56:59 lxjima gnome-shell[1989]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Jul 25 21:56:59 lxjima gnome-shell[1989]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564cd1cc5280. Jul 25 21:56:59 lxjima gnome-shell[1989]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Jul 25 21:56:59 lxjima gnome-shell[1989]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564cd1cc5280. Jul 25 21:56:59 lxjima gnome-shell[1989]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Jul 25 21:56:59 lxjima gnome-shell[1989]: == Stack trace for context 0x564cceda7190 == Jul 25 21:56:59 lxjima gnome-shell[1989]: message repeated 3 times: [ == Stack trace for context 0x564cceda7190 ==] Jul 25 21:56:59 lxjima gnome-shell[1989]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564cd1cc5280. Jul 25 21:56:59 lxjima gnome-shell[1989]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Jul 25 21:56:59 lxjima gnome-shell[1989]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564cd0a77f70. Jul 25 21:56:59 lxjima gnome-shell[1989]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Jul 25 21:56:59 lxjima gnome-shell[1989]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x564cd1e00270. Jul 25 21:56:59 lxjima gnome-shell[1989]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Jul 25 21:56:59 lxjima gnome-shell[1989]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564cd1cd5380. Jul 25 21:56:59 lxjima gnome-shell[1989]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Jul 25 21:56:59 lxjima gnome-shell[1989]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564cd1cd5380. Jul 25 21:56:59 lxjima gnome-shell[1989]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Jul 25 21:56:59 lxjima gnome-shell[1989]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564cd1cd5380. Jul 25 21:56:59 lxjima gnome-shell[1989]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Jul 25 21:56:59 lxjima gnome-shell[1989]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564cd007f580. Jul 25 21:56:59 lxjima gnome-shell[1989]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Jul 25 21:56:59 lxjima gnome-shell[1989]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x564cd1e00270. Jul 25 21:56:59 lxjima gnome-shell[1989]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Jul 25 21:56:59 lxjima gnome-shell[1989]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564ccf8aaaa0. Jul 25 21:56:59 lxjima gnome-shell[1989]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Jul 25 21:56:59 lxjima gnome-shell[1989]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564ccf8aaaa0. Jul 25 21:56:59 lxjima gnome-shell[1989]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Jul 25 21:56:59 lxjima gnome-shell[1989]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564ccf8aaaa0. Jul 25 21:56:59 lxjima gnome-shell[1989]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Jul 25 21:56:59 lxjima gnome-shell[1989]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564cd24acdc0. Jul 25 21:56:59 lxjima gnome-shell[1989]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Jul 25 21:56:59 lxjima gnome-shell[1989]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x564cd1e00270. Jul 25 21:56:59 lxjima gnome-shell[1989]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Jul 25 21:56:59 lxjima gnome-shell[1989]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564cd1bb1190. Jul 25 21:56:59 lxjima gnome-shell[1989]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Jul 25 21:56:59 lxjima gnome-shell[1989]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564cd1bb1190. Jul 25 21:56:59 lxjima gnome-shell[1989]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Jul 25 21:56:59 lxjima gnome-shell[1989]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564cd1bb1190. Jul 25 21:56:59 lxjima gnome-shell[1989]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Jul 25 21:56:59 lxjima gnome-shell[1989]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564cd1cd4970. Jul 25 21:56:59 lxjima gnome-shell[1989]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Jul 25 21:56:59 lxjima gnome-shell[1989]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x564cd1e00270. Jul 25 21:56:59 lxjima gnome-shell[1989]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Jul 25 21:56:59 lxjima gnome-shell[1989]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564cd1c55ba0. Jul 25 21:56:59 lxjima gnome-shell[1989]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Jul 25 21:56:59 lxjima gnome-shell[1989]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564cd1c55ba0. Jul 25 21:56:59 lxjima gnome-shell[1989]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Jul 25 21:56:59 lxjima gnome-shell[1989]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564cd1c55ba0. Jul 25 21:56:59 lxjima gnome-shell[1989]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Jul 25 21:56:59 lxjima gnome-shell[1989]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564ccf6fd080. Jul 25 21:56:59 lxjima gnome-shell[1989]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Jul 25 21:56:59 lxjima gnome-shell[1989]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x564cd1e00270. Jul 25 21:56:59 lxjima gnome-shell[1989]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Jul 25 21:56:59 lxjima gnome-shell[1989]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564cd25d4760. Jul 25 21:56:59 lxjima gnome-shell[1989]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Jul 25 21:56:59 lxjima gnome-shell[1989]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564cd25d4760. Jul 25 21:56:59 lxjima gnome-shell[1989]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Jul 25 21:56:59 lxjima gnome-shell[1989]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564cd25d4760. Jul 25 21:56:59 lxjima gnome-shell[1989]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Jul 25 21:56:59 lxjima gnome-shell[1989]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564cd0bbe1f0. Jul 25 21:56:59 lxjima gnome-shell[1989]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Jul 25 21:56:59 lxjima gnome-shell[1989]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x564cd1e00270. Jul 25 21:56:59 lxjima gnome-shell[1989]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Jul 25 21:56:59 lxjima gnome-shell[1989]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564cd0e4a110. Jul 25 21:56:59 lxjima gnome-shell[1989]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Jul 25 21:56:59 lxjima gnome-shell[1989]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564cd0e4a110. Jul 25 21:56:59 lxjima gnome-shell[1989]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Jul 25 21:56:59 lxjima gnome-shell[1989]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564cd0e4a110. Jul 25 21:56:59 lxjima gnome-shell[1989]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Jul 25 21:56:59 lxjima gnome-shell[1989]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564cd1e31d60. Jul 25 21:56:59 lxjima gnome-shell[1989]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Jul 25 21:56:59 lxjima gnome-shell[1989]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x564cd1e00270. Jul 25 21:56:59 lxjima gnome-shell[1989]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Jul 25 21:56:59 lxjima gnome-shell[1989]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564ccfbfb390. Jul 25 21:56:59 lxjima gnome-shell[1989]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Jul 25 21:56:59 lxjima gnome-shell[1989]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564ccfbfb390. Jul 25 21:56:59 lxjima gnome-shell[1989]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Jul 25 21:56:59 lxjima gnome-shell[1989]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564ccfbfb390. Jul 25 21:56:59 lxjima gnome-shell[1989]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Jul 25 21:56:59 lxjima gnome-shell[1989]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564cd233cf80. Jul 25 21:56:59 lxjima gnome-shell[1989]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Jul 25 21:56:59 lxjima gnome-shell[1989]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x564cd1e00270. Jul 25 21:56:59 lxjima gnome-shell[1989]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Jul 25 21:56:59 lxjima gnome-shell[1989]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564cd1c3c760. Jul 25 21:56:59 lxjima gnome-shell[1989]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Jul 25 21:56:59 lxjima gnome-shell[1989]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564cd1c3c760. Jul 25 21:56:59 lxjima gnome-shell[1989]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Jul 25 21:56:59 lxjima gnome-shell[1989]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564cd1c3c760. Jul 25 21:56:59 lxjima gnome-shell[1989]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Jul 25 21:56:59 lxjima gnome-shell[1989]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564cd0373870. Jul 25 21:56:59 lxjima gnome-shell[1989]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Jul 25 21:56:59 lxjima gnome-shell[1989]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x564cd1e00270. Jul 25 21:56:59 lxjima gnome-shell[1989]: 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. Jul 25 21:56:59 lxjima gnome-shell[1989]: The offending callback was set_container(), a vfunc. Jul 25 21:56:59 lxjima gnome-shell[1989]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Jul 25 21:56:59 lxjima gnome-shell[1989]: The offending signal was notify on NMDeviceEthernet 0x564cd1df0350. Jul 25 21:56:59 lxjima gnome-shell[1989]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Jul 25 21:56:59 lxjima gnome-shell[1989]: The offending signal was notify on NMDeviceWifi 0x564cd1df42c0. Jul 25 21:56:59 lxjima gnome-shell[1989]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Jul 25 21:56:59 lxjima gnome-shell[1989]: The offending signal was state-changed on NMDeviceEthernet 0x564cd1df0350. Jul 25 21:56:59 lxjima gnome-shell[1989]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Jul 25 21:56:59 lxjima gnome-shell[1989]: The offending signal was state-changed on NMDeviceWifi 0x564cd1df42c0. Jul 25 21:56:59 lxjima systemd[1695]: org.gnome.Shell@x11.service: Succeeded. Jul 25 21:56:59 lxjima systemd[1695]: org.gnome.Shell@x11.service: Scheduled restart job, restart counter is at 1. Jul 25 21:56:59 lxjima systemd[1695]: Stopped GNOME Shell on X11. Jul 25 21:56:59 lxjima systemd[1695]: Starting GNOME Shell on X11... Jul 25 21:56:59 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): EDID vendor "NEC", prod id 26342 Jul 25 21:56:59 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Using hsync ranges from config file Jul 25 21:56:59 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Using vrefresh ranges from config file Jul 25 21:56:59 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Printing DDC gathered Modelines: Jul 25 21:56:59 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Modeline "1920x1200"x0.0 154.00 1920 1968 2000 2080 1200 1203 1209 1235 +hsync -vsync (74.0 kHz eP) Jul 25 21:56:59 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Modeline "1680x1050"x0.0 146.25 1680 1784 1960 2240 1050 1053 1059 1089 -hsync +vsync (65.3 kHz e) Jul 25 21:56:59 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Modeline "720x480"x0.0 27.00 720 736 798 858 480 489 495 525 -hsync -vsync (31.5 kHz e) Jul 25 21:56:59 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Modeline "720x576"x0.0 27.00 720 732 796 864 576 581 586 625 -hsync -vsync (31.2 kHz e) Jul 25 21:56:59 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Modeline "1280x720"x0.0 74.25 1280 1390 1430 1650 720 725 730 750 +hsync +vsync (45.0 kHz e) Jul 25 21:56:59 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Modeline "1280x720"x0.0 74.25 1280 1720 1760 1980 720 725 730 750 +hsync +vsync (37.5 kHz e) Jul 25 21:56:59 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Modeline "1920x1080"x0.0 148.50 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync (67.5 kHz e) Jul 25 21:56:59 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Modeline "1920x1080"x0.0 148.50 1920 2448 2492 2640 1080 1084 1089 1125 +hsync +vsync (56.2 kHz e) Jul 25 21:56:59 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Modeline "1920x1080i"x0.0 74.25 1920 2008 2052 2200 1080 1084 1094 1125 interlace +hsync +vsync (33.8 kHz e) Jul 25 21:56:59 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Modeline "1920x1080i"x0.0 74.25 1920 2448 2492 2640 1080 1084 1094 1125 interlace +hsync +vsync (28.1 kHz e) Jul 25 21:56:59 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Modeline "1920x1080"x0.0 74.25 1920 2558 2602 2750 1080 1084 1089 1125 +hsync +vsync (27.0 kHz e) Jul 25 21:56:59 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e) Jul 25 21:56:59 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Modeline "800x600"x0.0 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz e) Jul 25 21:56:59 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e) Jul 25 21:56:59 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Modeline "640x480"x0.0 31.50 640 664 704 832 480 489 492 520 -hsync -vsync (37.9 kHz e) Jul 25 21:56:59 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Modeline "640x480"x0.0 30.24 640 704 768 864 480 483 486 525 -hsync -vsync (35.0 kHz e) Jul 25 21:56:59 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e) Jul 25 21:56:59 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Modeline "720x400"x0.0 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e) Jul 25 21:56:59 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Modeline "1280x1024"x0.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz e) Jul 25 21:56:59 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Modeline "1024x768"x0.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz e) Jul 25 21:56:59 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Modeline "1024x768"x0.0 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync (56.5 kHz e) Jul 25 21:56:59 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e) Jul 25 21:56:59 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Modeline "832x624"x0.0 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz e) Jul 25 21:56:59 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Modeline "800x600"x0.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e) Jul 25 21:56:59 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Modeline "800x600"x0.0 50.00 800 856 976 1040 600 637 643 666 +hsync +vsync (48.1 kHz e) Jul 25 21:56:59 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Modeline "1152x864"x0.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz e) Jul 25 21:56:59 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Modeline "1280x1024"x0.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz e) Jul 25 21:56:59 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Modeline "1400x1050"x0.0 101.00 1400 1448 1480 1560 1050 1053 1057 1080 +hsync -vsync (64.7 kHz e) Jul 25 21:56:59 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Modeline "1366x768"x59.8 84.75 1366 1431 1567 1776 768 771 781 798 -hsync +vsync (47.7 kHz e) Jul 25 21:56:59 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Modeline "1440x900"x0.0 88.75 1440 1488 1520 1600 900 903 909 926 +hsync -vsync (55.5 kHz e) Jul 25 21:56:59 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Modeline "1600x1200"x0.0 162.00 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync (75.0 kHz e) Jul 25 21:56:59 lxjima gnome-shell[3531]: org.gnome.Shell already exists on bus and --replace not specified Jul 25 21:56:59 lxjima systemd[1695]: org.gnome.Shell@x11.service: Failed with result 'protocol'. Jul 25 21:56:59 lxjima systemd[1695]: Failed to start GNOME Shell on X11. Jul 25 21:56:59 lxjima systemd[1695]: org.gnome.Shell@x11.service: Scheduled restart job, restart counter is at 2. Jul 25 21:56:59 lxjima systemd[1695]: Stopped GNOME Shell on X11. Jul 25 21:56:59 lxjima systemd[1695]: Starting GNOME Shell on X11... Jul 25 21:56:59 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): EDID vendor "NEC", prod id 26342 Jul 25 21:56:59 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Using hsync ranges from config file Jul 25 21:56:59 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Using vrefresh ranges from config file Jul 25 21:56:59 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Printing DDC gathered Modelines: Jul 25 21:56:59 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Modeline "1920x1200"x0.0 154.00 1920 1968 2000 2080 1200 1203 1209 1235 +hsync -vsync (74.0 kHz eP) Jul 25 21:56:59 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Modeline "1680x1050"x0.0 146.25 1680 1784 1960 2240 1050 1053 1059 1089 -hsync +vsync (65.3 kHz e) Jul 25 21:56:59 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Modeline "720x480"x0.0 27.00 720 736 798 858 480 489 495 525 -hsync -vsync (31.5 kHz e) Jul 25 21:56:59 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Modeline "720x576"x0.0 27.00 720 732 796 864 576 581 586 625 -hsync -vsync (31.2 kHz e) Jul 25 21:56:59 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Modeline "1280x720"x0.0 74.25 1280 1390 1430 1650 720 725 730 750 +hsync +vsync (45.0 kHz e) Jul 25 21:56:59 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Modeline "1280x720"x0.0 74.25 1280 1720 1760 1980 720 725 730 750 +hsync +vsync (37.5 kHz e) Jul 25 21:56:59 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Modeline "1920x1080"x0.0 148.50 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync (67.5 kHz e) Jul 25 21:56:59 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Modeline "1920x1080"x0.0 148.50 1920 2448 2492 2640 1080 1084 1089 1125 +hsync +vsync (56.2 kHz e) Jul 25 21:56:59 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Modeline "1920x1080i"x0.0 74.25 1920 2008 2052 2200 1080 1084 1094 1125 interlace +hsync +vsync (33.8 kHz e) Jul 25 21:56:59 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Modeline "1920x1080i"x0.0 74.25 1920 2448 2492 2640 1080 1084 1094 1125 interlace +hsync +vsync (28.1 kHz e) Jul 25 21:56:59 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Modeline "1920x1080"x0.0 74.25 1920 2558 2602 2750 1080 1084 1089 1125 +hsync +vsync (27.0 kHz e) Jul 25 21:56:59 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e) Jul 25 21:56:59 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Modeline "800x600"x0.0 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz e) Jul 25 21:56:59 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e) Jul 25 21:56:59 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Modeline "640x480"x0.0 31.50 640 664 704 832 480 489 492 520 -hsync -vsync (37.9 kHz e) Jul 25 21:56:59 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Modeline "640x480"x0.0 30.24 640 704 768 864 480 483 486 525 -hsync -vsync (35.0 kHz e) Jul 25 21:56:59 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e) Jul 25 21:56:59 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Modeline "720x400"x0.0 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e) Jul 25 21:56:59 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Modeline "1280x1024"x0.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz e) Jul 25 21:56:59 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Modeline "1024x768"x0.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz e) Jul 25 21:56:59 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Modeline "1024x768"x0.0 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync (56.5 kHz e) Jul 25 21:56:59 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e) Jul 25 21:56:59 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Modeline "832x624"x0.0 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz e) Jul 25 21:56:59 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Modeline "800x600"x0.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e) Jul 25 21:56:59 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Modeline "800x600"x0.0 50.00 800 856 976 1040 600 637 643 666 +hsync +vsync (48.1 kHz e) Jul 25 21:56:59 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Modeline "1152x864"x0.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz e) Jul 25 21:56:59 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Modeline "1280x1024"x0.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz e) Jul 25 21:56:59 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Modeline "1400x1050"x0.0 101.00 1400 1448 1480 1560 1050 1053 1057 1080 +hsync -vsync (64.7 kHz e) Jul 25 21:56:59 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Modeline "1366x768"x59.8 84.75 1366 1431 1567 1776 768 771 781 798 -hsync +vsync (47.7 kHz e) Jul 25 21:56:59 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Modeline "1440x900"x0.0 88.75 1440 1488 1520 1600 900 903 909 926 +hsync -vsync (55.5 kHz e) Jul 25 21:56:59 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Modeline "1600x1200"x0.0 162.00 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync (75.0 kHz e) Jul 25 21:56:59 lxjima dbus-daemon[1741]: [session uid=2000 pid=1741] Activating service name='org.freedesktop.portal.IBus' requested by ':1.104' (uid=2000 pid=3553 comm="ibus-daemon --panel disable --xim " label="unconfined") Jul 25 21:56:59 lxjima dbus-daemon[1741]: [session uid=2000 pid=1741] Successfully activated service 'org.freedesktop.portal.IBus' Jul 25 21:56:59 lxjima gnome-shell[3543]: org.gnome.Shell already exists on bus and --replace not specified Jul 25 21:56:59 lxjima systemd[1695]: org.gnome.Shell@x11.service: Failed with result 'protocol'. Jul 25 21:56:59 lxjima systemd[1695]: Failed to start GNOME Shell on X11. Jul 25 21:56:59 lxjima systemd[1695]: org.gnome.Shell@x11.service: Scheduled restart job, restart counter is at 3. Jul 25 21:56:59 lxjima systemd[1695]: Stopped GNOME Shell on X11. Jul 25 21:56:59 lxjima systemd[1695]: Starting GNOME Shell on X11... Jul 25 21:57:00 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): EDID vendor "NEC", prod id 26342 Jul 25 21:57:00 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Using hsync ranges from config file Jul 25 21:57:00 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Using vrefresh ranges from config file Jul 25 21:57:00 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Printing DDC gathered Modelines: Jul 25 21:57:00 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Modeline "1920x1200"x0.0 154.00 1920 1968 2000 2080 1200 1203 1209 1235 +hsync -vsync (74.0 kHz eP) Jul 25 21:57:00 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Modeline "1680x1050"x0.0 146.25 1680 1784 1960 2240 1050 1053 1059 1089 -hsync +vsync (65.3 kHz e) Jul 25 21:57:00 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Modeline "720x480"x0.0 27.00 720 736 798 858 480 489 495 525 -hsync -vsync (31.5 kHz e) Jul 25 21:57:00 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Modeline "720x576"x0.0 27.00 720 732 796 864 576 581 586 625 -hsync -vsync (31.2 kHz e) Jul 25 21:57:00 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Modeline "1280x720"x0.0 74.25 1280 1390 1430 1650 720 725 730 750 +hsync +vsync (45.0 kHz e) Jul 25 21:57:00 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Modeline "1280x720"x0.0 74.25 1280 1720 1760 1980 720 725 730 750 +hsync +vsync (37.5 kHz e) Jul 25 21:57:00 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Modeline "1920x1080"x0.0 148.50 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync (67.5 kHz e) Jul 25 21:57:00 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Modeline "1920x1080"x0.0 148.50 1920 2448 2492 2640 1080 1084 1089 1125 +hsync +vsync (56.2 kHz e) Jul 25 21:57:00 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Modeline "1920x1080i"x0.0 74.25 1920 2008 2052 2200 1080 1084 1094 1125 interlace +hsync +vsync (33.8 kHz e) Jul 25 21:57:00 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Modeline "1920x1080i"x0.0 74.25 1920 2448 2492 2640 1080 1084 1094 1125 interlace +hsync +vsync (28.1 kHz e) Jul 25 21:57:00 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Modeline "1920x1080"x0.0 74.25 1920 2558 2602 2750 1080 1084 1089 1125 +hsync +vsync (27.0 kHz e) Jul 25 21:57:00 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e) Jul 25 21:57:00 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Modeline "800x600"x0.0 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz e) Jul 25 21:57:00 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e) Jul 25 21:57:00 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Modeline "640x480"x0.0 31.50 640 664 704 832 480 489 492 520 -hsync -vsync (37.9 kHz e) Jul 25 21:57:00 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Modeline "640x480"x0.0 30.24 640 704 768 864 480 483 486 525 -hsync -vsync (35.0 kHz e) Jul 25 21:57:00 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e) Jul 25 21:57:00 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Modeline "720x400"x0.0 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e) Jul 25 21:57:00 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Modeline "1280x1024"x0.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz e) Jul 25 21:57:00 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Modeline "1024x768"x0.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz e) Jul 25 21:57:00 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Modeline "1024x768"x0.0 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync (56.5 kHz e) Jul 25 21:57:00 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e) Jul 25 21:57:00 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Modeline "832x624"x0.0 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz e) Jul 25 21:57:00 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Modeline "800x600"x0.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e) Jul 25 21:57:00 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Modeline "800x600"x0.0 50.00 800 856 976 1040 600 637 643 666 +hsync +vsync (48.1 kHz e) Jul 25 21:57:00 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Modeline "1152x864"x0.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz e) Jul 25 21:57:00 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Modeline "1280x1024"x0.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz e) Jul 25 21:57:00 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Modeline "1400x1050"x0.0 101.00 1400 1448 1480 1560 1050 1053 1057 1080 +hsync -vsync (64.7 kHz e) Jul 25 21:57:00 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Modeline "1366x768"x59.8 84.75 1366 1431 1567 1776 768 771 781 798 -hsync +vsync (47.7 kHz e) Jul 25 21:57:00 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Modeline "1440x900"x0.0 88.75 1440 1488 1520 1600 900 903 909 926 +hsync -vsync (55.5 kHz e) Jul 25 21:57:00 lxjima /usr/libexec/gdm-x-session[1739]: (II) modeset(0): Modeline "1600x1200"x0.0 162.00 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync (75.0 kHz e) Jul 25 21:57:00 lxjima gnome-shell[3575]: org.gnome.Shell already exists on bus and --replace not specified Jul 25 21:57:00 lxjima systemd[1695]: org.gnome.Shell@x11.service: Failed with result 'protocol'. Jul 25 21:57:00 lxjima systemd[1695]: Failed to start GNOME Shell on X11. Jul 25 21:57:00 lxjima systemd[1695]: org.gnome.Shell@x11.service: Scheduled restart job, restart counter is at 4. Jul 25 21:57:00 lxjima systemd[1695]: Stopped GNOME Shell on X11. Jul 25 21:57:00 lxjima systemd[1695]: org.gnome.Shell@x11.service: Start request repeated too quickly. Jul 25 21:57:00 lxjima systemd[1695]: org.gnome.Shell@x11.service: Failed with result 'protocol'. Jul 25 21:57:00 lxjima systemd[1695]: Failed to start GNOME Shell on X11. Jul 25 21:57:00 lxjima systemd[1695]: org.gnome.Shell@x11.service: Triggering OnFailure= dependencies. Jul 25 21:57:00 lxjima systemd[1695]: Started GNOME Session Failed lockdown screen (user). Jul 25 21:57:00 lxjima systemd[1695]: Reached target GNOME Session Failed. Jul 25 21:57:00 lxjima systemd[1695]: Condition check resulted in Disable GNOME Shell extensions after failure being skipped. Jul 25 21:57:00 lxjima dbus-daemon[1436]: [system] Activating via systemd: service name='org.freedesktop.GeoClue2' unit='geoclue.service' requested by ':1.86' (uid=2000 pid=3507 comm="/usr/bin/gnome-shell --replace " label="unconfined") Jul 25 21:57:00 lxjima systemd[1]: Starting Location Lookup Service... Jul 25 21:57:00 lxjima dbus-daemon[1436]: [system] Successfully activated service 'org.freedesktop.GeoClue2' Jul 25 21:57:00 lxjima systemd[1]: Started Location Lookup Service. Jul 25 21:57:00 lxjima dbus-daemon[1741]: [session uid=2000 pid=1741] Activating service name='org.freedesktop.FileManager1' requested by ':1.101' (uid=2000 pid=3507 comm="/usr/bin/gnome-shell --replace " label="unconfined") Jul 25 21:57:00 lxjima dbus-daemon[1741]: [session uid=2000 pid=1741] Activating service name='org.gnome.Shell.Notifications' requested by ':1.101' (uid=2000 pid=3507 comm="/usr/bin/gnome-shell --replace " label="unconfined") Jul 25 21:57:00 lxjima dbus-daemon[1741]: [session uid=2000 pid=1741] Successfully activated service 'org.gnome.Shell.Notifications' Jul 25 21:57:00 lxjima NetworkManager[1437]: [1627275420.3592] agent-manager: agent[90990d8667597241,:1.86/org.gnome.Shell.NetworkAgent/2000]: agent registered Jul 25 21:57:00 lxjima org.freedesktop.FileManager1[3598]: Initializing nautilus-image-converter extension Jul 25 21:57:00 lxjima dbus-daemon[1741]: [session uid=2000 pid=1741] Successfully activated service 'org.freedesktop.FileManager1' Jul 25 21:57:00 lxjima gsd-media-keys[2267]: Failed to grab accelerator for keybinding settings:rfkill Jul 25 21:57:00 lxjima gsd-media-keys[2267]: Failed to grab accelerator for keybinding settings:playback-random Jul 25 21:57:00 lxjima gsd-media-keys[2267]: Failed to grab accelerator for keybinding settings:playback-repeat Jul 25 21:57:00 lxjima gsd-media-keys[2267]: Failed to grab accelerator for keybinding settings:rotate-video-lock Jul 25 21:57:00 lxjima gsd-media-keys[2267]: Failed to grab accelerator for keybinding settings:hibernate Jul 25 21:57:20 lxjima systemd[1]: Started Session 22 of user jima. Jul 25 21:57:22 lxjima accounts-daemon[1475]: failed to check if user 'jima2' in cache dir is present on system: No such file or directory Jul 25 21:58:00 lxjima geoclue[3592]: Service not used for 60 seconds. Shutting down.. Jul 25 21:58:00 lxjima systemd[1]: geoclue.service: Succeeded. === end test ===