cheese display corrupted under Ubuntu 22.04

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1967843

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Thank you to report this bug and make Ubuntu better,

Could you please run: apport-collect 1967843 from you terminal again in order to drag relevant info about cheese into this bug?

Thank you!

Thank you for your bug report, do you have the same issue if you start

$ GST_V4L2_USE_LIBV4L2=1 gst-launch-1.0 v4l2src ! xvimagesink

?

apport information

apport information

apport information

apport information

apport information

apport information

Unlike cheese, 'ST_V4L2_USE_LIBV4L2=1 gst-launch-1.0 v4l2src ! xvimagesink' displays the webcam image fine.

I also can confirm that the warnings...

(cheese:2554): cheese-WARNING **: 16:50:13.024: A lot of buffers are being dropped.: ../libs/gst/base/gstbasesink.c(3143): gst_base_sink_is_too_late (): /GstCameraBin:camerabin/GstViewfinderBin:vf-bin/ClutterGstVideoSink:cluttergstvideosink0:
There may be a timestamping problem, or this computer is too slow.

and associated rendering artifacts in the cheese display occur for both the nouveau and nvidia 510 drivers.

Hi Jack,

Thanks for reporting. I have a Logitech C270 camera, and I am also affected.

Attached is what I see, I get green and purple bars, and overall terrible performance.

I am on Jammy 5.15.0-25-generic, Wayland session, gnome 42, cheese 41.1-1build1.

I will start investigating.

Thanks,
Matthew

I downgraded cheese from 41.1-1build1 to 3.38.0-4 and it works fine again. Seems to be a cheese 41 problem.

GST_V4L2_USE_LIBV4L2=1 gst-launch-1.0 v4l2src ! xvimagesink

works fine, as well as using the webcam in Google Meet with Firefox.

Upstream bug: https://gitlab.gnome.org/GNOME/cheese/-/issues/126

I have determined the root cause via git bisecting the master branch.

The issue was introduced in:

commit 58de82b3d463b69f4c0bef75667e47020924e28b
Author: Jakub Adam <email address hidden>
Date: Tue Sep 3 13:00:30 2019 +0200
Subject: Support camera video formats with MJPEG output
Link: https://gitlab.gnome.org/GNOME/cheese/-/commit/58de82b3d463b69f4c0bef75667e47020924e28b

If I checkout current master branch and revert this commit, things work fine.

I will report the issue to upstream, and we can go from there.

It is very odd that Fedora 36 beta also uses a build of cheese 41.1 with minimal patching and the apparently the same optimizations yet it doesn't exhibit this artifact.

Matthew, do you see the same corruption if you boot the same machine with the Logitech C270 camera under a Fedora 36 Beta live image? It would be interesting to know if their Fedora cheese 41.1 package doesn't show the same artifact like it doesn't on my hardware.

I can confirm that rebuilding the current 41.1-1build1 cheese packaging with the offending commit reverted...

https://gitlab.gnome.org/GNOME/cheese/-/commit/58de82b3d463b69f4c0bef75667e47020924e28b.patch

...allows my Logitech C525 webcam to operate properly again.

Hi Jack,

I booted a Fedora 36 Beta live image like you suggested, and cheese works fine there on my machine.

Their cheese includes the above patch. I had a look around, it has a 5.17 kernel, and gstreamer 1.20.

Ubuntu has gstreamer 1.20.1, and when I booted my machine into a 5.17 kernel, I found that the issue still persists. So it doesn't appear to be a kernel issue.

Will have to try and keep narrowing it down.

Matthew

Just an additional info:
The issue also presents when Take a Picture is selected in Profile image change.

Using Cheese (with Logitech C270), selecting 640x480 resolution provides good picture.

Also with Logitech C270. 640x480 provides good picture but you can't take a photo.

$ cheese

(cheese:19369): Gdk-WARNING **: 15:21:08.634: Native Windows taller than 65535 pixels are not supported
Unsupported modifier, resource creation failed.
XXX: resource creation failed
Unsupported modifier, resource creation failed.
XXX: resource creation failed
Unsupported modifier, resource creation failed.
XXX: resource creation failed
Unsupported modifier, resource creation failed.
XXX: resource creation failed

(cheese:19369): cheese-WARNING **: 15:21:40.621: Output state was not configured: ../gst-libs/gst/video/gstvideoencoder.c(2281): gst_video_encoder_can_push_unlocked (): /GstCameraBin:camerabin/GstEncodeBin:image-encodebin/GstJpegEnc:jpegenc0

I added a fix for this to Arch's `clutter-gst` (bug link https://bugs.archlinux.org/task/74222):

https://github.com/archlinux/svntogit-packages/blob/packages/clutter-gst/trunk/0001-video-sink-Remove-RGBx-BGRx-support.patch

This allows MJPEG cameras to work properly.

Jan also added a testcase to the upstream bug, that calls clutter-gst directly and does not require cheese:

$ gst-launch-1.0 videotestsrc ! jpegenc ! jpegdec ! clutterautovideosink

Attached is a picture running the testcase with clutter-gst-3.0 3.0.27-2build2, showing distorted picture.

I built the patch Jan provided into a test package, available in the below ppa:

https://launchpad.net/~mruffell/+archive/ubuntu/lp1967843-test

When I install it, the testcase is fixed, shown in the attachment, and cheese works as normal.

Jeremy, shall we submit the patch to Debian, and SRU to Ubuntu? It seems the upstream clutter-gst project is now archived and not accepting new patches.

Status changed to 'Confirmed' because the bug affects multiple users.

My Ubuntu 22.04 also affected. After upgrading from 21.10 the Cheese shows blank screen.
Running from terminal this is the message:
$ cheese

(cheese:88137): cheese-WARNING **: 20:11:16.797: Internal data stream error.: ../libs/gst/base/gstbasesrc.c(3127): gst_base_src_loop (): /GstCameraBin:camerabin/GstWrapperCameraBinSrc:camera_source/GstBin:bin18/GstPipeWireSrc:pipewiresrc1:
streaming stopped, reason not-negotiated (-4)

And also affected the latest Zoom client.

I'm on Ubuntu 22.04:
Linux 5.15.0-27-generic #28-Ubuntu SMP
Same problems with chees as reported above:
(cheese:5095): cheese-WARNING **: 19:48:12.491: A lot of buffers are being dropped.: ../libs/gst/base/gstbasesink.c(3143): gst_base_sink_is_too_late (): /GstCameraBin:camerabin/GstViewfinderBin:vf-bin/ClutterGstVideoSink:cluttergstvideosink0:
There may be a timestamping problem, or this computer is too slow.

GST_V4L2_USE_LIBV4L2=1 gst-launch-1.0 v4l2src ! xvimagesink
Works fine! Same for skype and google meeting.

A patch in the official repo would be very much appreciated.

Hello Jack, or anyone else affected,

Accepted clutter-gst-3.0 into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/clutter-gst-3.0/3.0.27-2ubuntu1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-jammy. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Hi all, the new package did solve the bug for me — Cheese display now correct, captured pictures & videos also OK.

Package: libclutter-gst-3.0-0
Version: 3.0.27-2ubuntu1
Status: install ok installed

This bug was fixed in the package clutter-gst-3.0 - 3.0.27-3

---------------
clutter-gst-3.0 (3.0.27-3) unstable; urgency=medium

  * Add patch from Arch Linux to fix corrupted display with Cheese
    (LP: #1967843)

 -- Jeremy Bicha <email address hidden> Thu, 12 May 2022 16:30:52 -0400

Same problem here with a Logitech C505 on Ubuntu 22.04.

Performing verification for Jammy.

Starting with the broken 3.0.27-2build2 in -release, running

gst-launch-1.0 videotestsrc ! jpegenc ! jpegdec ! clutterautovideosink

shows a grey picture with vertical bars. Opening cheese, we see the same vertical bars, poor video performance and purple lines.

I enabled -proposed and installed 3.0.27-2ubuntu1, and re-ran

gst-launch-1.0 videotestsrc ! jpegenc ! jpegdec ! clutterautovideosink

and had cheese running. Performance was great, nice and smooth, and picture is correct.

Tested with my Logitech C720 webcam, and attached is a screenshot of everything running with 3.0.27-2ubuntu1 from -proposed.

Happy to mark as verified for Jammy.

I can confirm that the update fixes the issue for me.
In particular, Zoom works again now.

This bug was fixed in the package clutter-gst-3.0 - 3.0.27-2ubuntu1

---------------
clutter-gst-3.0 (3.0.27-2ubuntu1) jammy; urgency=medium

  * Add patch from Arch Linux to fix corrupted display with Cheese
    (LP: #1967843)

 -- Jeremy Bicha <email address hidden> Thu, 12 May 2022 16:48:21 -0400

The verification of the Stable Release Update for clutter-gst-3.0 has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

I can confirmed the original issue gone after installing the version from comment#37