Error parsing PCC subspaces from PCCT --- On startup

[Robert Shields]

New install of Ubuntu 16.04 from Windows 10

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-21-generic 4.4.0-21.37 [modified: boot/vmlinuz-4.4.0-21-generic]
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: shieldrj 1781 F.... pulseaudio
 /dev/snd/controlC0: shieldrj 1781 F.... pulseaudio
CurrentDesktop: Unity
Date: Fri May 6 09:08:38 2016
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=3b95cab7-d12d-4d82-aad7-7b9697484746
InstallationDate: Installed on 2016-05-03 (2 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: LENOVO 20DQ001LUS
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic root=UUID=8a46bfbe-3fd3-4c14-b860-40af27c8c96b ro quiet splash
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-21-generic N/A
 linux-backports-modules-4.4.0-21-generic N/A
 linux-firmware 1.157
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/25/2015
dmi.bios.vendor: LENOVO
dmi.bios.version: N19ET35W (1.08 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20DQ001LUS
dmi.board.vendor: LENOVO
dmi.board.version: SDK0E50510 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: dmi:bvnLENOVO:bvrN19ET35W(1.08):bd03/25/2015:svnLENOVO:pn20DQ001LUS:pvrThinkPadS5Yoga15:rvnLENOVO:rn20DQ001LUS:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.name: 20DQ001LUS
dmi.product.version: ThinkPad S5 Yoga 15
dmi.sys.vendor: LENOVO

[Marc Deslauriers (mdeslaur)]

Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.

[Brad Figg (brad-figg)]

This change was made by a bot.

[penalvch (penalvch)]

Robert Shields, thank you for reporting this and helping make Ubuntu better.

As per http://support.lenovo.com/us/en/products/Laptops-and-netbooks/ThinkPad-Yoga-Series-laptops/ThinkPad-Yoga-15?tabName=Downloads&linkTrack=Mast:SubNav:Support:Drivers%20and%20Software|Drivers%20and%20Software&beta=false an update to your computer's buggy, insecure, and outdated BIOS is available (1.22). If you update to this following https://help.ubuntu.com/community/BIOSUpdate does it change anything?

For more on BIOS updates and linux, please see https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette .

Please note your current BIOS is already in the Bug Description, so posting this on the old BIOS would not be helpful.

Also, you don't have to create a new bug report.

Once the BIOS is updated, if the problem is still reproducible:
1) Please provide the output of the following terminal command (not perform an apport-collect):
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
2) Please make a comment specifically advising on if there was an improvement or not.
3) Please mark this report Status Confirmed.

If it's not reproducible, please mark this as Invalid.

Thank you for your understanding.

[Christopher Kosciuk (cjkosciuk)]

This bug also affects me. I'm using a Lenovo ThinkPad T450s with an updated BIOS.

$ uname -a
Linux T450s 4.4.0-31-generic #50-Ubuntu SMP Wed Jul 13 00:07:12 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

$ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
JBET61WW (1.25 )
07/13/2016

[Launchpad Janitor (janitor)]

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

[penalvch (penalvch)]

Christopher Kosciuk (cjkosciuk), it will help immensely if you filed a new report with the Ubuntu repository kernel (not mainline/upstream) via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.

For more on why this is helpful, please see https://wiki.ubuntu.com/ReportingBugs.