Re: finding package for reportbug
Charles Curley <charlescurley@charlescurley.com> wrote:
> On Wed, 5 Feb 2025 15:46:23 +0100
> Franziska Menti <fmenti@phys.ethz.ch> wrote:
>
> > Hi Charles
[snip]
> What I had in mind here is something like:
>
> dmesg | less -X
>
> then use the search function (the / key) to search for snd_hda_intel
> and (separately) snd_sof_pci_intel_mtl. Check in the neighbor of any
> entries for error messages.
>
> For journalctl, the setup will be a bit more complex. depending on
> what you want.
>
> journalctl -b | less
>
> for everything since the last boot.
>
> journalctl -S YYYY-MM-DD | less
>
> for everything since the given date (e.g. 2012-10-30).
>
> man less and man journalctl are your friends. And your IT person
> should be familiar with these tools.
Indeed so, and in particular the bit in journalctl's man page where it
says "The output is paged through less by default ..." !
Piping journalctl's output through less is pointless, I think.
dmesg -H might also be worth looking at.
Reply to: