Linux Mint 20.3 Cinnamon keeps crashing

[daimon]

Hey folks, so my machine keeps crashing, and we are talking like every couple of days.. everything is updated on it etc, but it keeps crashing and I've had a look at the logs and found some interesting stuff...
So now I've got to ask for some assistance to work out how to fix it, LOL... cos ya' know, I've forgotten more about *nix systems than I ever thought I knew, haha.

So I've got a bit of the log files that look very interesting, some of it is just repeating over and over, and while I've gone and tried to chase down some of it I've not had any luck.

One of the things that concerns me the most is that almost all of this is happening when I'm not actively using the machine.. so I'm not messing with anything, it just seems to be stuck in some sort of a vicious cycle.

Would love any assistance possible with this.. as I've then got to go and try to do it with the machine that I want to set up as my 'cloud server' as well..

Code: Select all

01:01:01 sendmail-msp: unable to qualify my own domain name (GlobalWalkabout) -- using short name
00:19:14 sendmail: unable to qualify my own domain name (GlobalWalkabout) -- using short name
00:01:02 sendmail-msp: unable to qualify my own domain name (GlobalWalkabout) -- using short name
Jan 16 16:01:14 sendmail: unable to qualify my own domain name (GlobalWalkabout) -- using short name
Jan 16 16:00:14 sendmail: My unqualified host name (GlobalWalkabout) unknown; sleeping for retry
Jan 16 08:01:16 sendmail: unable to qualify my own domain name (GlobalWalkabout) -- using short name
Jan 16 08:00:16 sendmail: My unqualified host name (GlobalWalkabout) unknown; sleeping for retry
Jan 16 07:37:42 sendmail: unable to qualify my own domain name (GlobalWalkabout) -- using short name
Jan 16 07:21:01 sendmail-msp: unable to qualify my own domain name (GlobalWalkabout) -- using short name
Jan 16 06:53:43 cinnamon-screen: pam_ecryptfs: seteuid error
Jan 16 06:41:01 sendmail-msp: unable to qualify my own domain name (GlobalWalkabout) -- using short name
Jan 16 05:21:38 cinnamon-screen: pam_ecryptfs: seteuid error
Jan 16 05:21:01 sendmail-msp: unable to qualify my own domain name (GlobalWalkabout) -- using short name
Jan 16 05:06:58 cinnamon-screen: pam_unix(cinnamon-screensaver:auth): auth could not identify password for [simon]
Jan 16 05:01:02 sendmail: unable to qualify my own domain name (GlobalWalkabout) -- using short name
Jan 16 05:00:12 cinnamon-screen: pam_unix(cinnamon-screensaver:auth): auth could not identify password for [simon]
Jan 16 05:00:02 sendmail: My unqualified host name (GlobalWalkabout) unknown; sleeping for retry
Jan 16 01:19:30 sendmail: unable to qualify my own domain name (GlobalWalkabout) -- using short name
Jan 16 01:01:01 sendmail-msp: unable to qualify my own domain name (GlobalWalkabout) -- using short name
Jan 16 00:18:38 sendmail: unable to qualify my own domain name (GlobalWalkabout) -- using short name
Jan 16 00:00:14 sendmail: My unqualified host name (GlobalWalkabout) unknown; sleeping for retry
Jan 15 17:56:56 cinnamon-screen: pam_unix(cinnamon-screensaver:auth): auth could not identify password for [simon]
Jan 15 17:41:01 sendmail-msp: unable to qualify my own domain name (GlobalWalkabout) -- using short name
Jan 15 16:01:13 sendmail: unable to qualify my own domain name (GlobalWalkabout) -- using short name
Jan 15 16:00:13 sendmail: My unqualified host name (GlobalWalkabout) unknown; sleeping for retry
Jan 15 13:41:16 cinnamon-screen: pam_unix(cinnamon-screensaver:auth): auth could not identify password for [simon]
Jan 15 13:41:01 sendmail-msp: unable to qualify my own domain name (GlobalWalkabout) -- using short name
Jan 15 08:48:43 cinnamon-screen: pam_unix(cinnamon-screensaver:auth): auth could not identify password for [simon]
Jan 15 08:41:01 sendmail-msp: unable to qualify my own domain name (GlobalWalkabout) -- using short name
Jan 15 08:15:36 cinnamon-screen: pam_unix(cinnamon-screensaver:auth): auth could not identify password for [simon]
Jan 15 08:01:16 sendmail: unable to qualify my own domain name (GlobalWalkabout) -- using short name
Jan 15 08:00:16 sendmail: My unqualified host name (GlobalWalkabout) unknown; sleeping for retry
Jan 15 07:54:26 cinnamon-screen: pam_unix(cinnamon-screensaver:auth): auth could not identify password for [simon]
Jan 15 07:41:01 sendmail-msp: unable to qualify my own domain name (GlobalWalkabout) -- using short name
Jan 15 07:36:42 sendmail: unable to qualify my own domain name (GlobalWalkabout) -- using short name
Jan 15 07:21:01 sendmail-msp: unable to qualify my own domain name (GlobalWalkabout) -- using short name
Jan 15 06:01:01 sendmail: unable to qualify my own domain name (GlobalWalkabout) -- using short name
Jan 15 06:00:01 sendmail: My unqualified host name (GlobalWalkabout) unknown; sleeping for retry
Jan 15 05:07:41 cinnamon-screen: pam_ecryptfs: seteuid error
Jan 15 05:01:01 sendmail: unable to qualify my own domain name (GlobalWalkabout) -- using short name
Jan 15 05:00:01 sendmail: My unqualified host name (GlobalWalkabout) unknown; sleeping for retry
Jan 15 01:19:06 sendmail: unable to qualify my own domain name (GlobalWalkabout) -- using short name
Jan 15 01:01:01 sendmail-msp: unable to qualify my own domain name (GlobalWalkabout) -- using short name
Jan 15 00:18:32 sendmail: unable to qualify my own domain name (GlobalWalkabout) -- using short name
Jan 15 00:00:14 sendmail: My unqualified host name (GlobalWalkabout) unknown; sleeping for retry
Jan 14 16:01:17 sendmail: unable to qualify my own domain name (GlobalWalkabout) -- using short name
Jan 14 16:00:17 sendmail: My unqualified host name (GlobalWalkabout) unknown; sleeping for retry
Jan 14 10:01:02 sendmail: unable to qualify my own domain name (GlobalWalkabout) -- using short name
Jan 14 10:00:02 sendmail: My unqualified host name (GlobalWalkabout) unknown; sleeping for retry
Jan 14 08:01:20 sendmail: unable to qualify my own domain name (GlobalWalkabout) -- using short name
Jan 14 08:00:20 sendmail: My unqualified host name (GlobalWalkabout) unknown; sleeping for retry

[daimon]

I might also add to this that these are only the logs listed as 'important' the bit that's below is from the 'ALL' section, there is of course a lot more than this, but hopefully some of this will make sense to someone here who's smarter than me, haha.

Code: Select all

01:08:47 kernel: [UFW BLOCK] IN=wlp1s0 OUT= MAC=10:02:b5:e4:fd:0e:b0:02:47:98:0d:4f:08:00 SRC=192.168.8.104 DST=192.168.8.105 LEN=543 TOS=0x00 PREC=0x00 TTL=64 ID=23612 DF PROTO=UDP SPT=55876 DPT=55867 LEN=523 
01:02:37 systemd: NetworkManager-dispatcher.service: Succeeded.
01:02:27 NetworkManager: <info>  [1642341747.4775] manager: NetworkManager state is now CONNECTED_GLOBAL
01:02:26 systemd: Started Network Manager Script Dispatcher Service.
01:02:26 dbus-daemon: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
01:02:26 systemd: Starting Network Manager Script Dispatcher Service...
01:02:26 dbus-daemon: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.8' (uid=0 pid=747 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined")
01:02:26 NetworkManager: <info>  [1642341746.8401] manager: NetworkManager state is now CONNECTED_SITE
01:01:01 cron: pam_unix(cron:session): session closed for user smmsp
01:01:01 sendmail-msp: unable to qualify my own domain name (GlobalWalkabout) -- using short name
01:00:48 kernel: [UFW BLOCK] IN=wlp1s0 OUT= MAC=10:02:b5:e4:fd:0e:b0:02:47:98:0d:4f:08:00 SRC=192.168.8.104 DST=192.168.8.105 LEN=543 TOS=0x00 PREC=0x00 TTL=64 ID=51134 DF PROTO=UDP SPT=57669 DPT=58763 LEN=523 
01:00:29 clamd: Mon Jan 17 01:00:29 2022 -> SelfCheck: Database status OK.
01:00:01 sendmail-msp: My unqualified host name (GlobalWalkabout) unknown; sleeping for retry
01:00:01 sh: (smmsp) CMD (test -x /etc/init.d/sendmail && test -x /usr/share/sendmail/sendmail && test -x /usr/lib/sm.bin/sendmail && /usr/share/sendmail/sendmail cron-msp)
01:00:01 cron: pam_unix(cron:session): session opened for user smmsp by (uid=0)
00:53:20 systemd: Finished Update Manager weekly autoremove.
00:41:44 packagekitd: daemon quit
00:41:01 cron: pam_unix(cron:session): session closed for user smmsp
00:41:01 sendmail-msp: unable to qualify my own domain name (GlobalWalkabout) -- using short name
00:40:01 sh: (smmsp) CMD (test -x /etc/init.d/sendmail && test -x /usr/share/sendmail/sendmail && test -x /usr/lib/sm.bin/sendmail && /usr/share/sendmail/sendmail cron-msp)
00:40:01 cron: pam_unix(cron:session): session opened for user smmsp by (uid=0)
00:36:52 sudo: pam_unix(sudo:session): session closed for user root
00:36:43 systemd: Finished Update Manager automatic upgrades.

[SMG]

Please give us information about your install by entering this command in a terminal: inxi -Fxxxrz
Click </> from the mini toolbar above the textbox where you type your reply and then place your cursor between the code markers and paste the results of the command between the code markers [code]Results[/code]. This will let us know how Mint sees your hardware.

Please also explain what "crashing" means exactly. People tend to use that term differently and knowing more about exactly what is happening will help others to help you.

[daimon]

Sorry yes, I should've explained 'crashing' more.. it basically becomes completely unresponsive to all attempts to get things back on track and I end up having to use the power button for a restart... I've tried restarting cinnamon and all the other things that I could find to get it to respond, but nothing at all worked.

This is the info from my computer:

Code: Select all

simon@GlobalWalkabout:~$ inxi -Fxxxrz
System:
  Kernel: 5.4.0-94-generic x86_64 bits: 64 compiler: gcc v: 9.3.0 
  Desktop: Cinnamon 5.2.7 wm: muffin 5.2.0 dm: LightDM 1.30.0 
  Distro: Linux Mint 20.3 Una base: Ubuntu 20.04 focal 
Machine:
  Type: Desktop System: HP product: HP EliteDesk 800 G2 DM 35W v: N/A 
  serial: <filter> Chassis: type: 15 serial: <filter> 
  Mobo: HP model: 8055 v: KBC Version 05.22 serial: <filter> UEFI: HP 
  v: N21 Ver. 02.14 date: 04/28/2016 
CPU:
  Topology: Quad Core model: Intel Core i5-6500T bits: 64 type: MCP 
  arch: Skylake-S rev: 3 L2 cache: 6144 KiB 
  flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx 
  bogomips: 19999 
  Speed: 900 MHz min/max: 800/3100 MHz Core speeds (MHz): 1: 900 2: 900 
  3: 900 4: 900 
Graphics:
  Device-1: Intel HD Graphics 530 vendor: Hewlett-Packard driver: i915 
  v: kernel bus ID: 00:02.0 chip ID: 8086:1912 
  Display: x11 server: X.Org 1.20.13 driver: modesetting 
  unloaded: fbdev,vesa resolution: 1920x1080~60Hz 
  OpenGL: renderer: Mesa Intel HD Graphics 530 (SKL GT2) v: 4.6 Mesa 21.0.3 
  direct render: Yes 
Audio:
  Device-1: Intel 100 Series/C230 Series Family HD Audio 
  vendor: Hewlett-Packard driver: snd_hda_intel v: kernel bus ID: 00:1f.3 
  chip ID: 8086:a170 
  Sound Server: ALSA v: k5.4.0-94-generic 
Network:
  Device-1: Intel Ethernet I219-LM vendor: Hewlett-Packard driver: e1000e 
  v: 3.2.6-k port: efa0 bus ID: 00:1f.6 chip ID: 8086:15b7 
  IF: eno1 state: down mac: <filter> 
  Device-2: Intel Wireless 7265 driver: iwlwifi v: kernel port: efa0 
  bus ID: 01:00.0 chip ID: 8086:095a 
  IF: wlp1s0 state: up mac: <filter> 
Drives:
  Local Storage: total: 3.76 TiB used: 186.76 GiB (4.9%) 
  ID-1: /dev/sda type: USB vendor: Seagate model: One Touch w PW 
  size: 3.64 TiB serial: <filter> rev: 1707 scheme: GPT 
  ID-2: /dev/sdb vendor: SanDisk model: SD7TB3Q-128G-1006 size: 119.24 GiB 
  speed: 6.0 Gb/s serial: <filter> rev: 0306 scheme: GPT 
Partition:
  ID-1: / size: 87.00 GiB used: 60.41 GiB (69.4%) fs: ext4 dev: /dev/sdb5 
Sensors:
  System Temperatures: cpu: 39.5 C mobo: N/A 
  Fan Speeds (RPM): N/A 
Repos:
  No active apt repos in: /etc/apt/sources.list 
  Active apt repos in: /etc/apt/sources.list.d/google-earth-pro.list 
  1: deb [arch=amd64] http://dl.google.com/linux/earth/deb/ stable main
  Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list 
  1: deb http://packages.linuxmint.com una main upstream import backport #id:linuxmint_main
  2: deb http://archive.ubuntu.com/ubuntu focal main restricted universe multiverse
  3: deb http://archive.ubuntu.com/ubuntu focal-updates main restricted universe multiverse
  4: deb http://archive.ubuntu.com/ubuntu focal-backports main restricted universe multiverse
  5: deb http://security.ubuntu.com/ubuntu/ focal-security main restricted universe multiverse
  6: deb http://archive.canonical.com/ubuntu/ focal partner
  Active apt repos in: /etc/apt/sources.list.d/skype-stable.list 
  1: deb [arch=amd64] https://repo.skype.com/deb stable main
Info:
  Processes: 270 Uptime: 1h 56m Memory: 7.65 GiB used: 3.91 GiB (51.1%) 
  Init: systemd v: 245 runlevel: 5 Compilers: gcc: 9.3.0 alt: 9 Shell: bash 
  v: 5.0.17 running in: gnome-terminal inxi: 3.0.38 
simon@GlobalWalkabout:~$ 

[SMG]

Sorry yes, I should've explained 'crashing' more.. it basically becomes completely unresponsive to all attempts to get things back on track and I end up having to use the power button for a restart... I've tried restarting cinnamon and all the other things that I could find to get it to respond, but nothing at all worked.

I would consider that more of a freeze issue than a crash.

I notice you are running LM20.3. Did you have this problem with LM20.2 or did it start after upgrading?

If you are using the power button to restart the computer, you can run the following to see what the last messages were. That might give an indication of what is happening.

Code: Select all

journalctl -rb -1 | nc termbin.com 9999

It will return with a url address that you should post in your next reply.

That command prints the journal log information of the prior boot cycle (the one which you stopped with the power button) in reverse order (so the reason for the freeze should be near the top) and sends it to termbin.

[daimon]

Sorry for the late reply, I had to sleep as I'd been working all night, I only planned on a few hours which basically became all day :'(

Code: Select all

https://termbin.com/85jm

That's the output..

I had the problem occasionally before the update, but more prevalent now, also Cinnamon keeps doing weird things and I have to keep doing an Alt+F2 / R on it, simple things like clicking a button on a browser or stuff like that won't give me any ability to click, and I restart Cinnamon and it all works properly again, in fact that restart of Cinnamon is really quite handy.

[SMG]

That's the output..

I checked through it and I do not see any issues. Most of what was listed were network, domain name, or antivirus related messages.

I checked Software and drivers for HP EliteDesk 800 35W G2 Desktop Mini PC and if I have the correct page (I set the OS to Windows 10), it appears your system is missing a lot of BIOS/UEFI updates. I went through some of them and I see 00.02.22 Rev.A mentions several updates related to Linux. I did not go through all of them, so there might be others with changes related to Linux as well.

Cinnamon keeps doing weird things and I have to keep doing an Alt+F2 / R on it, simple things like clicking a button on a browser or stuff like that won't give me any ability to click, and I restart Cinnamon and it all works properly again, in fact that restart of Cinnamon is really quite handy.

I wonder if those sporadic times are when ClamAV is running?

If you want, you can see if a newer kernel might stop the freeze issues. The 5.11 and 5.13 kernels are available in Update Manager. Let us know if you want to try either of them and would like installation directions.

[daimon]

Oh dear, sounds like I'll have to work out how to update the bios hahah.

Do you think it's worthwhile running clamAV? I wasn't really sure if I should bother or not, but as I'm playing with the system and it's always online etc I figured it wouldn't hurt to have something running in the background.. but if it's liable to cause problems I might be better removing it?

I'd certainly consider updating the kernel if that's going to help fix some of the issues... as well as updating the bios (though I can't remember ever doing that before so I'm not sure how to update the bios first) LOL..

[SMG]

Do you think it's worthwhile running clamAV? I wasn't really sure if I should bother or not, but as I'm playing with the system and it's always online etc I figured it wouldn't hurt to have something running in the background.. but if it's liable to cause problems I might be better removing it?

I think using an antivirus is a personal decision based on one's needs and browsing habits.

I do not know if ClamAV is any performance issue on your machine. You could watch system monitor to see if you notice periodic changes because of it.

Now that I think about it, I recall someone running into periodic freeze issues that correlated to Timeshift running in the background. When the person switched to only running manual snapshots periodically, their freeze issues cleared. I think that computer was a bit older than yours, but I do not recall for sure.

I'd certainly consider updating the kernel if that's going to help fix some of the issues... as well as updating the bios (though I can't remember ever doing that before so I'm not sure how to update the bios first) LOL..

Instructions for upgrading to the 5.13 kernel:

• Open Update Manager.
• Select View > Linux Kernels and click Continue.
• Make sure 5.13 is selected on the left panel and then click the top-most option on the right panel. An "Install" button will appear.
• Install the kernel and then reboot for it to become active.

If, for some reason, you do not like the performance of that kernel, you boot into an older kernel and then remove the 5.13.

To boot into an older kernel, bring up the grub menu, select the Advanced Options, and then select the desired kernel. If you do not normally see grub menu,
repeatedly tap the escape key during boot to enter grub for an UEFI boot computer (which is what your computer has). See this post for how to edit grub to get the menu to show if you are having problems getting that to work.

Once you boot with the older kernel, you will want to remove the newer one because Mint automatically boots into the highest number kernel. You can remove the newer kernel in a manner similar to the way you installed it in Update Manager. Only this time, you will get a "Remove" button option when you click on the kernel.

[daimon]

Ok, so I followed all of that precisely, and rebooted and now magically when I started everything up again I've got an update notice on the kernel in the update manager, I'm guessing that's the previous kernel? (I didn't take too much notice of the numbers of the previous one, but the one in the update manager is 5.13.0.27.29-20.04.13)

Oh, also for info, I don't have Timewarp running automagically as it takes up soooo much hard drive space that it's not funny, and it won't put it's stuff on to an external hdd I've got running as it's NTFS or FAT or something, as I use it on windows as well...

[SMG]

Ok, so I followed all of that precisely, and rebooted and now magically when I started everything up again I've got an update notice on the kernel in the update manager, I'm guessing that's the previous kernel? (I didn't take too much notice of the numbers of the previous one, but the one in the update manager is 5.13.0.27.29-20.04.13)

Kernel updates did just come through the last day or so, so that is probably what this is.

Oh, also for info, I don't have Timewarp running automagically as it takes up soooo much hard drive space that it's not funny, and it won't put it's stuff on to an external hdd I've got running as it's NTFS or FAT or something, as I use it on windows as well...

Yes, Timeshift does require the snapshot to be on file space with the same format as the install. Most people install using EXT4 format which means you can not put snapshots on a Windows partition.

Timeshift can be run manually and saved to an external drive or a usb. Here is the method I use How to Use Timeshift to Backup and Restore Linux Mint 19 Systems from USB Drive.

[daimon]

Fantastic, thank you, I'll give that a try for backup's. (timeshift, lol NOT timewarp, haha)

Do you think it's worthwhile doing the kernel update then? (I've just noticed it's not showing there today)

[SMG]

(timeshift, lol NOT timewarp, haha)

I did get a chuckle from timewarp.

Do you think it's worthwhile doing the kernel update then? (I've just noticed it's not showing there today)

If it is not showing today, then it is likely you installed it. That is the only reason of which I can think where it would be there one day and not the next.

You can check in Update Manager to see which kernels are installed and which one is active. Select View > Linux Kernels and click Continue. Then check the right pane for each of the kernel series (selected in the left pane) to see which kernels are listed as "Installed" in the middle column. Only one kernel will be "Active" because you can only use one at a time. Only the ones listed as "Installed" or "Active" are actually on your computer. All the rest are just ones which are available to install.

[happnatious1]

I updated my bios recently (which defaulted all the bios settings) and started having a hard freeze problem, then I remembered when I first installed Linux Mint years ago I had the same issue until I went in and disabled C6 power states in the bios.

[daimon]

(timeshift, lol NOT timewarp, haha)

I did get a chuckle from timewarp.

Do you think it's worthwhile doing the kernel update then? (I've just noticed it's not showing there today)

If it is not showing today, then it is likely you installed it. That is the only reason of which I can think where it would be there one day and not the next.

You can check in Update Manager to see which kernels are installed and which one is active. Select View > Linux Kernels and click Continue. Then check the right pane for each of the kernel series (selected in the left pane) to see which kernels are listed as "Installed" in the middle column. Only one kernel will be "Active" because you can only use one at a time. Only the ones listed as "Installed" or "Active" are actually on your computer. All the rest are just ones which are available to install.

Actually yeah, I went and checked the number that I had in the previous post and it was the same kernel, and it's gone from the list so it's all good as it's showing as the currently active kernel.

I'm glad you got a chuckle from it, I must say I did a bit when I realised what I'd written, haha.. too late to go change it at that point

[daimon]

SMG, thank you so much for your assistance so far, it's been invaluable!!

So the other issue that keeps rearing it's ugly head is that Cinnamon itself seems to keep going in to the same thing every day.. it's now allowing me to click things like the + or the - [] x on Chromium, it does sometimes spread to other programs which are running as well, but as the most common thing running is either xchat or chromium I notice it more on chromium.

The only way I've been able to fix it is Alt+F2 / r

Have you seen/heard of something similar to this before?

I updated my bios recently (which defaulted all the bios settings) and started having a hard freeze problem, then I remembered when I first installed Linux Mint years ago I had the same issue until I went in and disabled C6 power states in the bios.

I'll have to check my bios to see if it has anything like that in there, but from memory it doesn't.. but I can't be a hundred percent on that, so next time I'm rebooting for some reason I'll have a look-see.. cheers for the heads up.

[SMG]

Cinnamon itself seems to keep going in to the same thing every day.. it's now allowing me to click things like the + or the - [] x on Chromium, it does sometimes spread to other programs which are running as well, but as the most common thing running is either xchat or chromium I notice it more on chromium.

That sounds like your CPU might be busy?

I do not use Chromium, so I am not all that familiar with the settings which can be tweaked to give it better performance.

The only way I've been able to fix it is Alt+F2 / r

I'm sorry, but I do not understand what this is? (It look like a math equation to me. )

[daimon]

The only way I've been able to fix it is Alt+F2 / r

I'm sorry, but I do not understand what this is? (It look like a math equation to me. )

That restarts Cinnamon

[SMG]

The only way I've been able to fix it is Alt+F2 / r

I'm sorry, but I do not understand what this is? (It look like a math equation to me. )

That restarts Cinnamon

I'm familiar with Ctl-Alt-Escape to restart Cinnamon.

I did find someone else mention that Alf-F2 and then typing r will restart Cinnamon. I'm not familiar with the shorthand you used to know that is what you were probably describing.

[daimon]

ahhh, and now I learn a new way to do it..

It seems almost every time I log back in to my machine I have to do it because chromium has done that weird thing again