Cinnamon 17 Crashes help needed

fenwron · 06-18-2019, 05:06 PM

My desktop Linux Mint 17 Cinnamon crashes with each reboot and offers no solution or cause. Can anyone with a similar problem help? Running on a HP 7 with Intel i5 processor.

greencedar · 06-18-2019, 05:16 PM

More information on the status of the OS at the time of failure is needed.

Between the time after it reboots and crashes can you first go to the terminal and copy and paste the following information from the terminal?

Code:

Code:

~$journatlctl

snowday · 06-18-2019, 06:09 PM

Welcome to the forums!

The first thing that occurs to me is that Linux Mint 17 is "end of life" and completely unsupported since May 2019. If your system is crashing because of a bug, this bug will never be fixed (because there are no more updates)!

https://news.softpedia.com/news/linu...9-525900.shtml

Have you tried Linux Mint 18 or the current Linux Mint 19?

fenwron · 06-18-2019, 08:20 PM

snowpine Thanks for the info I am intending to install 19.1 Tesa but want to stabilize my current system first. The problem with the crashes began with the catastrophic simultaneous failures of my power supply and UPS (an older Ferrups 700. Now, as soon as the login is complete I am notified of the crash. I am able to get a terminal to follow greencedar's suggestion but all I get is a command not found.

fenwron · 06-18-2019, 08:55 PM

snowpine Thanks for the info I am intending to install 19.1 Tesa but want to stabilize my current system first. The problem with the crashes began with the catastrophic simultaneous failures of my power supply and UPS (an older Ferrups 700. Now, as soon as the login is complete I am notified of the crash. I am able to get a terminal to follow greencedar's suggestion but all I get is a command not found.

greencedar · 06-18-2019, 09:54 PM

Please enter the following code in the terminal and let us see the results: even though it says "Command nor found." or come other phrase.

Code:

Code:

~$ gnome-system-log &

If you are uncertain how to post the code onto this thread, the instructions to do so are at the bottom of my thread. Follow the link and follow the instructions. If you are uncertain how to follow the instructions please let us know.

Also, snowpine was correct. We may not be able to find the cause of the problem if it is a bug due to the end of life for Linux 17 series.

fenwron · 06-20-2019, 09:38 AM

Greencedar; I did as you suggested but still only get a command not recognized. On the other hand I have a new computer coming and I will do a fresh install of 19.1. Thank you for your efforts.