Cheese exits with errors on Razer Blade Pro

[Steve Kondik]

The camera on the new Razer Blade Pro does not work correctly with Ubuntu. With the default resolution (1920x1080), Cheese plays a few frames and exits with the following error:

libv4l2: error got 4 consecutive frame decode errors, last error: v4l-convert: libjpeg error: End Of Image

(cheese:15842): cheese-WARNING **: Failed to allocate a buffer: gstv4l2src.c(884): gst_v4l2src_create (): /GstCameraBin:camerabin/GstWrapperCameraBinSrc:camera_source/GstBin:bin18/GstV4l2Src:v4l2src1

If I reduce the resolution to 640x480, it works fine. The same issue occurs in guvcview and is likely a lower layer issue, so feel free to relocate this bug.

The device is:

Bus 001 Device 006: ID 0bda:579f Realtek Semiconductor Corp.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: cheese 3.22.0-1ubuntu1
ProcVersionSignature: Ubuntu 4.8.0-29.31-generic 4.8.11
Uname: Linux 4.8.0-29-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
CurrentDesktop: GNOME
Date: Fri Dec 2 21:03:14 2016
MachineType: Razer Blade Pro
RelatedPackageVersions:
 cheese 3.22.0-1ubuntu1
 cheese-common 3.22.0-1ubuntu1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/07/2016
dmi.bios.vendor: Razer
dmi.bios.version: 04.00
dmi.board.name: Blade Pro
dmi.board.vendor: Razer
dmi.board.version: Late 2016
dmi.chassis.type: 9
dmi.chassis.vendor: Razer
dmi.chassis.version: Blade Pro(Late 2016)
dmi.modalias: dmi:bvnRazer:bvr04.00:bd11/07/2016:svnRazer:pnBladePro:pvr1.04:rvnRazer:rnBladePro:rvrLate2016:cvnRazer:ct9:cvrBladePro(Late2016):
dmi.product.name: Blade Pro
dmi.product.version: 1.04
dmi.sys.vendor: Razer

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1647015

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.

[Joseph Salisbury (jsalisbury)]

Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.9 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.9-rc8

[Steve Kondik (cyanogen)]

I'm running 4.9.0-040900rc7-generic from the mainline builds and the issue is present.

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]