Screengrabs do not fit my purpose.

I know about /var/log/apt and history.log and term.log in there but it doesn't get logged in there in Ubuntu MATE 20.04.3. In fact it gets logged nowhere, since UM comes with the handy Log File Viewer, I've been able to verify that,I could copypaste lines as it happens but I then would likely be told that the log is not complete, there's a certain limit to how many lines the screen will show. I need to be able to copy paste lines from an updating process, it's not as simple as "command > result.txt" with sudo apt update then sudo apt upgrade. I'm not really a newbie but I guess I never had to do this, I could always find logs for anything before, but I never needed to get update lines from an update to catch an error I cannot show otherwise (screengrabs are not good enough apparently).

Thank you very much, I hope it is possible at all, this one error I have figured everything about except for one last step to fix, I can't find how or get help to fix it without update logs I can copypaste and put in bbcode tags.

/var/log/dpkg.log perhaps?

Nope, it's on the options right on the left in the Log-File Viewer in MATE. The updates do not get logged at all, we have to get past that. Maybe there is a way to create a log file when one does sudo apt-update && sudo apt-upgrade , some parameters added to it or something maybe?

I have found this as a solution, but someone will have to tell me if it would only work for a single package as in the example I found

tee command does it all apparently, first time I hear of it in 11 years of usage, always learning something new lol

Now, I'm just afraid to proceed without confirmation that it will work for a general update, not just for one package.

To be clear, DPKG will show some installations, but not the error message that is only shown during the install process I experience since a while, that I have a good idea how to get rid of, but I need a copypaste of the install process entirely.

Are you sure that error message is displayed on stdout and not on stderr?

You may have to redirect stderr.

This is good to know. I have been using tee to log the results for apt-get dist-upgrade for a while now and didn't realize that the stderr wasn't getting logged. Luckily I didn't need to but going forward I can ensure all errors are also logged.

1 members found this post helpful.