<div dir="ltr"><div>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 . . . .</div><div><br></div><div>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.</div><div><br></div><div>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???</div><div><br></div><div>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???</div><div><br></div><div>These are somewhat "moot" . . . in that Lu boots and runs OK . . . but, something "happened" last week . . .????</div><div><br></div><div>F<br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Sep 6, 2022 at 12:51 PM Fritz Hudnut <<a href="mailto:este.el.paz@gmail.com">este.el.paz@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>Nio:</div><div><br></div><div>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 . . . ???</div><div><br></div><div>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.</div><div><br></div><div>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 . . . ???</div><div><br></div><div>Anyway . . . I'll get back to it in a bit and see if grub found the 5.19 kernel option to boot up . . . .<br></div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Sep 6, 2022 at 12:05 PM Nio Wiklund <<a href="mailto:nio.wiklund@gmail.com" target="_blank">nio.wiklund@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Den 2022-09-06 kl. 20:57, skrev Israel Dahl:<br>
> On 9/6/22 09:31, Fritz Hudnut wrote:<br>
>> > . . . . On cold boot FF came back.<br>
>><br>
>> ><br>
>> > But, the question of what happened with apt was the more important<br>
>> > question . . . was it trying to install a too new kernel and then<br>
>> > tried to back out of it? It was an odd episode . . . .<br>
>> ><br>
>> > F<br>
>> ><br>
>> Hey Fritz,<br>
>><br>
>> You could search for the available kernels to see which ones are<br>
>> available, and which ones are installed.<br>
>><br>
>> You can also look in the /var/log/dpkg.log something like:<br>
>><br>
>> grep "upgrade " /var/log/dpkg.log<br>
>><br>
>> That might give you a starting point.<br>
>><br>
>> As for the disappearance of firefox, I think snap/flatpak packages<br>
>> don't<br>
>> always show up after install, there may be a way to force it to<br>
>> update<br>
>> the menus but I don't really like to use either of those unless I<br>
>> *really* have to, so I don't know off the top of my head/<br>
>><br>
>> -- <br>
>> 😷<br>
>><br>
>><br>
>><br>
>> Israel:<br>
>><br>
>> Thanks for the suggestions . . . I'll check into them when I get back <br>
>> to Lu in a few days. One of my problems is that since I'm rotating <br>
>> OSs each day, I don't know where each system is vis the kernel. <br>
>> Possibly kinetic is a "5.13" base system, but I did see "5.15" in the <br>
>> upgrade list. Yesterday I was in Tumbleweed, which is 5.19 . . . and <br>
>> then today I'm in Deb Sid, which I thought would be like 5.20??? but, <br>
>> nope, uname -r shows "5.10" . . . .<br>
>><br>
>> The good news is that whatever blew up in the middle or end of the <br>
>> apt, the kinetic system rebooted into the GUI . . . . It was just a <br>
>> rare instance of a "hang" in the apt dist-upgrade.<br>
>><br>
>> F<br>
>><br>
> It looks like Kinetic has a 5.19 now, so you should try to update again.<br>
> <br>
> You should check to see that everything was unpacked in that last <br>
> upgrade as well. You might need to use dpkg to fix things if not.<br>
> <br>
> -- <br>
> 😷<br>
<br>
Hi Fritz and Israel,<br>
<br>
I can confirm that Kinetic is a 5.19 now. Today I installed Lubuntu via<br>
<br>
kinetic-preinstalled-server-amd64.img.xz<br>
<br>
and lubuntu-desktop, installed into it when running in an external SSD <br>
according to<br>
<br>
"Ubuntu Server amd64 compressed image (when extracted) boots in UEFI and <br>
BIOS mode",<br>
<br>
<a href="https://ubuntuforums.org/showthread.php?t=2474692" rel="noreferrer" target="_blank">https://ubuntuforums.org/showthread.php?t=2474692</a><br>
<br>
Best regards<br>
Nio<br>
<br>
<br>
<br>
</blockquote></div>
</blockquote></div>