<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix">On 9/5/22 10:32, Fritz Hudnut wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAG62idD4sZuMdgE=qU9=frt=nVhwhD7BCJf7X9hpfFg-BZ-E-w@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div dir="ltr"><br>
</div>
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">(snip)<br>
</blockquote>
<div><br>
</div>
<div>Ralf:</div>
<div><br>
</div>
<div>Alrighty, thanks for the reply . . . the "disappearing
Firefox" thing only was a problem as far as wanting a
browser to search for answers to the problem of apt
"hanging" in the process of updating the system . . . . On
cold boot FF came back.</div>
<div><br>
</div>
<div>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 . . . .</div>
<div><br>
</div>
<div>F <br>
</div>
</div>
</div>
<br>
<fieldset class="moz-mime-attachment-header"></fieldset>
</blockquote>
<p>Hey Fritz,<br>
</p>
<p>You could search for the available kernels to see which ones are
available, and which ones are installed.</p>
<p>You can also look in the /var/log/dpkg.log something like:</p>
<p>grep "upgrade " /var/log/dpkg.log</p>
<p>That might give you a starting point.</p>
<p>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 head/<br>
</p>
<pre class="moz-signature" cols="72">--
😷</pre>
</body>
</html>