Often system and other warning messages can't be caught by highlighting, so as to paste into Thread or for raising bug reports.

Often the warning will contain long undecipherable strings which get lost because of this failing.

Not difficult to sort I would have thought.

Would be very useful in problem tracing.

I'll leave this here for a day or so, then remove it so as not to clutter the place up! :-)

Regards
Chris

Normally you can capture screen messages to a file.

https://www.google.com/search?client...sages+on+linux

Or check various logs for the info.

The SUSE/openSUSE sub-forum is far from clogged. But as fatmac says, there are indeed ways to sift out what you need.

This is a problem on all graphical Linux systems - but much less than you make it sound. In my experience, only rarely is it not possible to copy the text or get at the file where the text originates from.
So to help we would need some concrete examples.
Or is this just some complainy rant?

Not unusually the result of doing a quick poke on the PrintScrn key will save better than a copy and paste. Have you tried?

Thanks all

Various suggestions such as print sreen are not always useful as on occasions i've seen the message go beyond the window it is in, but thank you Mrmazda for the thought.

ondoho, the initial text is both a question and a suggestion for improving linux, you'll need to brush up your idea of what a 'rant' is. In times of stress, minor problems seem far larger than they are.

On the occasions I, a dumb beginner, have struggled with a problem, a message appearing to give guidance to the knowledgable has been lost because I could not capture it.

Had I been able to of course, we would not be having this discussion

Thank you for your input fatmac, I'll explore that when I get back to the machine.

Again folks, let me stress, this is a suggestion for improving linux, not an attack on its integrity.

You people seem to know exactly what I'm talking about. It's there, it could be improved and while it may not have seemed a problem for you, it exists nonetheless.

Ensuring that reports and error messages are presented in a textual and capturable form can only improve the situation for the user imho.

Regards

Chris

P.S. If your problem is when booting dmesg is your friend, run it through less or more.

Thanks fatmac, it is usually when an upgrade has gone seriously wrong. It has happened on more that one occasion but I've made a note of your helpful suggestion on my windoze machine!

Regards
Chris

It's a critique best directed to the respective DE (desktop environment) designers.
But since the absence of meaningful error message is deliberately designed it, I doubt they will change course.

BTW, package managers (that what does the update in the background) also have logs.

Well, without going into all the reasons why here, I need to install WPS-Office.

Yast is doing the job, from the Suse site and I get a message that I cannot 'cursor highlight' and capture.
This is a simple one, but as a matter of interest, would you/should I break and ignore some of it's dependencies?

Attached Thumbnails

 

^ my guess is that neither option will result in a working WPS office.
Is it possible to install versions of libfontconfig side-by-side?

Thanks ondoho, Warning for all. I installed WPS, ran it. Really really didn't like what I was getting.

Simple job, Yast, get rid of this for me please.

Yast proceeds to uninstall all of LibreOffice as well of some of WPS

But the WPS installer is still there and how would I get roid of that because Yast just ignores it!

Try first using yast's repositories management to disable or remove the home repo from which WPS-office comes, which looks to be either fusion809, opensuse_zh or regataos. If that's not enough, then:If you get a dependency failure from rpm, either follow your nose if you can, or paste the output here for examination and recommendation.

Thank you Mr Mazda but I think I'd best chase this in another thread. It's getting messy.

Back to the subject of the this thread, it's just happened again. This time LibreOffice just upped and closed without a bye-your-leave!

A picture of the message which can't be swiped is attached.

Attached Thumbnails

 

There isn't much technical data in that message anyhow.
I was thinking more along the lines of technical error messages, log excerpts that cannopt be (easily) typed out.
This is just a paraphrasing, can't hurt to paraphrase it again (if one doesn't want to post screenshots).
But, as I pointed out earlier, I'm sure there's log files to look at. Global, or LO-specific in this case.