Error message cannot copy error message

try to discuss content of error message with help desk person. But as usual error message cannot be copied. This is so wrong and absurd. Do something on that problem…

Hello @jpbn
I don’t understand what you’re referring to. Could you provide some more information?

1 Like

Thank you for your kind question.
I would like An easy way to respond to error messages. Just click on the message and copy the content of it. In Fedora31 error messages are very hard to screenshot because they disappear when doing so. And a picture of the content of the error message is now what i want.
I would like to copy the vcontent of an error message. I want to edit the content to erase all private facts from it (server IP, names, email, … ) before sending the content to a forum. or report a bug with the content of the error message.
Regards Jaap

  What about a Gnome Logs app?

Have you considered using your phone to take a picture of the message? Or, if all else fails, you can always use a pen and some paper to write it down.

1 Like

Thanks, Did try that, but it only keeps logs for the current day. as far as I know.

Thanks, I do try to solve computer problems with heut not easy because the message disappears suddenly. Lots of ways to do the trick. But just copy edit and paste is not yet invented for error messages. I think that is a mistake in software production.

But are you talking about logs you can view with journalctl?
If yes you can navigate through them, and there are various options. Have a look to this document: https://docs.fedoraproject.org/en-US/quick-docs/viewing-logs/

2 Likes

Alciregi, Thank you, and all other humans.
I can use journalctl.
Point is: somebody long time ago did invent error messages, BUT did not make them archived in a file. And did not make them very good copy-able. I would like to stress sombody smarter than me in writing the right solution into software.
Thanks again. Jaap

Well, if your intent is to suggest things to developers, I don’t think that this forum is the right place. Btw, as far as I can understand, the goal of journalctl was to get rid of log files and however, what you can do with a file, you can do with journalct command as well.

BTW, most commands, journalctl included, can have their output sent to a file for perusal and later use by using the redirect symbol.
ie: command > filename
then you can do whatever you need with the file.

Just my $0.02 worth.

Thanks for your 2 cents.
Let me explain. When an error message jumps up most people will do a search with the text of that message. And they are right because that is the quick way to find a solution. Maybe they should not do but they do. But even in journalctl the literary text of the error message is mostly not to be found.
It could be so easy,just copy the error message where it is.
Searching journalctl for a text is so 20th century. Ans by the way some other OS’s do have copiable error messages.
Thanks

Then use Gnome Logs. You can search, copy and paste anything you want, going back days or even weeks…

Another trick, if you simply want to forward the error message to your IT, make a screenshot with the Printkey and send it by email.

It would actually be helpful to understand in what program the error message appears. Is it in the terminal? Then mark the text and hot CTRL + Shift + C (not just CTRL + C as you know if from GUI programs).

Florian, thanks for your answer.
Screenshot from 2020-04-13 08-28-53
This error message is about an existing bug. reported. But in gnome logs I cannot find this error message.

Second: when an error message appears first thing is a search for a solution. and I cannot do a search with a screenshot. Then I need text.
Most users do not even think of posting a bug, they do want to find a solution.
Thanks

2 Likes