Bug 482614 - Detect camera usage from apps accessing the camera in a low-level way (e.g. accessing /dev/video* directly)
Summary: Detect camera usage from apps accessing the camera in a low-level way (e.g. a...
Status: CONFIRMED
Alias: None
Product: plasmashell
Classification: Plasma
Component: Camera Indicator widget (other bugs)
Version First Reported In: 6.0.1
Platform: Arch Linux Linux
: NOR wishlist
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
: 485438 492591 495288 508246 (view as bug list)
Depends on:
Blocks:
 
Reported: 2024-03-06 23:40 UTC by Sdar
Modified: 2025-08-14 14:57 UTC (History)
8 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Sdar 2024-03-06 23:40:40 UTC
SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols.
See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***


STEPS TO REPRODUCE
1. Connect a camera (In my case i was trying a ps eye)
2. Use the camera (ie: ffplay /dev/video0)

OBSERVED RESULT
The camera is not listed on the camera indicator and remains in "No camera is in use" even when there's actual output from the camera (tested on ffplay, v4l2 and zoom)

EXPECTED RESULT
The camera indicator should show that a camera is in use.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 
6.0.1
KDE Plasma Version: 6.0.1
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2

ADDITIONAL INFORMATION
Comment 1 Nate Graham 2024-03-07 17:49:19 UTC
It detects apps using it via PipeWire. It can't detect camera use for apps that open it in a lower-level way at the moment. Making this bug a wishlist requesting that it do so.
Comment 2 Sdar 2024-03-07 17:56:52 UTC
(In reply to Nate Graham from comment #1)
> It detects apps using it via PipeWire. It can't detect camera use for apps
> that open it in a lower-level way at the moment. Making this bug a wishlist
> requesting that it do so.

Oh, didn't know that, my camera has a led that turns on when in use so it's not really bothering me but some laptops don't, and having a way to tell if the camera is recording seems like a good idea. gj with kde6 btw runs great kudos to all the team.
Comment 3 Nate Graham 2024-03-07 17:57:43 UTC
Thanks a lot for the kind words! It's nice to know the work is appreciated.
Comment 4 Nate Graham 2024-10-28 03:59:27 UTC
*** Bug 495288 has been marked as a duplicate of this bug. ***
Comment 5 Nate Graham 2024-10-28 04:00:03 UTC
*** Bug 492591 has been marked as a duplicate of this bug. ***
Comment 6 Nate Graham 2025-04-16 20:01:03 UTC
*** Bug 485438 has been marked as a duplicate of this bug. ***
Comment 7 kde 2025-05-07 18:43:12 UTC
Ran into this today as well. MS Teams progressive web app doesn't trigger the widget when using the camera.

Under normal circumstances I'd agree that adding new functionality should be a feature request and not a bug report, but in this case I think the mere existence of the Camera Indicator implies that the widget is functional, and that users can rely on it to accurately reflect whether they're being seen by [n > 0] people on the Internet. This gap in functionality could have major repercussions for an unlucky user, and constitutes a clear privacy risk. Perhaps before we've added support for other methods of camera access, we should find a way to clearly warn the user that they can't rely on this widget.
Comment 8 John 2025-07-01 06:25:32 UTC
(In reply to kde from comment #7)
> Ran into this today as well. MS Teams progressive web app doesn't trigger
> the widget when using the camera.
> 
> Under normal circumstances I'd agree that adding new functionality should be
> a feature request and not a bug report, but in this case I think the mere
> existence of the Camera Indicator implies that the widget is functional, and
> that users can rely on it to accurately reflect whether they're being seen
> by [n > 0] people on the Internet. This gap in functionality could have
> major repercussions for an unlucky user, and constitutes a clear privacy
> risk. Perhaps before we've added support for other methods of camera access,
> we should find a way to clearly warn the user that they can't rely on this
> widget.

I fully agree with you on this one.
This should be considered a bug, not just a wish or a nice to have request!
In my opinion, problems, issues related to our privacy and security should be treated by default as bugs as they can very serious consequences such as huge fines, jail time or even death depending who the user is, in what country he / she is and what he / she has done.
I can't imagine what it could happen with whistleblowers, journalists and activists that are against the some authoritarian / dictatorial regime, which they think using open source software will provide protection against unauthorized access of their webcam, mike, Wi-Fi scanning for geolocation...

The fact that MS Teams web app, which is closed-source, made by Microsoft, an American company (known for its greed and eagerness for data collection) can access it without triggering any alert, shows how bad this really is!
What will happen when programs developed by companies part of or supported by the countries in BRICS or plain crackers try it?
As an European, fighting as much as I can the huge propaganda coming from the east on all social platforms, because I love the democracy that my country and the EU has and the rights that we have, I'm very much afraid that they one day could crack my computer and get a picture of my face to punish me and make me stop and this is a battle we Europeans cannot afford to lose!
Especially now, when it seems that democracies, including the biggest/ strongest one, are falling.

So, please reconsider the classification of this bug report!
If this is fixed, maybe it will also help KDE software being chosen to be used on government institutions in countries that are moving away from Microsoft's products.

Thank you very much!
Comment 9 Nate Graham 2025-08-14 14:57:04 UTC
*** Bug 508246 has been marked as a duplicate of this bug. ***