Xfce Forum

Sub domains
 

You are not logged in.

#1 2021-01-14 15:54:21

Mark7
Member
Registered: 2007-10-05
Posts: 119

Why Does My Xubuntu 20.04 Desktop Keep Freezing?

I have no idea why it happens or when but...

Window decorations don't respond to mouse clicks, nor can the border be grabbed and dragged
Desktop and panel become unresponsive to right button clicks.

I've tried changing the window manager (from xfwm to openbox and pekwm) and the background manager (from xfdesktop to Nitrogen).  Same thing kept happening.  I thought it might be down to Firefox and it's notoriously leaky memory but I've even had the same problem when using other browsers.  My computer is a HP Elitebook 8460P laptop so, whilst it's not exactly new it should still be able to handle a DE like Xfce4.

So what's going on?

Offline

#2 2021-01-14 17:20:59

ToZ
Moderator
From: Canada
Registered: 2011-06-02
Posts: 7,554

Re: Why Does My Xubuntu 20.04 Desktop Keep Freezing?

Mark7 wrote:

Window decorations don't respond to mouse clicks, nor can the border be grabbed and dragged
Desktop and panel become unresponsive to right button clicks.

Sounds like xfwm4 is crashing.

I've tried changing the window manager (from xfwm to openbox and pekwm) and the background manager (from xfdesktop to Nitrogen).  Same thing kept happening.

It is odd that it happens here as well. Maybe a video driver problem?

Is there anything in your ~/.xsession-errors or ~/.xsession-errors.old log files that would indicate a problem with xfwm4 or with your video driver? Note: video driver messages are probably in your journal.

Offline

#3 2021-01-14 19:28:06

Mark7
Member
Registered: 2007-10-05
Posts: 119

Re: Why Does My Xubuntu 20.04 Desktop Keep Freezing?

Looked at the xsessions-errors file.  It appears to be in Greek.  Or it may as well be.

Offline

#4 2021-01-14 21:18:51

ToZ
Moderator
From: Canada
Registered: 2011-06-02
Posts: 7,554

Re: Why Does My Xubuntu 20.04 Desktop Keep Freezing?

Can you post it?

Offline

#5 2021-01-14 22:06:39

Mark7
Member
Registered: 2007-10-05
Posts: 119

Re: Why Does My Xubuntu 20.04 Desktop Keep Freezing?

Don't say you didn't ask for it tongue wink

dbus-update-activation-environment: setting DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
dbus-update-activation-environment: setting DISPLAY=:0
dbus-update-activation-environment: setting XAUTHORITY=/home/mark/.Xauthority
dbus-update-activation-environment: setting QT_ACCESSIBILITY=1
dbus-update-activation-environment: setting SHELL=/bin/bash
dbus-update-activation-environment: setting QT_ACCESSIBILITY=1
dbus-update-activation-environment: setting XDG_CONFIG_DIRS=/etc/xdg/xdg-xubuntu:/etc/xdg
dbus-update-activation-environment: setting XDG_SESSION_PATH=/org/freedesktop/DisplayManager/Session1
dbus-update-activation-environment: setting CLUTTER_BACKEND=x11
dbus-update-activation-environment: setting LANGUAGE=en_GB:en
dbus-update-activation-environment: setting MANDATORY_PATH=/usr/share/gconf/xubuntu.mandatory.path
dbus-update-activation-environment: setting DESKTOP_SESSION=xubuntu
dbus-update-activation-environment: setting GTK_MODULES=appmenu-gtk-module
dbus-update-activation-environment: setting PWD=/home/mark
dbus-update-activation-environment: setting XDG_SESSION_DESKTOP=xubuntu
dbus-update-activation-environment: setting LOGNAME=mark
dbus-update-activation-environment: setting QT_QPA_PLATFORMTHEME=gtk2
dbus-update-activation-environment: setting XDG_SESSION_TYPE=x11
dbus-update-activation-environment: setting GPG_AGENT_INFO=/run/user/1000/gnupg/S.gpg-agent:0:1
dbus-update-activation-environment: setting XAUTHORITY=/home/mark/.Xauthority
dbus-update-activation-environment: setting XDG_GREETER_DATA_DIR=/var/lib/lightdm-data/mark
dbus-update-activation-environment: setting GDM_LANG=en_GB
dbus-update-activation-environment: setting HOME=/home/mark
dbus-update-activation-environment: setting IM_CONFIG_PHASE=1
dbus-update-activation-environment: setting LANG=en_GB.UTF-8
dbus-update-activation-environment: setting XDG_CURRENT_DESKTOP=XFCE
dbus-update-activation-environment: setting XDG_SEAT_PATH=/org/freedesktop/DisplayManager/Seat0
dbus-update-activation-environment: setting XDG_SESSION_CLASS=user
dbus-update-activation-environment: setting GTK_OVERLAY_SCROLLING=0
dbus-update-activation-environment: setting DEFAULTS_PATH=/usr/share/gconf/xubuntu.default.path
dbus-update-activation-environment: setting USER=mark
dbus-update-activation-environment: setting DISPLAY=:0
dbus-update-activation-environment: setting SHLVL=1
dbus-update-activation-environment: setting UBUNTU_MENUPROXY=1
dbus-update-activation-environment: setting XDG_RUNTIME_DIR=/run/user/1000
dbus-update-activation-environment: setting XDG_DATA_DIRS=/usr/share/xubuntu:/usr/share/xfce4:/usr/local/share:/usr/share:/var/lib/snapd/desktop
dbus-update-activation-environment: setting PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin
dbus-update-activation-environment: setting GDMSESSION=xubuntu
dbus-update-activation-environment: setting DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
dbus-update-activation-environment: setting _=/usr/bin/dbus-update-activation-environment
xfce4-session-Message: 15:45:50.237: SSH authentication agent is already running
gpg-agent[3547]: WARNING: "--write-env-file" is an obsolete option - it has no effect
gpg-agent: a gpg-agent is already running - not starting a new one

(xfce4-session:3439): xfce4-session-WARNING **: 15:45:50.244: gpg-agent returned no PID in the variables

** (xfce4-clipman:3669): WARNING **: 15:45:51.722: Unable to register GApplication: An object is already exported for the interface org.gtk.Application at /org/xfce/clipman

(xfce4-clipman:3669): GLib-GIO-CRITICAL **: 15:45:51.722: g_application_get_is_remote: assertion 'application->priv->is_registered' failed

(xfce4-clipman:3669): GLib-WARNING **: 15:45:51.722: g_set_application_name() called multiple times
Gtk-Message: 15:45:52.467: Failed to load module "appmenu-gtk-module"

(wrapper-2.0:3756): Gtk-WARNING **: 15:45:52.503: Negative content width -3 (allocation 1, extents 2x2) while allocating gadget (node button, owner GtkButton)

(wrapper-2.0:3803): Gtk-WARNING **: 15:45:52.503: gtk_widget_size_allocate(): attempt to allocate widget with width -1 and height 22

(wrapper-2.0:3818): GLib-GIO-CRITICAL **: 15:45:52.564: g_file_new_for_path: assertion 'path != NULL' failed

(wrapper-2.0:3818): GLib-GIO-CRITICAL **: 15:45:52.579: g_file_monitor_file: assertion 'G_IS_FILE (file)' failed

(wrapper-2.0:3818): GLib-GObject-WARNING **: 15:45:52.579: invalid (NULL) pointer instance

(wrapper-2.0:3818): GLib-GObject-CRITICAL **: 15:45:52.579: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed

(wrapper-2.0:3818): Gtk-WARNING **: 15:45:52.579: Attempting to add a widget with type GtkToggleButton to a container of type XfcePanelPlugin, but the widget is already inside a container of type XfcePanelPlugin, please remove the widget from its existing container first.

(twinux:3588): Gtk-WARNING **: 15:45:52.568: Theme parsing error: gtk.css:1555:23: 'font-feature-settings' is not a valid property name

(twinux:3588): Gtk-WARNING **: 15:45:52.617: Theme parsing error: gtk.css:3591:25: 'font-feature-settings' is not a valid property name

(twinux:3588): Gtk-WARNING **: 15:45:52.620: Theme parsing error: gtk.css:4053:23: 'font-feature-settings' is not a valid property name

(wrapper-2.0:3718): Gtk-WARNING **: 15:45:52.627: Negative content width -19 (allocation 1, extents 10x10) while allocating gadget (node button, owner PlacesButton)

(wrapper-2.0:3811): Gtk-WARNING **: 15:45:52.642: Negative content width -1 (allocation 1, extents 1x1) while allocating gadget (node border, owner GtkFrame)

(wrapper-2.0:3818): Gtk-WARNING **: 15:45:52.718: Negative content width -3 (allocation 1, extents 2x2) while allocating gadget (node button, owner GtkToggleButton)

(wrapper-2.0:3814): Gtk-WARNING **: 15:45:52.753: gtk_widget_size_allocate(): attempt to allocate widget with width -3 and height 20

(wrapper-2.0:3830): Gtk-WARNING **: 15:45:52.974: Negative content width -3 (allocation 1, extents 2x2) while allocating gadget (node button, owner PulseaudioButton)

** (xfce4-volumed:4046): WARNING **: 15:45:53.022: Binding 'XF86AudioRaiseVolume' failed!

** (xfce4-volumed:4046): WARNING **: 15:45:53.033: Binding 'XF86AudioLowerVolume' failed!

** (xfce4-volumed:4046): WARNING **: 15:45:53.044: Binding 'XF86AudioMute' failed!
weather-Message: 15:45:53.222: getting [url]https://api.met.no/weatherapi/locationforecast/1.9/?lat=52.604900&lon=-1.148800&msl=66[/url]
error: autostart failed for the following apps:
- "ubuntu-software-service.desktop": skipped: current desktop ["XFCE"] not included in ["GNOME" "Unity"]
- "yakyak.desktop": cannot match desktop file with snap yakyak applications

Gtk-Message: 15:45:53.663: Failed to load module "appmenu-gtk-module"

(wrapper-2.0:3834): Gtk-WARNING **: 15:45:53.697: Negative content width -3 (allocation 1, extents 2x2) while allocating gadget (node button, owner GtkToggleButton)

(liferea:3668): Gtk-WARNING **: 15:45:53.746: Theme parsing error: gtk.css:1555:23: 'font-feature-settings' is not a valid property name

(liferea:3668): Gtk-WARNING **: 15:45:53.794: Theme parsing error: gtk.css:3591:25: 'font-feature-settings' is not a valid property name

(liferea:3668): Gtk-WARNING **: 15:45:53.803: Theme parsing error: gtk.css:4053:23: 'font-feature-settings' is not a valid property name

** (xfce4-screensaver:4069): WARNING **: 15:45:53.917: screensaver already running in this session

(polkit-gnome-authentication-agent-1:4076): GLib-CRITICAL **: 15:45:54.021: g_variant_new_string: assertion 'string != NULL' failed

(polkit-gnome-authentication-agent-1:4076): polkit-gnome-1-WARNING **: 15:45:54.022: Failed to register client: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files
Error creating DBus server : Error binding to address: Permission denied
Gtk-Message: 15:45:54.535: Failed to load module "appmenu-gtk-module"
Gtk-Message: 15:45:55.189: Failed to load module "appmenu-gtk-module"

(caprine:3719): Gtk-WARNING **: 15:45:55.236: Theme parsing error: gtk.css:1555:23: 'font-feature-settings' is not a valid property name

(caprine:3719): Gtk-WARNING **: 15:45:55.266: Theme parsing error: gtk.css:3591:25: 'font-feature-settings' is not a valid property name

(caprine:3719): Gtk-WARNING **: 15:45:55.288: Theme parsing error: gtk.css:4053:23: 'font-feature-settings' is not a valid property name
Gtk-Message: 15:45:55.288: Failed to load module "appmenu-gtk-module"
(node:3667) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.

(yakyak:3577): Gtk-WARNING **: 15:45:55.365: Theme parsing error: gtk.css:1555:23: 'font-feature-settings' is not a valid property name

(yakyak:3577): Gtk-WARNING **: 15:45:55.374: Theme parsing error: gtk.css:3591:25: 'font-feature-settings' is not a valid property name

(yakyak:3577): Gtk-WARNING **: 15:45:55.376: Theme parsing error: gtk.css:4053:23: 'font-feature-settings' is not a valid property name
Gtk-Message: 15:45:55.387: Failed to load module "appmenu-gtk-module"

(Discord:3667): Gtk-WARNING **: 15:45:55.440: Theme parsing error: gtk.css:1555:23: 'font-feature-settings' is not a valid property name

(Discord:3667): Gtk-WARNING **: 15:45:55.453: Theme parsing error: gtk.css:3591:25: 'font-feature-settings' is not a valid property name

(Discord:3667): Gtk-WARNING **: 15:45:55.475: Theme parsing error: gtk.css:4053:23: 'font-feature-settings' is not a valid property name
blueman-applet 15.45.56 WARNING  PluginManager:147 __load_plugin: Not loading DhcpClient because its conflict has higher priority

** (liferea:3668): CRITICAL **: 15:45:56.561: secret_service_load_collections_sync: assertion 'paths != NULL' failed

** (liferea:3668): CRITICAL **: 15:45:56.572: secret_service_load_collections_sync: assertion 'paths != NULL' failed

** (liferea:3668): CRITICAL **: 15:45:56.577: secret_service_load_collections_sync: assertion 'paths != NULL' failed

** (liferea:3668): CRITICAL **: 15:45:56.604: secret_service_load_collections_sync: assertion 'paths != NULL' failed

** (liferea:3668): CRITICAL **: 15:45:56.615: secret_service_load_collections_sync: assertion 'paths != NULL' failed

** (liferea:3668): CRITICAL **: 15:45:56.620: secret_service_load_collections_sync: assertion 'paths != NULL' failed

** (liferea:3668): CRITICAL **: 15:45:56.626: secret_service_load_collections_sync: assertion 'paths != NULL' failed

** (liferea:3668): CRITICAL **: 15:45:56.634: secret_service_load_collections_sync: assertion 'paths != NULL' failed

** (liferea:3668): CRITICAL **: 15:45:56.650: secret_service_load_collections_sync: assertion 'paths != NULL' failed

** (liferea:3668): CRITICAL **: 15:45:56.677: secret_service_load_collections_sync: assertion 'paths != NULL' failed

** (liferea:3668): CRITICAL **: 15:45:56.683: secret_service_load_collections_sync: assertion 'paths != NULL' failed

** (liferea:3668): CRITICAL **: 15:45:56.689: secret_service_load_collections_sync: assertion 'paths != NULL' failed

** (liferea:3668): CRITICAL **: 15:45:56.702: secret_service_load_collections_sync: assertion 'paths != NULL' failed

** (liferea:3668): CRITICAL **: 15:45:56.707: secret_service_load_collections_sync: assertion 'paths != NULL' failed

** (liferea:3668): CRITICAL **: 15:45:56.714: secret_service_load_collections_sync: assertion 'paths != NULL' failed

** (liferea:3668): CRITICAL **: 15:45:56.733: secret_service_load_collections_sync: assertion 'paths != NULL' failed

** (liferea:3668): CRITICAL **: 15:45:56.739: secret_service_load_collections_sync: assertion 'paths != NULL' failed

** (liferea:3668): CRITICAL **: 15:45:56.744: secret_service_load_collections_sync: assertion 'paths != NULL' failed
blueman-applet 15.45.57 WARNING  PluginManager:147 __load_plugin: Not loading PPPSupport because its conflict has higher priority
Traceback (most recent call last):
  File "/usr/bin/unity-mail", line 12, in <module>
    UnityMail()
  File "/usr/share/unity-mail/UnityMail/application.py", line 165, in __init__
    self.oMessagingMenu = MessagingMenu(self.onMenuItemClicked, self.openDialog, self.updateMessageAges)
  File "/usr/share/unity-mail/UnityMail/__init__.py", line 121, in __init__
    nVersion = int(platform.linux_distribution()[1].replace('.', ''))
AttributeError: module 'platform' has no attribute 'linux_distribution'

(WebKitWebProcess:4257): Gtk-WARNING **: 15:45:57.733: Theme parsing error: gtk.css:1555:23: 'font-feature-settings' is not a valid property name

(WebKitWebProcess:4257): Gtk-WARNING **: 15:45:57.780: Theme parsing error: gtk.css:3591:25: 'font-feature-settings' is not a valid property name

(WebKitWebProcess:4257): Gtk-WARNING **: 15:45:57.783: Theme parsing error: gtk.css:4053:23: 'font-feature-settings' is not a valid property name

(WebKitWebProcess:4257): Gtk-WARNING **: 15:45:57.934: Theme parsing error: gtk.css:1566:23: 'font-feature-settings' is not a valid property name

(WebKitWebProcess:4257): Gtk-WARNING **: 15:45:57.943: Theme parsing error: gtk.css:3616:25: 'font-feature-settings' is not a valid property name

(WebKitWebProcess:4257): Gtk-WARNING **: 15:45:57.947: Theme parsing error: gtk.css:4078:23: 'font-feature-settings' is not a valid property name

(xfce4-session:3439): xfce4-session-WARNING **: 15:46:13.598: xfsm_client.c:builder_add_value: Value type not supported

(xfce4-session:3439): xfce4-session-WARNING **: 15:46:13.654: xfsm_client.c:builder_add_value: Value type not supported

(xfce4-session:3439): xfce4-session-WARNING **: 15:46:13.659: xfsm_client.c:builder_add_value: Value type not supported

(xfce4-session:3439): xfce4-session-WARNING **: 15:46:13.660: xfsm_client.c:builder_add_value: Value type not supported

(xfce4-session:3439): xfce4-session-WARNING **: 15:46:13.660: xfsm_client.c:builder_add_value: Value type not supported

(xfce4-session:3439): xfce4-session-WARNING **: 15:46:13.662: xfsm_client.c:builder_add_value: Value type not supported

(xfce4-session:3439): xfce4-session-WARNING **: 15:46:13.674: xfsm_client.c:builder_add_value: Value type not supported

(xfce4-session:3439): xfce4-session-WARNING **: 15:46:13.674: xfsm_client.c:builder_add_value: Value type not supported

(xfce4-session:3439): xfce4-session-WARNING **: 15:46:13.674: xfsm_client.c:builder_add_value: Value type not supported

(xfce4-session:3439): xfce4-session-WARNING **: 15:46:13.674: xfsm_client.c:builder_add_value: Value type not supported

(xfce4-panel:3556): Gtk-CRITICAL **: 15:54:56.393: gtk_widget_grab_default: assertion 'gtk_widget_get_can_default (widget)' failed

(wrapper-2.0:5300): Gtk-WARNING **: 15:55:05.106: Negative content width -3 (allocation 1, extents 2x2) while allocating gadget (node button, owner GtkToggleButton)

(xfce4-panel:3556): Gtk-CRITICAL **: 15:55:09.440: gtk_icon_theme_load_icon: assertion 'icon_name != NULL' failed

(wrapper-2.0:5300): Gdk-CRITICAL **: 15:59:39.022: Window 0x55fda51f1270 has not been made visible in GdkSeatGrabPrepareFunc
JavaScript error: resource:///modules/activity/autosync.jsm, line 251: uncaught exception: 2147746065
JavaScript error: resource:///modules/activity/autosync.jsm, line 251: uncaught exception: 2147746065
JavaScript error: resource:///modules/activity/autosync.jsm, line 251: uncaught exception: 2147746065
JavaScript error: resource:///modules/activity/autosync.jsm, line 251: uncaught exception: 2147746065
JavaScript error: resource:///modules/activity/autosync.jsm, line 251: uncaught exception: 2147746065

(xfce4-taskmanager:6368): dbind-WARNING **: 16:08:35.741: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

(xfce4-taskmanager:6373): dbind-WARNING **: 16:08:36.348: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
JavaScript error: resource:///modules/activity/autosync.jsm, line 251: uncaught exception: 2147746065
JavaScript error: resource:///modules/activity/autosync.jsm, line 251: uncaught exception: 2147746065

(xfce4-taskmanager:6431): dbind-WARNING **: 16:10:41.246: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

(xfce4-settings-manager:6451): dbind-WARNING **: 16:11:04.280: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

(xfce4-session-settings:6458): dbind-WARNING **: 16:11:10.898: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

(xfce4-session:3439): xfce4-session-WARNING **: 16:11:10.938: xfsm_client.c:builder_add_value: Value type not supported

(xfce4-session:3439): xfce4-session-WARNING **: 16:11:10.970: xfsm_client.c:builder_add_value: Value type not supported

(xfce4-session:3439): xfce4-session-WARNING **: 16:11:11.007: xfsm_client.c:builder_add_value: Value type not supported

(xfce4-session:3439): xfce4-session-WARNING **: 16:11:11.007: xfsm_client.c:builder_add_value: Value type not supported

(xfce4-session:3439): xfce4-session-WARNING **: 16:11:11.008: xfsm_client.c:builder_add_value: Value type not supported

(xfce4-session:3439): xfce4-session-WARNING **: 16:11:11.012: xfsm_client.c:builder_add_value: Value type not supported

(xfce4-session:3439): xfce4-session-WARNING **: 16:11:11.018: xfsm_client.c:builder_add_value: Value type not supported

(xfce4-session:3439): xfce4-session-WARNING **: 16:11:11.018: xfsm_client.c:builder_add_value: Value type not supported

(xfce4-session:3439): xfce4-session-WARNING **: 16:11:11.018: xfsm_client.c:builder_add_value: Value type not supported

(xfce4-session:3439): xfce4-session-WARNING **: 16:11:11.018: xfsm_client.c:builder_add_value: Value type not supported

(xfce4-session:3439): xfce4-session-WARNING **: 16:11:11.021: xfsm_client.c:builder_add_value: Value type not supported

(xfce4-session:3439): xfce4-session-WARNING **: 16:11:11.021: xfsm_client.c:builder_add_value: Value type not supported

(xfce4-session:3439): xfce4-session-WARNING **: 16:11:11.021: xfsm_client.c:builder_add_value: Value type not supported

(xfce4-session:3439): xfce4-session-WARNING **: 16:11:11.021: xfsm_client.c:builder_add_value: Value type not supported

(birdtray:6803): dbind-WARNING **: 16:20:09.463: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

(wrapper-2.0:3810): LIBDBUSMENU-GLIB-WARNING **: 16:21:24.913: Unable to replace properties on 0: Error getting properties for ID

(wrapper-2.0:3810): LIBDBUSMENU-GLIB-WARNING **: 16:22:47.954: Getting layout failed: Operation was cancelled

(pavucontrol:6910): dbind-WARNING **: 16:24:53.654: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

(xfce4-volumed:4046): xfce4-volumed-WARNING **: 16:24:56.902: xvd_update_sink_callback: invalid argument

(thunar-volman:6963): dbind-WARNING **: 16:25:22.063: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
thunar-volman: Unsupported USB device type "usb".

(thunar-volman:6970): dbind-WARNING **: 16:25:22.505: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
thunar-volman: Unsupported USB device type "snd-usb-audio".

(thunar-volman:6975): dbind-WARNING **: 16:25:22.594: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
thunar-volman: Unsupported USB device type "(null)".

(thunar-volman:6980): dbind-WARNING **: 16:25:22.687: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
thunar-volman: Unsupported USB device type "snd-usb-audio".

(thunar-volman:6985): dbind-WARNING **: 16:25:22.786: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
thunar-volman: Unsupported USB device type "usb-storage".

(thunar-volman:6990): dbind-WARNING **: 16:25:22.886: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
thunar-volman: Unsupported USB device type "snd-usb-audio".

(thunar-volman:7018): dbind-WARNING **: 16:25:24.615: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
thunar-volman: Unknown block device type "disk".

(thunar-volman:7036): dbind-WARNING **: 16:25:24.856: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

(exo-open:7132): dbind-WARNING **: 16:25:33.343: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

(exo-helper-2:7140): dbind-WARNING **: 16:25:33.495: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
weather-Message: 16:45:53.227: getting [url]https://api.met.no/weatherapi/locationforecast/1.9/?lat=52.604900&lon=-1.148800&msl=66[/url]
gweled: ../nptl/pthread_mutex_lock.c:438: __pthread_mutex_lock_full: Assertion `robust || (oldval & FUTEX_OWNER_DIED) == 0' failed.

###!!! [Parent][RunMessage] Error: Channel closing: too late to send/recv, messages will be lost

[Child 7428, MediaDecoderStateMachine #1] WARNING: Decoder=7f6ea9b9e800 Decode error: NS_ERROR_DOM_MEDIA_FATAL_ERR (0x806e0005) - RefPtr<MediaSourceTrackDemuxer::SamplesPromise> mozilla::MediaSourceTrackDemuxer::DoGetSamples(int32_t): manager is detached.: file /build/firefox-3wnhso/firefox-84.0.2+build1/dom/media/MediaDecoderStateMachine.cpp:3471
[Child 7428, MediaDecoderStateMachine #1] WARNING: Decoder=7f6ea9b9e800 Decode error: NS_ERROR_DOM_MEDIA_FATAL_ERR (0x806e0005) - RefPtr<MediaSourceTrackDemuxer::SamplesPromise> mozilla::MediaSourceTrackDemuxer::DoGetSamples(int32_t): manager is detached.: file /build/firefox-3wnhso/firefox-84.0.2+build1/dom/media/MediaDecoderStateMachine.cpp:3471
[Child 7428, MediaDecoderStateMachine #1] WARNING: Decoder=7f6eaa8e1800 Decode error: NS_ERROR_DOM_MEDIA_FATAL_ERR (0x806e0005) - RefPtr<MediaSourceTrackDemuxer::SamplesPromise> mozilla::MediaSourceTrackDemuxer::DoGetSamples(int32_t): manager is detached.: file /build/firefox-3wnhso/firefox-84.0.2+build1/dom/media/MediaDecoderStateMachine.cpp:3471
[Child 7428, MediaDecoderStateMachine #1] WARNING: Decoder=7f6eaa8e1800 Decode error: NS_ERROR_DOM_MEDIA_FATAL_ERR (0x806e0005) - RefPtr<MediaSourceTrackDemuxer::SamplesPromise> mozilla::MediaSourceTrackDemuxer::DoGetSamples(int32_t): manager is detached.: file /build/firefox-3wnhso/firefox-84.0.2+build1/dom/media/MediaDecoderStateMachine.cpp:3471

(exo-open:9014): dbind-WARNING **: 17:42:02.322: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

(exo-helper-2:9021): dbind-WARNING **: 17:42:02.529: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
weather-Message: 17:45:53.212: getting [url]https://api.met.no/weatherapi/locationforecast/1.9/?lat=52.604900&lon=-1.148800&msl=66[/url]
[Child 9835, MediaDecoderStateMachine #1] WARNING: Decoder=7f9a069f4c00 Decode error: NS_ERROR_DOM_MEDIA_FATAL_ERR (0x806e0005) - RefPtr<MediaSourceTrackDemuxer::SamplesPromise> mozilla::MediaSourceTrackDemuxer::DoGetSamples(int32_t): manager is detached.: file /build/firefox-3wnhso/firefox-84.0.2+build1/dom/media/MediaDecoderStateMachine.cpp:3471
[Child 9835, MediaDecoderStateMachine #1] WARNING: Decoder=7f9a069f4c00 Decode error: NS_ERROR_DOM_MEDIA_FATAL_ERR (0x806e0005) - RefPtr<MediaSourceTrackDemuxer::SamplesPromise> mozilla::MediaSourceTrackDemuxer::DoGetSamples(int32_t): manager is detached.: file /build/firefox-3wnhso/firefox-84.0.2+build1/dom/media/MediaDecoderStateMachine.cpp:3471

(exo-open:10771): dbind-WARNING **: 18:34:04.388: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

(exo-helper-2:10777): dbind-WARNING **: 18:34:04.556: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
JavaScript error: resource:///modules/activity/autosync.jsm, line 251: uncaught exception: 2147746065
weather-Message: 18:45:53.236: getting [url]https://api.met.no/weatherapi/locationforecast/1.9/?lat=52.604900&lon=-1.148800&msl=66[/url]

(exo-helper-2:12593): dbind-WARNING **: 19:15:58.389: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

(mousepad:12654): dbind-WARNING **: 19:16:34.850: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

(helper-dialog:14157): dbind-WARNING **: 19:39:00.194: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Memory pressure relief: Total: res = 8232960/7577600/-655360, res+swap = 8327168/7626752/-700416
Memory pressure relief: Total: res = 7634944/7659520/24576, res+swap = 7643136/7643136/0
weather-Message: 19:45:53.234: getting [url]https://api.met.no/weatherapi/locationforecast/1.9/?lat=52.604900&lon=-1.148800&msl=66[/url]
(node:3577) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 click listeners added to [EventEmitter]. Use emitter.setMaxListeners() to increase limit

(exo-helper-2:16844): dbind-WARNING **: 20:33:52.690: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

(mousepad:16867): dbind-WARNING **: 20:34:01.106: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

(mousepad:16867): Gtk-WARNING **: 20:34:58.398: Negative content width -19 (allocation 1, extents 10x10) while allocating gadget (node button, owner GtkToggleButton)

(mousepad:16867): Gtk-WARNING **: 20:34:58.398: Negative content height -9 (allocation 1, extents 5x5) while allocating gadget (node button, owner GtkToggleButton)
weather-Message: 20:37:25.211: getting [url]https://api.met.no/weatherapi/sunrise/2.0/?lat=52.604900&lon=-1.148800&date=2021-01-14&offset=+00:00&days=10[/url]

(exo-open:16994): dbind-WARNING **: 20:40:43.684: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

(exo-helper-2:17000): dbind-WARNING **: 20:40:43.756: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
JavaScript error: resource:///modules/activity/autosync.jsm, line 251: uncaught exception: 2147746065
weather-Message: 20:45:53.211: getting [url]https://api.met.no/weatherapi/locationforecast/1.9/?lat=52.604900&lon=-1.148800&msl=66[/url]
IPDL protocol error: Handler returned error code!

###!!! [Parent][DispatchAsyncMessage] Error: PMessagePort::Msg_PostMessages Processing error: message was deserialized, but the handler returned false (indicating failure)

JavaScript error: resource:///modules/activity/autosync.jsm, line 251: uncaught exception: 2147746065

(helper-dialog:17788): dbind-WARNING **: 21:03:34.264: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

(helper-dialog:18090): dbind-WARNING **: 21:26:15.453: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

(xfrun4:18095): dbind-WARNING **: 21:26:16.369: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

(xfwm4:3549): Gdk-ERROR **: 21:26:20.214: The program 'xfwm4' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadValue (integer parameter out of range for operation)'.
  (Details: serial 343991 error_code 2 request_code 113 (core protocol) minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the GDK_SYNCHRONIZE environment
   variable to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)

(xfwm4:18125): dbind-WARNING **: 21:26:33.262: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

(xfwm4:18134): dbind-WARNING **: 21:26:42.452: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

(exo-helper-2:18336): dbind-WARNING **: 21:26:52.504: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

(mousepad:18670): dbind-WARNING **: 21:27:06.634: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

(mousepad:18670): Gtk-WARNING **: 21:27:12.672: Negative content width -19 (allocation 1, extents 10x10) while allocating gadget (node button, owner GtkToggleButton)

(mousepad:18670): Gtk-WARNING **: 21:27:12.672: Negative content height -9 (allocation 1, extents 5x5) while allocating gadget (node button, owner GtkToggleButton)
weather-Message: 21:45:53.212: getting [url]https://api.met.no/weatherapi/locationforecast/1.9/?lat=52.604900&lon=-1.148800&msl=66[/url]
[Child 9095, MediaDecoderStateMachine #1] WARNING: Decoder=7f2f0d7ba000 Decode error: NS_ERROR_DOM_MEDIA_FATAL_ERR (0x806e0005) - RefPtr<MediaSourceTrackDemuxer::SamplesPromise> mozilla::MediaSourceTrackDemuxer::DoGetSamples(int32_t): manager is detached.: file /build/firefox-3wnhso/firefox-84.0.2+build1/dom/media/MediaDecoderStateMachine.cpp:3471
[Child 9095, MediaDecoderStateMachine #1] WARNING: Decoder=7f2f0d7ba000 Decode error: NS_ERROR_DOM_MEDIA_FATAL_ERR (0x806e0005) - RefPtr<MediaSourceTrackDemuxer::SamplesPromise> mozilla::MediaSourceTrackDemuxer::DoGetSamples(int32_t): manager is detached.: file /build/firefox-3wnhso/firefox-84.0.2+build1/dom/media/MediaDecoderStateMachine.cpp:3471
[Child 9095, MediaDecoderStateMachine #1] WARNING: Decoder=7f2f0d7ba000 Decode error: NS_ERROR_DOM_MEDIA_FATAL_ERR (0x806e0005) - RefPtr<MediaSourceTrackDemuxer::SamplesPromise> mozilla::MediaSourceTrackDemuxer::DoGetSamples(int32_t): manager is detached.: file /build/firefox-3wnhso/firefox-84.0.2+build1/dom/media/MediaDecoderStateMachine.cpp:3471
[Child 9095, MediaDecoderStateMachine #1] WARNING: Decoder=7f2f0d7ba000 Decode error: NS_ERROR_DOM_MEDIA_FATAL_ERR (0x806e0005) - RefPtr<MediaSourceTrackDemuxer::SamplesPromise> mozilla::MediaSourceTrackDemuxer::DoGetSamples(int32_t): manager is detached.: file /build/firefox-3wnhso/firefox-84.0.2+build1/dom/media/MediaDecoderStateMachine.cpp:3471
[Child 9095, MediaDecoderStateMachine #1] WARNING: Decoder=7f2f0d7ba000 Decode error: NS_ERROR_DOM_MEDIA_FATAL_ERR (0x806e0005) - RefPtr<MediaSourceTrackDemuxer::SamplesPromise> mozilla::MediaSourceTrackDemuxer::DoGetSamples(int32_t): manager is detached.: file /build/firefox-3wnhso/firefox-84.0.2+build1/dom/media/MediaDecoderStateMachine.cpp:3471
[Child 9095, MediaDecoderStateMachine #1] WARNING: Decoder=7f2f0d7ba000 Decode error: NS_ERROR_DOM_MEDIA_FATAL_ERR (0x806e0005) - RefPtr<MediaSourceTrackDemuxer::SamplesPromise> mozilla::MediaSourceTrackDemuxer::DoGetSamples(int32_t): manager is detached.: file /build/firefox-3wnhso/firefox-84.0.2+build1/dom/media/MediaDecoderStateMachine.cpp:3471
[Child 9095, MediaDecoderStateMachine #1] WARNING: Decoder=7f2f0d7ba000 Decode error: NS_ERROR_DOM_MEDIA_FATAL_ERR (0x806e0005) - RefPtr<MediaSourceTrackDemuxer::SamplesPromise> mozilla::MediaSourceTrackDemuxer::DoGetSamples(int32_t): manager is detached.: file /build/firefox-3wnhso/firefox-84.0.2+build1/dom/media/MediaDecoderStateMachine.cpp:3471
[Child 9095, MediaDecoderStateMachine #1] WARNING: Decoder=7f2f0d7ba000 Decode error: NS_ERROR_DOM_MEDIA_FATAL_ERR (0x806e0005) - RefPtr<MediaSourceTrackDemuxer::SamplesPromise> mozilla::MediaSourceTrackDemuxer::DoGetSamples(int32_t): manager is detached.: file /build/firefox-3wnhso/firefox-84.0.2+build1/dom/media/MediaDecoderStateMachine.cpp:3471

(exo-open:19495): dbind-WARNING **: 22:04:01.448: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

(exo-helper-2:19501): dbind-WARNING **: 22:04:01.527: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

(exo-helper-2:19685): dbind-WARNING **: 22:05:25.567: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

(mousepad:19705): dbind-WARNING **: 22:05:32.033: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

ToZ: added code tags

Last edited by ToZ (2021-01-14 23:50:21)

Offline

#6 2021-01-14 23:55:13

ToZ
Moderator
From: Canada
Registered: 2011-06-02
Posts: 7,554

Re: Why Does My Xubuntu 20.04 Desktop Keep Freezing?

Well, there is an xfwm4 crash there:

(xfwm4:3549): Gdk-ERROR **: 21:26:20.214: The program 'xfwm4' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadValue (integer parameter out of range for operation)'.
  (Details: serial 343991 error_code 2 request_code 113 (core protocol) minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the GDK_SYNCHRONIZE environment
   variable to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)

What does the following return:

coredumpctl coredumpctl | grep xfwm4

Can you run the following command:

GDK_SYNCHRONIZE=1 xfwm4 --replace &

...and when xfwm4 crashes again and you recover, post back the results of:

coredumpctl info xfwm4 --no-pager

Offline

#7 2021-01-15 09:32:24

Mark7
Member
Registered: 2007-10-05
Posts: 119

Re: Why Does My Xubuntu 20.04 Desktop Keep Freezing?

It said

Unknown operation coredumpctl.

And that was after I installed systemd-coredump after the first attempt to run it

Offline

#8 2021-01-15 11:27:24

ToZ
Moderator
From: Canada
Registered: 2011-06-02
Posts: 7,554

Re: Why Does My Xubuntu 20.04 Desktop Keep Freezing?

I forgot that ubuntu uses something different. Follow the instructions in the answer here and post back the backtrace (bt) that is generated (after running "GDK_SYNCHRONIZE=1 xfwm4 --replace &" and getting xfwm4 to crash).

Offline

#9 2021-01-15 12:26:35

Mark7
Member
Registered: 2007-10-05
Posts: 119

Re: Why Does My Xubuntu 20.04 Desktop Keep Freezing?

Okay,  I ran "$ apport-unpack /var/crash/_usr_bin_xfwm4.1000.crash ~/Unpack" and got a folder full of files, none of which is called backtrace or bt, aftetr crashing xfwm4.

So what am I looking for?

Offline

#10 2021-01-15 13:56:25

ToZ
Moderator
From: Canada
Registered: 2011-06-02
Posts: 7,554

Re: Why Does My Xubuntu 20.04 Desktop Keep Freezing?

I don't have an ubuntu system handy to verify, but according to that answer, the following should work:

cd ~/Unpack
gdb `cat /usr/bin/xfwm4` CoreDump

...and at the gdb> prompt, run:

bt

...to generate the backtrace.

Offline

#11 2021-01-15 15:02:04

Mark7
Member
Registered: 2007-10-05
Posts: 119

Re: Why Does My Xubuntu 20.04 Desktop Keep Freezing?

Ugh.  Ran that.  Got

bash: warning: command substitution: ignored null byte in input
gdb: unrecognised option

What is the null byte that is being ignored?

Just to be clear, the bash warning came after running the gdb `cat /usr/bin/xfwm4` CoreDump command

Last edited by Mark7 (2021-01-15 15:45:54)

Offline

#12 2021-01-15 21:46:26

Mark7
Member
Registered: 2007-10-05
Posts: 119

Re: Why Does My Xubuntu 20.04 Desktop Keep Freezing?

I'm still stuck.

Is there a way to remove xfwm4 without losing the rest of xfce?

Offline

#13 2021-01-16 17:24:57

mint4all
Member
From: out of sight
Registered: 2018-08-21
Posts: 168

Re: Why Does My Xubuntu 20.04 Desktop Keep Freezing?

Greetings!

My apology for chiming in late. With utmost respect to ToZ -- he is a giant among us -- I have a different take on your system's xsessions' error log. I've run into this problem on a friend's HP Pavilion laptop of recent issue (2019, dual boot Win-10 & Mint 19.3 XFCE). The problem: firefox had crashed and badly corrupted the ext4 volume. After during repairing the volume with fsck.ext4 (verbose) I observed many files related to xfce crosslinked with firefox's sesssion cache.

Regrettably, even after restoring the system using Mint's latest "timeshift" backup, the XFCE desktop was hopelessly corrupted and had to be reinstalled and recustomized. The upshot is: you may have defective memory (running out of memory can lock up the entire system, a poblem i'm running into occasionally on the old apple imac), or a corrupted volume, or a failing  harddrive. Can you boot your system with a live dvd or usb stick, and test your system that way?

I found that compared to other DEs (Cinnamon, Mate, KDE, Gnome) XFCE is the most robust and forgiving one, with nary a memory leak or other hickups. Just trying to help ...

Cheers, m4a


Linux Mint 18.3, 19.3, 20.0 -- xfce 4.12 & 4.14... Apple IMAC 11,3 -- Dell Precision T1500 Desktops -- Toshiba Satellite, Dell Inspiron & HP Pavilion Laptops -- Family & Community Support re. Linux

Offline

#14 2021-01-16 18:58:17

Mark7
Member
Registered: 2007-10-05
Posts: 119

Re: Why Does My Xubuntu 20.04 Desktop Keep Freezing?

I can boot it with a USB.  What should I do after that?

Offline

#15 2021-01-16 18:58:40

ToZ
Moderator
From: Canada
Registered: 2011-06-02
Posts: 7,554

Re: Why Does My Xubuntu 20.04 Desktop Keep Freezing?

Sorry, busy evaluating proposals. I don't have access to an ubuntu system with crash files that I can test with. Perhaps ubuntu has some documentation to assist?

@mint4all proposes a plausible reason. Perhaps try their suggestion?

Offline

#16 2021-01-17 00:21:17

mint4all
Member
From: out of sight
Registered: 2018-08-21
Posts: 168

Re: Why Does My Xubuntu 20.04 Desktop Keep Freezing?

Mark7 wrote:

I can boot it with a USB.  What should I do after that?

Assuming you are using one of the ubuntu-based live distributions (ie xubuntu, or mint) boot it up to where you have a functioning, live xfce session.

1st, check the health of your disk. Although there's a way to do this from the command line, the simplest way i know of, and use myself, is to: run the "disks" utility via the whisker menu, or "gnome-disks" from a terminal. Once the utility's window opens, look for the menu button (the 4th icon from the top right corner of the title bar). From that menu popup, select (left click) the "SMART Data ...." option, then peruse the drives self-test diagnostics for any alerts (displayed in red), or unusual/high error rates on disk reads, seeks and writes, reallocated sectors , and temparature failures. The diags are labeled "pre-fail", "old-age", or"failure". High error rates, or red flags, indicate imminent drive failure. The built-in Ai-algo rates each diagnosis, if it states "ok" then the drive's partititions can be mounted for integrity checks. High seek- and write-errors are typical for aging laptops, especially if the battery has gone dead before and the disk's write-back cache chip could not flush to disk during shutdown, or AC-power failure.

As a starting point, lets see what you find out. Let's hope your laptop has a healthy disk ...

Cheers, m4a


Linux Mint 18.3, 19.3, 20.0 -- xfce 4.12 & 4.14... Apple IMAC 11,3 -- Dell Precision T1500 Desktops -- Toshiba Satellite, Dell Inspiron & HP Pavilion Laptops -- Family & Community Support re. Linux

Offline

#17 2021-01-17 07:14:13

Mark7
Member
Registered: 2007-10-05
Posts: 119

Re: Why Does My Xubuntu 20.04 Desktop Keep Freezing?

This is probably going to sound thick but... What is Disks?  I couldn't find it anywhere in the menu (even with a search).

I did run the laptop's own integral HDD health check and nothing unusual came up.

Offline

#18 2021-01-17 07:42:08

MrEen
Member
Registered: 2019-04-19
Posts: 294

Re: Why Does My Xubuntu 20.04 Desktop Keep Freezing?

The command name is gnome-disks, which is part of the gnome-disk-utility package on Debian/Ubuntu based distro's.

Looks like it's a default installed package on Ubuntu but not Xubuntu based on my search at DistroWatch.

It'll be in your repositories for installation though.

sudo apt-get install gnome-disk-utility

Then it should be in the Menu under Settings > Disks (at least that's the location on Mint.)

Offline

#19 2021-01-17 16:29:56

Mark7
Member
Registered: 2007-10-05
Posts: 119

Re: Why Does My Xubuntu 20.04 Desktop Keep Freezing?

Does it generate some kind of report I can copy and paste here?

Offline

#20 2021-01-17 17:39:24

MrEen
Member
Registered: 2019-04-19
Posts: 294

Re: Why Does My Xubuntu 20.04 Desktop Keep Freezing?

I believe so. I've seen outputs showing the "pre-fail", "old-age", or "failure" outputs that appear to be pasted from the application. I assume it'll be a separate window showing the output from the test, but could be wrong as I've not used it myself.

Offline

#21 2021-01-18 00:22:12

mint4all
Member
From: out of sight
Registered: 2018-08-21
Posts: 168

Re: Why Does My Xubuntu 20.04 Desktop Keep Freezing?

Mark7 wrote:

Does it generate some kind of report I can copy and paste here?

Did some more sleuthing and can confirm that MrEen is correct. There's a command-line tool "smartmontools" maintained by ubuntu and in its repositories. It can easily be installed via

sudo apt install smartmontools

I did just that, and i am happy with its utility. It is discussed at length @ https://www.techrepublic.com/blog/linux … rd-drives/ with a comment @ https://askubuntu.com/questions/528072/ … f-ubuntu-1 and its man page @ http://manpages.ubuntu.com/manpages/bio … ctl.8.html

Note: the point of this is to determine the physical condition of your disk drive WITHOUT altering its data structures (whether intact or corrupted). Unless mounted read-only, the mere act of mounting its partitions causes integrity checks and/or -repairs, and if booted up into a working system (which you have) starts all sorts of cleanup/housekeeing that can further override otherwise intact data -- i admit i learned this lesson the hard way...

With this command option

sudo smartctl -a /dev/sda

you'll get everything for your 1st disk  (usually the boot disk/drive). Please run the foregoing command in a terminal after booting your live usb system, and installing "smartmontools".

Following that, i suggest your run the following command

inxi -p

to get an idea of your system's partitions/volumes, folllowed by

inxi -m

to look at your laptop's installed memory (assuming that the "inxi" command is installed on your usb system. Please copy the commands' output and paste it into your next reply.

Cheers, m4a


Linux Mint 18.3, 19.3, 20.0 -- xfce 4.12 & 4.14... Apple IMAC 11,3 -- Dell Precision T1500 Desktops -- Toshiba Satellite, Dell Inspiron & HP Pavilion Laptops -- Family & Community Support re. Linux

Offline

#22 2021-01-18 09:26:38

Mark7
Member
Registered: 2007-10-05
Posts: 119

Re: Why Does My Xubuntu 20.04 Desktop Keep Freezing?

Here goes

mark@mark-HP-EliteBook-8460p:~$ sudo smartctl -a /dev/sda
[sudo] password for mark:
smartctl 7.1 2019-12-30 r5022 [x86_64-linux-5.4.0-62-generic] (local build)
Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Western Digital Scorpio Black
Device Model:     WDC WD3200BEKT-60PVMT0
Serial Number:    WD-WXQ1A71R2444
LU WWN Device Id: 5 0014ee 206436849
Firmware Version: 01.01A01
User Capacity:    320,072,933,376 bytes [320 GB]
Sector Size:      512 bytes logical/physical
Rotation Rate:    7200 rpm
Form Factor:      2.5 inches
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ATA8-ACS (minor revision not indicated)
SATA Version is:  SATA 2.6, 3.0 Gb/s
Local Time is:    Mon Jan 18 09:19:41 2021 GMT
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status:  (0x00)    Offline data collection activity
                    was never started.
                    Auto Offline Data Collection: Disabled.
Self-test execution status:      (   0)    The previous self-test routine completed
                    without error or no self-test has ever
                    been run.
Total time to complete Offline
data collection:         ( 5700) seconds.
Offline data collection
capabilities:              (0x51) SMART execute Offline immediate.
                    No Auto Offline data collection support.
                    Suspend Offline collection upon new
                    command.
                    No Offline surface scan supported.
                    Self-test supported.
                    No Conveyance Self-test supported.
                    Selective Self-test supported.
SMART capabilities:            (0x0003)    Saves SMART data before entering
                    power-saving mode.
                    Supports SMART auto save timer.
Error logging capability:        (0x01)    Error logging supported.
                    General Purpose Logging supported.
Short self-test routine
recommended polling time:      (   2) minutes.
Extended self-test routine
recommended polling time:      (  59) minutes.
SCT capabilities:            (0x703d)    SCT Status supported.
                    SCT Error Recovery Control supported.
                    SCT Feature Control supported.
                    SCT Data Table supported.

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x002f   200   200   051    Pre-fail  Always       -       8
  3 Spin_Up_Time            0x0027   160   140   021    Pre-fail  Always       -       966
  4 Start_Stop_Count        0x0032   095   095   000    Old_age   Always       -       5787
  5 Reallocated_Sector_Ct   0x0033   200   200   140    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x002f   100   253   051    Pre-fail  Always       -       0
  9 Power_On_Hours          0x0032   071   071   000    Old_age   Always       -       21326
10 Spin_Retry_Count        0x0033   100   100   051    Pre-fail  Always       -       0
11 Calibration_Retry_Count 0x0032   100   100   000    Old_age   Always       -       0
12 Power_Cycle_Count       0x0032   095   095   000    Old_age   Always       -       5738
183 Runtime_Bad_Block       0x0032   046   046   000    Old_age   Always       -       54
184 End-to-End_Error        0x0033   100   100   097    Pre-fail  Always       -       0
187 Reported_Uncorrect      0x0032   100   099   000    Old_age   Always       -       1
188 Command_Timeout         0x0032   100   084   000    Old_age   Always       -       876186894552
190 Airflow_Temperature_Cel 0x0022   066   050   040    Old_age   Always       -       34 (Min/Max 22/34)
191 G-Sense_Error_Rate      0x0032   001   001   000    Old_age   Always       -       53875
192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age   Always       -       285
193 Load_Cycle_Count        0x0032   193   193   000    Old_age   Always       -       22815
194 Temperature_Celsius     0x0022   109   093   000    Old_age   Always       -       34
196 Reallocated_Event_Count 0x0032   200   200   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0032   200   200   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0030   100   253   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x0032   200   200   000    Old_age   Always       -       0
200 Multi_Zone_Error_Rate   0x0009   200   200   051    Pre-fail  Offline      -       0

SMART Error Log Version: 1
ATA Error Count: 1
    CR = Command Register [HEX]
    FR = Features Register [HEX]
    SC = Sector Count Register [HEX]
    SN = Sector Number Register [HEX]
    CL = Cylinder Low Register [HEX]
    CH = Cylinder High Register [HEX]
    DH = Device/Head Register [HEX]
    DC = Device Command Register [HEX]
    ER = Error register [HEX]
    ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.

Error 1 occurred at disk power-on lifetime: 17086 hours (711 days + 22 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 d8 e0 54 76 ee  Error: UNC 216 sectors at LBA = 0x0e7654e0 = 242636000

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  c8 00 d8 e0 54 76 ee 08      01:44:39.991  READ DMA
  c8 00 00 e0 53 76 ee 08      01:44:39.985  READ DMA
  c8 00 00 e0 52 76 ee 08      01:44:39.976  READ DMA
  c8 00 00 e0 51 76 ee 08      01:44:39.898  READ DMA

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Extended offline    Completed without error       00%     21315         -
# 2  Short offline       Completed without error       00%     21309         -
# 3  Extended offline    Completed without error       00%     21309         -
# 4  Short offline       Completed without error       00%     21308         -
# 5  Short offline       Aborted by host               90%     20451         -
# 6  Short offline       Completed without error       00%     20451         -
# 7  Short offline       Completed without error       00%     20451         -
# 8  Short offline       Completed without error       00%     20451         -
# 9  Short offline       Interrupted (host reset)      10%     20446         -
#10  Extended offline    Aborted by host               80%     17781         -
#11  Short offline       Completed without error       00%     17781         -
#12  Short offline       Completed without error       00%     17781         -
#13  Short offline       Completed without error       00%     17781         -
#14  Short offline       Completed without error       00%     17781         -
#15  Short offline       Aborted by host               90%      9995         -
#16  Short offline       Aborted by host               90%      9995         -
#17  Short offline       Completed without error       00%      9995         -
#18  Short offline       Completed without error       00%      9995         -
#19  Extended offline    Interrupted (host reset)      90%      6535         -
#20  Short offline       Completed without error       00%      6535         -
#21  Short offline       Completed without error       00%         1         -

SMART Selective self-test log data structure revision number 1
SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Not_testing
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Not_testing
Selective self-test flags (0x0):
  After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.

mark@mark-HP-EliteBook-8460p:~$ sudo inxi -p
Partition:
  ID-1: / size: 291.92 GiB used: 21.58 GiB (7.4%) fs: ext4 dev: /dev/sda5
  ID-2: /boot/efi size: 511.0 MiB used: 4 KiB (0.0%) fs: vfat dev: /dev/sda1
  ID-3: /media/mark/Back Up size: 29.09 GiB used: 8.41 GiB (28.9%) fs: vfat
  dev: /dev/sdc1
  ID-4: /snap/camus/45 raw size: 10.6 MiB size: N/A (hidden?)
  used: N/A (hidden?) fs: squashfs dev: /dev/loop2
  ID-5: /snap/caprine/43 raw size: 64.5 MiB size: N/A (hidden?)
  used: N/A (hidden?) fs: squashfs dev: /dev/loop3
  ID-6: /snap/core18/1944 raw size: 55.4 MiB size: N/A (hidden?)
  used: N/A (hidden?) fs: squashfs dev: /dev/loop0
  ID-7: /snap/core20/904 raw size: 61.6 MiB size: N/A (hidden?)
  used: N/A (hidden?) fs: squashfs dev: /dev/loop1
  ID-8: /snap/deja-dup/427 raw size: 106.4 MiB size: N/A (hidden?)
  used: N/A (hidden?) fs: squashfs dev: /dev/loop4
  ID-9: /snap/discord/120 raw size: 59.5 MiB size: N/A (hidden?)
  used: N/A (hidden?) fs: squashfs dev: /dev/loop5
  ID-10: /snap/gnome-3-28-1804/145 raw size: 162.9 MiB size: N/A (hidden?)
  used: N/A (hidden?) fs: squashfs dev: /dev/loop6
  ID-11: /snap/gtk-common-themes/1514 raw size: 64.8 MiB size: N/A (hidden?)
  used: N/A (hidden?) fs: squashfs dev: /dev/loop7
  ID-12: /snap/istekram/12 raw size: 62.3 MiB size: N/A (hidden?)
  used: N/A (hidden?) fs: squashfs dev: /dev/loop14
  ID-13: /snap/istekram/3 raw size: 59.4 MiB size: N/A (hidden?)
  used: N/A (hidden?) fs: squashfs dev: /dev/loop8
  ID-14: /snap/liferea/11 raw size: 103.0 MiB size: N/A (hidden?)
  used: N/A (hidden?) fs: squashfs dev: /dev/loop9
  ID-15: /snap/snapd/10707 raw size: 31.1 MiB size: N/A (hidden?)
  used: N/A (hidden?) fs: squashfs dev: /dev/loop10
  ID-16: /snap/twinux/62 raw size: 51.1 MiB size: N/A (hidden?)
  used: N/A (hidden?) fs: squashfs dev: /dev/loop11
  ID-17: /snap/yakyak/91 raw size: 107.5 MiB size: N/A (hidden?)
  used: N/A (hidden?) fs: squashfs dev: /dev/loop12
  ID-18: /snap/zoom-client/128 raw size: 233.8 MiB size: N/A (hidden?)
  used: N/A (hidden?) fs: squashfs dev: /dev/loop13
mark@mark-HP-EliteBook-8460p:~$ sudo inxi -m
Memory:
  RAM: total: 3.76 GiB used: 2.03 GiB (54.1%)
  Array-1: capacity: 8 GiB slots: 2 EC: None
  Device-1: Bottom-Slot 1(top) size: No Module Installed
  Device-2: Bottom-Slot 2(under) size: 4 GiB speed: 1333 MT/s
mark@mark-HP-EliteBook-8460p:~$

Offline

#23 2021-01-18 17:26:56

mint4all
Member
From: out of sight
Registered: 2018-08-21
Posts: 168

Re: Why Does My Xubuntu 20.04 Desktop Keep Freezing?

Thanks for going to all this trouble, but it was worth it! SMART #188 gives us the tipoff to your problem. According to this page @ https://www.stellarinfo.com/blog/command-timeout-error/  (posted by a reputable cloud-kit servicer) your disk suffers extremely high command timeouts. This can lead to all sorts of collateral problems, and usually (ime) the early warning signs are system freezes, because, sooner or later, your disk does the heavy lifting.

If it were me, i would not attempt anything else other than (a) clone the drive, ie with clonezilla, or (b) backup important data to either cloud or attached media, preferrably both (i usually keep 3 backups 'cause one never knows).

Then, and only then, explore what causes the power issues with your sata drive: cables, connectors, sockets, etc. There could be vibration/shock issues, too. My preference: replace the drive, then restore the clone, or rebuild the system then resstore the data.

In the alternative, after cloning/backup, open the laptop, reseat the drive, then boot into grub's recovery option and perform the file system repair. It could be as simple as the drive rattled loose over time, or a thermal failure on the connectors/sockets that impairs the necessary tight grip.

Good luck, m4a


Linux Mint 18.3, 19.3, 20.0 -- xfce 4.12 & 4.14... Apple IMAC 11,3 -- Dell Precision T1500 Desktops -- Toshiba Satellite, Dell Inspiron & HP Pavilion Laptops -- Family & Community Support re. Linux

Offline

#24 2021-01-18 18:58:33

Mark7
Member
Registered: 2007-10-05
Posts: 119

Re: Why Does My Xubuntu 20.04 Desktop Keep Freezing?

I do tend to knock or pull it off the table it sits on a lot (I'm quite clumsy).

Offline

#25 2021-01-18 22:52:01

Mark7
Member
Registered: 2007-10-05
Posts: 119

Re: Why Does My Xubuntu 20.04 Desktop Keep Freezing?

I don't actually seem to have Grub.  Or it doesn't show up when I turn the laptop on.

Offline

Board footer

Powered by FluxBB