System freeze-up

[Moltke]

I didn't get any errors in the terminal so I closed it and deleted mozilla.old and started Firefox from the taskbar like usual.  Soon after that it froze.  But... like I said - I am not sure if it is the fault of FF - I am just assuming it might be.  It also might NOT be...?

I see. Sure, it can be a number of things other than FF, but since you mentioned it, it's a good starting point. That's why I suggested you to download it, to try and see whether it is the installed version the culprit. If it's not, then you can start looking somewhere else, and we can help you do that.

[j8a]

Hi [member=9729]lintek[/member] ,
As a regular FF user on LL, I guess you have tried to purge the history on FF and also run Lite Tweaks and remove the FF cache.
I could suggest to give a try in order to see whether it solves your problem.
Regards

[lintek]

Hi [member=9729]lintek[/member] ,
As a regular FF user on LL, I guess you have tried to purge the history on FF and also run Lite Tweaks and remove the FF cache.
I could suggest to give a try in order to see whether it solves your problem.
Regards

Thanks for the advice - I am not really a regular user AND I am a true novice at Linux, even though I've been using it for a while...  ;D

[lintek]

Well... I don't think it is Firefox anymore.

I decided to try using it without using Firefox.  After a couple minutes, it froze up.

Maybe Jerry has an idea?  Maybe it is just a bad install?  I just don't get it...  :012:

[Moltke]

Open the terminal and run this

Code:

sudo journalctl priority err --since "10 min ago"

You can replace "10 min ago" if you want by another time, i.e. "20 min ago", and look for any error messages in the output, you can also copy/paste the output here in your reply. If you get

Code:

-- no entries

try running it without the "--since "10 min ago"". For more info run

Code:

man journalctl

[lintek]

Tried line 1 - got this

"Failed to add match 'priority': Invalid argument"

Also tried upgrading from 5.2 to 5.4

NO LUCK. I am about ready to just reinstall.

[Moltke]

Tried line 1 - got this

"Failed to add match 'priority': Invalid argument"

Also tried upgrading from 5.2 to 5.4

NO LUCK. I am about ready to just reinstall.

Oops! Sorry, my bad! I missed "--" before and  "=" after priority this is the correct command

Code:

sudo journalctl --priority=err --since "10 min ago"

Again, really sorry I didn't realize that earlier when I posted. Try again, it should work this time.

[lintek]

I am about ready to shoot my Linux Lite.

Since I can barely try any of the things you suggest due to freezing up, I decided to drop in a new hard rive and load a fresh copy of 5.4 onto it.

AND IT STILL FROZE UP.  With Firefox on, with firefox off, with chromium on with chromium off, with a different mouse, etc etc.

At this point I cannot imagine what is causing this. 

But this is a dual boot computer and luckily my old copy of Windows 7 works.

[Moltke]

While in the desktop, xfce, press Ctrl + Alt + F1 to jump to a TTY(command line mode) login with your credentials; username and password. Then run the journalctl command, but since you can't copy/paste the output in that mode, you'll have to redirect it to a file, like this

Code:

sudo journalctl --priority=err --since "30 min ago" > journalctl_output

name it whatever else you want to, the file will be saved in your home directory, if by any chance you get no output, or it is too short, like 3 lines short or something like that, you can, 1) increase the time, i.e. "60", 2) run without time which will print the whole thing in which case you'll have to attach the file in your reply since it'll be very long for coping/pasting, once you've done that,  press Ctrl + d to logout from that session, then press Ctrl + Alt + F7 to return to the desktop session, find the file, open it in a text editor and copy/paste the output here, or attach it if it is too long as explained above. The system shouldn't freeze in that mode, and if it does, then the problem might be a graphics related thing, I think. The output of journalctl might give us a hint whether it is or not.

[lintek]

journalctl_output

Code:

-- Logs begin at Sat 2021-05-08 00:08:36 CDT, end at Tue 2021-05-11 23:47:25 CDT. --
May 11 23:42:54 linux-DX4860 systemd[1]: Failed to start Show Plymouth Boot Screen.
May 11 23:42:59 linux-DX4860 ntpd[1214]: error resolving pool 0.ubuntu.pool.ntp.org: Temporary failure in name resolution (-3)
May 11 23:43:00 linux-DX4860 /hpfax[1260]: [1260]: error: Failed to create /var/spool/cups/tmp/.hplip
May 11 23:43:00 linux-DX4860 ntpd[1214]: error resolving pool 1.ubuntu.pool.ntp.org: Temporary failure in name resolution (-3)
May 11 23:43:01 linux-DX4860 ntpd[1214]: error resolving pool 2.ubuntu.pool.ntp.org: Temporary failure in name resolution (-3)
May 11 23:43:01 linux-DX4860 nmbd[1301]: [2021/05/11 23:43:01.784944,  0] ../../lib/util/become_daemon.c:147(daemon_status)
May 11 23:43:01 linux-DX4860 nmbd[1301]:   daemon_status: daemon 'nmbd' : No local IPv4 non-loopback interfaces available, waiting for interface ...
May 11 23:43:01 linux-DX4860 nmbd[1301]: [2021/05/11 23:43:01.785037,  0] ../../source3/nmbd/nmbd_subnetdb.c:253(create_subnets)
May 11 23:43:01 linux-DX4860 nmbd[1301]:   NOTE: NetBIOS name resolution is not supported for Internet Protocol Version 6 (IPv6).
May 11 23:43:02 linux-DX4860 ntpd[1214]: error resolving pool 3.ubuntu.pool.ntp.org: Temporary failure in name resolution (-3)
May 11 23:43:03 linux-DX4860 ntpd[1214]: error resolving pool ntp.ubuntu.com: Temporary failure in name resolution (-3)
May 11 23:43:32 linux-DX4860 pulseaudio[1287]: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: 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.
-- Reboot --
May 11 23:44:22 linux-DX4860 systemd[1]: Failed to start Show Plymouth Boot Screen.
May 11 23:44:26 linux-DX4860 ntpd[1169]: error resolving pool 0.ubuntu.pool.ntp.org: Temporary failure in name resolution (-3)
May 11 23:44:27 linux-DX4860 ntpd[1169]: error resolving pool 1.ubuntu.pool.ntp.org: Temporary failure in name resolution (-3)
May 11 23:44:27 linux-DX4860 /hpfax[1211]: [1211]: error: Failed to create /var/spool/cups/tmp/.hplip
May 11 23:44:28 linux-DX4860 ntpd[1169]: error resolving pool 2.ubuntu.pool.ntp.org: Temporary failure in name resolution (-3)
May 11 23:44:29 linux-DX4860 nmbd[1227]: [2021/05/11 23:44:29.407539,  0] ../../lib/util/become_daemon.c:147(daemon_status)
May 11 23:44:29 linux-DX4860 nmbd[1227]:   daemon_status: daemon 'nmbd' : No local IPv4 non-loopback interfaces available, waiting for interface ...
May 11 23:44:29 linux-DX4860 nmbd[1227]: [2021/05/11 23:44:29.407610,  0] ../../source3/nmbd/nmbd_subnetdb.c:253(create_subnets)
May 11 23:44:29 linux-DX4860 nmbd[1227]:   NOTE: NetBIOS name resolution is not supported for Internet Protocol Version 6 (IPv6).
May 11 23:44:29 linux-DX4860 ntpd[1169]: error resolving pool 3.ubuntu.pool.ntp.org: Temporary failure in name resolution (-3)
May 11 23:44:30 linux-DX4860 ntpd[1169]: error resolving pool ntp.ubuntu.com: Temporary failure in name resolution (-3)
May 11 23:45:00 linux-DX4860 pulseaudio[1245]: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: 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.
-- Reboot --
May 11 23:45:57 linux-DX4860 systemd[1]: Failed to start Show Plymouth Boot Screen.
May 11 23:46:01 linux-DX4860 ntpd[1173]: error resolving pool 0.ubuntu.pool.ntp.org: Temporary failure in name resolution (-3)
May 11 23:46:02 linux-DX4860 ntpd[1173]: error resolving pool 1.ubuntu.pool.ntp.org: Temporary failure in name resolution (-3)
May 11 23:46:02 linux-DX4860 /hpfax[1222]: [1222]: error: Failed to create /var/spool/cups/tmp/.hplip
May 11 23:46:03 linux-DX4860 ntpd[1173]: error resolving pool 2.ubuntu.pool.ntp.org: Temporary failure in name resolution (-3)
May 11 23:46:04 linux-DX4860 nmbd[1231]: [2021/05/11 23:46:04.320142,  0] ../../lib/util/become_daemon.c:147(daemon_status)
May 11 23:46:04 linux-DX4860 nmbd[1231]:   daemon_status: daemon 'nmbd' : No local IPv4 non-loopback interfaces available, waiting for interface ...
May 11 23:46:04 linux-DX4860 nmbd[1231]: [2021/05/11 23:46:04.320892,  0] ../../source3/nmbd/nmbd_subnetdb.c:253(create_subnets)
May 11 23:46:04 linux-DX4860 nmbd[1231]:   NOTE: NetBIOS name resolution is not supported for Internet Protocol Version 6 (IPv6).
May 11 23:46:04 linux-DX4860 ntpd[1173]: error resolving pool 3.ubuntu.pool.ntp.org: Temporary failure in name resolution (-3)
May 11 23:46:05 linux-DX4860 ntpd[1173]: error resolving pool ntp.ubuntu.com: Temporary failure in name resolution (-3)
May 11 23:46:35 linux-DX4860 pulseaudio[1249]: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: 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.
May 11 23:47:05 linux-DX4860 ntpd[1173]: error resolving pool 0.ubuntu.pool.ntp.org: Temporary failure in name resolution (-3)
May 11 23:47:08 linux-DX4860 ntpd[1173]: error resolving pool 3.ubuntu.pool.ntp.org: Temporary failure in name resolution (-3)
May 11 23:47:08 linux-DX4860 ntpd[1173]: error resolving pool 1.ubuntu.pool.ntp.org: Temporary failure in name resolution (-3)
May 11 23:47:10 linux-DX4860 ntpd[1173]: error resolving pool 2.ubuntu.pool.ntp.org: Temporary failure in name resolution (-3)
May 11 23:47:11 linux-DX4860 ntpd[1173]: error resolving pool ntp.ubuntu.com: Temporary failure in name resolution (-3)