Bug 2035106

Still an issue as of today. The version from Flathub works perfectly fine.

This has also been discussed in https://discussion.fedoraproject.org/t/debugging-webcam-microphone-in-cheese-flatpak/34189

If the one from Flathub works and the one from Fedora does not then someone should compare the permissions in the manifests:
- https://github.com/flathub/org.gnome.Cheese/blob/master/org.gnome.Cheese.yml
- https://src.fedoraproject.org/flatpaks/cheese

I believe the permissions are the same:

flathub's:

```
flatpak info --show-permissions org.gnome.Cheese
[Context]
shared=ipc;
sockets=x11;wayland;pulseaudio;fallback-x11;
devices=all;
filesystems=xdg-pictures;xdg-videos;
```

Fedora's:
```
flatpak info --show-permissions org.gnome.Cheese
[Context]
shared=ipc;
sockets=x11;wayland;pulseaudio;fallback-x11;
devices=all;
filesystems=xdg-pictures;xdg-videos;
```

Assuming I'm reading the manifest correctly they are also the same there:
https://github.com/flathub/org.gnome.Cheese/blob/master/org.gnome.Cheese.yml#L7-L14
https://src.fedoraproject.org/flatpaks/cheese/blob/stable/f/container.yaml#_9-16

I confirm the flathub version still shows the webcam feed, and the fedora-flatpak version still shows the "No device found" message.

I can get bash inside the cheese flatpak. If you tell me what to look for inside the container I can report back the difference.

I don't really know how Cheese works but removing access from a working Flatpak until it breaks will get you started.
Maybe the Runtime permissions are different between the Fedora Platform one and the Flatpak GNOME one?

This message is a reminder that Fedora Linux 35 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 35 on 2022-12-13.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '35'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 35 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Fedora Linux 35 entered end-of-life (EOL) status on 2022-12-13.

Fedora Linux 35 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.

I tracked this one down and it should be fixed with https://bodhi.fedoraproject.org/updates/FEDORA-FLATPAK-2023-1e9ccabe66 flatpak runtime update.

It turned out that the way gstreamer1-plugins-good was built didn't work for v4l2 detection and the fix was to build it with v4l2-gudev=disabled for flatpak. https://src.fedoraproject.org/rpms/gstreamer1-plugins-good/c/5a0d15ca6153c68276933c9595ce6d653d865ac3?branch=rawhide

FEDORA-FLATPAK-2023-1e9ccabe66 has been submitted as an update to Fedora 37 Flatpaks. https://bodhi.fedoraproject.org/updates/FEDORA-FLATPAK-2023-1e9ccabe66

FEDORA-FLATPAK-2023-1e9ccabe66 has been pushed to the Fedora 37 Flatpaks testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-FLATPAK-2023-1e9ccabe66

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

FEDORA-FLATPAK-2023-1e9ccabe66 has been pushed to the Fedora 37 Flatpaks stable repository.
If problem still persists, please make note of it in this bug report.