[lubuntu-users] What happened?? apt freezes during dist-upgrade in kinetic??
nio.wiklund at gmail.com
Sat Sep 10 18:55:26 UTC 2022
This is what I think:
If the active grub is controlled by some other distro in a dual-boot or
of Lubuntu will not upgrade which kernel it points to. You should boot
into the system that controls the active grub and run
or some corresponding command. Chances are that it will make Lubuntu
boot into the 5.19 kernel.
Den 2022-09-10 kl. 20:27, skrev Fritz Hudnut:
> So, following up on my investigations . . . synaptic "kernels" does show
> "5.19" as "installed" . . . but uname -r still shows that 5.13 is being
> I installed "mainline" some time back, but forgot how to use it . . .
> until I found the github page tabbed in FF. I ran a couple commands and
> it shows: [CODE] $ mainline --list-installed
> mainline 1.0.16
> Distribution: Ubuntu Kinetic Kudu (development branch)
> Architecture: amd64
> Running kernel: 5.13.0-16-generic
> Found installed: 5.19.0-15.15
> Found installed: 188.8.131.52.15
> Found installed: 5.13.0-16.16
> I forget how to get it to switch the kernel . . . 5.19 is "installed"
> but grub is still selecting 5.13 . . . do I run "mainline
> --install-latest" to "reinstall" . . . or is this a grub error of some
> I went into grub's "advanced options" and it's only showing three
> options for 5.13 . . . I selected recovery and ran fsck which did
> nothing, and then dpkg . . . which also found nothing . . . . In the
> sense that the system is not finding anything "broken" . . . but it
> isn't sliding up to select 5.19 options . . . .
> On Sat, Sep 10, 2022 at 8:35 AM Fritz Hudnut <este.el.paz at gmail.com
> <mailto:este.el.paz at gmail.com>> wrote:
> I jumped the queue and booted Lu this morning . . . it was still
> showing 5.13 as the kernel . . . ran a 93 package upgrade . . . no
> mention of a kernel in the list . . . went through w/o error . . . .
> Booted over into master grub control system . . . updated the grub
> bootloader . . . then back into Lu . . . ran another apt . . .
> couple packages to upgrade . . . nothing on the kernel.
> Uname -r still showing "5.13.0-16" . . . ???? I guess the question
> is, if Sid is running 5.10 why would kinetic be running 5.19???
> And, then, other interesting question, why did apt show something
> like 5.15 the last time I was in Lu . . . but then "hang" and lose
> track of it???
> These are somewhat "moot" . . . in that Lu boots and runs OK . . .
> but, something "happened" last week . . .????
> On Tue, Sep 6, 2022 at 12:51 PM Fritz Hudnut <este.el.paz at gmail.com
> <mailto:este.el.paz at gmail.com>> wrote:
> I guess there was a post on the list that I didn't get, as I'm
> on digest . . . . But, thanks guys for checking on the "5.19" .
> . . I'm doing "weekly" apt update/upgrade and pretty sure I saw
> it was attempting to install 5.15??? (something less than 5.19)
> and then now seems to have selected 5.13 . . . ???
> I ran the master grub bootloader this morning, which should
> select the newest kernel in Lu . . . next time I boot into it .
> . . . And I did run "apt -f install" and that brought back
> "nothing to do" . . . it didn't show anything "broken" and so forth.
> I will also check synaptic to see if it shows anything broken .
> . . sometimes it can actually "fix broken" and sometimes it
> "blinks its eyes" and nothing happens . . . . I was looking
> through my cheat sheet notes for how to fix problems, but I
> didn't see anything on "dpkg" and/or how to use it to find and
> fix any issues . . . ???
> Anyway . . . I'll get back to it in a bit and see if grub found
> the 5.19 kernel option to boot up . . . .
> On Tue, Sep 6, 2022 at 12:05 PM Nio Wiklund
> <nio.wiklund at gmail.com <mailto:nio.wiklund at gmail.com>> wrote:
> Den 2022-09-06 kl. 20:57, skrev Israel Dahl:
> > On 9/6/22 09:31, Fritz Hudnut wrote:
> >> > . . . . On cold boot FF came back.
> >> >
> >> > But, the question of what happened with apt was
> the more important
> >> > question . . . was it trying to install a too new
> kernel and then
> >> > tried to back out of it? It was an odd episode .
> . . .
> >> >
> >> > F
> >> >
> >> Hey Fritz,
> >> You could search for the available kernels to see
> which ones are
> >> available, and which ones are installed.
> >> You can also look in the /var/log/dpkg.log something
> >> grep "upgrade " /var/log/dpkg.log
> >> That might give you a starting point.
> >> As for the disappearance of firefox, I think
> snap/flatpak packages
> >> don't
> >> always show up after install, there may be a way to
> force it to
> >> update
> >> the menus but I don't really like to use either of
> those unless I
> >> *really* have to, so I don't know off the top of my
> >> --
> >> 😷
> >> Israel:
> >> Thanks for the suggestions . . . I'll check into them
> when I get back
> >> to Lu in a few days. One of my problems is that since
> I'm rotating
> >> OSs each day, I don't know where each system is vis the
> >> Possibly kinetic is a "5.13" base system, but I did see
> "5.15" in the
> >> upgrade list. Yesterday I was in Tumbleweed, which is
> 5.19 . . . and
> >> then today I'm in Deb Sid, which I thought would be like
> 5.20??? but,
> >> nope, uname -r shows "5.10" . . . .
> >> The good news is that whatever blew up in the middle or
> end of the
> >> apt, the kinetic system rebooted into the GUI . . . .
> It was just a
> >> rare instance of a "hang" in the apt dist-upgrade.
> >> F
> > It looks like Kinetic has a 5.19 now, so you should try
> to update again.
> > You should check to see that everything was unpacked in
> that last
> > upgrade as well. You might need to use dpkg to fix
> things if not.
> > --
> > 😷
> Hi Fritz and Israel,
> I can confirm that Kinetic is a 5.19 now. Today I installed
> Lubuntu via
> and lubuntu-desktop, installed into it when running in an
> external SSD
> according to
> "Ubuntu Server amd64 compressed image (when extracted) boots
> in UEFI and
> BIOS mode",
> Best regards
More information about the Lubuntu-users