I found a few sources that mention it could be related to multimedia keys or possibly microphone input. Maybe they can provide some clues:
Added gnome, workstation
You are using a theme. Does this happen when using default Adwaita?
Yes ! right now I am using a theme, but this issue was there while using the default theme too…
Thank you Olivier, below links are still unable to provide me the solution to the problem…can you please suggest me some more solutions to try on…
You could consider filing a bug at the gnome-shell tracker:
It does not look like a bug and I would be reluctant to just file a bug against Gnome until I found out more about the actual issue. It does look like a configuration thing. Like noted, it could be to do with the media keys.
@acc-sharmadeepak please include the details about your system, as well it would be good to note if you are using remote communication SW such as Zoom or others like it that will try to use cameras, microphones, etc …
The fact that it’s a broad and unclear symbol that could represent many different problems or causes qualifies it as a bug. Any error message should be clear and informative. If there are no means to determine as a user what the indication means and if it is interfering with your normal workflow, it’s a bug.
(I’m a UX developer myself and i would accept this as a bug)
That may be, but it is an indicator that something is being prevented from accessing a system resource (likely), so it is likely not the shell that is causing the behaviour but the app that is not behaving appropriately in the shell. I still am not convinced that it constitutes a Gnome issue. Frankly, there has been no troubleshooting in this discussion of the OP’s problem, which is also not clearly stated. Until there is more info from @acc-sharmadeepak on what the system setup is, and when exactly this icon appears during their workflow, we are only speculating. I would like to help with the actual problem, and for that more facts are needed.
Yes both are valid issues i think. There is an underlying cause that OP might be able to find, and then there is the vague intrusive desktop symbol that provides little information.
For the former perhaps more information can be gathered by looking into system logs or by checking all peripherals (keyboard, mouse, headphones, microphone, camera, USB etc) for potential problems.
For the latter OP could file a bug with gnome-shell, if they determine it is the wrong place they will let him know. For future generations of users it would be good if this indicator were replaced by a more informative error message.
I think this is not really a Gnome thing. I would imagine there is a default icon that Gnome provides for such behaviour that app dev’s are encouraged to replace with a more descriptive one.
In any case, you and I discussing the potential is still not helping the OP with their specific issue, I would like to stay on topic for them please.
Hello @acc-sharmadeepak ,
Could you please install inxi if you haven’t already? You can do it in a terminal with sudo dnf install inxi. Once installed please run inxi -b in a terminal to get the basic info from your system that you can post here using the </> icon in the post editing window.
I have filed an issue on the GNOME tracker for this issue which can be found back here:
A developer has responded and indicates that the notice originates here:
This OSD gets shown by the media keys plugin of gnome-settings-daemon when the user presses a multimedia key that tries to interact with a media player, but no player is currently running. So the root cause is probably somewhere at the hardware or input driver level.
System Details Report
Report details
- Date generated: 2024-07-27 19:28:30
Hardware Information:
- Hardware Model: Lenovo Lenovo V130-15IKB
- Memory: 4.0 GiB
- Processor: Intel® Core™ i3-6006U × 4
- Graphics: Intel® HD Graphics 520 (SKL GT2)
- Disk Capacity: 1.1 TB
Software Information:
- Firmware Version: 8VCN26WW
- OS Name: Fedora Linux 40 (Workstation Edition)
- OS Build: (null)
- OS Type: 64-bit
- GNOME Version: 46
- Windowing System: Wayland
- Kernel Version: Linux 6.8.5-301.fc40.x86_64
System Details Report
Report details
- Date generated: 2024-07-27 19:28:30
Hardware Information:
- Hardware Model: Lenovo Lenovo V130-15IKB
- Memory: 4.0 GiB
- Processor: Intel® Core™ i3-6006U × 4
- Graphics: Intel® HD Graphics 520 (SKL GT2)
- Disk Capacity: 1.1 TB
Software Information:
- Firmware Version: 8VCN26WW
- OS Name: Fedora Linux 40 (Workstation Edition)
- OS Build: (null)
- OS Type: 64-bit
- GNOME Version: 46
- Windowing System: Wayland
- Kernel Version: Linux 6.8.5-301.fc40.x86_64
here are the details of the system I am using RN.
@acc-sharmadeepak since the issue will most likely be connected to your keyboard, it might help to walk through the steps mentioned in the second article posted earlier (from MUO).
It’s possible that your keyboard driver is issuing media keypresses on it’s own accord. You can test this with the ‘evtest’ tool described in the article.
[Edit:] Another test you can do is whether your system loads the intel_vbtn kernel module that is described as a possible culprit. You can determine if it is loaded by issuing this in a terminal:
lsmod | grep vbtn
If it doesn’t give back any results you can rule that out.
sure @litemotiv Olivier, let me try this too
Deepak if you’re still looking into this issue, one of the GNOME devs responded to the upstream ticket with some additional information for testing. You can find it back on the Gitlab link mentioned earlier, and you can also respond there if you want to ask them for additional information.
Good luck 