Ιουν 23 21:29:05 machine gnome-shell[1737]: GNOME Shell started at Tue Jun 23 2020 21:29:03 GMT+0200 (CEST) Ιουν 23 21:29:05 machine gnome-shell[1737]: Registering session with GDM Ιουν 23 21:29:05 machine gnome-shell[1737]: Error registering session with GDM: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.DisplayManager was not provided by any .service files Ιουν 23 21:29:17 machine gnome-shell[1737]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a). Ιουν 23 21:29:17 machine gnome-shell[1737]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b). Ιουν 23 21:29:17 machine gnome-shell[1737]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c). Ιουν 23 21:29:17 machine gnome-shell[1737]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d). Ιουν 23 21:29:17 machine gnome-shell[1737]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). Ιουν 23 21:29:17 machine gnome-shell[1737]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f). Ιουν 23 21:29:17 machine gnome-shell[1737]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11). Ιουν 23 21:29:17 machine gnome-shell[1737]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12). Ιουν 23 21:29:17 machine gnome-shell[1737]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). Ιουν 23 21:29:19 machine gnome-shell[1737]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11). Ιουν 23 21:29:19 machine gnome-shell[1737]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a). Ιουν 23 21:29:19 machine gnome-shell[1737]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12). Ιουν 23 21:29:19 machine gnome-shell[1737]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b). Ιουν 23 21:29:19 machine gnome-shell[1737]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c). Ιουν 23 21:29:19 machine gnome-shell[1737]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). Ιουν 23 21:29:19 machine gnome-shell[1737]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d). Ιουν 23 21:29:19 machine gnome-shell[1737]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). Ιουν 23 21:29:19 machine gnome-shell[1737]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f). Ιουν 23 21:29:23 machine gnome-shell[1737]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a). Ιουν 23 21:29:23 machine gnome-shell[1737]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b). Ιουν 23 21:29:23 machine gnome-shell[1737]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c). Ιουν 23 21:29:23 machine gnome-shell[1737]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d). Ιουν 23 21:29:23 machine gnome-shell[1737]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11). Ιουν 23 21:29:23 machine gnome-shell[1737]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12). Ιουν 23 21:29:23 machine gnome-shell[1737]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). Ιουν 23 21:29:23 machine gnome-shell[1737]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f). Ιουν 23 21:29:23 machine gnome-shell[1737]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). Ιουν 23 21:29:33 machine gnome-shell[1737]: ../clutter/clutter/clutter-actor.c:10548: The clutter_actor_set_allocation() function can only be called from within the implementation of the ClutterActor::allocate() virtual function. Ιουν 23 21:29:36 machine gnome-shell[1737]: ../clutter/clutter/clutter-actor.c:10548: The clutter_actor_set_allocation() function can only be called from within the implementation of the ClutterActor::allocate() virtual function. Ιουν 23 21:29:40 machine gnome-shell[1737]: ../clutter/clutter/clutter-actor.c:10548: The clutter_actor_set_allocation() function can only be called from within the implementation of the ClutterActor::allocate() virtual function. Ιουν 23 21:29:57 machine gnome-shell[1737]: gnome-session gave us a dead inhibitor: /org/gnome/SessionManager/Inhibitor1 Ιουν 23 21:30:00 machine gnome-shell[1737]: Window manager warning: META_CURRENT_TIME used to choose focus window; focus window may not be correct. Ιουν 23 21:30:00 machine gnome-shell[1737]: JS ERROR: TypeError: actor.get_meta_window(...) is null _destroyWindowDone@resource:///org/gnome/shell/ui/windowManager.js:1578:32 onStopped@resource:///org/gnome/shell/ui/windowManager.js:1548:39 _makeEaseCallback/<@resource:///org/gnome/shell/ui/environment.js:73:13 _easeActor/<@resource:///org/gnome/shell/ui/environment.js:149:56 Ιουν 23 21:30:00 machine gnome-shell[1737]: JS ERROR: TypeError: actor.get_meta_window(...) is null _destroyWindowDone@resource:///org/gnome/shell/ui/windowManager.js:1578:32 onStopped@resource:///org/gnome/shell/ui/windowManager.js:1548:39 _makeEaseCallback/<@resource:///org/gnome/shell/ui/environment.js:73:13 _easeActor/<@resource:///org/gnome/shell/ui/environment.js:149:56 Ιουν 23 21:30:00 machine gnome-shell[1737]: JS ERROR: TypeError: actor.get_meta_window(...) is null _destroyWindowDone@resource:///org/gnome/shell/ui/windowManager.js:1578:32 onStopped@resource:///org/gnome/shell/ui/windowManager.js:1548:39 _makeEaseCallback/<@resource:///org/gnome/shell/ui/environment.js:73:13 _easeActor/<@resource:///org/gnome/shell/ui/environment.js:149:56 Ιουν 23 21:30:00 machine gnome-shell[1737]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Ιουν 23 21:30:00 machine gnome-shell[1737]: == Stack trace for context 0x55b7ea8926f0 == Ιουν 23 21:30:00 machine gnome-shell[1737]: == Stack trace for context 0x55b7ea8926f0 == Ιουν 23 21:30:00 machine gnome-shell[1737]: == Stack trace for context 0x55b7ea8926f0 == Ιουν 23 21:30:00 machine gnome-shell[1737]: == Stack trace for context 0x55b7ea8926f0 == Ιουν 23 21:30:00 machine gnome-shell[1737]: The offending signal was destroy on Gjs_ui_iconGrid_IconGrid 0x55b7edbf0120. Ιουν 23 21:30:00 machine gnome-shell[1737]: == Stack trace for context 0x55b7ea8926f0 == Ιουν 23 21:30:00 machine gnome-shell[1737]: == Stack trace for context 0x55b7ea8926f0 == Ιουν 23 21:30:00 machine gnome-shell[1737]: == Stack trace for context 0x55b7ea8926f0 == Ιουν 23 21:30:00 machine gnome-shell[1737]: == Stack trace for context 0x55b7ea8926f0 == Ιουν 23 21:30:00 machine gnome-shell[1737]: == Stack trace for context 0x55b7ea8926f0 == Ιουν 23 21:30:00 machine gnome-shell[1737]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Ιουν 23 21:30:00 machine gnome-shell[1737]: == Stack trace for context 0x55b7ea8926f0 == Ιουν 23 21:30:00 machine gnome-shell[1737]: The offending signal was destroy on Gjs_ui_iconGrid_IconGrid 0x55b7edb0f290. Ιουν 23 21:30:00 machine gnome-shell[1737]: == Stack trace for context 0x55b7ea8926f0 == Ιουν 23 21:30:00 machine gnome-shell[1737]: == Stack trace for context 0x55b7ea8926f0 == Ιουν 23 21:30:00 machine gnome-shell[1737]: == Stack trace for context 0x55b7ea8926f0 == Ιουν 23 21:30:00 machine gnome-shell[1737]: == Stack trace for context 0x55b7ea8926f0 == Ιουν 23 21:30:00 machine gnome-shell[1737]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Ιουν 23 21:30:00 machine gnome-shell[1737]: == Stack trace for context 0x55b7ea8926f0 == Ιουν 23 21:30:00 machine gnome-shell[1737]: == Stack trace for context 0x55b7ea8926f0 == Ιουν 23 21:30:00 machine gnome-shell[1737]: == Stack trace for context 0x55b7ea8926f0 == Ιουν 23 21:30:00 machine gnome-shell[1737]: == Stack trace for context 0x55b7ea8926f0 == Ιουν 23 21:30:00 machine gnome-shell[1737]: == Stack trace for context 0x55b7ea8926f0 == Ιουν 23 21:30:00 machine gnome-shell[1737]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55b7ed960680. Ιουν 23 21:30:00 machine gnome-shell[1737]: == Stack trace for context 0x55b7ea8926f0 == Ιουν 23 21:30:00 machine gnome-shell[1737]: == Stack trace for context 0x55b7ea8926f0 == Ιουν 23 21:30:00 machine gnome-shell[1737]: == Stack trace for context 0x55b7ea8926f0 == Ιουν 23 21:30:00 machine gnome-shell[1737]: == Stack trace for context 0x55b7ea8926f0 == Ιουν 23 21:30:00 machine gnome-shell[1737]: == Stack trace for context 0x55b7ea8926f0 == Ιουν 23 21:30:00 machine gnome-shell[1737]: == Stack trace for context 0x55b7ea8926f0 == Ιουν 23 21:30:00 machine gnome-shell[1737]: == Stack trace for context 0x55b7ea8926f0 == Ιουν 23 21:30:00 machine gnome-shell[1737]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Ιουν 23 21:30:00 machine gnome-shell[1737]: == Stack trace for context 0x55b7ea8926f0 == Ιουν 23 21:30:00 machine gnome-shell[1737]: == Stack trace for context 0x55b7ea8926f0 == Ιουν 23 21:30:00 machine gnome-shell[1737]: == Stack trace for context 0x55b7ea8926f0 == Ιουν 23 21:30:00 machine gnome-shell[1737]: == Stack trace for context 0x55b7ea8926f0 == Ιουν 23 21:30:00 machine gnome-shell[1737]: == Stack trace for context 0x55b7ea8926f0 == Ιουν 23 21:30:00 machine gnome-shell[1737]: == Stack trace for context 0x55b7ea8926f0 == Ιουν 23 21:30:00 machine gnome-shell[1737]: == Stack trace for context 0x55b7ea8926f0 == Ιουν 23 21:30:00 machine gnome-shell[1737]: == Stack trace for context 0x55b7ea8926f0 == Ιουν 23 21:30:00 machine gnome-shell[1737]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55b7ed960680. Ιουν 23 21:30:00 machine gnome-shell[1737]: == Stack trace for context 0x55b7ea8926f0 == Ιουν 23 21:30:00 machine gnome-shell[1737]: == Stack trace for context 0x55b7ea8926f0 == Ιουν 23 21:30:00 machine gnome-shell[1737]: == Stack trace for context 0x55b7ea8926f0 == Ιουν 23 21:30:00 machine gnome-shell[1737]: == Stack trace for context 0x55b7ea8926f0 == Ιουν 23 21:30:00 machine gnome-shell[1737]: == Stack trace for context 0x55b7ea8926f0 == Ιουν 23 21:30:00 machine gnome-shell[1737]: == Stack trace for context 0x55b7ea8926f0 == Ιουν 23 21:30:00 machine gnome-shell[1737]: == Stack trace for context 0x55b7ea8926f0 == Ιουν 23 21:30:00 machine gnome-shell[1737]: == Stack trace for context 0x55b7ea8926f0 == Ιουν 23 21:30:00 machine gnome-shell[1737]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Ιουν 23 21:30:00 machine gnome-shell[1737]: == Stack trace for context 0x55b7ea8926f0 == Ιουν 23 21:30:00 machine gnome-shell[1737]: == Stack trace for context 0x55b7ea8926f0 == Ιουν 23 21:30:00 machine gnome-shell[1737]: == Stack trace for context 0x55b7ea8926f0 == Ιουν 23 21:30:00 machine gnome-shell[1737]: == Stack trace for context 0x55b7ea8926f0 == Ιουν 23 21:30:00 machine gnome-shell[1737]: == Stack trace for context 0x55b7ea8926f0 == Ιουν 23 21:30:00 machine gnome-shell[1737]: == Stack trace for context 0x55b7ea8926f0 == Ιουν 23 21:30:00 machine gnome-shell[1737]: == Stack trace for context 0x55b7ea8926f0 == Ιουν 23 21:30:00 machine gnome-shell[1737]: == Stack trace for context 0x55b7ea8926f0 == Ιουν 23 21:30:00 machine gnome-shell[1737]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55b7ee1b6130. Ιουν 23 21:30:00 machine gnome-shell[1737]: == Stack trace for context 0x55b7ea8926f0 == Ιουν 23 21:30:00 machine gnome-shell[1737]: == Stack trace for context 0x55b7ea8926f0 == Ιουν 23 21:30:00 machine gnome-shell[1737]: == Stack trace for context 0x55b7ea8926f0 == Ιουν 23 21:30:00 machine gnome-shell[1737]: == Stack trace for context 0x55b7ea8926f0 == Ιουν 23 21:30:00 machine gnome-shell[1737]: == Stack trace for context 0x55b7ea8926f0 == Ιουν 23 21:30:00 machine gnome-shell[1737]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Ιουν 23 21:30:00 machine gnome-shell[1737]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55b7edb0f290. Ιουν 23 21:30:00 machine gnome-shell[1737]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Ιουν 23 21:30:00 machine gnome-shell[1737]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55b7ee2add00. Ιουν 23 21:30:00 machine gnome-shell[1737]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Ιουν 23 21:30:00 machine gnome-shell[1737]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55b7ee2add00. Ιουν 23 21:30:00 machine gnome-shell[1737]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Ιουν 23 21:30:00 machine gnome-shell[1737]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55b7ed863a90. Ιουν 23 21:30:00 machine gnome-shell[1737]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Ιουν 23 21:30:00 machine gnome-shell[1737]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55b7edb0f290. Ιουν 23 21:30:00 machine gnome-shell[1737]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Ιουν 23 21:30:00 machine gnome-shell[1737]: The offending signal was destroy on Gjs_ui_iconGrid_IconGrid 0x55b7ee26bd10. Ιουν 23 21:30:00 machine gnome-shell[1737]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Ιουν 23 21:30:00 machine gnome-shell[1737]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55b7ee4f8b10. Ιουν 23 21:30:00 machine gnome-shell[1737]: == Stack trace for context 0x55b7ea8926f0 == Ιουν 23 21:30:00 machine gnome-shell[1737]: == Stack trace for context 0x55b7ea8926f0 == Ιουν 23 21:30:00 machine gnome-shell[1737]: == Stack trace for context 0x55b7ea8926f0 == Ιουν 23 21:30:00 machine gnome-shell[1737]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Ιουν 23 21:30:00 machine gnome-shell[1737]: == Stack trace for context 0x55b7ea8926f0 == Ιουν 23 21:30:00 machine gnome-shell[1737]: == Stack trace for context 0x55b7ea8926f0 == Ιουν 23 21:30:00 machine gnome-shell[1737]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55b7ee4f8b10. Ιουν 23 21:30:00 machine gnome-shell[1737]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Ιουν 23 21:30:00 machine gnome-shell[1737]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55b7ee417700. Ιουν 23 21:30:00 machine gnome-shell[1737]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Ιουν 23 21:30:00 machine gnome-shell[1737]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55b7ee26bd10. Ιουν 23 21:30:00 machine gnome-shell[1737]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Ιουν 23 21:30:00 machine gnome-shell[1737]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55b7ee36d1e0. Ιουν 23 21:30:00 machine gnome-shell[1737]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Ιουν 23 21:30:00 machine gnome-shell[1737]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55b7ee36d1e0. Ιουν 23 21:30:00 machine gnome-shell[1737]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Ιουν 23 21:30:00 machine gnome-shell[1737]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55b7ee40ca90. Ιουν 23 21:30:00 machine gnome-shell[1737]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Ιουν 23 21:30:00 machine gnome-shell[1737]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55b7ee26bd10. Ιουν 23 21:30:00 machine gnome-shell[1737]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Ιουν 23 21:30:00 machine gnome-shell[1737]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55b7f0a35a50. Ιουν 23 21:30:00 machine gnome-shell[1737]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Ιουν 23 21:30:00 machine gnome-shell[1737]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55b7f0a35a50. Ιουν 23 21:30:00 machine gnome-shell[1737]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Ιουν 23 21:30:00 machine gnome-shell[1737]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55b7ebe9c170. Ιουν 23 21:30:00 machine gnome-shell[1737]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Ιουν 23 21:30:00 machine gnome-shell[1737]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55b7ee26bd10. Ιουν 23 21:30:00 machine gnome-shell[1737]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Ιουν 23 21:30:00 machine gnome-shell[1737]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55b7ef11c5d0. Ιουν 23 21:30:00 machine gnome-shell[1737]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Ιουν 23 21:30:00 machine gnome-shell[1737]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55b7ef11c5d0. Ιουν 23 21:30:00 machine gnome-shell[1737]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Ιουν 23 21:30:00 machine gnome-shell[1737]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55b7ee8083c0. Ιουν 23 21:30:00 machine gnome-shell[1737]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Ιουν 23 21:30:00 machine gnome-shell[1737]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55b7ee26bd10. Ιουν 23 21:30:00 machine gnome-shell[1737]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Ιουν 23 21:30:00 machine gnome-shell[1737]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55b7ee3e4b50. Ιουν 23 21:30:00 machine gnome-shell[1737]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Ιουν 23 21:30:00 machine gnome-shell[1737]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55b7ee3e4b50. Ιουν 23 21:30:00 machine gnome-shell[1737]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Ιουν 23 21:30:00 machine gnome-shell[1737]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55b7f08b8e70. Ιουν 23 21:30:00 machine gnome-shell[1737]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Ιουν 23 21:30:00 machine gnome-shell[1737]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55b7ee26bd10. Ιουν 23 21:30:00 machine gnome-shell[1737]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Ιουν 23 21:30:00 machine gnome-shell[1737]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55b7f0a17420. Ιουν 23 21:30:00 machine gnome-shell[1737]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Ιουν 23 21:30:00 machine gnome-shell[1737]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55b7f0a17420. Ιουν 23 21:30:00 machine gnome-shell[1737]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Ιουν 23 21:30:00 machine gnome-shell[1737]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55b7ed972c00. Ιουν 23 21:30:00 machine gnome-shell[1737]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Ιουν 23 21:30:00 machine gnome-shell[1737]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55b7ee26bd10. Ιουν 23 21:30:00 machine gnome-shell[1737]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Ιουν 23 21:30:00 machine gnome-shell[1737]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55b7ed785ed0. Ιουν 23 21:30:00 machine gnome-shell[1737]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Ιουν 23 21:30:00 machine gnome-shell[1737]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55b7ed785ed0. Ιουν 23 21:30:00 machine gnome-shell[1737]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Ιουν 23 21:30:00 machine gnome-shell[1737]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55b7ee27a4d0. Ιουν 23 21:30:00 machine gnome-shell[1737]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Ιουν 23 21:30:00 machine gnome-shell[1737]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55b7ee26bd10. Ιουν 23 21:30:00 machine gnome-shell[1737]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Ιουν 23 21:30:00 machine gnome-shell[1737]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55b7ee1eeec0. Ιουν 23 21:30:00 machine gnome-shell[1737]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Ιουν 23 21:30:00 machine gnome-shell[1737]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55b7ee1eeec0. Ιουν 23 21:30:00 machine gnome-shell[1737]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Ιουν 23 21:30:00 machine gnome-shell[1737]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55b7eb499f70. Ιουν 23 21:30:00 machine gnome-shell[1737]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Ιουν 23 21:30:00 machine gnome-shell[1737]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55b7ee26bd10. Ιουν 23 21:30:00 machine gnome-shell[1737]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Ιουν 23 21:30:00 machine gnome-shell[1737]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55b7ec318c90. Ιουν 23 21:30:00 machine gnome-shell[1737]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Ιουν 23 21:30:00 machine gnome-shell[1737]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55b7ec318c90. Ιουν 23 21:30:00 machine gnome-shell[1737]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Ιουν 23 21:30:00 machine gnome-shell[1737]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55b7f0a15420. Ιουν 23 21:30:00 machine gnome-shell[1737]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Ιουν 23 21:30:00 machine gnome-shell[1737]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55b7ee26bd10. Ιουν 23 21:30:00 machine gnome-shell[1737]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Ιουν 23 21:30:00 machine gnome-shell[1737]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55b7eb47d790. Ιουν 23 21:30:00 machine gnome-shell[1737]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Ιουν 23 21:30:00 machine gnome-shell[1737]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55b7eb47d790. Ιουν 23 21:30:00 machine gnome-shell[1737]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Ιουν 23 21:30:00 machine gnome-shell[1737]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55b7ecc34e00. Ιουν 23 21:30:00 machine gnome-shell[1737]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Ιουν 23 21:30:00 machine gnome-shell[1737]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55b7ee26bd10. Ιουν 23 21:30:00 machine gnome-shell[1737]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Ιουν 23 21:30:00 machine gnome-shell[1737]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55b7ed867890. Ιουν 23 21:30:00 machine gnome-shell[1737]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Ιουν 23 21:30:00 machine gnome-shell[1737]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55b7ed867890. Ιουν 23 21:30:00 machine gnome-shell[1737]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Ιουν 23 21:30:00 machine gnome-shell[1737]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55b7ee829380. Ιουν 23 21:30:00 machine gnome-shell[1737]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Ιουν 23 21:30:00 machine gnome-shell[1737]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55b7ee26bd10. Ιουν 23 21:30:00 machine gnome-shell[1737]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Ιουν 23 21:30:00 machine gnome-shell[1737]: The offending signal was notify on NMDeviceEthernet 0x55b7f08a0230. Ιουν 23 21:30:00 machine gnome-shell[1737]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Ιουν 23 21:30:00 machine gnome-shell[1737]: The offending signal was notify on NMDeviceWifi 0x7f36a4016e30. Ιουν 23 21:30:00 machine gnome-shell[1737]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Ιουν 23 21:30:00 machine gnome-shell[1737]: The offending signal was notify on NMActiveConnection 0x55b7f08a5180. Ιουν 23 21:30:00 machine gnome-shell[1737]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Ιουν 23 21:30:00 machine gnome-shell[1737]: The offending signal was state-changed on NMDeviceEthernet 0x55b7f08a0230. Ιουν 23 21:30:00 machine gnome-shell[1737]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Ιουν 23 21:30:00 machine gnome-shell[1737]: The offending signal was state-changed on NMDeviceWifi 0x7f36a4016e30. Ιουν 23 21:30:16 machine gnome-shell[6614]: Telepathy is not available, chat integration will be disabled. Ιουν 23 21:30:16 machine gnome-shell[6614]: Failed to create file /run/user/1000/gnome-shell-disable-extensions: Error opening file “/run/user/1000/gnome-shell-disable-extensions”: File exists Ιουν 23 21:30:16 machine gnome-shell[6614]: loading user theme: /usr/share/themes/Yaru-dark/gnome-shell/gnome-shell.css Ιουν 23 21:30:16 machine gnome-shell[6614]: Usage of object.actor is deprecated for ATIndicator get@resource:///org/gnome/shell/ui/environment.js:287:29 _init@/home/user/.local/share/gnome-shell/extensions/removeaccesibility@lomegor/extension.js:37:9 wrapper@resource:///org/gnome/gjs/modules/script/_legacy.js:82:27 _Base.prototype._construct@resource:///org/gnome/gjs/modules/script/_legacy.js:18:10 newClass@resource:///org/gnome/gjs/modules/script/_legacy.js:114:21 enable@/home/user/.local/share/gnome-shell/extensions/removeaccesibility@lomegor/extension.js:72:19 _callExtensionEnable@resource:///org/gnome/shell/ui/extensionSystem.js:166:32 loadExtension@resource:///org/gnome/shell/ui/extensionSystem.js:336:26 _loadExtensions/<@resource:///org/gnome/shell/ui/extensionSystem.js:577:18 collectFromDatadirs@resource:///org/gnome/shell/misc/fileUtils.js:27:17 _loadExtensions@resource:///org/gnome/shell/ui/extensionSystem.js:552:19 _enableAllExtensions@resource:///org/gnome/shell/ui/extensionSystem.js:586:18 _sessionUpdated@resource:///org/gnome/shell/ui/extensionSystem.js:617:18 init@resource:///org/gnome/shell/ui/extensionSystem.js:55:14 _initializeUI@resource:///org/gnome/shell/ui/main.js:257:22 start@resource:///org/gnome/shell/ui/main.js:146:5 @
:1:47 Ιουν 23 21:30:17 machine gnome-shell[6614]: Error looking up permission: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for geolocation Ιουν 23 21:30:19 machine gnome-shell[6614]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11). Ιουν 23 21:30:19 machine gnome-shell[6614]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12). Ιουν 23 21:30:19 machine gnome-shell[6614]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a). Ιουν 23 21:30:19 machine gnome-shell[6614]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b). Ιουν 23 21:30:19 machine gnome-shell[6614]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c). Ιουν 23 21:30:19 machine gnome-shell[6614]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d). Ιουν 23 21:30:19 machine gnome-shell[6614]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). Ιουν 23 21:30:19 machine gnome-shell[6614]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f). Ιουν 23 21:30:19 machine gnome-shell[6614]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). Ιουν 23 21:30:20 machine gnome-shell[6614]: GNOME Shell started at Tue Jun 23 2020 21:30:16 GMT+0200 (CEST) Ιουν 23 21:30:20 machine gnome-shell[6614]: Registering session with GDM Ιουν 23 21:30:20 machine gnome-shell[6614]: Error registering session with GDM: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.DisplayManager was not provided by any .service files Ιουν 23 21:30:52 machine gnome-shell[6614]: Enabling experimental feature 'x11-randr-fractional-scaling' Ιουν 23 21:30:52 machine gnome-shell[6614]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a). Ιουν 23 21:30:52 machine gnome-shell[6614]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b). Ιουν 23 21:30:52 machine gnome-shell[6614]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c). Ιουν 23 21:30:52 machine gnome-shell[6614]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d). Ιουν 23 21:30:52 machine gnome-shell[6614]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). Ιουν 23 21:30:52 machine gnome-shell[6614]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f). Ιουν 23 21:30:52 machine gnome-shell[6614]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11). Ιουν 23 21:30:52 machine gnome-shell[6614]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12). Ιουν 23 21:30:52 machine gnome-shell[6614]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). Ιουν 23 21:31:03 machine gnome-shell[6614]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a). Ιουν 23 21:31:03 machine gnome-shell[6614]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b). Ιουν 23 21:31:03 machine gnome-shell[6614]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c). Ιουν 23 21:31:03 machine gnome-shell[6614]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d). Ιουν 23 21:31:03 machine gnome-shell[6614]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11). Ιουν 23 21:31:03 machine gnome-shell[6614]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12). Ιουν 23 21:31:03 machine gnome-shell[6614]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). Ιουν 23 21:31:03 machine gnome-shell[6614]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f). Ιουν 23 21:31:03 machine gnome-shell[6614]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).