-- Logs begin at Thu 2018-03-01 10:20:10 EST, end at Fri 2018-03-02 12:00:21 EST. -- Mar 01 12:36:06 hostname gnome-terminal-[1661]: Allocating size to GtkBox 0x5647a62246d0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Mar 01 12:37:00 hostname org.debian.apt[610]: 12:37:00 AptDaemon [INFO]: Quitting due to inactivity Mar 01 12:37:00 hostname org.debian.apt[610]: 12:37:00 AptDaemon [INFO]: Quitting was requested Mar 01 12:37:05 hostname gnome-software[1599]: no app for changed ubuntu-appindicators@ubuntu.com Mar 01 12:37:05 hostname gnome-software[1599]: no app for changed ubuntu-dock@ubuntu.com Mar 01 12:37:14 hostname gnome-software[1599]: no app for changed ubuntu-dock@ubuntu.com Mar 01 12:37:14 hostname gnome-software[1599]: no app for changed ubuntu-appindicators@ubuntu.com Mar 01 12:38:43 hostname nautilus[6412]: g_key_file_load_from_file: assertion 'file != NULL' failed Mar 01 12:38:43 hostname nautilus[6412]: Could not establish a connection to Tracker: Failed to load SPARQL backend: Key file does not have group “DomainOntology” Mar 01 12:38:44 hostname nautilus[6412]: g_key_file_load_from_file: assertion 'file != NULL' failed Mar 01 12:38:44 hostname nautilus[6412]: Could not establish a connection to Tracker: Failed to load SPARQL backend: Key file does not have group “DomainOntology” Mar 01 12:38:45 hostname gnome-tweak-too[15890]: Failed to measure available space: The specified location is not supported Mar 01 12:38:45 hostname gnome-tweak-too[15890]: Failed to measure available space: The specified location is not supported Mar 01 12:38:55 hostname gnome-terminal-[1661]: Allocating size to GtkBox 0x5647a62246d0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Mar 01 12:38:55 hostname kerneloops-appl[1597]: Unable to locate theme engine in module_path: "hcengine", Mar 01 12:38:55 hostname gnome-terminal-[1661]: Allocating size to GtkBox 0x5647a66bc470 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Mar 01 12:38:56 hostname gnome-terminal-[1661]: Allocating size to GtkBox 0x5647a62246d0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Mar 01 12:38:56 hostname gnome-terminal-[1661]: Allocating size to GtkBox 0x5647a66bc470 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Mar 01 12:38:56 hostname gnome-terminal-[1661]: Allocating size to GtkBox 0x5647a66bc470 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Mar 01 12:39:32 hostname gnome-terminal-[1661]: Allocating size to GtkBox 0x5647a62246d0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Mar 01 12:39:32 hostname gnome-terminal-[1661]: Allocating size to GtkBox 0x5647a66bc470 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Mar 01 12:39:32 hostname gnome-terminal-[1661]: Allocating size to GtkBox 0x5647a62246d0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Mar 01 12:39:32 hostname gnome-terminal-[1661]: Allocating size to GtkBox 0x5647a66bc470 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Mar 01 12:39:32 hostname gnome-terminal-[1661]: Allocating size to GtkBox 0x5647a62246d0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Mar 01 12:39:32 hostname gnome-terminal-[1661]: Allocating size to GtkBox 0x5647a66bc470 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Mar 01 12:39:32 hostname gnome-terminal-[1661]: Allocating size to GtkBox 0x5647a66bc470 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Mar 01 12:40:43 hostname nautilus[6412]: Failed to measure available space: The specified location is not supported Mar 01 12:41:23 hostname gnome-shell[1310]: setup_framebuffers: assertion 'width > 0' failed Mar 01 12:41:23 hostname eog[16017]: Failed to open file '/home/username/.cache/thumbnails/normal/36987f74ce515faa65f19b187dbb6f7d.png': No such file or directory Mar 01 12:41:26 hostname eog[16017]: Failed to open file '/home/username/.cache/thumbnails/normal/79c838271e63e41a058caee97086a946.png': No such file or directory Mar 01 12:41:27 hostname eog[16017]: Failed to open file '/home/username/.cache/thumbnails/normal/c406ee7cfb33acee42e1c421bcf9f3cf.png': No such file or directory Mar 01 12:41:28 hostname org.gnome.Nautilus[1227]: Duplicate property or field node Mar 01 12:41:28 hostname eog[16017]: Failed to open file '/home/username/.cache/thumbnails/normal/5610d31ae8f915ef97f627de3b7a746a.png': No such file or directory Mar 01 12:41:29 hostname eog[16017]: Failed to open file '/home/username/.cache/thumbnails/normal/3b2dec6f9dcdbb7bf9b06aad0996cad8.png': No such file or directory Mar 01 12:41:31 hostname eog[16017]: Failed to open file '/home/username/.cache/thumbnails/normal/b9cba313fffa18491974db396c3d8e68.png': No such file or directory Mar 01 12:41:33 hostname eog[16017]: Failed to open file '/home/username/.cache/thumbnails/normal/5cde55cf788db2b1a91c1767e6b5b769.png': No such file or directory Mar 01 12:41:34 hostname org.gnome.Nautilus[1227]: Duplicate property or field node Mar 01 12:41:34 hostname eog[16017]: Failed to open file '/home/username/.cache/thumbnails/normal/90613b908f88122f814997b4acc88db8.png': No such file or directory Mar 01 12:41:35 hostname eog[16017]: Failed to open file '/home/username/.cache/thumbnails/normal/0acba2da5dcbeecabb0817da154970d4.png': No such file or directory Mar 01 12:41:36 hostname eog[16017]: Failed to open file '/home/username/.cache/thumbnails/normal/4680560503c46ab5f17d4ef2d97a96ee.png': No such file or directory Mar 01 12:41:37 hostname eog[16017]: Failed to open file '/home/username/.cache/thumbnails/normal/c1190b4097b22d1fe48414a5c097e838.png': No such file or directory Mar 01 12:41:39 hostname eog[16017]: Failed to open file '/home/username/.cache/thumbnails/normal/764408fe922e3a8ba899f39abaf1ef44.png': No such file or directory Mar 01 12:41:41 hostname eog[16017]: Failed to open file '/home/username/.cache/thumbnails/normal/e91d7effc8edd7546cead4d94baa2b3f.png': No such file or directory Mar 01 12:41:42 hostname eog[16017]: Failed to open file '/home/username/.cache/thumbnails/normal/5fd4d232b949ffb1424b9600cc9b8f78.png': No such file or directory Mar 01 12:41:43 hostname eog[16017]: Failed to open file '/home/username/.cache/thumbnails/normal/44cadf616779958f66126919001b70c2.png': No such file or directory Mar 01 12:41:44 hostname eog[16017]: Failed to open file '/home/username/.cache/thumbnails/normal/80669861f9aa5aea3fe60cb442f453cc.png': No such file or directory Mar 01 12:41:49 hostname org.gnome.Nautilus[1227]: Duplicate property or field node Mar 01 12:41:56 hostname nautilus[6412]: gtk_widget_get_mapped: assertion 'GTK_IS_WIDGET (widget)' failed Mar 01 12:41:56 hostname nautilus[6412]: gdk_window_is_visible: assertion 'GDK_IS_WINDOW (window)' failed Mar 01 12:41:56 hostname nautilus[6412]: gdk_window_show_internal: assertion 'GDK_IS_WINDOW (window)' failed Mar 01 12:41:56 hostname nautilus[6412]: gtk_widget_set_opacity: assertion 'GTK_IS_WIDGET (widget)' failed Mar 01 12:41:56 hostname nautilus[6412]: gtk_widget_queue_draw: assertion 'GTK_IS_WIDGET (widget)' failed Mar 01 12:41:58 hostname nautilus[6412]: gtk_widget_get_mapped: assertion 'GTK_IS_WIDGET (widget)' failed Mar 01 12:41:58 hostname nautilus[6412]: gdk_window_is_visible: assertion 'GDK_IS_WINDOW (window)' failed Mar 01 12:41:58 hostname nautilus[6412]: gtk_widget_set_opacity: assertion 'GTK_IS_WIDGET (widget)' failed Mar 01 12:41:58 hostname nautilus[6412]: gtk_widget_queue_draw: assertion 'GTK_IS_WIDGET (widget)' failed Mar 01 12:45:33 hostname nautilus[6412]: g_key_file_load_from_file: assertion 'file != NULL' failed Mar 01 12:45:33 hostname nautilus[6412]: Could not establish a connection to Tracker: Failed to load SPARQL backend: Key file does not have group “DomainOntology” Mar 01 12:45:33 hostname nautilus[6412]: g_key_file_load_from_file: assertion 'file != NULL' failed Mar 01 12:45:33 hostname nautilus[6412]: Could not establish a connection to Tracker: Failed to load SPARQL backend: Key file does not have group “DomainOntology” Mar 01 12:45:34 hostname nautilus[6412]: g_key_file_load_from_file: assertion 'file != NULL' failed Mar 01 12:45:34 hostname nautilus[6412]: Could not establish a connection to Tracker: Failed to load SPARQL backend: Key file does not have group “DomainOntology” Mar 01 12:45:34 hostname nautilus[6412]: g_key_file_load_from_file: assertion 'file != NULL' failed Mar 01 12:45:34 hostname nautilus[6412]: Could not establish a connection to Tracker: Failed to load SPARQL backend: Key file does not have group “DomainOntology” Mar 01 12:45:34 hostname nautilus[6412]: g_key_file_load_from_file: assertion 'file != NULL' failed Mar 01 12:45:34 hostname nautilus[6412]: Could not establish a connection to Tracker: Failed to load SPARQL backend: Key file does not have group “DomainOntology” Mar 01 12:45:35 hostname nautilus[6412]: g_key_file_load_from_file: assertion 'file != NULL' failed Mar 01 12:45:35 hostname nautilus[6412]: Could not establish a connection to Tracker: Failed to load SPARQL backend: Key file does not have group “DomainOntology” Mar 01 12:45:35 hostname nautilus[6412]: g_key_file_load_from_file: assertion 'file != NULL' failed Mar 01 12:45:35 hostname nautilus[6412]: Could not establish a connection to Tracker: Failed to load SPARQL backend: Key file does not have group “DomainOntology” Mar 01 12:45:35 hostname nautilus[6412]: g_key_file_load_from_file: assertion 'file != NULL' failed Mar 01 12:45:35 hostname nautilus[6412]: Could not establish a connection to Tracker: Failed to load SPARQL backend: Key file does not have group “DomainOntology” Mar 01 12:45:35 hostname nautilus[6412]: g_key_file_load_from_file: assertion 'file != NULL' failed Mar 01 12:45:35 hostname nautilus[6412]: Could not establish a connection to Tracker: Failed to load SPARQL backend: Key file does not have group “DomainOntology” Mar 01 12:45:35 hostname nautilus[6412]: g_key_file_load_from_file: assertion 'file != NULL' failed Mar 01 12:45:35 hostname nautilus[6412]: Could not establish a connection to Tracker: Failed to load SPARQL backend: Key file does not have group “DomainOntology” Mar 01 12:45:36 hostname nautilus[6412]: g_key_file_load_from_file: assertion 'file != NULL' failed Mar 01 12:45:36 hostname nautilus[6412]: Could not establish a connection to Tracker: Failed to load SPARQL backend: Key file does not have group “DomainOntology” Mar 01 12:45:36 hostname nautilus[6412]: g_key_file_load_from_file: assertion 'file != NULL' failed Mar 01 12:45:36 hostname nautilus[6412]: Could not establish a connection to Tracker: Failed to load SPARQL backend: Key file does not have group “DomainOntology” Mar 01 13:03:27 hostname nautilus[6412]: gtk_revealer_set_reveal_child: assertion 'GTK_IS_REVEALER (revealer)' failed Mar 01 13:03:42 hostname thunderbird[16301]: Failed to measure available space: The specified location is not supported Mar 01 13:10:36 hostname gnome-shell[1310]: Failed to apply DRM plane transform 0: Invalid argument Mar 01 13:10:36 hostname gnome-shell[1310]: Failed to apply DRM plane transform 0: Invalid argument Mar 01 13:10:36 hostname gnome-shell[1310]: Failed to apply DRM plane transform 0: Invalid argument Mar 01 13:10:37 hostname gnome-shell[1310]: st_widget_get_theme_node called on the widget [0x5560a71b36a0 StButton.app-well-app running1 ("2")] which is not in the stage. Mar 01 13:10:37 hostname gnome-shell[1310]: st_widget_get_theme_node called on the widget [0x5560a71b6650 StWidget:last-child first-child ("2")] which is not in the stage. Mar 01 13:10:37 hostname gnome-shell[1310]: st_widget_get_theme_node called on the widget [0x5560a71b36a0 StButton.app-well-app running1 ("2")] which is not in the stage. Mar 01 13:10:37 hostname gnome-shell[1310]: st_widget_get_theme_node called on the widget [0x5560a71b6650 StWidget:last-child first-child ("2")] which is not in the stage. Mar 01 13:10:37 hostname gnome-shell[1310]: st_widget_get_theme_node called on the widget [0x5560a71b4d20 StWidget.app-well-app-running-dot:first-child] which is not in the stage. Mar 01 13:10:37 hostname gnome-shell[1310]: st_widget_get_theme_node called on the widget [0x5560a71b36a0 StButton.app-well-app running1 ("2")] which is not in the stage. Mar 01 13:10:37 hostname gnome-shell[1310]: st_widget_get_theme_node called on the widget [0x5560a71b6650 StWidget:last-child first-child ("2")] which is not in the stage. Mar 01 13:10:37 hostname gnome-shell[1310]: st_widget_get_theme_node called on the widget [0x5560a71b6f20 StBin.overview-icon] which is not in the stage. Mar 01 13:10:37 hostname gnome-shell[1310]: st_widget_get_theme_node called on the widget [0x5560a71b36a0 StButton.app-well-app running1 ("2")] which is not in the stage. Mar 01 13:10:37 hostname gnome-shell[1310]: st_widget_get_theme_node called on the widget [0x5560a71b6650 StWidget:last-child first-child ("2")] which is not in the stage. Mar 01 13:10:37 hostname gnome-shell[1310]: st_widget_get_theme_node called on the widget [0x5560a71b6f20 StBin.overview-icon] which is not in the stage. Mar 01 13:10:37 hostname gnome-shell[1310]: st_widget_get_theme_node called on the widget [0x5560a71b8050 ShellGenericContainer:last-child first-child] which is not in the stage. Mar 01 13:10:37 hostname gnome-shell[1310]: st_widget_get_theme_node called on the widget [0x5560a71b36a0 StButton.app-well-app running1 ("2")] which is not in the stage. Mar 01 13:10:37 hostname gnome-shell[1310]: st_widget_get_theme_node called on the widget [0x5560a71b6650 StWidget:last-child first-child ("2")] which is not in the stage. Mar 01 13:10:37 hostname gnome-shell[1310]: st_widget_get_theme_node called on the widget [0x5560a71b6f20 StBin.overview-icon] which is not in the stage. Mar 01 13:10:37 hostname gnome-shell[1310]: st_widget_get_theme_node called on the widget [0x5560a71b8050 ShellGenericContainer:last-child first-child] which is not in the stage. Mar 01 13:10:37 hostname gnome-shell[1310]: st_widget_get_theme_node called on the widget [0x5560a71b8f00 StBin:last-child first-child] which is not in the stage. Mar 01 13:10:37 hostname gnome-shell[1310]: st_widget_get_theme_node called on the widget [0x5560a71b36a0 StButton.app-well-app running1 ("2")] which is not in the stage. Mar 01 13:10:37 hostname gnome-shell[1310]: st_widget_get_theme_node called on the widget [0x5560a71b6650 StWidget:last-child first-child ("2")] which is not in the stage. Mar 01 13:10:37 hostname gnome-shell[1310]: st_widget_get_theme_node called on the widget [0x5560a71bb8f0 StDrawingArea] which is not in the stage. Mar 01 13:11:16 hostname gnome-shell[1310]: Failed to apply DRM plane transform 0: Invalid argument Mar 01 13:11:16 hostname gnome-shell[1310]: Failed to apply DRM plane transform 0: Invalid argument Mar 01 13:11:16 hostname gnome-shell[1310]: Failed to apply DRM plane transform 0: Invalid argument Mar 01 13:11:17 hostname gnome-shell[1310]: st_widget_get_theme_node called on the widget [0x5560a7915a50 StButton.app-well-app running1 ("2")] which is not in the stage. Mar 01 13:11:17 hostname gnome-shell[1310]: st_widget_get_theme_node called on the widget [0x5560a7918440 StWidget:last-child first-child ("2")] which is not in the stage. Mar 01 13:11:17 hostname gnome-shell[1310]: st_widget_get_theme_node called on the widget [0x5560a7915a50 StButton.app-well-app running1 ("2")] which is not in the stage. Mar 01 13:11:17 hostname gnome-shell[1310]: st_widget_get_theme_node called on the widget [0x5560a7918440 StWidget:last-child first-child ("2")] which is not in the stage. Mar 01 13:11:17 hostname gnome-shell[1310]: st_widget_get_theme_node called on the widget [0x5560a79168d0 StWidget.app-well-app-running-dot:first-child] which is not in the stage. Mar 01 13:11:17 hostname gnome-shell[1310]: st_widget_get_theme_node called on the widget [0x5560a7915a50 StButton.app-well-app running1 ("2")] which is not in the stage. Mar 01 13:11:17 hostname gnome-shell[1310]: st_widget_get_theme_node called on the widget [0x5560a7918440 StWidget:last-child first-child ("2")] which is not in the stage. Mar 01 13:11:17 hostname gnome-shell[1310]: st_widget_get_theme_node called on the widget [0x5560a7919010 StBin.overview-icon] which is not in the stage. Mar 01 13:11:17 hostname gnome-shell[1310]: st_widget_get_theme_node called on the widget [0x5560a7915a50 StButton.app-well-app running1 ("2")] which is not in the stage. Mar 01 13:11:17 hostname gnome-shell[1310]: st_widget_get_theme_node called on the widget [0x5560a7918440 StWidget:last-child first-child ("2")] which is not in the stage. Mar 01 13:11:17 hostname gnome-shell[1310]: st_widget_get_theme_node called on the widget [0x5560a7919010 StBin.overview-icon] which is not in the stage. Mar 01 13:11:17 hostname gnome-shell[1310]: st_widget_get_theme_node called on the widget [0x5560a7919c50 ShellGenericContainer:last-child first-child] which is not in the stage. Mar 01 13:11:17 hostname gnome-shell[1310]: st_widget_get_theme_node called on the widget [0x5560a7915a50 StButton.app-well-app running1 ("2")] which is not in the stage. Mar 01 13:11:17 hostname gnome-shell[1310]: st_widget_get_theme_node called on the widget [0x5560a7918440 StWidget:last-child first-child ("2")] which is not in the stage. Mar 01 13:11:17 hostname gnome-shell[1310]: st_widget_get_theme_node called on the widget [0x5560a7919010 StBin.overview-icon] which is not in the stage. Mar 01 13:11:17 hostname gnome-shell[1310]: st_widget_get_theme_node called on the widget [0x5560a7919c50 ShellGenericContainer:last-child first-child] which is not in the stage. Mar 01 13:11:17 hostname gnome-shell[1310]: st_widget_get_theme_node called on the widget [0x5560a791b430 StBin:last-child first-child] which is not in the stage. Mar 01 13:11:17 hostname gnome-shell[1310]: st_widget_get_theme_node called on the widget [0x5560a7915a50 StButton.app-well-app running1 ("2")] which is not in the stage. Mar 01 13:11:17 hostname gnome-shell[1310]: st_widget_get_theme_node called on the widget [0x5560a7918440 StWidget:last-child first-child ("2")] which is not in the stage. Mar 01 13:11:17 hostname gnome-shell[1310]: st_widget_get_theme_node called on the widget [0x5560a791de60 StDrawingArea] which is not in the stage. Mar 01 13:11:39 hostname gnome-shell[1310]: Failed to apply DRM plane transform 0: Invalid argument Mar 01 13:11:39 hostname gnome-shell[1310]: Failed to apply DRM plane transform 0: Invalid argument Mar 01 13:11:39 hostname gnome-shell[1310]: Failed to apply DRM plane transform 0: Invalid argument Mar 01 13:11:39 hostname gnome-shell[1310]: st_widget_get_theme_node called on the widget [0x5560a7b0ec80 StButton.app-well-app running1 ("2")] which is not in the stage. Mar 01 13:11:39 hostname gnome-shell[1310]: st_widget_get_theme_node called on the widget [0x5560a7b10680 StWidget:last-child first-child ("2")] which is not in the stage. Mar 01 13:11:39 hostname gnome-shell[1310]: st_widget_get_theme_node called on the widget [0x5560a7b0ec80 StButton.app-well-app running1 ("2")] which is not in the stage. Mar 01 13:11:39 hostname gnome-shell[1310]: st_widget_get_theme_node called on the widget [0x5560a7b10680 StWidget:last-child first-child ("2")] which is not in the stage. Mar 01 13:11:39 hostname gnome-shell[1310]: st_widget_get_theme_node called on the widget [0x5560a7b0f850 StWidget.app-well-app-running-dot:first-child] which is not in the stage. Mar 01 13:11:39 hostname gnome-shell[1310]: st_widget_get_theme_node called on the widget [0x5560a7b0ec80 StButton.app-well-app running1 ("2")] which is not in the stage. Mar 01 13:11:39 hostname gnome-shell[1310]: st_widget_get_theme_node called on the widget [0x5560a7b10680 StWidget:last-child first-child ("2")] which is not in the stage. Mar 01 13:11:39 hostname gnome-shell[1310]: st_widget_get_theme_node called on the widget [0x5560a7b112c0 StBin.overview-icon] which is not in the stage. Mar 01 13:11:39 hostname gnome-shell[1310]: st_widget_get_theme_node called on the widget [0x5560a7b0ec80 StButton.app-well-app running1 ("2")] which is not in the stage. Mar 01 13:11:39 hostname gnome-shell[1310]: st_widget_get_theme_node called on the widget [0x5560a7b10680 StWidget:last-child first-child ("2")] which is not in the stage. Mar 01 13:11:39 hostname gnome-shell[1310]: st_widget_get_theme_node called on the widget [0x5560a7b112c0 StBin.overview-icon] which is not in the stage. Mar 01 13:11:39 hostname gnome-shell[1310]: st_widget_get_theme_node called on the widget [0x5560a7b11f00 ShellGenericContainer:last-child first-child] which is not in the stage. Mar 01 13:11:39 hostname gnome-shell[1310]: st_widget_get_theme_node called on the widget [0x5560a7b0ec80 StButton.app-well-app running1 ("2")] which is not in the stage. Mar 01 13:11:39 hostname gnome-shell[1310]: st_widget_get_theme_node called on the widget [0x5560a7b10680 StWidget:last-child first-child ("2")] which is not in the stage. Mar 01 13:11:39 hostname gnome-shell[1310]: st_widget_get_theme_node called on the widget [0x5560a7b112c0 StBin.overview-icon] which is not in the stage. Mar 01 13:11:39 hostname gnome-shell[1310]: st_widget_get_theme_node called on the widget [0x5560a7b11f00 ShellGenericContainer:last-child first-child] which is not in the stage. Mar 01 13:11:39 hostname gnome-shell[1310]: st_widget_get_theme_node called on the widget [0x5560a7b12ea0 StBin:last-child first-child] which is not in the stage. Mar 01 13:11:39 hostname gnome-shell[1310]: st_widget_get_theme_node called on the widget [0x5560a7b0ec80 StButton.app-well-app running1 ("2")] which is not in the stage. Mar 01 13:11:39 hostname gnome-shell[1310]: st_widget_get_theme_node called on the widget [0x5560a7b10680 StWidget:last-child first-child ("2")] which is not in the stage. Mar 01 13:11:39 hostname gnome-shell[1310]: st_widget_get_theme_node called on the widget [0x5560a7b15900 StDrawingArea] which is not in the stage. Mar 01 13:14:45 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (10476258) is greater than comparison timestamp (10476249). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 01 13:14:45 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2200010 (17.10 gnom) appears to be one of the offending windows with a timestamp of 10476258. Working around... Mar 01 13:14:45 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (10476288) is greater than comparison timestamp (10476280). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 01 13:14:45 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2200010 (17.10 gnom) appears to be one of the offending windows with a timestamp of 10476288. Working around... Mar 01 13:14:45 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (10476318) is greater than comparison timestamp (10476313). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 01 13:14:45 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2200010 (17.10 gnom) appears to be one of the offending windows with a timestamp of 10476318. Working around... Mar 01 13:14:45 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (10476348) is greater than comparison timestamp (10476343). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 01 13:14:45 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2200010 (17.10 gnom) appears to be one of the offending windows with a timestamp of 10476348. Working around... Mar 01 13:14:45 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (10476408) is greater than comparison timestamp (10476405). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 01 13:14:45 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2200010 (17.10 gnom) appears to be one of the offending windows with a timestamp of 10476408. Working around... Mar 01 13:14:45 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (10476438) is greater than comparison timestamp (10476435). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 01 13:14:45 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2200010 (17.10 gnom) appears to be one of the offending windows with a timestamp of 10476438. Working around... Mar 01 13:18:13 hostname gnome-software[1599]: no app for changed ubuntu-appindicators@ubuntu.com Mar 01 13:18:13 hostname gnome-software[1599]: no app for changed ubuntu-dock@ubuntu.com Mar 01 14:33:27 hostname gnome-software[1599]: no app for changed ubuntu-dock@ubuntu.com Mar 01 14:33:27 hostname gnome-software[1599]: no app for changed ubuntu-appindicators@ubuntu.com Mar 01 14:58:59 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (16731048) is greater than comparison timestamp (16731038). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 01 14:58:59 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2200010 (thunderbir) appears to be one of the offending windows with a timestamp of 16731048. Working around... Mar 01 15:03:47 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (17018925) is greater than comparison timestamp (17018918). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 01 15:03:47 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2200010 (Ask a Ques) appears to be one of the offending windows with a timestamp of 17018925. Working around... Mar 01 15:04:53 hostname Web Content[1823]: Unable to open /var/lib/snapd/desktop/dconf/profile/user: Permission denied Mar 01 15:16:40 hostname nautilus[6412]: g_key_file_load_from_file: assertion 'file != NULL' failed Mar 01 15:16:40 hostname nautilus[6412]: Could not establish a connection to Tracker: Failed to load SPARQL backend: Key file does not have group “DomainOntology” Mar 01 15:16:41 hostname nautilus[6412]: g_key_file_load_from_file: assertion 'file != NULL' failed Mar 01 15:16:41 hostname nautilus[6412]: Could not establish a connection to Tracker: Failed to load SPARQL backend: Key file does not have group “DomainOntology” Mar 01 15:16:44 hostname org.gnome.Shell.desktop[1310]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2c00041 (Open Datab) Mar 01 15:16:50 hostname org.gnome.Shell.desktop[1310]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2c00041 (Open Datab) Mar 01 15:16:51 hostname org.gnome.Shell.desktop[1310]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2c00017 (DalePwDb.k) Mar 01 15:16:56 hostname org.gnome.Shell.desktop[1310]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2c00260 (Add Entry) Mar 01 15:16:56 hostname org.gnome.Shell.desktop[1310]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2c00260 (Add Entry) Mar 01 15:17:15 hostname org.gnome.Shell.desktop[1310]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2c00017 (DalePwDb.k) Mar 01 15:17:18 hostname org.gnome.Shell.desktop[1310]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2c0058e (KeePass - ) Mar 01 15:17:18 hostname org.gnome.Shell.desktop[1310]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2c0058e (KeePass - ) Mar 01 15:17:28 hostname org.gnome.Shell.desktop[1310]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2c00017 (DalePwDb.k) Mar 01 15:17:28 hostname org.gnome.Shell.desktop[1310]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2c00726 (KeePass) Mar 01 15:17:28 hostname org.gnome.Shell.desktop[1310]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2c00726 (KeePass) Mar 01 15:17:36 hostname org.gnome.Shell.desktop[1310]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2c00017 (DalePwDb.k) Mar 01 15:17:40 hostname org.gnome.Shell.desktop[1310]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2c00924 (KeePass) Mar 01 15:17:40 hostname org.gnome.Shell.desktop[1310]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2c00924 (KeePass) Mar 01 15:19:00 hostname gnome-terminal-[1661]: Allocating size to GtkBox 0x5647a66bcf70 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Mar 01 15:19:00 hostname gnome-terminal-[1661]: Allocating size to GtkBox 0x5647a66bcf70 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Mar 01 15:19:00 hostname gnome-terminal-[1661]: Allocating size to GtkBox 0x5647a66bcf70 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Mar 01 15:19:00 hostname gnome-terminal-[1661]: Allocating size to GtkBox 0x5647a66bcf70 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Mar 01 15:19:00 hostname gnome-terminal-[1661]: Allocating size to GtkBox 0x5647a66bcf70 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Mar 01 15:19:00 hostname gnome-terminal-[1661]: Allocating size to GtkBox 0x5647a66bcf70 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Mar 01 15:19:00 hostname gnome-terminal-[1661]: Allocating size to GtkBox 0x5647a66bcf70 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Mar 01 15:19:00 hostname gnome-terminal-[1661]: Allocating size to GtkBox 0x5647a66bcf70 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Mar 01 15:19:01 hostname gnome-terminal-[1661]: Allocating size to GtkBox 0x5647a66bcf70 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Mar 01 15:19:01 hostname gnome-terminal-[1661]: Allocating size to GtkBox 0x5647a66bcf70 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Mar 01 15:19:01 hostname gnome-terminal-[1661]: Allocating size to GtkBox 0x5647a66bcf70 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Mar 01 15:19:01 hostname gnome-terminal-[1661]: Allocating size to GtkBox 0x5647a66bcf70 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Mar 01 15:19:01 hostname gnome-terminal-[1661]: Allocating size to GtkBox 0x5647a66bcf70 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Mar 01 15:19:27 hostname org.gnome.Shell.desktop[1310]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2c00017 (DalePwDb.k) Mar 01 15:19:37 hostname org.gnome.Shell.desktop[1310]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2c00ad5 (Save Datab) Mar 01 15:19:37 hostname org.gnome.Shell.desktop[1310]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2c00ad5 (Save Datab) Mar 01 15:19:47 hostname org.gnome.Shell.desktop[1310]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2c00017 (DalePwDb.k) Mar 01 15:24:08 hostname gnome-terminal-[1661]: Allocating size to GtkBox 0x5647a66bc470 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Mar 01 15:24:08 hostname gnome-terminal-[1661]: Allocating size to GtkBox 0x5647a66bc470 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Mar 01 15:24:10 hostname gnome-terminal-[1661]: Allocating size to GtkBox 0x5647a66bc470 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Mar 01 15:24:10 hostname gnome-terminal-[1661]: Allocating size to GtkBox 0x5647a66bc470 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Mar 01 15:26:40 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (18391754) is greater than comparison timestamp (18391753). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 01 15:26:40 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2200010 (virtualbox) appears to be one of the offending windows with a timestamp of 18391754. Working around... Mar 01 15:28:13 hostname systemd[1]: avahi-daemon.socket: Socket unit configuration has changed while unit has been running, no open socket file descriptor left. The socket unit is not functional until restarted. Mar 01 15:28:13 hostname systemd[1]: avahi-daemon.socket: Socket unit configuration has changed while unit has been running, no open socket file descriptor left. The socket unit is not functional until restarted. Mar 01 15:28:13 hostname systemd[1]: avahi-daemon.socket: Socket unit configuration has changed while unit has been running, no open socket file descriptor left. The socket unit is not functional until restarted. Mar 01 15:28:15 hostname gnome-software[1599]: failed to rescan: Failed to parse /usr/share/applications/virtualbox.desktop.dpkg-new file: cannot process file of type text/plain Mar 01 15:28:16 hostname gnome-software[1599]: failed to rescan: Failed to parse /usr/share/applications/virtualbox.desktop file: cannot process file of type application/x-desktop Mar 01 15:28:17 hostname systemd[1]: avahi-daemon.socket: Socket unit configuration has changed while unit has been running, no open socket file descriptor left. The socket unit is not functional until restarted. Mar 01 15:28:21 hostname systemd[1]: avahi-daemon.socket: Socket unit configuration has changed while unit has been running, no open socket file descriptor left. The socket unit is not functional until restarted. Mar 01 15:28:21 hostname systemd[1]: avahi-daemon.socket: Socket unit configuration has changed while unit has been running, no open socket file descriptor left. The socket unit is not functional until restarted. Mar 01 15:28:22 hostname systemd[1]: avahi-daemon.socket: Socket unit configuration has changed while unit has been running, no open socket file descriptor left. The socket unit is not functional until restarted. Mar 01 15:28:22 hostname systemd[1]: avahi-daemon.socket: Socket unit configuration has changed while unit has been running, no open socket file descriptor left. The socket unit is not functional until restarted. Mar 01 15:28:22 hostname systemd[1]: avahi-daemon.socket: Socket unit configuration has changed while unit has been running, no open socket file descriptor left. The socket unit is not functional until restarted. Mar 01 15:28:22 hostname kernel: systemd: 49 output lines suppressed due to ratelimiting Mar 01 15:28:22 hostname systemd[1]: avahi-daemon.socket: Socket unit configuration has changed while unit has been running, no open socket file descriptor left. The socket unit is not functional until restarted. Mar 01 15:28:22 hostname systemd[1]: avahi-daemon.socket: Socket unit configuration has changed while unit has been running, no open socket file descriptor left. The socket unit is not functional until restarted. Mar 01 15:28:23 hostname systemd[1]: avahi-daemon.socket: Socket unit configuration has changed while unit has been running, no open socket file descriptor left. The socket unit is not functional until restarted. Mar 01 15:28:23 hostname systemd[1]: avahi-daemon.socket: Socket unit configuration has changed while unit has been running, no open socket file descriptor left. The socket unit is not functional until restarted. Mar 01 15:28:23 hostname systemd[1]: avahi-daemon.socket: Socket unit configuration has changed while unit has been running, no open socket file descriptor left. The socket unit is not functional until restarted. Mar 01 15:28:23 hostname systemd[1]: avahi-daemon.socket: Socket unit configuration has changed while unit has been running, no open socket file descriptor left. The socket unit is not functional until restarted. Mar 01 15:28:23 hostname systemd[1]: avahi-daemon.socket: Socket unit configuration has changed while unit has been running, no open socket file descriptor left. The socket unit is not functional until restarted. Mar 01 15:28:23 hostname systemd[1]: avahi-daemon.socket: Socket unit configuration has changed while unit has been running, no open socket file descriptor left. The socket unit is not functional until restarted. Mar 01 15:28:23 hostname systemd[1]: avahi-daemon.socket: Socket unit configuration has changed while unit has been running, no open socket file descriptor left. The socket unit is not functional until restarted. Mar 01 15:28:23 hostname systemd[1]: avahi-daemon.socket: Socket unit configuration has changed while unit has been running, no open socket file descriptor left. The socket unit is not functional until restarted. Mar 01 15:28:24 hostname systemd[1]: avahi-daemon.socket: Socket unit configuration has changed while unit has been running, no open socket file descriptor left. The socket unit is not functional until restarted. Mar 01 15:28:24 hostname systemd[1]: avahi-daemon.socket: Socket unit configuration has changed while unit has been running, no open socket file descriptor left. The socket unit is not functional until restarted. Mar 01 15:28:24 hostname systemd[1]: avahi-daemon.socket: Socket unit configuration has changed while unit has been running, no open socket file descriptor left. The socket unit is not functional until restarted. Mar 01 15:28:24 hostname systemd[1]: avahi-daemon.socket: Socket unit configuration has changed while unit has been running, no open socket file descriptor left. The socket unit is not functional until restarted. Mar 01 15:28:24 hostname systemd[1]: avahi-daemon.socket: Socket unit configuration has changed while unit has been running, no open socket file descriptor left. The socket unit is not functional until restarted. Mar 01 15:28:36 hostname kernel: vboxdrv: loading out-of-tree module taints kernel. Mar 01 15:28:36 hostname kernel: VBoxNetFlt: Successfully started. Mar 01 15:28:36 hostname kernel: VBoxNetAdp: Successfully started. Mar 01 15:28:36 hostname kernel: VBoxPciLinuxInit Mar 01 15:29:20 hostname gnome-terminal-[1661]: Allocating size to GtkBox 0x5647a66bc470 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Mar 01 15:29:20 hostname gnome-terminal-[1661]: Allocating size to GtkBox 0x5647a66bc470 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Mar 01 15:29:22 hostname gnome-terminal-[1661]: Allocating size to GtkBox 0x5647a66bc470 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Mar 01 15:29:22 hostname gnome-terminal-[1661]: Allocating size to GtkBox 0x5647a66bc470 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Mar 01 15:30:41 hostname gnome-shell[1310]: Some code accessed the property 'refreshPropertyOnProxy' on the module 'util'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway. Mar 01 15:31:41 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (18692967) is greater than comparison timestamp (18692957). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 01 15:31:41 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2200010 (virtualbox) appears to be one of the offending windows with a timestamp of 18692967. Working around... Mar 01 15:31:41 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (18692997) is greater than comparison timestamp (18692988). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 01 15:31:41 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2200010 (virtualbox) appears to be one of the offending windows with a timestamp of 18692997. Working around... Mar 01 15:33:42 hostname nautilus[6412]: g_key_file_load_from_file: assertion 'file != NULL' failed Mar 01 15:33:42 hostname nautilus[6412]: Could not establish a connection to Tracker: Failed to load SPARQL backend: Key file does not have group “DomainOntology” Mar 01 15:33:42 hostname nautilus[6412]: g_key_file_load_from_file: assertion 'file != NULL' failed Mar 01 15:33:42 hostname nautilus[6412]: Could not establish a connection to Tracker: Failed to load SPARQL backend: Key file does not have group “DomainOntology” Mar 01 15:33:42 hostname nautilus[6412]: g_key_file_load_from_file: assertion 'file != NULL' failed Mar 01 15:33:42 hostname nautilus[6412]: Could not establish a connection to Tracker: Failed to load SPARQL backend: Key file does not have group “DomainOntology” Mar 01 15:33:43 hostname nautilus[6412]: g_key_file_load_from_file: assertion 'file != NULL' failed Mar 01 15:33:43 hostname nautilus[6412]: Could not establish a connection to Tracker: Failed to load SPARQL backend: Key file does not have group “DomainOntology” Mar 01 15:33:50 hostname nautilus[6412]: g_key_file_load_from_file: assertion 'file != NULL' failed Mar 01 15:33:50 hostname nautilus[6412]: Could not establish a connection to Tracker: Failed to load SPARQL backend: Key file does not have group “DomainOntology” Mar 01 15:33:50 hostname nautilus[6412]: g_key_file_load_from_file: assertion 'file != NULL' failed Mar 01 15:33:50 hostname nautilus[6412]: Could not establish a connection to Tracker: Failed to load SPARQL backend: Key file does not have group “DomainOntology” Mar 01 15:33:51 hostname nautilus[6412]: g_key_file_load_from_file: assertion 'file != NULL' failed Mar 01 15:33:51 hostname nautilus[6412]: Could not establish a connection to Tracker: Failed to load SPARQL backend: Key file does not have group “DomainOntology” Mar 01 15:34:27 hostname gnome-control-c[29911]: Failed fetch permissions from flatpak permission store: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.impl.portal.PermissionStore was not provided by any .service files Mar 01 15:34:27 hostname geoclue[29939]: Failed to connect to avahi service: Daemon not running Mar 01 15:34:28 hostname gsd-power[1429]: gsd_power_backlight_abs_to_percentage: assertion 'max > min' failed Mar 01 15:35:22 hostname nautilus[6412]: g_key_file_load_from_file: assertion 'file != NULL' failed Mar 01 15:35:22 hostname nautilus[6412]: Could not establish a connection to Tracker: Failed to load SPARQL backend: Key file does not have group “DomainOntology” Mar 01 15:35:23 hostname nautilus[6412]: g_key_file_load_from_file: assertion 'file != NULL' failed Mar 01 15:35:23 hostname nautilus[6412]: Could not establish a connection to Tracker: Failed to load SPARQL backend: Key file does not have group “DomainOntology” Mar 01 15:35:23 hostname nautilus[6412]: g_key_file_load_from_file: assertion 'file != NULL' failed Mar 01 15:35:23 hostname nautilus[6412]: Could not establish a connection to Tracker: Failed to load SPARQL backend: Key file does not have group “DomainOntology” Mar 01 15:35:23 hostname nautilus[6412]: g_key_file_load_from_file: assertion 'file != NULL' failed Mar 01 15:35:23 hostname nautilus[6412]: Could not establish a connection to Tracker: Failed to load SPARQL backend: Key file does not have group “DomainOntology” Mar 01 15:35:24 hostname gnome-tweak-too[30070]: Failed to measure available space: The specified location is not supported Mar 01 15:35:24 hostname gnome-tweak-too[30070]: Failed to measure available space: The specified location is not supported Mar 01 15:36:28 hostname nautilus[6412]: g_key_file_load_from_file: assertion 'file != NULL' failed Mar 01 15:36:28 hostname nautilus[6412]: Could not establish a connection to Tracker: Failed to load SPARQL backend: Key file does not have group “DomainOntology” Mar 01 15:36:28 hostname nautilus[6412]: g_key_file_load_from_file: assertion 'file != NULL' failed Mar 01 15:36:28 hostname nautilus[6412]: Could not establish a connection to Tracker: Failed to load SPARQL backend: Key file does not have group “DomainOntology” Mar 01 15:36:46 hostname VirtualBox[30170]: Failed to measure available space: The specified location is not supported Mar 01 15:37:09 hostname kernel: SUPR0GipMap: fGetGipCpu=0xb Mar 01 15:37:09 hostname org.gnome.Shell.desktop[1310]: syntax error: line 1 of stdin Mar 01 15:37:09 hostname org.gnome.Shell.desktop[1310]: Errors encountered in stdin; not compiled. Mar 01 15:37:09 hostname kernel: vboxdrv: 0000000000000000 VMMR0.r0 Mar 01 15:39:27 hostname org.gnome.Shell.desktop[1310]: syntax error: line 1 of stdin Mar 01 15:39:27 hostname org.gnome.Shell.desktop[1310]: Errors encountered in stdin; not compiled. Mar 01 15:39:27 hostname kernel: vboxdrv: 0000000000000000 VMMR0.r0 Mar 01 15:39:27 hostname kernel: vboxdrv: 0000000000000000 VBoxDDR0.r0 Mar 01 15:39:27 hostname kernel: vboxdrv: 0000000000000000 VBoxEhciR0.r0 Mar 01 15:41:41 hostname kernel: CIFS VFS: Server moortgat has not responded in 120 seconds. Reconnecting... Mar 01 15:41:41 hostname kernel: CIFS VFS: Free previous auth_key.response = ffff9bd56bfcbf00 Mar 01 15:46:56 hostname gnome-software[1599]: no app for changed ubuntu-appindicators@ubuntu.com Mar 01 15:46:56 hostname gnome-software[1599]: no app for changed ubuntu-dock@ubuntu.com Mar 01 15:51:37 hostname gnome-software[1599]: no app for changed ubuntu-dock@ubuntu.com Mar 01 15:51:37 hostname gnome-software[1599]: no app for changed ubuntu-appindicators@ubuntu.com Mar 01 15:51:55 hostname gnome-software[1599]: failed to rescan: Failed to parse /home/username/.local/share/applications/copyottell.desktop file: cannot process file of type application/x-desktop Mar 01 15:51:55 hostname gnome-software[1599]: failed to rescan: Failed to parse /home/username/.local/share/applications/examples.desktop file: cannot process file of type application/x-desktop Mar 01 15:51:55 hostname gnome-software[1599]: failed to rescan: Failed to parse /home/username/.local/share/applications/gnome-moortgat.desktop file: cannot process file of type application/x-desktop Mar 01 15:51:55 hostname gnome-software[1599]: failed to rescan: Failed to parse /home/username/.local/share/applications/huyghe-terminal.desktop file: cannot process file of type application/x-desktop Mar 01 15:51:55 hostname gnome-software[1599]: failed to rescan: Failed to parse /home/username/.local/share/applications/moortgat-terminal.desktop file: cannot process file of type application/x-desktop Mar 01 15:51:55 hostname gnome-software[1599]: failed to rescan: Failed to parse /home/username/.local/share/applications/ssh-cassomir.desktop file: cannot process file of type application/x-desktop Mar 01 15:51:55 hostname gnome-software[1599]: failed to rescan: Failed to parse /home/username/.local/share/applications/ssh-huyghe.desktop file: cannot process file of type application/x-desktop Mar 01 15:51:55 hostname gnome-software[1599]: failed to rescan: Failed to parse /home/username/.local/share/applications/ssh-moortgat.desktop file: cannot process file of type application/x-desktop Mar 01 15:51:55 hostname gnome-software[1599]: failed to rescan: Failed to parse /home/username/.local/share/applications/ssh-tape.desktop file: cannot process file of type application/x-desktop Mar 01 15:51:55 hostname gnome-software[1599]: failed to rescan: Failed to parse /home/username/.local/share/applications/ssh-tell.desktop file: cannot process file of type application/x-desktop Mar 01 15:51:55 hostname gnome-software[1599]: failed to rescan: Failed to parse /home/username/.local/share/applications/tape-terminal.desktop file: cannot process file of type application/x-desktop Mar 01 15:51:55 hostname gnome-software[1599]: failed to rescan: Failed to parse /home/username/.local/share/applications/tell-terminal.desktop file: cannot process file of type application/x-desktop Mar 01 15:54:19 hostname gnome-shell[1310]: Could not load a pixbuf from icon theme. This may indicate that pixbuf loaders or the mime database could not be found. Mar 01 15:54:20 hostname nautilus[6412]: g_key_file_load_from_file: assertion 'file != NULL' failed Mar 01 15:54:20 hostname nautilus[6412]: Could not establish a connection to Tracker: Failed to load SPARQL backend: Key file does not have group “DomainOntology” Mar 01 15:54:20 hostname nautilus[6412]: g_key_file_load_from_file: assertion 'file != NULL' failed Mar 01 15:54:20 hostname nautilus[6412]: Could not establish a connection to Tracker: Failed to load SPARQL backend: Key file does not have group “DomainOntology” Mar 01 15:55:22 hostname nautilus[6412]: g_key_file_load_from_file: assertion 'file != NULL' failed Mar 01 15:55:22 hostname nautilus[6412]: Could not establish a connection to Tracker: Failed to load SPARQL backend: Key file does not have group “DomainOntology” Mar 01 15:55:22 hostname nautilus[6412]: g_key_file_load_from_file: assertion 'file != NULL' failed Mar 01 15:55:22 hostname nautilus[6412]: Could not establish a connection to Tracker: Failed to load SPARQL backend: Key file does not have group “DomainOntology” Mar 01 15:55:22 hostname nautilus[6412]: g_key_file_load_from_file: assertion 'file != NULL' failed Mar 01 15:55:22 hostname nautilus[6412]: Could not establish a connection to Tracker: Failed to load SPARQL backend: Key file does not have group “DomainOntology” Mar 01 15:57:23 hostname Web Content[2007]: Unable to open /var/lib/snapd/desktop/dconf/profile/user: Permission denied Mar 01 16:00:10 hostname nautilus[6412]: g_key_file_load_from_file: assertion 'file != NULL' failed Mar 01 16:00:10 hostname nautilus[6412]: Could not establish a connection to Tracker: Failed to load SPARQL backend: Key file does not have group “DomainOntology” Mar 01 16:00:10 hostname nautilus[6412]: g_key_file_load_from_file: assertion 'file != NULL' failed Mar 01 16:00:10 hostname nautilus[6412]: Could not establish a connection to Tracker: Failed to load SPARQL backend: Key file does not have group “DomainOntology” Mar 01 16:00:10 hostname nautilus[6412]: g_key_file_load_from_file: assertion 'file != NULL' failed Mar 01 16:00:10 hostname nautilus[6412]: Could not establish a connection to Tracker: Failed to load SPARQL backend: Key file does not have group “DomainOntology” Mar 01 16:00:11 hostname nautilus[6412]: g_key_file_load_from_file: assertion 'file != NULL' failed Mar 01 16:00:11 hostname nautilus[6412]: Could not establish a connection to Tracker: Failed to load SPARQL backend: Key file does not have group “DomainOntology” Mar 01 16:00:12 hostname kernel: CIFS VFS: Autodisabling the use of server inode numbers on \\moortgat\username. This server doesn't seem to support them properly. Hardlinks will not be recognized on this mount. Consider mounting with the "noserverino" option to silence this message. Mar 01 16:02:33 hostname gnome-terminal-[1661]: Allocating size to GtkBox 0x5647a70dd2d0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Mar 01 16:02:33 hostname gnome-terminal-[1661]: Allocating size to GtkBox 0x5647a70dd2d0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Mar 01 16:02:33 hostname gnome-terminal-[1661]: Allocating size to GtkBox 0x5647a70dd2d0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Mar 01 16:02:33 hostname gnome-terminal-[1661]: Allocating size to GtkBox 0x5647a70dd2d0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Mar 01 16:02:33 hostname gnome-terminal-[1661]: Allocating size to GtkBox 0x5647a70dd2d0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Mar 01 16:02:33 hostname gnome-terminal-[1661]: Allocating size to GtkBox 0x5647a70dd2d0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Mar 01 16:02:33 hostname gnome-terminal-[1661]: Allocating size to GtkBox 0x5647a70dd2d0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Mar 01 16:02:33 hostname gnome-terminal-[1661]: Allocating size to GtkBox 0x5647a70dd2d0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Mar 01 16:02:33 hostname gnome-terminal-[1661]: Allocating size to GtkBox 0x5647a70dd2d0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Mar 01 16:02:33 hostname gnome-terminal-[1661]: Allocating size to GtkBox 0x5647a70dd2d0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Mar 01 16:02:33 hostname gnome-terminal-[1661]: Allocating size to GtkBox 0x5647a70dd2d0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Mar 01 16:02:33 hostname gnome-terminal-[1661]: Allocating size to GtkBox 0x5647a70dd2d0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Mar 01 16:02:33 hostname gnome-terminal-[1661]: Allocating size to GtkBox 0x5647a70dd2d0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Mar 01 16:02:34 hostname gnome-terminal-[1661]: Allocating size to GtkBox 0x5647a70dd2d0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Mar 01 16:02:34 hostname gnome-terminal-[1661]: Allocating size to GtkBox 0x5647a70dd2d0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Mar 01 16:02:34 hostname gnome-terminal-[1661]: Allocating size to GtkBox 0x5647a70dd2d0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Mar 01 16:02:34 hostname gnome-terminal-[1661]: Allocating size to GtkBox 0x5647a70dd2d0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Mar 01 16:02:34 hostname gnome-terminal-[1661]: Allocating size to GtkBox 0x5647a70dd2d0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Mar 01 16:06:00 hostname gnome-shell[1310]: Some code accessed the property 'WindowPreviewMenu' on the module 'windowPreview'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway. Mar 01 16:09:59 hostname nautilus[6412]: g_key_file_load_from_file: assertion 'file != NULL' failed Mar 01 16:09:59 hostname nautilus[6412]: Could not establish a connection to Tracker: Failed to load SPARQL backend: Key file does not have group “DomainOntology” Mar 01 16:09:59 hostname nautilus[6412]: g_key_file_load_from_file: assertion 'file != NULL' failed Mar 01 16:09:59 hostname nautilus[6412]: Could not establish a connection to Tracker: Failed to load SPARQL backend: Key file does not have group “DomainOntology” Mar 01 16:10:00 hostname nautilus[6412]: g_key_file_load_from_file: assertion 'file != NULL' failed Mar 01 16:10:00 hostname nautilus[6412]: Could not establish a connection to Tracker: Failed to load SPARQL backend: Key file does not have group “DomainOntology” Mar 01 16:10:01 hostname gnome-tweak-too[31753]: Failed to measure available space: The specified location is not supported Mar 01 16:10:01 hostname gnome-tweak-too[31753]: Failed to measure available space: The specified location is not supported Mar 01 16:10:17 hostname nautilus[6412]: g_key_file_load_from_file: assertion 'file != NULL' failed Mar 01 16:10:17 hostname nautilus[6412]: Could not establish a connection to Tracker: Failed to load SPARQL backend: Key file does not have group “DomainOntology” Mar 01 16:10:17 hostname nautilus[6412]: g_key_file_load_from_file: assertion 'file != NULL' failed Mar 01 16:10:17 hostname nautilus[6412]: Could not establish a connection to Tracker: Failed to load SPARQL backend: Key file does not have group “DomainOntology” Mar 01 16:13:18 hostname gnome-terminal-[1661]: invalid unclassed pointer in cast to 'GtkWindow' Mar 01 16:13:18 hostname gnome-terminal-[1661]: invalid unclassed pointer in cast to 'TerminalWindow' Mar 01 16:13:18 hostname gnome-terminal-[1661]: terminal_mdi_container_get_active_screen: assertion 'TERMINAL_IS_MDI_CONTAINER (container)' failed Mar 01 16:13:18 hostname gnome-terminal-[1661]: gtk_widget_style_get: assertion 'GTK_IS_WIDGET (widget)' failed Mar 01 16:14:23 hostname gnome-shell[1310]: Some code accessed the property 'discreteGpuAvailable' on the module 'appDisplay'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway. Mar 01 16:14:23 hostname gnome-shell[1310]: Some code accessed the property 'WindowPreviewMenuItem' on the module 'windowPreview'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway. Mar 01 16:15:22 hostname gnome-terminal-[1661]: invalid unclassed pointer in cast to 'GtkWindow' Mar 01 16:15:22 hostname gnome-terminal-[1661]: invalid unclassed pointer in cast to 'TerminalWindow' Mar 01 16:15:22 hostname gnome-terminal-[1661]: terminal_mdi_container_get_active_screen: assertion 'TERMINAL_IS_MDI_CONTAINER (container)' failed Mar 01 16:15:22 hostname gnome-terminal-[1661]: gtk_widget_style_get: assertion 'GTK_IS_WIDGET (widget)' failed Mar 01 16:15:43 hostname gnome-terminal-[1661]: invalid unclassed pointer in cast to 'GtkWindow' Mar 01 16:15:44 hostname gnome-terminal-[1661]: invalid unclassed pointer in cast to 'TerminalWindow' Mar 01 16:15:44 hostname gnome-terminal-[1661]: terminal_mdi_container_get_active_screen: assertion 'TERMINAL_IS_MDI_CONTAINER (container)' failed Mar 01 16:15:44 hostname gnome-terminal-[1661]: gtk_widget_style_get: assertion 'GTK_IS_WIDGET (widget)' failed Mar 01 16:16:01 hostname gnome-terminal-[1661]: invalid unclassed pointer in cast to 'GtkWindow' Mar 01 16:16:01 hostname gnome-terminal-[1661]: invalid unclassed pointer in cast to 'TerminalWindow' Mar 01 16:16:01 hostname gnome-terminal-[1661]: terminal_mdi_container_get_active_screen: assertion 'TERMINAL_IS_MDI_CONTAINER (container)' failed Mar 01 16:16:01 hostname gnome-terminal-[1661]: gtk_widget_style_get: assertion 'GTK_IS_WIDGET (widget)' failed Mar 01 16:24:45 hostname gnome-terminal-[1661]: Allocating size to GtkBox 0x5647a66bcf70 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Mar 01 16:24:45 hostname gnome-terminal-[1661]: Allocating size to GtkBox 0x5647a66bcf70 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Mar 01 16:24:45 hostname gnome-terminal-[1661]: Allocating size to GtkBox 0x5647a66bcf70 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Mar 01 16:24:45 hostname gnome-terminal-[1661]: Allocating size to GtkBox 0x5647a66bcf70 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Mar 01 16:27:03 hostname evince[32181]: Allocating size to EvSidebar 0x55ba02a5d700 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Mar 01 16:27:03 hostname gnome-shell[1310]: setup_framebuffers: assertion 'width > 0' failed Mar 01 16:29:30 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (22161815) is greater than comparison timestamp (22161813). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 01 16:29:30 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00003 (RUNME.sh +) appears to be one of the offending windows with a timestamp of 22161815. Working around... Mar 01 16:29:36 hostname org.gnome.Shell.desktop[1310]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough! Mar 01 16:29:37 hostname org.gnome.Shell.desktop[1310]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough! Mar 01 16:29:37 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (22168407) is greater than comparison timestamp (22168398). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 01 16:29:37 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00003 (RUNME.sh () appears to be one of the offending windows with a timestamp of 22168407. Working around... Mar 01 16:29:37 hostname org.gnome.Shell.desktop[1310]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough! Mar 01 16:30:28 hostname gnome-terminal-[1661]: Allocating size to GtkBox 0x5647a72a15c0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Mar 01 16:30:28 hostname gnome-terminal-[1661]: Allocating size to GtkBox 0x5647a72a15c0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Mar 01 16:30:28 hostname gnome-terminal-[1661]: Allocating size to GtkBox 0x5647a72a15c0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Mar 01 16:30:28 hostname gnome-terminal-[1661]: Allocating size to GtkBox 0x5647a72a15c0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Mar 01 16:30:28 hostname gnome-terminal-[1661]: Allocating size to GtkBox 0x5647a72a15c0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Mar 01 16:30:28 hostname gnome-terminal-[1661]: Allocating size to GtkBox 0x5647a72a15c0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Mar 01 16:30:28 hostname gnome-terminal-[1661]: Allocating size to GtkBox 0x5647a72a15c0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Mar 01 16:30:28 hostname gnome-terminal-[1661]: Allocating size to GtkBox 0x5647a72a15c0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Mar 01 16:30:28 hostname gnome-terminal-[1661]: Allocating size to GtkBox 0x5647a72a15c0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Mar 01 16:30:28 hostname gnome-terminal-[1661]: Allocating size to GtkBox 0x5647a72a15c0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Mar 01 16:30:28 hostname gnome-terminal-[1661]: Allocating size to GtkBox 0x5647a72a15c0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Mar 01 16:30:28 hostname gnome-terminal-[1661]: Allocating size to GtkBox 0x5647a72a15c0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Mar 01 16:33:45 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (22416758) is greater than comparison timestamp (22416754). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 01 16:33:45 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00003 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 22416758. Working around... Mar 01 16:34:07 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (22439231) is greater than comparison timestamp (22439224). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 01 16:34:07 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00003 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 22439231. Working around... Mar 01 16:34:08 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (22439291) is greater than comparison timestamp (22439288). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 01 16:34:08 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00003 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 22439291. Working around... Mar 01 16:34:31 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (22462531) is greater than comparison timestamp (22462524). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 01 16:34:31 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00003 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 22462531. Working around... Mar 01 16:34:49 hostname gnome-terminal-[1661]: Allocating size to GtkBox 0x5647a62246d0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Mar 01 16:37:47 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (22658624) is greater than comparison timestamp (22658607). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 01 16:37:47 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 22658624. Working around... Mar 01 16:38:08 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (22680212) is greater than comparison timestamp (22680210). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 01 16:38:08 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 22680212. Working around... Mar 01 16:38:09 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (22680574) is greater than comparison timestamp (22680571). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 01 16:38:09 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 22680574. Working around... Mar 01 16:38:09 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (22680874) is greater than comparison timestamp (22680870). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 01 16:38:09 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 22680874. Working around... Mar 01 16:38:09 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (22681055) is greater than comparison timestamp (22681051). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 01 16:38:09 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 22681055. Working around... Mar 01 16:38:09 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (22681235) is greater than comparison timestamp (22681230). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 01 16:38:09 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 22681235. Working around... Mar 01 16:38:10 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (22682140) is greater than comparison timestamp (22682130). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 01 16:38:10 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 22682140. Working around... Mar 01 16:38:11 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (22682500) is greater than comparison timestamp (22682493). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 01 16:38:11 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 22682500. Working around... Mar 01 16:38:13 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (22685073) is greater than comparison timestamp (22685072). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 01 16:38:13 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 22685073. Working around... Mar 01 16:38:13 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (22685103) is greater than comparison timestamp (22685102). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 01 16:38:13 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 22685103. Working around... Mar 01 16:40:46 hostname gnome-terminal-[1661]: Allocating size to GtkBox 0x5647a66bcf70 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Mar 01 16:40:46 hostname gnome-terminal-[1661]: Allocating size to GtkBox 0x5647a66bcf70 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Mar 01 16:40:46 hostname gnome-terminal-[1661]: Allocating size to GtkBox 0x5647a66bcf70 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Mar 01 16:40:46 hostname gnome-terminal-[1661]: Allocating size to GtkBox 0x5647a66bcf70 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Mar 01 16:40:46 hostname gnome-terminal-[1661]: Allocating size to GtkBox 0x5647a66bcf70 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Mar 01 16:42:17 hostname Web Content[32129]: Unable to open /var/lib/snapd/desktop/dconf/profile/user: Permission denied Mar 01 16:43:01 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (22972456) is greater than comparison timestamp (22972442). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 01 16:43:01 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 22972456. Working around... Mar 01 16:43:19 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (22990649) is greater than comparison timestamp (22990648). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 01 16:43:19 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 22990649. Working around... Mar 01 16:43:19 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (22990800) is greater than comparison timestamp (22990790). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 01 16:43:19 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 22990800. Working around... Mar 01 16:44:00 hostname org.gnome.Shell.desktop[1310]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough! Mar 01 16:44:00 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (23032237) is greater than comparison timestamp (23032222). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 01 16:44:00 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 23032237. Working around... Mar 01 16:44:01 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (23032388) is greater than comparison timestamp (23032372). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 01 16:44:01 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 23032388. Working around... Mar 01 16:44:01 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (23032449) is greater than comparison timestamp (23032440). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 01 16:44:01 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 23032449. Working around... Mar 01 16:44:11 hostname org.gnome.Shell.desktop[1310]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough! Mar 01 16:44:19 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (23050837) is greater than comparison timestamp (23050835). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 01 16:44:19 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 23050837. Working around... Mar 01 16:44:25 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (23056882) is greater than comparison timestamp (23056872). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 01 16:44:25 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 23056882. Working around... Mar 01 16:44:25 hostname org.gnome.Shell.desktop[1310]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough! Mar 01 16:46:44 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (23196047) is greater than comparison timestamp (23196042). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 01 16:46:44 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 23196047. Working around... Mar 01 16:46:44 hostname org.gnome.Shell.desktop[1310]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough! Mar 01 16:46:45 hostname org.gnome.Shell.desktop[1310]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough! Mar 01 16:47:43 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (23254420) is greater than comparison timestamp (23254418). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 01 16:47:43 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 23254420. Working around... Mar 01 16:47:43 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (23254450) is greater than comparison timestamp (23254448). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 01 16:47:43 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 23254450. Working around... Mar 01 16:47:47 hostname org.gnome.Shell.desktop[1310]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough! Mar 01 16:47:47 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (23258539) is greater than comparison timestamp (23258538). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 01 16:47:47 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 23258539. Working around... Mar 01 16:50:23 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (23415150) is greater than comparison timestamp (23415136). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 01 16:50:23 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 23415150. Working around... Mar 01 16:51:19 hostname org.gnome.Shell.desktop[1310]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough! Mar 01 16:51:20 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (23472163) is greater than comparison timestamp (23472153). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 01 16:51:20 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 23472163. Working around... Mar 01 16:51:21 hostname org.gnome.Shell.desktop[1310]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough! Mar 01 16:51:24 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (23475567) is greater than comparison timestamp (23475561). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 01 16:51:24 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 23475567. Working around... Mar 01 16:51:36 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (23488183) is greater than comparison timestamp (23488179). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 01 16:51:36 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 23488183. Working around... Mar 01 16:51:45 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (23497168) is greater than comparison timestamp (23497162). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 01 16:51:45 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 23497168. Working around... Mar 01 16:52:14 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (23525788) is greater than comparison timestamp (23525785). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 01 16:52:14 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 23525788. Working around... Mar 01 16:52:14 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (23525818) is greater than comparison timestamp (23525816). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 01 16:52:14 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 23525818. Working around... Mar 01 16:52:14 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (23525848) is greater than comparison timestamp (23525847). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 01 16:52:14 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 23525848. Working around... Mar 01 16:52:14 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (23525880) is greater than comparison timestamp (23525878). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 01 16:52:14 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 23525880. Working around... Mar 01 16:52:41 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (23553237) is greater than comparison timestamp (23553232). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 01 16:52:41 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 23553237. Working around... Mar 01 16:52:42 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (23553267) is greater than comparison timestamp (23553263). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 01 16:52:42 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 23553267. Working around... Mar 01 16:53:01 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (23572918) is greater than comparison timestamp (23572912). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 01 16:53:01 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 23572918. Working around... Mar 01 16:54:10 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (23642026) is greater than comparison timestamp (23642025). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 01 16:54:10 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 23642026. Working around... Mar 01 16:54:48 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (23679804) is greater than comparison timestamp (23679802). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 01 16:54:48 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 23679804. Working around... Mar 01 16:55:54 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (23745414) is greater than comparison timestamp (23745404). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 01 16:55:54 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 23745414. Working around... Mar 01 16:55:54 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (23745444) is greater than comparison timestamp (23745440). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 01 16:55:54 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 23745444. Working around... Mar 01 16:55:54 hostname org.gnome.Shell.desktop[1310]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough! Mar 01 16:55:54 hostname org.gnome.Shell.desktop[1310]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough! Mar 01 16:56:51 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (23802667) is greater than comparison timestamp (23802659). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 01 16:56:51 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2200010 (Mozilla Fi) appears to be one of the offending windows with a timestamp of 23802667. Working around... Mar 01 17:03:37 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (24208473) is greater than comparison timestamp (24208465). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 01 17:03:37 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 24208473. Working around... Mar 01 17:04:28 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (24259412) is greater than comparison timestamp (24259408). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 01 17:04:28 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 24259412. Working around... Mar 01 17:04:28 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (24259442) is greater than comparison timestamp (24259439). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 01 17:04:28 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 24259442. Working around... Mar 01 17:04:28 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (24259624) is greater than comparison timestamp (24259616). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 01 17:04:28 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 24259624. Working around... Mar 01 17:04:28 hostname org.gnome.Shell.desktop[1310]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough! Mar 01 17:04:28 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (24260081) is greater than comparison timestamp (24260076). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 01 17:04:28 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 24260081. Working around... Mar 01 17:11:22 hostname gnome-software[1599]: no app for changed ubuntu-appindicators@ubuntu.com Mar 01 17:11:22 hostname gnome-software[1599]: no app for changed ubuntu-dock@ubuntu.com Mar 02 00:05:12 hostname gsd-color[1464]: failed to connect to device: Failed to connect to missing device /org/freedesktop/ColorManager/devices/cups_Hewlett_Packard_HP_Color_LaserJet_M553 Mar 02 00:05:12 hostname gsd-color[1084]: failed to connect to device: Failed to connect to missing device /org/freedesktop/ColorManager/devices/cups_Hewlett_Packard_HP_Color_LaserJet_M553 Mar 02 00:05:12 hostname colord[1151]: failed to get session [pid 2620]: No data available Mar 02 06:25:44 hostname kernel: kauditd_printk_skb: 14 callbacks suppressed Mar 02 09:36:25 hostname gnome-software[1599]: no app for changed ubuntu-dock@ubuntu.com Mar 02 09:36:25 hostname gnome-software[1599]: no app for changed ubuntu-appindicators@ubuntu.com Mar 02 09:41:19 hostname firefox[1757]: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Avahi was not provided by any .service files Mar 02 09:41:19 hostname firefox[1757]: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Avahi was not provided by any .service files Mar 02 09:57:27 hostname org.gnome.Shell.desktop[1310]: [Parent 1757, Gecko_IOThread] WARNING: pipe error: Broken pipe: file /build/firefox-h7Huxq/firefox-58.0.2+build1/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 709 Mar 02 10:00:01 hostname firefox[1757]: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Avahi was not provided by any .service files Mar 02 10:00:01 hostname firefox[1757]: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Avahi was not provided by any .service files Mar 02 10:00:18 hostname firefox[1757]: Failed to measure available space: The specified location is not supported Mar 02 10:00:58 hostname evince[4619]: Allocating size to EvSidebar 0x561f420f1690 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Mar 02 10:01:17 hostname nautilus[6412]: g_key_file_load_from_file: assertion 'file != NULL' failed Mar 02 10:01:17 hostname nautilus[6412]: Could not establish a connection to Tracker: Failed to load SPARQL backend: Key file does not have group “DomainOntology” Mar 02 10:01:17 hostname nautilus[6412]: g_key_file_load_from_file: assertion 'file != NULL' failed Mar 02 10:01:17 hostname nautilus[6412]: Could not establish a connection to Tracker: Failed to load SPARQL backend: Key file does not have group “DomainOntology” Mar 02 10:01:17 hostname nautilus[6412]: g_key_file_load_from_file: assertion 'file != NULL' failed Mar 02 10:01:17 hostname nautilus[6412]: Could not establish a connection to Tracker: Failed to load SPARQL backend: Key file does not have group “DomainOntology” Mar 02 10:01:17 hostname nautilus[6412]: g_key_file_load_from_file: assertion 'file != NULL' failed Mar 02 10:01:17 hostname nautilus[6412]: Could not establish a connection to Tracker: Failed to load SPARQL backend: Key file does not have group “DomainOntology” Mar 02 10:01:18 hostname gnome-tweak-too[4754]: Failed to measure available space: The specified location is not supported Mar 02 10:01:18 hostname gnome-tweak-too[4754]: Failed to measure available space: The specified location is not supported Mar 02 10:10:59 hostname gnome-terminal-[1661]: Allocating size to GtkBox 0x5647a7179820 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Mar 02 10:10:59 hostname gnome-terminal-[1661]: Allocating size to GtkBox 0x5647a7179820 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Mar 02 10:10:59 hostname gnome-terminal-[1661]: Allocating size to GtkBox 0x5647a7179820 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Mar 02 10:10:59 hostname gnome-terminal-[1661]: Allocating size to GtkBox 0x5647a7179820 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Mar 02 10:10:59 hostname gnome-terminal-[1661]: Allocating size to GtkBox 0x5647a7179820 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Mar 02 10:10:59 hostname gnome-terminal-[1661]: Allocating size to GtkBox 0x5647a7179820 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Mar 02 10:11:00 hostname gnome-terminal-[1661]: Allocating size to GtkBox 0x5647a7179820 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Mar 02 10:11:00 hostname gnome-terminal-[1661]: Allocating size to GtkBox 0x5647a7179820 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Mar 02 10:11:00 hostname gnome-terminal-[1661]: Allocating size to GtkBox 0x5647a7179820 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Mar 02 10:11:00 hostname gnome-terminal-[1661]: Allocating size to GtkBox 0x5647a7179820 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Mar 02 10:11:00 hostname gnome-terminal-[1661]: Allocating size to GtkBox 0x5647a7179820 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Mar 02 10:11:00 hostname gnome-terminal-[1661]: Allocating size to GtkBox 0x5647a7179820 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Mar 02 10:11:00 hostname gnome-terminal-[1661]: Allocating size to GtkBox 0x5647a7179820 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Mar 02 10:11:00 hostname gnome-terminal-[1661]: Allocating size to GtkBox 0x5647a7179820 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Mar 02 10:11:00 hostname gnome-terminal-[1661]: Allocating size to GtkBox 0x5647a7179820 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Mar 02 10:11:00 hostname gnome-terminal-[1661]: Allocating size to GtkBox 0x5647a7179820 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Mar 02 10:11:00 hostname gnome-terminal-[1661]: Allocating size to GtkBox 0x5647a7179820 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Mar 02 10:11:00 hostname gnome-terminal-[1661]: Allocating size to GtkBox 0x5647a7179820 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Mar 02 10:11:00 hostname gnome-terminal-[1661]: Allocating size to GtkBox 0x5647a7179820 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Mar 02 10:11:00 hostname gnome-terminal-[1661]: Allocating size to GtkBox 0x5647a7179820 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Mar 02 10:11:00 hostname gnome-terminal-[1661]: Allocating size to GtkBox 0x5647a7179820 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Mar 02 10:11:00 hostname gnome-terminal-[1661]: Allocating size to GtkBox 0x5647a7179820 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Mar 02 10:11:00 hostname gnome-terminal-[1661]: Allocating size to GtkBox 0x5647a7179820 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Mar 02 10:11:15 hostname gnome-terminal-[1661]: invalid unclassed pointer in cast to 'GtkWindow' Mar 02 10:11:15 hostname gnome-terminal-[1661]: invalid unclassed pointer in cast to 'TerminalWindow' Mar 02 10:11:15 hostname gnome-terminal-[1661]: terminal_mdi_container_get_active_screen: assertion 'TERMINAL_IS_MDI_CONTAINER (container)' failed Mar 02 10:11:15 hostname gnome-terminal-[1661]: gtk_widget_style_get: assertion 'GTK_IS_WIDGET (widget)' failed Mar 02 10:15:02 hostname Web Content[32079]: Unable to open /var/lib/snapd/desktop/dconf/profile/user: Permission denied Mar 02 10:16:19 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (86170448) is greater than comparison timestamp (86170446). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 10:16:19 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 86170448. Working around... Mar 02 10:16:21 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (86172610) is greater than comparison timestamp (86172607). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 10:16:21 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 86172610. Working around... Mar 02 10:18:39 hostname org.gnome.Shell.desktop[1310]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough! Mar 02 10:20:41 hostname org.gnome.Shell.desktop[1310]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough! Mar 02 10:21:06 hostname org.gnome.Shell.desktop[1310]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough! Mar 02 10:21:06 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (86457390) is greater than comparison timestamp (86457380). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 10:21:06 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 86457390. Working around... Mar 02 10:21:06 hostname org.gnome.Shell.desktop[1310]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough! Mar 02 10:21:08 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (86459370) is greater than comparison timestamp (86459360). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 10:21:08 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 86459370. Working around... Mar 02 10:21:08 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (86459580) is greater than comparison timestamp (86459571). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 10:21:08 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 86459580. Working around... Mar 02 10:21:13 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (86464428) is greater than comparison timestamp (86464414). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 10:21:13 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 86464428. Working around... Mar 02 10:21:13 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (86464578) is greater than comparison timestamp (86464562). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 10:21:13 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 86464578. Working around... Mar 02 10:21:20 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (86471628) is greater than comparison timestamp (86471624). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 10:21:20 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 86471628. Working around... Mar 02 10:21:27 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (86478590) is greater than comparison timestamp (86478589). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 10:21:27 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 86478590. Working around... Mar 02 10:21:27 hostname org.gnome.Shell.desktop[1310]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough! Mar 02 10:22:48 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (86559977) is greater than comparison timestamp (86559966). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 10:22:48 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 86559977. Working around... Mar 02 10:22:49 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (86560278) is greater than comparison timestamp (86560277). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 10:22:49 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 86560278. Working around... Mar 02 10:22:50 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (86561944) is greater than comparison timestamp (86561937). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 10:22:50 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 86561944. Working around... Mar 02 10:22:50 hostname org.gnome.Shell.desktop[1310]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough! Mar 02 10:22:50 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (86562246) is greater than comparison timestamp (86562238). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 10:22:50 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 86562246. Working around... Mar 02 10:22:51 hostname org.gnome.Shell.desktop[1310]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough! Mar 02 10:22:51 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (86562546) is greater than comparison timestamp (86562537). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 10:22:51 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 86562546. Working around... Mar 02 10:22:55 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (86566377) is greater than comparison timestamp (86566368). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 10:22:55 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 86566377. Working around... Mar 02 10:22:55 hostname org.gnome.Shell.desktop[1310]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough! Mar 02 10:25:08 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (86700065) is greater than comparison timestamp (86700062). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 10:25:08 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 86700065. Working around... Mar 02 10:25:09 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (86700246) is greater than comparison timestamp (86700242). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 10:25:09 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 86700246. Working around... Mar 02 10:25:09 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (86700277) is greater than comparison timestamp (86700273). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 10:25:09 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 86700277. Working around... Mar 02 10:25:09 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (86700547) is greater than comparison timestamp (86700542). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 10:25:09 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 86700547. Working around... Mar 02 10:25:09 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (86700577) is greater than comparison timestamp (86700573). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 10:25:09 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 86700577. Working around... Mar 02 10:25:09 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (86700607) is greater than comparison timestamp (86700604). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 10:25:09 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 86700607. Working around... Mar 02 10:25:09 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (86700727) is greater than comparison timestamp (86700722). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 10:25:09 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 86700727. Working around... Mar 02 10:25:09 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (86700757) is greater than comparison timestamp (86700752). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 10:25:09 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 86700757. Working around... Mar 02 10:25:09 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (86700848) is greater than comparison timestamp (86700842). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 10:25:09 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 86700848. Working around... Mar 02 10:25:09 hostname org.gnome.Shell.desktop[1310]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough! Mar 02 10:25:09 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (86701149) is greater than comparison timestamp (86701142). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 10:25:09 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 86701149. Working around... Mar 02 10:25:10 hostname org.gnome.Shell.desktop[1310]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough! Mar 02 10:25:10 hostname org.gnome.Shell.desktop[1310]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough! Mar 02 10:25:10 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (86701752) is greater than comparison timestamp (86701742). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 10:25:10 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 86701752. Working around... Mar 02 10:25:10 hostname org.gnome.Shell.desktop[1310]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough! Mar 02 10:25:10 hostname org.gnome.Shell.desktop[1310]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough! Mar 02 10:25:10 hostname org.gnome.Shell.desktop[1310]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough! Mar 02 10:25:17 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (86708360) is greater than comparison timestamp (86708355). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 10:25:17 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 86708360. Working around... Mar 02 10:25:17 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (86708661) is greater than comparison timestamp (86708644). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 10:25:17 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 86708661. Working around... Mar 02 10:25:18 hostname org.gnome.Shell.desktop[1310]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough! Mar 02 10:25:18 hostname org.gnome.Shell.desktop[1310]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough! Mar 02 10:25:20 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (86711461) is greater than comparison timestamp (86711445). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 10:25:20 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 86711461. Working around... Mar 02 10:25:22 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (86713509) is greater than comparison timestamp (86713505). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 10:25:22 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 86713509. Working around... Mar 02 10:25:30 hostname org.gnome.Shell.desktop[1310]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough! Mar 02 10:25:30 hostname org.gnome.Shell.desktop[1310]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough! Mar 02 10:25:46 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (86737292) is greater than comparison timestamp (86737291). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 10:25:46 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 86737292. Working around... Mar 02 10:25:46 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (86737383) is greater than comparison timestamp (86737382). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 10:25:46 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 86737383. Working around... Mar 02 10:27:46 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (86857860) is greater than comparison timestamp (86857842). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 10:27:46 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 86857860. Working around... Mar 02 10:27:46 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (86858043) is greater than comparison timestamp (86858042). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 10:27:46 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 86858043. Working around... Mar 02 10:28:14 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (86885396) is greater than comparison timestamp (86885389). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 10:28:14 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 86885396. Working around... Mar 02 10:28:29 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (86901052) is greater than comparison timestamp (86901033). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 10:28:29 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 86901052. Working around... Mar 02 10:28:35 hostname org.gnome.Shell.desktop[1310]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough! Mar 02 10:30:17 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (87009207) is greater than comparison timestamp (87009199). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 10:30:17 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 87009207. Working around... Mar 02 10:30:21 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (87012728) is greater than comparison timestamp (87012722). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 10:30:21 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 87012728. Working around... Mar 02 10:32:50 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (87161390) is greater than comparison timestamp (87161389). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 10:32:50 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 87161390. Working around... Mar 02 10:34:03 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (87235148) is greater than comparison timestamp (87235139). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 10:34:03 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 87235148. Working around... Mar 02 10:34:03 hostname org.gnome.Shell.desktop[1310]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough! Mar 02 10:34:12 hostname org.gnome.Shell.desktop[1310]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough! Mar 02 10:34:24 hostname org.gnome.Shell.desktop[1310]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough! Mar 02 10:34:24 hostname org.gnome.Shell.desktop[1310]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough! Mar 02 10:34:31 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (87262747) is greater than comparison timestamp (87262746). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 10:34:31 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 87262747. Working around... Mar 02 10:35:43 hostname systemd-tmpfiles[5108]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring. Mar 02 10:35:50 hostname gnome-software[1599]: no app for changed ubuntu-appindicators@ubuntu.com Mar 02 10:35:50 hostname gnome-software[1599]: no app for changed ubuntu-dock@ubuntu.com Mar 02 10:47:26 hostname gnome-software[1599]: no app for changed ubuntu-dock@ubuntu.com Mar 02 10:47:26 hostname gnome-software[1599]: no app for changed ubuntu-appindicators@ubuntu.com Mar 02 10:48:41 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (88112536) is greater than comparison timestamp (88112524). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 10:48:41 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2e00ba1 (Write: Re:) appears to be one of the offending windows with a timestamp of 88112536. Working around... Mar 02 10:48:41 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (88112686) is greater than comparison timestamp (88112676). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 10:48:41 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2e00ba1 (Write: Re:) appears to be one of the offending windows with a timestamp of 88112686. Working around... Mar 02 10:48:41 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (88112716) is greater than comparison timestamp (88112706). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 10:48:41 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2e00ba1 (Write: Re:) appears to be one of the offending windows with a timestamp of 88112716. Working around... Mar 02 10:48:41 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (88112867) is greater than comparison timestamp (88112859). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 10:48:41 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2e00ba1 (Write: Re:) appears to be one of the offending windows with a timestamp of 88112867. Working around... Mar 02 10:49:01 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (88132732) is greater than comparison timestamp (88132719). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 10:49:01 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2e00ba1 (Write: Re:) appears to be one of the offending windows with a timestamp of 88132732. Working around... Mar 02 10:49:01 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (88132883) is greater than comparison timestamp (88132873). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 10:49:01 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2e00ba1 (Write: Re:) appears to be one of the offending windows with a timestamp of 88132883. Working around... Mar 02 10:49:01 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (88132913) is greater than comparison timestamp (88132904). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 10:49:01 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2e00ba1 (Write: Re:) appears to be one of the offending windows with a timestamp of 88132913. Working around... Mar 02 10:49:01 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (88133064) is greater than comparison timestamp (88133056). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 10:49:01 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2e00ba1 (Write: Re:) appears to be one of the offending windows with a timestamp of 88133064. Working around... Mar 02 10:49:01 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (88133094) is greater than comparison timestamp (88133088). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 10:49:01 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2e00ba1 (Write: Re:) appears to be one of the offending windows with a timestamp of 88133094. Working around... Mar 02 10:49:01 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (88133124) is greater than comparison timestamp (88133118). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 10:49:01 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2e00ba1 (Write: Re:) appears to be one of the offending windows with a timestamp of 88133124. Working around... Mar 02 10:49:01 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (88133214) is greater than comparison timestamp (88133211). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 10:49:01 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2e00ba1 (Write: Re:) appears to be one of the offending windows with a timestamp of 88133214. Working around... Mar 02 10:49:02 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (88133244) is greater than comparison timestamp (88133241). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 10:49:02 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2e00ba1 (Write: Re:) appears to be one of the offending windows with a timestamp of 88133244. Working around... Mar 02 10:49:02 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (88133274) is greater than comparison timestamp (88133271). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 10:49:02 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2e00ba1 (Write: Re:) appears to be one of the offending windows with a timestamp of 88133274. Working around... Mar 02 10:49:02 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (88133364) is greater than comparison timestamp (88133362). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 10:49:02 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2e00ba1 (Write: Re:) appears to be one of the offending windows with a timestamp of 88133364. Working around... Mar 02 10:49:02 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (88133424) is greater than comparison timestamp (88133423). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 10:49:02 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2e00ba1 (Write: Re:) appears to be one of the offending windows with a timestamp of 88133424. Working around... Mar 02 10:50:31 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (88222881) is greater than comparison timestamp (88222869). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 10:50:31 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2e00ba1 (Write: Re:) appears to be one of the offending windows with a timestamp of 88222881. Working around... Mar 02 10:50:31 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (88222911) is greater than comparison timestamp (88222900). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 10:50:31 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2e00ba1 (Write: Re:) appears to be one of the offending windows with a timestamp of 88222911. Working around... Mar 02 10:50:31 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (88222941) is greater than comparison timestamp (88222934). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 10:50:31 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2e00ba1 (Write: Re:) appears to be one of the offending windows with a timestamp of 88222941. Working around... Mar 02 10:50:31 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (88223061) is greater than comparison timestamp (88223056). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 10:50:31 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2e00ba1 (Write: Re:) appears to be one of the offending windows with a timestamp of 88223061. Working around... Mar 02 10:50:31 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (88223091) is greater than comparison timestamp (88223086). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 10:50:31 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2e00ba1 (Write: Re:) appears to be one of the offending windows with a timestamp of 88223091. Working around... Mar 02 10:50:31 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (88223182) is greater than comparison timestamp (88223178). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 10:50:31 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2e00ba1 (Write: Re:) appears to be one of the offending windows with a timestamp of 88223182. Working around... Mar 02 10:50:31 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (88223212) is greater than comparison timestamp (88223209). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 10:50:31 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2e00ba1 (Write: Re:) appears to be one of the offending windows with a timestamp of 88223212. Working around... Mar 02 10:50:32 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (88223242) is greater than comparison timestamp (88223239). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 10:50:32 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2e00ba1 (Write: Re:) appears to be one of the offending windows with a timestamp of 88223242. Working around... Mar 02 10:50:32 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (88223273) is greater than comparison timestamp (88223270). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 10:50:32 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2e00ba1 (Write: Re:) appears to be one of the offending windows with a timestamp of 88223273. Working around... Mar 02 10:50:32 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (88223333) is greater than comparison timestamp (88223330). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 10:50:32 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2e00ba1 (Write: Re:) appears to be one of the offending windows with a timestamp of 88223333. Working around... Mar 02 10:50:32 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (88223363) is greater than comparison timestamp (88223360). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 10:50:32 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2e00ba1 (Write: Re:) appears to be one of the offending windows with a timestamp of 88223363. Working around... Mar 02 10:50:32 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (88223454) is greater than comparison timestamp (88223452). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 10:50:32 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2e00ba1 (Write: Re:) appears to be one of the offending windows with a timestamp of 88223454. Working around... Mar 02 10:50:32 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (88223484) is greater than comparison timestamp (88223483). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 10:50:32 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2e00ba1 (Write: Re:) appears to be one of the offending windows with a timestamp of 88223484. Working around... Mar 02 10:54:31 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (88462780) is greater than comparison timestamp (88462777). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 10:54:31 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 88462780. Working around... Mar 02 10:54:31 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (88462811) is greater than comparison timestamp (88462807). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 10:54:31 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 88462811. Working around... Mar 02 10:54:37 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (88468311) is greater than comparison timestamp (88468299). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 10:54:37 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 88468311. Working around... Mar 02 10:55:25 hostname org.gnome.Shell.desktop[1310]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough! Mar 02 10:57:23 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (88634442) is greater than comparison timestamp (88634441). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 10:57:23 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 88634442. Working around... Mar 02 10:57:23 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (88634472) is greater than comparison timestamp (88634471). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 10:57:23 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 88634472. Working around... Mar 02 10:57:39 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (88651232) is greater than comparison timestamp (88651225). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 10:57:39 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 88651232. Working around... Mar 02 10:57:42 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (88653476) is greater than comparison timestamp (88653466). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 10:57:42 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 88653476. Working around... Mar 02 10:57:42 hostname org.gnome.Shell.desktop[1310]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough! Mar 02 10:57:42 hostname org.gnome.Shell.desktop[1310]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough! Mar 02 10:57:42 hostname org.gnome.Shell.desktop[1310]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough! Mar 02 10:58:37 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (88708492) is greater than comparison timestamp (88708488). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 10:58:37 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 88708492. Working around... Mar 02 10:58:43 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (88714625) is greater than comparison timestamp (88714624). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 10:58:43 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 88714625. Working around... Mar 02 10:58:43 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (88714745) is greater than comparison timestamp (88714741). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 10:58:43 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 88714745. Working around... Mar 02 10:58:43 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (88714775) is greater than comparison timestamp (88714772). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 10:58:43 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 88714775. Working around... Mar 02 11:00:53 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (88844925) is greater than comparison timestamp (88844916). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 11:00:53 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 88844925. Working around... Mar 02 11:01:49 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (88900390) is greater than comparison timestamp (88900389). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 11:01:49 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 88900390. Working around... Mar 02 11:01:49 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (88900420) is greater than comparison timestamp (88900419). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 11:01:49 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 88900420. Working around... Mar 02 11:02:44 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (88955790) is greater than comparison timestamp (88955786). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 11:02:44 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 88955790. Working around... Mar 02 11:02:47 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (88959234) is greater than comparison timestamp (88959224). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 11:02:47 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 88959234. Working around... Mar 02 11:02:48 hostname org.gnome.Shell.desktop[1310]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough! Mar 02 11:02:55 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (88967240) is greater than comparison timestamp (88967232). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 11:02:55 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 88967240. Working around... Mar 02 11:02:56 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (88967330) is greater than comparison timestamp (88967326). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 11:02:56 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 88967330. Working around... Mar 02 11:03:50 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (89021424) is greater than comparison timestamp (89021421). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 11:03:50 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 89021424. Working around... Mar 02 11:05:39 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (89130923) is greater than comparison timestamp (89130918). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 11:05:39 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 89130923. Working around... Mar 02 11:05:39 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (89131013) is greater than comparison timestamp (89131008). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 11:05:39 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 89131013. Working around... Mar 02 11:06:59 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (89210921) is greater than comparison timestamp (89210914). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 11:06:59 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 89210921. Working around... Mar 02 11:06:59 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (89210952) is greater than comparison timestamp (89210948). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 11:06:59 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 89210952. Working around... Mar 02 11:06:59 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (89211102) is greater than comparison timestamp (89211088). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 11:06:59 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 89211102. Working around... Mar 02 11:06:59 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (89211194) is greater than comparison timestamp (89211188). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 11:06:59 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 89211194. Working around... Mar 02 11:08:20 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (89291689) is greater than comparison timestamp (89291688). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 11:08:20 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 89291689. Working around... Mar 02 11:08:27 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (89298458) is greater than comparison timestamp (89298457). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 11:08:27 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 89298458. Working around... Mar 02 11:10:07 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (89398842) is greater than comparison timestamp (89398836). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 11:10:07 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 89398842. Working around... Mar 02 11:10:07 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (89398932) is greater than comparison timestamp (89398916). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 11:10:07 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 89398932. Working around... Mar 02 11:10:22 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (89414153) is greater than comparison timestamp (89414151). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 11:10:22 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 89414153. Working around... Mar 02 11:10:23 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (89414333) is greater than comparison timestamp (89414320). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 11:10:23 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 89414333. Working around... Mar 02 11:13:32 hostname org.gnome.Shell.desktop[1310]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough! Mar 02 11:13:32 hostname org.gnome.Shell.desktop[1310]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough! Mar 02 11:13:32 hostname org.gnome.Shell.desktop[1310]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough! Mar 02 11:14:17 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (89648533) is greater than comparison timestamp (89648531). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 11:14:17 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 89648533. Working around... Mar 02 11:14:17 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (89648563) is greater than comparison timestamp (89648561). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 11:14:17 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 89648563. Working around... Mar 02 11:20:39 hostname evolution-sourc[1370]: secret_service_search_sync: must specify at least one attribute to match Mar 02 11:24:30 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (90261405) is greater than comparison timestamp (90261396). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 11:24:30 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x3000007 (plot_png_O) appears to be one of the offending windows with a timestamp of 90261405. Working around... Mar 02 11:24:30 hostname org.gnome.Shell.desktop[1310]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough! Mar 02 11:24:30 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (90261596) is greater than comparison timestamp (90261589). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 11:24:30 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x3000007 (plot_png_O) appears to be one of the offending windows with a timestamp of 90261596. Working around... Mar 02 11:24:53 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (90285096) is greater than comparison timestamp (90285083). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 11:24:53 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x3000007 (plot_png_O) appears to be one of the offending windows with a timestamp of 90285096. Working around... Mar 02 11:25:04 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (90295894) is greater than comparison timestamp (90295888). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 11:25:04 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 90295894. Working around... Mar 02 11:25:13 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (90304484) is greater than comparison timestamp (90304483). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 11:25:13 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 90304484. Working around... Mar 02 11:25:13 hostname org.gnome.Shell.desktop[1310]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough! Mar 02 11:26:12 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (90363292) is greater than comparison timestamp (90363287). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 11:26:12 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 90363292. Working around... Mar 02 11:26:12 hostname org.gnome.Shell.desktop[1310]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough! Mar 02 11:26:42 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (90393957) is greater than comparison timestamp (90393951). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 11:26:42 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 90393957. Working around... Mar 02 11:27:01 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (90412640) is greater than comparison timestamp (90412635). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 11:27:01 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 90412640. Working around... Mar 02 11:27:01 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (90412745) is greater than comparison timestamp (90412736). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 11:27:01 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 90412745. Working around... Mar 02 11:27:02 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (90413324) is greater than comparison timestamp (90413315). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 11:27:02 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 90413324. Working around... Mar 02 11:27:02 hostname org.gnome.Shell.desktop[1310]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough! Mar 02 11:28:38 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (90509873) is greater than comparison timestamp (90509870). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 11:28:38 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 90509873. Working around... Mar 02 11:28:38 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (90509993) is greater than comparison timestamp (90509990). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 11:28:38 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 90509993. Working around... Mar 02 11:28:39 hostname org.gnome.Shell.desktop[1310]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough! Mar 02 11:28:40 hostname org.gnome.Shell.desktop[1310]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough! Mar 02 11:28:40 hostname org.gnome.Shell.desktop[1310]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough! Mar 02 11:28:40 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (90511460) is greater than comparison timestamp (90511438). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 11:28:40 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 90511460. Working around... Mar 02 11:29:01 hostname org.gnome.Shell.desktop[1310]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough! Mar 02 11:29:08 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (90539811) is greater than comparison timestamp (90539807). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 11:29:08 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 90539811. Working around... Mar 02 11:29:23 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (90554702) is greater than comparison timestamp (90554691). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 11:29:23 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 90554702. Working around... Mar 02 11:29:23 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (90554762) is greater than comparison timestamp (90554761). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 11:29:23 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 90554762. Working around... Mar 02 11:29:35 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (90566561) is greater than comparison timestamp (90566557). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 11:29:35 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 90566561. Working around... Mar 02 11:29:58 hostname org.gnome.Shell.desktop[1310]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough! Mar 02 11:30:23 hostname org.gnome.Shell.desktop[1310]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough! Mar 02 11:30:52 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (90643409) is greater than comparison timestamp (90643404). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 11:30:52 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 90643409. Working around... Mar 02 11:32:13 hostname org.gnome.Shell.desktop[1310]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough! Mar 02 11:32:31 hostname org.gnome.Shell.desktop[1310]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough! Mar 02 11:32:31 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (90742377) is greater than comparison timestamp (90742360). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 11:32:31 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 90742377. Working around... Mar 02 11:32:31 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (90742467) is greater than comparison timestamp (90742459). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 11:32:31 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 90742467. Working around... Mar 02 11:32:31 hostname org.gnome.Shell.desktop[1310]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough! Mar 02 11:32:31 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (90742648) is greater than comparison timestamp (90742639). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 11:32:31 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 90742648. Working around... Mar 02 11:32:31 hostname org.gnome.Shell.desktop[1310]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough! Mar 02 11:33:14 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (90785807) is greater than comparison timestamp (90785802). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 11:33:14 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 90785807. Working around... Mar 02 11:34:55 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (90886975) is greater than comparison timestamp (90886967). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 11:34:55 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 90886975. Working around... Mar 02 11:34:55 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (90887005) is greater than comparison timestamp (90886998). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 11:34:55 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 90887005. Working around... Mar 02 11:34:57 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (90888848) is greater than comparison timestamp (90888839). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 11:34:57 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2a00007 (hw4_2.plot) appears to be one of the offending windows with a timestamp of 90888848. Working around... Mar 02 11:37:48 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (91059839) is greater than comparison timestamp (91059827). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 11:37:48 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2e00c90 (Write: Re:) appears to be one of the offending windows with a timestamp of 91059839. Working around... Mar 02 11:37:48 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (91059869) is greater than comparison timestamp (91059862). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 11:37:48 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2e00c90 (Write: Re:) appears to be one of the offending windows with a timestamp of 91059869. Working around... Mar 02 11:37:48 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (91059899) is greater than comparison timestamp (91059894). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 11:37:48 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2e00c90 (Write: Re:) appears to be one of the offending windows with a timestamp of 91059899. Working around... Mar 02 11:37:48 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (91059989) is greater than comparison timestamp (91059986). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 11:37:48 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2e00c90 (Write: Re:) appears to be one of the offending windows with a timestamp of 91059989. Working around... Mar 02 11:37:49 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (91061206) is greater than comparison timestamp (91061196). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 11:37:49 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2e00c90 (Write: Re:) appears to be one of the offending windows with a timestamp of 91061206. Working around... Mar 02 11:37:50 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (91061296) is greater than comparison timestamp (91061288). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 11:37:50 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2e00c90 (Write: Re:) appears to be one of the offending windows with a timestamp of 91061296. Working around... Mar 02 11:37:50 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (91061356) is greater than comparison timestamp (91061349). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 11:37:50 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2e00c90 (Write: Re:) appears to be one of the offending windows with a timestamp of 91061356. Working around... Mar 02 11:37:50 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (91061387) is greater than comparison timestamp (91061379). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 11:37:50 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2e00c90 (Write: Re:) appears to be one of the offending windows with a timestamp of 91061387. Working around... Mar 02 11:37:51 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (91062740) is greater than comparison timestamp (91062728). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 11:37:51 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2e00c90 (Write: Re:) appears to be one of the offending windows with a timestamp of 91062740. Working around... Mar 02 11:37:51 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (91062770) is greater than comparison timestamp (91062760). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 11:37:51 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2e00c90 (Write: Re:) appears to be one of the offending windows with a timestamp of 91062770. Working around... Mar 02 11:37:57 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (91069027) is greater than comparison timestamp (91069026). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 11:37:57 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2e00c90 (Write: Re:) appears to be one of the offending windows with a timestamp of 91069027. Working around... Mar 02 11:39:51 hostname eog[5899]: Failed to open file '/home/username/.cache/thumbnails/normal/6ef81ede9c0f961d1fb3a6ef2aae48c6.png': No such file or directory Mar 02 11:39:51 hostname gnome-shell[1310]: setup_framebuffers: assertion 'width > 0' failed Mar 02 11:41:11 hostname eog[5928]: Failed to open file '/home/username/.cache/thumbnails/normal/60fda6c0ecfdfed82b51598cf699de98.png': No such file or directory Mar 02 11:41:11 hostname gnome-shell[1310]: setup_framebuffers: assertion 'width > 0' failed Mar 02 11:44:21 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (91453235) is greater than comparison timestamp (91453232). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 11:44:21 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2200010 (Where is t) appears to be one of the offending windows with a timestamp of 91453235. Working around... Mar 02 11:44:22 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (91453415) is greater than comparison timestamp (91453413). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 11:44:22 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2200010 (Where is t) appears to be one of the offending windows with a timestamp of 91453415. Working around... Mar 02 11:44:22 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (91453535) is greater than comparison timestamp (91453532). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 11:44:22 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2200010 (Where is t) appears to be one of the offending windows with a timestamp of 91453535. Working around... Mar 02 11:44:22 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (91453715) is greater than comparison timestamp (91453712). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 11:44:22 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2200010 (Where is t) appears to be one of the offending windows with a timestamp of 91453715. Working around... Mar 02 11:44:22 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (91453805) is greater than comparison timestamp (91453803). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 11:44:22 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2200010 (Where is t) appears to be one of the offending windows with a timestamp of 91453805. Working around... Mar 02 11:44:22 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (91453835) is greater than comparison timestamp (91453834). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 11:44:22 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2200010 (Where is t) appears to be one of the offending windows with a timestamp of 91453835. Working around... Mar 02 11:44:22 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (91454015) is greater than comparison timestamp (91454013). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 11:44:22 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2200010 (Where is t) appears to be one of the offending windows with a timestamp of 91454015. Working around... Mar 02 11:44:22 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (91454135) is greater than comparison timestamp (91454132). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 11:44:22 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2200010 (Where is t) appears to be one of the offending windows with a timestamp of 91454135. Working around... Mar 02 11:44:23 hostname org.gnome.Shell.desktop[1310]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough! Mar 02 11:48:07 hostname firefox[1757]: Failed to measure available space: The specified location is not supported Mar 02 11:48:41 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (91713070) is greater than comparison timestamp (91713058). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 11:48:41 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2200010 (Where is t) appears to be one of the offending windows with a timestamp of 91713070. Working around... Mar 02 11:48:42 hostname org.gnome.Shell.desktop[1310]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough! Mar 02 11:48:43 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (91715170) is greater than comparison timestamp (91715163). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 11:48:43 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2200010 (Where is t) appears to be one of the offending windows with a timestamp of 91715170. Working around... Mar 02 11:48:43 hostname org.gnome.Shell.desktop[1310]: Window manager warning: last_user_time (91715200) is greater than comparison timestamp (91715193). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... Mar 02 11:48:43 hostname org.gnome.Shell.desktop[1310]: Window manager warning: 0x2200010 (Where is t) appears to be one of the offending windows with a timestamp of 91715200. Working around... Mar 02 11:48:44 hostname org.gnome.Shell.desktop[1310]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough! Mar 02 11:49:17 hostname org.gnome.Shell.desktop[1310]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough! Mar 02 11:49:17 hostname org.gnome.Shell.desktop[1310]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough! Mar 02 11:49:17 hostname org.gnome.Shell.desktop[1310]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough! Mar 02 11:49:17 hostname org.gnome.Shell.desktop[1310]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough! Mar 02 11:49:25 hostname firefox[1757]: Failed to measure available space: The specified location is not supported Mar 02 11:49:41 hostname org.gnome.Shell.desktop[1310]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough! Mar 02 11:49:41 hostname org.gnome.Shell.desktop[1310]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough! Mar 02 11:49:41 hostname org.gnome.Shell.desktop[1310]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough! Mar 02 11:50:26 hostname org.gnome.Shell.desktop[1310]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough! Mar 02 11:50:27 hostname org.gnome.Shell.desktop[1310]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough! Mar 02 11:50:43 hostname org.gnome.Shell.desktop[1310]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough! Mar 02 11:50:43 hostname org.gnome.Shell.desktop[1310]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough! Mar 02 11:51:50 hostname org.gnome.Shell.desktop[1310]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough! Mar 02 11:51:50 hostname org.gnome.Shell.desktop[1310]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough! Mar 02 11:51:50 hostname org.gnome.Shell.desktop[1310]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough! Mar 02 11:56:38 hostname gnome-shell[1310]: Failed to set the markup of the actor 'ClutterText': Error on line 1: Entity did not end with a semicolon; most likely you used an ampersand character without intending to start an entity - escape ampersand as & Mar 02 11:56:39 hostname nautilus[6412]: g_key_file_load_from_file: assertion 'file != NULL' failed Mar 02 11:56:39 hostname nautilus[6412]: Could not establish a connection to Tracker: Failed to load SPARQL backend: Key file does not have group “DomainOntology” Mar 02 11:56:41 hostname nautilus[6412]: g_key_file_load_from_file: assertion 'file != NULL' failed Mar 02 11:56:41 hostname nautilus[6412]: Could not establish a connection to Tracker: Failed to load SPARQL backend: Key file does not have group “DomainOntology” Mar 02 11:56:41 hostname nautilus[6412]: g_key_file_load_from_file: assertion 'file != NULL' failed Mar 02 11:56:41 hostname nautilus[6412]: Could not establish a connection to Tracker: Failed to load SPARQL backend: Key file does not have group “DomainOntology” Mar 02 11:56:41 hostname nautilus[6412]: g_key_file_load_from_file: assertion 'file != NULL' failed Mar 02 11:56:41 hostname nautilus[6412]: Could not establish a connection to Tracker: Failed to load SPARQL backend: Key file does not have group “DomainOntology” Mar 02 11:56:42 hostname nautilus[6412]: g_key_file_load_from_file: assertion 'file != NULL' failed Mar 02 11:56:42 hostname nautilus[6412]: Could not establish a connection to Tracker: Failed to load SPARQL backend: Key file does not have group “DomainOntology” Mar 02 11:56:43 hostname nautilus[6412]: g_key_file_load_from_file: assertion 'file != NULL' failed Mar 02 11:56:43 hostname nautilus[6412]: Could not establish a connection to Tracker: Failed to load SPARQL backend: Key file does not have group “DomainOntology” Mar 02 11:57:05 hostname nautilus[6412]: g_key_file_load_from_file: assertion 'file != NULL' failed Mar 02 11:57:05 hostname nautilus[6412]: Could not establish a connection to Tracker: Failed to load SPARQL backend: Key file does not have group “DomainOntology” Mar 02 11:57:05 hostname nautilus[6412]: g_key_file_load_from_file: assertion 'file != NULL' failed Mar 02 11:57:05 hostname nautilus[6412]: Could not establish a connection to Tracker: Failed to load SPARQL backend: Key file does not have group “DomainOntology” Mar 02 11:57:05 hostname nautilus[6412]: g_key_file_load_from_file: assertion 'file != NULL' failed Mar 02 11:57:05 hostname nautilus[6412]: Could not establish a connection to Tracker: Failed to load SPARQL backend: Key file does not have group “DomainOntology” Mar 02 11:57:06 hostname nautilus[6412]: g_key_file_load_from_file: assertion 'file != NULL' failed Mar 02 11:57:06 hostname nautilus[6412]: Could not establish a connection to Tracker: Failed to load SPARQL backend: Key file does not have group “DomainOntology” Mar 02 11:57:06 hostname nautilus[6412]: g_key_file_load_from_file: assertion 'file != NULL' failed Mar 02 11:57:06 hostname nautilus[6412]: Could not establish a connection to Tracker: Failed to load SPARQL backend: Key file does not have group “DomainOntology” Mar 02 11:57:06 hostname nautilus[6412]: g_key_file_load_from_file: assertion 'file != NULL' failed Mar 02 11:57:06 hostname nautilus[6412]: Could not establish a connection to Tracker: Failed to load SPARQL backend: Key file does not have group “DomainOntology” Mar 02 11:57:26 hostname nautilus[6412]: g_key_file_load_from_file: assertion 'file != NULL' failed Mar 02 11:57:26 hostname nautilus[6412]: Could not establish a connection to Tracker: Failed to load SPARQL backend: Key file does not have group “DomainOntology” Mar 02 11:57:26 hostname nautilus[6412]: g_key_file_load_from_file: assertion 'file != NULL' failed Mar 02 11:57:26 hostname nautilus[6412]: Could not establish a connection to Tracker: Failed to load SPARQL backend: Key file does not have group “DomainOntology” Mar 02 11:57:26 hostname nautilus[6412]: g_key_file_load_from_file: assertion 'file != NULL' failed Mar 02 11:57:26 hostname nautilus[6412]: Could not establish a connection to Tracker: Failed to load SPARQL backend: Key file does not have group “DomainOntology” Mar 02 11:57:27 hostname nautilus[6412]: g_key_file_load_from_file: assertion 'file != NULL' failed Mar 02 11:57:27 hostname nautilus[6412]: Could not establish a connection to Tracker: Failed to load SPARQL backend: Key file does not have group “DomainOntology” Mar 02 11:57:27 hostname nautilus[6412]: g_key_file_load_from_file: assertion 'file != NULL' failed Mar 02 11:57:27 hostname nautilus[6412]: Could not establish a connection to Tracker: Failed to load SPARQL backend: Key file does not have group “DomainOntology” Mar 02 11:57:28 hostname nautilus[6412]: g_key_file_load_from_file: assertion 'file != NULL' failed Mar 02 11:57:28 hostname nautilus[6412]: Could not establish a connection to Tracker: Failed to load SPARQL backend: Key file does not have group “DomainOntology” Mar 02 11:57:28 hostname nautilus[6412]: g_key_file_load_from_file: assertion 'file != NULL' failed Mar 02 11:57:28 hostname nautilus[6412]: Could not establish a connection to Tracker: Failed to load SPARQL backend: Key file does not have group “DomainOntology” Mar 02 11:57:29 hostname nautilus[6412]: g_key_file_load_from_file: assertion 'file != NULL' failed Mar 02 11:57:29 hostname nautilus[6412]: Could not establish a connection to Tracker: Failed to load SPARQL backend: Key file does not have group “DomainOntology” Mar 02 11:57:30 hostname nautilus[6412]: g_key_file_load_from_file: assertion 'file != NULL' failed Mar 02 11:57:30 hostname nautilus[6412]: Could not establish a connection to Tracker: Failed to load SPARQL backend: Key file does not have group “DomainOntology” Mar 02 11:57:31 hostname nautilus[6412]: g_key_file_load_from_file: assertion 'file != NULL' failed Mar 02 11:57:31 hostname nautilus[6412]: Could not establish a connection to Tracker: Failed to load SPARQL backend: Key file does not have group “DomainOntology” Mar 02 11:57:32 hostname nautilus[6412]: g_key_file_load_from_file: assertion 'file != NULL' failed Mar 02 11:57:32 hostname nautilus[6412]: Could not establish a connection to Tracker: Failed to load SPARQL backend: Key file does not have group “DomainOntology” Mar 02 11:57:32 hostname nautilus[6412]: g_key_file_load_from_file: assertion 'file != NULL' failed Mar 02 11:57:32 hostname nautilus[6412]: Could not establish a connection to Tracker: Failed to load SPARQL backend: Key file does not have group “DomainOntology” Mar 02 11:57:35 hostname nautilus[6412]: g_key_file_load_from_file: assertion 'file != NULL' failed Mar 02 11:57:35 hostname nautilus[6412]: Could not establish a connection to Tracker: Failed to load SPARQL backend: Key file does not have group “DomainOntology” Mar 02 11:57:36 hostname nautilus[6412]: g_key_file_load_from_file: assertion 'file != NULL' failed Mar 02 11:57:36 hostname nautilus[6412]: Could not establish a connection to Tracker: Failed to load SPARQL backend: Key file does not have group “DomainOntology” Mar 02 12:00:21 hostname gnome-shell[1310]: setup_framebuffers: assertion 'width > 0' failed