[Kernel-packages] [Bug 1436940] Re: Atheros wifi 168c:0041(QCA6174) is not supported
I just tried the 20150903 backports and I didn't have to patch the code (still need to copy the firmware and create /etc/modprobe.d/ath10k.conf. Also, looking at the code from the backport, the firmware still needs to be copied to QCA6174 (instead of QCA6164). Guess it's getting better (maybe in a few months, there will be no need to do manual work). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1436940 Title: Atheros wifi 168c:0041(QCA6174) is not supported Status in linux package in Ubuntu: Confirmed Status in linux source package in Vivid: Confirmed Status in linux source package in Wily: Confirmed Bug description: The atheros wireless device (168c:0041) isn't supported by the ath10k_pci kernel driver. Found in several laptop models: Lenovo Z70 Lenovo G50-45 Lenovo G50-80 Lenovo Edge 15 Lenovo Yoga 3 11 Lenovo Flex 3-1470 Samsung ATIV Book 9 NP930X2K ProblemType: BugDistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-9-generic 3.19.0-9.9 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 ApportVersion: 2.16.2-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicholas 1695 F pulseaudio /dev/snd/controlC1: nicholas 1695 F pulseaudio CurrentDesktop: Unity Date: Thu Mar 26 09:47:16 2015 HibernationDevice: RESUME=UUID=5b068cd8-e60a-49b9-a88e-1581bb6b3dc1 InstallationDate: Installed on 2015-03-25 (1 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0cf3:e300 Atheros Communications, Inc. Bus 001 Device 003: ID 5986:0652 Acer, Inc Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80E5 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-generic root=UUID=e52867c5-0b50-42fb-8288-f30765f926c5 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-9-generic N/A linux-backports-modules-3.19.0-9-generic N/A linux-firmware1.143SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2015-03-26 (0 days ago) dmi.bios.date: 06/20/2014 dmi.bios.vendor: LENOVO dmi.bios.version: B0CN69WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lenovo G50-80 dmi.board.vendor: LENOVO dmi.board.version: 31900058 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G50-80 dmi.modalias: dmi:bvnLENOVO:bvrB0CN69WW:bd06/20/2014:svnLENOVO:pn80E5:pvrLenovoG50-80:rvnLENOVO:rnLenovoG50-80:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoG50-80: dmi.product.name: 80E5 dmi.product.version: Lenovo G50-80 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1436940/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1484159] Re: Qualcomm Atheros Device [168c:0042] (rev 30) not working on Ubuntu
Different machine: Acer ASpire E14 - E5-473G but same issue Network controller [0280]: Qualcomm Atheros Device [168c:0042] (rev 30) Subsystem: Foxconn International, Inc. Device [105b:e09a] -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1484159 Title: Qualcomm Atheros Device [168c:0042] (rev 30) not working on Ubuntu Status in linux package in Ubuntu: Triaged Bug description: Hi, Qualcomm Atheros Device [168c:0042] (rev 30) is not supported by linux kernal. Please add support. Thanks ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-61-generic 3.13.0-61.100 ProcVersionSignature: Ubuntu 3.13.0-61.100-generic 3.13.11-ckt22 Uname: Linux 3.13.0-61-generic i686 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu14 1658 F pulseaudio /dev/snd/controlC1: ubuntu14 1658 F pulseaudio CurrentDesktop: Unity Date: Wed Aug 12 20:31:24 2015 HibernationDevice: RESUME=UUID=0483444a-0d9a-4215-b36b-4aee75fd9ec0 InstallationDate: Installed on 2015-08-11 (0 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140722.2) IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: Acer Aspire E5-573 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-61-generic root=UUID=72a8a100-d5ec-4e9d-8bc5-45695001a29c ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-61-generic N/A linux-backports-modules-3.13.0-61-generic N/A linux-firmware 1.127.15 SourcePackage: linux StagingDrivers: rts5139 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/20/2015 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.11 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: ZORO_BH dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.11:bd04/20/2015:svnAcer:pnAspireE5-573:pvrV3.72:rvnAcer:rnZORO_BH:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Aspire E5-573 dmi.product.version: V3.72 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1484159/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1500242] Re: Bluetooth device (Jabra BT250, Audi A3 car kit) can not be connected with BQ Aquaris 4.5
It looks like you're still on ota5. Can you make sure you applied all recent OS updates? We've fixed some problems in the settings application with ota6 which should really improve the behavior you're seeing here. ** Tags added: after-bluez5 bluetooth ** Also affects: canonical-devices-system-image Importance: Undecided Status: New ** Changed in: bluez (Ubuntu) Assignee: (unassigned) => Simon Fels (morphis) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1500242 Title: Bluetooth device (Jabra BT250, Audi A3 car kit) can not be connected with BQ Aquaris 4.5 Status in Canonical System Image: New Status in bluez package in Ubuntu: New Bug description: STEPS: Requirements: Aquaris E4.5, Jabra BT250 blue tooth handset device (rather old one supports blue tooth 1.1 and therefore I thought should be no issue) or Audi car kit (A3 2012 model) 1. Put Jabra BT250 into receiving mode 2. Phone searches automatically every 15 - 30 seconds for a new blue tooth device 3. Phone finds Jabra BT250 and asks for pairing code 4. Enter code into phone 5. Jabra BT250 automatically exits the pairing mode (which is a sign that pairing should have worked) 6. Phone looses connection to Jabra BT250 7. Manual reconnection via phone works (shows Jabra BT250 as being connected) but ignores the device Same behaviour with Audi car kit (Audi A3, 2012 model) EXPECTED: I expect that the blue tooth kits work similar to my Seat Alhambra (also 2012 model) where the blue tooth pairing etc. works great (except some bugs which are already filed). ACTUAL: No connection to the blue tooth device VERSIONS: OS-Build-Number: 25 Ubuntu-Image: 20150825.1 POSSIBLE ROOT CAUSE: Is this issue also solved as soon as bluez5 is implemented? When will this be? To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1500242/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1478353] Re: bluetooth mouse sluggish
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1478353 Title: bluetooth mouse sluggish Status in linux package in Ubuntu: Expired Bug description: Bluetooth mouse became sluggish after updates. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-23-generic 3.19.0-23.24 ProcVersionSignature: Ubuntu 3.19.0-23.24-generic 3.19.8-ckt2 Uname: Linux 3.19.0-23-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: feri 2347 F pulseaudio CurrentDesktop: Unity Date: Sun Jul 26 10:32:08 2015 HibernationDevice: RESUME=UUID=1d1d2bfb-e088-4b98-9f29-8275ee426fce InstallationDate: Installed on 2013-03-02 (876 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MachineType: Dell Inc. Inspiron 5423 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-23-generic root=UUID=57c4d374-223f-4855-ac5b-cc8e74091214 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-23-generic N/A linux-backports-modules-3.19.0-23-generic N/A linux-firmware 1.143.2 SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2015-05-02 (85 days ago) dmi.bios.date: 09/17/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 0T6TG2 dmi.board.vendor: Dell Inc. dmi.board.version: A06 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA06:bd09/17/2012:svnDellInc.:pnInspiron5423:pvrNotSpecified:rvnDellInc.:rn0T6TG2:rvrA06:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 5423 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1478353/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1425252] Re: 0489:e076 - Qualcomm Atheros - Ubuntu 14.10 bluetooth does not see any devices
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1425252 Title: 0489:e076 - Qualcomm Atheros - Ubuntu 14.10 bluetooth does not see any devices Status in linux package in Ubuntu: Expired Bug description: This bug is related to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1352821 Bluetooth on Ubuntu 14.10 running on Acer Aspire V3-371-79RJ laptop does not work. WiFi on the same device works normally and also bluetooth seems to work normally, but when searching for external devices Ubuntu cannot see any bluetooth devices. I've tried to connect to both bluetooth mouse and an Android phone, no luck. On another Ubuntu laptop the same external bluetooth devices are visible and work ok. lspci -nnk printout includes this: 02:00.0 Network controller [0280]: Qualcomm Atheros AR9462 Wireless Network Adapter [168c:0034] (rev 01) Subsystem: Foxconn International, Inc. Device [105b:e07d] Kernel driver in use: ath9k and lsusb printout includes this: Bus 002 Device 002: ID 0489:e076 Foxconn / Hon Hai Full listings are attached. What was expected to happen: - Expected that Ubuntu would find my bluetooth mouse and phone when searching for new bluetooth devices. What happened instead: - Everything seemed to work ok, but nothing happened. Ubuntu does not see any bluetooth devices. Background Information: - Description: Ubuntu 14.10 - Release: 14.10 - gnome-bluetooth 3.8.2.1-0ubuntu9 - Hardware used: Acer Aspire V3-371-79RJ --- ApportVersion: 2.14.7-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jniirane 2414 F pulseaudio /dev/snd/controlC1: jniirane 2414 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.10 EcryptfsInUse: Yes InstallationDate: Installed on 2015-01-03 (52 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: Acer Aspire V3-371 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-31-generic root=UUID=c66b9d81-d91d-4201-85b9-a288b70f371f ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.16.0-31.41~lp1352821v1-generic 3.16.7-ckt5 RelatedPackageVersions: linux-restricted-modules-3.16.0-31-generic N/A linux-backports-modules-3.16.0-31-generic N/A linux-firmware 1.138.1 Tags: utopic Uname: Linux 3.16.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/05/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.12 dmi.board.asset.tag: No Asset Tag dmi.board.name: Aspire V3-371 dmi.board.vendor: Acer dmi.board.version: V1.12 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.12 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.12:bd09/05/2014:svnAcer:pnAspireV3-371:pvrV1.12:rvnAcer:rnAspireV3-371:rvrV1.12:cvnAcer:ct10:cvrV1.12: dmi.product.name: Aspire V3-371 dmi.product.version: V1.12 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1425252/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1479144] Re: package linux-image-extra-3.13.0-58-generic 3.13.0-58.97 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1479144 Title: package linux-image-extra-3.13.0-58-generic 3.13.0-58.97 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in linux package in Ubuntu: Expired Bug description: It displays this error everytime the system is rebooted ProblemType: Package DistroRelease: Ubuntu 14.04 Package: linux-image-extra-3.13.0-58-generic 3.13.0-58.97 ProcVersionSignature: Ubuntu 3.13.0-58.97-generic 3.13.11-ckt22 Uname: Linux 3.13.0-58-generic x86_64 NonfreeKernelModules: symap_custom_dkms_x86_64 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jlcadena 3079 F pulseaudio Date: Fri Jul 24 07:54:27 2015 ErrorMessage: subprocess installed post-installation script returned error exit status 1 HibernationDevice: RESUME=UUID=5a9bfaf3-7252-441a-b383-1845a80a4d5f InstallationDate: Installed on 2015-05-26 (62 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: LENOVO 23501K0 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-58-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-9ubuntu1.3 SourcePackage: linux Title: package linux-image-extra-3.13.0-58-generic 3.13.0-58.97 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/08/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G1ET93WW (2.53 ) dmi.board.asset.tag: Not Available dmi.board.name: 23501K0 dmi.board.vendor: LENOVO dmi.board.version: Win8 Pro DPK TPG dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG1ET93WW(2.53):bd03/08/2013:svnLENOVO:pn23501K0:pvrThinkPadT430:rvnLENOVO:rn23501K0:rvrWin8ProDPKTPG:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 23501K0 dmi.product.version: ThinkPad T430 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1479144/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1479021] Re: package linux-image-3.19.0-25-generic 3.19.0-25.26 failed to install/upgrade: subprocess new pre-installation script returned error exit status 128
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1479021 Title: package linux-image-3.19.0-25-generic 3.19.0-25.26 failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 Status in linux package in Ubuntu: Expired Bug description: install failed ProblemType: Package DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-25-generic 3.19.0-25.26 ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2 Uname: Linux 3.19.0-25-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lenah 1719 F pulseaudio Date: Tue Jul 28 06:13:50 2015 DuplicateSignature: package:linux-image-3.19.0-25-generic:3.19.0-25.26:subprocess new pre-installation script returned error exit status 128 ErrorMessage: subprocess new pre-installation script returned error exit status 128 HibernationDevice: RESUME=UUID=915d66ae-39ea-4a1e-b998-b38cddb14db2 InstallationDate: Installed on 2015-01-27 (181 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: Hewlett-Packard HP Pavilion dv6 Notebook PC ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-25-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-22ubuntu1.1 SourcePackage: linux Title: package linux-image-3.19.0-25-generic 3.19.0-25.26 failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 UpgradeStatus: Upgraded to vivid on 2015-06-14 (44 days ago) dmi.bios.date: 10/05/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.1B dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1658 dmi.board.vendor: Hewlett-Packard dmi.board.version: 10.31 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnHewlett-Packard:bvrF.1B:bd10/05/2011:svnHewlett-Packard:pnHPPaviliondv6NotebookPC:pvr058F1024471620100:rvnHewlett-Packard:rn1658:rvr10.31:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion dv6 Notebook PC dmi.product.version: 058F1024471620100 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1479021/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1450557] Re: 15.04: Broadwell HD 5500: screen corruption after logout
This behavior is now happening in new trusty installs. I downloaded the 14.04.3 (64 bit) ISO yesterday and installed it on the Lenovo x250. Upon shutting down, the corruption happens. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1450557 Title: 15.04: Broadwell HD 5500: screen corruption after logout Status in System76: New Status in linux package in Ubuntu: Triaged Bug description: On a 1366x768 Broadwell i3-5010U laptop (System76 Lemur lemu5), sometimes after I logout there is strange horizontal wrapping/scrolling corruption at the lightdm login screen plus a fixed vertical wrapping (see attached video). After the first time that the screen goes wonky, I see this error in dmesg: [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun Logging back into to Unity seems to consistently fix the screen corruption after a few seconds. This doesn't happen every time you logout, but probably happens 1/3 of the time or so. Occasionally I'll also see similar corruption during shutdown right around the time that X stops and Plymouth takes over. Interestingly, on a Broadwell i3 desktop connected to a 1920x1080 external display via HDMI, I've never encountered this problem. So it might be related to the specific 1366x768 screen resolution or to the embedded display port (eDP). I filed this bug against the kernel because of the dmesg error from the DRM module... but the problem could just as likely be in xserver- xorg-video-intel. For what it's worth, I've tried the latest 4.0 mainline build from the kernel PPA as well as the 4.1rc1 mainline build, and this problem still exists with both. I've also tried the slightly updated X packages for 15.04 from the xorg-edgers PPA, and this problem is likewise still present. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-15-generic 3.19.0-15.15 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: oem1360 F pulseaudio /dev/snd/controlC0: oem1360 F pulseaudio CurrentDesktop: Unity Date: Thu Apr 30 10:23:52 2015 HibernationDevice: RESUME=UUID=35ecebc1-3c1c-4a1f-9431-ce62b4803c50 MachineType: System76, Inc. Lemur ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-15-generic root=UUID=395797c2-b33c-46b5-9a64-abfcd6416195 ro acpi_backlight=vendor quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-15-generic N/A linux-backports-modules-3.19.0-15-generic N/A linux-firmware 1.143 SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/25/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: Lemur dmi.board.vendor: System76, Inc. dmi.board.version: lemu5 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: System76, Inc. dmi.chassis.version: lemu5 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.6.5:bd02/25/2015:svnSystem76,Inc.:pnLemur:pvrlemu5:rvnSystem76,Inc.:rnLemur:rvrlemu5:cvnSystem76,Inc.:ct9:cvrlemu5: dmi.product.name: Lemur dmi.product.version: lemu5 dmi.sys.vendor: System76, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/system76/+bug/1450557/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1498667] Re: [Toshiba P50W-B00F] Touchscreen no longer working
I'm having trouble updating the BIOS since I don't have an easy way of running Windows on this machine so it might take some time to test. Do you expect a BIOS update to fix this? Note that this functionality was working perfectly before and Googling for similar dmesg erorrs suggest problems like this in the past. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1498667 Title: [Toshiba P50W-B00F] Touchscreen no longer working Status in linux package in Ubuntu: Incomplete Bug description: Sometime in the last month or so my touchscreen stopped working on my Toshiba P50W. The dmesg log shows it constantly reconnecting to it: [ 556.407964] usb 1-4: new full-speed USB device number 119 using xhci_hcd [ 556.538341] usb 1-4: New USB device found, idVendor=04f3, idProduct=0381 [ 556.538347] usb 1-4: New USB device strings: Mfr=4, Product=14, SerialNumber=0 [ 556.538349] usb 1-4: Product: Touchscreen [ 556.538351] usb 1-4: Manufacturer: ELAN [ 556.538505] usb 1-4: ep 0x2 - rounding interval to 64 microframes, ep desc says 80 microframes [ 556.547788] input: ELAN Touchscreen as /devices/pci:00/:00:14.0/usb1/1-4/1-4:1.0/0003:04F3:0381.04A1/input/input2374 [ 556.600478] hid-multitouch 0003:04F3:0381.04A1: input,hiddev0,hidraw4: USB HID v1.10 Device [ELAN Touchscreen] on usb-:00:14.0-4/input0 [ 556.600584] usb 1-4: USB disconnect, device number 119 [ 556.860456] usb 1-4: new full-speed USB device number 120 using xhci_hcd [ 556.990494] usb 1-4: New USB device found, idVendor=04f3, idProduct=0381 [ 556.990500] usb 1-4: New USB device strings: Mfr=4, Product=14, SerialNumber=0 [ 556.990503] usb 1-4: Product: Touchscreen [ 556.990506] usb 1-4: Manufacturer: ELAN [ 556.990755] usb 1-4: ep 0x2 - rounding interval to 64 microframes, ep desc says 80 microframes [ 557.001248] input: ELAN Touchscreen as /devices/pci:00/:00:14.0/usb1/1-4/1-4:1.0/0003:04F3:0381.04A2/input/input2376 [ 557.002517] hid-multitouch 0003:04F3:0381.04A2: input,hiddev0,hidraw4: USB HID v1.10 Device [ELAN Touchscreen] on usb-:00:14.0-4/input0 [ 557.013831] usb 1-4: USB disconnect, device number 120 ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-11-generic 4.2.0-11.13 ProcVersionSignature: Ubuntu 4.2.0-11.13-generic 4.2.1 Uname: Linux 4.2.0-11-generic x86_64 ApportVersion: 2.18.1-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bob2041 F pulseaudio /dev/snd/controlC0: bob2041 F pulseaudio CurrentDesktop: Unity Date: Wed Sep 23 09:46:25 2015 HibernationDevice: RESUME=UUID=5033984a-21af-482d-a1fd-c075e818cd12 InstallationDate: Installed on 2013-12-26 (635 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: TOSHIBA Satellite P50W-B ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-11-generic root=UUID=885f0f10-b818-4eb4-8ff4-d067e16bef2f ro quiet splash nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-11-generic N/A linux-backports-modules-4.2.0-11-generic N/A linux-firmware1.148 SourcePackage: linux UpgradeStatus: Upgraded to wily on 2013-12-26 (635 days ago) dmi.bios.date: 08/08/2014 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.40 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Type2 - Board Product Name1 dmi.board.vendor: Type2 - Board Vendor Name1 dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis ManuFacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvr1.40:bd08/08/2014:svnTOSHIBA:pnSatelliteP50W-B:pvrPSVP2A-00F002:rvnType2-BoardVendorName1:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion: dmi.product.name: Satellite P50W-B dmi.product.version: PSVP2A-00F002 dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1498667/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1500218] Re: Please backport on 4.2 : Important fix for tcp kernel
** Also affects: linux (Ubuntu Wily) Importance: Undecided Status: Incomplete ** Changed in: linux (Ubuntu Wily) Status: Incomplete => Fix Committed ** Changed in: linux (Ubuntu Wily) Assignee: (unassigned) => Tim Gardner (timg-tpi) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1500218 Title: Please backport on 4.2 : Important fix for tcp kernel Status in linux package in Ubuntu: Fix Committed Status in linux source package in Wily: Fix Committed Bug description: The patch addresses a problem with cubic congestion control: https://github.com/torvalds/linux/commit/30927520dbae297182990bb21d08762bcc35ce1d http://bitsup.blogspot.fr/2015/09/thanks-google-tcp-team-for-open-source.html This indeed can be included to all the supported kernels to get benefit everywhere. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1500218/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1460909] Re: [Feature]intel PowerClamp driver support for Skylake
These patches are already included in the Wily kernel. ** Information type changed from Proprietary to Public ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Wily) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Wily) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1460909 Title: [Feature]intel PowerClamp driver support for Skylake Status in intel: New Status in linux package in Ubuntu: Fix Released Status in linux source package in Wily: Fix Released Bug description: Add Skylake processor support to intel PowerClamp Schedule: kernel: TBD To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1460909/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1499622] Re: multipath keep failure after the interface is recovered
The issue when I running the command above. Seems that it is blocked by EMC corporate firewall. stack@openstack:~$ apport-collect 1499622 ERROR: connecting to Launchpad failed: [Errno 1] _ssl.c:510: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed You can reset the credentials by removing the file "/home/stack/.cache/apport/launchpad.credentials" stack@openstack:~$ By the way, I tried to rest the credentials by removing the file above, still does not work. Is there any other command I can run and post the log manually? ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1499622 Title: multipath keep failure after the interface is recovered Status in linux package in Ubuntu: Confirmed Bug description: We encounter a multipath issue on Ubuntu 14.04.2 LTS. dm state (i.e. failed) cannot be recovered automatically when the interface is back. But path check state (i.e. faulty) can. In order to describe the issue clearly, the attached slides shows the detail of reproduce steps. Meanwhile, attachment also includes the output from multipath tool. P.S. We are writing the IO to the volume through dm device during the interface enable/disable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1499622/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1397863] Re: [Feature] Red Rock Canyon driver (for switch chip)
It should be in 4.2 kernel, close it. ** Changed in: intel Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1397863 Title: [Feature] Red Rock Canyon driver (for switch chip) Status in intel: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Vivid: Fix Released Bug description: Add support for Red Rock Canyon in fm10k driver Upstream status: kernel 3.18 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1397863/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1500274] Re: device descriptor read/64, error -71
It's having issues with Windows 8.1 also, even with LG Enact driver downloaded from LG.com. Hence, appears a HW issue. ** Changed in: linux (Ubuntu) Status: Triaged => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1500274 Title: device descriptor read/64, error -71 Status in linux package in Ubuntu: Invalid Bug description: When plugging in an LG Enact cell phone in via USB, and setting it to MTP, I'm expecting it to connect. Instead, I get errors in kern.log: Sep 27 16:32:42 monikerpc kernel: [95740.772217] usb 1-1: new low-speed USB device number 3 using xhci_hcd Sep 27 16:32:43 monikerpc kernel: [95741.936187] usb 1-1: new low-speed USB device number 5 using xhci_hcd Sep 27 16:32:43 monikerpc kernel: [95742.056435] usb 1-1: device descriptor read/64, error -71 Sep 27 16:32:43 monikerpc kernel: [95742.280452] usb 1-1: device descriptor read/64, error -71 Sep 27 16:32:43 monikerpc kernel: [95742.496374] usb 1-1: new low-speed USB device number 6 using xhci_hcd Sep 27 16:32:44 monikerpc kernel: [95742.616454] usb 1-1: device descriptor read/64, error -71 Sep 27 16:32:44 monikerpc kernel: [95742.840491] usb 1-1: device descriptor read/64, error -71 Sep 27 16:32:44 monikerpc kernel: [95743.056425] usb 1-1: new low-speed USB device number 7 using xhci_hcd Sep 27 16:32:44 monikerpc kernel: [95743.057137] usb 1-1: Device not responding to setup address. Sep 27 16:32:44 monikerpc kernel: [95743.261282] usb 1-1: Device not responding to setup address. Sep 27 16:32:44 monikerpc kernel: [95743.464381] usb 1-1: device not accepting address 7, error -71 Sep 27 16:32:45 monikerpc kernel: [95743.576465] usb 1-1: new low-speed USB device number 8 using xhci_hcd Sep 27 16:32:45 monikerpc kernel: [95743.577177] usb 1-1: Device not responding to setup address. Sep 27 16:32:45 monikerpc kernel: [95743.781228] usb 1-1: Device not responding to setup address. Sep 27 16:32:45 monikerpc kernel: [95743.984428] usb 1-1: device not accepting address 8, error -71 Sep 27 16:32:45 monikerpc kernel: [95743.984532] usb usb1-port1: unable to enumerate USB device Sep 27 16:32:58 monikerpc kernel: [95757.081642] usb 1-1: new low-speed USB device number 9 using xhci_hcd Sep 27 16:32:58 monikerpc kernel: [95757.201670] usb 1-1: device descriptor read/64, error -71 Sep 27 16:32:58 monikerpc kernel: [95757.425823] usb 1-1: device descriptor read/64, error -71 Sep 27 16:32:59 monikerpc kernel: [95757.641741] usb 1-1: new low-speed USB device number 10 using xhci_hcd Sep 27 16:32:59 monikerpc kernel: [95757.761851] usb 1-1: device descriptor read/64, error -71 Sep 27 16:32:59 monikerpc kernel: [95757.985773] usb 1-1: device descriptor read/64, error -71 Sep 27 16:32:59 monikerpc kernel: [95758.201734] usb 1-1: new low-speed USB device number 11 using xhci_hcd Sep 27 16:32:59 monikerpc kernel: [95758.202513] usb 1-1: Device not responding to setup address. Sep 27 16:32:59 monikerpc kernel: [95758.406515] usb 1-1: Device not responding to setup address. Sep 27 16:33:00 monikerpc kernel: [95758.609820] usb 1-1: device not accepting address 11, error -71 Sep 27 16:33:00 monikerpc kernel: [95758.721829] usb 1-1: new low-speed USB device number 12 using xhci_hcd Sep 27 16:33:00 monikerpc kernel: [95758.722572] usb 1-1: Device not responding to setup address. Sep 27 16:33:00 monikerpc kernel: [95758.926585] usb 1-1: Device not responding to setup address. Sep 27 16:33:00 monikerpc kernel: [95759.129866] usb 1-1: device not accepting address 12, error -71 Sep 27 16:33:00 monikerpc kernel: [95759.129965] usb usb1-port1: unable to enumerate USB device Sep 27 16:41:10 monikerpc kernel: [96248.613911] usb 1-1: new low-speed USB device number 14 using xhci_hcd Sep 27 16:41:24 monikerpc kernel: [96262.979197] usb 1-1: new low-speed USB device number 27 using xhci_hcd Sep 27 16:41:25 monikerpc kernel: [96263.743283] usb 1-1: new low-speed USB device number 29 using xhci_hcd Sep 27 16:42:05 monikerpc kernel: [96304.275050] usb 1-1: new low-speed USB device number 35 using xhci_hcd Sep 27 16:42:05 monikerpc kernel: [96304.395141] usb 1-1: device descriptor read/64, error -71 Sep 27 16:42:06 monikerpc kernel: [96305.195138] usb 1-1: new low-speed USB device number 37 using xhci_hcd Sep 27 16:42:06 monikerpc kernel: [96305.315111] usb 1-1: device descriptor read/64, error -71 Sep 27 16:42:06 monikerpc kernel: [96305.539248] usb 1-1: device descriptor read/64, error -71 Sep 27 16:42:07 monikerpc kernel: [96305.755170] usb 1-1: new low-speed USB device number 38 using xhci_hcd Sep 27 16:42:07 monikerpc kernel: [96305.875269] usb 1-1: device descriptor read/64, error -71 Sep 27 16:42:07 monikerpc kernel: [96306.099303] usb 1-1: device descriptor read/64, error -71 Sep 27 16:42:07 monikerpc kernel: [96306.3
[Kernel-packages] [Bug 1500274] Re: device descriptor read/64, error -71
** Tags removed: regression-release ** Tags added: trusty ** Description changed: When plugging in an LG Enact cell phone in via USB, and setting it to MTP, I'm expecting it to connect. Instead, I get errors in kern.log: Sep 27 16:32:42 monikerpc kernel: [95740.772217] usb 1-1: new low-speed USB device number 3 using xhci_hcd Sep 27 16:32:43 monikerpc kernel: [95741.936187] usb 1-1: new low-speed USB device number 5 using xhci_hcd Sep 27 16:32:43 monikerpc kernel: [95742.056435] usb 1-1: device descriptor read/64, error -71 Sep 27 16:32:43 monikerpc kernel: [95742.280452] usb 1-1: device descriptor read/64, error -71 Sep 27 16:32:43 monikerpc kernel: [95742.496374] usb 1-1: new low-speed USB device number 6 using xhci_hcd Sep 27 16:32:44 monikerpc kernel: [95742.616454] usb 1-1: device descriptor read/64, error -71 Sep 27 16:32:44 monikerpc kernel: [95742.840491] usb 1-1: device descriptor read/64, error -71 Sep 27 16:32:44 monikerpc kernel: [95743.056425] usb 1-1: new low-speed USB device number 7 using xhci_hcd Sep 27 16:32:44 monikerpc kernel: [95743.057137] usb 1-1: Device not responding to setup address. Sep 27 16:32:44 monikerpc kernel: [95743.261282] usb 1-1: Device not responding to setup address. Sep 27 16:32:44 monikerpc kernel: [95743.464381] usb 1-1: device not accepting address 7, error -71 Sep 27 16:32:45 monikerpc kernel: [95743.576465] usb 1-1: new low-speed USB device number 8 using xhci_hcd Sep 27 16:32:45 monikerpc kernel: [95743.577177] usb 1-1: Device not responding to setup address. Sep 27 16:32:45 monikerpc kernel: [95743.781228] usb 1-1: Device not responding to setup address. Sep 27 16:32:45 monikerpc kernel: [95743.984428] usb 1-1: device not accepting address 8, error -71 Sep 27 16:32:45 monikerpc kernel: [95743.984532] usb usb1-port1: unable to enumerate USB device Sep 27 16:32:58 monikerpc kernel: [95757.081642] usb 1-1: new low-speed USB device number 9 using xhci_hcd Sep 27 16:32:58 monikerpc kernel: [95757.201670] usb 1-1: device descriptor read/64, error -71 Sep 27 16:32:58 monikerpc kernel: [95757.425823] usb 1-1: device descriptor read/64, error -71 Sep 27 16:32:59 monikerpc kernel: [95757.641741] usb 1-1: new low-speed USB device number 10 using xhci_hcd Sep 27 16:32:59 monikerpc kernel: [95757.761851] usb 1-1: device descriptor read/64, error -71 Sep 27 16:32:59 monikerpc kernel: [95757.985773] usb 1-1: device descriptor read/64, error -71 Sep 27 16:32:59 monikerpc kernel: [95758.201734] usb 1-1: new low-speed USB device number 11 using xhci_hcd Sep 27 16:32:59 monikerpc kernel: [95758.202513] usb 1-1: Device not responding to setup address. Sep 27 16:32:59 monikerpc kernel: [95758.406515] usb 1-1: Device not responding to setup address. Sep 27 16:33:00 monikerpc kernel: [95758.609820] usb 1-1: device not accepting address 11, error -71 Sep 27 16:33:00 monikerpc kernel: [95758.721829] usb 1-1: new low-speed USB device number 12 using xhci_hcd Sep 27 16:33:00 monikerpc kernel: [95758.722572] usb 1-1: Device not responding to setup address. Sep 27 16:33:00 monikerpc kernel: [95758.926585] usb 1-1: Device not responding to setup address. Sep 27 16:33:00 monikerpc kernel: [95759.129866] usb 1-1: device not accepting address 12, error -71 Sep 27 16:33:00 monikerpc kernel: [95759.129965] usb usb1-port1: unable to enumerate USB device Sep 27 16:41:10 monikerpc kernel: [96248.613911] usb 1-1: new low-speed USB device number 14 using xhci_hcd Sep 27 16:41:24 monikerpc kernel: [96262.979197] usb 1-1: new low-speed USB device number 27 using xhci_hcd Sep 27 16:41:25 monikerpc kernel: [96263.743283] usb 1-1: new low-speed USB device number 29 using xhci_hcd Sep 27 16:42:05 monikerpc kernel: [96304.275050] usb 1-1: new low-speed USB device number 35 using xhci_hcd Sep 27 16:42:05 monikerpc kernel: [96304.395141] usb 1-1: device descriptor read/64, error -71 Sep 27 16:42:06 monikerpc kernel: [96305.195138] usb 1-1: new low-speed USB device number 37 using xhci_hcd Sep 27 16:42:06 monikerpc kernel: [96305.315111] usb 1-1: device descriptor read/64, error -71 Sep 27 16:42:06 monikerpc kernel: [96305.539248] usb 1-1: device descriptor read/64, error -71 Sep 27 16:42:07 monikerpc kernel: [96305.755170] usb 1-1: new low-speed USB device number 38 using xhci_hcd Sep 27 16:42:07 monikerpc kernel: [96305.875269] usb 1-1: device descriptor read/64, error -71 Sep 27 16:42:07 monikerpc kernel: [96306.099303] usb 1-1: device descriptor read/64, error -71 Sep 27 16:42:07 monikerpc kernel: [96306.315236] usb 1-1: new low-speed USB device number 39 using xhci_hcd Sep 27 16:42:08 monikerpc kernel: [96307.006425] usb 1-1: Device not responding to setup address. Sep 27 16:42:09 monikerpc kernel: [96307.663353] usb 1-1: Device not responding to setup address. Sep 27 16:42:09 monikerpc kernel: [96307.867299] usb 1-1: device not accepting address 39, error -71
[Kernel-packages] [Bug 1500277] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1500277 Title: iwlwifi :01:00.0: Microcode SW error detected. Restarting 0x200. Status in linux package in Ubuntu: Confirmed Bug description: dmesg: [16043.074355] iwlwifi :01:00.0: Microcode SW error detected. Restarting 0x200. [16043.074362] iwlwifi :01:00.0: CSR values: [16043.074365] iwlwifi :01:00.0: (2nd byte of CSR_INT_COALESCING is CSR_INT_PERIODIC_REG) [16043.074371] iwlwifi :01:00.0:CSR_HW_IF_CONFIG_REG: 0X00484b00 [16043.074377] iwlwifi :01:00.0: CSR_INT_COALESCING: 0Xff40 [16043.074383] iwlwifi :01:00.0: CSR_INT: 0X [16043.074389] iwlwifi :01:00.0:CSR_INT_MASK: 0X [16043.074395] iwlwifi :01:00.0: CSR_FH_INT_STATUS: 0X [16043.074401] iwlwifi :01:00.0: CSR_GPIO_IN: 0X003c [16043.074406] iwlwifi :01:00.0: CSR_RESET: 0X [16043.074412] iwlwifi :01:00.0:CSR_GP_CNTRL: 0X080403c5 [16043.074417] iwlwifi :01:00.0: CSR_HW_REV: 0X00b0 [16043.074423] iwlwifi :01:00.0: CSR_EEPROM_REG: 0Xdc540ffd [16043.074428] iwlwifi :01:00.0: CSR_EEPROM_GP: 0X9801 [16043.074434] iwlwifi :01:00.0: CSR_OTP_GP_REG: 0X00030001 [16043.074439] iwlwifi :01:00.0: CSR_GIO_REG: 0X00080044 [16043.07] iwlwifi :01:00.0:CSR_GP_UCODE_REG: 0X404d [16043.074450] iwlwifi :01:00.0: CSR_GP_DRIVER_REG: 0X [16043.074455] iwlwifi :01:00.0: CSR_UCODE_DRV_GP1: 0X [16043.074460] iwlwifi :01:00.0: CSR_UCODE_DRV_GP2: 0X [16043.074466] iwlwifi :01:00.0: CSR_LED_REG: 0X0040 [16043.074471] iwlwifi :01:00.0:CSR_DRAM_INT_TBL_REG: 0X880cb9bb [16043.074476] iwlwifi :01:00.0:CSR_GIO_CHICKEN_BITS: 0X27800200 [16043.074482] iwlwifi :01:00.0: CSR_ANA_PLL_CFG: 0X [16043.074487] iwlwifi :01:00.0: CSR_MONITOR_STATUS_REG: 0X43f7ffd7 [16043.074493] iwlwifi :01:00.0: CSR_HW_REV_WA_REG: 0X0001001a [16043.074498] iwlwifi :01:00.0:CSR_DBG_HPET_MEM_REG: 0X [16043.074501] iwlwifi :01:00.0: FH register values: [16043.074516] iwlwifi :01:00.0: FH_RSCSR_CHNL0_STTS_WPTR_REG: 0X0ca56600 [16043.074531] iwlwifi :01:00.0:FH_RSCSR_CHNL0_RBDCB_BASE_REG: 0X00ca5650 [16043.074546] iwlwifi :01:00.0: FH_RSCSR_CHNL0_WPTR: 0X00f0 [16043.074560] iwlwifi :01:00.0: FH_MEM_RCSR_CHNL0_CONFIG_REG: 0X80801114 [16043.074574] iwlwifi :01:00.0: FH_MEM_RSSR_SHARED_CTRL_REG: 0X00fc [16043.074588] iwlwifi :01:00.0:FH_MEM_RSSR_RX_STATUS_REG: 0X0703 [16043.074603] iwlwifi :01:00.0:FH_MEM_RSSR_RX_ENABLE_ERR_IRQ2DRV: 0X [16043.074617] iwlwifi :01:00.0:FH_TSSR_TX_STATUS_REG: 0X07ff0001 [16043.074632] iwlwifi :01:00.0: FH_TSSR_TX_ERROR_REG: 0X [16043.074635] iwlwifi :01:00.0: Loaded firmware version: 18.168.6.1 [16043.074756] iwlwifi :01:00.0: Start IWL Error Log Dump: [16043.074759] iwlwifi :01:00.0: Status: 0x02CC, count: 6 [16043.074762] iwlwifi :01:00.0: 0x198A | ADVANCED_SYSASSERT [16043.074765] iwlwifi :01:00.0: 0x00015920 | uPc [16043.074767] iwlwifi :01:00.0: 0x00015910 | branchlink1 [16043.074770] iwlwifi :01:00.0: 0x00015910 | branchlink2 [16043.074772] iwlwifi :01:00.0: 0xDBEA | interruptlink1 [16043.074774] iwlwifi :01:00.0: 0x | interruptlink2 [16043.074777] iwlwifi :01:00.0: 0x23FC | data1 [16043.074779] iwlwifi :01:00.0: 0x000A | data2 [16043.074781] iwlwifi :01:00.0: 0x01DC | line [16043.074784] iwlwifi :01:00.0: 0xEDC02035 | beacon time [16043.074786] iwlwifi :01:00.0: 0x9C715FCB | tsf low [16043.074789] iwlwifi :01:00.0: 0x017F | tsf hi [16043.074791] iwlwifi :01:00.0: 0x | time gp1 [16043.074793] iwlwifi :01:00.0: 0xBC02C2D7 | time gp2 [16043.074796] iwlwifi :01:00.0: 0x | time gp3 [16043.074798] iwlwifi :01:00.0: 0x754312A8 | uCode version [16043.074800] iwlwifi :01:00.0: 0x00B0 | hw version [16043.074803] iwlwifi :01:00.0: 0x00484B00 | board version [16043.074805] iwlwifi :01:00.0: 0x001C | hcmd [16043.074807] iwlwifi :01:00.0: 0x2F863840 | isr0 [16043.074810] iwlwifi :01:00.0: 0x1189F800 | isr1 [16043.074812] iwlwifi :01:00.0: 0x0E07 | isr2 [16043.07481
[Kernel-packages] [Bug 1500277] [NEW] iwlwifi 0000:01:00.0: Microcode SW error detected. Restarting 0x2000000.
Public bug reported: dmesg: [16043.074355] iwlwifi :01:00.0: Microcode SW error detected. Restarting 0x200. [16043.074362] iwlwifi :01:00.0: CSR values: [16043.074365] iwlwifi :01:00.0: (2nd byte of CSR_INT_COALESCING is CSR_INT_PERIODIC_REG) [16043.074371] iwlwifi :01:00.0:CSR_HW_IF_CONFIG_REG: 0X00484b00 [16043.074377] iwlwifi :01:00.0: CSR_INT_COALESCING: 0Xff40 [16043.074383] iwlwifi :01:00.0: CSR_INT: 0X [16043.074389] iwlwifi :01:00.0:CSR_INT_MASK: 0X [16043.074395] iwlwifi :01:00.0: CSR_FH_INT_STATUS: 0X [16043.074401] iwlwifi :01:00.0: CSR_GPIO_IN: 0X003c [16043.074406] iwlwifi :01:00.0: CSR_RESET: 0X [16043.074412] iwlwifi :01:00.0:CSR_GP_CNTRL: 0X080403c5 [16043.074417] iwlwifi :01:00.0: CSR_HW_REV: 0X00b0 [16043.074423] iwlwifi :01:00.0: CSR_EEPROM_REG: 0Xdc540ffd [16043.074428] iwlwifi :01:00.0: CSR_EEPROM_GP: 0X9801 [16043.074434] iwlwifi :01:00.0: CSR_OTP_GP_REG: 0X00030001 [16043.074439] iwlwifi :01:00.0: CSR_GIO_REG: 0X00080044 [16043.07] iwlwifi :01:00.0:CSR_GP_UCODE_REG: 0X404d [16043.074450] iwlwifi :01:00.0: CSR_GP_DRIVER_REG: 0X [16043.074455] iwlwifi :01:00.0: CSR_UCODE_DRV_GP1: 0X [16043.074460] iwlwifi :01:00.0: CSR_UCODE_DRV_GP2: 0X [16043.074466] iwlwifi :01:00.0: CSR_LED_REG: 0X0040 [16043.074471] iwlwifi :01:00.0:CSR_DRAM_INT_TBL_REG: 0X880cb9bb [16043.074476] iwlwifi :01:00.0:CSR_GIO_CHICKEN_BITS: 0X27800200 [16043.074482] iwlwifi :01:00.0: CSR_ANA_PLL_CFG: 0X [16043.074487] iwlwifi :01:00.0: CSR_MONITOR_STATUS_REG: 0X43f7ffd7 [16043.074493] iwlwifi :01:00.0: CSR_HW_REV_WA_REG: 0X0001001a [16043.074498] iwlwifi :01:00.0:CSR_DBG_HPET_MEM_REG: 0X [16043.074501] iwlwifi :01:00.0: FH register values: [16043.074516] iwlwifi :01:00.0: FH_RSCSR_CHNL0_STTS_WPTR_REG: 0X0ca56600 [16043.074531] iwlwifi :01:00.0:FH_RSCSR_CHNL0_RBDCB_BASE_REG: 0X00ca5650 [16043.074546] iwlwifi :01:00.0: FH_RSCSR_CHNL0_WPTR: 0X00f0 [16043.074560] iwlwifi :01:00.0: FH_MEM_RCSR_CHNL0_CONFIG_REG: 0X80801114 [16043.074574] iwlwifi :01:00.0: FH_MEM_RSSR_SHARED_CTRL_REG: 0X00fc [16043.074588] iwlwifi :01:00.0:FH_MEM_RSSR_RX_STATUS_REG: 0X0703 [16043.074603] iwlwifi :01:00.0:FH_MEM_RSSR_RX_ENABLE_ERR_IRQ2DRV: 0X [16043.074617] iwlwifi :01:00.0:FH_TSSR_TX_STATUS_REG: 0X07ff0001 [16043.074632] iwlwifi :01:00.0: FH_TSSR_TX_ERROR_REG: 0X [16043.074635] iwlwifi :01:00.0: Loaded firmware version: 18.168.6.1 [16043.074756] iwlwifi :01:00.0: Start IWL Error Log Dump: [16043.074759] iwlwifi :01:00.0: Status: 0x02CC, count: 6 [16043.074762] iwlwifi :01:00.0: 0x198A | ADVANCED_SYSASSERT [16043.074765] iwlwifi :01:00.0: 0x00015920 | uPc [16043.074767] iwlwifi :01:00.0: 0x00015910 | branchlink1 [16043.074770] iwlwifi :01:00.0: 0x00015910 | branchlink2 [16043.074772] iwlwifi :01:00.0: 0xDBEA | interruptlink1 [16043.074774] iwlwifi :01:00.0: 0x | interruptlink2 [16043.074777] iwlwifi :01:00.0: 0x23FC | data1 [16043.074779] iwlwifi :01:00.0: 0x000A | data2 [16043.074781] iwlwifi :01:00.0: 0x01DC | line [16043.074784] iwlwifi :01:00.0: 0xEDC02035 | beacon time [16043.074786] iwlwifi :01:00.0: 0x9C715FCB | tsf low [16043.074789] iwlwifi :01:00.0: 0x017F | tsf hi [16043.074791] iwlwifi :01:00.0: 0x | time gp1 [16043.074793] iwlwifi :01:00.0: 0xBC02C2D7 | time gp2 [16043.074796] iwlwifi :01:00.0: 0x | time gp3 [16043.074798] iwlwifi :01:00.0: 0x754312A8 | uCode version [16043.074800] iwlwifi :01:00.0: 0x00B0 | hw version [16043.074803] iwlwifi :01:00.0: 0x00484B00 | board version [16043.074805] iwlwifi :01:00.0: 0x001C | hcmd [16043.074807] iwlwifi :01:00.0: 0x2F863840 | isr0 [16043.074810] iwlwifi :01:00.0: 0x1189F800 | isr1 [16043.074812] iwlwifi :01:00.0: 0x0E07 | isr2 [16043.074814] iwlwifi :01:00.0: 0x0547FCC2 | isr3 [16043.074817] iwlwifi :01:00.0: 0x | isr4 [16043.074819] iwlwifi :01:00.0: 0x00800110 | isr_pref [16043.074821] iwlwifi :01:00.0: 0x000260A4 | wait_event [16043.074824] iwlwifi :01:00.0: 0x00D4 | l2p_control [16043.074826] iwlwifi :01:00.0: 0x | l2p_duration [16043.074828] iwlwifi :01:00.0: 0x0007 | l2p_mhvalid [16043.074831] iwlwifi :01:00.0: 0x00101040 | l2p_addr_match [16043.074833] iwlwifi :01:00.0: 0x0005
[Kernel-packages] [Bug 1500274] Re: device descriptor read/64, error -71
sudo cat /sys/kernel/debug/usb/usbmon/6u >bus2data.txt ** Attachment added: "bus2data.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1500274/+attachment/4476980/+files/bus2data.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1500274 Title: device descriptor read/64, error -71 Status in linux package in Ubuntu: Triaged Bug description: When plugging in an LG Enact cell phone in via USB, and setting it to MTP, I'm expecting it to connect. Instead, I get errors in kern.log: Sep 27 16:32:42 monikerpc kernel: [95740.772217] usb 1-1: new low-speed USB device number 3 using xhci_hcd Sep 27 16:32:43 monikerpc kernel: [95741.936187] usb 1-1: new low-speed USB device number 5 using xhci_hcd Sep 27 16:32:43 monikerpc kernel: [95742.056435] usb 1-1: device descriptor read/64, error -71 Sep 27 16:32:43 monikerpc kernel: [95742.280452] usb 1-1: device descriptor read/64, error -71 Sep 27 16:32:43 monikerpc kernel: [95742.496374] usb 1-1: new low-speed USB device number 6 using xhci_hcd Sep 27 16:32:44 monikerpc kernel: [95742.616454] usb 1-1: device descriptor read/64, error -71 Sep 27 16:32:44 monikerpc kernel: [95742.840491] usb 1-1: device descriptor read/64, error -71 Sep 27 16:32:44 monikerpc kernel: [95743.056425] usb 1-1: new low-speed USB device number 7 using xhci_hcd Sep 27 16:32:44 monikerpc kernel: [95743.057137] usb 1-1: Device not responding to setup address. Sep 27 16:32:44 monikerpc kernel: [95743.261282] usb 1-1: Device not responding to setup address. Sep 27 16:32:44 monikerpc kernel: [95743.464381] usb 1-1: device not accepting address 7, error -71 Sep 27 16:32:45 monikerpc kernel: [95743.576465] usb 1-1: new low-speed USB device number 8 using xhci_hcd Sep 27 16:32:45 monikerpc kernel: [95743.577177] usb 1-1: Device not responding to setup address. Sep 27 16:32:45 monikerpc kernel: [95743.781228] usb 1-1: Device not responding to setup address. Sep 27 16:32:45 monikerpc kernel: [95743.984428] usb 1-1: device not accepting address 8, error -71 Sep 27 16:32:45 monikerpc kernel: [95743.984532] usb usb1-port1: unable to enumerate USB device Sep 27 16:32:58 monikerpc kernel: [95757.081642] usb 1-1: new low-speed USB device number 9 using xhci_hcd Sep 27 16:32:58 monikerpc kernel: [95757.201670] usb 1-1: device descriptor read/64, error -71 Sep 27 16:32:58 monikerpc kernel: [95757.425823] usb 1-1: device descriptor read/64, error -71 Sep 27 16:32:59 monikerpc kernel: [95757.641741] usb 1-1: new low-speed USB device number 10 using xhci_hcd Sep 27 16:32:59 monikerpc kernel: [95757.761851] usb 1-1: device descriptor read/64, error -71 Sep 27 16:32:59 monikerpc kernel: [95757.985773] usb 1-1: device descriptor read/64, error -71 Sep 27 16:32:59 monikerpc kernel: [95758.201734] usb 1-1: new low-speed USB device number 11 using xhci_hcd Sep 27 16:32:59 monikerpc kernel: [95758.202513] usb 1-1: Device not responding to setup address. Sep 27 16:32:59 monikerpc kernel: [95758.406515] usb 1-1: Device not responding to setup address. Sep 27 16:33:00 monikerpc kernel: [95758.609820] usb 1-1: device not accepting address 11, error -71 Sep 27 16:33:00 monikerpc kernel: [95758.721829] usb 1-1: new low-speed USB device number 12 using xhci_hcd Sep 27 16:33:00 monikerpc kernel: [95758.722572] usb 1-1: Device not responding to setup address. Sep 27 16:33:00 monikerpc kernel: [95758.926585] usb 1-1: Device not responding to setup address. Sep 27 16:33:00 monikerpc kernel: [95759.129866] usb 1-1: device not accepting address 12, error -71 Sep 27 16:33:00 monikerpc kernel: [95759.129965] usb usb1-port1: unable to enumerate USB device Sep 27 16:41:10 monikerpc kernel: [96248.613911] usb 1-1: new low-speed USB device number 14 using xhci_hcd Sep 27 16:41:24 monikerpc kernel: [96262.979197] usb 1-1: new low-speed USB device number 27 using xhci_hcd Sep 27 16:41:25 monikerpc kernel: [96263.743283] usb 1-1: new low-speed USB device number 29 using xhci_hcd Sep 27 16:42:05 monikerpc kernel: [96304.275050] usb 1-1: new low-speed USB device number 35 using xhci_hcd Sep 27 16:42:05 monikerpc kernel: [96304.395141] usb 1-1: device descriptor read/64, error -71 Sep 27 16:42:06 monikerpc kernel: [96305.195138] usb 1-1: new low-speed USB device number 37 using xhci_hcd Sep 27 16:42:06 monikerpc kernel: [96305.315111] usb 1-1: device descriptor read/64, error -71 Sep 27 16:42:06 monikerpc kernel: [96305.539248] usb 1-1: device descriptor read/64, error -71 Sep 27 16:42:07 monikerpc kernel: [96305.755170] usb 1-1: new low-speed USB device number 38 using xhci_hcd Sep 27 16:42:07 monikerpc kernel: [96305.875269] usb 1-1: device descriptor read/64, error -71 Sep 27 16:42:07 monikerpc kernel: [96306.099303] usb 1-1: device descriptor read/64, error -71 Sep 27 16:42:07 monikerpc ker
[Kernel-packages] [Bug 1500274] Re: device descriptor read/64, error -71
While booted into mainline kernel 4.3-rc3: sudo cat /sys/kernel/debug/usb/usbmon/6u >bus2data.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1500274 Title: device descriptor read/64, error -71 Status in linux package in Ubuntu: Triaged Bug description: When plugging in an LG Enact cell phone in via USB, and setting it to MTP, I'm expecting it to connect. Instead, I get errors in kern.log: Sep 27 16:32:42 monikerpc kernel: [95740.772217] usb 1-1: new low-speed USB device number 3 using xhci_hcd Sep 27 16:32:43 monikerpc kernel: [95741.936187] usb 1-1: new low-speed USB device number 5 using xhci_hcd Sep 27 16:32:43 monikerpc kernel: [95742.056435] usb 1-1: device descriptor read/64, error -71 Sep 27 16:32:43 monikerpc kernel: [95742.280452] usb 1-1: device descriptor read/64, error -71 Sep 27 16:32:43 monikerpc kernel: [95742.496374] usb 1-1: new low-speed USB device number 6 using xhci_hcd Sep 27 16:32:44 monikerpc kernel: [95742.616454] usb 1-1: device descriptor read/64, error -71 Sep 27 16:32:44 monikerpc kernel: [95742.840491] usb 1-1: device descriptor read/64, error -71 Sep 27 16:32:44 monikerpc kernel: [95743.056425] usb 1-1: new low-speed USB device number 7 using xhci_hcd Sep 27 16:32:44 monikerpc kernel: [95743.057137] usb 1-1: Device not responding to setup address. Sep 27 16:32:44 monikerpc kernel: [95743.261282] usb 1-1: Device not responding to setup address. Sep 27 16:32:44 monikerpc kernel: [95743.464381] usb 1-1: device not accepting address 7, error -71 Sep 27 16:32:45 monikerpc kernel: [95743.576465] usb 1-1: new low-speed USB device number 8 using xhci_hcd Sep 27 16:32:45 monikerpc kernel: [95743.577177] usb 1-1: Device not responding to setup address. Sep 27 16:32:45 monikerpc kernel: [95743.781228] usb 1-1: Device not responding to setup address. Sep 27 16:32:45 monikerpc kernel: [95743.984428] usb 1-1: device not accepting address 8, error -71 Sep 27 16:32:45 monikerpc kernel: [95743.984532] usb usb1-port1: unable to enumerate USB device Sep 27 16:32:58 monikerpc kernel: [95757.081642] usb 1-1: new low-speed USB device number 9 using xhci_hcd Sep 27 16:32:58 monikerpc kernel: [95757.201670] usb 1-1: device descriptor read/64, error -71 Sep 27 16:32:58 monikerpc kernel: [95757.425823] usb 1-1: device descriptor read/64, error -71 Sep 27 16:32:59 monikerpc kernel: [95757.641741] usb 1-1: new low-speed USB device number 10 using xhci_hcd Sep 27 16:32:59 monikerpc kernel: [95757.761851] usb 1-1: device descriptor read/64, error -71 Sep 27 16:32:59 monikerpc kernel: [95757.985773] usb 1-1: device descriptor read/64, error -71 Sep 27 16:32:59 monikerpc kernel: [95758.201734] usb 1-1: new low-speed USB device number 11 using xhci_hcd Sep 27 16:32:59 monikerpc kernel: [95758.202513] usb 1-1: Device not responding to setup address. Sep 27 16:32:59 monikerpc kernel: [95758.406515] usb 1-1: Device not responding to setup address. Sep 27 16:33:00 monikerpc kernel: [95758.609820] usb 1-1: device not accepting address 11, error -71 Sep 27 16:33:00 monikerpc kernel: [95758.721829] usb 1-1: new low-speed USB device number 12 using xhci_hcd Sep 27 16:33:00 monikerpc kernel: [95758.722572] usb 1-1: Device not responding to setup address. Sep 27 16:33:00 monikerpc kernel: [95758.926585] usb 1-1: Device not responding to setup address. Sep 27 16:33:00 monikerpc kernel: [95759.129866] usb 1-1: device not accepting address 12, error -71 Sep 27 16:33:00 monikerpc kernel: [95759.129965] usb usb1-port1: unable to enumerate USB device Sep 27 16:41:10 monikerpc kernel: [96248.613911] usb 1-1: new low-speed USB device number 14 using xhci_hcd Sep 27 16:41:24 monikerpc kernel: [96262.979197] usb 1-1: new low-speed USB device number 27 using xhci_hcd Sep 27 16:41:25 monikerpc kernel: [96263.743283] usb 1-1: new low-speed USB device number 29 using xhci_hcd Sep 27 16:42:05 monikerpc kernel: [96304.275050] usb 1-1: new low-speed USB device number 35 using xhci_hcd Sep 27 16:42:05 monikerpc kernel: [96304.395141] usb 1-1: device descriptor read/64, error -71 Sep 27 16:42:06 monikerpc kernel: [96305.195138] usb 1-1: new low-speed USB device number 37 using xhci_hcd Sep 27 16:42:06 monikerpc kernel: [96305.315111] usb 1-1: device descriptor read/64, error -71 Sep 27 16:42:06 monikerpc kernel: [96305.539248] usb 1-1: device descriptor read/64, error -71 Sep 27 16:42:07 monikerpc kernel: [96305.755170] usb 1-1: new low-speed USB device number 38 using xhci_hcd Sep 27 16:42:07 monikerpc kernel: [96305.875269] usb 1-1: device descriptor read/64, error -71 Sep 27 16:42:07 monikerpc kernel: [96306.099303] usb 1-1: device descriptor read/64, error -71 Sep 27 16:42:07 monikerpc kernel: [96306.315236] usb 1-1: new low-speed USB device number 39 using xhci_hcd Sep 27 16:42:08 m
[Kernel-packages] [Bug 1500274] Re: device descriptor read/64, error -71
** Tags added: kernel-bug-exists-upstream kernel-bug-exists- upstream-4.3-rc3 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1500274 Title: device descriptor read/64, error -71 Status in linux package in Ubuntu: Triaged Bug description: When plugging in an LG Enact cell phone in via USB, and setting it to MTP, I'm expecting it to connect. Instead, I get errors in kern.log: Sep 27 16:32:42 monikerpc kernel: [95740.772217] usb 1-1: new low-speed USB device number 3 using xhci_hcd Sep 27 16:32:43 monikerpc kernel: [95741.936187] usb 1-1: new low-speed USB device number 5 using xhci_hcd Sep 27 16:32:43 monikerpc kernel: [95742.056435] usb 1-1: device descriptor read/64, error -71 Sep 27 16:32:43 monikerpc kernel: [95742.280452] usb 1-1: device descriptor read/64, error -71 Sep 27 16:32:43 monikerpc kernel: [95742.496374] usb 1-1: new low-speed USB device number 6 using xhci_hcd Sep 27 16:32:44 monikerpc kernel: [95742.616454] usb 1-1: device descriptor read/64, error -71 Sep 27 16:32:44 monikerpc kernel: [95742.840491] usb 1-1: device descriptor read/64, error -71 Sep 27 16:32:44 monikerpc kernel: [95743.056425] usb 1-1: new low-speed USB device number 7 using xhci_hcd Sep 27 16:32:44 monikerpc kernel: [95743.057137] usb 1-1: Device not responding to setup address. Sep 27 16:32:44 monikerpc kernel: [95743.261282] usb 1-1: Device not responding to setup address. Sep 27 16:32:44 monikerpc kernel: [95743.464381] usb 1-1: device not accepting address 7, error -71 Sep 27 16:32:45 monikerpc kernel: [95743.576465] usb 1-1: new low-speed USB device number 8 using xhci_hcd Sep 27 16:32:45 monikerpc kernel: [95743.577177] usb 1-1: Device not responding to setup address. Sep 27 16:32:45 monikerpc kernel: [95743.781228] usb 1-1: Device not responding to setup address. Sep 27 16:32:45 monikerpc kernel: [95743.984428] usb 1-1: device not accepting address 8, error -71 Sep 27 16:32:45 monikerpc kernel: [95743.984532] usb usb1-port1: unable to enumerate USB device Sep 27 16:32:58 monikerpc kernel: [95757.081642] usb 1-1: new low-speed USB device number 9 using xhci_hcd Sep 27 16:32:58 monikerpc kernel: [95757.201670] usb 1-1: device descriptor read/64, error -71 Sep 27 16:32:58 monikerpc kernel: [95757.425823] usb 1-1: device descriptor read/64, error -71 Sep 27 16:32:59 monikerpc kernel: [95757.641741] usb 1-1: new low-speed USB device number 10 using xhci_hcd Sep 27 16:32:59 monikerpc kernel: [95757.761851] usb 1-1: device descriptor read/64, error -71 Sep 27 16:32:59 monikerpc kernel: [95757.985773] usb 1-1: device descriptor read/64, error -71 Sep 27 16:32:59 monikerpc kernel: [95758.201734] usb 1-1: new low-speed USB device number 11 using xhci_hcd Sep 27 16:32:59 monikerpc kernel: [95758.202513] usb 1-1: Device not responding to setup address. Sep 27 16:32:59 monikerpc kernel: [95758.406515] usb 1-1: Device not responding to setup address. Sep 27 16:33:00 monikerpc kernel: [95758.609820] usb 1-1: device not accepting address 11, error -71 Sep 27 16:33:00 monikerpc kernel: [95758.721829] usb 1-1: new low-speed USB device number 12 using xhci_hcd Sep 27 16:33:00 monikerpc kernel: [95758.722572] usb 1-1: Device not responding to setup address. Sep 27 16:33:00 monikerpc kernel: [95758.926585] usb 1-1: Device not responding to setup address. Sep 27 16:33:00 monikerpc kernel: [95759.129866] usb 1-1: device not accepting address 12, error -71 Sep 27 16:33:00 monikerpc kernel: [95759.129965] usb usb1-port1: unable to enumerate USB device Sep 27 16:41:10 monikerpc kernel: [96248.613911] usb 1-1: new low-speed USB device number 14 using xhci_hcd Sep 27 16:41:24 monikerpc kernel: [96262.979197] usb 1-1: new low-speed USB device number 27 using xhci_hcd Sep 27 16:41:25 monikerpc kernel: [96263.743283] usb 1-1: new low-speed USB device number 29 using xhci_hcd Sep 27 16:42:05 monikerpc kernel: [96304.275050] usb 1-1: new low-speed USB device number 35 using xhci_hcd Sep 27 16:42:05 monikerpc kernel: [96304.395141] usb 1-1: device descriptor read/64, error -71 Sep 27 16:42:06 monikerpc kernel: [96305.195138] usb 1-1: new low-speed USB device number 37 using xhci_hcd Sep 27 16:42:06 monikerpc kernel: [96305.315111] usb 1-1: device descriptor read/64, error -71 Sep 27 16:42:06 monikerpc kernel: [96305.539248] usb 1-1: device descriptor read/64, error -71 Sep 27 16:42:07 monikerpc kernel: [96305.755170] usb 1-1: new low-speed USB device number 38 using xhci_hcd Sep 27 16:42:07 monikerpc kernel: [96305.875269] usb 1-1: device descriptor read/64, error -71 Sep 27 16:42:07 monikerpc kernel: [96306.099303] usb 1-1: device descriptor read/64, error -71 Sep 27 16:42:07 monikerpc kernel: [96306.315236] usb 1-1: new low-speed USB device number 39 using xhci_hcd Sep 27 16:42:08 monikerpc kernel: [96
[Kernel-packages] [Bug 1500274] [NEW] device descriptor read/64, error -71
Public bug reported: When plugging in an LG Enact cell phone in via USB, and setting it to MTP, I'm expecting it to connect. Instead, I get errors in kern.log: Sep 27 16:32:42 monikerpc kernel: [95740.772217] usb 1-1: new low-speed USB device number 3 using xhci_hcd Sep 27 16:32:43 monikerpc kernel: [95741.936187] usb 1-1: new low-speed USB device number 5 using xhci_hcd Sep 27 16:32:43 monikerpc kernel: [95742.056435] usb 1-1: device descriptor read/64, error -71 Sep 27 16:32:43 monikerpc kernel: [95742.280452] usb 1-1: device descriptor read/64, error -71 Sep 27 16:32:43 monikerpc kernel: [95742.496374] usb 1-1: new low-speed USB device number 6 using xhci_hcd Sep 27 16:32:44 monikerpc kernel: [95742.616454] usb 1-1: device descriptor read/64, error -71 Sep 27 16:32:44 monikerpc kernel: [95742.840491] usb 1-1: device descriptor read/64, error -71 Sep 27 16:32:44 monikerpc kernel: [95743.056425] usb 1-1: new low-speed USB device number 7 using xhci_hcd Sep 27 16:32:44 monikerpc kernel: [95743.057137] usb 1-1: Device not responding to setup address. Sep 27 16:32:44 monikerpc kernel: [95743.261282] usb 1-1: Device not responding to setup address. Sep 27 16:32:44 monikerpc kernel: [95743.464381] usb 1-1: device not accepting address 7, error -71 Sep 27 16:32:45 monikerpc kernel: [95743.576465] usb 1-1: new low-speed USB device number 8 using xhci_hcd Sep 27 16:32:45 monikerpc kernel: [95743.577177] usb 1-1: Device not responding to setup address. Sep 27 16:32:45 monikerpc kernel: [95743.781228] usb 1-1: Device not responding to setup address. Sep 27 16:32:45 monikerpc kernel: [95743.984428] usb 1-1: device not accepting address 8, error -71 Sep 27 16:32:45 monikerpc kernel: [95743.984532] usb usb1-port1: unable to enumerate USB device Sep 27 16:32:58 monikerpc kernel: [95757.081642] usb 1-1: new low-speed USB device number 9 using xhci_hcd Sep 27 16:32:58 monikerpc kernel: [95757.201670] usb 1-1: device descriptor read/64, error -71 Sep 27 16:32:58 monikerpc kernel: [95757.425823] usb 1-1: device descriptor read/64, error -71 Sep 27 16:32:59 monikerpc kernel: [95757.641741] usb 1-1: new low-speed USB device number 10 using xhci_hcd Sep 27 16:32:59 monikerpc kernel: [95757.761851] usb 1-1: device descriptor read/64, error -71 Sep 27 16:32:59 monikerpc kernel: [95757.985773] usb 1-1: device descriptor read/64, error -71 Sep 27 16:32:59 monikerpc kernel: [95758.201734] usb 1-1: new low-speed USB device number 11 using xhci_hcd Sep 27 16:32:59 monikerpc kernel: [95758.202513] usb 1-1: Device not responding to setup address. Sep 27 16:32:59 monikerpc kernel: [95758.406515] usb 1-1: Device not responding to setup address. Sep 27 16:33:00 monikerpc kernel: [95758.609820] usb 1-1: device not accepting address 11, error -71 Sep 27 16:33:00 monikerpc kernel: [95758.721829] usb 1-1: new low-speed USB device number 12 using xhci_hcd Sep 27 16:33:00 monikerpc kernel: [95758.722572] usb 1-1: Device not responding to setup address. Sep 27 16:33:00 monikerpc kernel: [95758.926585] usb 1-1: Device not responding to setup address. Sep 27 16:33:00 monikerpc kernel: [95759.129866] usb 1-1: device not accepting address 12, error -71 Sep 27 16:33:00 monikerpc kernel: [95759.129965] usb usb1-port1: unable to enumerate USB device Sep 27 16:41:10 monikerpc kernel: [96248.613911] usb 1-1: new low-speed USB device number 14 using xhci_hcd Sep 27 16:41:24 monikerpc kernel: [96262.979197] usb 1-1: new low-speed USB device number 27 using xhci_hcd Sep 27 16:41:25 monikerpc kernel: [96263.743283] usb 1-1: new low-speed USB device number 29 using xhci_hcd Sep 27 16:42:05 monikerpc kernel: [96304.275050] usb 1-1: new low-speed USB device number 35 using xhci_hcd Sep 27 16:42:05 monikerpc kernel: [96304.395141] usb 1-1: device descriptor read/64, error -71 Sep 27 16:42:06 monikerpc kernel: [96305.195138] usb 1-1: new low-speed USB device number 37 using xhci_hcd Sep 27 16:42:06 monikerpc kernel: [96305.315111] usb 1-1: device descriptor read/64, error -71 Sep 27 16:42:06 monikerpc kernel: [96305.539248] usb 1-1: device descriptor read/64, error -71 Sep 27 16:42:07 monikerpc kernel: [96305.755170] usb 1-1: new low-speed USB device number 38 using xhci_hcd Sep 27 16:42:07 monikerpc kernel: [96305.875269] usb 1-1: device descriptor read/64, error -71 Sep 27 16:42:07 monikerpc kernel: [96306.099303] usb 1-1: device descriptor read/64, error -71 Sep 27 16:42:07 monikerpc kernel: [96306.315236] usb 1-1: new low-speed USB device number 39 using xhci_hcd Sep 27 16:42:08 monikerpc kernel: [96307.006425] usb 1-1: Device not responding to setup address. Sep 27 16:42:09 monikerpc kernel: [96307.663353] usb 1-1: Device not responding to setup address. Sep 27 16:42:09 monikerpc kernel: [96307.867299] usb 1-1: device not accepting address 39, error -71 I tried turning changing USB auto suspend from: cat /sys/module/usbcore/parameters/autosuspend 2 to: sudo su echo -1 > /sys/module/usbcore/parameters/autosus
[Kernel-packages] [Bug 919115] Re: CVE-2012-0056
** Changed in: linux (Ubuntu Wily) Status: Fix Released => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/919115 Title: CVE-2012-0056 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: New Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: Invalid Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: Invalid Status in linux-lts-backport-maverick package in Ubuntu: Invalid Status in linux-lts-backport-natty package in Ubuntu: Invalid Status in linux-lts-backport-oneiric package in Ubuntu: Invalid Status in linux-lts-quantal package in Ubuntu: New Status in linux-lts-raring package in Ubuntu: New Status in linux-lts-saucy package in Ubuntu: New Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: Invalid Status in linux-manta package in Ubuntu: Invalid Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux-lts-backport-maverick source package in Lucid: Invalid Status in linux-lts-backport-natty source package in Lucid: Invalid Status in linux-lts-backport-oneiric source package in Lucid: Fix Released Status in linux-lts-backport-maverick source package in Maverick: Invalid Status in linux-lts-backport-natty source package in Maverick: Invalid Status in linux-lts-backport-oneiric source package in Maverick: Invalid Status in linux-lts-backport-maverick source package in Natty: Invalid Status in linux-lts-backport-natty source package in Natty: Invalid Status in linux-lts-backport-oneiric source package in Natty: Invalid Status in linux-lts-backport-maverick source package in Oneiric: Invalid Status in linux-lts-backport-natty source package in Oneiric: Invalid Status in linux-lts-backport-oneiric source package in Oneiric: Invalid Status in linux source package in Precise: Fix Released Status in linux-armadaxp source package in Precise: New Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: Invalid Status in linux-lts-backport-natty source package in Precise: Invalid Status in linux-lts-backport-oneiric source package in Precise: Invalid Status in linux-lts-quantal source package in Precise: New Status in linux-lts-raring source package in Precise: New Status in linux-lts-saucy source package in Precise: New Status in linux-lts-trusty source package in Precise: Invalid Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Fix Released Status in linux source package in Trusty: Invalid Status in linux-armadaxp source package in Trusty: New Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: New Status in linux-lts-backport-natty source package in Trusty: New Status in linux-lts-backport-oneiric source package in Trusty: New Status in linux-lts-quantal source package in Trusty: New Status in linux-lts-raring source package in Trusty: New Status in linux-lts-saucy source package in Trusty: New Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Invalid Status in linux-lts-vivid source package in Trusty: Fix Committed Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-mvl-dove source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Utopic: Invalid Status in linux-armadaxp source package in Utopic: New Status in linux-ec2 source package in Utopic: Invalid Status in linux-flo source package in Utopic: Invalid Status in linux-fsl-imx51 source package in Utopic: Invalid Status in linux-goldfish source package in Utopic: Invalid Status in linux-lts-backport-maverick source package in Utopic: New Status in linux-lts-backport-natty source package i
[Kernel-packages] [Bug 917842] Re: CVE-2012-0045
affects ubuntu/precise/linux-lts-raring status invalid affects ubuntu/trusty/linux-lts-raring status invalid affects ubuntu/vivid/linux-lts-raring status invalid affects ubuntu/wily/linux-lts-raring status invalid affects ubuntu/precise/linux-lts-saucy status invalid affects ubuntu/trusty/linux-lts-saucy status invalid affects ubuntu/vivid/linux-lts-saucy status invalid affects ubuntu/wily/linux-lts-saucy status invalid ** No longer affects: linux-lts-quantal (Ubuntu Utopic) ** No longer affects: linux-lts-raring (Ubuntu Utopic) ** No longer affects: linux-lts-saucy (Ubuntu Utopic) ** No longer affects: linux-ti-omap4 (Ubuntu Utopic) ** No longer affects: linux-lts-trusty (Ubuntu Utopic) ** No longer affects: linux-lts-utopic (Ubuntu Utopic) ** No longer affects: linux-lts-vivid (Ubuntu Utopic) ** No longer affects: linux-mako (Ubuntu Utopic) ** No longer affects: linux-manta (Ubuntu Utopic) ** No longer affects: linux-mvl-dove (Ubuntu Utopic) ** Changed in: linux-lts-raring (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-lts-raring (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-lts-raring (Ubuntu Vivid) Status: New => Invalid ** Changed in: linux-lts-raring (Ubuntu Wily) Status: New => Invalid ** Changed in: linux-lts-saucy (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-lts-saucy (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-lts-saucy (Ubuntu Vivid) Status: New => Invalid ** Changed in: linux-lts-saucy (Ubuntu Wily) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/917842 Title: CVE-2012-0045 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: Invalid Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: Invalid Status in linux-lts-backport-maverick package in Ubuntu: Invalid Status in linux-lts-backport-natty package in Ubuntu: Invalid Status in linux-lts-backport-oneiric package in Ubuntu: Invalid Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: Invalid Status in linux-manta package in Ubuntu: Invalid Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux-lts-backport-maverick source package in Lucid: Fix Released Status in linux-lts-backport-natty source package in Lucid: Fix Released Status in linux-lts-backport-oneiric source package in Lucid: Fix Released Status in linux-lts-backport-maverick source package in Maverick: Invalid Status in linux-lts-backport-natty source package in Maverick: Invalid Status in linux-lts-backport-oneiric source package in Maverick: Invalid Status in linux-lts-backport-maverick source package in Natty: Invalid Status in linux-lts-backport-natty source package in Natty: Invalid Status in linux-lts-backport-oneiric source package in Natty: Invalid Status in linux-lts-backport-maverick source package in Oneiric: Invalid Status in linux-lts-backport-natty source package in Oneiric: Invalid Status in linux-lts-backport-oneiric source package in Oneiric: Invalid Status in linux source package in Precise: Invalid Status in linux-armadaxp source package in Precise: Invalid Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: Invalid Status in linux-lts-backport-natty source package in Precise: Invalid Status in linux-lts-backport-oneiric source package in Precise: Invalid Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Invalid Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Invalid Status in linux-lts-backport-maverick source packa
[Kernel-packages] [Bug 917842]
no longer affects ubuntu/utopic/linux-lts-quantal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/917842 Title: CVE-2012-0045 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: Invalid Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: Invalid Status in linux-lts-backport-maverick package in Ubuntu: Invalid Status in linux-lts-backport-natty package in Ubuntu: Invalid Status in linux-lts-backport-oneiric package in Ubuntu: Invalid Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: New Status in linux-lts-saucy package in Ubuntu: New Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: Invalid Status in linux-manta package in Ubuntu: Invalid Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux-lts-backport-maverick source package in Lucid: Fix Released Status in linux-lts-backport-natty source package in Lucid: Fix Released Status in linux-lts-backport-oneiric source package in Lucid: Fix Released Status in linux-lts-backport-maverick source package in Maverick: Invalid Status in linux-lts-backport-natty source package in Maverick: Invalid Status in linux-lts-backport-oneiric source package in Maverick: Invalid Status in linux-lts-backport-maverick source package in Natty: Invalid Status in linux-lts-backport-natty source package in Natty: Invalid Status in linux-lts-backport-oneiric source package in Natty: Invalid Status in linux-lts-backport-maverick source package in Oneiric: Invalid Status in linux-lts-backport-natty source package in Oneiric: Invalid Status in linux-lts-backport-oneiric source package in Oneiric: Invalid Status in linux source package in Precise: Invalid Status in linux-armadaxp source package in Precise: Invalid Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: Invalid Status in linux-lts-backport-natty source package in Precise: Invalid Status in linux-lts-backport-oneiric source package in Precise: Invalid Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: New Status in linux-lts-saucy source package in Precise: New Status in linux-lts-trusty source package in Precise: Invalid Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Quantal: Invalid Status in linux-lts-backport-natty source package in Quantal: Invalid Status in linux-lts-backport-oneiric source package in Quantal: Invalid Status in linux source package in Trusty: Invalid Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: Invalid Status in linux-lts-backport-natty source package in Trusty: Invalid Status in linux-lts-backport-oneiric source package in Trusty: Invalid Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: New Status in linux-lts-saucy source package in Trusty: New Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Invalid Status in linux-lts-vivid source package in Trusty: Invalid Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-mvl-dove source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux-lts-quantal source package in Utopic: New Status in linux-lts-raring source package in Utopic: New Status in linux-lts-saucy source package in Utopic: New Status in linux-lts-trusty source package in Utopic: Invali
[Kernel-packages] [Bug 1499665] Re: [SynPS/2 Synaptics TouchPad] TouchPad not working after installtion
** Changed in: xorg (Ubuntu) Importance: Undecided => Low ** Changed in: xorg (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1499665 Title: [SynPS/2 Synaptics TouchPad] TouchPad not working after installtion Status in linux package in Ubuntu: Incomplete Status in xorg package in Ubuntu: Incomplete Bug description: During installation touchpad works perfectly, but after trusty(3.19) installed, and restarted, touchpad unable to use anymore. Steps to reproduce: 1. Boot system with 14.04.3 live usb 2. Install the system Expected result: Touchpad works normally as in live environment Actual results: Touchpad no response Additional Info.: $ xinput list ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ Logitech USB-PS/2 Optical Mouse id=9[slave pointer (2)] ⎜ ↳ ELAN Touchscreenid=11 [slave pointer (2)] ⎜ ↳ DLLC6D7:00 06CB:796Aid=12 [slave pointer (2)] ⎜ ↳ SynPS/2 Synaptics TouchPad id=14 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Sleep Buttonid=8[slave keyboard (3)] ↳ Integrated_Webcam_HDid=10 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=13 [slave keyboard (3)] ↳ Dell WMI hotkeysid=15 [slave keyboard (3)] ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.19.0-28.30~14.04.1-generic 3.19.8-ckt5 Uname: Linux 3.19.0-28-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Sep 25 17:48:59 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation ValleyView Gen7 [8086:0f31] (rev 0e) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:06d7] InstallationDate: Installed on 2015-09-22 (2 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: Dell Inc. Inspiron 5551 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-28-generic.efi.signed root=UUID=3bf855c2-39fe-4325-a1cc-960930d96a9e ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/28/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: X16 dmi.board.asset.tag: AFTPASS dmi.board.name: Type2 - Board Product Name1 dmi.board.vendor: Dell Inc. dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: AFTPASS dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: X16 dmi.modalias: dmi:bvnDellInc.:bvrX16:bd01/28/2015:svnDellInc.:pnInspiron5551:pvrX16:rvnDellInc.:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnDellInc.:ct8:cvrX16: dmi.product.name: Inspiron 5551 dmi.product.version: X16 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Fri Sep 25 17:06:43 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5100 vendor AUO xserver.version: 2:1.17.1-0ubuntu3.1~trusty1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1499665/+subscriptions -- Mailing list: htt
[Kernel-packages] [Bug 1490143] Re: When resuming after suspension desktop is freezed
Carla Sella, the issue you are reporting is an upstream one. Could you please report this problem through the appropriate channel by following the instructions verbatim at http://nouveau.freedesktop.org/wiki/Bugs/ ? Please provide a direct URL to your bug report once you have made it so that it may be tracked. Thank you for your understanding. ** Tags removed: kernel-bug-exists-upstream-4.3-rc2 ** Tags added: kernel-bug-exists-upstream kernel-bug-exists-upstream-4.3-rc3 ** Changed in: linux (Ubuntu) Status: Incomplete => Triaged ** Summary changed: - When resuming after suspension desktop is freezed + 10de:040a When resuming after suspension desktop is freezed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1490143 Title: 10de:040a When resuming after suspension desktop is freezed Status in linux package in Ubuntu: Triaged Bug description: I suspended my PC for like about 1,5 - 2 hours and when I resumed the desktop had a black background, you could see the launcher bat you were unable to do anything it was freezed. This is my hardware: https://gist.github.com/anonymous/3203c7c5a43a509c0f22. I am attaching the screen-shots of my desktop after resuming, also in terminal (CTRL+ALT+F1) it looked rather garbled. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3 Uname: Linux 4.1.0-3-generic x86_64 ApportVersion: 2.18-0ubuntu7 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Sat Aug 29 13:57:20 2015 DistUpgraded: Fresh install DistroCodename: wily DistroVariant: ubuntu DkmsStatus: virtualbox, 5.0.2, 4.1.0-3-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation G84GL [Quadro FX 370] [10de:040a] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation Device [10de:0491] InstallationDate: Installed on 2015-08-16 (12 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150816) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.1.0-3-generic root=UUID=4b5d483e-4c0c-4013-b27c-0684b9343728 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/13/2007 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0803 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M2N dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0803:bd09/13/2007:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2N:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.12.1+15.10.20150805-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.6.3-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.6.3-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0+git20150819-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3 xserver.bootTime: Sat Aug 29 11:08:42 2015 xserver.configfile: default xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) NOUVEAU(0): [COPY] failed to allocate class. xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.17.2-1ubuntu3 xserver.video_driver: nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1490143/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 917842]
affects ubuntu/precise/linux-lts-quantal status invalid affects ubuntu/trusty/linux-lts-quantal status invalid affects ubuntu/vivid/linux-lts-quantal status invalid affects ubuntu/wily/linux-lts-quantal status invalid ** Changed in: linux-lts-quantal (Ubuntu Precise) Status: New => Invalid ** Changed in: linux-lts-quantal (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-lts-quantal (Ubuntu Vivid) Status: New => Invalid ** Changed in: linux-lts-quantal (Ubuntu Wily) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/917842 Title: CVE-2012-0045 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: Invalid Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: Invalid Status in linux-lts-backport-maverick package in Ubuntu: Invalid Status in linux-lts-backport-natty package in Ubuntu: Invalid Status in linux-lts-backport-oneiric package in Ubuntu: Invalid Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: New Status in linux-lts-saucy package in Ubuntu: New Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: Invalid Status in linux-manta package in Ubuntu: Invalid Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux-lts-backport-maverick source package in Lucid: Fix Released Status in linux-lts-backport-natty source package in Lucid: Fix Released Status in linux-lts-backport-oneiric source package in Lucid: Fix Released Status in linux-lts-backport-maverick source package in Maverick: Invalid Status in linux-lts-backport-natty source package in Maverick: Invalid Status in linux-lts-backport-oneiric source package in Maverick: Invalid Status in linux-lts-backport-maverick source package in Natty: Invalid Status in linux-lts-backport-natty source package in Natty: Invalid Status in linux-lts-backport-oneiric source package in Natty: Invalid Status in linux-lts-backport-maverick source package in Oneiric: Invalid Status in linux-lts-backport-natty source package in Oneiric: Invalid Status in linux-lts-backport-oneiric source package in Oneiric: Invalid Status in linux source package in Precise: Invalid Status in linux-armadaxp source package in Precise: Invalid Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: Invalid Status in linux-lts-backport-natty source package in Precise: Invalid Status in linux-lts-backport-oneiric source package in Precise: Invalid Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: New Status in linux-lts-saucy source package in Precise: New Status in linux-lts-trusty source package in Precise: Invalid Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Quantal: Invalid Status in linux-lts-backport-natty source package in Quantal: Invalid Status in linux-lts-backport-oneiric source package in Quantal: Invalid Status in linux source package in Trusty: Invalid Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: Invalid Status in linux-lts-backport-natty source package in Trusty: Invalid Status in linux-lts-backport-oneiric source package in Trusty: Invalid Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: New Status in linux-lts-saucy source package in Trusty: New Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Invalid Status in linux-lts-vivid source package
[Kernel-packages] [Bug 1498065] Re: linux: 3.19.0-30.33 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-security Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Confirmed ** Description changed: This bug is for tracking the 3.19.0-30.33 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Monday, 21. September 2015 15:30 UTC kernel-stable-Prepare-package-end:Tuesday, 22. September 2015 06:02 UTC kernel-stable-Promote-to-proposed-start:Tuesday, 22. September 2015 06:02 UTC kernel-stable-Promote-to-proposed-end:Tuesday, 22. September 2015 21:15 UTC kernel-stable-Verification-testing-start:Tuesday, 22. September 2015 23:01 UTC kernel-stable-Certification-testing-start:Tuesday, 22. September 2015 23:01 UTC kernel-stable-Security-signoff-start:Tuesday, 22. September 2015 23:01 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Tuesday, 22. September 2015 23:01 UTC kernel-stable-Security-signoff-end:Wednesday, 23. September 2015 16:00 UTC kernel-stable-Regression-testing-end:Thursday, 24. September 2015 16:00 UTC - kernel-stable-phase:Testing - kernel-stable-phase-changed:Friday, 25. September 2015 16:07 UTC kernel-stable-Verification-testing-end:Friday, 25. September 2015 16:07 UTC kernel-stable-Certification-testing-end:Saturday, 26. September 2015 18:00 UTC + kernel-stable-phase:CopyToUpdates + kernel-stable-phase-changed:Sunday, 27. September 2015 21:00 UTC + kernel-stable-Promote-to-updates-start:Sunday, 27. September 2015 21:00 UTC -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1498065 Title: linux: 3.19.0-30.33 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Confirmed Status in Kernel SRU Workflow promote-to-updates series: Confirmed Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Vivid: Confirmed Bug description: This bug is for tracking the 3.19.0-30.33 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Monday, 21. September 2015 15:30 UTC kernel-stable-Prepare-package-end:Tuesday, 22. September 2015 06:02 UTC kernel-stable-Promote-to-proposed-start:Tuesday, 22. September 2015 06:02 UTC kernel-stable-Promote-to-proposed-end:Tuesday, 22. September 2015 21:15 UTC kernel-stable-Verification-testing-start:Tuesday, 22. September 2015 23:01 UTC kernel-stable-Certification-testing-start:Tuesday, 22. September 2015 23:01 UTC kernel-stable-Security-signoff-start:Tuesday, 22. September 2015 23:01 UTC proposed-announcement-sent:True kernel-stable-Regression-testing-start:Tuesday, 22. September 2015 23:01 UTC kernel-stable-Security-signoff-end:Wednesday, 23. September 2015 16:00 UTC kernel-stable-Regression-testing-end:Thursday, 24. September 2015 16:00 UTC kernel-stable-Verification-testing-end:Friday, 25. September 2015 16:07 UTC kernel-stable-Certification-testing-end:Saturday, 26. September 2015 18:00 UTC kernel-stable-phase:CopyToUpdates kernel-stable-phase-changed:Sunday, 27. September 2015 21:00 UTC kernel-stable-Promote-to-updates-start:Sunday, 27. September 2015 21:00 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1498065/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1465506] Re: plane A assertion failure (expected on, current off) on Intel NUC 5i5RYH
Alexander List, thank you for reporting this and helping make Ubuntu better. As per https://downloadcenter.intel.com/search?keyword=NUC5i5RY an update to your computer's buggy and outdated BIOS is available (0350). If you update to this following https://help.ubuntu.com/community/BIOSUpdate does it change anything? If it doesn't, could you please both specify what happened, and provide the output of the following terminal command: sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date 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. As well, you don't have to create a new bug report. Once the BIOS is updated, if the problem is still reproducible, and the information above is provided, then please mark this report Status Confirmed. Otherwise, please mark this as Invalid. Thank you for your understanding. ** Tags added: bios-outdated-0350 ** Package changed: xserver-xorg-video-intel (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Importance: High => Low ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1465506 Title: plane A assertion failure (expected on, current off) on Intel NUC 5i5RYH Status in xf86-video-intel: Unknown Status in linux package in Ubuntu: Incomplete Bug description: Getting assertion failures: [ 9925.287975] WARNING: CPU: 3 PID: 7538 at /build/buildd/linux-3.19.0/drivers/gpu/drm/i915/intel_display.c:1256 assert_plane.constprop.87+0x7b/0x90 [i 915]() [ 9925.287976] plane A assertion failure (expected on, current off) Around the same time, WiFi connections drop. I cannot prove the two problems are related, but I don't have WiFi issues on other devices. alex@nuc1-hkg:~$ lsb_release -rd Description: Ubuntu 15.04 Release: 15.04 alex@nuc1-hkg:~$ apt-cache policy xserver-xorg-video-intel xserver-xorg-video-intel: Installed: 2:2.99.917-1~exp1ubuntu2.2 Candidate: 2:2.99.917-1~exp1ubuntu2.2 Version table: *** 2:2.99.917-1~exp1ubuntu2.2 0 500 http://tw.archive.ubuntu.com/ubuntu/ vivid-updates/main amd64 Packages 100 /var/lib/dpkg/status 2:2.99.917-1~exp1ubuntu2build1 0 500 http://tw.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages alex@nuc1-hkg:~$ apt-cache policy linux-image-generic linux-image-generic: Installed: 3.19.0.21.20 Candidate: 3.19.0.21.20 Version table: *** 3.19.0.21.20 0 500 http://tw.archive.ubuntu.com/ubuntu/ vivid-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ vivid-security/main amd64 Packages 100 /var/lib/dpkg/status 3.19.0.15.14 0 500 http://tw.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2.2 ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8 Uname: Linux 3.19.0-21-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Tue Jun 16 14:33:41 2015 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Broadwell-U Integrated Graphics [8086:1626] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Device [8086:2057] InstallationDate: Installed on 2015-06-16 (0 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-21-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-video-intel UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/29/2015 dmi.bios.vendor: Intel Corporation dmi.bios.version: RYBDWi35.86A.0249.2015.0529.1640 dmi.board.name: NUC5i5RYB dmi.board.vendor: Intel Corporation dmi.board.version: H40999-503 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorporation:bvrRYBDWi35.86A.0249.2015.0529.1640:bd05/29/2015:svn:pn:pvr:rvnIntelCorporation:rnNUC5i5RYB:rvrH40999-503:cvn:ct3:cvr: version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17
[Kernel-packages] [Bug 917842] Re: CVE-2012-0045
** Changed in: linux (Ubuntu Precise) Status: Fix Released => Invalid ** Changed in: linux (Ubuntu Wily) Status: Fix Released => Invalid ** No longer affects: linux (Ubuntu Utopic) ** Changed in: linux-armadaxp (Ubuntu Precise) Status: Fix Released => Invalid ** Changed in: linux-lts-vivid (Ubuntu Trusty) Status: Fix Committed => Invalid ** Changed in: linux-ti-omap4 (Ubuntu Precise) Status: Fix Released => Invalid ** No longer affects: linux-armadaxp (Ubuntu Utopic) ** No longer affects: linux-ec2 (Ubuntu Utopic) ** No longer affects: linux-flo (Ubuntu Utopic) ** No longer affects: linux-fsl-imx51 (Ubuntu Utopic) ** No longer affects: linux-goldfish (Ubuntu Utopic) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/917842 Title: CVE-2012-0045 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: Invalid Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: Invalid Status in linux-lts-backport-maverick package in Ubuntu: Invalid Status in linux-lts-backport-natty package in Ubuntu: Invalid Status in linux-lts-backport-oneiric package in Ubuntu: Invalid Status in linux-lts-quantal package in Ubuntu: New Status in linux-lts-raring package in Ubuntu: New Status in linux-lts-saucy package in Ubuntu: New Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: Invalid Status in linux-manta package in Ubuntu: Invalid Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux-lts-backport-maverick source package in Lucid: Fix Released Status in linux-lts-backport-natty source package in Lucid: Fix Released Status in linux-lts-backport-oneiric source package in Lucid: Fix Released Status in linux-lts-backport-maverick source package in Maverick: Invalid Status in linux-lts-backport-natty source package in Maverick: Invalid Status in linux-lts-backport-oneiric source package in Maverick: Invalid Status in linux-lts-backport-maverick source package in Natty: Invalid Status in linux-lts-backport-natty source package in Natty: Invalid Status in linux-lts-backport-oneiric source package in Natty: Invalid Status in linux-lts-backport-maverick source package in Oneiric: Invalid Status in linux-lts-backport-natty source package in Oneiric: Invalid Status in linux-lts-backport-oneiric source package in Oneiric: Invalid Status in linux source package in Precise: Invalid Status in linux-armadaxp source package in Precise: Invalid Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: Invalid Status in linux-lts-backport-natty source package in Precise: Invalid Status in linux-lts-backport-oneiric source package in Precise: Invalid Status in linux-lts-quantal source package in Precise: New Status in linux-lts-raring source package in Precise: New Status in linux-lts-saucy source package in Precise: New Status in linux-lts-trusty source package in Precise: Invalid Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Quantal: Invalid Status in linux-lts-backport-natty source package in Quantal: Invalid Status in linux-lts-backport-oneiric source package in Quantal: Invalid Status in linux source package in Trusty: Invalid Status in linux-armadaxp source package in Trusty: Invalid Status in linux-ec2 source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-fsl-imx51 source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-lts-backport-maverick source package in Trusty: New Status in linux-lts-backport-natty source package in Trusty: New Status in linux-lts-backport-oneiric source package in Trusty: New Status in linux-lts-quantal source package in Trusty: New Status in linux-lts-raring source package in Trusty: New Status in linux-lts-saucy source package in Trusty: New Status in linux-l
[Kernel-packages] [Bug 1456531] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1456531/+attachment/4476863/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1456531 Title: LightDM (?) blank/white screen after resume from suspend Status in linux package in Ubuntu: Incomplete Bug description: On Xubuntu 15.04, when I suspend the machine and resume afterwards, the screen remains completely white/blank. I can move the mouse cursor, but I don't see any screen elements. Clicking or wildly pressing keys doesn't do anything. I can switch to a different console with Ctrl+Alt+F1 and log in, just fine. For this bug report, I have removed all files from /var/log/lightdm, then rebooted, suspended, resumed, and switched to VT1. Then copied the /var/log/lightdm files to a different location. See their contents attached to this bug report. Other parameters: - Simply locking and unlocking the screen works, ALTHOUGH I also see the white screen there at first, and have to click a mouse button for the login form to show up. - I'm running a system with a fully encrypted hard-drive and have configured LightDM to log me in automatically. - System is up-to-date. - No experimental packages, although I had an experimental version of xserver-xorg-video-intel running, but removed it shortly after. - System is a Thinkpad T450s with Intel HD 5500 graphics. Hope I didn't forget to mention anything important. If you need more information or want me to try something, let me know. --- ApportVersion: 2.17.2-0ubuntu1.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: lxg2068 F pulseaudio /dev/snd/controlC0: lxg2068 F pulseaudio DistroRelease: Ubuntu 15.04 InstallationDate: Installed on 2015-05-16 (134 days ago) InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1) MachineType: LENOVO 20BXCTO1WW Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-28-generic root=UUID=7247f3dc-87dc-460f-a4ec-7d049af66a36 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.19.0-28-generic N/A linux-backports-modules-3.19.0-28-generic N/A linux-firmware 1.143.3 Tags: vivid UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 3.19.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 04/20/2015 dmi.bios.vendor: LENOVO dmi.bios.version: JBET48WW (1.13 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BXCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0E50512 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET48WW(1.13):bd04/20/2015:svnLENOVO:pn20BXCTO1WW:pvrThinkPadT450s:rvnLENOVO:rn20BXCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20BXCTO1WW dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1456531/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 917842] Re: CVE-2012-0045
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 affects ubuntu/trusty/linux-lts-backport-maverick status invalid affects ubuntu/vivid/linux-lts-backport-maverick status invalid affects ubuntu/trusty/linux-lts-backport-natty status invalid affects ubuntu/vivid/linux-lts-backport-natty status invalid affects ubuntu/trusty/linux-lts-backport-oneiric status invalid affects ubuntu/vivid/linux-lts-backport-oneiric status invalid -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (GNU/Linux) iQEcBAEBAgAGBQJWCFYRAAoJEEUTBuC2oiinrPIH/3TCGUSPxc4gWmPNoUUz/HTo tdk8nJwko8vCBrR88HsaiA3C6hiLuofPNXhtGANy7LoqEBCJgFro6EqyGQaN//+O kUP893OOCLuy9ma087ktofDzPcMrZgzxGHozcr9VRrPQEAbASTHxls8HXFm0xA19 f3fiJdqlUW69mC4QFcNnGXBJcMgbQvI+GkF2naZO+S30/xr/Atr2n5DzE5kdn8r0 0NoRzcIHjik5rBBxLCzoEdh94vRmoeuzYBaHSIHseW35WDVTICYCJ63rPzVrgen9 VscAzoprScEP9lYDGL15bRKvFz151X8a0xrjB4G0/fgkSECcxrocTLcElHDdY0E= =ZhuV -END PGP SIGNATURE- ** No longer affects: linux-lts-backport-maverick (Ubuntu Utopic) ** No longer affects: linux-lts-backport-natty (Ubuntu Utopic) ** No longer affects: linux-lts-backport-oneiric (Ubuntu Utopic) ** Changed in: linux-lts-backport-maverick (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-lts-backport-maverick (Ubuntu Vivid) Status: New => Invalid ** Changed in: linux-lts-backport-natty (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-lts-backport-natty (Ubuntu Vivid) Status: New => Invalid ** Changed in: linux-lts-backport-oneiric (Ubuntu Trusty) Status: New => Invalid ** Changed in: linux-lts-backport-oneiric (Ubuntu Vivid) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/917842 Title: CVE-2012-0045 Status in linux package in Ubuntu: Invalid Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-ec2 package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: Invalid Status in linux-fsl-imx51 package in Ubuntu: Invalid Status in linux-goldfish package in Ubuntu: Invalid Status in linux-lts-backport-maverick package in Ubuntu: Invalid Status in linux-lts-backport-natty package in Ubuntu: Invalid Status in linux-lts-backport-oneiric package in Ubuntu: Invalid Status in linux-lts-quantal package in Ubuntu: New Status in linux-lts-raring package in Ubuntu: New Status in linux-lts-saucy package in Ubuntu: New Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: Invalid Status in linux-manta package in Ubuntu: Invalid Status in linux-mvl-dove package in Ubuntu: Invalid Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux-lts-backport-maverick source package in Lucid: Fix Released Status in linux-lts-backport-natty source package in Lucid: Fix Released Status in linux-lts-backport-oneiric source package in Lucid: Fix Released Status in linux-lts-backport-maverick source package in Maverick: Invalid Status in linux-lts-backport-natty source package in Maverick: Invalid Status in linux-lts-backport-oneiric source package in Maverick: Invalid Status in linux-lts-backport-maverick source package in Natty: Invalid Status in linux-lts-backport-natty source package in Natty: Invalid Status in linux-lts-backport-oneiric source package in Natty: Invalid Status in linux-lts-backport-maverick source package in Oneiric: Invalid Status in linux-lts-backport-natty source package in Oneiric: Invalid Status in linux-lts-backport-oneiric source package in Oneiric: Invalid Status in linux source package in Precise: Invalid Status in linux-armadaxp source package in Precise: Invalid Status in linux-ec2 source package in Precise: Invalid Status in linux-flo source package in Precise: Invalid Status in linux-fsl-imx51 source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-lts-backport-maverick source package in Precise: Invalid Status in linux-lts-backport-natty source package in Precise: Invalid Status in linux-lts-backport-oneiric source package in Precise: Invalid Status in linux-lts-quantal source package in Precise: New Status in linux-lts-raring source package in Precise: New Status in linux-lts-saucy source package in Precise: New Status in linux-lts-trusty source package in Precise: Invalid Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-mvl-dove source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Invalid Status in linux-lts-backport-
[Kernel-packages] [Bug 1456531] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1456531/+attachment/4476860/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1456531 Title: LightDM (?) blank/white screen after resume from suspend Status in linux package in Ubuntu: Incomplete Bug description: On Xubuntu 15.04, when I suspend the machine and resume afterwards, the screen remains completely white/blank. I can move the mouse cursor, but I don't see any screen elements. Clicking or wildly pressing keys doesn't do anything. I can switch to a different console with Ctrl+Alt+F1 and log in, just fine. For this bug report, I have removed all files from /var/log/lightdm, then rebooted, suspended, resumed, and switched to VT1. Then copied the /var/log/lightdm files to a different location. See their contents attached to this bug report. Other parameters: - Simply locking and unlocking the screen works, ALTHOUGH I also see the white screen there at first, and have to click a mouse button for the login form to show up. - I'm running a system with a fully encrypted hard-drive and have configured LightDM to log me in automatically. - System is up-to-date. - No experimental packages, although I had an experimental version of xserver-xorg-video-intel running, but removed it shortly after. - System is a Thinkpad T450s with Intel HD 5500 graphics. Hope I didn't forget to mention anything important. If you need more information or want me to try something, let me know. --- ApportVersion: 2.17.2-0ubuntu1.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: lxg2068 F pulseaudio /dev/snd/controlC0: lxg2068 F pulseaudio DistroRelease: Ubuntu 15.04 InstallationDate: Installed on 2015-05-16 (134 days ago) InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1) MachineType: LENOVO 20BXCTO1WW Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-28-generic root=UUID=7247f3dc-87dc-460f-a4ec-7d049af66a36 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.19.0-28-generic N/A linux-backports-modules-3.19.0-28-generic N/A linux-firmware 1.143.3 Tags: vivid UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 3.19.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 04/20/2015 dmi.bios.vendor: LENOVO dmi.bios.version: JBET48WW (1.13 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BXCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0E50512 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET48WW(1.13):bd04/20/2015:svnLENOVO:pn20BXCTO1WW:pvrThinkPadT450s:rvnLENOVO:rn20BXCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20BXCTO1WW dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1456531/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1456531] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1456531/+attachment/4476859/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1456531 Title: LightDM (?) blank/white screen after resume from suspend Status in linux package in Ubuntu: Incomplete Bug description: On Xubuntu 15.04, when I suspend the machine and resume afterwards, the screen remains completely white/blank. I can move the mouse cursor, but I don't see any screen elements. Clicking or wildly pressing keys doesn't do anything. I can switch to a different console with Ctrl+Alt+F1 and log in, just fine. For this bug report, I have removed all files from /var/log/lightdm, then rebooted, suspended, resumed, and switched to VT1. Then copied the /var/log/lightdm files to a different location. See their contents attached to this bug report. Other parameters: - Simply locking and unlocking the screen works, ALTHOUGH I also see the white screen there at first, and have to click a mouse button for the login form to show up. - I'm running a system with a fully encrypted hard-drive and have configured LightDM to log me in automatically. - System is up-to-date. - No experimental packages, although I had an experimental version of xserver-xorg-video-intel running, but removed it shortly after. - System is a Thinkpad T450s with Intel HD 5500 graphics. Hope I didn't forget to mention anything important. If you need more information or want me to try something, let me know. --- ApportVersion: 2.17.2-0ubuntu1.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: lxg2068 F pulseaudio /dev/snd/controlC0: lxg2068 F pulseaudio DistroRelease: Ubuntu 15.04 InstallationDate: Installed on 2015-05-16 (134 days ago) InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1) MachineType: LENOVO 20BXCTO1WW Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-28-generic root=UUID=7247f3dc-87dc-460f-a4ec-7d049af66a36 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.19.0-28-generic N/A linux-backports-modules-3.19.0-28-generic N/A linux-firmware 1.143.3 Tags: vivid UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 3.19.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 04/20/2015 dmi.bios.vendor: LENOVO dmi.bios.version: JBET48WW (1.13 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BXCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0E50512 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET48WW(1.13):bd04/20/2015:svnLENOVO:pn20BXCTO1WW:pvrThinkPadT450s:rvnLENOVO:rn20BXCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20BXCTO1WW dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1456531/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1490143] Re: When resuming after suspension desktop is freezed
Hi Christopher, no changes with kernel 4.3-rc3, same blue screen after resuming from suspension. I am attaching dmesg after resume. ** Attachment added: "dmesg-4.3-rc3" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1490143/+attachment/4476880/+files/dmesg5.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1490143 Title: When resuming after suspension desktop is freezed Status in linux package in Ubuntu: Incomplete Bug description: I suspended my PC for like about 1,5 - 2 hours and when I resumed the desktop had a black background, you could see the launcher bat you were unable to do anything it was freezed. This is my hardware: https://gist.github.com/anonymous/3203c7c5a43a509c0f22. I am attaching the screen-shots of my desktop after resuming, also in terminal (CTRL+ALT+F1) it looked rather garbled. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3 Uname: Linux 4.1.0-3-generic x86_64 ApportVersion: 2.18-0ubuntu7 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Sat Aug 29 13:57:20 2015 DistUpgraded: Fresh install DistroCodename: wily DistroVariant: ubuntu DkmsStatus: virtualbox, 5.0.2, 4.1.0-3-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation G84GL [Quadro FX 370] [10de:040a] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation Device [10de:0491] InstallationDate: Installed on 2015-08-16 (12 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150816) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.1.0-3-generic root=UUID=4b5d483e-4c0c-4013-b27c-0684b9343728 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/13/2007 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0803 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M2N dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0803:bd09/13/2007:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2N:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.12.1+15.10.20150805-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.6.3-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.6.3-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0+git20150819-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3 xserver.bootTime: Sat Aug 29 11:08:42 2015 xserver.configfile: default xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) NOUVEAU(0): [COPY] failed to allocate class. xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.17.2-1ubuntu3 xserver.video_driver: nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1490143/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1456531] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1456531/+attachment/4476861/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1456531 Title: LightDM (?) blank/white screen after resume from suspend Status in linux package in Ubuntu: Incomplete Bug description: On Xubuntu 15.04, when I suspend the machine and resume afterwards, the screen remains completely white/blank. I can move the mouse cursor, but I don't see any screen elements. Clicking or wildly pressing keys doesn't do anything. I can switch to a different console with Ctrl+Alt+F1 and log in, just fine. For this bug report, I have removed all files from /var/log/lightdm, then rebooted, suspended, resumed, and switched to VT1. Then copied the /var/log/lightdm files to a different location. See their contents attached to this bug report. Other parameters: - Simply locking and unlocking the screen works, ALTHOUGH I also see the white screen there at first, and have to click a mouse button for the login form to show up. - I'm running a system with a fully encrypted hard-drive and have configured LightDM to log me in automatically. - System is up-to-date. - No experimental packages, although I had an experimental version of xserver-xorg-video-intel running, but removed it shortly after. - System is a Thinkpad T450s with Intel HD 5500 graphics. Hope I didn't forget to mention anything important. If you need more information or want me to try something, let me know. --- ApportVersion: 2.17.2-0ubuntu1.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: lxg2068 F pulseaudio /dev/snd/controlC0: lxg2068 F pulseaudio DistroRelease: Ubuntu 15.04 InstallationDate: Installed on 2015-05-16 (134 days ago) InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1) MachineType: LENOVO 20BXCTO1WW Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-28-generic root=UUID=7247f3dc-87dc-460f-a4ec-7d049af66a36 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.19.0-28-generic N/A linux-backports-modules-3.19.0-28-generic N/A linux-firmware 1.143.3 Tags: vivid UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 3.19.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 04/20/2015 dmi.bios.vendor: LENOVO dmi.bios.version: JBET48WW (1.13 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BXCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0E50512 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET48WW(1.13):bd04/20/2015:svnLENOVO:pn20BXCTO1WW:pvrThinkPadT450s:rvnLENOVO:rn20BXCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20BXCTO1WW dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1456531/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1296224] Re: Horrible noise via DisplayPort [regression]
Andreas Schildbach, could you please test the latest upstream kernel available from the very top line at the top of the page from http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D (the release names are irrelevant for testing, and please do not test the daily folder)? Install instructions are available at https://wiki.ubuntu.com/Kernel/MainlineBuilds . This will allow additional upstream developers to examine the issue. If the latest kernel did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this issue is fixed in the mainline kernel, please add the following tags by clicking on the yellow circle with a black pencil icon, next to the word Tags, located at the bottom of the report description: kernel-fixed-upstream kernel-fixed-upstream-X.Y-rcZ Where X, Y, and Z are numbers corresponding to the kernel version. If the mainline kernel does not fix the issue, please add the following tags: kernel-bug-exists-upstream kernel-bug-exists-upstream-X.Y-rcZ Please note, an error to install the kernel does not fit the criteria of kernel-bug-exists-upstream. Once testing of the latest upstream kernel is complete, please mark this report's Status as Confirmed. Please let us know your results. Thank you for your understanding. ** Package changed: xserver-xorg-video-intel (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1296224 Title: Horrible noise via DisplayPort [regression] Status in linux package in Ubuntu: Incomplete Bug description: This issue has been present and fixed two years ago and with Trusty Tahr it re-appeared: When logging in and my display is extended to two monitors, and also when the screen blanks, I get 3-5 seconds of horrible noise via DisplayPort audio out. The noise is loud enough to damage ears and loudspeakers, if volume has been set to a normal listening level. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6 Uname: Linux 3.13.0-18-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sun Mar 23 10:18:08 2014 DistUpgraded: 2014-01-03 23:25:11,434 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21c1] InstallationDate: Installed on 2011-08-05 (960 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110803.1) MachineType: LENOVO 29123AG ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-18-generic root=UUID=b9fb2d9e-d248-4294-bd6b-9abe27dfcea4 ro quiet splash SourcePackage: xserver-xorg-video-intel UpgradeStatus: Upgraded to trusty on 2014-01-03 (78 days ago) dmi.bios.date: 10/11/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 6UET70WW (1.50 ) dmi.board.name: 29123AG dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6UET70WW(1.50):bd10/11/2012:svnLENOVO:pn29123AG:pvrThinkPadT410s:rvnLENOVO:rn29123AG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 29123AG dmi.product.version: ThinkPad T410s dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.11+14.04.20140320.1-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.
[Kernel-packages] [Bug 1456531] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1456531/+attachment/4476865/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1456531 Title: LightDM (?) blank/white screen after resume from suspend Status in linux package in Ubuntu: Incomplete Bug description: On Xubuntu 15.04, when I suspend the machine and resume afterwards, the screen remains completely white/blank. I can move the mouse cursor, but I don't see any screen elements. Clicking or wildly pressing keys doesn't do anything. I can switch to a different console with Ctrl+Alt+F1 and log in, just fine. For this bug report, I have removed all files from /var/log/lightdm, then rebooted, suspended, resumed, and switched to VT1. Then copied the /var/log/lightdm files to a different location. See their contents attached to this bug report. Other parameters: - Simply locking and unlocking the screen works, ALTHOUGH I also see the white screen there at first, and have to click a mouse button for the login form to show up. - I'm running a system with a fully encrypted hard-drive and have configured LightDM to log me in automatically. - System is up-to-date. - No experimental packages, although I had an experimental version of xserver-xorg-video-intel running, but removed it shortly after. - System is a Thinkpad T450s with Intel HD 5500 graphics. Hope I didn't forget to mention anything important. If you need more information or want me to try something, let me know. --- ApportVersion: 2.17.2-0ubuntu1.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: lxg2068 F pulseaudio /dev/snd/controlC0: lxg2068 F pulseaudio DistroRelease: Ubuntu 15.04 InstallationDate: Installed on 2015-05-16 (134 days ago) InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1) MachineType: LENOVO 20BXCTO1WW Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-28-generic root=UUID=7247f3dc-87dc-460f-a4ec-7d049af66a36 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.19.0-28-generic N/A linux-backports-modules-3.19.0-28-generic N/A linux-firmware 1.143.3 Tags: vivid UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 3.19.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 04/20/2015 dmi.bios.vendor: LENOVO dmi.bios.version: JBET48WW (1.13 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BXCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0E50512 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET48WW(1.13):bd04/20/2015:svnLENOVO:pn20BXCTO1WW:pvrThinkPadT450s:rvnLENOVO:rn20BXCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20BXCTO1WW dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1456531/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1456531] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1456531/+attachment/4476866/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1456531 Title: LightDM (?) blank/white screen after resume from suspend Status in linux package in Ubuntu: Incomplete Bug description: On Xubuntu 15.04, when I suspend the machine and resume afterwards, the screen remains completely white/blank. I can move the mouse cursor, but I don't see any screen elements. Clicking or wildly pressing keys doesn't do anything. I can switch to a different console with Ctrl+Alt+F1 and log in, just fine. For this bug report, I have removed all files from /var/log/lightdm, then rebooted, suspended, resumed, and switched to VT1. Then copied the /var/log/lightdm files to a different location. See their contents attached to this bug report. Other parameters: - Simply locking and unlocking the screen works, ALTHOUGH I also see the white screen there at first, and have to click a mouse button for the login form to show up. - I'm running a system with a fully encrypted hard-drive and have configured LightDM to log me in automatically. - System is up-to-date. - No experimental packages, although I had an experimental version of xserver-xorg-video-intel running, but removed it shortly after. - System is a Thinkpad T450s with Intel HD 5500 graphics. Hope I didn't forget to mention anything important. If you need more information or want me to try something, let me know. --- ApportVersion: 2.17.2-0ubuntu1.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: lxg2068 F pulseaudio /dev/snd/controlC0: lxg2068 F pulseaudio DistroRelease: Ubuntu 15.04 InstallationDate: Installed on 2015-05-16 (134 days ago) InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1) MachineType: LENOVO 20BXCTO1WW Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-28-generic root=UUID=7247f3dc-87dc-460f-a4ec-7d049af66a36 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.19.0-28-generic N/A linux-backports-modules-3.19.0-28-generic N/A linux-firmware 1.143.3 Tags: vivid UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 3.19.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 04/20/2015 dmi.bios.vendor: LENOVO dmi.bios.version: JBET48WW (1.13 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BXCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0E50512 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET48WW(1.13):bd04/20/2015:svnLENOVO:pn20BXCTO1WW:pvrThinkPadT450s:rvnLENOVO:rn20BXCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20BXCTO1WW dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1456531/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1456531] Re: LightDM (?) blank/white screen after resume from suspend
lxg, as per http://support.lenovo.com/us/en/products/laptops-and- netbooks/thinkpad-t-series-laptops/thinkpad-t450s an update to your computer's buggy and outdated BIOS is available (1.17). If you update to this following https://help.ubuntu.com/community/BIOSUpdate does it change anything? If it doesn't, could you please both specify what happened, and provide the output of the following terminal command: sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date 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. As well, you don't have to create a new bug report. Once the BIOS is updated, if the problem is still reproducible, and the information above is provided, then please mark this report Status Confirmed. Otherwise, please mark this as Invalid. Thank you for your understanding. ** Tags added: bios-outdated-1.17 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1456531 Title: LightDM (?) blank/white screen after resume from suspend Status in linux package in Ubuntu: Incomplete Bug description: On Xubuntu 15.04, when I suspend the machine and resume afterwards, the screen remains completely white/blank. I can move the mouse cursor, but I don't see any screen elements. Clicking or wildly pressing keys doesn't do anything. I can switch to a different console with Ctrl+Alt+F1 and log in, just fine. For this bug report, I have removed all files from /var/log/lightdm, then rebooted, suspended, resumed, and switched to VT1. Then copied the /var/log/lightdm files to a different location. See their contents attached to this bug report. Other parameters: - Simply locking and unlocking the screen works, ALTHOUGH I also see the white screen there at first, and have to click a mouse button for the login form to show up. - I'm running a system with a fully encrypted hard-drive and have configured LightDM to log me in automatically. - System is up-to-date. - No experimental packages, although I had an experimental version of xserver-xorg-video-intel running, but removed it shortly after. - System is a Thinkpad T450s with Intel HD 5500 graphics. Hope I didn't forget to mention anything important. If you need more information or want me to try something, let me know. --- ApportVersion: 2.17.2-0ubuntu1.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: lxg2068 F pulseaudio /dev/snd/controlC0: lxg2068 F pulseaudio DistroRelease: Ubuntu 15.04 InstallationDate: Installed on 2015-05-16 (134 days ago) InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1) MachineType: LENOVO 20BXCTO1WW Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-28-generic root=UUID=7247f3dc-87dc-460f-a4ec-7d049af66a36 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.19.0-28-generic N/A linux-backports-modules-3.19.0-28-generic N/A linux-firmware 1.143.3 Tags: vivid UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 3.19.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 04/20/2015 dmi.bios.vendor: LENOVO dmi.bios.version: JBET48WW (1.13 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BXCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0E50512 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET48WW(1.13):bd04/20/2015:svnLENOVO:pn20BXCTO1WW:pvrThinkPadT450s:rvnLENOVO:rn20BXCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20BXCTO1WW dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1456531/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1456531] Re: LightDM (?) blank/white screen after resume from suspend
** Attachment removed: "WifiSyslog.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1456531/+attachment/4476866/+files/WifiSyslog.txt ** Attachment removed: "CurrentDmesg.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1456531/+attachment/4476855/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1456531 Title: LightDM (?) blank/white screen after resume from suspend Status in linux package in Ubuntu: Incomplete Bug description: On Xubuntu 15.04, when I suspend the machine and resume afterwards, the screen remains completely white/blank. I can move the mouse cursor, but I don't see any screen elements. Clicking or wildly pressing keys doesn't do anything. I can switch to a different console with Ctrl+Alt+F1 and log in, just fine. For this bug report, I have removed all files from /var/log/lightdm, then rebooted, suspended, resumed, and switched to VT1. Then copied the /var/log/lightdm files to a different location. See their contents attached to this bug report. Other parameters: - Simply locking and unlocking the screen works, ALTHOUGH I also see the white screen there at first, and have to click a mouse button for the login form to show up. - I'm running a system with a fully encrypted hard-drive and have configured LightDM to log me in automatically. - System is up-to-date. - No experimental packages, although I had an experimental version of xserver-xorg-video-intel running, but removed it shortly after. - System is a Thinkpad T450s with Intel HD 5500 graphics. Hope I didn't forget to mention anything important. If you need more information or want me to try something, let me know. --- ApportVersion: 2.17.2-0ubuntu1.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: lxg2068 F pulseaudio /dev/snd/controlC0: lxg2068 F pulseaudio DistroRelease: Ubuntu 15.04 InstallationDate: Installed on 2015-05-16 (134 days ago) InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1) MachineType: LENOVO 20BXCTO1WW Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-28-generic root=UUID=7247f3dc-87dc-460f-a4ec-7d049af66a36 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.19.0-28-generic N/A linux-backports-modules-3.19.0-28-generic N/A linux-firmware 1.143.3 Tags: vivid UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 3.19.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 04/20/2015 dmi.bios.vendor: LENOVO dmi.bios.version: JBET48WW (1.13 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BXCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0E50512 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET48WW(1.13):bd04/20/2015:svnLENOVO:pn20BXCTO1WW:pvrThinkPadT450s:rvnLENOVO:rn20BXCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20BXCTO1WW dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1456531/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1296224] [NEW] Horrible noise via DisplayPort [regression]
You have been subscribed to a public bug: This issue has been present and fixed two years ago and with Trusty Tahr it re-appeared: When logging in and my display is extended to two monitors, and also when the screen blanks, I get 3-5 seconds of horrible noise via DisplayPort audio out. The noise is loud enough to damage ears and loudspeakers, if volume has been set to a normal listening level. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6 Uname: Linux 3.13.0-18-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sun Mar 23 10:18:08 2014 DistUpgraded: 2014-01-03 23:25:11,434 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21c1] InstallationDate: Installed on 2011-08-05 (960 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110803.1) MachineType: LENOVO 29123AG ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-18-generic root=UUID=b9fb2d9e-d248-4294-bd6b-9abe27dfcea4 ro quiet splash SourcePackage: xserver-xorg-video-intel UpgradeStatus: Upgraded to trusty on 2014-01-03 (78 days ago) dmi.bios.date: 10/11/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 6UET70WW (1.50 ) dmi.board.name: 29123AG dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6UET70WW(1.50):bd10/11/2012:svnLENOVO:pn29123AG:pvrThinkPadT410s:rvnLENOVO:rn29123AG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 29123AG dmi.product.version: ThinkPad T410s dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.11+14.04.20140320.1-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Sun Mar 23 10:09:13 2014 xserver.configfile: default xserver.errors: N-Trig Pen stylus: Invalid type 'cursor' for this device. N-Trig Pen stylus: Invalid type 'touch' for this device. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 16438 vendor LEN xserver.version: 2:1.15.0-1ubuntu7 ** Affects: linux (Ubuntu) Importance: Medium Status: Incomplete ** Tags: amd64 apport-bug compiz-0.9 latest-bios-1.5 trusty ubuntu utopic vivid wily -- Horrible noise via DisplayPort [regression] https://bugs.launchpad.net/bugs/1296224 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1456531] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1456531/+attachment/4476864/+files/RfKill.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1456531 Title: LightDM (?) blank/white screen after resume from suspend Status in linux package in Ubuntu: Incomplete Bug description: On Xubuntu 15.04, when I suspend the machine and resume afterwards, the screen remains completely white/blank. I can move the mouse cursor, but I don't see any screen elements. Clicking or wildly pressing keys doesn't do anything. I can switch to a different console with Ctrl+Alt+F1 and log in, just fine. For this bug report, I have removed all files from /var/log/lightdm, then rebooted, suspended, resumed, and switched to VT1. Then copied the /var/log/lightdm files to a different location. See their contents attached to this bug report. Other parameters: - Simply locking and unlocking the screen works, ALTHOUGH I also see the white screen there at first, and have to click a mouse button for the login form to show up. - I'm running a system with a fully encrypted hard-drive and have configured LightDM to log me in automatically. - System is up-to-date. - No experimental packages, although I had an experimental version of xserver-xorg-video-intel running, but removed it shortly after. - System is a Thinkpad T450s with Intel HD 5500 graphics. Hope I didn't forget to mention anything important. If you need more information or want me to try something, let me know. --- ApportVersion: 2.17.2-0ubuntu1.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: lxg2068 F pulseaudio /dev/snd/controlC0: lxg2068 F pulseaudio DistroRelease: Ubuntu 15.04 InstallationDate: Installed on 2015-05-16 (134 days ago) InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1) MachineType: LENOVO 20BXCTO1WW Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-28-generic root=UUID=7247f3dc-87dc-460f-a4ec-7d049af66a36 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.19.0-28-generic N/A linux-backports-modules-3.19.0-28-generic N/A linux-firmware 1.143.3 Tags: vivid UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 3.19.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 04/20/2015 dmi.bios.vendor: LENOVO dmi.bios.version: JBET48WW (1.13 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BXCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0E50512 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET48WW(1.13):bd04/20/2015:svnLENOVO:pn20BXCTO1WW:pvrThinkPadT450s:rvnLENOVO:rn20BXCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20BXCTO1WW dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1456531/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1456531] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1456531/+attachment/4476862/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1456531 Title: LightDM (?) blank/white screen after resume from suspend Status in linux package in Ubuntu: Incomplete Bug description: On Xubuntu 15.04, when I suspend the machine and resume afterwards, the screen remains completely white/blank. I can move the mouse cursor, but I don't see any screen elements. Clicking or wildly pressing keys doesn't do anything. I can switch to a different console with Ctrl+Alt+F1 and log in, just fine. For this bug report, I have removed all files from /var/log/lightdm, then rebooted, suspended, resumed, and switched to VT1. Then copied the /var/log/lightdm files to a different location. See their contents attached to this bug report. Other parameters: - Simply locking and unlocking the screen works, ALTHOUGH I also see the white screen there at first, and have to click a mouse button for the login form to show up. - I'm running a system with a fully encrypted hard-drive and have configured LightDM to log me in automatically. - System is up-to-date. - No experimental packages, although I had an experimental version of xserver-xorg-video-intel running, but removed it shortly after. - System is a Thinkpad T450s with Intel HD 5500 graphics. Hope I didn't forget to mention anything important. If you need more information or want me to try something, let me know. --- ApportVersion: 2.17.2-0ubuntu1.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: lxg2068 F pulseaudio /dev/snd/controlC0: lxg2068 F pulseaudio DistroRelease: Ubuntu 15.04 InstallationDate: Installed on 2015-05-16 (134 days ago) InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1) MachineType: LENOVO 20BXCTO1WW Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-28-generic root=UUID=7247f3dc-87dc-460f-a4ec-7d049af66a36 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.19.0-28-generic N/A linux-backports-modules-3.19.0-28-generic N/A linux-firmware 1.143.3 Tags: vivid UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 3.19.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 04/20/2015 dmi.bios.vendor: LENOVO dmi.bios.version: JBET48WW (1.13 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BXCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0E50512 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET48WW(1.13):bd04/20/2015:svnLENOVO:pn20BXCTO1WW:pvrThinkPadT450s:rvnLENOVO:rn20BXCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20BXCTO1WW dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1456531/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1456531] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1456531/+attachment/4476856/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1456531 Title: LightDM (?) blank/white screen after resume from suspend Status in linux package in Ubuntu: Incomplete Bug description: On Xubuntu 15.04, when I suspend the machine and resume afterwards, the screen remains completely white/blank. I can move the mouse cursor, but I don't see any screen elements. Clicking or wildly pressing keys doesn't do anything. I can switch to a different console with Ctrl+Alt+F1 and log in, just fine. For this bug report, I have removed all files from /var/log/lightdm, then rebooted, suspended, resumed, and switched to VT1. Then copied the /var/log/lightdm files to a different location. See their contents attached to this bug report. Other parameters: - Simply locking and unlocking the screen works, ALTHOUGH I also see the white screen there at first, and have to click a mouse button for the login form to show up. - I'm running a system with a fully encrypted hard-drive and have configured LightDM to log me in automatically. - System is up-to-date. - No experimental packages, although I had an experimental version of xserver-xorg-video-intel running, but removed it shortly after. - System is a Thinkpad T450s with Intel HD 5500 graphics. Hope I didn't forget to mention anything important. If you need more information or want me to try something, let me know. --- ApportVersion: 2.17.2-0ubuntu1.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: lxg2068 F pulseaudio /dev/snd/controlC0: lxg2068 F pulseaudio DistroRelease: Ubuntu 15.04 InstallationDate: Installed on 2015-05-16 (134 days ago) InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1) MachineType: LENOVO 20BXCTO1WW Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-28-generic root=UUID=7247f3dc-87dc-460f-a4ec-7d049af66a36 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.19.0-28-generic N/A linux-backports-modules-3.19.0-28-generic N/A linux-firmware 1.143.3 Tags: vivid UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 3.19.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 04/20/2015 dmi.bios.vendor: LENOVO dmi.bios.version: JBET48WW (1.13 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BXCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0E50512 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET48WW(1.13):bd04/20/2015:svnLENOVO:pn20BXCTO1WW:pvrThinkPadT450s:rvnLENOVO:rn20BXCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20BXCTO1WW dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1456531/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1456531] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1456531/+attachment/4476857/+files/JournalErrors.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1456531 Title: LightDM (?) blank/white screen after resume from suspend Status in linux package in Ubuntu: Incomplete Bug description: On Xubuntu 15.04, when I suspend the machine and resume afterwards, the screen remains completely white/blank. I can move the mouse cursor, but I don't see any screen elements. Clicking or wildly pressing keys doesn't do anything. I can switch to a different console with Ctrl+Alt+F1 and log in, just fine. For this bug report, I have removed all files from /var/log/lightdm, then rebooted, suspended, resumed, and switched to VT1. Then copied the /var/log/lightdm files to a different location. See their contents attached to this bug report. Other parameters: - Simply locking and unlocking the screen works, ALTHOUGH I also see the white screen there at first, and have to click a mouse button for the login form to show up. - I'm running a system with a fully encrypted hard-drive and have configured LightDM to log me in automatically. - System is up-to-date. - No experimental packages, although I had an experimental version of xserver-xorg-video-intel running, but removed it shortly after. - System is a Thinkpad T450s with Intel HD 5500 graphics. Hope I didn't forget to mention anything important. If you need more information or want me to try something, let me know. --- ApportVersion: 2.17.2-0ubuntu1.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: lxg2068 F pulseaudio /dev/snd/controlC0: lxg2068 F pulseaudio DistroRelease: Ubuntu 15.04 InstallationDate: Installed on 2015-05-16 (134 days ago) InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1) MachineType: LENOVO 20BXCTO1WW Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-28-generic root=UUID=7247f3dc-87dc-460f-a4ec-7d049af66a36 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.19.0-28-generic N/A linux-backports-modules-3.19.0-28-generic N/A linux-firmware 1.143.3 Tags: vivid UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 3.19.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 04/20/2015 dmi.bios.vendor: LENOVO dmi.bios.version: JBET48WW (1.13 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BXCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0E50512 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET48WW(1.13):bd04/20/2015:svnLENOVO:pn20BXCTO1WW:pvrThinkPadT450s:rvnLENOVO:rn20BXCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20BXCTO1WW dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1456531/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1456531] Re: LightDM (?) blank/white screen after resume from suspend
apport information ** Tags added: apport-collected vivid ** Description changed: On Xubuntu 15.04, when I suspend the machine and resume afterwards, the screen remains completely white/blank. I can move the mouse cursor, but I don't see any screen elements. Clicking or wildly pressing keys doesn't do anything. I can switch to a different console with Ctrl+Alt+F1 and log in, just fine. For this bug report, I have removed all files from /var/log/lightdm, then rebooted, suspended, resumed, and switched to VT1. Then copied the /var/log/lightdm files to a different location. See their contents attached to this bug report. Other parameters: - Simply locking and unlocking the screen works, ALTHOUGH I also see the white screen there at first, and have to click a mouse button for the login form to show up. - I'm running a system with a fully encrypted hard-drive and have configured LightDM to log me in automatically. - System is up-to-date. - No experimental packages, although I had an experimental version of xserver-xorg-video-intel running, but removed it shortly after. - System is a Thinkpad T450s with Intel HD 5500 graphics. - Hope I didn't forget to mention anything important. If you need more - information or want me to try something, let me know. + Hope I didn't forget to mention anything important. If you need more information or want me to try something, let me know. + --- + ApportVersion: 2.17.2-0ubuntu1.5 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC1: lxg2068 F pulseaudio + /dev/snd/controlC0: lxg2068 F pulseaudio + DistroRelease: Ubuntu 15.04 + InstallationDate: Installed on 2015-05-16 (134 days ago) + InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1) + MachineType: LENOVO 20BXCTO1WW + Package: linux (not installed) + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-28-generic root=UUID=7247f3dc-87dc-460f-a4ec-7d049af66a36 ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5 + PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. + RelatedPackageVersions: + linux-restricted-modules-3.19.0-28-generic N/A + linux-backports-modules-3.19.0-28-generic N/A + linux-firmware 1.143.3 + Tags: vivid + UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' + Uname: Linux 3.19.0-28-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: + + _MarkForUpload: True + dmi.bios.date: 04/20/2015 + dmi.bios.vendor: LENOVO + dmi.bios.version: JBET48WW (1.13 ) + dmi.board.asset.tag: Not Available + dmi.board.name: 20BXCTO1WW + dmi.board.vendor: LENOVO + dmi.board.version: SDK0E50512 STD + dmi.chassis.asset.tag: No Asset Information + dmi.chassis.type: 10 + dmi.chassis.vendor: LENOVO + dmi.chassis.version: None + dmi.modalias: dmi:bvnLENOVO:bvrJBET48WW(1.13):bd04/20/2015:svnLENOVO:pn20BXCTO1WW:pvrThinkPadT450s:rvnLENOVO:rn20BXCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone: + dmi.product.name: 20BXCTO1WW + dmi.product.version: ThinkPad T450s + dmi.sys.vendor: LENOVO ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1456531/+attachment/4476853/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1456531 Title: LightDM (?) blank/white screen after resume from suspend Status in linux package in Ubuntu: Incomplete Bug description: On Xubuntu 15.04, when I suspend the machine and resume afterwards, the screen remains completely white/blank. I can move the mouse cursor, but I don't see any screen elements. Clicking or wildly pressing keys doesn't do anything. I can switch to a different console with Ctrl+Alt+F1 and log in, just fine. For this bug report, I have removed all files from /var/log/lightdm, then rebooted, suspended, resumed, and switched to VT1. Then copied the /var/log/lightdm files to a different location. See their contents attached to this bug report. Other parameters: - Simply locking and unlocking the screen works, ALTHOUGH I also see the white screen there at first, and have to click a mouse button for the login form to show up. - I'm running a system with a fully encrypted hard-drive and have configured LightDM to log me in automatically. - System is up-to-date. - No experimental packages, although I had an experimental version of xserver-xorg-video-intel running, but removed it shortly after. - System is a Thinkpad T450s with Intel HD 5500 graphics. Hope I didn't forget to mention anything important. If you need more information or want me to try something, let me know. --- ApportVersion: 2.17.2-0ubuntu1.5
[Kernel-packages] [Bug 1456531] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1456531/+attachment/4476855/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1456531 Title: LightDM (?) blank/white screen after resume from suspend Status in linux package in Ubuntu: Incomplete Bug description: On Xubuntu 15.04, when I suspend the machine and resume afterwards, the screen remains completely white/blank. I can move the mouse cursor, but I don't see any screen elements. Clicking or wildly pressing keys doesn't do anything. I can switch to a different console with Ctrl+Alt+F1 and log in, just fine. For this bug report, I have removed all files from /var/log/lightdm, then rebooted, suspended, resumed, and switched to VT1. Then copied the /var/log/lightdm files to a different location. See their contents attached to this bug report. Other parameters: - Simply locking and unlocking the screen works, ALTHOUGH I also see the white screen there at first, and have to click a mouse button for the login form to show up. - I'm running a system with a fully encrypted hard-drive and have configured LightDM to log me in automatically. - System is up-to-date. - No experimental packages, although I had an experimental version of xserver-xorg-video-intel running, but removed it shortly after. - System is a Thinkpad T450s with Intel HD 5500 graphics. Hope I didn't forget to mention anything important. If you need more information or want me to try something, let me know. --- ApportVersion: 2.17.2-0ubuntu1.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: lxg2068 F pulseaudio /dev/snd/controlC0: lxg2068 F pulseaudio DistroRelease: Ubuntu 15.04 InstallationDate: Installed on 2015-05-16 (134 days ago) InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1) MachineType: LENOVO 20BXCTO1WW Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-28-generic root=UUID=7247f3dc-87dc-460f-a4ec-7d049af66a36 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.19.0-28-generic N/A linux-backports-modules-3.19.0-28-generic N/A linux-firmware 1.143.3 Tags: vivid UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 3.19.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 04/20/2015 dmi.bios.vendor: LENOVO dmi.bios.version: JBET48WW (1.13 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BXCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0E50512 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET48WW(1.13):bd04/20/2015:svnLENOVO:pn20BXCTO1WW:pvrThinkPadT450s:rvnLENOVO:rn20BXCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20BXCTO1WW dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1456531/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1456531] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1456531/+attachment/4476854/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1456531 Title: LightDM (?) blank/white screen after resume from suspend Status in linux package in Ubuntu: Incomplete Bug description: On Xubuntu 15.04, when I suspend the machine and resume afterwards, the screen remains completely white/blank. I can move the mouse cursor, but I don't see any screen elements. Clicking or wildly pressing keys doesn't do anything. I can switch to a different console with Ctrl+Alt+F1 and log in, just fine. For this bug report, I have removed all files from /var/log/lightdm, then rebooted, suspended, resumed, and switched to VT1. Then copied the /var/log/lightdm files to a different location. See their contents attached to this bug report. Other parameters: - Simply locking and unlocking the screen works, ALTHOUGH I also see the white screen there at first, and have to click a mouse button for the login form to show up. - I'm running a system with a fully encrypted hard-drive and have configured LightDM to log me in automatically. - System is up-to-date. - No experimental packages, although I had an experimental version of xserver-xorg-video-intel running, but removed it shortly after. - System is a Thinkpad T450s with Intel HD 5500 graphics. Hope I didn't forget to mention anything important. If you need more information or want me to try something, let me know. --- ApportVersion: 2.17.2-0ubuntu1.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: lxg2068 F pulseaudio /dev/snd/controlC0: lxg2068 F pulseaudio DistroRelease: Ubuntu 15.04 InstallationDate: Installed on 2015-05-16 (134 days ago) InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1) MachineType: LENOVO 20BXCTO1WW Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-28-generic root=UUID=7247f3dc-87dc-460f-a4ec-7d049af66a36 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.19.0-28-generic N/A linux-backports-modules-3.19.0-28-generic N/A linux-firmware 1.143.3 Tags: vivid UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 3.19.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 04/20/2015 dmi.bios.vendor: LENOVO dmi.bios.version: JBET48WW (1.13 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BXCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0E50512 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET48WW(1.13):bd04/20/2015:svnLENOVO:pn20BXCTO1WW:pvrThinkPadT450s:rvnLENOVO:rn20BXCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20BXCTO1WW dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1456531/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1456531] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1456531/+attachment/4476858/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1456531 Title: LightDM (?) blank/white screen after resume from suspend Status in linux package in Ubuntu: Incomplete Bug description: On Xubuntu 15.04, when I suspend the machine and resume afterwards, the screen remains completely white/blank. I can move the mouse cursor, but I don't see any screen elements. Clicking or wildly pressing keys doesn't do anything. I can switch to a different console with Ctrl+Alt+F1 and log in, just fine. For this bug report, I have removed all files from /var/log/lightdm, then rebooted, suspended, resumed, and switched to VT1. Then copied the /var/log/lightdm files to a different location. See their contents attached to this bug report. Other parameters: - Simply locking and unlocking the screen works, ALTHOUGH I also see the white screen there at first, and have to click a mouse button for the login form to show up. - I'm running a system with a fully encrypted hard-drive and have configured LightDM to log me in automatically. - System is up-to-date. - No experimental packages, although I had an experimental version of xserver-xorg-video-intel running, but removed it shortly after. - System is a Thinkpad T450s with Intel HD 5500 graphics. Hope I didn't forget to mention anything important. If you need more information or want me to try something, let me know. --- ApportVersion: 2.17.2-0ubuntu1.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: lxg2068 F pulseaudio /dev/snd/controlC0: lxg2068 F pulseaudio DistroRelease: Ubuntu 15.04 InstallationDate: Installed on 2015-05-16 (134 days ago) InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1) MachineType: LENOVO 20BXCTO1WW Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-28-generic root=UUID=7247f3dc-87dc-460f-a4ec-7d049af66a36 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.19.0-28-generic N/A linux-backports-modules-3.19.0-28-generic N/A linux-firmware 1.143.3 Tags: vivid UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 3.19.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 04/20/2015 dmi.bios.vendor: LENOVO dmi.bios.version: JBET48WW (1.13 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BXCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0E50512 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET48WW(1.13):bd04/20/2015:svnLENOVO:pn20BXCTO1WW:pvrThinkPadT450s:rvnLENOVO:rn20BXCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20BXCTO1WW dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1456531/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1465506] [NEW] plane A assertion failure (expected on, current off) on Intel NUC 5i5RYH
You have been subscribed to a public bug: Getting assertion failures: [ 9925.287975] WARNING: CPU: 3 PID: 7538 at /build/buildd/linux-3.19.0/drivers/gpu/drm/i915/intel_display.c:1256 assert_plane.constprop.87+0x7b/0x90 [i 915]() [ 9925.287976] plane A assertion failure (expected on, current off) Around the same time, WiFi connections drop. I cannot prove the two problems are related, but I don't have WiFi issues on other devices. alex@nuc1-hkg:~$ lsb_release -rd Description:Ubuntu 15.04 Release:15.04 alex@nuc1-hkg:~$ apt-cache policy xserver-xorg-video-intel xserver-xorg-video-intel: Installed: 2:2.99.917-1~exp1ubuntu2.2 Candidate: 2:2.99.917-1~exp1ubuntu2.2 Version table: *** 2:2.99.917-1~exp1ubuntu2.2 0 500 http://tw.archive.ubuntu.com/ubuntu/ vivid-updates/main amd64 Packages 100 /var/lib/dpkg/status 2:2.99.917-1~exp1ubuntu2build1 0 500 http://tw.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages alex@nuc1-hkg:~$ apt-cache policy linux-image-generic linux-image-generic: Installed: 3.19.0.21.20 Candidate: 3.19.0.21.20 Version table: *** 3.19.0.21.20 0 500 http://tw.archive.ubuntu.com/ubuntu/ vivid-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ vivid-security/main amd64 Packages 100 /var/lib/dpkg/status 3.19.0.15.14 0 500 http://tw.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2.2 ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8 Uname: Linux 3.19.0-21-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Tue Jun 16 14:33:41 2015 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Broadwell-U Integrated Graphics [8086:1626] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Device [8086:2057] InstallationDate: Installed on 2015-06-16 (0 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-21-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-video-intel UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/29/2015 dmi.bios.vendor: Intel Corporation dmi.bios.version: RYBDWi35.86A.0249.2015.0529.1640 dmi.board.name: NUC5i5RYB dmi.board.vendor: Intel Corporation dmi.board.version: H40999-503 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorporation:bvrRYBDWi35.86A.0249.2015.0529.1640:bd05/29/2015:svn:pn:pvr:rvnIntelCorporation:rnNUC5i5RYB:rvrH40999-503:cvn:ct3:cvr: version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Tue Jun 16 14:32:31 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 10103 vendor AOC xserver.version: 2:1.17.1-0ubuntu3 ** Affects: xserver-xorg-video-intel Importance: Unknown Status: Unknown ** Affects: linux (Ubuntu) Importance: Low Status: Incomplete ** Tags: amd64 apport-bug bios-outdated-0350 ubuntu vivid -- plane A assertion failure (expected on, current off) on Intel NUC 5i5RYH https://bugs.launchpad.net/bugs/1465506 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1454108] Re: HP Probook 450 usb ehci breaks between 3.13.0-36 and 3.13.0-37
All the new kernel updates still suffer from same problem, I have to hold back kernel to 3.13.0-36 think its related to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1072918 and https://bugs.launchpad.net/ubuntu/+source/linux-lts-trusty/+bug/1454108 and https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1133670 If it worked perfectly in 3.13.0-36, what change was made in 37 that breaks it? There is no linux firmware updater software on HP site, and I do not wish to install windows just to do a hp firmware flash if its some changes in linux kernel that is causing the problem. ** Also affects: linux-kernel-headers Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-trusty in Ubuntu. https://bugs.launchpad.net/bugs/1454108 Title: HP Probook 450 usb ehci breaks between 3.13.0-36 and 3.13.0-37 Status in linux-kernel-headers: New Status in linux-lts-trusty package in Ubuntu: New Bug description: Release: Ubuntu 14.04.2 LTS Package version: linux-image-3.13.0-37-generic What expect to happen: USB to work after boot-up Whap happened instead: dead USB, no dmesg messages when unplugging or plugging in USB devices. HP Probook 450 USB support got broken since 3.13.0-37. Ubuntu 14.04.2 LTS Similar but not identical to problems as described in https://bugs.launchpad.net/bugs/1072918. All USB ports dead. dmesg shows ehci_hcd died. cleaning up. By passing extra kernel parameters using grub menu: ehci=noirq (or was that acpi=noirq) makes it work but that breaks onboard ethernet. also tried with tried iommu=soft (didn't work) Tried all kernel images from 3.13.0-37 to 3.13.0-52 .. all the same result: broken USB. had to back-step to 3.13.0-36 ... Just thought I'd mention, that might affect other HP Probook models as well. kernel modules affected: xhci_hcd, hid_generic, usbhid, ehci To manage notifications about this bug go to: https://bugs.launchpad.net/linux-kernel-headers/+bug/1454108/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1462728] Re: intel driver keeps crashing after suspend
the_one(2), thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command, as it will automatically gather debugging information, in a terminal: apport-collect -p linux 1462728 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. ** Package changed: xserver-xorg-video-intel (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Importance: Undecided => Low ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1462728 Title: intel driver keeps crashing after suspend Status in linux package in Ubuntu: Incomplete Bug description: I'm not completely sure what's happening but after resuming from suspend eth0 stops working all the time. Dmesg seems to indicate that the intel driver is responsible? Dmesg says: [16066.244100] [ cut here ] [16066.244187] WARNING: CPU: 0 PID: 0 at /build/buildd/linux-3.19.0/drivers/gpu/drm/i915/intel_display.c:9717 intel_check_page_flip+0xda/0xf0 [i915]() [16066.244189] Kicking stuck page flip: queued at 820384, now 820396 [16066.244191] Modules linked in: ctr ccm binfmt_misc bbswitch(OE) nls_iso8859_1 i915_bpo snd_hda_codec_idt snd_hda_codec_generic intel_ips arc4 intel_rapl iosf_mbi x86_pkg_temp_thermal intel_powerclamp coretemp ath9k ath9k_common kvm ath9k_hw snd_hda_intel snd_hda_controller snd_hda_codec crct10dif_pclmul crc32_pclmul ath uvcvideo snd_hwdep mac80211 ghash_clmulni_intel videobuf2_vmalloc snd_pcm videobuf2_memops videobuf2_core aesni_intel i915 v4l2_common aes_x86_64 videodev lrw snd_seq_midi media snd_seq_midi_event gf128mul glue_helper cfg80211 snd_rawmidi ablk_helper cryptd snd_seq drm_kms_helper snd_seq_device joydev snd_timer drm serio_raw snd ie31200_edac mei_me soundcore mei i2c_algo_bit lpc_ich shpchp edac_core ideapad_laptop soc_button_array sparse_keymap wmi video mac_hid parport_pc ppdev lp [16066.244230] parport autofs4 uas usb_storage ahci psmouse alx libahci mdio [16066.244240] CPU: 0 PID: 0 Comm: swapper/0 Tainted: GW OE 3.19.0-18-generic #18-Ubuntu [16066.244242] Hardware name: LENOVO 20250/Durian 7A1, BIOS 7FCN95WW 04/29/2014 [16066.244243] c065dde8 88035f203d28 817c27cd 0007 [16066.244245] 88035f203d78 88035f203d68 8107593a 88035f203d88 [16066.244247] 880350a94000 88034cdfd000 88034cdfd1a8 [16066.244249] Call Trace: [16066.244251][] dump_stack+0x45/0x57 [16066.244267] [] warn_slowpath_common+0x8a/0xc0 [16066.244269] [] warn_slowpath_fmt+0x46/0x50 [16066.244288] [] intel_check_page_flip+0xda/0xf0 [i915] [16066.244306] [] ironlake_irq_handler+0x2e8/0xfd0 [i915] [16066.244314] [] ? rebalance_domains+0xe0/0x280 [16066.244322] [] handle_irq_event_percpu+0x77/0x1a0 [16066.244324] [] handle_irq_event+0x41/0x70 [16066.244328] [] handle_edge_irq+0x6e/0x120 [16066.244331] [] handle_irq+0x22/0x40 [16066.244334] [] do_IRQ+0x4f/0xf0 [16066.244336] [] common_interrupt+0x6d/0x6d [16066.244337][] ? cpuidle_enter_state+0x65/0x160 [16066.244341] [] ? cpuidle_enter_state+0x51/0x160 [16066.244343] [] cpuidle_enter+0x17/0x20 [16066.244345] [] cpu_startup_entry+0x311/0x3b0 [16066.244349] [] rest_init+0x77/0x80 [16066.244354] [] start_kernel+0x482/0x48f [16066.244356] [] ? early_idt_handlers+0x120/0x120 [16066.244358] [] x86_64_start_reservations+0x2a/0x2c [16066.244360] [] x86_64_start_kernel+0x143/0x152 [16066.244361] ---[ end trace 5d72b504d95d3a93 ]--- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1462728/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1456531] Re: LightDM (?) blank/white screen after resume from suspend
lxg, thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command, as it will automatically gather debugging information, in a terminal: apport-collect -p linux 1456531 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. ** Package changed: xserver-xorg-video-intel (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Importance: Undecided => Low ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1456531 Title: LightDM (?) blank/white screen after resume from suspend Status in linux package in Ubuntu: Incomplete Bug description: On Xubuntu 15.04, when I suspend the machine and resume afterwards, the screen remains completely white/blank. I can move the mouse cursor, but I don't see any screen elements. Clicking or wildly pressing keys doesn't do anything. I can switch to a different console with Ctrl+Alt+F1 and log in, just fine. For this bug report, I have removed all files from /var/log/lightdm, then rebooted, suspended, resumed, and switched to VT1. Then copied the /var/log/lightdm files to a different location. See their contents attached to this bug report. Other parameters: - Simply locking and unlocking the screen works, ALTHOUGH I also see the white screen there at first, and have to click a mouse button for the login form to show up. - I'm running a system with a fully encrypted hard-drive and have configured LightDM to log me in automatically. - System is up-to-date. - No experimental packages, although I had an experimental version of xserver-xorg-video-intel running, but removed it shortly after. - System is a Thinkpad T450s with Intel HD 5500 graphics. Hope I didn't forget to mention anything important. If you need more information or want me to try something, let me know. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1456531/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1495116] Re: booting with amd64 kernel and completely i386 userland is unstable during the system upstart
Yes, my BIOS is also Phoenix, as in that buggy case! So, it's very probable that it's the same known problem. marsmorgana@marsmorgana:~$ cat /sys/devices/virtual/dmi/id/bios_vendor Phoenix Technologies Ltd. marsmorgana@marsmorgana:~$ cat /sys/devices/virtual/dmi/id/bios_version 07LI.MP00.20080926.SCY marsmorgana@marsmorgana:~$ cat /sys/devices/virtual/dmi/id/bios_date 09/26/2008 marsmorgana@marsmorgana:~$ The samsung site offers a newer BIOS (10LI) for my computer model at http://www.samsung.com/ru/support/model/NP-R510-FS0JRU ; as WIN_R510_10LI.exe . Well, it seems that I'll have to use windows to update the BIOS (as the simplest way)... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1495116 Title: booting with amd64 kernel and completely i386 userland is unstable during the system upstart Status in linux package in Ubuntu: Confirmed Bug description: I wanted to run my 14.10 (Utopic) i386 system with the amd64 kernel, so I added that architecture and apt-get-installed the amd64 linux- image and linux-image-extra (I learned this was possible thanks to the advice at http://askubuntu.com/a/635774/19753 ). However, the system upstart procedure more often fails than not: it fails by rebooting the computer. (Only around 1 time of 4 is successful.) A limited system start is (probably, always) successful: either with init=/bin/bash parameter to the kernel, or choosing the recovery boot option. (However, if I "resume" from the recovery menu, or run "exec init" in bash, then the upstart procedure is similarly unstable: it usually fails/crashes and reboots.) I checked my suspection that the video driver (nouveau) and X might be involved, but that turned out not true: the upstart procedure is similarly unstable with "nomodesetting" kernel parameter and without, booting into runlevel 3 or the default one. Perhaps, I'd like to debug the upstart procedure step-by-step to detect which step makes the system crash and reboot, but I don't know how. As concerns the timing, the moment the reboot happens can be different: it can happen rather early (when I see the message about activating the swap) or much later. If the system upstart procedure has completed successfully, then it works in a quite stable manner and doesn't crash/reboot. So, there is something bad specifically during the system upstart procedure. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: upstart 1.13.2-0ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-44.59-generic 3.16.7-ckt14 Uname: Linux 3.16.0-44-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.5 Architecture: i386 CurrentDesktop: Unity Date: Sat Sep 12 18:36:28 2015 InstallationDate: Installed on 2014-06-04 (464 days ago) InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 (20140204) ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash SourcePackage: upstart UpgradeStatus: Upgraded to utopic on 2015-09-11 (0 days ago) UpstartBugCategory: System UpstartRunningSessionVersion: upstart 1.13.2 UpstartRunningSystemVersion: init (upstart 1.13.2) modified.conffile..etc.at.deny: [inaccessible: [Errno 13] Отказано в доступе: '/etc/at.deny'] modified.conffile..etc.cron.daily.upstart: [modified] modified.conffile..etc.cups.cups.browsed.conf: [modified] modified.conffile..etc.default.apport: [modified] modified.conffile..etc.default.cups: [modified] modified.conffile..etc.init.d.binfmt.support: [modified] mtime.conffile..etc.X11.Xsession.d.99upstart: 2014-09-30T12:21:08 mtime.conffile..etc.cron.daily.upstart: 2014-09-30T12:27:13 mtime.conffile..etc.cups.cups.browsed.conf: 2015-09-06T09:29:16.410097 mtime.conffile..etc.default.apport: 2014-06-05T12:49:10.316398 mtime.conffile..etc.default.cups: 2015-09-06T09:20:49.891585 mtime.conffile..etc.init.d.binfmt.support: 2014-09-30T12:21:08 mtime.conffile..etc.upstart.xsessions: 2014-09-30T12:21:08 --- ApportVersion: 2.14.7-0ubuntu8.5 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: marsmorgana 1972 F pulseaudio CRDA: country RU: DFS-UNSET (2402 - 2482 @ 40), (N/A, 20) (5735 - 5835 @ 20), (N/A, 30) CurrentDesktop: Unity DistroRelease: Ubuntu 14.10 HibernationDevice: RESUME=UUID=9267c811-3a01-4484-b968-c08582280d81 InstallationDate: Installed on 2014-06-04 (464 days ago) InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 (20140204) MachineType: SAMSUNG ELECTRONICS CO., LTD. R510/P510 Package: upstart 1.13.2-0ubuntu2 PackageArchitecture: i386 ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16
[Kernel-packages] [Bug 1462728] [NEW] intel driver keeps crashing after suspend
You have been subscribed to a public bug: I'm not completely sure what's happening but after resuming from suspend eth0 stops working all the time. Dmesg seems to indicate that the intel driver is responsible? Dmesg says: [16066.244100] [ cut here ] [16066.244187] WARNING: CPU: 0 PID: 0 at /build/buildd/linux-3.19.0/drivers/gpu/drm/i915/intel_display.c:9717 intel_check_page_flip+0xda/0xf0 [i915]() [16066.244189] Kicking stuck page flip: queued at 820384, now 820396 [16066.244191] Modules linked in: ctr ccm binfmt_misc bbswitch(OE) nls_iso8859_1 i915_bpo snd_hda_codec_idt snd_hda_codec_generic intel_ips arc4 intel_rapl iosf_mbi x86_pkg_temp_thermal intel_powerclamp coretemp ath9k ath9k_common kvm ath9k_hw snd_hda_intel snd_hda_controller snd_hda_codec crct10dif_pclmul crc32_pclmul ath uvcvideo snd_hwdep mac80211 ghash_clmulni_intel videobuf2_vmalloc snd_pcm videobuf2_memops videobuf2_core aesni_intel i915 v4l2_common aes_x86_64 videodev lrw snd_seq_midi media snd_seq_midi_event gf128mul glue_helper cfg80211 snd_rawmidi ablk_helper cryptd snd_seq drm_kms_helper snd_seq_device joydev snd_timer drm serio_raw snd ie31200_edac mei_me soundcore mei i2c_algo_bit lpc_ich shpchp edac_core ideapad_laptop soc_button_array sparse_keymap wmi video mac_hid parport_pc ppdev lp [16066.244230] parport autofs4 uas usb_storage ahci psmouse alx libahci mdio [16066.244240] CPU: 0 PID: 0 Comm: swapper/0 Tainted: GW OE 3.19.0-18-generic #18-Ubuntu [16066.244242] Hardware name: LENOVO 20250/Durian 7A1, BIOS 7FCN95WW 04/29/2014 [16066.244243] c065dde8 88035f203d28 817c27cd 0007 [16066.244245] 88035f203d78 88035f203d68 8107593a 88035f203d88 [16066.244247] 880350a94000 88034cdfd000 88034cdfd1a8 [16066.244249] Call Trace: [16066.244251][] dump_stack+0x45/0x57 [16066.244267] [] warn_slowpath_common+0x8a/0xc0 [16066.244269] [] warn_slowpath_fmt+0x46/0x50 [16066.244288] [] intel_check_page_flip+0xda/0xf0 [i915] [16066.244306] [] ironlake_irq_handler+0x2e8/0xfd0 [i915] [16066.244314] [] ? rebalance_domains+0xe0/0x280 [16066.244322] [] handle_irq_event_percpu+0x77/0x1a0 [16066.244324] [] handle_irq_event+0x41/0x70 [16066.244328] [] handle_edge_irq+0x6e/0x120 [16066.244331] [] handle_irq+0x22/0x40 [16066.244334] [] do_IRQ+0x4f/0xf0 [16066.244336] [] common_interrupt+0x6d/0x6d [16066.244337][] ? cpuidle_enter_state+0x65/0x160 [16066.244341] [] ? cpuidle_enter_state+0x51/0x160 [16066.244343] [] cpuidle_enter+0x17/0x20 [16066.244345] [] cpu_startup_entry+0x311/0x3b0 [16066.244349] [] rest_init+0x77/0x80 [16066.244354] [] start_kernel+0x482/0x48f [16066.244356] [] ? early_idt_handlers+0x120/0x120 [16066.244358] [] x86_64_start_reservations+0x2a/0x2c [16066.244360] [] x86_64_start_kernel+0x143/0x152 [16066.244361] ---[ end trace 5d72b504d95d3a93 ]--- ** Affects: linux (Ubuntu) Importance: Low Status: Incomplete -- intel driver keeps crashing after suspend https://bugs.launchpad.net/bugs/1462728 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1456531] [NEW] LightDM (?) blank/white screen after resume from suspend
You have been subscribed to a public bug: On Xubuntu 15.04, when I suspend the machine and resume afterwards, the screen remains completely white/blank. I can move the mouse cursor, but I don't see any screen elements. Clicking or wildly pressing keys doesn't do anything. I can switch to a different console with Ctrl+Alt+F1 and log in, just fine. For this bug report, I have removed all files from /var/log/lightdm, then rebooted, suspended, resumed, and switched to VT1. Then copied the /var/log/lightdm files to a different location. See their contents attached to this bug report. Other parameters: - Simply locking and unlocking the screen works, ALTHOUGH I also see the white screen there at first, and have to click a mouse button for the login form to show up. - I'm running a system with a fully encrypted hard-drive and have configured LightDM to log me in automatically. - System is up-to-date. - No experimental packages, although I had an experimental version of xserver-xorg-video-intel running, but removed it shortly after. - System is a Thinkpad T450s with Intel HD 5500 graphics. Hope I didn't forget to mention anything important. If you need more information or want me to try something, let me know. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed -- LightDM (?) blank/white screen after resume from suspend https://bugs.launchpad.net/bugs/1456531 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1210748] Re: On Lenovo Thinkpad Twist internal mouse does not work after turning on machine, only works after reboot
Yes, link isn't working and I am having the same issue. Recently updated BIOS to 1.70. Please and thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1210748 Title: On Lenovo Thinkpad Twist internal mouse does not work after turning on machine, only works after reboot Status in linux package in Ubuntu: Invalid Bug description: I have a Lenovo ThinkPad Twist (convertible ultrabook with Core i7 processor) with touch screen, touch pad, rubber nipple mouse, and external Bluetooth mouse. From these 4 mice 2 always work, the touch screen and the external Bluetooth mouse. The touchpad and the nipple do not work right after turning on the machine, only when I reboot the machine they work after rebooting. I have observed the problem only recently, so it is perhaps triggered by the BIOS upgrade to version 1.57. The problem is independent of the Ubuntu version. I did not only observe it on the installed Raring and Saucy systems but also with several live CDs of older Ubuntu versions (Quantal, Precise). There is also another user with the same problem. See http://www.iasptk.com/ubuntuwp/tag/13-10/ and search for "twist". Unfortunately, the question got removed from Ask Ubuntu, but one can still access the dmesg output from this user on http://paste.ubuntu.com/5889489/ --- ApportVersion: 2.12-0ubuntu3 Architecture: amd64 DistroRelease: Ubuntu 13.10 InstallationDate: Installed on 2013-06-05 (65 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130605) MarkForUpload: True Package: linux (not installed) Tags: saucy Uname: Linux 3.11.0-031100rc3-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo --- ApportVersion: 2.12-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: till 2756 F pulseaudio DistroRelease: Ubuntu 13.10 HibernationDevice: RESUME=UUID=e0af6e5c-3cf3-47e2-8603-6a9ffb019484 InstallationDate: Installed on 2013-06-05 (65 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130605) MachineType: LENOVO 334729G MarkForUpload: True Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.10.0-6-generic root=UUID=71da60b2-cc11-47bf-9120-bfad5b1c7eaa ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3 RelatedPackageVersions: linux-restricted-modules-3.10.0-6-generic N/A linux-backports-modules-3.10.0-6-generic N/A linux-firmware1.113 Tags: saucy Uname: Linux 3.10.0-6-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 07/01/2013 dmi.bios.vendor: LENOVO dmi.bios.version: GDET97WW (1.57 ) dmi.board.asset.tag: Not Available dmi.board.name: 334729G dmi.board.vendor: LENOVO dmi.board.version: Win8 Pro DPK TPG dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGDET97WW(1.57):bd07/01/2013:svnLENOVO:pn334729G:pvrThinkPadTwist:rvnLENOVO:rn334729G:rvrWin8ProDPKTPG:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 334729G dmi.product.version: ThinkPad Twist dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1210748/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1495116] Re: booting with amd64 kernel and completely i386 userland is unstable during the system upstart
I'll have to see whether there some updates fro my BIOS available. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1495116 Title: booting with amd64 kernel and completely i386 userland is unstable during the system upstart Status in linux package in Ubuntu: Confirmed Bug description: I wanted to run my 14.10 (Utopic) i386 system with the amd64 kernel, so I added that architecture and apt-get-installed the amd64 linux- image and linux-image-extra (I learned this was possible thanks to the advice at http://askubuntu.com/a/635774/19753 ). However, the system upstart procedure more often fails than not: it fails by rebooting the computer. (Only around 1 time of 4 is successful.) A limited system start is (probably, always) successful: either with init=/bin/bash parameter to the kernel, or choosing the recovery boot option. (However, if I "resume" from the recovery menu, or run "exec init" in bash, then the upstart procedure is similarly unstable: it usually fails/crashes and reboots.) I checked my suspection that the video driver (nouveau) and X might be involved, but that turned out not true: the upstart procedure is similarly unstable with "nomodesetting" kernel parameter and without, booting into runlevel 3 or the default one. Perhaps, I'd like to debug the upstart procedure step-by-step to detect which step makes the system crash and reboot, but I don't know how. As concerns the timing, the moment the reboot happens can be different: it can happen rather early (when I see the message about activating the swap) or much later. If the system upstart procedure has completed successfully, then it works in a quite stable manner and doesn't crash/reboot. So, there is something bad specifically during the system upstart procedure. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: upstart 1.13.2-0ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-44.59-generic 3.16.7-ckt14 Uname: Linux 3.16.0-44-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.5 Architecture: i386 CurrentDesktop: Unity Date: Sat Sep 12 18:36:28 2015 InstallationDate: Installed on 2014-06-04 (464 days ago) InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 (20140204) ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash SourcePackage: upstart UpgradeStatus: Upgraded to utopic on 2015-09-11 (0 days ago) UpstartBugCategory: System UpstartRunningSessionVersion: upstart 1.13.2 UpstartRunningSystemVersion: init (upstart 1.13.2) modified.conffile..etc.at.deny: [inaccessible: [Errno 13] Отказано в доступе: '/etc/at.deny'] modified.conffile..etc.cron.daily.upstart: [modified] modified.conffile..etc.cups.cups.browsed.conf: [modified] modified.conffile..etc.default.apport: [modified] modified.conffile..etc.default.cups: [modified] modified.conffile..etc.init.d.binfmt.support: [modified] mtime.conffile..etc.X11.Xsession.d.99upstart: 2014-09-30T12:21:08 mtime.conffile..etc.cron.daily.upstart: 2014-09-30T12:27:13 mtime.conffile..etc.cups.cups.browsed.conf: 2015-09-06T09:29:16.410097 mtime.conffile..etc.default.apport: 2014-06-05T12:49:10.316398 mtime.conffile..etc.default.cups: 2015-09-06T09:20:49.891585 mtime.conffile..etc.init.d.binfmt.support: 2014-09-30T12:21:08 mtime.conffile..etc.upstart.xsessions: 2014-09-30T12:21:08 --- ApportVersion: 2.14.7-0ubuntu8.5 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: marsmorgana 1972 F pulseaudio CRDA: country RU: DFS-UNSET (2402 - 2482 @ 40), (N/A, 20) (5735 - 5835 @ 20), (N/A, 30) CurrentDesktop: Unity DistroRelease: Ubuntu 14.10 HibernationDevice: RESUME=UUID=9267c811-3a01-4484-b968-c08582280d81 InstallationDate: Installed on 2014-06-04 (464 days ago) InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 (20140204) MachineType: SAMSUNG ELECTRONICS CO., LTD. R510/P510 Package: upstart 1.13.2-0ubuntu2 PackageArchitecture: i386 ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash ProcVersionSignature: Ubuntu 3.16.0-44.59-generic 3.16.7-ckt14 RelatedPackageVersions: linux-restricted-modules-3.16.0-44-generic N/A linux-backports-modules-3.16.0-44-generic N/A linux-firmware 1.138.1 Tags: utopic utopic third-party-packages Uname: Linux 3.16.0-44-generic x86_64 UpgradeStatus: Upgraded to utopic on 2015-09-11 (0 days ago) UpstartBugCategory: System UpstartRunningSessionVersion: upstart 1.13.2 UpstartRunningSystemVersion: init (upstar
[Kernel-packages] [Bug 1500246] [NEW] modemmanager fails to configure during upgrade from 15.04 to 15.10
Public bug reported: It appears that the upgrade will refuse to continue. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: crash (not installed) ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5 Uname: Linux 3.19.0-28-generic x86_64 ApportVersion: 2.19-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sun Sep 27 14:17:16 2015 InstallationDate: Installed on 2015-07-25 (64 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: crash UpgradeStatus: Upgraded to wily on 2015-09-27 (0 days ago) ** Affects: crash (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug wily -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to crash in Ubuntu. https://bugs.launchpad.net/bugs/1500246 Title: modemmanager fails to configure during upgrade from 15.04 to 15.10 Status in crash package in Ubuntu: New Bug description: It appears that the upgrade will refuse to continue. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: crash (not installed) ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5 Uname: Linux 3.19.0-28-generic x86_64 ApportVersion: 2.19-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sun Sep 27 14:17:16 2015 InstallationDate: Installed on 2015-07-25 (64 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: crash UpgradeStatus: Upgraded to wily on 2015-09-27 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1500246/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1495116] Re: booting with amd64 kernel and completely i386 userland is unstable during the system upstart
The same CPU means: Intel P7350. Other found links (under the title "join club"): http://ubuntuforums.org/showthread.php?t=1137153 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1495116 Title: booting with amd64 kernel and completely i386 userland is unstable during the system upstart Status in linux package in Ubuntu: Confirmed Bug description: I wanted to run my 14.10 (Utopic) i386 system with the amd64 kernel, so I added that architecture and apt-get-installed the amd64 linux- image and linux-image-extra (I learned this was possible thanks to the advice at http://askubuntu.com/a/635774/19753 ). However, the system upstart procedure more often fails than not: it fails by rebooting the computer. (Only around 1 time of 4 is successful.) A limited system start is (probably, always) successful: either with init=/bin/bash parameter to the kernel, or choosing the recovery boot option. (However, if I "resume" from the recovery menu, or run "exec init" in bash, then the upstart procedure is similarly unstable: it usually fails/crashes and reboots.) I checked my suspection that the video driver (nouveau) and X might be involved, but that turned out not true: the upstart procedure is similarly unstable with "nomodesetting" kernel parameter and without, booting into runlevel 3 or the default one. Perhaps, I'd like to debug the upstart procedure step-by-step to detect which step makes the system crash and reboot, but I don't know how. As concerns the timing, the moment the reboot happens can be different: it can happen rather early (when I see the message about activating the swap) or much later. If the system upstart procedure has completed successfully, then it works in a quite stable manner and doesn't crash/reboot. So, there is something bad specifically during the system upstart procedure. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: upstart 1.13.2-0ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-44.59-generic 3.16.7-ckt14 Uname: Linux 3.16.0-44-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.5 Architecture: i386 CurrentDesktop: Unity Date: Sat Sep 12 18:36:28 2015 InstallationDate: Installed on 2014-06-04 (464 days ago) InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 (20140204) ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash SourcePackage: upstart UpgradeStatus: Upgraded to utopic on 2015-09-11 (0 days ago) UpstartBugCategory: System UpstartRunningSessionVersion: upstart 1.13.2 UpstartRunningSystemVersion: init (upstart 1.13.2) modified.conffile..etc.at.deny: [inaccessible: [Errno 13] Отказано в доступе: '/etc/at.deny'] modified.conffile..etc.cron.daily.upstart: [modified] modified.conffile..etc.cups.cups.browsed.conf: [modified] modified.conffile..etc.default.apport: [modified] modified.conffile..etc.default.cups: [modified] modified.conffile..etc.init.d.binfmt.support: [modified] mtime.conffile..etc.X11.Xsession.d.99upstart: 2014-09-30T12:21:08 mtime.conffile..etc.cron.daily.upstart: 2014-09-30T12:27:13 mtime.conffile..etc.cups.cups.browsed.conf: 2015-09-06T09:29:16.410097 mtime.conffile..etc.default.apport: 2014-06-05T12:49:10.316398 mtime.conffile..etc.default.cups: 2015-09-06T09:20:49.891585 mtime.conffile..etc.init.d.binfmt.support: 2014-09-30T12:21:08 mtime.conffile..etc.upstart.xsessions: 2014-09-30T12:21:08 --- ApportVersion: 2.14.7-0ubuntu8.5 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: marsmorgana 1972 F pulseaudio CRDA: country RU: DFS-UNSET (2402 - 2482 @ 40), (N/A, 20) (5735 - 5835 @ 20), (N/A, 30) CurrentDesktop: Unity DistroRelease: Ubuntu 14.10 HibernationDevice: RESUME=UUID=9267c811-3a01-4484-b968-c08582280d81 InstallationDate: Installed on 2014-06-04 (464 days ago) InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 (20140204) MachineType: SAMSUNG ELECTRONICS CO., LTD. R510/P510 Package: upstart 1.13.2-0ubuntu2 PackageArchitecture: i386 ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash ProcVersionSignature: Ubuntu 3.16.0-44.59-generic 3.16.7-ckt14 RelatedPackageVersions: linux-restricted-modules-3.16.0-44-generic N/A linux-backports-modules-3.16.0-44-generic N/A linux-firmware 1.138.1 Tags: utopic utopic third-party-packages Uname: Linux 3.16.0-44-generic x86_64 UpgradeStatus: Upgraded to utopic on 2015-09-11 (0 days ago) UpstartBugCategory: System UpstartRunningSessionV
[Kernel-packages] [Bug 1500242] [NEW] Bluetooth device (Jabra BT250, Audi A3 car kit) can not be connected with BQ Aquaris 4.5
Public bug reported: STEPS: Requirements: Aquaris E4.5, Jabra BT250 blue tooth handset device (rather old one supports blue tooth 1.1 and therefore I thought should be no issue) or Audi car kit (A3 2012 model) 1. Put Jabra BT250 into receiving mode 2. Phone searches automatically every 15 - 30 seconds for a new blue tooth device 3. Phone finds Jabra BT250 and asks for pairing code 4. Enter code into phone 5. Jabra BT250 automatically exits the pairing mode (which is a sign that pairing should have worked) 6. Phone looses connection to Jabra BT250 7. Manual reconnection via phone works (shows Jabra BT250 as being connected) but ignores the device Same behaviour with Audi car kit (Audi A3, 2012 model) EXPECTED: I expect that the blue tooth kits work similar to my Seat Alhambra (also 2012 model) where the blue tooth pairing etc. works great (except some bugs which are already filed). ACTUAL: No connection to the blue tooth device VERSIONS: OS-Build-Number: 25 Ubuntu-Image: 20150825.1 POSSIBLE ROOT CAUSE: Is this issue also solved as soon as bluez5 is implemented? When will this be? ** Affects: bluez (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1500242 Title: Bluetooth device (Jabra BT250, Audi A3 car kit) can not be connected with BQ Aquaris 4.5 Status in bluez package in Ubuntu: New Bug description: STEPS: Requirements: Aquaris E4.5, Jabra BT250 blue tooth handset device (rather old one supports blue tooth 1.1 and therefore I thought should be no issue) or Audi car kit (A3 2012 model) 1. Put Jabra BT250 into receiving mode 2. Phone searches automatically every 15 - 30 seconds for a new blue tooth device 3. Phone finds Jabra BT250 and asks for pairing code 4. Enter code into phone 5. Jabra BT250 automatically exits the pairing mode (which is a sign that pairing should have worked) 6. Phone looses connection to Jabra BT250 7. Manual reconnection via phone works (shows Jabra BT250 as being connected) but ignores the device Same behaviour with Audi car kit (Audi A3, 2012 model) EXPECTED: I expect that the blue tooth kits work similar to my Seat Alhambra (also 2012 model) where the blue tooth pairing etc. works great (except some bugs which are already filed). ACTUAL: No connection to the blue tooth device VERSIONS: OS-Build-Number: 25 Ubuntu-Image: 20150825.1 POSSIBLE ROOT CAUSE: Is this issue also solved as soon as bluez5 is implemented? When will this be? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1500242/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1500156] Re: r592 IRQ: DMA errors cause log files to grow *HUGE*
Launchpad has imported 24 comments from the remote bug at https://bugzilla.novell.com/show_bug.cgi?id=892249. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2014-08-16T13:45:45+00:00 gldickens3 wrote: User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Firefox/31.0 I am seeing this problem on OpenSUSE with kernel-desktop versions 3.15.6 (stable repo) and 3.16.0 (HEAD repo). The log files on my laptop, /var/log/messages and /var/log/warn, will grow HUGE with the following repeated over and over along with some extraneous related log entries: 2014-08-15T12:18:41.396981-04:00 localhost kernel: [17310.691176] r592: IRQ: card added 2014-08-15T12:18:41.396983-04:00 localhost kernel: [17310.691178] r592: IRQ: DMA error . . 2014-08-15T12:18:41.397001-04:00 localhost kernel: [17311.223846] r592: IRQ: card added 2014-08-15T12:18:41.397004-04:00 localhost kernel: [17311.223847] r592: IRQ: DMA error On any given day, there will be tens of thousands of these entries such that /var/log/messages and /var/log/warn will both exceed 3GB within a day (over 6GB total). I believe that this bug is generated due to the presence of a Ricoh R5C592 Memory Stick Adapter on my laptop and which has never been properly recognized by the stock linux kernels. Apparently, the kernel developers keep trying to make it work but have now introduced a "bigger" problem so to speak since it is now causing all these extraneous error messages to be generated in the logs. I am seeing this bug on OpenSUSE with kernel-desktop versions 3.15.6 and 3.16.0. This bug does not appear to be present in the OpenSUSE stock 3.11.6 and 3.11.10 kernels. I have since reverted back to the earlier kernels that don't have this problem. This bug has also been reported at Red Hat's bugzilla at: https://bugzilla.redhat.com/show_bug.cgi?id=1119361 IMHO, this bug needs to be fixed prior to the release of OpenSUSE 13.2. FYI, Gordon Reproducible: Always Steps to Reproduce: 1. Boot 2. Wait a while. It sometimes takes an hour or two for the log errors to begin at top volume. Actual Results: Logs grow *HUGE* with r592IRQ: DMA errors and related entries. Expected Results: Logger should not produce error messages of this magnitude and size. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1500156/comments/0 On 2014-08-22T16:02:20+00:00 Tiwai-r wrote: Since it's endless irq wakeups, here is a blind shot: could you check whether the patch below works? Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1500156/comments/1 On 2014-08-22T16:02:49+00:00 Tiwai-r wrote: Created attachment 603338 Test patch Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1500156/comments/2 On 2014-08-27T17:19:05+00:00 gldickens3 wrote: I am not a kernel developer and so I'm not sure how to build r592.c with the patch, however, I would be happy to test it if somebody else would build it for me. Alternatively, if its simple to do, then please provide some instructions and I will attempt to build it. Also, the following is from a post at: https://forums.opensuse.org/showthread.php/494706-openSUSE-13-1-KDE- inconsistant-resume-from-Suspend-to-RAM?p=2661131#post2661131 Quoting Romanator: "The most recent openSUSE kernel (3.11.10-21-desktop) Makefile for the r592.c from Maxim Levitsky is from 2010. His final patch wasn't submitted until Jan. 8, 2011. Ask the openSUSE kernel devs to look at and backport patch #5b945a6 from this link: https://gitorious.org/ricoh-kernel/ricoh-kernel.git ". So, it doesn't look like the OpenSUSE kernel has the most recent r592 driver... Also, there is a good bit of recent activity by the r592 developer, Maxim Levitsky, on this exact same bug at Red Hat's Bugzilla site here: https://bugzilla.redhat.com/show_bug.cgi?id=1119361 The bottom line is that someone needs to make sure that OpenSUSE is using the most recent version of r592.c. FYI, Gordon Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1500156/comments/3 On 2014-08-27T17:27:50+00:00 gldickens3 wrote: The ricoh-kernel project is maintained here: https://gitorious.org/ricoh-kernel/ricoh- kernel/source/33138f5085346e1000bcab7ef83e2c88a200b6ec: Also, there is a more recent (March 31, 2011) r592.c patch here: https://gitorious.org/ricoh-kernel/ricoh- kernel/commit/33138f5085346e1000bcab7ef83e2c88a200b6ec FYI, Gordon Reply at: https://bugs.launchpad.net/ubuntu/+source/l
[Kernel-packages] [Bug 1283003] Re: [Bluetooth + 14.04] Bluetooth headsets are not working after last couple of updates
Currently, on Lubuntu Trusty, I have no problems with Skullcandy Hesh 2 and: * kernel 3.13.0-63-generic #103 * pulseaudio 1:4.0-0ubuntu11.1+kxstudio1 (I did not test with the standard Canonical version, sorry) * bluez 4.101-0ubuntu13.1 * blueman 1.23-git201403102151-1ubuntu though I will note it's not always as seamless as I would like. I've discovered elsewhere people suggesting that the adapter is turned on after pulse does its check for bluetooth adapters. That leaves you two choices: 1. pactl load-module module-bluetooth-discover && pulseaudio -k (note actually sending a KILL signal to the daemon may get it unstuck if it's not behaving) 2. remove the conditional from /etc/pulse/default.pa regarding loading module-bluetooth-discover neither of which are particularly elegant, but oh well. This and similar issues are ultimately an aesthetic issue, though, and deserve a separate bug report, as this more general one has brown extensive enough. From my experience, audio sink service (A2DP) *IS* possible with current versions. I'm inclined to call this fixed, unless I hear otherwise from folks. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1283003 Title: [Bluetooth + 14.04] Bluetooth headsets are not working after last couple of updates Status in Blueman: New Status in blueman package in Ubuntu: Fix Released Status in bluez package in Ubuntu: Confirmed Status in gnome-bluetooth package in Ubuntu: Confirmed Bug description: Hi, I found a bug in Ubuntu 14.04 ! I tried to pair a bluetooth stereo headset (A2DP compatible). The pairing process goes well, but after that I can't select it on the audio preferences. When I select it, it only shows the last selected item options and don't do anything. (he should switch to the headset output). I must mention that it worked very well on Ubuntu 12.04. This bug can be in the bluetooth stack or in unity-control-center or maybe pulseaudio. I actually have no idea. To manage notifications about this bug go to: https://bugs.launchpad.net/blueman/+bug/1283003/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1495116] Re: booting with amd64 kernel and completely i386 userland is unstable during the system upstart
Similar random reboots with a amd64 kernel in the cases with the same CPU were reported (quite a long ago,for Ubuntu 9.04) there: http://ubuntuforums.org/showthread.php?t=1137153 They also say that some other distros also had this problem (e.g.,Gentoo), but there were successful boots of some Knoppix and Mint distros. That discussion is of course about a completely amd64 system, not like in my experiment (amd64 kernel + i386 userland). So, it well might be a problem notrelated to my experimental mixof amd64 and i386. I wonder whether there has been found a workaround ever since. (In my case, it's that simple: if the bootup succeeds, there are no more problems/reboots for hours and even days.) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1495116 Title: booting with amd64 kernel and completely i386 userland is unstable during the system upstart Status in linux package in Ubuntu: Confirmed Bug description: I wanted to run my 14.10 (Utopic) i386 system with the amd64 kernel, so I added that architecture and apt-get-installed the amd64 linux- image and linux-image-extra (I learned this was possible thanks to the advice at http://askubuntu.com/a/635774/19753 ). However, the system upstart procedure more often fails than not: it fails by rebooting the computer. (Only around 1 time of 4 is successful.) A limited system start is (probably, always) successful: either with init=/bin/bash parameter to the kernel, or choosing the recovery boot option. (However, if I "resume" from the recovery menu, or run "exec init" in bash, then the upstart procedure is similarly unstable: it usually fails/crashes and reboots.) I checked my suspection that the video driver (nouveau) and X might be involved, but that turned out not true: the upstart procedure is similarly unstable with "nomodesetting" kernel parameter and without, booting into runlevel 3 or the default one. Perhaps, I'd like to debug the upstart procedure step-by-step to detect which step makes the system crash and reboot, but I don't know how. As concerns the timing, the moment the reboot happens can be different: it can happen rather early (when I see the message about activating the swap) or much later. If the system upstart procedure has completed successfully, then it works in a quite stable manner and doesn't crash/reboot. So, there is something bad specifically during the system upstart procedure. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: upstart 1.13.2-0ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-44.59-generic 3.16.7-ckt14 Uname: Linux 3.16.0-44-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.5 Architecture: i386 CurrentDesktop: Unity Date: Sat Sep 12 18:36:28 2015 InstallationDate: Installed on 2014-06-04 (464 days ago) InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 (20140204) ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosplash SourcePackage: upstart UpgradeStatus: Upgraded to utopic on 2015-09-11 (0 days ago) UpstartBugCategory: System UpstartRunningSessionVersion: upstart 1.13.2 UpstartRunningSystemVersion: init (upstart 1.13.2) modified.conffile..etc.at.deny: [inaccessible: [Errno 13] Отказано в доступе: '/etc/at.deny'] modified.conffile..etc.cron.daily.upstart: [modified] modified.conffile..etc.cups.cups.browsed.conf: [modified] modified.conffile..etc.default.apport: [modified] modified.conffile..etc.default.cups: [modified] modified.conffile..etc.init.d.binfmt.support: [modified] mtime.conffile..etc.X11.Xsession.d.99upstart: 2014-09-30T12:21:08 mtime.conffile..etc.cron.daily.upstart: 2014-09-30T12:27:13 mtime.conffile..etc.cups.cups.browsed.conf: 2015-09-06T09:29:16.410097 mtime.conffile..etc.default.apport: 2014-06-05T12:49:10.316398 mtime.conffile..etc.default.cups: 2015-09-06T09:20:49.891585 mtime.conffile..etc.init.d.binfmt.support: 2014-09-30T12:21:08 mtime.conffile..etc.upstart.xsessions: 2014-09-30T12:21:08 --- ApportVersion: 2.14.7-0ubuntu8.5 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: marsmorgana 1972 F pulseaudio CRDA: country RU: DFS-UNSET (2402 - 2482 @ 40), (N/A, 20) (5735 - 5835 @ 20), (N/A, 30) CurrentDesktop: Unity DistroRelease: Ubuntu 14.10 HibernationDevice: RESUME=UUID=9267c811-3a01-4484-b968-c08582280d81 InstallationDate: Installed on 2014-06-04 (464 days ago) InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 (20140204) MachineType: SAMSUNG ELECTRONICS CO., LTD. R510/P510 Package: upstart 1.13.2-0ubuntu2 PackageArchitecture: i386 ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic root=UUID=980299a2-fde5-4f39-acb0-189f528b8485 ro nosp
[Kernel-packages] [Bug 1499491] Re: Display connected on DisplayPort turns black during boot and never returns
Olivier Caro, via SSH? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1499491 Title: Display connected on DisplayPort turns black during boot and never returns Status in linux package in Ubuntu: Incomplete Bug description: The display connected on my R9 290 through DisplayPort connection turns black during boot and never comes back again. According to the power led, it is up and does not turn into power saving mode. According to xorg.0.log and System Settings / Display the display is perfectly detected. This display worked perfectly fine using the same DisplayPort cable, running the same driver on my Radeon HD 6670. Description: Ubuntu 15.04 Release: 15.04 --- ApportVersion: 2.17.2-0ubuntu1.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: olivier2403 F pulseaudio /dev/snd/controlC2: olivier2403 F pulseaudio /dev/snd/controlC1: olivier2403 F pulseaudio /dev/snd/seq:timidity 1672 F timidity DistroRelease: Ubuntu 15.04 EcryptfsInUse: Yes IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: To be filled by O.E.M. To be filled by O.E.M. Package: linux (not installed) ProcFB: 0 radeondrmfb 1 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-30-generic root=/dev/mapper/vg0-root ro radeon.auxch=0 init=/lib/systemd/systemd-bootchart ProcVersionSignature: Ubuntu 3.19.0-30.33-generic 3.19.8-ckt6 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.19.0-30-generic N/A linux-backports-modules-3.19.0-30-generic N/A linux-firmware 1.143.3 RfKill: Tags: vivid Uname: Linux 3.19.0-30-generic x86_64 UpgradeStatus: Upgraded to vivid on 2015-04-30 (149 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 04/09/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2501 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M5A97 LE R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2501:bd04/09/2014:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97LER2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1499491/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1484159] Re: Qualcomm Atheros Device [168c:0042] (rev 30) not working on Ubuntu
I am also seeing this. 03:00.0 Network controller [0280]: Qualcomm Atheros Device [168c:0042] (rev 30) Subsystem: Foxconn International, Inc. Device [105b:e09a] Same machine - Acer Aspire E5-573 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1484159 Title: Qualcomm Atheros Device [168c:0042] (rev 30) not working on Ubuntu Status in linux package in Ubuntu: Triaged Bug description: Hi, Qualcomm Atheros Device [168c:0042] (rev 30) is not supported by linux kernal. Please add support. Thanks ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-61-generic 3.13.0-61.100 ProcVersionSignature: Ubuntu 3.13.0-61.100-generic 3.13.11-ckt22 Uname: Linux 3.13.0-61-generic i686 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu14 1658 F pulseaudio /dev/snd/controlC1: ubuntu14 1658 F pulseaudio CurrentDesktop: Unity Date: Wed Aug 12 20:31:24 2015 HibernationDevice: RESUME=UUID=0483444a-0d9a-4215-b36b-4aee75fd9ec0 InstallationDate: Installed on 2015-08-11 (0 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140722.2) IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: Acer Aspire E5-573 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-61-generic root=UUID=72a8a100-d5ec-4e9d-8bc5-45695001a29c ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-61-generic N/A linux-backports-modules-3.13.0-61-generic N/A linux-firmware 1.127.15 SourcePackage: linux StagingDrivers: rts5139 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/20/2015 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.11 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: ZORO_BH dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.11:bd04/20/2015:svnAcer:pnAspireE5-573:pvrV3.72:rvnAcer:rnZORO_BH:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Aspire E5-573 dmi.product.version: V3.72 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1484159/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1499491] Re: Display connected on DisplayPort turns black during boot and never returns
I already had removed quiet and splash keywords from my grub configuration. Grub option : "gfxmode text" did not help (no change). I am not sure I can provide the missing debug information for now. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1499491 Title: Display connected on DisplayPort turns black during boot and never returns Status in linux package in Ubuntu: Incomplete Bug description: The display connected on my R9 290 through DisplayPort connection turns black during boot and never comes back again. According to the power led, it is up and does not turn into power saving mode. According to xorg.0.log and System Settings / Display the display is perfectly detected. This display worked perfectly fine using the same DisplayPort cable, running the same driver on my Radeon HD 6670. Description: Ubuntu 15.04 Release: 15.04 --- ApportVersion: 2.17.2-0ubuntu1.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: olivier2403 F pulseaudio /dev/snd/controlC2: olivier2403 F pulseaudio /dev/snd/controlC1: olivier2403 F pulseaudio /dev/snd/seq:timidity 1672 F timidity DistroRelease: Ubuntu 15.04 EcryptfsInUse: Yes IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: To be filled by O.E.M. To be filled by O.E.M. Package: linux (not installed) ProcFB: 0 radeondrmfb 1 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-30-generic root=/dev/mapper/vg0-root ro radeon.auxch=0 init=/lib/systemd/systemd-bootchart ProcVersionSignature: Ubuntu 3.19.0-30.33-generic 3.19.8-ckt6 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.19.0-30-generic N/A linux-backports-modules-3.19.0-30-generic N/A linux-firmware 1.143.3 RfKill: Tags: vivid Uname: Linux 3.19.0-30-generic x86_64 UpgradeStatus: Upgraded to vivid on 2015-04-30 (149 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 04/09/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2501 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M5A97 LE R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2501:bd04/09/2014:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97LER2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1499491/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1500156] Re: r592 IRQ: DMA errors cause log files to grow *HUGE*
** Bug watch added: Novell/SUSE Bugzilla #892249 https://bugzilla.novell.com/show_bug.cgi?id=892249 ** Also affects: opensuse via https://bugzilla.novell.com/show_bug.cgi?id=892249 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1500156 Title: r592 IRQ: DMA errors cause log files to grow *HUGE* Status in linux package in Ubuntu: Confirmed Status in openSUSE: Unknown Bug description: Hi, Since some recent time, my log files (syslog & kern.log) grow huge, making the computer unusable when it performs logrotate operations. Having a look to that, I see it contains many many lines : Sep 27 09:50:44 mmb-laptop kernel: [42839.496635] r592: IRQ: DMA error Sep 27 09:50:44 mmb-laptop kernel: [42839.599027] r592: IRQ: card added It seems related to this device : Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter (rev 12) I do not use it and I do not need it for now. I am using Ubuntu 15.04 with latest updates (as of 27-sep-2015), kernel 3.19.0-28-generic #30-Ubuntu on x86_64. I've read some posts/other bug reports related to the same issue : http://lists.opensuse.org/opensuse-bugs/2014-08/msg01076.html https://bugzilla.redhat.com/show_bug.cgi?id=1119361 https://forum.ubuntu-fr.org/viewtopic.php?id=1907131&p=1 https://bugzilla.novell.com/show_bug.cgi?id=892249 I would be glad if some solution is proposed to stop filling these logs ! Cheers, Laurent --- ApportVersion: 2.17.2-0ubuntu1.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lmartinb 1656 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 15.04 HibernationDevice: RESUME=UUID=6512e903-d5d3-4c2e-90b4-45ed0610fcd5 InstallationDate: Installed on 2014-07-29 (424 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) JournalErrors: Error: command ['journalctl', '-b', '--priority', 'warning'] failed with exit code 1: -- Logs begin at dim. 2015-09-27 14:32:35 CEST, end at dim. 2015-09-27 14:49:34 CEST. -- MachineType: ASUSTeK Computer Inc. M50Vc NonfreeKernelModules: nvidia Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-28-generic root=UUID=c05406a2-6b6b-4c79-aa26-51af9aa16cb1 ro quiet splash ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5 RelatedPackageVersions: linux-restricted-modules-3.19.0-28-generic N/A linux-backports-modules-3.19.0-28-generic N/A linux-firmware 1.143.3 Tags: vivid Uname: Linux 3.19.0-28-generic x86_64 UpgradeStatus: Upgraded to vivid on 2015-08-30 (27 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/14/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 212 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: M50Vc dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr212:bd10/14/2009:svnASUSTeKComputerInc.:pnM50Vc:pvr1.0:rvnASUSTeKComputerInc.:rnM50Vc:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: M50Vc dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1500156/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1490143] Re: When resuming after suspension desktop is freezed
Carla Sella, any change with the latest mainline kernel (4.3-rc3)? ** Tags removed: bios-outdated-0808 ** Tags added: latest-bios-0808 ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1490143 Title: When resuming after suspension desktop is freezed Status in linux package in Ubuntu: Incomplete Bug description: I suspended my PC for like about 1,5 - 2 hours and when I resumed the desktop had a black background, you could see the launcher bat you were unable to do anything it was freezed. This is my hardware: https://gist.github.com/anonymous/3203c7c5a43a509c0f22. I am attaching the screen-shots of my desktop after resuming, also in terminal (CTRL+ALT+F1) it looked rather garbled. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3 Uname: Linux 4.1.0-3-generic x86_64 ApportVersion: 2.18-0ubuntu7 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Sat Aug 29 13:57:20 2015 DistUpgraded: Fresh install DistroCodename: wily DistroVariant: ubuntu DkmsStatus: virtualbox, 5.0.2, 4.1.0-3-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation G84GL [Quadro FX 370] [10de:040a] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation Device [10de:0491] InstallationDate: Installed on 2015-08-16 (12 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150816) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.1.0-3-generic root=UUID=4b5d483e-4c0c-4013-b27c-0684b9343728 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/13/2007 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0803 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M2N dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0803:bd09/13/2007:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2N:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.12.1+15.10.20150805-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.6.3-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.6.3-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0+git20150819-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3 xserver.bootTime: Sat Aug 29 11:08:42 2015 xserver.configfile: default xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) NOUVEAU(0): [COPY] failed to allocate class. xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.17.2-1ubuntu3 xserver.video_driver: nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1490143/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1408593] Re: X server disables acceleration or turns off output (makes screen black) after kernel upgrade to v3.18 (Ubuntu Vivid)
Wladimir Mutel, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1408593/comments/36 regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find. ** No longer affects: xserver-xorg-video-intel (Ubuntu) ** Changed in: linux (Ubuntu) Status: Fix Committed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1408593 Title: X server disables acceleration or turns off output (makes screen black) after kernel upgrade to v3.18 (Ubuntu Vivid) Status in linux package in Ubuntu: Invalid Bug description: after reboot into kernel 3.18 (3.18.0-8.9) with Intel driver version 2:2.99.916+git20141119-1~exp1ubuntu1 it disables output / blacks the screen and puts in the log : [37.179] (II) GLX: Initialized DRI2 GL provider for screen 0 [37.215] (WW) intel(0): Failed to submit rendering commands, trying again with outputs disabled. (then refuses to switch local VTs both by [Ctrl-]Alt-Fn and by chvt in remote logins) after reverting to 2:2.99.914-1~exp1ubuntu6 it puts : [41.679] (II) GLX: Initialized DRI2 GL provider for screen 0 [41.711] (EE) intel(0): Failed to submit rendering commands, disabling acceleration. (then allows to log in bu with desktop composition effects disabled) after reboot back into kernel 3.16.0-28.38 , both *.916 and *.914 drivers work well probably this bug should also be attached to kernel package v3.18 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.18.0-8.9-generic 3.18.1 Uname: Linux 3.18.0-8-generic x86_64 ApportVersion: 2.15.1-0ubuntu1 Architecture: amd64 Date: Thu Jan 8 11:23:52 2015 InstallationDate: Installed on 2009-11-01 (1893 days ago) InstallationMedia: Kubuntu 9.10 "Karmic Koala" - Release amd64 (20091027) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=uk_UA.UTF-8 SHELL=/bin/bash SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.15.1-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mwg1214 F pulseaudio CRDA: country UA: DFS-UNSET (2400 - 2483 @ 40), (N/A, 20), (N/A), NO-OUTDOOR (5150 - 5350 @ 40), (N/A, 20), (N/A), NO-OUTDOOR (57240 - 65880 @ 2160), (N/A, 40), (N/A), NO-OUTDOOR CurrentDesktop: KDE DistroRelease: Ubuntu 15.04 HibernationDevice: RESUME=UUID=6932e499-f0ad-4456-b93c-2b7f9bf763dc InstallationDate: Installed on 2009-11-01 (1893 days ago) InstallationMedia: Kubuntu 9.10 "Karmic Koala" - Release amd64 (20091027) MachineType: Acer Aspire Package: xorg 1:7.7+7ubuntu2 PackageArchitecture: amd64 ProcEnviron: LANGUAGE= TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-28-generic root=UUID=9bc29087-2e9e-4bf9-bea1-2540902b5ae3 ro rootflags=commit=3600 transparent_hugepage=always init=/lib/systemd/systemd ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1 RelatedPackageVersions: linux-restricted-modules-3.16.0-28-generic N/A linux-backports-modules-3.16.0-28-generic N/A linux-firmware 1.140 Tags: vivid vivid Uname: Linux 3.16.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm admin cdrom dialout disk kvm lpadmin netdev plugdev sambashare src _MarkForUpload: True dmi.bios.date: 05/06/2011 dmi.bios.vendor: INSYDE dmi.bios.version: V1.24 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: JV10_CS dmi.board.vendor: Intel Corp. dmi.board.version: Base Board Version dmi.chassis.type: 1 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDE:bvrV1.24:bd05/06/2011:svnAcer:pnAspire:pvrV1.24:rvnIntelCorp.:rnJV10_CS:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion: dmi.product.name: Aspire dmi.product.version: V1.24 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1408593/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : h
[Kernel-packages] [Bug 1388039] Re: Random screen blackouts
Daniel Lehmann, thank you for reporting this bug to Ubuntu. Utopic reached EOL on July 23, 2015. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases If this is reproducible in a supported release, please file a new report. ** Package changed: xserver-xorg-video-intel (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1388039 Title: Random screen blackouts Status in linux package in Ubuntu: Invalid Bug description: In random intervals my laptops screen goes dark and comes up seconds later with the normal graphics. Dmesg gets spammed with oopses like those: 26195.272441] [ cut here ] [26195.272453] WARNING: CPU: 0 PID: 27459 at /build/buildd/linux-3.16.0/drivers/gpu/drm/i915/intel_pm.c:6001 intel_display_power_put+0xf9/0x160 [i915]() [26195.272454] Modules linked in: snd_usb_audio snd_usbmidi_lib nls_utf8 btrfs xor raid6_pq ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs libcrc32c btusb rfcomm bnep bluetooth 6lowpan_iphc joydev wl(POE) applesmc input_polldev snd_hda_codec_hdmi snd_hda_codec_cirrus snd_hda_codec_generic intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp snd_hda_intel kvm_intel snd_hda_controller snd_hda_codec kvm snd_hwdep snd_pcm bcm5974 snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device snd_timer cfg80211 lpc_ich snd nls_iso8859_1 shpchp mei_me mei soundcore sbs sbshc mac_hid apple_bl parport_pc ppdev lp parport dm_crypt hid_generic hid_apple crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel i915 aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd i2c_algo_bit drm_kms_helper [26195.272484] ahci libahci usbhid drm hid uas usb_storage video [26195.272488] CPU: 0 PID: 27459 Comm: Xorg Tainted: PW OE 3.16.0-24-generic #32-Ubuntu [26195.272489] Hardware name: Apple Inc. MacBookPro11,1/Mac-189A3D4F975D5FFC, BIOS MBP111.88Z.0138.B11.1408291433 08/29/2014 [26195.272490] 0009 880076d53bf0 8277fcbc [26195.272492] 880076d53c28 8206fd8d c0438800 2000 [26195.272494] 880452dc8520 880452dc 880076d53c38 [26195.272497] Call Trace: [26195.272499] [] dump_stack+0x45/0x56 [26195.272502] [] warn_slowpath_common+0x7d/0xa0 [26195.272505] [] warn_slowpath_null+0x1a/0x20 [26195.272513] [] intel_display_power_put+0xf9/0x160 [i915] [26195.272527] [] intel_hdmi_detect+0x9a/0x140 [i915] [26195.272532] [] drm_helper_probe_single_connector_modes_merge_bits+0x2a3/0x390 [drm_kms_helper] [26195.272536] [] drm_helper_probe_single_connector_modes+0x13/0x20 [drm_kms_helper] [26195.272546] [] drm_mode_getconnector+0x41c/0x480 [drm] [26195.272552] [] drm_ioctl+0x1df/0x680 [drm] [26195.272556] [] do_vfs_ioctl+0x2c8/0x4a0 [26195.272558] [] ? __sys_recvmsg+0x65/0x80 [26195.272560] [] SyS_ioctl+0x81/0xa0 [26195.272562] [] system_call_fastpath+0x1a/0x1f [26195.272564] ---[ end trace b40040e032179882 ]--- [26195.272570] [ cut here ] [26195.272578] WARNING: CPU: 0 PID: 27459 at /build/buildd/linux-3.16.0/drivers/gpu/drm/i915/intel_pm.c:6001 intel_display_power_put+0xf9/0x160 [i915]() [26195.272579] Modules linked in: snd_usb_audio snd_usbmidi_lib nls_utf8 btrfs xor raid6_pq ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs libcrc32c btusb rfcomm bnep bluetooth 6lowpan_iphc joydev wl(POE) applesmc input_polldev snd_hda_codec_hdmi snd_hda_codec_cirrus snd_hda_codec_generic intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp snd_hda_intel kvm_intel snd_hda_controller snd_hda_codec kvm snd_hwdep snd_pcm bcm5974 snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device snd_timer cfg80211 lpc_ich snd nls_iso8859_1 shpchp mei_me mei soundcore sbs sbshc mac_hid apple_bl parport_pc ppdev lp parport dm_crypt hid_generic hid_apple crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel i915 aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd i2c_algo_bit drm_kms_helper [26195.272608] ahci libahci usbhid drm hid uas usb_storage video [26195.272613] CPU: 0 PID: 27459 Comm: Xorg Tainted: PW OE 3.16.0-24-generic #32-Ubuntu [26195.272614] Hardware name: Apple Inc. MacBookPro11,1/Mac-189A3D4F975D5FFC, BIOS MBP111.88Z.0138.B11.1408291433 08/29/2014 [26195.272615] 0009 880076d53be0 8277fcbc [26195.272617] 880076d53c18 8206fd8d c0438800 8000 [26195.272619] 880452dc8520 880452dc 880076d53c28 [26195.272621] Call Trace: [26195.272623] [] dump_stack+0x45/0x56 [26195.272626] [] warn_slowpath_common+0x7d/0xa0 [26195.272629] [] warn_slowpath_null+0x1a/0x20
[Kernel-packages] [Bug 1490143] Re: When resuming after suspension desktop is freezed
I upgraded my BIOS to 0808. I suspended my PC for about 15 min. and when I resumed got a blue screen. I am attaching the dmesg output just after resuming. letozaf@letozaf-PC:~$ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date [sudo] password for letozaf: 0808 03/27/2008 ** Attachment added: "dmesg-afterBIOS-update" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1490143/+attachment/4476698/+files/dmesg4.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1490143 Title: When resuming after suspension desktop is freezed Status in linux package in Ubuntu: Confirmed Bug description: I suspended my PC for like about 1,5 - 2 hours and when I resumed the desktop had a black background, you could see the launcher bat you were unable to do anything it was freezed. This is my hardware: https://gist.github.com/anonymous/3203c7c5a43a509c0f22. I am attaching the screen-shots of my desktop after resuming, also in terminal (CTRL+ALT+F1) it looked rather garbled. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3 Uname: Linux 4.1.0-3-generic x86_64 ApportVersion: 2.18-0ubuntu7 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Sat Aug 29 13:57:20 2015 DistUpgraded: Fresh install DistroCodename: wily DistroVariant: ubuntu DkmsStatus: virtualbox, 5.0.2, 4.1.0-3-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation G84GL [Quadro FX 370] [10de:040a] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation Device [10de:0491] InstallationDate: Installed on 2015-08-16 (12 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150816) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.1.0-3-generic root=UUID=4b5d483e-4c0c-4013-b27c-0684b9343728 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/13/2007 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0803 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M2N dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0803:bd09/13/2007:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2N:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.12.1+15.10.20150805-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.6.3-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.6.3-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0+git20150819-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3 xserver.bootTime: Sat Aug 29 11:08:42 2015 xserver.configfile: default xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) NOUVEAU(0): [COPY] failed to allocate class. xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.17.2-1ubuntu3 xserver.video_driver: nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1490143/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1490143] Re: When resuming after suspension desktop is freezed
I upgraded my BIOS to 0808. I suspended my PC for about 15 min. and when I resumed got a blue screen. I am attaching the dmesg output just after resuming. letozaf@letozaf-PC:~$ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date [sudo] password for letozaf: 0808 03/27/2008 ** Attachment added: "dmesg-afterBIOS-update" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1490143/+attachment/4476699/+files/dmesg4.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1490143 Title: When resuming after suspension desktop is freezed Status in linux package in Ubuntu: Confirmed Bug description: I suspended my PC for like about 1,5 - 2 hours and when I resumed the desktop had a black background, you could see the launcher bat you were unable to do anything it was freezed. This is my hardware: https://gist.github.com/anonymous/3203c7c5a43a509c0f22. I am attaching the screen-shots of my desktop after resuming, also in terminal (CTRL+ALT+F1) it looked rather garbled. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3 Uname: Linux 4.1.0-3-generic x86_64 ApportVersion: 2.18-0ubuntu7 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Sat Aug 29 13:57:20 2015 DistUpgraded: Fresh install DistroCodename: wily DistroVariant: ubuntu DkmsStatus: virtualbox, 5.0.2, 4.1.0-3-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation G84GL [Quadro FX 370] [10de:040a] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation Device [10de:0491] InstallationDate: Installed on 2015-08-16 (12 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150816) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.1.0-3-generic root=UUID=4b5d483e-4c0c-4013-b27c-0684b9343728 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/13/2007 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0803 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M2N dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0803:bd09/13/2007:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2N:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.12.1+15.10.20150805-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.6.3-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.6.3-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0+git20150819-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3 xserver.bootTime: Sat Aug 29 11:08:42 2015 xserver.configfile: default xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) NOUVEAU(0): [COPY] failed to allocate class. xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.17.2-1ubuntu3 xserver.video_driver: nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1490143/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1388039] [NEW] Random screen blackouts
You have been subscribed to a public bug: In random intervals my laptops screen goes dark and comes up seconds later with the normal graphics. Dmesg gets spammed with oopses like those: 26195.272441] [ cut here ] [26195.272453] WARNING: CPU: 0 PID: 27459 at /build/buildd/linux-3.16.0/drivers/gpu/drm/i915/intel_pm.c:6001 intel_display_power_put+0xf9/0x160 [i915]() [26195.272454] Modules linked in: snd_usb_audio snd_usbmidi_lib nls_utf8 btrfs xor raid6_pq ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs libcrc32c btusb rfcomm bnep bluetooth 6lowpan_iphc joydev wl(POE) applesmc input_polldev snd_hda_codec_hdmi snd_hda_codec_cirrus snd_hda_codec_generic intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp snd_hda_intel kvm_intel snd_hda_controller snd_hda_codec kvm snd_hwdep snd_pcm bcm5974 snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device snd_timer cfg80211 lpc_ich snd nls_iso8859_1 shpchp mei_me mei soundcore sbs sbshc mac_hid apple_bl parport_pc ppdev lp parport dm_crypt hid_generic hid_apple crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel i915 aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd i2c_algo_bit drm_kms_helper [26195.272484] ahci libahci usbhid drm hid uas usb_storage video [26195.272488] CPU: 0 PID: 27459 Comm: Xorg Tainted: PW OE 3.16.0-24-generic #32-Ubuntu [26195.272489] Hardware name: Apple Inc. MacBookPro11,1/Mac-189A3D4F975D5FFC, BIOS MBP111.88Z.0138.B11.1408291433 08/29/2014 [26195.272490] 0009 880076d53bf0 8277fcbc [26195.272492] 880076d53c28 8206fd8d c0438800 2000 [26195.272494] 880452dc8520 880452dc 880076d53c38 [26195.272497] Call Trace: [26195.272499] [] dump_stack+0x45/0x56 [26195.272502] [] warn_slowpath_common+0x7d/0xa0 [26195.272505] [] warn_slowpath_null+0x1a/0x20 [26195.272513] [] intel_display_power_put+0xf9/0x160 [i915] [26195.272527] [] intel_hdmi_detect+0x9a/0x140 [i915] [26195.272532] [] drm_helper_probe_single_connector_modes_merge_bits+0x2a3/0x390 [drm_kms_helper] [26195.272536] [] drm_helper_probe_single_connector_modes+0x13/0x20 [drm_kms_helper] [26195.272546] [] drm_mode_getconnector+0x41c/0x480 [drm] [26195.272552] [] drm_ioctl+0x1df/0x680 [drm] [26195.272556] [] do_vfs_ioctl+0x2c8/0x4a0 [26195.272558] [] ? __sys_recvmsg+0x65/0x80 [26195.272560] [] SyS_ioctl+0x81/0xa0 [26195.272562] [] system_call_fastpath+0x1a/0x1f [26195.272564] ---[ end trace b40040e032179882 ]--- [26195.272570] [ cut here ] [26195.272578] WARNING: CPU: 0 PID: 27459 at /build/buildd/linux-3.16.0/drivers/gpu/drm/i915/intel_pm.c:6001 intel_display_power_put+0xf9/0x160 [i915]() [26195.272579] Modules linked in: snd_usb_audio snd_usbmidi_lib nls_utf8 btrfs xor raid6_pq ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs libcrc32c btusb rfcomm bnep bluetooth 6lowpan_iphc joydev wl(POE) applesmc input_polldev snd_hda_codec_hdmi snd_hda_codec_cirrus snd_hda_codec_generic intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp snd_hda_intel kvm_intel snd_hda_controller snd_hda_codec kvm snd_hwdep snd_pcm bcm5974 snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device snd_timer cfg80211 lpc_ich snd nls_iso8859_1 shpchp mei_me mei soundcore sbs sbshc mac_hid apple_bl parport_pc ppdev lp parport dm_crypt hid_generic hid_apple crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel i915 aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd i2c_algo_bit drm_kms_helper [26195.272608] ahci libahci usbhid drm hid uas usb_storage video [26195.272613] CPU: 0 PID: 27459 Comm: Xorg Tainted: PW OE 3.16.0-24-generic #32-Ubuntu [26195.272614] Hardware name: Apple Inc. MacBookPro11,1/Mac-189A3D4F975D5FFC, BIOS MBP111.88Z.0138.B11.1408291433 08/29/2014 [26195.272615] 0009 880076d53be0 8277fcbc [26195.272617] 880076d53c18 8206fd8d c0438800 8000 [26195.272619] 880452dc8520 880452dc 880076d53c28 [26195.272621] Call Trace: [26195.272623] [] dump_stack+0x45/0x56 [26195.272626] [] warn_slowpath_common+0x7d/0xa0 [26195.272629] [] warn_slowpath_null+0x1a/0x20 [26195.272637] [] intel_display_power_put+0xf9/0x160 [i915] [26195.272650] [] intel_dp_detect+0xa5/0x320 [i915] [26195.272662] [] ? intel_hdmi_detect+0x9a/0x140 [i915] [26195.272667] [] drm_helper_probe_single_connector_modes_merge_bits+0x2a3/0x390 [drm_kms_helper] [26195.272672] [] drm_helper_probe_single_connector_modes+0x13/0x20 [drm_kms_helper] [26195.272681] [] drm_mode_getconnector+0x41c/0x480 [drm] [26195.272687] [] drm_ioctl+0x1df/0x680 [drm] [26195.272691] [] do_vfs_ioctl+0x2c8/0x4a0 [26195.272693] [] ? __sys_recvmsg+0x65/0x80 [26195.272695] [] SyS_ioctl+0x81/0xa0 [26195.272697] [] system_call_fastpath+0x1a/0x1f [26195.272698] ---[ end trace b40040e032179883 ]--- Pr
[Kernel-packages] [Bug 1383034] Re: DisplayPort no longer works on Lenovo x220 after upgrade to 14.04
Elmar Pruesse, as per http://support.lenovo.com/us/en/products/laptops- and-netbooks/thinkpad-x-series-laptops/thinkpad-x220 an update to your computer's buggy and outdated BIOS is available (1.40). If you update to this following https://help.ubuntu.com/community/BIOSUpdate does it change anything? If it doesn't, could you please both specify what happened, and provide the output of the following terminal command: sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date 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. As well, you don't have to create a new bug report. Once the BIOS is updated, if the problem is still reproducible, and the information above is provided, then please mark this report Status Confirmed. Otherwise, please mark this as Invalid. Thank you for your understanding. ** Tags added: bios-outdated-1.40 ** Package changed: xserver-xorg-video-intel (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Importance: Undecided => Low ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1383034 Title: DisplayPort no longer works on Lenovo x220 after upgrade to 14.04 Status in linux package in Ubuntu: Incomplete Bug description: This is a regression that appeared when upgrading from 13.10 to 14.04. The issue had appeared briefly before (IIRC on 13.04). However, I can no longer find the bug report filed at the time. On 13.10, my Eizo monitor worked fine when connected via DisplayPort to my Lenovo X220. Since upgrading to 14.04, it simply shows a blank black display. This "crashes" the monitor, which has to be power cycled for any of the buttons or the VGA port to work again. VGA works, and the monitor does work during boot when connected via DP. Sometimes, dmesg shows the following error (seems to appear later on): [ 866.470728] [ cut here ] [ 866.470767] WARNING: CPU: 0 PID: 2060 at /build/buildd/linux-3.13.0/drivers/gpu/drm/i915/intel_dp.c:2758 intel_dp_link_down+0x1d2/0x210 [i915]() [ 866.470769] Modules linked in: ipt_MASQUERADE iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT xt_CHECKSUM iptable_mangle xt_tcpudp bridge stp llc ip6table_filter ip6_tables iptable_filter ip_tables ebtable_nat ebtables x_tables autofs4 rfcomm bnep nfsd auth_rpcgss nfs_acl binfmt_misc nfs lockd sunrpc fscache dm_multipath scsi_dh intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core arc4 joydev snd_hda_codec_hdmi iwldvm serio_raw videodev mac80211 btusb bluetooth iwlwifi snd_hda_codec_conexant thinkpad_acpi lpc_ich nvram snd_seq_midi snd_seq_midi_event cfg80211 snd_rawmidi snd_hda_intel snd_hda_codec snd_hwdep parport_pc snd_seq snd_pcm mei_me snd_seq_device snd_page_alloc ppdev mei snd_timer snd lp parport soundcore mac_hid zfs(POX) zunicode(POX) zavl(POX) zcommon(POX) znvpair(POX) spl(OX) btrfs xor raid6_pq libcrc32c usb_storage dm_mirror dm_region_h ash dm_log dm_crypt hid_generic usbhid hid crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper e1000e ablk_helper i915 cryptd ptp psmouse ahci sdhci_pci libahci sdhci pps_core i2c_algo_bit drm_kms_helper video wmi drm [ 866.470831] CPU: 0 PID: 2060 Comm: Xorg Tainted: PW OX 3.13.0-37-generic #64-Ubuntu [ 866.470833] Hardware name: LENOVO 4290G51/4290G51, BIOS 8DET66WW (1.36 ) 10/22/2012 [ 866.470835] 0009 8800d1437a80 8171ed09 [ 866.470838] 8800d1437ab8 8106773d 880401f510c8 880401891000 [ 866.470841] 88040235f000 80180344 88040192c000 8800d1437ac8 [ 866.470844] Call Trace: [ 866.470850] [] dump_stack+0x45/0x56 [ 866.470854] [] warn_slowpath_common+0x7d/0xa0 [ 866.470857] [] warn_slowpath_null+0x1a/0x20 [ 866.470873] [] intel_dp_link_down+0x1d2/0x210 [i915] [ 866.470888] [] intel_disable_dp+0x70/0x80 [i915] [ 866.470902] [] ironlake_crtc_disable+0x1ae/0x940 [i915] [ 866.470907] [] ? consume_skb+0x34/0x80 [ 866.470921] [] __intel_set_mode+0x2c9/0x9d0 [i915] [ 866.470935] [] intel_set_mode+0x16/0x30 [i915] [ 866.470947] [] intel_crtc_set_config+0x7ab/0x9a0 [i915] [ 866.470963] [] drm_mode_set_config_internal+0x5d/0xe0 [drm] [ 866.470976] [] drm_mode_setcrtc+0xf7/0x5e0 [drm] [ 866.470980] [] ? poll_select_copy_remaining+0x130/0x130 [ 866.470990] [] drm_ioctl+0x502/0x630 [drm] [ 866.470997] [] ? __hrtimer_start_range_ns+0x1a2/0x3a0 [ 866.471000] [] do_vf
[Kernel-packages] [Bug 1383034] [NEW] DisplayPort no longer works on Lenovo x220 after upgrade to 14.04
You have been subscribed to a public bug: This is a regression that appeared when upgrading from 13.10 to 14.04. The issue had appeared briefly before (IIRC on 13.04). However, I can no longer find the bug report filed at the time. On 13.10, my Eizo monitor worked fine when connected via DisplayPort to my Lenovo X220. Since upgrading to 14.04, it simply shows a blank black display. This "crashes" the monitor, which has to be power cycled for any of the buttons or the VGA port to work again. VGA works, and the monitor does work during boot when connected via DP. Sometimes, dmesg shows the following error (seems to appear later on): [ 866.470728] [ cut here ] [ 866.470767] WARNING: CPU: 0 PID: 2060 at /build/buildd/linux-3.13.0/drivers/gpu/drm/i915/intel_dp.c:2758 intel_dp_link_down+0x1d2/0x210 [i915]() [ 866.470769] Modules linked in: ipt_MASQUERADE iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT xt_CHECKSUM iptable_mangle xt_tcpudp bridge stp llc ip6table_filter ip6_tables iptable_filter ip_tables ebtable_nat ebtables x_tables autofs4 rfcomm bnep nfsd auth_rpcgss nfs_acl binfmt_misc nfs lockd sunrpc fscache dm_multipath scsi_dh intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core arc4 joydev snd_hda_codec_hdmi iwldvm serio_raw videodev mac80211 btusb bluetooth iwlwifi snd_hda_codec_conexant thinkpad_acpi lpc_ich nvram snd_seq_midi snd_seq_midi_event cfg80211 snd_rawmidi snd_hda_intel snd_hda_codec snd_hwdep parport_pc snd_seq snd_pcm mei_me snd_seq_device snd_page_alloc ppdev mei snd_timer snd lp parport soundcore mac_hid zfs(POX) zunicode(POX) zavl(POX) zcommon(POX) znvpair(POX) spl(OX) btrfs xor raid6_pq libcrc32c usb_storage dm_mirror dm_region_has h dm_log dm_crypt hid_generic usbhid hid crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper e1000e ablk_helper i915 cryptd ptp psmouse ahci sdhci_pci libahci sdhci pps_core i2c_algo_bit drm_kms_helper video wmi drm [ 866.470831] CPU: 0 PID: 2060 Comm: Xorg Tainted: PW OX 3.13.0-37-generic #64-Ubuntu [ 866.470833] Hardware name: LENOVO 4290G51/4290G51, BIOS 8DET66WW (1.36 ) 10/22/2012 [ 866.470835] 0009 8800d1437a80 8171ed09 [ 866.470838] 8800d1437ab8 8106773d 880401f510c8 880401891000 [ 866.470841] 88040235f000 80180344 88040192c000 8800d1437ac8 [ 866.470844] Call Trace: [ 866.470850] [] dump_stack+0x45/0x56 [ 866.470854] [] warn_slowpath_common+0x7d/0xa0 [ 866.470857] [] warn_slowpath_null+0x1a/0x20 [ 866.470873] [] intel_dp_link_down+0x1d2/0x210 [i915] [ 866.470888] [] intel_disable_dp+0x70/0x80 [i915] [ 866.470902] [] ironlake_crtc_disable+0x1ae/0x940 [i915] [ 866.470907] [] ? consume_skb+0x34/0x80 [ 866.470921] [] __intel_set_mode+0x2c9/0x9d0 [i915] [ 866.470935] [] intel_set_mode+0x16/0x30 [i915] [ 866.470947] [] intel_crtc_set_config+0x7ab/0x9a0 [i915] [ 866.470963] [] drm_mode_set_config_internal+0x5d/0xe0 [drm] [ 866.470976] [] drm_mode_setcrtc+0xf7/0x5e0 [drm] [ 866.470980] [] ? poll_select_copy_remaining+0x130/0x130 [ 866.470990] [] drm_ioctl+0x502/0x630 [drm] [ 866.470997] [] ? __hrtimer_start_range_ns+0x1a2/0x3a0 [ 866.471000] [] do_vfs_ioctl+0x2e0/0x4c0 [ 866.471003] [] ? __sys_recvmsg+0x65/0x80 [ 866.471007] [] SyS_ioctl+0x81/0xa0 [ 866.471010] [] system_call_fastpath+0x1a/0x1f [ 866.471012] ---[ end trace 0e7181aa00bf0b6d ]--- ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,compiztoolbox,decor,gnomecompat,grid,vpswitch,resize,imgpng,regex,mousepoll,move,wall,snap,place,unitymtgrabhandles,animation,session,fade,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: None CurrentDesktop: GNOME Date: Sun Oct 19 22:07:02 2014 DistUpgraded: 2014-10-12 14:54:45,124 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21da] InstallationDate: Installed on 2013-10-13 (371 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: LENOVO 4290G51 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-37-generic root=/dev/mapper/vg-u1304 ro splash quiet SourcePackage: xserver-xorg-video-intel UpgradeStatus: Upgraded to trusty on 2014-10-12 (7 days ago) dmi.bios.date: 10/22/2012 dmi.b
[Kernel-packages] [Bug 1363430] Re: [mesa] firefox: intel_do_flush_locked failed: Invalid argument
Andreas Weller, thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command, as it will automatically gather debugging information, in a terminal: apport-collect -p linux 1363430 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. ** No longer affects: firefox (Ubuntu) ** Package changed: xserver-xorg-video-intel (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Importance: Undecided => Low ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1363430 Title: [mesa] firefox: intel_do_flush_locked failed: Invalid argument Status in linux package in Ubuntu: Incomplete Bug description: Frequent crashes giving the following abort message on the console: (process:8065): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed (firefox:8065): GLib-GObject-WARNING **: Attempt to add property GnomeProgram::sm-connect after class was initialised (firefox:8065): GLib-GObject-WARNING **: Attempt to add property GnomeProgram::show-crash-dialog after class was initialised (firefox:8065): GLib-GObject-WARNING **: Attempt to add property GnomeProgram::display after class was initialised (firefox:8065): GLib-GObject-WARNING **: Attempt to add property GnomeProgram::default-icon after class was initialised ATTENTION: default value of option force_s3tc_enable overridden by environment. intel_do_flush_locked failed: Das Argument ist ungültig [8095] ###!!! ABORT: Aborting on channel error.: file /build/buildd/firefox-31.0+build1/ipc/glue/MessageChannel.cpp, line 1531 [8093] ###!!! ABORT: Aborting on channel error.: file /build/buildd/firefox-31.0+build1/ipc/glue/MessageChannel.cpp, line 1531 [8095] ###!!! ABORT: Aborting on channel error.: file /build/buildd/firefox-31.0+build1/ipc/glue/MessageChannel.cpp, line 1531[8093] ###!!! ABORT: Aborting on channel error.: file /build/buildd/firefox-31.0+build1/ipc/glue/MessageChannel.cpp, line 1531 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1363430/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1363430] [NEW] [mesa] firefox: intel_do_flush_locked failed: Invalid argument
You have been subscribed to a public bug: Frequent crashes giving the following abort message on the console: (process:8065): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed (firefox:8065): GLib-GObject-WARNING **: Attempt to add property GnomeProgram::sm-connect after class was initialised (firefox:8065): GLib-GObject-WARNING **: Attempt to add property GnomeProgram::show-crash-dialog after class was initialised (firefox:8065): GLib-GObject-WARNING **: Attempt to add property GnomeProgram::display after class was initialised (firefox:8065): GLib-GObject-WARNING **: Attempt to add property GnomeProgram::default-icon after class was initialised ATTENTION: default value of option force_s3tc_enable overridden by environment. intel_do_flush_locked failed: Das Argument ist ungültig [8095] ###!!! ABORT: Aborting on channel error.: file /build/buildd/firefox-31.0+build1/ipc/glue/MessageChannel.cpp, line 1531 [8093] ###!!! ABORT: Aborting on channel error.: file /build/buildd/firefox-31.0+build1/ipc/glue/MessageChannel.cpp, line 1531 [8095] ###!!! ABORT: Aborting on channel error.: file /build/buildd/firefox-31.0+build1/ipc/glue/MessageChannel.cpp, line 1531[8093] ###!!! ABORT: Aborting on channel error.: file /build/buildd/firefox-31.0+build1/ipc/glue/MessageChannel.cpp, line 1531 ** Affects: linux (Ubuntu) Importance: Low Status: Incomplete -- [mesa] firefox: intel_do_flush_locked failed: Invalid argument https://bugs.launchpad.net/bugs/1363430 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1499491] Re: Display connected on DisplayPort turns black during boot and never returns
Olivier Caro, could you please use the latest mainline kernel and provide the missing information following https://wiki.ubuntu.com/DebuggingKernelBoot ? ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1499491 Title: Display connected on DisplayPort turns black during boot and never returns Status in linux package in Ubuntu: Incomplete Bug description: The display connected on my R9 290 through DisplayPort connection turns black during boot and never comes back again. According to the power led, it is up and does not turn into power saving mode. According to xorg.0.log and System Settings / Display the display is perfectly detected. This display worked perfectly fine using the same DisplayPort cable, running the same driver on my Radeon HD 6670. Description: Ubuntu 15.04 Release: 15.04 --- ApportVersion: 2.17.2-0ubuntu1.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: olivier2403 F pulseaudio /dev/snd/controlC2: olivier2403 F pulseaudio /dev/snd/controlC1: olivier2403 F pulseaudio /dev/snd/seq:timidity 1672 F timidity DistroRelease: Ubuntu 15.04 EcryptfsInUse: Yes IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: To be filled by O.E.M. To be filled by O.E.M. Package: linux (not installed) ProcFB: 0 radeondrmfb 1 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-30-generic root=/dev/mapper/vg0-root ro radeon.auxch=0 init=/lib/systemd/systemd-bootchart ProcVersionSignature: Ubuntu 3.19.0-30.33-generic 3.19.8-ckt6 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.19.0-30-generic N/A linux-backports-modules-3.19.0-30-generic N/A linux-firmware 1.143.3 RfKill: Tags: vivid Uname: Linux 3.19.0-30-generic x86_64 UpgradeStatus: Upgraded to vivid on 2015-04-30 (149 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 04/09/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2501 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M5A97 LE R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2501:bd04/09/2014:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97LER2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1499491/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1490143] Re: When resuming after suspension desktop is freezed
Hi Christopher, I will do what you suggest in comment #15, meanwhile I had left my PC suspended for 1 hour and when I resumed I had a blue screen, I am attaching the dmesg output run just after resuming. Anyway I will now update my BIOS and then let you know. Thanks. ** Attachment added: "dmesg-third-time" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1490143/+attachment/4476682/+files/dmesg2.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1490143 Title: When resuming after suspension desktop is freezed Status in linux package in Ubuntu: Incomplete Bug description: I suspended my PC for like about 1,5 - 2 hours and when I resumed the desktop had a black background, you could see the launcher bat you were unable to do anything it was freezed. This is my hardware: https://gist.github.com/anonymous/3203c7c5a43a509c0f22. I am attaching the screen-shots of my desktop after resuming, also in terminal (CTRL+ALT+F1) it looked rather garbled. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3 Uname: Linux 4.1.0-3-generic x86_64 ApportVersion: 2.18-0ubuntu7 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Sat Aug 29 13:57:20 2015 DistUpgraded: Fresh install DistroCodename: wily DistroVariant: ubuntu DkmsStatus: virtualbox, 5.0.2, 4.1.0-3-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation G84GL [Quadro FX 370] [10de:040a] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation Device [10de:0491] InstallationDate: Installed on 2015-08-16 (12 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150816) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.1.0-3-generic root=UUID=4b5d483e-4c0c-4013-b27c-0684b9343728 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/13/2007 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0803 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M2N dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0803:bd09/13/2007:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2N:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.12.1+15.10.20150805-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.6.3-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.6.3-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0+git20150819-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3 xserver.bootTime: Sat Aug 29 11:08:42 2015 xserver.configfile: default xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) NOUVEAU(0): [COPY] failed to allocate class. xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.17.2-1ubuntu3 xserver.video_driver: nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1490143/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1499491] Re: Display connected on DisplayPort turns black during boot and never returns
I have successfully installed and booted the kernel from /~kernel-ppa/mainline/v4.3-rc3-unstable The behaviour is still the same: The display connected on DisplayPort keeps being black. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1499491 Title: Display connected on DisplayPort turns black during boot and never returns Status in linux package in Ubuntu: Incomplete Bug description: The display connected on my R9 290 through DisplayPort connection turns black during boot and never comes back again. According to the power led, it is up and does not turn into power saving mode. According to xorg.0.log and System Settings / Display the display is perfectly detected. This display worked perfectly fine using the same DisplayPort cable, running the same driver on my Radeon HD 6670. Description: Ubuntu 15.04 Release: 15.04 --- ApportVersion: 2.17.2-0ubuntu1.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: olivier2403 F pulseaudio /dev/snd/controlC2: olivier2403 F pulseaudio /dev/snd/controlC1: olivier2403 F pulseaudio /dev/snd/seq:timidity 1672 F timidity DistroRelease: Ubuntu 15.04 EcryptfsInUse: Yes IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: To be filled by O.E.M. To be filled by O.E.M. Package: linux (not installed) ProcFB: 0 radeondrmfb 1 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-30-generic root=/dev/mapper/vg0-root ro radeon.auxch=0 init=/lib/systemd/systemd-bootchart ProcVersionSignature: Ubuntu 3.19.0-30.33-generic 3.19.8-ckt6 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.19.0-30-generic N/A linux-backports-modules-3.19.0-30-generic N/A linux-firmware 1.143.3 RfKill: Tags: vivid Uname: Linux 3.19.0-30-generic x86_64 UpgradeStatus: Upgraded to vivid on 2015-04-30 (149 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 04/09/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2501 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M5A97 LE R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2501:bd04/09/2014:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97LER2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1499491/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1354046] Re: no 3d acceleration with error [drm:intel_dp_start_link_train] *ERROR* too many full retries, give up
Jonas G. Drange, thank you for reporting this bug to Ubuntu. Utopic reached EOL on July 23, 2015. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases If this is reproducible in a supported release, please file a new report. ** Tags removed: trusty ** No longer affects: ubuntu (Ubuntu) ** No longer affects: linux (Ubuntu) ** Changed in: xserver-xorg-video-intel (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1354046 Title: no 3d acceleration with error [drm:intel_dp_start_link_train] *ERROR* too many full retries, give up Status in xserver-xorg-video-intel package in Ubuntu: Invalid Bug description: Description: 3D games, video (especially flash) makes computer unresponsive. The problem has been present since upgrade to Utopic, but have recently become worse, maybe because of error message [drm:intel_dp_start_link_train] *ERROR* too many full retries, give up which appears in all terminals. How to reproduce: Start a 1080p video. e.g. Note that the video is not run from an encrypted folder. Or watch a video on youtube. Reproducable for new users as well, so not related to /home/$USER What happens: Usage on all four CPUs on my DELL XPS 13 DEVELOPER EDITION will be between 30% and 100%. What I expected: Expected same 3D performance as on Thrusty. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7 Uname: Linux 3.16.0-6-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.5-0ubuntu3 Architecture: amd64 BootLog: Scanning for Btrfs filesystems * Setting up X socket directories... [240G [234G[ OK ] CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Thu Aug 7 17:03:51 2014 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20120703-2 DistroCodename: utopic DistroVariant: ubuntu DkmsStatus: vboxhost, 4.3.12, 3.13.0-24-generic, x86_64: installed vboxhost, 4.3.12, 3.13.0-27-generic, x86_64: installed vboxhost, 4.3.12, 3.13.0-29-generic, x86_64: installed vboxhost, 4.3.12, 3.16.0-5-generic, x86_64: installed vboxhost, 4.3.12, 3.16.0-6-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:058b] InstallationDate: Installed on 2013-08-27 (345 days ago) InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 20120703-15:08 MachineType: Dell Inc. Dell System XPS L322X ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-6-generic root=UUID=221de9c1-f10a-4be4-9273-5c12864c8680 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display SystemImageInfo: Error: [Errno 2] No such file or directory: 'system-image-cli' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/15/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 0PJHXN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA09:bd05/15/2013:svnDellInc.:pnDellSystemXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L322X dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11+14.10.20140707-0ubuntu1b1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.54-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.2.3-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental 10.0.0-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx 10.2.3-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu9 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Thu Aug 7 16:54:59 2014 xserver.configfile: default xserver.errors: intel: Failed to load module "dri3" (module does not exist, 0) intel: Failed to load mod
[Kernel-packages] [Bug 1500218] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. >From a terminal window please run: apport-collect 1500218 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. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1500218 Title: Please backport on 4.2 : Important fix for tcp kernel Status in linux package in Ubuntu: Incomplete Bug description: The patch addresses a problem with cubic congestion control: https://github.com/torvalds/linux/commit/30927520dbae297182990bb21d08762bcc35ce1d http://bitsup.blogspot.fr/2015/09/thanks-google-tcp-team-for-open-source.html This indeed can be included to all the supported kernels to get benefit everywhere. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1500218/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1499491] Re: Display connected on DisplayPort turns black during boot and never returns
** Tags added: kernel-bug-exists-upstream-4.3-rc3 ** Tags added: kernel-bug-exists-upstream -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1499491 Title: Display connected on DisplayPort turns black during boot and never returns Status in linux package in Ubuntu: Incomplete Bug description: The display connected on my R9 290 through DisplayPort connection turns black during boot and never comes back again. According to the power led, it is up and does not turn into power saving mode. According to xorg.0.log and System Settings / Display the display is perfectly detected. This display worked perfectly fine using the same DisplayPort cable, running the same driver on my Radeon HD 6670. Description: Ubuntu 15.04 Release: 15.04 --- ApportVersion: 2.17.2-0ubuntu1.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: olivier2403 F pulseaudio /dev/snd/controlC2: olivier2403 F pulseaudio /dev/snd/controlC1: olivier2403 F pulseaudio /dev/snd/seq:timidity 1672 F timidity DistroRelease: Ubuntu 15.04 EcryptfsInUse: Yes IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: To be filled by O.E.M. To be filled by O.E.M. Package: linux (not installed) ProcFB: 0 radeondrmfb 1 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-30-generic root=/dev/mapper/vg0-root ro radeon.auxch=0 init=/lib/systemd/systemd-bootchart ProcVersionSignature: Ubuntu 3.19.0-30.33-generic 3.19.8-ckt6 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.19.0-30-generic N/A linux-backports-modules-3.19.0-30-generic N/A linux-firmware 1.143.3 RfKill: Tags: vivid Uname: Linux 3.19.0-30-generic x86_64 UpgradeStatus: Upgraded to vivid on 2015-04-30 (149 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 04/09/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2501 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M5A97 LE R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2501:bd04/09/2014:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97LER2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1499491/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1500218] [NEW] Please backport on 4.2 : Important fix for tcp kernel
Public bug reported: The patch addresses a problem with cubic congestion control: https://github.com/torvalds/linux/commit/30927520dbae297182990bb21d08762bcc35ce1d http://bitsup.blogspot.fr/2015/09/thanks-google-tcp-team-for-open-source.html This indeed can be included to all the supported kernels to get benefit everywhere. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: bot-stop-nagging wily ** Tags added: bot-stop-nagging ** Tags added: wily ** Description changed: The patch addresses a problem with cubic congestion control: https://github.com/torvalds/linux/commit/30927520dbae297182990bb21d08762bcc35ce1d http://bitsup.blogspot.fr/2015/09/thanks-google-tcp-team-for-open-source.html + + This indeed can be included to all the supported kernels to get benefit + everywhere. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1500218 Title: Please backport on 4.2 : Important fix for tcp kernel Status in linux package in Ubuntu: New Bug description: The patch addresses a problem with cubic congestion control: https://github.com/torvalds/linux/commit/30927520dbae297182990bb21d08762bcc35ce1d http://bitsup.blogspot.fr/2015/09/thanks-google-tcp-team-for-open-source.html This indeed can be included to all the supported kernels to get benefit everywhere. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1500218/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1327774] Re: asus x200la brightness hotkeys not working (rest of them do)
Jaime Pérez, thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command, as it will automatically gather debugging information, in a terminal: apport-collect -p linux 1327774 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. ** Package changed: xserver-xorg-video-intel (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Importance: Undecided => Low ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1327774 Title: asus x200la brightness hotkeys not working (rest of them do) Status in linux package in Ubuntu: Incomplete Bug description: If I click on brightness hotkeys nothing (apparently) happens. I suppose keys are missbinded or something like that. How can I fix it? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1327774/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1327774] [NEW] asus x200la brightness hotkeys not working (rest of them do)
You have been subscribed to a public bug: If I click on brightness hotkeys nothing (apparently) happens. I suppose keys are missbinded or something like that. How can I fix it? ** Affects: linux (Ubuntu) Importance: Low Status: Incomplete ** Tags: 4400 64bit asus hd intel patch trusty unity x200la -- asus x200la brightness hotkeys not working (rest of them do) https://bugs.launchpad.net/bugs/1327774 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1496052] Re: 3.19.0 Wifi is very unstable
Enkouyami, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1496052/comments/21 regarding this is not reproducible in Ubuntu. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find. ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1496052 Title: 3.19.0 Wifi is very unstable Status in linux package in Ubuntu: Invalid Bug description: With the 3.19 kernel, wifi is very unstable. I don't have this problem on other kernels (3.13, 3.16, 4.0, & 4.2). My OS is Linux Mint 17.2 Cinnamon 64-bit; I originally had been 17.1 installed before I upgraded. --- ApportVersion: 2.14.1-0ubuntu3.13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ely3083 F pulseaudio /dev/snd/pcmC1D0p: ely3083 F...m pulseaudio /dev/snd/controlC1: ely3083 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=db907587-bbc0-43fe-92a4-5d8c2acce879 InstallationDate: Installed on 2014-12-07 (283 days ago) InstallationMedia: Linux Mint 17.1 "Rebecca" - Release amd64 20141126 MachineType: Hewlett-Packard HP Pavilion 17 Notebook PC Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-49-generic root=/dev/mapper/Linux-LinuxMint ro quiet splash resume=/dev/Linux/Swap vt.handoff=7 ProcVersionSignature: Ubuntu 3.16.0-49.65~14.04.1-generic 3.16.7-ckt15 RelatedPackageVersions: linux-restricted-modules-3.16.0-49-generic N/A linux-backports-modules-3.16.0-49-generic N/A linux-firmware 1.127.15 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: rafaela Uname: Linux 3.16.0-49-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip fuse lpadmin plugdev sambashare sudo users _MarkForUpload: True dmi.bios.date: 12/19/2014 dmi.bios.vendor: Insyde dmi.bios.version: F.34 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 227F dmi.board.vendor: Hewlett-Packard dmi.board.version: 77.35 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.34:bd12/19/2014:svnHewlett-Packard:pnHPPavilion17NotebookPC:pvr097510405F1620180:rvnHewlett-Packard:rn227F:rvr77.35:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion 17 Notebook PC dmi.product.version: 097510405F1620180 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1496052/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1499491] Re: Display connected on DisplayPort turns black during boot and never returns
Olivier Caro, could you please test the latest upstream kernel available from the very top line at the top of the page from http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D (the release names are irrelevant for testing, and please do not test the daily folder)? Install instructions are available at https://wiki.ubuntu.com/Kernel/MainlineBuilds . This will allow additional upstream developers to examine the issue. If the latest kernel did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this issue is fixed in the mainline kernel, please add the following tags by clicking on the yellow circle with a black pencil icon, next to the word Tags, located at the bottom of the report description: kernel-fixed-upstream kernel-fixed-upstream-X.Y-rcZ Where X, Y, and Z are numbers corresponding to the kernel version. If the mainline kernel does not fix the issue, please add the following tags: kernel-bug-exists-upstream kernel-bug-exists-upstream-X.Y-rcZ Please note, an error to install the kernel does not fit the criteria of kernel-bug-exists-upstream. Once testing of the latest upstream kernel is complete, please mark this report's Status as Confirmed. Please let us know your results. Thank you for your understanding. ** Tags removed: bios-outdated-2601 ** Tags added: latest-bios-2601 ** Changed in: linux (Ubuntu) Importance: Low => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1499491 Title: Display connected on DisplayPort turns black during boot and never returns Status in linux package in Ubuntu: Incomplete Bug description: The display connected on my R9 290 through DisplayPort connection turns black during boot and never comes back again. According to the power led, it is up and does not turn into power saving mode. According to xorg.0.log and System Settings / Display the display is perfectly detected. This display worked perfectly fine using the same DisplayPort cable, running the same driver on my Radeon HD 6670. Description: Ubuntu 15.04 Release: 15.04 --- ApportVersion: 2.17.2-0ubuntu1.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: olivier2403 F pulseaudio /dev/snd/controlC2: olivier2403 F pulseaudio /dev/snd/controlC1: olivier2403 F pulseaudio /dev/snd/seq:timidity 1672 F timidity DistroRelease: Ubuntu 15.04 EcryptfsInUse: Yes IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: To be filled by O.E.M. To be filled by O.E.M. Package: linux (not installed) ProcFB: 0 radeondrmfb 1 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-30-generic root=/dev/mapper/vg0-root ro radeon.auxch=0 init=/lib/systemd/systemd-bootchart ProcVersionSignature: Ubuntu 3.19.0-30.33-generic 3.19.8-ckt6 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.19.0-30-generic N/A linux-backports-modules-3.19.0-30-generic N/A linux-firmware 1.143.3 RfKill: Tags: vivid Uname: Linux 3.19.0-30-generic x86_64 UpgradeStatus: Upgraded to vivid on 2015-04-30 (149 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 04/09/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2501 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M5A97 LE R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2501:bd04/09/2014:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97LER2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1499491/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1496052] Re: 3.19.0 Wifi is very unstable
On Ubuntu I don't have that problem. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1496052 Title: 3.19.0 Wifi is very unstable Status in linux package in Ubuntu: Incomplete Bug description: With the 3.19 kernel, wifi is very unstable. I don't have this problem on other kernels (3.13, 3.16, 4.0, & 4.2). My OS is Linux Mint 17.2 Cinnamon 64-bit; I originally had been 17.1 installed before I upgraded. --- ApportVersion: 2.14.1-0ubuntu3.13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ely3083 F pulseaudio /dev/snd/pcmC1D0p: ely3083 F...m pulseaudio /dev/snd/controlC1: ely3083 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=db907587-bbc0-43fe-92a4-5d8c2acce879 InstallationDate: Installed on 2014-12-07 (283 days ago) InstallationMedia: Linux Mint 17.1 "Rebecca" - Release amd64 20141126 MachineType: Hewlett-Packard HP Pavilion 17 Notebook PC Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-49-generic root=/dev/mapper/Linux-LinuxMint ro quiet splash resume=/dev/Linux/Swap vt.handoff=7 ProcVersionSignature: Ubuntu 3.16.0-49.65~14.04.1-generic 3.16.7-ckt15 RelatedPackageVersions: linux-restricted-modules-3.16.0-49-generic N/A linux-backports-modules-3.16.0-49-generic N/A linux-firmware 1.127.15 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: rafaela Uname: Linux 3.16.0-49-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip fuse lpadmin plugdev sambashare sudo users _MarkForUpload: True dmi.bios.date: 12/19/2014 dmi.bios.vendor: Insyde dmi.bios.version: F.34 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 227F dmi.board.vendor: Hewlett-Packard dmi.board.version: 77.35 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.34:bd12/19/2014:svnHewlett-Packard:pnHPPavilion17NotebookPC:pvr097510405F1620180:rvnHewlett-Packard:rn227F:rvr77.35:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion 17 Notebook PC dmi.product.version: 097510405F1620180 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1496052/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1499491] Re: Display connected on DisplayPort turns black during boot and never returns
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1499491 Title: Display connected on DisplayPort turns black during boot and never returns Status in linux package in Ubuntu: Confirmed Bug description: The display connected on my R9 290 through DisplayPort connection turns black during boot and never comes back again. According to the power led, it is up and does not turn into power saving mode. According to xorg.0.log and System Settings / Display the display is perfectly detected. This display worked perfectly fine using the same DisplayPort cable, running the same driver on my Radeon HD 6670. Description: Ubuntu 15.04 Release: 15.04 --- ApportVersion: 2.17.2-0ubuntu1.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: olivier2403 F pulseaudio /dev/snd/controlC2: olivier2403 F pulseaudio /dev/snd/controlC1: olivier2403 F pulseaudio /dev/snd/seq:timidity 1672 F timidity DistroRelease: Ubuntu 15.04 EcryptfsInUse: Yes IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: To be filled by O.E.M. To be filled by O.E.M. Package: linux (not installed) ProcFB: 0 radeondrmfb 1 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-30-generic root=/dev/mapper/vg0-root ro radeon.auxch=0 init=/lib/systemd/systemd-bootchart ProcVersionSignature: Ubuntu 3.19.0-30.33-generic 3.19.8-ckt6 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.19.0-30-generic N/A linux-backports-modules-3.19.0-30-generic N/A linux-firmware 1.143.3 RfKill: Tags: vivid Uname: Linux 3.19.0-30-generic x86_64 UpgradeStatus: Upgraded to vivid on 2015-04-30 (149 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 04/09/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2501 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M5A97 LE R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2501:bd04/09/2014:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97LER2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1499491/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1499491] Re: Display connected on DisplayPort turns black during boot and never returns
Hi Christopher, Thank you for your time. As requested I have updated the BIOS from the BIOS interface itself. The display connected on Display port behaves exactly the same as before : - It is on during bios startup - It is on during grub menu - It is on and showing the first lines during linux boot. - It turns black after about one second (probably when radeon module is loaded). - it stays black when xorg is started - It seems to be recognised by randr but never displays anything. Here are the results of the dmidecode commands : sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date 2601 03/24/2015 Regards. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1499491 Title: Display connected on DisplayPort turns black during boot and never returns Status in linux package in Ubuntu: Confirmed Bug description: The display connected on my R9 290 through DisplayPort connection turns black during boot and never comes back again. According to the power led, it is up and does not turn into power saving mode. According to xorg.0.log and System Settings / Display the display is perfectly detected. This display worked perfectly fine using the same DisplayPort cable, running the same driver on my Radeon HD 6670. Description: Ubuntu 15.04 Release: 15.04 --- ApportVersion: 2.17.2-0ubuntu1.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: olivier2403 F pulseaudio /dev/snd/controlC2: olivier2403 F pulseaudio /dev/snd/controlC1: olivier2403 F pulseaudio /dev/snd/seq:timidity 1672 F timidity DistroRelease: Ubuntu 15.04 EcryptfsInUse: Yes IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: To be filled by O.E.M. To be filled by O.E.M. Package: linux (not installed) ProcFB: 0 radeondrmfb 1 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-30-generic root=/dev/mapper/vg0-root ro radeon.auxch=0 init=/lib/systemd/systemd-bootchart ProcVersionSignature: Ubuntu 3.19.0-30.33-generic 3.19.8-ckt6 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.19.0-30-generic N/A linux-backports-modules-3.19.0-30-generic N/A linux-firmware 1.143.3 RfKill: Tags: vivid Uname: Linux 3.19.0-30-generic x86_64 UpgradeStatus: Upgraded to vivid on 2015-04-30 (149 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 04/09/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2501 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M5A97 LE R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2501:bd04/09/2014:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97LER2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1499491/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1500070] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1500070/+attachment/4476663/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1500070 Title: Lumia 535 (RM-1089) detected, but file manager shows no content Status in linux package in Ubuntu: Incomplete Bug description: Hi, a Lumia 535 (RM-1089) Windows Phone connected via USB to a notebook running Ubuntu 15.10 will be detected, but Ubuntu's file manager shows no content even though there are directories and many files (e.g. pictures) stored on the smartphone. Installing the mtpfs package didn't change anything. The directories and files are accessible on Windows 7 (tested!). Curiously, the mtp-detect tool doesn't find any MTP devices. :~$ sudo mtp-detect Unable to open ~/.mtpz-data for reading, MTPZ disabled. libmtp version: 1.1.8 Listing raw device(s) No raw devices found. :~$ lsusb -v Bus 001 Device 007: ID 0421:06fc Nokia Mobile Phones Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize064 idVendor 0x0421 Nokia Mobile Phones idProduct 0x06fc bcdDevice1.00 iManufacturer 1 Microsoft iProduct2 Lumia 535 (RM-1089) iSerial 3 510008ECC1C1 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 108 bNumInterfaces 4 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xa0 (Bus Powered) Remote Wakeup MaxPower 100mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 3 bInterfaceClass 6 Imaging bInterfaceSubClass 1 Still Image Capture bInterfaceProtocol 1 Picture Transfer Protocol (PIMA 15470) iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x01 EP 1 OUT bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes3 Transfer TypeInterrupt Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 4 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber1 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass255 Vendor Specific Subclass bInterfaceProtocol255 Vendor Specific Protocol iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x83 EP 3 IN bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x02 EP 2 OUT bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber2 bAlternateSetting 0 bNumEndpoints 2
[Kernel-packages] [Bug 1500070] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1500070/+attachment/4476664/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1500070 Title: Lumia 535 (RM-1089) detected, but file manager shows no content Status in linux package in Ubuntu: Incomplete Bug description: Hi, a Lumia 535 (RM-1089) Windows Phone connected via USB to a notebook running Ubuntu 15.10 will be detected, but Ubuntu's file manager shows no content even though there are directories and many files (e.g. pictures) stored on the smartphone. Installing the mtpfs package didn't change anything. The directories and files are accessible on Windows 7 (tested!). Curiously, the mtp-detect tool doesn't find any MTP devices. :~$ sudo mtp-detect Unable to open ~/.mtpz-data for reading, MTPZ disabled. libmtp version: 1.1.8 Listing raw device(s) No raw devices found. :~$ lsusb -v Bus 001 Device 007: ID 0421:06fc Nokia Mobile Phones Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize064 idVendor 0x0421 Nokia Mobile Phones idProduct 0x06fc bcdDevice1.00 iManufacturer 1 Microsoft iProduct2 Lumia 535 (RM-1089) iSerial 3 510008ECC1C1 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 108 bNumInterfaces 4 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xa0 (Bus Powered) Remote Wakeup MaxPower 100mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 3 bInterfaceClass 6 Imaging bInterfaceSubClass 1 Still Image Capture bInterfaceProtocol 1 Picture Transfer Protocol (PIMA 15470) iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x01 EP 1 OUT bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes3 Transfer TypeInterrupt Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 4 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber1 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass255 Vendor Specific Subclass bInterfaceProtocol255 Vendor Specific Protocol iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x83 EP 3 IN bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x02 EP 2 OUT bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber2 bAlternateSetting 0 bNumEndpoints 2
[Kernel-packages] [Bug 1500070] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1500070/+attachment/4476661/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1500070 Title: Lumia 535 (RM-1089) detected, but file manager shows no content Status in linux package in Ubuntu: Incomplete Bug description: Hi, a Lumia 535 (RM-1089) Windows Phone connected via USB to a notebook running Ubuntu 15.10 will be detected, but Ubuntu's file manager shows no content even though there are directories and many files (e.g. pictures) stored on the smartphone. Installing the mtpfs package didn't change anything. The directories and files are accessible on Windows 7 (tested!). Curiously, the mtp-detect tool doesn't find any MTP devices. :~$ sudo mtp-detect Unable to open ~/.mtpz-data for reading, MTPZ disabled. libmtp version: 1.1.8 Listing raw device(s) No raw devices found. :~$ lsusb -v Bus 001 Device 007: ID 0421:06fc Nokia Mobile Phones Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize064 idVendor 0x0421 Nokia Mobile Phones idProduct 0x06fc bcdDevice1.00 iManufacturer 1 Microsoft iProduct2 Lumia 535 (RM-1089) iSerial 3 510008ECC1C1 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 108 bNumInterfaces 4 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xa0 (Bus Powered) Remote Wakeup MaxPower 100mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 3 bInterfaceClass 6 Imaging bInterfaceSubClass 1 Still Image Capture bInterfaceProtocol 1 Picture Transfer Protocol (PIMA 15470) iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x01 EP 1 OUT bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes3 Transfer TypeInterrupt Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 4 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber1 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass255 Vendor Specific Subclass bInterfaceProtocol255 Vendor Specific Protocol iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x83 EP 3 IN bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x02 EP 2 OUT bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber2 bAlternateSetting 0 bNumEndpoints 2 bInterfaceC
[Kernel-packages] [Bug 1500070] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1500070/+attachment/4476658/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1500070 Title: Lumia 535 (RM-1089) detected, but file manager shows no content Status in linux package in Ubuntu: Incomplete Bug description: Hi, a Lumia 535 (RM-1089) Windows Phone connected via USB to a notebook running Ubuntu 15.10 will be detected, but Ubuntu's file manager shows no content even though there are directories and many files (e.g. pictures) stored on the smartphone. Installing the mtpfs package didn't change anything. The directories and files are accessible on Windows 7 (tested!). Curiously, the mtp-detect tool doesn't find any MTP devices. :~$ sudo mtp-detect Unable to open ~/.mtpz-data for reading, MTPZ disabled. libmtp version: 1.1.8 Listing raw device(s) No raw devices found. :~$ lsusb -v Bus 001 Device 007: ID 0421:06fc Nokia Mobile Phones Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize064 idVendor 0x0421 Nokia Mobile Phones idProduct 0x06fc bcdDevice1.00 iManufacturer 1 Microsoft iProduct2 Lumia 535 (RM-1089) iSerial 3 510008ECC1C1 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 108 bNumInterfaces 4 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xa0 (Bus Powered) Remote Wakeup MaxPower 100mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 3 bInterfaceClass 6 Imaging bInterfaceSubClass 1 Still Image Capture bInterfaceProtocol 1 Picture Transfer Protocol (PIMA 15470) iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x01 EP 1 OUT bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes3 Transfer TypeInterrupt Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 4 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber1 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass255 Vendor Specific Subclass bInterfaceProtocol255 Vendor Specific Protocol iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x83 EP 3 IN bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x02 EP 2 OUT bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber2 bAlternateSetting 0 bNumEndpoints 2 bInt
[Kernel-packages] [Bug 1500070] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1500070/+attachment/447/+files/WifiSyslog.txt ** Attachment removed: "AlsaInfo.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1500070/+attachment/4476655/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1500070 Title: Lumia 535 (RM-1089) detected, but file manager shows no content Status in linux package in Ubuntu: Incomplete Bug description: Hi, a Lumia 535 (RM-1089) Windows Phone connected via USB to a notebook running Ubuntu 15.10 will be detected, but Ubuntu's file manager shows no content even though there are directories and many files (e.g. pictures) stored on the smartphone. Installing the mtpfs package didn't change anything. The directories and files are accessible on Windows 7 (tested!). Curiously, the mtp-detect tool doesn't find any MTP devices. :~$ sudo mtp-detect Unable to open ~/.mtpz-data for reading, MTPZ disabled. libmtp version: 1.1.8 Listing raw device(s) No raw devices found. :~$ lsusb -v Bus 001 Device 007: ID 0421:06fc Nokia Mobile Phones Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize064 idVendor 0x0421 Nokia Mobile Phones idProduct 0x06fc bcdDevice1.00 iManufacturer 1 Microsoft iProduct2 Lumia 535 (RM-1089) iSerial 3 510008ECC1C1 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 108 bNumInterfaces 4 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xa0 (Bus Powered) Remote Wakeup MaxPower 100mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 3 bInterfaceClass 6 Imaging bInterfaceSubClass 1 Still Image Capture bInterfaceProtocol 1 Picture Transfer Protocol (PIMA 15470) iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x01 EP 1 OUT bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes3 Transfer TypeInterrupt Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 4 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber1 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass255 Vendor Specific Subclass bInterfaceProtocol255 Vendor Specific Protocol iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x83 EP 3 IN bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x02 EP 2 OUT bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Interface Descriptor: bLength 9
[Kernel-packages] [Bug 1500070] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1500070/+attachment/4476665/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1500070 Title: Lumia 535 (RM-1089) detected, but file manager shows no content Status in linux package in Ubuntu: Incomplete Bug description: Hi, a Lumia 535 (RM-1089) Windows Phone connected via USB to a notebook running Ubuntu 15.10 will be detected, but Ubuntu's file manager shows no content even though there are directories and many files (e.g. pictures) stored on the smartphone. Installing the mtpfs package didn't change anything. The directories and files are accessible on Windows 7 (tested!). Curiously, the mtp-detect tool doesn't find any MTP devices. :~$ sudo mtp-detect Unable to open ~/.mtpz-data for reading, MTPZ disabled. libmtp version: 1.1.8 Listing raw device(s) No raw devices found. :~$ lsusb -v Bus 001 Device 007: ID 0421:06fc Nokia Mobile Phones Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize064 idVendor 0x0421 Nokia Mobile Phones idProduct 0x06fc bcdDevice1.00 iManufacturer 1 Microsoft iProduct2 Lumia 535 (RM-1089) iSerial 3 510008ECC1C1 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 108 bNumInterfaces 4 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xa0 (Bus Powered) Remote Wakeup MaxPower 100mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 3 bInterfaceClass 6 Imaging bInterfaceSubClass 1 Still Image Capture bInterfaceProtocol 1 Picture Transfer Protocol (PIMA 15470) iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x01 EP 1 OUT bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes3 Transfer TypeInterrupt Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 4 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber1 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass255 Vendor Specific Subclass bInterfaceProtocol255 Vendor Specific Protocol iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x83 EP 3 IN bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x02 EP 2 OUT bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber2 bAlternateSetting 0 bNumEndpoints 2 bInterfac
[Kernel-packages] [Bug 1500070] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1500070/+attachment/4476659/+files/JournalErrors.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1500070 Title: Lumia 535 (RM-1089) detected, but file manager shows no content Status in linux package in Ubuntu: Incomplete Bug description: Hi, a Lumia 535 (RM-1089) Windows Phone connected via USB to a notebook running Ubuntu 15.10 will be detected, but Ubuntu's file manager shows no content even though there are directories and many files (e.g. pictures) stored on the smartphone. Installing the mtpfs package didn't change anything. The directories and files are accessible on Windows 7 (tested!). Curiously, the mtp-detect tool doesn't find any MTP devices. :~$ sudo mtp-detect Unable to open ~/.mtpz-data for reading, MTPZ disabled. libmtp version: 1.1.8 Listing raw device(s) No raw devices found. :~$ lsusb -v Bus 001 Device 007: ID 0421:06fc Nokia Mobile Phones Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize064 idVendor 0x0421 Nokia Mobile Phones idProduct 0x06fc bcdDevice1.00 iManufacturer 1 Microsoft iProduct2 Lumia 535 (RM-1089) iSerial 3 510008ECC1C1 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 108 bNumInterfaces 4 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xa0 (Bus Powered) Remote Wakeup MaxPower 100mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 3 bInterfaceClass 6 Imaging bInterfaceSubClass 1 Still Image Capture bInterfaceProtocol 1 Picture Transfer Protocol (PIMA 15470) iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x01 EP 1 OUT bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes3 Transfer TypeInterrupt Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 4 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber1 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass255 Vendor Specific Subclass bInterfaceProtocol255 Vendor Specific Protocol iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x83 EP 3 IN bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x02 EP 2 OUT bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber2 bAlternateSetting 0 bNumEndpoints 2
