On 2023-03-12 04:47, J Leslie Turriff wrote:
On 2023-03-11 04:33:51 Carlos E. R. wrote:
These:
<1.4> 2023-03-09T21:45:20.910119+01:00 Telcontar krusader 17147 - - QCoreApplication::applicationDirPath: Please instantiate the QApplication object first <1.4> 2023-03-09T21:45:21.655721+01:00 Telcontar krusader 17147 - - 21:45:21.655-warning default unknown@0 # QWidget::insertAction: Attempt to insert null action <1.4> 2023-03-09T21:45:21.657776+01:00 Telcontar krusader 17147 - - 21:45:21.657-warning default unknown@0 # QWidget::insertAction: Attempt to insert null action <1.4> 2023-03-09T21:45:21.666504+01:00 Telcontar krusader 17147 - - 21:45:21.666-warning kf.i18n unknown@0 # Trying to convert empty KLocalizedString to QString. <1.4> 2023-03-09T21:53:41.223609+01:00 Telcontar tracker-extract 17950 - - Locale 'LANG' is not set, defaulting to C locale <1.4> 2023-03-09T22:20:14.013742+01:00 Telcontar krusader 6836 - - 22:20:14.012-warning kf.kio.widgets unknown@0 # Failed to check which JobView API is supported "The name org.kde.kuiserver was not provided by any .service files"
are programmers errors.
I suspect that messages like these are caused by developers who assume that their applications will always execute in a full-blown desktop designed for their use (in this case, KDE). I get the same thing with Gnome applications that assume that all of Gnome is installed, though I never use the Gnome desktop. The ones that really irritate me are those from the DE that I'm running, that spam my terminal session when I start them from the command line. I can't see any excuse for their being written to the terminal, especially since they aren't complaining about things that stop the applications' successful execution.
Well, in that case they are intended to not be run from the terminal, unless you are debugging the application. They should all have a --quiet option. -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)