Software updater hangs after about 80%

[Richard Kimber]

On Mon, 2 Jul 2018 18:32:04 +0200
Liam Proven <lproven at gmail.com> wrote:

> On Mon, 2 Jul 2018 at 18:27, Richard Kimber
> <richardkimber at politicsresources.net> wrote:
> >
> > It's USB. It has 4 slots, so I suppose that accounts for the sdk.  
> 
> Would only seem to account for h/i/j/k but maybe if some slots do
> different types of media, then they'd take >1 letter up. I don't
> actually have a modern one of these things; the only modern media I
> use are µSD and all my machines have built-in readers for those. As a
> result I am not familiar with their foibles.
> 
> > The
> > reader was plugged in, but no card was plugged into the reader.  
> 
> Yes, you mentioned, and in theory, it should not induce this bug if
> there are no volume(s) mounted.
> 
> > I've
> > taken the reader out now, so I guess I'll kill the update process.
> > Is it both of these?
> >
> > 4762 pts/3    SN+
> > 0:00 /bin/sh /var/lib/dpkg/info/linux-image-4.15.0-24-generic.postinst
> > triggered linux-update-4.15.0-24-generic
> >
> > 25451 ?        SNl
> > 0:08 /usr/bin/python3 /usr/bin/update-manager --no-update
> > --no-focus-on-map  
> 
> Ah, it was happening from the GUI, not the CLI? Hm. I would suggest
> the latter first, then a retry, and if that doesn't work, then the
> former.
> 
> To retry, open a shell  (Ctrl+Alt+T) and type:
> 
> sudo apt full-upgrade -y
> 
> If it complains of errors, try:
> 
> sudo apt install -f

The latter worked ok, but sudo apt full-upgrade -y just gave a help
message listing the commands, and sudo apt install -f complained that
it could not get an exclusive lock.

I tried killing the other process, but it remains in the list.

- Richard
-- 
Richard Kimber