[SOLVED] After Cinnamon lock-up can’t access one particular program

paxolin · 05-17-2018, 01:27 AM

Quote:

Originally Posted by hydrurga

Don't worry about the en_GB.utf8 warnings - I get those as well and I'm in the UK.

However, you do have more kernels than you need (I usually only keep three of those at at time, the active one and two previous ones).

Please open the Update Manager, choose View->Linux kernels, and tell me which kernel is marked as "Active".

The one marked Active is 4.4.0-124 It says I have ten installed altogether - see attached.

hydrurga · 05-17-2018, 01:39 AM

Good. If you scroll down, you should see that you have a total of 12 installed (see the list in your previous post).

For all the kernels apart from the active one and the two beneath it (4.4.0-124, 122 and 121), click on the kernel and select "remove" (you will need to enter your password for each one).

At the moment, there is no facility in Mint for telling the system how many kernels you want it to hang on to, so deletion of old kernels has to be done manually like this.

hydrurga · 05-17-2018, 02:49 AM

I'm away for a few hours. Once you've sorted out the kernels, you need to work through the upgrade from 18.2 to 18.3 (https://blog.linuxmint.com/?p=3462) - you can ignore the spices, as we discussed earlier.

paxolin · 05-17-2018, 05:45 AM

I deleted the kernels as you said.
How did you know I missed two that were right at the bottom of the list? I had wrongly assumed they would all be listed together.

Did the upgrade.
All seemed to be fine until right at the end when I was told there had been an error. Another window offered details and when clicked it took me to terminal. I've listed the errors terminal showed right at the end.

Code:

Warning: No support for locale: en_GB.utf8
Errors were encountered while processing:
 mintinstall
 mint-meta-core
 mint-meta-cinnamon
E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install.  Trying to recover:
Setting up mintinstall (7.8.9) ...
Setting up mint-meta-core (2017.09.19) ...
Setting up mint-meta-cinnamon (2017.09.19) ...

See all the images as well. I restarted as told, and included a shot of System Info.
There is an Update notice about a kernel. I haven't done anything about it yet.

hydrurga · 05-17-2018, 06:19 AM

Thanks, I knew about the number of kernels because they were listed in post #44.

Ok, it didn't go entirely smoothly but may nevertheless be fine.

Let's check the current situation with an:

Code:

apt update

apt list --upgradable

We'll leave the kernel update for the moment.

paxolin · 05-17-2018, 06:26 AM

Quote:

Originally Posted by hydrurga

Thanks, I knew about the number of kernels because they were listed in post #44.

Ok, it didn't go entirely smoothly but may nevertheless be fine.

Let's check the current situation with an:

Code:

apt update

apt list --upgradable

We'll leave the kernel update for the moment.

The result of the above only threw up that same "Warning: No support for locale: en_GB.utf8" again, nothing else.

hydrurga · 05-17-2018, 06:48 AM

Quote:

Originally Posted by paxolin

The result of the above only threw up that same "Warning: No support for locale: en_GB.utf8" again, nothing else.

Ok, I wouldn't have expected to see that warning there (which of the two commands produced it?).

Just to check that the packages which threw errors are up-to-date, can you please paste the output from:

Code:

apt policy mintinstall mint-meta-cinnamon mint-meta-core

Thanks.

paxolin · 05-17-2018, 06:58 AM

Quote:

Originally Posted by hydrurga

Ok, I wouldn't have expected to see that warning there (which of the two commands produced it?).

Just to check that the packages which threw errors are up-to-date, can you please paste the output from:

Code:

apt policy mintinstall mint-meta-cinnamon mint-meta-core

Thanks.

Err, I think it was the second command.

Code:

 ~ $ apt policy mintinstall mint-meta-cinnamon mint-meta-core
mintinstall:
  Installed: 7.8.9
  Candidate: 7.8.9
  Version table:
 *** 7.8.9 500
        500 http://packages.linuxmint.com sylvia/main amd64 Packages
        500 http://packages.linuxmint.com sylvia/main i386 Packages
        100 /var/lib/dpkg/status
mint-meta-cinnamon:
  Installed: 2017.09.19
  Candidate: 2017.09.19
  Version table:
 *** 2017.09.19 500
        500 http://packages.linuxmint.com sylvia/main amd64 Packages
        500 http://packages.linuxmint.com sylvia/main i386 Packages
        100 /var/lib/dpkg/status
mint-meta-core:
  Installed: 2017.09.19
  Candidate: 2017.09.19
  Version table:
 *** 2017.09.19 500
        500 http://packages.linuxmint.com sylvia/main amd64 Packages
        500 http://packages.linuxmint.com sylvia/main i386 Packages
        100 /var/lib/dpkg/status

hydrurga · 05-17-2018, 07:07 AM

Ok, that's great.

Let's get that new kernel installed.

In the Update Manager: View->Linux kernels. Then click on the latest kernel in the 4.13.x range (so that we're ahead of the game regarding Meltdown and Spectre) and select "Install". If all goes well, reboot.

paxolin · 05-17-2018, 07:43 AM

Quote:

Originally Posted by hydrurga

Ok, that's great.

Let's get that new kernel installed.

In the Update Manager: View->Linux kernels. Then click on the latest kernel in the 4.13.x range (so that we're ahead of the game regarding Meltdown and Spectre) and select "Install". If all goes well, reboot.

Installed 4.13.0-41 and having rebooted, this is confirmed in System Info.

hydrurga · 05-17-2018, 07:50 AM

Good stuff.

If you are so inclined, and I would advise that you be so, you could create another system image of your Linux partition in its current state. This means that if anything goes awry in the future, you can roll back to now, Mint 18.3, rather than have to roll back all the way to 18.2 and upgrade again.

Just for info, Mint 19 will be available next month, most probably, and you will be able to upgrade from 18.3 to 19 as you did from 18.2 to 18.3 (remember to make a system image before carrying out the upgrade).

Anyway, let's go right back to the reason for this thread. Is Simple Scan working again or is there still an issue with it?

paxolin · 05-17-2018, 08:02 AM

Quote:

Originally Posted by hydrurga

Good stuff.

If you are so inclined, and I would advise that you be so, you could create another system image of your Linux partition in its current state. This means that if anything goes awry in the future, you can roll back to now, Mint 18.3, rather than have to roll back all the way to 18.2 and upgrade again.

Just for info, Mint 19 will be available next month, most probably, and you will be able to upgrade from 18.3 to 19 as you did from 18.2 to 18.3 (remember to make a system image before carrying out the upgrade).

Anyway, let's go right back to the reason for this thread. Is Simple Scan working again or is there still an issue with it?

Crikey, you're on the ball! I've been so involved in this upgrade, that wasn't even on my mind!
No it's not working.
Quick recap: After Mint locked up one of many times, restarted and Simple scan wouldn't run. Another member suggested I un-install and re-install.
Did that, noting that Simple Scan was originally listed in Synaptic Package Manager as Unbuntu, after re-install it was listed as 32.20.0-0linuxmint1, but still wouldn't run. In terminal, typing simple-scan produces: Segmentation fault

hydrurga · 05-17-2018, 08:12 AM

Quote:

Originally Posted by paxolin

Crikey, you're on the ball! I've been so involved in this upgrade, that wasn't even on my mind!
No it's not working.
Quick recap: After Mint locked up one of many times, restarted and Simple scan wouldn't run. Another member suggested I un-install and re-install.
Did that, noting that Simple Scan was originally listed in Synaptic Package Manager as Unbuntu, after re-install it was listed as 32.20.0-0linuxmint1, but still wouldn't run. In terminal, typing simple-scan produces: Segmentation fault

Darn, I wish I hadn't remembered.

Try the following:

Code:

rm -r ~/.cache/simple-scan/autosaves/

rm ~/.cache/simple-scan/state

Then try simple-scan again.

paxolin · 05-17-2018, 08:22 AM

Quote:

Originally Posted by hydrurga

Darn, I wish I hadn't remembered.

Try the following:

Code:

rm -r ~/.cache/simple-scan/autosaves/

rm ~/.cache/simple-scan/state

Then try simple-scan again.

Hell.....! It works! Thanks so much. What in layman's terms is a segmentation fault, and how did you get rid of it?

hydrurga · 05-17-2018, 08:30 AM

Quote:

Originally Posted by paxolin

Hell.....! It works! Thanks so much. What in layman's terms is a segmentation fault, and how did you get rid of it?

Yay!

A segmentation fault is where a process tries to access memory that doesn't belong to it (or so it says on a web page I found).

I just used my Google-fu, searching for "simple-scan" segmentation fault, which returned the following page:

https://askubuntu.com/questions/5164...un-in-terminal

and suggested you try the top answer. We all stand on the shoulders of giants.

I suppose I could have just done that right at the start, but then we would have missed out on all the fun of providing you with an up-to-date version of Mint with some servicing thrown in, and showing you how to make system images.

Thanks for bearing with me!