Problem
On Linux, when IVPN UI is launched normally (via .desktop file / application
menu), the system journal (journalctl) is continuously flooded with low-level
daemon protocol trace messages:
ivpn-ui[1234]: ==> ConnectSettings [42]
ivpn-ui[1234]: <== SettingsResp [42]
ivpn-ui[1234]: ==> PingServers [43]
ivpn-ui[1234]: <== PingServersResp [43]
...
These messages are generated for every request/response exchanged between
the UI and the IVPN daemon, which happens frequently during normal operation.
Root Cause
The electron-log library defaults its console transport to 'debug' level.
When the app is launched via the desktop session (not a terminal), the
process stdout/stderr is captured by systemd and forwarded to journald,
so all debug output ends up in the system log.
Expected Behavior
The system journal should only contain warnings and errors from the IVPN UI,
not routine internal protocol traffic.
Problem
On Linux, when IVPN UI is launched normally (via .desktop file / application
menu), the system journal (journalctl) is continuously flooded with low-level
daemon protocol trace messages:
These messages are generated for every request/response exchanged between
the UI and the IVPN daemon, which happens frequently during normal operation.
Root Cause
The electron-log library defaults its console transport to 'debug' level.
When the app is launched via the desktop session (not a terminal), the
process stdout/stderr is captured by systemd and forwarded to journald,
so all debug output ends up in the system log.
Expected Behavior
The system journal should only contain warnings and errors from the IVPN UI,
not routine internal protocol traffic.