Hi,
I'd like to suggest a UX improvement that I think would benefit many users, especially those who are not deeply familiar with Linux internals.
The Problem
When a kernel-level error occurs (for example, a GPU driver fault like nouveau: bus: MMIO read FAULT [ PRIVRING ]), the system plays a bell sound with no visual feedback whatsoever — no notification, no tooltip, no indicator. The user hears a mysterious "dink" sound and has no idea what caused it or whether it's something to worry about.
For non-technical users, this is confusing and provides zero actionable information. Even for developers, it's easy to miss the connection between the sound and the actual error.
Real-world example
I recently noticed a recurring bell sound on my system. After some investigation with journalctl -f -k, I found it was caused by:
nouveau 0000:03:00.0: bus: MMIO read of 00000000 FAULT at 6013d4 [ PRIVRING ]
This was happening repeatedly, but there was nothing on the screen to point me in the right direction.
The Suggestion
When the kernel bell is triggered — especially alongside kernel log entries of level WARNING or higher — mintreport or a lightweight background service could catch this and show a simple desktop notification such as:
⚠️ A system event was detected. Check Details → (opens a brief log summary)
This doesn't need to be verbose or alarming. Even a subtle, non-intrusive notification would be a significant UX improvement over total silence.
Hi,
I'd like to suggest a UX improvement that I think would benefit many users, especially those who are not deeply familiar with Linux internals.
The Problem
When a kernel-level error occurs (for example, a GPU driver fault like nouveau: bus: MMIO read FAULT [ PRIVRING ]), the system plays a bell sound with no visual feedback whatsoever — no notification, no tooltip, no indicator. The user hears a mysterious "dink" sound and has no idea what caused it or whether it's something to worry about.
For non-technical users, this is confusing and provides zero actionable information. Even for developers, it's easy to miss the connection between the sound and the actual error.
Real-world example
I recently noticed a recurring bell sound on my system. After some investigation with journalctl -f -k, I found it was caused by:
nouveau 0000:03:00.0: bus: MMIO read of 00000000 FAULT at 6013d4 [ PRIVRING ]
This was happening repeatedly, but there was nothing on the screen to point me in the right direction.
The Suggestion
When the kernel bell is triggered — especially alongside kernel log entries of level WARNING or higher — mintreport or a lightweight background service could catch this and show a simple desktop notification such as:
This doesn't need to be verbose or alarming. Even a subtle, non-intrusive notification would be a significant UX improvement over total silence.