-
Notifications
You must be signed in to change notification settings - Fork 0
Logging
devlinman edited this page Feb 1, 2026
·
1 revision
- If you wish to see or store the logs, then turn on
Debug: Enable File Logging. - The log file will be created at
~/.cache/whatsit/whatsit.log. - In
v5.0.0, the log file will be automatically deleted when you turn off the toggle.
$ cat ~/.cache/whatsit/whatsit.log
[01-02-2026 23:00:49] File logging ENABLED
[01-02-2026 23:00:58] Close event ignored -> Minimizing to tray.
[01-02-2026 23:00:58] Use Less Memory: Unloading content to dark blank page
[01-02-2026 23:00:58] Starting periodic check timer: 2 minutes
[01-02-2026 23:01:03] Memory State: Ensuring content is loaded
[01-02-2026 23:01:09] Applying autostart: DISABLED
[01-02-2026 23:01:13] Applying autostart: ENABLED
[01-02-2026 23:01:26] WebEngineHelper: Setting audio muted to 0
[01-02-2026 23:01:30] WebEngineHelper: Setting audio muted to 1
- Info from log file is sometimes helpful to debug.
- Consider attaching the log file (if possible) when you open bug reports. they will help.
- Even when
Debug: Enable File Loggingis off, the app still logs to stdout. - When the app crashes or when it can not or will not open a GUI, this may be your savior when debugging.
- You can see these logs by running the app from a terminal emulator. For example:
$ whatsit
[01-02-2026 23:05:21] Application starting...
[01-02-2026 23:05:21] Checking for existing instance...
[01-02-2026 23:05:21] Loading configuration...
[01-02-2026 23:05:21] Applying autostart: ENABLED
[01-02-2026 23:05:21] Syncing configuration to disk: /home/devlinman/.config/whatsit/whatsit.ini
[01-02-2026 23:05:21] MainWindow constructor
[01-02-2026 23:05:21] Loading configuration...
[01-02-2026 23:05:21] Applying autostart: ENABLED
[01-02-2026 23:05:21] Syncing configuration to disk: /home/devlinman/.config/whatsit/whatsit.ini
[01-02-2026 23:05:21] WebEngineHelper::initialize
[01-02-2026 23:05:21] WebEngineHelper: Setting audio muted to 1
[01-02-2026 23:05:21] Found Custom App icon:
[01-02-2026 23:05:21] WhatsApp
[01-02-2026 23:05:21] Desktop file is up to date.
[01-02-2026 23:05:21] Starting IPC server...
[01-02-2026 23:05:21] Low-memory startup: Delaying load of https://web.whatsapp.com
[01-02-2026 23:05:21] Starting periodic check timer (Startup): 2 minutes
[01-02-2026 23:05:26] Memory State: Ensuring content is loaded
[01-02-2026 23:05:29] File logging DISABLED
Deleting log file: /home/devlinman/.cache/whatsit/whatsit.log
Log file deleted successfully.
[01-02-2026 23:05:31] Close event ignored -> Minimizing to tray.
[01-02-2026 23:05:31] Use Less Memory: Unloading content to dark blank page
[01-02-2026 23:05:31] Starting periodic check timer: 2 minutes
^C
- These logs are detailed, but they do not contain much personally identifiable information.
- However, through these logs, it is possible to see when you opened the app, what options you have enabled in it, your file paths, etc. - mildly concerning private information.
- Note that leaving the option turned on will generate immense amount of logs. Don't forget turning it off.
- To be absolutely sure that the app is logging everything, you may use the following command in the terminal:
$ whatsit 2>&1 # redirect the stderr to stdout
- If you wish to start the app from command-line (terminal) but you don't want the logs, you may try to redirect the
stdout, though it is not recommended...
$ whatsit 1>/dev/null # Not Recommended
- To detach the app from the terminal, use:
$ whatsit & disown # Detach the app from terminal
-
Logger.handLogger.cppare the files that contain the logic for logging. - By reading the logs, you can pinpoint the origin of the bug/trace the output to specific
.cppfiles.
created by devlinman