Feature Request: Show desktop notification when kernel bell is triggered by a hardware/driver error
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Quiet
- Tech stack
- python
- Domain
- desktop, observability, operating-systems
Research direction
Start by reproducing the reported behavior with journalctl -f -k and confirm how the kernel bell relates to WARNING-or-higher log entries. Define how mintreport or a lightweight background service would detect the event, present a non-intrusive desktop notification, and expose a brief log summary; done should include an agreed design and validation path.
Written by the indexing model from the issue text.
Description
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.
- Dominant language
- Python
- Stars
- 30
- Forks
- 26
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from linuxmint/mintreport
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
linuxmint/mintreport#137 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
linuxmint/mintreport#134 · 1 reaction ·
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
linuxmint/mintreport#133 ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
linuxmint/mintreport#131 ·
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
linuxmint/mintreport#130 ·
All issues in linuxmint/mintreport
Similar issues
-
bug confirmed issue
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
open-webui/open-webui#30750 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
OpenwaterHealth/openmotion-bloodflow-app#604 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
good first issue
Difficulty 1/5 Under an hour Newbie friendliness 90/100