How do you launch AppImage via KDE GUI so it does not output anything into the syslog/journal

Help
,
1

Hello,

after many days, I have noticed that on KDE Neon with Plasma 6.6.1 an AppImage is spamming the syslog/journal with too many messages, being too verbose.

When i open the KDE aplications menu and right click the appimage launcher menu entry and go to properties, “Advanced” tab, enable “Run in terminal” with “terminal options” field set to “&>/dev/null”, then the “journalctl -xef” output is reduced to the apparmor log lines:

kernel: audit: type=1400 audit(…322:…): apparmor=“ALLOWED” operation=“file_lock” class=“file” profile=“/home/…/…/…AppImage//null-/tmp/…/AppRun//null-/tmp/…/…-…//null-/usr/bin/bash//null-/tmp/…/…-…-bin” name=“/…/.config/…/sql/..sqlite-shm” pid=1346879 comm=“…-…” requested_mask=“k” denied_mask=“k” fsuid=1000 ouid=1000
… requested_mask=“w” denied_mask=“w”
… requested_mask=“wk” denied_mask=“wk” fsuid=1000 ouid=1000

but these are still quite too frequent (multiple per second) and also need to run a terminal window seems to be inconvenient.

adding " &>/dev/null" to the “command-line arguments” field, turns it into “‘&>/dev/null’” (notice the quotation marks) and the logging remains too verbose.

So how do you please run the appimage silently (or to only log errors) via KDE apps menu?

Operating System: KDE neon User Edition
KDE Plasma Version: 6.6.1
KDE Frameworks Version: 6.23.0
Qt Version: 6.10.2
Kernel Version: 6.17.0-14-generic (64-bit)
Graphics Platform: Wayland
2

Should’nt there be a space between > and /dev/null eg “> /dev/null”?

3

no, that does not avoid that verbose output.

&> /dev/null
gets converted to:
'&>' /dev/null
(after saving the launcher menu entry and revisiting it)

4

Since the desktop is not involved with any application’s logging, it is not something it can influence either.

The application author might have options to reduce or deactivate it.

Your attempt to run the application “in terminal” suggests that its logging detects this and switches its logging to console output.
You could probably create a small start script that redirects the output and then use this script as the application in Plasma’s app menu.

1 Like
5

Thank you for the input, good idea, even it is not so easy. This worked:

cd /path/to/scripts/
nano abc-appimage-launcher

#!/bin/bash
# Launching the AppImage via this bash script prevents appimage emitting too many log lines into the syslog (journalctl -xef).
LANGUAGE=en_US $HOME/appspath/abc-x86_64-*.AppImage --no-sandbox &>/dev/null

chmod +x abc-appimage-launcher

Then add full path to that script into the app launcher menu item.

Even it still “SPAMs” journal with AppArmor messages mentioned in OP.

6

have you tried contacting the developer about resolving the issues raised in the log output?

it seems like it would be worth looking into rather than just trying to suppress it.

1 Like
7

Even it still “SPAMs” journal with AppArmor messages mentioned in OP.

Modify the script:

 > /dev/null 2>&1

Why are you running the no-sandbox switch? You do realize the security implications of that, correct? It likely means the appimage is corrupt, or incorrectly built - or cracked.