[Kernel-packages] [Bug 1841040] [NEW] r8169 ethernet sometimes doesn't work after cold boot/boot
Public bug reported: Whenever the computer is rebooted there is a roughly 50% chance that the r8169 ethernet cannot negotiate a link. There is no relevant information in dmesg except for the "link down" message. The work around is to just keep rebooting the computer until it eventually works; sometimes this may take up to 7 reboots. The first set of attached log files were generated while the ethernet was working. The second set are generated on the 5.0 HWE kernel when the ethernet was NOT working. Note that this is a regression. Ubuntu 16.04 ran on this computer for three years without the ethernet doing this even once. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-58-generic 4.15.0-58.64 ProcVersionSignature: Ubuntu 4.15.0-58.64-generic 4.15.18 Uname: Linux 4.15.0-58-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', '/dev/snd/pcmC2D0c', '/dev/snd/controlC2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/by-path', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu Aug 22 10:05:17 2019 HibernationDevice: RESUME=UUID=4ab51820-6203-45a8-a04d-07946b0fbe56 InstallationDate: Installed on 2013-12-22 (2068 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: ASUS All Series ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-58-generic root=UUID=e1e7d1a7-19e8-4203-ad6a-86a144db61bc ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-58-generic N/A linux-backports-modules-4.15.0-58-generic N/A linux-firmware 1.173.9 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2019-01-30 (203 days ago) dmi.bios.date: 06/18/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2201 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H87M-E dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2201:bd06/18/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH87M-E:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: al14985 F pulseaudio /dev/snd/controlC0: al14985 F pulseaudio /dev/snd/controlC1: al14985 F pulseaudio CurrentDesktop: Unity:Unity7:ubuntu DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=4ab51820-6203-45a8-a04d-07946b0fbe56 InstallationDate: Installed on 2013-12-22 (2068 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: ASUS All Series Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-25-generic root=UUID=e1e7d1a7-19e8-4203-ad6a-86a144db61bc ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-25.26~18.04.1-generic 5.0.18 RelatedPackageVersions: linux-restricted-modules-5.0.0-25-generic N/A linux-backports-modules-5.0.0-25-generic N/A linux-firmware1.173.9 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 5.0.0-25-generic x86_64 UpgradeStatus: Upgraded to bionic on 2019-01-30 (203 days ago) UserGroups: adm lpadmin sambashare sudo _MarkForUpload: True dmi.bios.date: 06/18/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2201 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H87M-E dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2201:bd06/18/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH87M-E:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug apport-collected bionic ** Description changed: Whenever the comput
[Kernel-packages] [Bug 1841040] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1841040/+attachment/5283952/+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/1841040 Title: r8169 ethernet sometimes doesn't work after cold boot/boot Status in linux package in Ubuntu: Confirmed Bug description: Whenever the computer is rebooted there is a roughly 50% chance that the r8169 ethernet cannot negotiate a link. There is no relevant information in dmesg except for the "link down" message. The work around is to just keep rebooting the computer until it eventually works; sometimes this may take up to 7 reboots. The first set of attached log files were generated while the ethernet was working. The second set are generated on the 5.0 HWE kernel when the ethernet was NOT working. Note that this is a regression. Ubuntu 16.04 ran on this computer for three years without the ethernet doing this even once. Unloading and loading the r8169 module will eventually make it work. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-58-generic 4.15.0-58.64 ProcVersionSignature: Ubuntu 4.15.0-58.64-generic 4.15.18 Uname: Linux 4.15.0-58-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', '/dev/snd/pcmC2D0c', '/dev/snd/controlC2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/by-path', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu Aug 22 10:05:17 2019 HibernationDevice: RESUME=UUID=4ab51820-6203-45a8-a04d-07946b0fbe56 InstallationDate: Installed on 2013-12-22 (2068 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: ASUS All Series ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-58-generic root=UUID=e1e7d1a7-19e8-4203-ad6a-86a144db61bc ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-58-generic N/A linux-backports-modules-4.15.0-58-generic N/A linux-firmware 1.173.9 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2019-01-30 (203 days ago) dmi.bios.date: 06/18/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2201 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H87M-E dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2201:bd06/18/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH87M-E:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: al14985 F pulseaudio /dev/snd/controlC0: al14985 F pulseaudio /dev/snd/controlC1: al14985 F pulseaudio CurrentDesktop: Unity:Unity7:ubuntu DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=4ab51820-6203-45a8-a04d-07946b0fbe56 InstallationDate: Installed on 2013-12-22 (2068 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: ASUS All Series Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-25-generic root=UUID=e1e7d1a7-19e8-4203-ad6a-86a144db61bc ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-25.26~18.04.1-generic 5.0.18 RelatedPackageVersions: linux-restricted-modules-5.0.0-25-generic N/A linux-backports-modules-5.0.0-25-generic N/A linux-firmware1.173.9 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 5.0.0-25-generic x86_64 UpgradeStatus: Upgraded to bionic on 2019-01-30 (203 days ago) UserGroups: adm lpadmin sambashare sudo _MarkForUpload: True dmi.bios.date: 06/18/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2201 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H87M-E dmi.board.vendor: ASUSTeK
[Kernel-packages] [Bug 1841040] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1841040/+attachment/5283947/+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/1841040 Title: r8169 ethernet sometimes doesn't work after cold boot/boot Status in linux package in Ubuntu: Confirmed Bug description: Whenever the computer is rebooted there is a roughly 50% chance that the r8169 ethernet cannot negotiate a link. There is no relevant information in dmesg except for the "link down" message. The work around is to just keep rebooting the computer until it eventually works; sometimes this may take up to 7 reboots. The first set of attached log files were generated while the ethernet was working. The second set are generated on the 5.0 HWE kernel when the ethernet was NOT working. Note that this is a regression. Ubuntu 16.04 ran on this computer for three years without the ethernet doing this even once. Unloading and loading the r8169 module will eventually make it work. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-58-generic 4.15.0-58.64 ProcVersionSignature: Ubuntu 4.15.0-58.64-generic 4.15.18 Uname: Linux 4.15.0-58-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', '/dev/snd/pcmC2D0c', '/dev/snd/controlC2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/by-path', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu Aug 22 10:05:17 2019 HibernationDevice: RESUME=UUID=4ab51820-6203-45a8-a04d-07946b0fbe56 InstallationDate: Installed on 2013-12-22 (2068 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: ASUS All Series ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-58-generic root=UUID=e1e7d1a7-19e8-4203-ad6a-86a144db61bc ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-58-generic N/A linux-backports-modules-4.15.0-58-generic N/A linux-firmware 1.173.9 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2019-01-30 (203 days ago) dmi.bios.date: 06/18/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2201 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H87M-E dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2201:bd06/18/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH87M-E:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: al14985 F pulseaudio /dev/snd/controlC0: al14985 F pulseaudio /dev/snd/controlC1: al14985 F pulseaudio CurrentDesktop: Unity:Unity7:ubuntu DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=4ab51820-6203-45a8-a04d-07946b0fbe56 InstallationDate: Installed on 2013-12-22 (2068 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: ASUS All Series Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-25-generic root=UUID=e1e7d1a7-19e8-4203-ad6a-86a144db61bc ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-25.26~18.04.1-generic 5.0.18 RelatedPackageVersions: linux-restricted-modules-5.0.0-25-generic N/A linux-backports-modules-5.0.0-25-generic N/A linux-firmware1.173.9 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 5.0.0-25-generic x86_64 UpgradeStatus: Upgraded to bionic on 2019-01-30 (203 days ago) UserGroups: adm lpadmin sambashare sudo _MarkForUpload: True dmi.bios.date: 06/18/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2201 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H87M-E dmi.board.vendor: ASUSTeK COMPUTER INC.
[Kernel-packages] [Bug 1841040] Re: r8169 ethernet sometimes doesn't work after cold boot/boot
apport information ** Tags added: apport-collected ** Description changed: Whenever the computer is rebooted there is a roughly 50% chance that the r8169 ethernet cannot negotiate a link. There is no relevant information in dmesg except for the "link down" message. The work around is to just keep rebooting the computer until it eventually works; sometimes this may take up to 7 reboots. The attached log files were generated while the ethernet was working. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-58-generic 4.15.0-58.64 ProcVersionSignature: Ubuntu 4.15.0-58.64-generic 4.15.18 Uname: Linux 4.15.0-58-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', '/dev/snd/pcmC2D0c', '/dev/snd/controlC2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/by-path', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu Aug 22 10:05:17 2019 HibernationDevice: RESUME=UUID=4ab51820-6203-45a8-a04d-07946b0fbe56 InstallationDate: Installed on 2013-12-22 (2068 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: ASUS All Series ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-58-generic root=UUID=e1e7d1a7-19e8-4203-ad6a-86a144db61bc ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-58-generic N/A linux-backports-modules-4.15.0-58-generic N/A linux-firmware 1.173.9 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2019-01-30 (203 days ago) dmi.bios.date: 06/18/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2201 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H87M-E dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2201:bd06/18/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH87M-E:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.7 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC2: al14985 F pulseaudio + /dev/snd/controlC0: al14985 F pulseaudio + /dev/snd/controlC1: al14985 F pulseaudio + CurrentDesktop: Unity:Unity7:ubuntu + DistroRelease: Ubuntu 18.04 + HibernationDevice: RESUME=UUID=4ab51820-6203-45a8-a04d-07946b0fbe56 + InstallationDate: Installed on 2013-12-22 (2068 days ago) + InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) + MachineType: ASUS All Series + Package: linux (not installed) + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-25-generic root=UUID=e1e7d1a7-19e8-4203-ad6a-86a144db61bc ro quiet splash vt.handoff=1 + ProcVersionSignature: Ubuntu 5.0.0-25.26~18.04.1-generic 5.0.18 + RelatedPackageVersions: + linux-restricted-modules-5.0.0-25-generic N/A + linux-backports-modules-5.0.0-25-generic N/A + linux-firmware1.173.9 + RfKill: + 0: phy0: Wireless LAN + Soft blocked: no + Hard blocked: no + Tags: bionic + Uname: Linux 5.0.0-25-generic x86_64 + UpgradeStatus: Upgraded to bionic on 2019-01-30 (203 days ago) + UserGroups: adm lpadmin sambashare sudo + _MarkForUpload: True + dmi.bios.date: 06/18/2015 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: 2201 + dmi.board.asset.tag: To be filled by O.E.M. + dmi.board.name: H87M-E + dmi.board.vendor: ASUSTeK COMPUTER INC. + dmi.board.version: Rev X.0x + dmi.chassis.asset.tag: Asset-1234567890 + dmi.chassis.type: 3 + dmi.chassis.vendor: Chassis Manufacture + dmi.chassis.version: Chassis Version + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2201:bd06/18/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH87M-E:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: + dmi.product.family: ASUS MB + dmi.product.name: All Series + dmi.product.sku: All + dmi.product.version: System Version + dmi.sys.vendor: ASUS ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1841040/+attachment/5283946/+files/AlsaInfo.txt -- You re
[Kernel-packages] [Bug 1841040] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1841040/+attachment/5283954/+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/1841040 Title: r8169 ethernet sometimes doesn't work after cold boot/boot Status in linux package in Ubuntu: Confirmed Bug description: Whenever the computer is rebooted there is a roughly 50% chance that the r8169 ethernet cannot negotiate a link. There is no relevant information in dmesg except for the "link down" message. The work around is to just keep rebooting the computer until it eventually works; sometimes this may take up to 7 reboots. The first set of attached log files were generated while the ethernet was working. The second set are generated on the 5.0 HWE kernel when the ethernet was NOT working. Note that this is a regression. Ubuntu 16.04 ran on this computer for three years without the ethernet doing this even once. Unloading and loading the r8169 module will eventually make it work. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-58-generic 4.15.0-58.64 ProcVersionSignature: Ubuntu 4.15.0-58.64-generic 4.15.18 Uname: Linux 4.15.0-58-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', '/dev/snd/pcmC2D0c', '/dev/snd/controlC2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/by-path', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu Aug 22 10:05:17 2019 HibernationDevice: RESUME=UUID=4ab51820-6203-45a8-a04d-07946b0fbe56 InstallationDate: Installed on 2013-12-22 (2068 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: ASUS All Series ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-58-generic root=UUID=e1e7d1a7-19e8-4203-ad6a-86a144db61bc ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-58-generic N/A linux-backports-modules-4.15.0-58-generic N/A linux-firmware 1.173.9 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2019-01-30 (203 days ago) dmi.bios.date: 06/18/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2201 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H87M-E dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2201:bd06/18/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH87M-E:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: al14985 F pulseaudio /dev/snd/controlC0: al14985 F pulseaudio /dev/snd/controlC1: al14985 F pulseaudio CurrentDesktop: Unity:Unity7:ubuntu DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=4ab51820-6203-45a8-a04d-07946b0fbe56 InstallationDate: Installed on 2013-12-22 (2068 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: ASUS All Series Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-25-generic root=UUID=e1e7d1a7-19e8-4203-ad6a-86a144db61bc ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-25.26~18.04.1-generic 5.0.18 RelatedPackageVersions: linux-restricted-modules-5.0.0-25-generic N/A linux-backports-modules-5.0.0-25-generic N/A linux-firmware1.173.9 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 5.0.0-25-generic x86_64 UpgradeStatus: Upgraded to bionic on 2019-01-30 (203 days ago) UserGroups: adm lpadmin sambashare sudo _MarkForUpload: True dmi.bios.date: 06/18/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2201 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H87M-E dmi.board.vendor: ASUSTeK
[Kernel-packages] [Bug 1841040] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1841040/+attachment/5283948/+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/1841040 Title: r8169 ethernet sometimes doesn't work after cold boot/boot Status in linux package in Ubuntu: Confirmed Bug description: Whenever the computer is rebooted there is a roughly 50% chance that the r8169 ethernet cannot negotiate a link. There is no relevant information in dmesg except for the "link down" message. The work around is to just keep rebooting the computer until it eventually works; sometimes this may take up to 7 reboots. The first set of attached log files were generated while the ethernet was working. The second set are generated on the 5.0 HWE kernel when the ethernet was NOT working. Note that this is a regression. Ubuntu 16.04 ran on this computer for three years without the ethernet doing this even once. Unloading and loading the r8169 module will eventually make it work. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-58-generic 4.15.0-58.64 ProcVersionSignature: Ubuntu 4.15.0-58.64-generic 4.15.18 Uname: Linux 4.15.0-58-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', '/dev/snd/pcmC2D0c', '/dev/snd/controlC2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/by-path', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu Aug 22 10:05:17 2019 HibernationDevice: RESUME=UUID=4ab51820-6203-45a8-a04d-07946b0fbe56 InstallationDate: Installed on 2013-12-22 (2068 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: ASUS All Series ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-58-generic root=UUID=e1e7d1a7-19e8-4203-ad6a-86a144db61bc ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-58-generic N/A linux-backports-modules-4.15.0-58-generic N/A linux-firmware 1.173.9 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2019-01-30 (203 days ago) dmi.bios.date: 06/18/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2201 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H87M-E dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2201:bd06/18/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH87M-E:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: al14985 F pulseaudio /dev/snd/controlC0: al14985 F pulseaudio /dev/snd/controlC1: al14985 F pulseaudio CurrentDesktop: Unity:Unity7:ubuntu DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=4ab51820-6203-45a8-a04d-07946b0fbe56 InstallationDate: Installed on 2013-12-22 (2068 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: ASUS All Series Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-25-generic root=UUID=e1e7d1a7-19e8-4203-ad6a-86a144db61bc ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-25.26~18.04.1-generic 5.0.18 RelatedPackageVersions: linux-restricted-modules-5.0.0-25-generic N/A linux-backports-modules-5.0.0-25-generic N/A linux-firmware1.173.9 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 5.0.0-25-generic x86_64 UpgradeStatus: Upgraded to bionic on 2019-01-30 (203 days ago) UserGroups: adm lpadmin sambashare sudo _MarkForUpload: True dmi.bios.date: 06/18/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2201 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H87M-E dmi.board.vendor: ASUSTe
[Kernel-packages] [Bug 1841040] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1841040/+attachment/5283949/+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/1841040 Title: r8169 ethernet sometimes doesn't work after cold boot/boot Status in linux package in Ubuntu: Confirmed Bug description: Whenever the computer is rebooted there is a roughly 50% chance that the r8169 ethernet cannot negotiate a link. There is no relevant information in dmesg except for the "link down" message. The work around is to just keep rebooting the computer until it eventually works; sometimes this may take up to 7 reboots. The first set of attached log files were generated while the ethernet was working. The second set are generated on the 5.0 HWE kernel when the ethernet was NOT working. Note that this is a regression. Ubuntu 16.04 ran on this computer for three years without the ethernet doing this even once. Unloading and loading the r8169 module will eventually make it work. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-58-generic 4.15.0-58.64 ProcVersionSignature: Ubuntu 4.15.0-58.64-generic 4.15.18 Uname: Linux 4.15.0-58-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', '/dev/snd/pcmC2D0c', '/dev/snd/controlC2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/by-path', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu Aug 22 10:05:17 2019 HibernationDevice: RESUME=UUID=4ab51820-6203-45a8-a04d-07946b0fbe56 InstallationDate: Installed on 2013-12-22 (2068 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: ASUS All Series ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-58-generic root=UUID=e1e7d1a7-19e8-4203-ad6a-86a144db61bc ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-58-generic N/A linux-backports-modules-4.15.0-58-generic N/A linux-firmware 1.173.9 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2019-01-30 (203 days ago) dmi.bios.date: 06/18/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2201 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H87M-E dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2201:bd06/18/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH87M-E:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: al14985 F pulseaudio /dev/snd/controlC0: al14985 F pulseaudio /dev/snd/controlC1: al14985 F pulseaudio CurrentDesktop: Unity:Unity7:ubuntu DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=4ab51820-6203-45a8-a04d-07946b0fbe56 InstallationDate: Installed on 2013-12-22 (2068 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: ASUS All Series Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-25-generic root=UUID=e1e7d1a7-19e8-4203-ad6a-86a144db61bc ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-25.26~18.04.1-generic 5.0.18 RelatedPackageVersions: linux-restricted-modules-5.0.0-25-generic N/A linux-backports-modules-5.0.0-25-generic N/A linux-firmware1.173.9 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 5.0.0-25-generic x86_64 UpgradeStatus: Upgraded to bionic on 2019-01-30 (203 days ago) UserGroups: adm lpadmin sambashare sudo _MarkForUpload: True dmi.bios.date: 06/18/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2201 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H87M-E dmi.board.vendor: ASUSTeK COMPUT
[Kernel-packages] [Bug 1841040] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1841040/+attachment/5283951/+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/1841040 Title: r8169 ethernet sometimes doesn't work after cold boot/boot Status in linux package in Ubuntu: Confirmed Bug description: Whenever the computer is rebooted there is a roughly 50% chance that the r8169 ethernet cannot negotiate a link. There is no relevant information in dmesg except for the "link down" message. The work around is to just keep rebooting the computer until it eventually works; sometimes this may take up to 7 reboots. The first set of attached log files were generated while the ethernet was working. The second set are generated on the 5.0 HWE kernel when the ethernet was NOT working. Note that this is a regression. Ubuntu 16.04 ran on this computer for three years without the ethernet doing this even once. Unloading and loading the r8169 module will eventually make it work. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-58-generic 4.15.0-58.64 ProcVersionSignature: Ubuntu 4.15.0-58.64-generic 4.15.18 Uname: Linux 4.15.0-58-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', '/dev/snd/pcmC2D0c', '/dev/snd/controlC2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/by-path', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu Aug 22 10:05:17 2019 HibernationDevice: RESUME=UUID=4ab51820-6203-45a8-a04d-07946b0fbe56 InstallationDate: Installed on 2013-12-22 (2068 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: ASUS All Series ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-58-generic root=UUID=e1e7d1a7-19e8-4203-ad6a-86a144db61bc ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-58-generic N/A linux-backports-modules-4.15.0-58-generic N/A linux-firmware 1.173.9 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2019-01-30 (203 days ago) dmi.bios.date: 06/18/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2201 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H87M-E dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2201:bd06/18/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH87M-E:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: al14985 F pulseaudio /dev/snd/controlC0: al14985 F pulseaudio /dev/snd/controlC1: al14985 F pulseaudio CurrentDesktop: Unity:Unity7:ubuntu DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=4ab51820-6203-45a8-a04d-07946b0fbe56 InstallationDate: Installed on 2013-12-22 (2068 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: ASUS All Series Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-25-generic root=UUID=e1e7d1a7-19e8-4203-ad6a-86a144db61bc ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-25.26~18.04.1-generic 5.0.18 RelatedPackageVersions: linux-restricted-modules-5.0.0-25-generic N/A linux-backports-modules-5.0.0-25-generic N/A linux-firmware1.173.9 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 5.0.0-25-generic x86_64 UpgradeStatus: Upgraded to bionic on 2019-01-30 (203 days ago) UserGroups: adm lpadmin sambashare sudo _MarkForUpload: True dmi.bios.date: 06/18/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2201 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H87M-E dmi.board.vendor: ASUSTeK COMPUTER INC.
[Kernel-packages] [Bug 1841040] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1841040/+attachment/5283959/+files/WifiSyslog.txt ** Description changed: Whenever the computer is rebooted there is a roughly 50% chance that the r8169 ethernet cannot negotiate a link. There is no relevant information in dmesg except for the "link down" message. The work around is to just keep rebooting the computer until it eventually works; sometimes this may take up to 7 reboots. - The attached log files were generated while the ethernet was working. + The first set of attached log files were generated while the ethernet + was working. + + The second set are generated on the 5.0 HWE kernel when the ethernet was + NOT working. + + Note that this is a regression. Ubuntu 16.04 ran on this computer for + three years without the ethernet doing this even once. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-58-generic 4.15.0-58.64 ProcVersionSignature: Ubuntu 4.15.0-58.64-generic 4.15.18 Uname: Linux 4.15.0-58-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', '/dev/snd/pcmC2D0c', '/dev/snd/controlC2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/by-path', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu Aug 22 10:05:17 2019 HibernationDevice: RESUME=UUID=4ab51820-6203-45a8-a04d-07946b0fbe56 InstallationDate: Installed on 2013-12-22 (2068 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: ASUS All Series ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-58-generic root=UUID=e1e7d1a7-19e8-4203-ad6a-86a144db61bc ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-58-generic N/A linux-backports-modules-4.15.0-58-generic N/A linux-firmware 1.173.9 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2019-01-30 (203 days ago) dmi.bios.date: 06/18/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2201 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H87M-E dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2201:bd06/18/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH87M-E:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS - --- + --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC2: al14985 F pulseaudio - /dev/snd/controlC0: al14985 F pulseaudio - /dev/snd/controlC1: al14985 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC2: al14985 F pulseaudio + /dev/snd/controlC0: al14985 F pulseaudio + /dev/snd/controlC1: al14985 F pulseaudio CurrentDesktop: Unity:Unity7:ubuntu DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=4ab51820-6203-45a8-a04d-07946b0fbe56 InstallationDate: Installed on 2013-12-22 (2068 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: ASUS All Series Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-25-generic root=UUID=e1e7d1a7-19e8-4203-ad6a-86a144db61bc ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-25.26~18.04.1-generic 5.0.18 RelatedPackageVersions: - linux-restricted-modules-5.0.0-25-generic N/A - linux-backports-modules-5.0.0-25-generic N/A - linux-firmware1.173.9 + linux-restricted-modules-5.0.0-25-generic N/A + linux-backports-modules-5.0.0-25-generic N/A + linux-firmware1.173.9 RfKill: - 0: phy0: Wireless LAN - Soft blocked: no - Hard blocked: no + 0: phy0: Wireless LAN + Soft blocked: no + Hard blocked: no Tags: bionic Uname: Linux 5.0.0-25-generic x86_64 UpgradeStatus: Upgraded to bionic on 2019-01-30 (203 days ago) UserGroups: adm lpadmin sambashare sudo _MarkForUpload: True dmi.bios.date: 06/18
[Kernel-packages] [Bug 1841040] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1841040/+attachment/5283957/+files/PulseList.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/1841040 Title: r8169 ethernet sometimes doesn't work after cold boot/boot Status in linux package in Ubuntu: Confirmed Bug description: Whenever the computer is rebooted there is a roughly 50% chance that the r8169 ethernet cannot negotiate a link. There is no relevant information in dmesg except for the "link down" message. The work around is to just keep rebooting the computer until it eventually works; sometimes this may take up to 7 reboots. The first set of attached log files were generated while the ethernet was working. The second set are generated on the 5.0 HWE kernel when the ethernet was NOT working. Note that this is a regression. Ubuntu 16.04 ran on this computer for three years without the ethernet doing this even once. Unloading and loading the r8169 module will eventually make it work. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-58-generic 4.15.0-58.64 ProcVersionSignature: Ubuntu 4.15.0-58.64-generic 4.15.18 Uname: Linux 4.15.0-58-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', '/dev/snd/pcmC2D0c', '/dev/snd/controlC2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/by-path', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu Aug 22 10:05:17 2019 HibernationDevice: RESUME=UUID=4ab51820-6203-45a8-a04d-07946b0fbe56 InstallationDate: Installed on 2013-12-22 (2068 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: ASUS All Series ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-58-generic root=UUID=e1e7d1a7-19e8-4203-ad6a-86a144db61bc ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-58-generic N/A linux-backports-modules-4.15.0-58-generic N/A linux-firmware 1.173.9 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2019-01-30 (203 days ago) dmi.bios.date: 06/18/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2201 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H87M-E dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2201:bd06/18/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH87M-E:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: al14985 F pulseaudio /dev/snd/controlC0: al14985 F pulseaudio /dev/snd/controlC1: al14985 F pulseaudio CurrentDesktop: Unity:Unity7:ubuntu DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=4ab51820-6203-45a8-a04d-07946b0fbe56 InstallationDate: Installed on 2013-12-22 (2068 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: ASUS All Series Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-25-generic root=UUID=e1e7d1a7-19e8-4203-ad6a-86a144db61bc ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-25.26~18.04.1-generic 5.0.18 RelatedPackageVersions: linux-restricted-modules-5.0.0-25-generic N/A linux-backports-modules-5.0.0-25-generic N/A linux-firmware1.173.9 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 5.0.0-25-generic x86_64 UpgradeStatus: Upgraded to bionic on 2019-01-30 (203 days ago) UserGroups: adm lpadmin sambashare sudo _MarkForUpload: True dmi.bios.date: 06/18/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2201 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H87M-E dmi.board.vendor: ASUSTeK COMP
[Kernel-packages] [Bug 1841040] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1841040/+attachment/5283953/+files/ProcCpuinfoMinimal.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/1841040 Title: r8169 ethernet sometimes doesn't work after cold boot/boot Status in linux package in Ubuntu: Confirmed Bug description: Whenever the computer is rebooted there is a roughly 50% chance that the r8169 ethernet cannot negotiate a link. There is no relevant information in dmesg except for the "link down" message. The work around is to just keep rebooting the computer until it eventually works; sometimes this may take up to 7 reboots. The first set of attached log files were generated while the ethernet was working. The second set are generated on the 5.0 HWE kernel when the ethernet was NOT working. Note that this is a regression. Ubuntu 16.04 ran on this computer for three years without the ethernet doing this even once. Unloading and loading the r8169 module will eventually make it work. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-58-generic 4.15.0-58.64 ProcVersionSignature: Ubuntu 4.15.0-58.64-generic 4.15.18 Uname: Linux 4.15.0-58-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', '/dev/snd/pcmC2D0c', '/dev/snd/controlC2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/by-path', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu Aug 22 10:05:17 2019 HibernationDevice: RESUME=UUID=4ab51820-6203-45a8-a04d-07946b0fbe56 InstallationDate: Installed on 2013-12-22 (2068 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: ASUS All Series ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-58-generic root=UUID=e1e7d1a7-19e8-4203-ad6a-86a144db61bc ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-58-generic N/A linux-backports-modules-4.15.0-58-generic N/A linux-firmware 1.173.9 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2019-01-30 (203 days ago) dmi.bios.date: 06/18/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2201 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H87M-E dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2201:bd06/18/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH87M-E:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: al14985 F pulseaudio /dev/snd/controlC0: al14985 F pulseaudio /dev/snd/controlC1: al14985 F pulseaudio CurrentDesktop: Unity:Unity7:ubuntu DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=4ab51820-6203-45a8-a04d-07946b0fbe56 InstallationDate: Installed on 2013-12-22 (2068 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: ASUS All Series Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-25-generic root=UUID=e1e7d1a7-19e8-4203-ad6a-86a144db61bc ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-25.26~18.04.1-generic 5.0.18 RelatedPackageVersions: linux-restricted-modules-5.0.0-25-generic N/A linux-backports-modules-5.0.0-25-generic N/A linux-firmware1.173.9 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 5.0.0-25-generic x86_64 UpgradeStatus: Upgraded to bionic on 2019-01-30 (203 days ago) UserGroups: adm lpadmin sambashare sudo _MarkForUpload: True dmi.bios.date: 06/18/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2201 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H87M-E dmi.board.ve
[Kernel-packages] [Bug 1841040] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1841040/+attachment/5283950/+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/1841040 Title: r8169 ethernet sometimes doesn't work after cold boot/boot Status in linux package in Ubuntu: Confirmed Bug description: Whenever the computer is rebooted there is a roughly 50% chance that the r8169 ethernet cannot negotiate a link. There is no relevant information in dmesg except for the "link down" message. The work around is to just keep rebooting the computer until it eventually works; sometimes this may take up to 7 reboots. The first set of attached log files were generated while the ethernet was working. The second set are generated on the 5.0 HWE kernel when the ethernet was NOT working. Note that this is a regression. Ubuntu 16.04 ran on this computer for three years without the ethernet doing this even once. Unloading and loading the r8169 module will eventually make it work. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-58-generic 4.15.0-58.64 ProcVersionSignature: Ubuntu 4.15.0-58.64-generic 4.15.18 Uname: Linux 4.15.0-58-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', '/dev/snd/pcmC2D0c', '/dev/snd/controlC2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/by-path', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu Aug 22 10:05:17 2019 HibernationDevice: RESUME=UUID=4ab51820-6203-45a8-a04d-07946b0fbe56 InstallationDate: Installed on 2013-12-22 (2068 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: ASUS All Series ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-58-generic root=UUID=e1e7d1a7-19e8-4203-ad6a-86a144db61bc ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-58-generic N/A linux-backports-modules-4.15.0-58-generic N/A linux-firmware 1.173.9 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2019-01-30 (203 days ago) dmi.bios.date: 06/18/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2201 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H87M-E dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2201:bd06/18/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH87M-E:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: al14985 F pulseaudio /dev/snd/controlC0: al14985 F pulseaudio /dev/snd/controlC1: al14985 F pulseaudio CurrentDesktop: Unity:Unity7:ubuntu DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=4ab51820-6203-45a8-a04d-07946b0fbe56 InstallationDate: Installed on 2013-12-22 (2068 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: ASUS All Series Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-25-generic root=UUID=e1e7d1a7-19e8-4203-ad6a-86a144db61bc ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-25.26~18.04.1-generic 5.0.18 RelatedPackageVersions: linux-restricted-modules-5.0.0-25-generic N/A linux-backports-modules-5.0.0-25-generic N/A linux-firmware1.173.9 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 5.0.0-25-generic x86_64 UpgradeStatus: Upgraded to bionic on 2019-01-30 (203 days ago) UserGroups: adm lpadmin sambashare sudo _MarkForUpload: True dmi.bios.date: 06/18/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2201 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H87M-E dmi.board.vendor: ASUSTeK COMPUTER INC.
[Kernel-packages] [Bug 1841040] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1841040/+attachment/5283956/+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/1841040 Title: r8169 ethernet sometimes doesn't work after cold boot/boot Status in linux package in Ubuntu: Confirmed Bug description: Whenever the computer is rebooted there is a roughly 50% chance that the r8169 ethernet cannot negotiate a link. There is no relevant information in dmesg except for the "link down" message. The work around is to just keep rebooting the computer until it eventually works; sometimes this may take up to 7 reboots. The first set of attached log files were generated while the ethernet was working. The second set are generated on the 5.0 HWE kernel when the ethernet was NOT working. Note that this is a regression. Ubuntu 16.04 ran on this computer for three years without the ethernet doing this even once. Unloading and loading the r8169 module will eventually make it work. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-58-generic 4.15.0-58.64 ProcVersionSignature: Ubuntu 4.15.0-58.64-generic 4.15.18 Uname: Linux 4.15.0-58-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', '/dev/snd/pcmC2D0c', '/dev/snd/controlC2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/by-path', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu Aug 22 10:05:17 2019 HibernationDevice: RESUME=UUID=4ab51820-6203-45a8-a04d-07946b0fbe56 InstallationDate: Installed on 2013-12-22 (2068 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: ASUS All Series ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-58-generic root=UUID=e1e7d1a7-19e8-4203-ad6a-86a144db61bc ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-58-generic N/A linux-backports-modules-4.15.0-58-generic N/A linux-firmware 1.173.9 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2019-01-30 (203 days ago) dmi.bios.date: 06/18/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2201 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H87M-E dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2201:bd06/18/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH87M-E:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: al14985 F pulseaudio /dev/snd/controlC0: al14985 F pulseaudio /dev/snd/controlC1: al14985 F pulseaudio CurrentDesktop: Unity:Unity7:ubuntu DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=4ab51820-6203-45a8-a04d-07946b0fbe56 InstallationDate: Installed on 2013-12-22 (2068 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: ASUS All Series Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-25-generic root=UUID=e1e7d1a7-19e8-4203-ad6a-86a144db61bc ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-25.26~18.04.1-generic 5.0.18 RelatedPackageVersions: linux-restricted-modules-5.0.0-25-generic N/A linux-backports-modules-5.0.0-25-generic N/A linux-firmware1.173.9 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 5.0.0-25-generic x86_64 UpgradeStatus: Upgraded to bionic on 2019-01-30 (203 days ago) UserGroups: adm lpadmin sambashare sudo _MarkForUpload: True dmi.bios.date: 06/18/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2201 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H87M-E dmi.board.vendor: ASUSTeK
[Kernel-packages] [Bug 1841040] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1841040/+attachment/5283958/+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/1841040 Title: r8169 ethernet sometimes doesn't work after cold boot/boot Status in linux package in Ubuntu: Confirmed Bug description: Whenever the computer is rebooted there is a roughly 50% chance that the r8169 ethernet cannot negotiate a link. There is no relevant information in dmesg except for the "link down" message. The work around is to just keep rebooting the computer until it eventually works; sometimes this may take up to 7 reboots. The first set of attached log files were generated while the ethernet was working. The second set are generated on the 5.0 HWE kernel when the ethernet was NOT working. Note that this is a regression. Ubuntu 16.04 ran on this computer for three years without the ethernet doing this even once. Unloading and loading the r8169 module will eventually make it work. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-58-generic 4.15.0-58.64 ProcVersionSignature: Ubuntu 4.15.0-58.64-generic 4.15.18 Uname: Linux 4.15.0-58-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', '/dev/snd/pcmC2D0c', '/dev/snd/controlC2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/by-path', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu Aug 22 10:05:17 2019 HibernationDevice: RESUME=UUID=4ab51820-6203-45a8-a04d-07946b0fbe56 InstallationDate: Installed on 2013-12-22 (2068 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: ASUS All Series ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-58-generic root=UUID=e1e7d1a7-19e8-4203-ad6a-86a144db61bc ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-58-generic N/A linux-backports-modules-4.15.0-58-generic N/A linux-firmware 1.173.9 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2019-01-30 (203 days ago) dmi.bios.date: 06/18/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2201 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H87M-E dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2201:bd06/18/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH87M-E:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: al14985 F pulseaudio /dev/snd/controlC0: al14985 F pulseaudio /dev/snd/controlC1: al14985 F pulseaudio CurrentDesktop: Unity:Unity7:ubuntu DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=4ab51820-6203-45a8-a04d-07946b0fbe56 InstallationDate: Installed on 2013-12-22 (2068 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: ASUS All Series Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-25-generic root=UUID=e1e7d1a7-19e8-4203-ad6a-86a144db61bc ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-25.26~18.04.1-generic 5.0.18 RelatedPackageVersions: linux-restricted-modules-5.0.0-25-generic N/A linux-backports-modules-5.0.0-25-generic N/A linux-firmware1.173.9 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 5.0.0-25-generic x86_64 UpgradeStatus: Upgraded to bionic on 2019-01-30 (203 days ago) UserGroups: adm lpadmin sambashare sudo _MarkForUpload: True dmi.bios.date: 06/18/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2201 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H87M-E dmi.board.vendor: ASUSTeK COMPUTER IN
[Kernel-packages] [Bug 1841040] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1841040/+attachment/5283955/+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/1841040 Title: r8169 ethernet sometimes doesn't work after cold boot/boot Status in linux package in Ubuntu: Confirmed Bug description: Whenever the computer is rebooted there is a roughly 50% chance that the r8169 ethernet cannot negotiate a link. There is no relevant information in dmesg except for the "link down" message. The work around is to just keep rebooting the computer until it eventually works; sometimes this may take up to 7 reboots. The first set of attached log files were generated while the ethernet was working. The second set are generated on the 5.0 HWE kernel when the ethernet was NOT working. Note that this is a regression. Ubuntu 16.04 ran on this computer for three years without the ethernet doing this even once. Unloading and loading the r8169 module will eventually make it work. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-58-generic 4.15.0-58.64 ProcVersionSignature: Ubuntu 4.15.0-58.64-generic 4.15.18 Uname: Linux 4.15.0-58-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', '/dev/snd/pcmC2D0c', '/dev/snd/controlC2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/by-path', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu Aug 22 10:05:17 2019 HibernationDevice: RESUME=UUID=4ab51820-6203-45a8-a04d-07946b0fbe56 InstallationDate: Installed on 2013-12-22 (2068 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: ASUS All Series ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-58-generic root=UUID=e1e7d1a7-19e8-4203-ad6a-86a144db61bc ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-58-generic N/A linux-backports-modules-4.15.0-58-generic N/A linux-firmware 1.173.9 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2019-01-30 (203 days ago) dmi.bios.date: 06/18/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2201 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H87M-E dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2201:bd06/18/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH87M-E:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: al14985 F pulseaudio /dev/snd/controlC0: al14985 F pulseaudio /dev/snd/controlC1: al14985 F pulseaudio CurrentDesktop: Unity:Unity7:ubuntu DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=4ab51820-6203-45a8-a04d-07946b0fbe56 InstallationDate: Installed on 2013-12-22 (2068 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: ASUS All Series Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-25-generic root=UUID=e1e7d1a7-19e8-4203-ad6a-86a144db61bc ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-25.26~18.04.1-generic 5.0.18 RelatedPackageVersions: linux-restricted-modules-5.0.0-25-generic N/A linux-backports-modules-5.0.0-25-generic N/A linux-firmware1.173.9 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 5.0.0-25-generic x86_64 UpgradeStatus: Upgraded to bionic on 2019-01-30 (203 days ago) UserGroups: adm lpadmin sambashare sudo _MarkForUpload: True dmi.bios.date: 06/18/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2201 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H87M-E dmi.board.vendor: AS
[Kernel-packages] [Bug 1841040] Re: r8169 ethernet sometimes doesn't work after cold boot/boot
I am not able to test that kernel as it is not signed. -- 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/1841040 Title: r8169 ethernet sometimes doesn't work after cold boot/boot Status in linux package in Ubuntu: Confirmed Bug description: Whenever the computer is rebooted there is a roughly 50% chance that the r8169 ethernet cannot negotiate a link. There is no relevant information in dmesg except for the "link down" message. The work around is to just keep rebooting the computer until it eventually works; sometimes this may take up to 7 reboots. The first set of attached log files were generated while the ethernet was working. The second set are generated on the 5.0 HWE kernel when the ethernet was NOT working. Note that this is a regression. Ubuntu 16.04 ran on this computer for three years without the ethernet doing this even once. Unloading and loading the r8169 module will eventually make it work. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-58-generic 4.15.0-58.64 ProcVersionSignature: Ubuntu 4.15.0-58.64-generic 4.15.18 Uname: Linux 4.15.0-58-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', '/dev/snd/pcmC2D0c', '/dev/snd/controlC2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/by-path', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu Aug 22 10:05:17 2019 HibernationDevice: RESUME=UUID=4ab51820-6203-45a8-a04d-07946b0fbe56 InstallationDate: Installed on 2013-12-22 (2068 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: ASUS All Series ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-58-generic root=UUID=e1e7d1a7-19e8-4203-ad6a-86a144db61bc ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-58-generic N/A linux-backports-modules-4.15.0-58-generic N/A linux-firmware 1.173.9 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2019-01-30 (203 days ago) dmi.bios.date: 06/18/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2201 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H87M-E dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2201:bd06/18/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH87M-E:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: al14985 F pulseaudio /dev/snd/controlC0: al14985 F pulseaudio /dev/snd/controlC1: al14985 F pulseaudio CurrentDesktop: Unity:Unity7:ubuntu DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=4ab51820-6203-45a8-a04d-07946b0fbe56 InstallationDate: Installed on 2013-12-22 (2068 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: ASUS All Series Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-25-generic root=UUID=e1e7d1a7-19e8-4203-ad6a-86a144db61bc ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-25.26~18.04.1-generic 5.0.18 RelatedPackageVersions: linux-restricted-modules-5.0.0-25-generic N/A linux-backports-modules-5.0.0-25-generic N/A linux-firmware1.173.9 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 5.0.0-25-generic x86_64 UpgradeStatus: Upgraded to bionic on 2019-01-30 (203 days ago) UserGroups: adm lpadmin sambashare sudo _MarkForUpload: True dmi.bios.date: 06/18/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2201 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H87M-E dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi
[Kernel-packages] [Bug 1841040] Re: r8169 ethernet sometimes doesn't work after cold boot/boot
I disabled secure boot and I was able to reproduce the problem with mainline on the first attempt. -- 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/1841040 Title: r8169 ethernet sometimes doesn't work after cold boot/boot Status in linux package in Ubuntu: Confirmed Bug description: Whenever the computer is rebooted there is a roughly 50% chance that the r8169 ethernet cannot negotiate a link. There is no relevant information in dmesg except for the "link down" message. The work around is to just keep rebooting the computer until it eventually works; sometimes this may take up to 7 reboots. The first set of attached log files were generated while the ethernet was working. The second set are generated on the 5.0 HWE kernel when the ethernet was NOT working. Note that this is a regression. Ubuntu 16.04 ran on this computer for three years without the ethernet doing this even once. Unloading and loading the r8169 module will eventually make it work. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-58-generic 4.15.0-58.64 ProcVersionSignature: Ubuntu 4.15.0-58.64-generic 4.15.18 Uname: Linux 4.15.0-58-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', '/dev/snd/pcmC2D0c', '/dev/snd/controlC2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/by-path', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu Aug 22 10:05:17 2019 HibernationDevice: RESUME=UUID=4ab51820-6203-45a8-a04d-07946b0fbe56 InstallationDate: Installed on 2013-12-22 (2068 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: ASUS All Series ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-58-generic root=UUID=e1e7d1a7-19e8-4203-ad6a-86a144db61bc ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-58-generic N/A linux-backports-modules-4.15.0-58-generic N/A linux-firmware 1.173.9 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2019-01-30 (203 days ago) dmi.bios.date: 06/18/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2201 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H87M-E dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2201:bd06/18/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH87M-E:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: al14985 F pulseaudio /dev/snd/controlC0: al14985 F pulseaudio /dev/snd/controlC1: al14985 F pulseaudio CurrentDesktop: Unity:Unity7:ubuntu DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=4ab51820-6203-45a8-a04d-07946b0fbe56 InstallationDate: Installed on 2013-12-22 (2068 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: ASUS All Series Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-25-generic root=UUID=e1e7d1a7-19e8-4203-ad6a-86a144db61bc ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-25.26~18.04.1-generic 5.0.18 RelatedPackageVersions: linux-restricted-modules-5.0.0-25-generic N/A linux-backports-modules-5.0.0-25-generic N/A linux-firmware1.173.9 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 5.0.0-25-generic x86_64 UpgradeStatus: Upgraded to bionic on 2019-01-30 (203 days ago) UserGroups: adm lpadmin sambashare sudo _MarkForUpload: True dmi.bios.date: 06/18/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2201 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H87M-E dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x d
[Kernel-packages] [Bug 1841040] Re: r8169 ethernet sometimes doesn't work after cold boot/boot
Why -rc? The last working kernel I know of is from the 4.4 series. -- 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/1841040 Title: r8169 ethernet sometimes doesn't work after cold boot/boot Status in linux package in Ubuntu: Confirmed Bug description: Whenever the computer is rebooted there is a roughly 50% chance that the r8169 ethernet cannot negotiate a link. There is no relevant information in dmesg except for the "link down" message. The work around is to just keep rebooting the computer until it eventually works; sometimes this may take up to 7 reboots. The first set of attached log files were generated while the ethernet was working. The second set are generated on the 5.0 HWE kernel when the ethernet was NOT working. Note that this is a regression. Ubuntu 16.04 ran on this computer for three years without the ethernet doing this even once. Unloading and loading the r8169 module will eventually make it work. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-58-generic 4.15.0-58.64 ProcVersionSignature: Ubuntu 4.15.0-58.64-generic 4.15.18 Uname: Linux 4.15.0-58-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', '/dev/snd/pcmC2D0c', '/dev/snd/controlC2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/by-path', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu Aug 22 10:05:17 2019 HibernationDevice: RESUME=UUID=4ab51820-6203-45a8-a04d-07946b0fbe56 InstallationDate: Installed on 2013-12-22 (2068 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: ASUS All Series ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-58-generic root=UUID=e1e7d1a7-19e8-4203-ad6a-86a144db61bc ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-58-generic N/A linux-backports-modules-4.15.0-58-generic N/A linux-firmware 1.173.9 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2019-01-30 (203 days ago) dmi.bios.date: 06/18/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2201 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H87M-E dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2201:bd06/18/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH87M-E:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: al14985 F pulseaudio /dev/snd/controlC0: al14985 F pulseaudio /dev/snd/controlC1: al14985 F pulseaudio CurrentDesktop: Unity:Unity7:ubuntu DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=4ab51820-6203-45a8-a04d-07946b0fbe56 InstallationDate: Installed on 2013-12-22 (2068 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: ASUS All Series Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-25-generic root=UUID=e1e7d1a7-19e8-4203-ad6a-86a144db61bc ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-25.26~18.04.1-generic 5.0.18 RelatedPackageVersions: linux-restricted-modules-5.0.0-25-generic N/A linux-backports-modules-5.0.0-25-generic N/A linux-firmware1.173.9 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 5.0.0-25-generic x86_64 UpgradeStatus: Upgraded to bionic on 2019-01-30 (203 days ago) UserGroups: adm lpadmin sambashare sudo _MarkForUpload: True dmi.bios.date: 06/18/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2201 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H87M-E dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234
[Kernel-packages] [Bug 1841040] Re: r8169 ethernet sometimes doesn't work after cold boot/boot
I am working on this but it is slow as the bug is difficult to reproduce. It seems to happen more often after cold boots. -- 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/1841040 Title: r8169 ethernet sometimes doesn't work after cold boot/boot Status in linux package in Ubuntu: Confirmed Bug description: Whenever the computer is rebooted there is a roughly 50% chance that the r8169 ethernet cannot negotiate a link. There is no relevant information in dmesg except for the "link down" message. The work around is to just keep rebooting the computer until it eventually works; sometimes this may take up to 7 reboots. The first set of attached log files were generated while the ethernet was working. The second set are generated on the 5.0 HWE kernel when the ethernet was NOT working. Note that this is a regression. Ubuntu 16.04 ran on this computer for three years without the ethernet doing this even once. Unloading and loading the r8169 module will eventually make it work. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-58-generic 4.15.0-58.64 ProcVersionSignature: Ubuntu 4.15.0-58.64-generic 4.15.18 Uname: Linux 4.15.0-58-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', '/dev/snd/pcmC2D0c', '/dev/snd/controlC2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/by-path', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu Aug 22 10:05:17 2019 HibernationDevice: RESUME=UUID=4ab51820-6203-45a8-a04d-07946b0fbe56 InstallationDate: Installed on 2013-12-22 (2068 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: ASUS All Series ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-58-generic root=UUID=e1e7d1a7-19e8-4203-ad6a-86a144db61bc ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-58-generic N/A linux-backports-modules-4.15.0-58-generic N/A linux-firmware 1.173.9 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2019-01-30 (203 days ago) dmi.bios.date: 06/18/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2201 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H87M-E dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2201:bd06/18/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH87M-E:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: al14985 F pulseaudio /dev/snd/controlC0: al14985 F pulseaudio /dev/snd/controlC1: al14985 F pulseaudio CurrentDesktop: Unity:Unity7:ubuntu DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=4ab51820-6203-45a8-a04d-07946b0fbe56 InstallationDate: Installed on 2013-12-22 (2068 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: ASUS All Series Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-25-generic root=UUID=e1e7d1a7-19e8-4203-ad6a-86a144db61bc ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-25.26~18.04.1-generic 5.0.18 RelatedPackageVersions: linux-restricted-modules-5.0.0-25-generic N/A linux-backports-modules-5.0.0-25-generic N/A linux-firmware1.173.9 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 5.0.0-25-generic x86_64 UpgradeStatus: Upgraded to bionic on 2019-01-30 (203 days ago) UserGroups: adm lpadmin sambashare sudo _MarkForUpload: True dmi.bios.date: 06/18/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2201 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H87M-E dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.boar
[Kernel-packages] [Bug 1841040] Re: r8169 ethernet sometimes doesn't work after cold boot/boot
(and by cold boots I mean very cold - like the computer has been switched off for several hours.) -- 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/1841040 Title: r8169 ethernet sometimes doesn't work after cold boot/boot Status in linux package in Ubuntu: Confirmed Bug description: Whenever the computer is rebooted there is a roughly 50% chance that the r8169 ethernet cannot negotiate a link. There is no relevant information in dmesg except for the "link down" message. The work around is to just keep rebooting the computer until it eventually works; sometimes this may take up to 7 reboots. The first set of attached log files were generated while the ethernet was working. The second set are generated on the 5.0 HWE kernel when the ethernet was NOT working. Note that this is a regression. Ubuntu 16.04 ran on this computer for three years without the ethernet doing this even once. Unloading and loading the r8169 module will eventually make it work. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-58-generic 4.15.0-58.64 ProcVersionSignature: Ubuntu 4.15.0-58.64-generic 4.15.18 Uname: Linux 4.15.0-58-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', '/dev/snd/pcmC2D0c', '/dev/snd/controlC2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/by-path', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu Aug 22 10:05:17 2019 HibernationDevice: RESUME=UUID=4ab51820-6203-45a8-a04d-07946b0fbe56 InstallationDate: Installed on 2013-12-22 (2068 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: ASUS All Series ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-58-generic root=UUID=e1e7d1a7-19e8-4203-ad6a-86a144db61bc ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-58-generic N/A linux-backports-modules-4.15.0-58-generic N/A linux-firmware 1.173.9 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2019-01-30 (203 days ago) dmi.bios.date: 06/18/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2201 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H87M-E dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2201:bd06/18/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH87M-E:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: al14985 F pulseaudio /dev/snd/controlC0: al14985 F pulseaudio /dev/snd/controlC1: al14985 F pulseaudio CurrentDesktop: Unity:Unity7:ubuntu DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=4ab51820-6203-45a8-a04d-07946b0fbe56 InstallationDate: Installed on 2013-12-22 (2068 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: ASUS All Series Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-25-generic root=UUID=e1e7d1a7-19e8-4203-ad6a-86a144db61bc ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-25.26~18.04.1-generic 5.0.18 RelatedPackageVersions: linux-restricted-modules-5.0.0-25-generic N/A linux-backports-modules-5.0.0-25-generic N/A linux-firmware1.173.9 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 5.0.0-25-generic x86_64 UpgradeStatus: Upgraded to bionic on 2019-01-30 (203 days ago) UserGroups: adm lpadmin sambashare sudo _MarkForUpload: True dmi.bios.date: 06/18/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2201 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H87M-E dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dm
[Kernel-packages] [Bug 1841040] Re: r8169 ethernet sometimes doesn't work after cold boot/boot
I have managed to reproduce this as far back as 2f34c1231bfc9f which is somewhere between 4.11 and 4.12rc1. I have been unable to reproduce it with 4.11, but this may just be due to bad luck. I will continue testing tomorrow. -- 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/1841040 Title: r8169 ethernet sometimes doesn't work after cold boot/boot Status in linux package in Ubuntu: Confirmed Bug description: Whenever the computer is rebooted there is a roughly 50% chance that the r8169 ethernet cannot negotiate a link. There is no relevant information in dmesg except for the "link down" message. The work around is to just keep rebooting the computer until it eventually works; sometimes this may take up to 7 reboots. The first set of attached log files were generated while the ethernet was working. The second set are generated on the 5.0 HWE kernel when the ethernet was NOT working. Note that this is a regression. Ubuntu 16.04 ran on this computer for three years without the ethernet doing this even once. Unloading and loading the r8169 module will eventually make it work. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-58-generic 4.15.0-58.64 ProcVersionSignature: Ubuntu 4.15.0-58.64-generic 4.15.18 Uname: Linux 4.15.0-58-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', '/dev/snd/pcmC2D0c', '/dev/snd/controlC2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/by-path', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu Aug 22 10:05:17 2019 HibernationDevice: RESUME=UUID=4ab51820-6203-45a8-a04d-07946b0fbe56 InstallationDate: Installed on 2013-12-22 (2068 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: ASUS All Series ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-58-generic root=UUID=e1e7d1a7-19e8-4203-ad6a-86a144db61bc ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-58-generic N/A linux-backports-modules-4.15.0-58-generic N/A linux-firmware 1.173.9 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2019-01-30 (203 days ago) dmi.bios.date: 06/18/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2201 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H87M-E dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2201:bd06/18/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH87M-E:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: al14985 F pulseaudio /dev/snd/controlC0: al14985 F pulseaudio /dev/snd/controlC1: al14985 F pulseaudio CurrentDesktop: Unity:Unity7:ubuntu DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=4ab51820-6203-45a8-a04d-07946b0fbe56 InstallationDate: Installed on 2013-12-22 (2068 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: ASUS All Series Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-25-generic root=UUID=e1e7d1a7-19e8-4203-ad6a-86a144db61bc ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-25.26~18.04.1-generic 5.0.18 RelatedPackageVersions: linux-restricted-modules-5.0.0-25-generic N/A linux-backports-modules-5.0.0-25-generic N/A linux-firmware1.173.9 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 5.0.0-25-generic x86_64 UpgradeStatus: Upgraded to bionic on 2019-01-30 (203 days ago) UserGroups: adm lpadmin sambashare sudo _MarkForUpload: True dmi.bios.date: 06/18/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2201 dmi.board.asset.t
[Kernel-packages] [Bug 1841040] Re: r8169 ethernet sometimes doesn't work after cold boot/boot
It is perhaps worth mentioning that there are only two patches to r8169
in this time frame:
commit 1bcf165ac6556dc55a596d524b8187d1ba7a8c7d
Author: Zhu Yanjun
Date: Sun Mar 12 05:02:54 2017 -0400
r8169: replace init_timer with setup_timer
Replace init_timer with setup_timer to simplify the source code.
Signed-off-by: Zhu Yanjun
Signed-off-by: David S. Miller
commit 6fa1ba61520576cf1346c4ff09a056f2950cb3bf
Author: Philippe Reynes
Date: Thu Feb 23 22:34:43 2017 +0100
net: realtek: r8169: use new api ethtool_{get|set}_link_ksettings
The ethtool api {get|set}_settings is deprecated.
We move this driver to new api {get|set}_link_ksettings.
As I don't have the hardware, I'd be very pleased if
someone may test this patch.
Signed-off-by: Philippe Reynes
Signed-off-by: David S. Miller
The difficulty of reproducing indicates it may be a timing-related issue, and
the failure to negotiate a link suggests that the second patch may also be
involved.
--
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/1841040
Title:
r8169 ethernet sometimes doesn't work after cold boot/boot
Status in linux package in Ubuntu:
Confirmed
Bug description:
Whenever the computer is rebooted there is a roughly 50% chance that
the r8169 ethernet cannot negotiate a link. There is no relevant
information in dmesg except for the "link down" message. The work
around is to just keep rebooting the computer until it eventually
works; sometimes this may take up to 7 reboots.
The first set of attached log files were generated while the ethernet
was working.
The second set are generated on the 5.0 HWE kernel when the ethernet
was NOT working.
Note that this is a regression. Ubuntu 16.04 ran on this computer for
three years without the ethernet doing this even once.
Unloading and loading the r8169 module will eventually make it work.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-58-generic 4.15.0-58.64
ProcVersionSignature: Ubuntu 4.15.0-58.64-generic 4.15.18
Uname: Linux 4.15.0-58-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id',
'/dev/snd/pcmC2D0c', '/dev/snd/controlC2', '/dev/snd/hwC0D0',
'/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p',
'/dev/snd/controlC0', '/dev/snd/by-path', '/dev/snd/hwC1D0',
'/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c',
'/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/seq', '/dev/snd/timer']
failed with exit code 1:
Date: Thu Aug 22 10:05:17 2019
HibernationDevice: RESUME=UUID=4ab51820-6203-45a8-a04d-07946b0fbe56
InstallationDate: Installed on 2013-12-22 (2068 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64
(20131016.1)
IwConfig:
lono wireless extensions.
eth0 no wireless extensions.
MachineType: ASUS All Series
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-58-generic
root=UUID=e1e7d1a7-19e8-4203-ad6a-86a144db61bc ro quiet splash vt.handoff=1
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-4.15.0-58-generic N/A
linux-backports-modules-4.15.0-58-generic N/A
linux-firmware 1.173.9
RfKill:
SourcePackage: linux
UpgradeStatus: Upgraded to bionic on 2019-01-30 (203 days ago)
dmi.bios.date: 06/18/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2201
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: H87M-E
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr2201:bd06/18/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH87M-E:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.family: ASUS MB
dmi.product.name: All Series
dmi.product.version: System Version
dmi.sys.vendor: ASUS
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: al14985 F pulseaudio
/dev/snd/controlC0: al14985 F pulseaudio
/dev/snd/controlC1: al14985 F pulseaudio
CurrentDesktop: Unity:Unity7:ubuntu
DistroRelease: Ubuntu 18.04
HibernationDevice: RESUME=UUID=4ab51820-6203-45a8-a04d-07946b0fbe56
InstallationDate: Installed on 2013-12-22 (2068 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64
(20131016.1)
MachineType: ASUS All Series
Pa
[Kernel-packages] [Bug 1841040] Re: r8169 ethernet sometimes doesn't work after cold boot/boot
Seems like you may be right. I could not reproduce it with 1bcf165ac6556d after about 10 attempts. This isn't conclusive unfortunately. I will continue with a regular bisect. -- 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/1841040 Title: r8169 ethernet sometimes doesn't work after cold boot/boot Status in linux package in Ubuntu: Confirmed Bug description: Whenever the computer is rebooted there is a roughly 50% chance that the r8169 ethernet cannot negotiate a link. There is no relevant information in dmesg except for the "link down" message. The work around is to just keep rebooting the computer until it eventually works; sometimes this may take up to 7 reboots. The first set of attached log files were generated while the ethernet was working. The second set are generated on the 5.0 HWE kernel when the ethernet was NOT working. Note that this is a regression. Ubuntu 16.04 ran on this computer for three years without the ethernet doing this even once. Unloading and loading the r8169 module will eventually make it work. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-58-generic 4.15.0-58.64 ProcVersionSignature: Ubuntu 4.15.0-58.64-generic 4.15.18 Uname: Linux 4.15.0-58-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', '/dev/snd/pcmC2D0c', '/dev/snd/controlC2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/by-path', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu Aug 22 10:05:17 2019 HibernationDevice: RESUME=UUID=4ab51820-6203-45a8-a04d-07946b0fbe56 InstallationDate: Installed on 2013-12-22 (2068 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: ASUS All Series ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-58-generic root=UUID=e1e7d1a7-19e8-4203-ad6a-86a144db61bc ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-58-generic N/A linux-backports-modules-4.15.0-58-generic N/A linux-firmware 1.173.9 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2019-01-30 (203 days ago) dmi.bios.date: 06/18/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2201 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H87M-E dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2201:bd06/18/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH87M-E:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: al14985 F pulseaudio /dev/snd/controlC0: al14985 F pulseaudio /dev/snd/controlC1: al14985 F pulseaudio CurrentDesktop: Unity:Unity7:ubuntu DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=4ab51820-6203-45a8-a04d-07946b0fbe56 InstallationDate: Installed on 2013-12-22 (2068 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: ASUS All Series Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-25-generic root=UUID=e1e7d1a7-19e8-4203-ad6a-86a144db61bc ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-25.26~18.04.1-generic 5.0.18 RelatedPackageVersions: linux-restricted-modules-5.0.0-25-generic N/A linux-backports-modules-5.0.0-25-generic N/A linux-firmware1.173.9 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 5.0.0-25-generic x86_64 UpgradeStatus: Upgraded to bionic on 2019-01-30 (203 days ago) UserGroups: adm lpadmin sambashare sudo _MarkForUpload: True dmi.bios.date: 06/18/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2201 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H87M-E
[Kernel-packages] [Bug 1841040] Re: r8169 ethernet sometimes doesn't work after cold boot/boot
It is a r8168 card. The problem continues to happen with the dkms module however. -- 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/1841040 Title: r8169 ethernet sometimes doesn't work after cold boot/boot Status in linux package in Ubuntu: Confirmed Bug description: Whenever the computer is rebooted there is a roughly 50% chance that the r8169 ethernet cannot negotiate a link. There is no relevant information in dmesg except for the "link down" message. The work around is to just keep rebooting the computer until it eventually works; sometimes this may take up to 7 reboots. The first set of attached log files were generated while the ethernet was working. The second set are generated on the 5.0 HWE kernel when the ethernet was NOT working. Note that this is a regression. Ubuntu 16.04 ran on this computer for three years without the ethernet doing this even once. Unloading and loading the r8169 module will eventually make it work. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-58-generic 4.15.0-58.64 ProcVersionSignature: Ubuntu 4.15.0-58.64-generic 4.15.18 Uname: Linux 4.15.0-58-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', '/dev/snd/pcmC2D0c', '/dev/snd/controlC2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/by-path', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu Aug 22 10:05:17 2019 HibernationDevice: RESUME=UUID=4ab51820-6203-45a8-a04d-07946b0fbe56 InstallationDate: Installed on 2013-12-22 (2068 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: ASUS All Series ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-58-generic root=UUID=e1e7d1a7-19e8-4203-ad6a-86a144db61bc ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-58-generic N/A linux-backports-modules-4.15.0-58-generic N/A linux-firmware 1.173.9 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2019-01-30 (203 days ago) dmi.bios.date: 06/18/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2201 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H87M-E dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2201:bd06/18/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH87M-E:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: al14985 F pulseaudio /dev/snd/controlC0: al14985 F pulseaudio /dev/snd/controlC1: al14985 F pulseaudio CurrentDesktop: Unity:Unity7:ubuntu DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=4ab51820-6203-45a8-a04d-07946b0fbe56 InstallationDate: Installed on 2013-12-22 (2068 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: ASUS All Series Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-25-generic root=UUID=e1e7d1a7-19e8-4203-ad6a-86a144db61bc ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-25.26~18.04.1-generic 5.0.18 RelatedPackageVersions: linux-restricted-modules-5.0.0-25-generic N/A linux-backports-modules-5.0.0-25-generic N/A linux-firmware1.173.9 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 5.0.0-25-generic x86_64 UpgradeStatus: Upgraded to bionic on 2019-01-30 (203 days ago) UserGroups: adm lpadmin sambashare sudo _MarkForUpload: True dmi.bios.date: 06/18/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2201 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H87M-E dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.
[Kernel-packages] [Bug 1841040] Re: r8169 ethernet sometimes doesn't work after cold boot/boot
I finally completed the bisection. An extremely large number of kernels failed to build. This is the result: # only skipped commits left to test # possible first bad commit: [4d6ca227c768b50b05cf183974b40abe444e9d0c] Merge branch 'for-4.12/asus' into for-linus # possible first bad commit: [800f3eef8ebc1264e9c135bfa892c8ae41fa4792] Merge branch 'for-4.12/sony' into for-linus # possible first bad commit: [18fc2163b8a410d4d36b8f44658580731c0afaa1] Merge branches 'for-4.11/upstream-fixes', 'for-4.12/accutouch', 'for-4.12/cp2112', 'for-4.12/hid-core-null-state-handling', 'for-4.12/hiddev', 'for-4.12/i2c-hid', 'for-4.12/innomedia', 'for-4.12/logitech-hidpp-battery-power-supply', 'for-4.12/multitouch', 'for-4.12/nti', 'for-4.12/upstream' and 'for-4.12/wacom' into for-linus # possible first bad commit: [d529a4ad91efcf68b65440c6555895fd7ad5a08e] HID: usbhid: Add HID_QUIRK_NOGET for Aten CS-1758 KVM switch # possible first bad commit: [149f6f6b8ff3288a88dc34755de7719637cc8cc4] HID: wacom: Move wacom_remote_irq and wacom_remote_status_irq # possible first bad commit: [ed1fa736839eb97b1d066e36150df28251095eef] HID: wacom: generic: sync pad events only for actual packets # possible first bad commit: [040fc001765d374776353cb4f8b03ea7fa41e3cd] HID: sony: remove redundant check for -ve err # possible first bad commit: [a676bdc422241822130364443a6a65b6520440ba] HID: sony: Make sure to unregister sensors on failure # possible first bad commit: [77b499e739ed5561e5026fa7140ae53f6c4d1d8e] HID: sony: Make DS4 bt poll interval adjustable # possible first bad commit: [5caceb0695d0498b8c931cbc3cdafd99bd37b8ae] HID: sony: Set proper bit flags on DS4 output report # possible first bad commit: [39254a13d64bc69b83f4097dacc4117d7b865118] HID: sony: DS4 use brighter LED colors # possible first bad commit: [b8f0970d2c5a03f5a431d51af74dd1a0ec62fe91] HID: sony: Improve navigation controller axis/button mapping # possible first bad commit: [5a144be39c3a32b3072529ccee79e4ec9eb9b275] HID: sony: Use DS3 MAC address as unique identifier on USB # possible first bad commit: [a4bf6153b317754e058ad9c7f5f02367e0bfdcc8] HID: logitech-hidpp: add a sysfs file to tell we support power_supply # possible first bad commit: [7f7ce2a258b47f9510ad613328c046a3ff9426b0] HID: logitech-hidpp: enable HID++ 1.0 battery reporting # possible first bad commit: [696ecef9b5874a312d74050525217f48d0f1b349] HID: logitech-hidpp: add support for battery status for the K750 # possible first bad commit: [5b036ea18e13e006e99cb197e9aceb09d897d20a] HID: logitech-hidpp: battery: provide CAPACITY_LEVEL # possible first bad commit: [14f437a1d7b49a2e873f63436526f9aed3a781c3] HID: logitech-hidpp: rename battery level into capacity # possible first bad commit: [284f8d7592673a7a6dae96d082806d324378f212] HID: logitech-hidpp: battery: provide ONLINE property # possible first bad commit: [9b9c519f1fe3ec9d2518a99c71c54f5c25eef345] HID: logitech-hidpp: notify battery on connect # possible first bad commit: [a9525b80feb1b6ae40244b16b0558cbdc64f28cd] HID: logitech-hidpp: return an error if the queried feature is not present # possible first bad commit: [a52ec107fa81c8f799654b860e262f07bd14d63a] HID: logitech-hidpp: create the battery for all types of HID++ devices # possible first bad commit: [32043d0fdf9c5ef246e92f59c98624ed135b9e4e] HID: logitech-hidpp: forward device info in power_supply # possible first bad commit: [eb626c573219233bfd330fef9066e7f9530b078e] HID: logitech-hidpp: handle battery events in hidpp_raw_hidpp_event() # possible first bad commit: [2936836f919af8d766a23fdf2bb945a0d74fa534] HID: logitech-hidpp: rework hidpp_connect_event() # possible first bad commit: [187f2bba93816a300018ad7fb0d79175af0643d3] HID: logitech-hidpp: retrieve the HID++ device name when available # possible first bad commit: [843c624eef0c198d7052bd527613a5e7350593e4] HID: logitech-hidpp: rework probe path for unifying devices # possible first bad commit: [206d7c68e83e1add3aa67019ab95d98f87c6edd4] HID: logitech-hidpp: create a capabilities bits field # possible first bad commit: [b4f8ce07b55fa30b5a8c0d2655f1c5cc4c0b9095] HID: logitech-hidpp: do not query the name through HID++ for 1.0 devices # possible first bad commit: [680de741e835d56e504997b613895058625291e9] HID: logitech-hidpp: make sure we only register one battery per device # possible first bad commit: [3861e6ca305c5262f0493e9141f0c52ba066a447] HID: logitech-hidpp: Add scope to battery # possible first bad commit: [8dba3026d5453aa6de00f8726fdcde45d5c57484] HID: logitech-dj: allow devices to request full pairing information # possible first bad commit: [b79cbc55481ddc0b7cc68fb2072d93ee7eefbf8f] HID: wacom: Bamboo One Medium does not have touch # possible first bad commit: [959d973e9890150342df76160d966ab1270208df] HID: add two missing usages for digitizer # possible first bad commit: [ac34b970a9ec536c59faa8cdd5678daeae8b9dd3] HID: cp2112: select GPIOLIB_IRQCHIP instead of depending on it # possible first ba
[Kernel-packages] [Bug 1841040] Re: r8169 ethernet sometimes doesn't work after cold boot/boot
Reloading the module does clear the error for me. I have never seen the problem where the link comes up but it won't receive packets. -- 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/1841040 Title: r8169 ethernet sometimes doesn't work after cold boot/boot Status in linux package in Ubuntu: Confirmed Bug description: Whenever the computer is rebooted there is a roughly 50% chance that the r8169 ethernet cannot negotiate a link. There is no relevant information in dmesg except for the "link down" message. The work around is to just keep rebooting the computer until it eventually works; sometimes this may take up to 7 reboots. The first set of attached log files were generated while the ethernet was working. The second set are generated on the 5.0 HWE kernel when the ethernet was NOT working. Note that this is a regression. Ubuntu 16.04 ran on this computer for three years without the ethernet doing this even once. Unloading and loading the r8169 module will eventually make it work. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-58-generic 4.15.0-58.64 ProcVersionSignature: Ubuntu 4.15.0-58.64-generic 4.15.18 Uname: Linux 4.15.0-58-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', '/dev/snd/pcmC2D0c', '/dev/snd/controlC2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/by-path', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu Aug 22 10:05:17 2019 HibernationDevice: RESUME=UUID=4ab51820-6203-45a8-a04d-07946b0fbe56 InstallationDate: Installed on 2013-12-22 (2068 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: ASUS All Series ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-58-generic root=UUID=e1e7d1a7-19e8-4203-ad6a-86a144db61bc ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-58-generic N/A linux-backports-modules-4.15.0-58-generic N/A linux-firmware 1.173.9 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2019-01-30 (203 days ago) dmi.bios.date: 06/18/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2201 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H87M-E dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2201:bd06/18/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH87M-E:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: al14985 F pulseaudio /dev/snd/controlC0: al14985 F pulseaudio /dev/snd/controlC1: al14985 F pulseaudio CurrentDesktop: Unity:Unity7:ubuntu DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=4ab51820-6203-45a8-a04d-07946b0fbe56 InstallationDate: Installed on 2013-12-22 (2068 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: ASUS All Series Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-25-generic root=UUID=e1e7d1a7-19e8-4203-ad6a-86a144db61bc ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-25.26~18.04.1-generic 5.0.18 RelatedPackageVersions: linux-restricted-modules-5.0.0-25-generic N/A linux-backports-modules-5.0.0-25-generic N/A linux-firmware1.173.9 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 5.0.0-25-generic x86_64 UpgradeStatus: Upgraded to bionic on 2019-01-30 (203 days ago) UserGroups: adm lpadmin sambashare sudo _MarkForUpload: True dmi.bios.date: 06/18/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2201 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H87M-E dmi.board.vendor: ASUSTeK COMPUTER IN
[Kernel-packages] [Bug 1754836] Re: Xubuntu: ERROR:dbus.proxies:Introspect error on org.bluez:/org/bluez: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut: Failed to activate service
On the current daily ISO this now hangs for 50 seconds instead of 75, and the blueman/bluetooth messages are completely gone from xsession- errors. -- 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/1754836 Title: Xubuntu: ERROR:dbus.proxies:Introspect error on org.bluez:/org/bluez: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) Status in blueman package in Ubuntu: New Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: Xubuntu seeing long first time boot to desktop from login. Also causing the long time to desktop from try/install livesession dialogue. Including xsession-errors from the first time boot on installed system. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Mar 10 11:32:59 2018 InstallationDate: Installed on 2018-03-08 (1 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180306.1) InterestingModules: bluetooth MachineType: NOVATECH LTD MBB-44608 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic root=UUID=8d9f054a-4c7a-481f-966e-fc2cd6f51aca ro quiet splash SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/19/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-DS2V dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: 7383241-001 dmi.chassis.type: 3 dmi.chassis.vendor: NOVATECH LTD dmi.chassis.version: V1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd06/19/2014:svnNOVATECHLTD:pnMBB-44608:pvrV1.0:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrTobefilledbyO.E.M.:cvnNOVATECHLTD:ct3:cvrV1.0: dmi.product.family: AMI PLATFORM dmi.product.name: MBB-44608 dmi.product.version: V1.0 dmi.sys.vendor: NOVATECH LTD hciconfig: rfkill: syslog: Mar 10 11:30:16 test-MBB-44608 NetworkManager[679]: [1520681416.8951] Loaded device plugin: NMBluezManager (/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin- bluetooth.so) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/blueman/+bug/1754836/+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 1754836] Re: Xubuntu: ERROR:dbus.proxies:Introspect error on org.bluez:/org/bluez: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut: Failed to activate service
Since this only happens on first login, I ran a diff on the full home directory before/after login: https://paste.ubuntu.com/p/SJ2nNx7WfP/ I don't see anything obvious in there. The pulse cookie and a blueman settings file (empty) were created. The rest seems to be Thunar/desktop defaults and example files. -- 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/1754836 Title: Xubuntu: ERROR:dbus.proxies:Introspect error on org.bluez:/org/bluez: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) Status in blueman package in Ubuntu: New Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: Xubuntu seeing long first time boot to desktop from login. Also causing the long time to desktop from try/install livesession dialogue. Including xsession-errors from the first time boot on installed system. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Mar 10 11:32:59 2018 InstallationDate: Installed on 2018-03-08 (1 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180306.1) InterestingModules: bluetooth MachineType: NOVATECH LTD MBB-44608 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic root=UUID=8d9f054a-4c7a-481f-966e-fc2cd6f51aca ro quiet splash SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/19/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-DS2V dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: 7383241-001 dmi.chassis.type: 3 dmi.chassis.vendor: NOVATECH LTD dmi.chassis.version: V1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd06/19/2014:svnNOVATECHLTD:pnMBB-44608:pvrV1.0:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrTobefilledbyO.E.M.:cvnNOVATECHLTD:ct3:cvrV1.0: dmi.product.family: AMI PLATFORM dmi.product.name: MBB-44608 dmi.product.version: V1.0 dmi.sys.vendor: NOVATECH LTD hciconfig: rfkill: syslog: Mar 10 11:30:16 test-MBB-44608 NetworkManager[679]: [1520681416.8951] Loaded device plugin: NMBluezManager (/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin- bluetooth.so) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/blueman/+bug/1754836/+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 1754836] Re: Xubuntu: ERROR:dbus.proxies:Introspect error on org.bluez:/org/bluez: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut: Failed to activate service
I tried to log in over ssh and run top so I could watch which processes were running but this caused the delay to disappear. -- 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/1754836 Title: Xubuntu: ERROR:dbus.proxies:Introspect error on org.bluez:/org/bluez: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) Status in blueman package in Ubuntu: New Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: Xubuntu seeing long first time boot to desktop from login. Also causing the long time to desktop from try/install livesession dialogue. Including xsession-errors from the first time boot on installed system. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Mar 10 11:32:59 2018 InstallationDate: Installed on 2018-03-08 (1 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180306.1) InterestingModules: bluetooth MachineType: NOVATECH LTD MBB-44608 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic root=UUID=8d9f054a-4c7a-481f-966e-fc2cd6f51aca ro quiet splash SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/19/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-DS2V dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: 7383241-001 dmi.chassis.type: 3 dmi.chassis.vendor: NOVATECH LTD dmi.chassis.version: V1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd06/19/2014:svnNOVATECHLTD:pnMBB-44608:pvrV1.0:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrTobefilledbyO.E.M.:cvnNOVATECHLTD:ct3:cvrV1.0: dmi.product.family: AMI PLATFORM dmi.product.name: MBB-44608 dmi.product.version: V1.0 dmi.sys.vendor: NOVATECH LTD hciconfig: rfkill: syslog: Mar 10 11:30:16 test-MBB-44608 NetworkManager[679]: [1520681416.8951] Loaded device plugin: NMBluezManager (/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin- bluetooth.so) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/blueman/+bug/1754836/+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 1754836] Re: Xubuntu: ERROR:dbus.proxies:Introspect error on org.bluez:/org/bluez: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut: Failed to activate service
As far as the original bug with delayed login goes... it seems that the Bluetooth stuff is a red herring. Since it only happens on first login, I deleted the contents of ~ and relogged. The delay came back, so I bisected the files until I arrived at the single file which needs to be deleted in order for the delay to happen. And that file is: ~/.cache/fontconfig/9b89f8e3dae116d678bbf48e5f21f69b-le32d4.cache-7 This cache file is associated with the Noto CJK fonts at: /usr/share/fonts/opentype/noto (You can see this by running strings on it.) Deleting this file while the user is not logged in causes the next login to take 60 seconds. ** Bug watch added: Debian Bug tracker #845058 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845058 -- 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/1754836 Title: Xubuntu: ERROR:dbus.proxies:Introspect error on org.bluez:/org/bluez: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) Status in blueman package in Ubuntu: New Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: Xubuntu seeing long first time boot to desktop from login. Also causing the long time to desktop from try/install livesession dialogue. Including xsession-errors from the first time boot on installed system. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Mar 10 11:32:59 2018 InstallationDate: Installed on 2018-03-08 (1 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180306.1) InterestingModules: bluetooth MachineType: NOVATECH LTD MBB-44608 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic root=UUID=8d9f054a-4c7a-481f-966e-fc2cd6f51aca ro quiet splash SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/19/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-DS2V dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: 7383241-001 dmi.chassis.type: 3 dmi.chassis.vendor: NOVATECH LTD dmi.chassis.version: V1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd06/19/2014:svnNOVATECHLTD:pnMBB-44608:pvrV1.0:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrTobefilledbyO.E.M.:cvnNOVATECHLTD:ct3:cvrV1.0: dmi.product.family: AMI PLATFORM dmi.product.name: MBB-44608 dmi.product.version: V1.0 dmi.sys.vendor: NOVATECH LTD hciconfig: rfkill: syslog: Mar 10 11:30:16 test-MBB-44608 NetworkManager[679]: [1520681416.8951] Loaded device plugin: NMBluezManager (/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin- bluetooth.so) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/blueman/+bug/1754836/+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 1754836] Re: Xubuntu: ERROR:dbus.proxies:Introspect error on org.bluez:/org/bluez: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut: Failed to activate service
seems related: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845058 -- 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/1754836 Title: Xubuntu: ERROR:dbus.proxies:Introspect error on org.bluez:/org/bluez: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) Status in blueman package in Ubuntu: New Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: Xubuntu seeing long first time boot to desktop from login. Also causing the long time to desktop from try/install livesession dialogue. Including xsession-errors from the first time boot on installed system. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Mar 10 11:32:59 2018 InstallationDate: Installed on 2018-03-08 (1 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180306.1) InterestingModules: bluetooth MachineType: NOVATECH LTD MBB-44608 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic root=UUID=8d9f054a-4c7a-481f-966e-fc2cd6f51aca ro quiet splash SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/19/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-DS2V dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: 7383241-001 dmi.chassis.type: 3 dmi.chassis.vendor: NOVATECH LTD dmi.chassis.version: V1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd06/19/2014:svnNOVATECHLTD:pnMBB-44608:pvrV1.0:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrTobefilledbyO.E.M.:cvnNOVATECHLTD:ct3:cvrV1.0: dmi.product.family: AMI PLATFORM dmi.product.name: MBB-44608 dmi.product.version: V1.0 dmi.sys.vendor: NOVATECH LTD hciconfig: rfkill: syslog: Mar 10 11:30:16 test-MBB-44608 NetworkManager[679]: [1520681416.8951] Loaded device plugin: NMBluezManager (/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin- bluetooth.so) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/blueman/+bug/1754836/+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 1754836] Re: Xubuntu: ERROR:dbus.proxies:Introspect error on org.bluez:/org/bluez: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut: Failed to activate service
Another piece of the puzzle: if you run: sudo fc-cache -fv this will rebuild the system font cache in /var/cache/fontconfig If you then delete the user's cache in ~/.cache/fontconfig and re-log, there is no delay... and the user's font cache will NOT be rebuilt. After a delayed login, user's cache and the system cache appear to contain the same files. So it looks as if something thinks the system cache is out of date and wants to rebuild it. Whatever it is only has user permissions, so rebuilds the font cache in the user's .cache -- 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/1754836 Title: Xubuntu: ERROR:dbus.proxies:Introspect error on org.bluez:/org/bluez: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) Status in blueman package in Ubuntu: New Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: Xubuntu seeing long first time boot to desktop from login. Also causing the long time to desktop from try/install livesession dialogue. Including xsession-errors from the first time boot on installed system. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Mar 10 11:32:59 2018 InstallationDate: Installed on 2018-03-08 (1 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180306.1) InterestingModules: bluetooth MachineType: NOVATECH LTD MBB-44608 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic root=UUID=8d9f054a-4c7a-481f-966e-fc2cd6f51aca ro quiet splash SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/19/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-DS2V dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: 7383241-001 dmi.chassis.type: 3 dmi.chassis.vendor: NOVATECH LTD dmi.chassis.version: V1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd06/19/2014:svnNOVATECHLTD:pnMBB-44608:pvrV1.0:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrTobefilledbyO.E.M.:cvnNOVATECHLTD:ct3:cvrV1.0: dmi.product.family: AMI PLATFORM dmi.product.name: MBB-44608 dmi.product.version: V1.0 dmi.sys.vendor: NOVATECH LTD hciconfig: rfkill: syslog: Mar 10 11:30:16 test-MBB-44608 NetworkManager[679]: [1520681416.8951] Loaded device plugin: NMBluezManager (/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin- bluetooth.so) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/blueman/+bug/1754836/+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 1754836] Re: Xubuntu: ERROR:dbus.proxies:Introspect error on org.bluez:/org/bluez: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut: Failed to activate service
Some more: touching the system cache files doesn't make it work. Binary diff on the cache files before and after running fc-cache shows this: 63 c7 c3 5a 00 00 00 00 47 72 ce 15 00 00 00 00 63 c7 c3 5a 00 00 00 00 00 00 00 00 00 00 00 00 Before, at offset 0x38, the "bad" cache files have a non-zero 32 bit number. The number is different in every "bad" cache file. It is always zero in the "good" files. This is the only difference. The rest of each file is identical. I don't know what this field represents. Need a fontconfig expert to look at this. -- 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/1754836 Title: Xubuntu: ERROR:dbus.proxies:Introspect error on org.bluez:/org/bluez: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) Status in blueman package in Ubuntu: New Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: Xubuntu seeing long first time boot to desktop from login. Also causing the long time to desktop from try/install livesession dialogue. Including xsession-errors from the first time boot on installed system. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Mar 10 11:32:59 2018 InstallationDate: Installed on 2018-03-08 (1 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180306.1) InterestingModules: bluetooth MachineType: NOVATECH LTD MBB-44608 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic root=UUID=8d9f054a-4c7a-481f-966e-fc2cd6f51aca ro quiet splash SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/19/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-DS2V dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: 7383241-001 dmi.chassis.type: 3 dmi.chassis.vendor: NOVATECH LTD dmi.chassis.version: V1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd06/19/2014:svnNOVATECHLTD:pnMBB-44608:pvrV1.0:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrTobefilledbyO.E.M.:cvnNOVATECHLTD:ct3:cvrV1.0: dmi.product.family: AMI PLATFORM dmi.product.name: MBB-44608 dmi.product.version: V1.0 dmi.sys.vendor: NOVATECH LTD hciconfig: rfkill: syslog: Mar 10 11:30:16 test-MBB-44608 NetworkManager[679]: [1520681416.8951] Loaded device plugin: NMBluezManager (/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin- bluetooth.so) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/blueman/+bug/1754836/+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 1754836] Re: Xubuntu: ERROR:dbus.proxies:Introspect error on org.bluez:/org/bluez: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut: Failed to activate service
One final thing: this does not affect Ubuntu desktop after install. But it does affect the Ubuntu live image, which takes an extra minute or so to boot. It seems that the Ubuntu desktop installer rebuilds the system font cache during install. -- 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/1754836 Title: Xubuntu: ERROR:dbus.proxies:Introspect error on org.bluez:/org/bluez: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) Status in blueman package in Ubuntu: New Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: Xubuntu seeing long first time boot to desktop from login. Also causing the long time to desktop from try/install livesession dialogue. Including xsession-errors from the first time boot on installed system. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Mar 10 11:32:59 2018 InstallationDate: Installed on 2018-03-08 (1 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180306.1) InterestingModules: bluetooth MachineType: NOVATECH LTD MBB-44608 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic root=UUID=8d9f054a-4c7a-481f-966e-fc2cd6f51aca ro quiet splash SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/19/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-DS2V dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: 7383241-001 dmi.chassis.type: 3 dmi.chassis.vendor: NOVATECH LTD dmi.chassis.version: V1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd06/19/2014:svnNOVATECHLTD:pnMBB-44608:pvrV1.0:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrTobefilledbyO.E.M.:cvnNOVATECHLTD:ct3:cvrV1.0: dmi.product.family: AMI PLATFORM dmi.product.name: MBB-44608 dmi.product.version: V1.0 dmi.sys.vendor: NOVATECH LTD hciconfig: rfkill: syslog: Mar 10 11:30:16 test-MBB-44608 NetworkManager[679]: [1520681416.8951] Loaded device plugin: NMBluezManager (/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin- bluetooth.so) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/blueman/+bug/1754836/+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 1754836] Re: Xubuntu: ERROR:dbus.proxies:Introspect error on org.bluez:/org/bluez: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut: Failed to activate service
*** This bug is a duplicate of bug 1749546 *** https://bugs.launchpad.net/bugs/1749546 The Bluez timeout errors still show up in ~/.xsession-errors at least on hardware without Bluetooth. However, it seems to be harmless. -- 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/1754836 Title: Xubuntu: ERROR:dbus.proxies:Introspect error on org.bluez:/org/bluez: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) Status in blueman package in Ubuntu: New Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: Xubuntu seeing long first time boot to desktop from login. Also causing the long time to desktop from try/install livesession dialogue. Including xsession-errors from the first time boot on installed system. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Mar 10 11:32:59 2018 InstallationDate: Installed on 2018-03-08 (1 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180306.1) InterestingModules: bluetooth MachineType: NOVATECH LTD MBB-44608 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic root=UUID=8d9f054a-4c7a-481f-966e-fc2cd6f51aca ro quiet splash SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/19/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-DS2V dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: 7383241-001 dmi.chassis.type: 3 dmi.chassis.vendor: NOVATECH LTD dmi.chassis.version: V1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd06/19/2014:svnNOVATECHLTD:pnMBB-44608:pvrV1.0:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrTobefilledbyO.E.M.:cvnNOVATECHLTD:ct3:cvrV1.0: dmi.product.family: AMI PLATFORM dmi.product.name: MBB-44608 dmi.product.version: V1.0 dmi.sys.vendor: NOVATECH LTD hciconfig: rfkill: syslog: Mar 10 11:30:16 test-MBB-44608 NetworkManager[679]: [1520681416.8951] Loaded device plugin: NMBluezManager (/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin- bluetooth.so) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/blueman/+bug/1754836/+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 1073089] Re: ubuntu kernel does not support gadgetfs
Still broken in 18.04 -- 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/1073089 Title: ubuntu kernel does not support gadgetfs Status in linux package in Ubuntu: Triaged Bug description: The Ubuntu kernel does not appear to support gadgetfs: $ sudo modprobe g_mass_storage file=/tmp/fake_usb_disk FATAL: Error inserting g_mass_storage (/lib/modules/3.5.0-17-generic/kernel/drivers/usb/gadget/g_mass_storage.ko): No such device $ ll /lib/modules/3.5.0-17-generic/kernel/drivers/usb/gadget/g_mass_storage.ko -rw-r--r-- 1 root root 56436 oct 9 21:06 /lib/modules/3.5.0-17-generic/kernel/drivers/usb/gadget/g_mass_storage.ko $ This seems to have been resolved in Igloo (see bug 923674) so is presumably a case of a cherry-pick? --- ApportVersion: 2.6.1-0ubuntu6 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: james 3464 F pulseaudio /dev/snd/controlC0: james 3464 F pulseaudio DistroRelease: Ubuntu 12.10 HibernationDevice: RESUME=UUID=67e3cd44-242b-4bbf-918b-28fff81e0312 InstallationDate: Installed on 2010-10-21 (740 days ago) InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007) MachineType: LENOVO 2516CTO MarkForUpload: True NonfreeKernelModules: nvidia Package: linux-image-generic-pae 3.5.0.17.19 PackageArchitecture: i386 ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic root=UUID=7ad192e9-7b26-49d1-8e1c-fefc7dc495cb ro quiet splash ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 RelatedPackageVersions: linux-restricted-modules-3.5.0-17-generic N/A linux-backports-modules-3.5.0-17-generic N/A linux-firmware1.95 Tags: quantal running-unity Uname: Linux 3.5.0-17-generic i686 UpgradeStatus: Upgraded to quantal on 2012-09-30 (29 days ago) UserGroups: adm admin cdrom dialout kvm libvirtd lpadmin plugdev sambashare sbuild vboxusers dmi.bios.date: 08/27/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 6IET72WW (1.32 ) dmi.board.name: 2516CTO 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:bvr6IET72WW(1.32):bd08/27/2010:svnLENOVO:pn2516CTO:pvrThinkPadT410:rvnLENOVO:rn2516CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2516CTO dmi.product.version: ThinkPad T410 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1073089/+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 1754836] Re: Failed to activate service
The same messages are logged on the live image boot. -- 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/1754836 Title: Failed to activate service Status in bluez package in Ubuntu: New Bug description: Xubuntu seeing long first time boot to desktop from login. Possibly also causing the long time to desktop from try/install livesession dialogue. Including xsession-errors from the first time boot on installed system. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Mar 10 11:32:59 2018 InstallationDate: Installed on 2018-03-08 (1 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180306.1) InterestingModules: bluetooth MachineType: NOVATECH LTD MBB-44608 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic root=UUID=8d9f054a-4c7a-481f-966e-fc2cd6f51aca ro quiet splash SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/19/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-DS2V dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: 7383241-001 dmi.chassis.type: 3 dmi.chassis.vendor: NOVATECH LTD dmi.chassis.version: V1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd06/19/2014:svnNOVATECHLTD:pnMBB-44608:pvrV1.0:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrTobefilledbyO.E.M.:cvnNOVATECHLTD:ct3:cvrV1.0: dmi.product.family: AMI PLATFORM dmi.product.name: MBB-44608 dmi.product.version: V1.0 dmi.sys.vendor: NOVATECH LTD hciconfig: rfkill: syslog: Mar 10 11:30:16 test-MBB-44608 NetworkManager[679]: [1520681416.8951] Loaded device plugin: NMBluezManager (/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-bluetooth.so) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1754836/+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 1754836] Re: Xubuntu: [pulseaudio] bluez5-util.c: GetManagedObjects() failed: org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out (service_sta
No, we are talking about the errors in xsession-errors.txt: ERROR:dbus.proxies:Introspect error on org.bluez:/: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) ERROR:dbus.proxies:Introspect error on org.bluez:/org/bluez: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) ERROR:dbus.proxies:Introspect error on org.bluez:/: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) Note that each one of these errors is a separate time out, so the total delay is 75 seconds. This delay blocks the desktop from starting during boot and first login. The delay can be reproduced any time on the live session by attempting to start blueman-applet from the terminal - it will produce the same errors and then give up after 75 seconds. The computer under test has no bluetooth hardware and blueman is not running. A patch was added to 16.04 because this situation led to blueman outright crashing there. Now in 18.04 instead of crashing it delays boot up by 75 seconds instead. -- 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/1754836 Title: ERROR:dbus.proxies:Introspect error on org.bluez:/org/bluez: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: Xubuntu seeing long first time boot to desktop from login. Possibly also causing the long time to desktop from try/install livesession dialogue. Including xsession-errors from the first time boot on installed system. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Mar 10 11:32:59 2018 InstallationDate: Installed on 2018-03-08 (1 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180306.1) InterestingModules: bluetooth MachineType: NOVATECH LTD MBB-44608 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic root=UUID=8d9f054a-4c7a-481f-966e-fc2cd6f51aca ro quiet splash SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/19/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-DS2V dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: 7383241-001 dmi.chassis.type: 3 dmi.chassis.vendor: NOVATECH LTD dmi.chassis.version: V1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd06/19/2014:svnNOVATECHLTD:pnMBB-44608:pvrV1.0:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrTobefilledbyO.E.M.:cvnNOVATECHLTD:ct3:cvrV1.0: dmi.product.family: AMI PLATFORM dmi.product.name: MBB-44608 dmi.product.version: V1.0 dmi.sys.vendor: NOVATECH LTD hciconfig: rfkill: syslog: Mar 10 11:30:16 test-MBB-44608 NetworkManager[679]: [1520681416.8951] Loaded device plugin: NMBluezManager (/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-bluetooth.so) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1754836/+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 1754836] Re: ERROR:dbus.proxies:Introspect error on org.bluez:/org/bluez: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.blu
** Summary changed: - Xubuntu: [pulseaudio] bluez5-util.c: GetManagedObjects() failed: org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) + ERROR:dbus.proxies:Introspect error on org.bluez:/org/bluez: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) ** Summary changed: - ERROR:dbus.proxies:Introspect error on org.bluez:/org/bluez: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) + Xubuntu: ERROR:dbus.proxies:Introspect error on org.bluez:/org/bluez: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) -- 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/1754836 Title: Xubuntu: ERROR:dbus.proxies:Introspect error on org.bluez:/org/bluez: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: Xubuntu seeing long first time boot to desktop from login. Possibly also causing the long time to desktop from try/install livesession dialogue. Including xsession-errors from the first time boot on installed system. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Mar 10 11:32:59 2018 InstallationDate: Installed on 2018-03-08 (1 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180306.1) InterestingModules: bluetooth MachineType: NOVATECH LTD MBB-44608 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic root=UUID=8d9f054a-4c7a-481f-966e-fc2cd6f51aca ro quiet splash SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/19/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-DS2V dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: 7383241-001 dmi.chassis.type: 3 dmi.chassis.vendor: NOVATECH LTD dmi.chassis.version: V1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd06/19/2014:svnNOVATECHLTD:pnMBB-44608:pvrV1.0:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrTobefilledbyO.E.M.:cvnNOVATECHLTD:ct3:cvrV1.0: dmi.product.family: AMI PLATFORM dmi.product.name: MBB-44608 dmi.product.version: V1.0 dmi.sys.vendor: NOVATECH LTD hciconfig: rfkill: syslog: Mar 10 11:30:16 test-MBB-44608 NetworkManager[679]: [1520681416.8951] Loaded device plugin: NMBluezManager (/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-bluetooth.so) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1754836/+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 1754836] Re: Xubuntu: ERROR:dbus.proxies:Introspect error on org.bluez:/org/bluez: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut: Failed to activate service
** Attachment added: "log running blueman-applet manually" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1754836/+attachment/5077985/+files/blueman-applet-manual.txt -- 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/1754836 Title: Xubuntu: ERROR:dbus.proxies:Introspect error on org.bluez:/org/bluez: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: Xubuntu seeing long first time boot to desktop from login. Possibly also causing the long time to desktop from try/install livesession dialogue. Including xsession-errors from the first time boot on installed system. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Mar 10 11:32:59 2018 InstallationDate: Installed on 2018-03-08 (1 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180306.1) InterestingModules: bluetooth MachineType: NOVATECH LTD MBB-44608 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic root=UUID=8d9f054a-4c7a-481f-966e-fc2cd6f51aca ro quiet splash SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/19/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-DS2V dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: 7383241-001 dmi.chassis.type: 3 dmi.chassis.vendor: NOVATECH LTD dmi.chassis.version: V1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd06/19/2014:svnNOVATECHLTD:pnMBB-44608:pvrV1.0:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrTobefilledbyO.E.M.:cvnNOVATECHLTD:ct3:cvrV1.0: dmi.product.family: AMI PLATFORM dmi.product.name: MBB-44608 dmi.product.version: V1.0 dmi.sys.vendor: NOVATECH LTD hciconfig: rfkill: syslog: Mar 10 11:30:16 test-MBB-44608 NetworkManager[679]: [1520681416.8951] Loaded device plugin: NMBluezManager (/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-bluetooth.so) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1754836/+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 1754836] Re: Xubuntu: ERROR:dbus.proxies:Introspect error on org.bluez:/org/bluez: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut: Failed to activate service
There is more stuff in syslog too. It looks like pulseaudio is trying and failing to start blueman. ** Attachment added: "cat syslog | grep -E '(pulseaudio|blueman)'" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1754836/+attachment/5077997/+files/syslog.txt -- 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/1754836 Title: Xubuntu: ERROR:dbus.proxies:Introspect error on org.bluez:/org/bluez: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: Xubuntu seeing long first time boot to desktop from login. Possibly also causing the long time to desktop from try/install livesession dialogue. Including xsession-errors from the first time boot on installed system. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Mar 10 11:32:59 2018 InstallationDate: Installed on 2018-03-08 (1 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180306.1) InterestingModules: bluetooth MachineType: NOVATECH LTD MBB-44608 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic root=UUID=8d9f054a-4c7a-481f-966e-fc2cd6f51aca ro quiet splash SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/19/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-DS2V dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: 7383241-001 dmi.chassis.type: 3 dmi.chassis.vendor: NOVATECH LTD dmi.chassis.version: V1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd06/19/2014:svnNOVATECHLTD:pnMBB-44608:pvrV1.0:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrTobefilledbyO.E.M.:cvnNOVATECHLTD:ct3:cvrV1.0: dmi.product.family: AMI PLATFORM dmi.product.name: MBB-44608 dmi.product.version: V1.0 dmi.sys.vendor: NOVATECH LTD hciconfig: rfkill: syslog: Mar 10 11:30:16 test-MBB-44608 NetworkManager[679]: [1520681416.8951] Loaded device plugin: NMBluezManager (/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-bluetooth.so) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1754836/+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 1073089] Re: ubuntu kernel does not support gadgetfs
Still broken in 16.04. gadgetfs has been replaced by functionfs, which is also available in the standard kernel packages, but still does not work because it too relies on dummy_hcd on x86 platforms. -- 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/1073089 Title: ubuntu kernel does not support gadgetfs Status in linux package in Ubuntu: Triaged Bug description: The Ubuntu kernel does not appear to support gadgetfs: $ sudo modprobe g_mass_storage file=/tmp/fake_usb_disk FATAL: Error inserting g_mass_storage (/lib/modules/3.5.0-17-generic/kernel/drivers/usb/gadget/g_mass_storage.ko): No such device $ ll /lib/modules/3.5.0-17-generic/kernel/drivers/usb/gadget/g_mass_storage.ko -rw-r--r-- 1 root root 56436 oct 9 21:06 /lib/modules/3.5.0-17-generic/kernel/drivers/usb/gadget/g_mass_storage.ko $ This seems to have been resolved in Igloo (see bug 923674) so is presumably a case of a cherry-pick? --- ApportVersion: 2.6.1-0ubuntu6 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: james 3464 F pulseaudio /dev/snd/controlC0: james 3464 F pulseaudio DistroRelease: Ubuntu 12.10 HibernationDevice: RESUME=UUID=67e3cd44-242b-4bbf-918b-28fff81e0312 InstallationDate: Installed on 2010-10-21 (740 days ago) InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007) MachineType: LENOVO 2516CTO MarkForUpload: True NonfreeKernelModules: nvidia Package: linux-image-generic-pae 3.5.0.17.19 PackageArchitecture: i386 ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic root=UUID=7ad192e9-7b26-49d1-8e1c-fefc7dc495cb ro quiet splash ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 RelatedPackageVersions: linux-restricted-modules-3.5.0-17-generic N/A linux-backports-modules-3.5.0-17-generic N/A linux-firmware1.95 Tags: quantal running-unity Uname: Linux 3.5.0-17-generic i686 UpgradeStatus: Upgraded to quantal on 2012-09-30 (29 days ago) UserGroups: adm admin cdrom dialout kvm libvirtd lpadmin plugdev sambashare sbuild vboxusers dmi.bios.date: 08/27/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 6IET72WW (1.32 ) dmi.board.name: 2516CTO 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:bvr6IET72WW(1.32):bd08/27/2010:svnLENOVO:pn2516CTO:pvrThinkPadT410:rvnLENOVO:rn2516CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2516CTO dmi.product.version: ThinkPad T410 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1073089/+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 1564901] [NEW] xpad rumble causes full system hang
Public bug reported: To reproduce: 1. Have a wired xbox controller. 2. Modify the SDL2 testrumble.c so it runs forever. (attached) 3. Build and run it. 4. Kill it with sigkill from another terminal. Expected result: The program should stop running. Actual result: Entire computer freezes. Soundcard continuously plays the last second of audio. No response from any input devices or the network. The bug can also be reproduced by playing the game Borderlands 2 while having a wired xbox controller connected. The system will randomly freeze in the exact same way. The bug has existed since at least 14.04. The last thing the kernel prints is this: Apr 1 03:38:29 al-desktop kernel: [94142.404218] usb 7-3: new full-speed USB device number 2 using ohci-pci Apr 1 03:38:29 al-desktop kernel: [94142.565264] usb 7-3: New USB device found, idVendor=045e, idProduct=0288 Apr 1 03:38:29 al-desktop kernel: [94142.565268] usb 7-3: New USB device strings: Mfr=0, Product=0, SerialNumber=0 Apr 1 03:38:29 al-desktop kernel: [94142.567304] hub 7-3:1.0: USB hub found Apr 1 03:38:29 al-desktop kernel: [94142.569259] hub 7-3:1.0: 3 ports detected Apr 1 03:38:29 al-desktop kernel: [94142.852248] usb 7-3.1: new full-speed USB device number 3 using ohci-pci Apr 1 03:38:29 al-desktop kernel: [94142.949301] usb 7-3.1: New USB device found, idVendor=045e, idProduct=0289 Apr 1 03:38:29 al-desktop kernel: [94142.949308] usb 7-3.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 Apr 1 03:38:29 al-desktop kernel: [94142.982402] input: Microsoft X-Box pad v2 (US) as /devices/pci:00/:00:13.0/usb7/7-3/7-3.1/7-3.1:1.0/input/input23 Apr 1 03:38:29 al-desktop kernel: [94142.982503] usbcore: registered new interface driver xpad Apr 1 03:40:09 al-desktop kernel: [94242.318271] [ cut here ] Apr 1 03:40:09 al-desktop kernel: [94242.318280] WARNING: CPU: 3 PID: 16529 at /build/linux-_Kv5oI/linux-4.2.0/drivers/usb/core/urb.c:339 usb_submit_urb+0x51/0x70() Apr 1 03:40:09 al-desktop kernel: [94242.318282] URB 880106cbacc0 submitted while active Apr 1 03:40:09 al-desktop kernel: [94242.318283] Modules linked in: joydev xpad ff_memless nvidia_uvm(POE) rfcomm pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) rc_pinnacle_pctv_hd em28xx_rc tda18271 cxd2820r em28xx_dvb d vb_core em28xx binfmt_misc bnep snd_hda_codec_hdmi rc_hauppauge ir_kbd_i2c tuner_simple tuner_types input_leds tuner uvcvideo videobuf2_vmalloc kvm_amd videobuf2_memops kvm btusb videobuf2_core btrtl snd_seq_midi btbcm snd_seq_midi_event btintel snd_usb_audio snd_usbmidi_lib snd_hda_codec_via msp3400 snd_hda_codec_generic snd_rawmidi bluetooth nvidia(POE) snd_seq serio_raw snd_hda_intel snd_seq_device snd_hda_codec snd_hda_core snd_hwdep bttv k10temp tea575x tveeprom edac _core videobuf_dma_sg edac_mce_amd rc_core videobuf_core snd_bt87x v4l2_common videodev snd_pcm media i2c_algo_bit snd_timer i2c_piix4 snd soundcore drm shpchp wmi 8250_fintek asus_atk0110 mac_hid parport_pc ppdev lp parport autofs4 uas u sb_storage hid_generic usbhid hid pata_acpi psmouse pata_atiixp ahci libahci r8169 mii Apr 1 03:40:09 al-desktop kernel: [94242.318324] CPU: 3 PID: 16529 Comm: testrumble Tainted: P OE 4.2.0-34-generic #39-Ubuntu Apr 1 03:40:09 al-desktop kernel: [94242.318326] Hardware name: System manufacturer System Product Name/M4A79XTD EVO, BIOS 210206/17/2010 Apr 1 03:40:09 al-desktop kernel: [94242.318328] 4da02d75 88010a9c3ba8 817ebed3 Apr 1 03:40:09 al-desktop kernel: [94242.318330] 88010a9c3c00 88010a9c3be8 8107b986 Apr 1 03:40:09 al-desktop kernel: [94242.318331] 88010a9c3bd8 0010 880103216f08 88010a9c3cd0 Apr 1 03:40:09 al-desktop kernel: [94242.318333] Call Trace: Apr 1 03:40:09 al-desktop kernel: [94242.318337] [] dump_stack+0x45/0x57 Apr 1 03:40:09 al-desktop kernel: [94242.318340] [] warn_slowpath_common+0x86/0xc0 Apr 1 03:40:09 al-desktop kernel: [94242.318342] [] warn_slowpath_fmt+0x55/0x70 Apr 1 03:40:09 al-desktop kernel: [94242.318345] [] usb_submit_urb+0x51/0x70 Apr 1 03:40:09 al-desktop kernel: [94242.318348] [] xpad_play_effect+0x130/0x240 [xpad] Apr 1 03:40:09 al-desktop kernel: [94242.318351] [] ml_play_effects+0x104/0x6b0 [ff_memless] Apr 1 03:40:09 al-desktop kernel: [94242.318353] [] ml_ff_playback+0x85/0x100 [ff_memless] Apr 1 03:40:09 al-desktop kernel: [94242.318355] [] input_ff_event+0x61/0x90 Apr 1 03:40:09 al-desktop kernel: [94242.318357] [] input_handle_event+0x77/0x4f0 Apr 1 03:40:09 al-desktop kernel: [94242.318359] [] input_inject_event+0x88/0x90 Apr 1 03:40:09 al-desktop kernel: [94242.318360] [] evdev_write+0x1b6/0x230 Apr 1 03:40:09 al-desktop kernel: [94242.318363] [] __vfs_write+0x18/0x40 Apr 1 03:40:09 al-desktop kernel: [94242.318364] [] vfs_write+0xa6/0x1a0 Apr 1 03:40:09 al-desktop kernel: [94242.318
[Kernel-packages] [Bug 1564901] Re: xpad rumble causes full system hang
This is probably fixed by: https://github.com/torvalds/linux/commit/7fc595f4c02636eadaeeecfe7bbc45b57c173004 -- 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/1564901 Title: xpad rumble causes full system hang Status in linux package in Ubuntu: Confirmed Bug description: To reproduce: 1. Have a wired xbox controller. 2. Modify the SDL2 testrumble.c so it runs forever. (attached) 3. Build and run it. 4. Kill it with sigkill from another terminal. Expected result: The program should stop running. Actual result: Entire computer freezes. Soundcard continuously plays the last second of audio. No response from any input devices or the network. The bug can also be reproduced by playing the game Borderlands 2 while having a wired xbox controller connected. The system will randomly freeze in the exact same way. The bug has existed since at least 14.04. The last thing the kernel prints is this: Apr 1 03:38:29 al-desktop kernel: [94142.404218] usb 7-3: new full-speed USB device number 2 using ohci-pci Apr 1 03:38:29 al-desktop kernel: [94142.565264] usb 7-3: New USB device found, idVendor=045e, idProduct=0288 Apr 1 03:38:29 al-desktop kernel: [94142.565268] usb 7-3: New USB device strings: Mfr=0, Product=0, SerialNumber=0 Apr 1 03:38:29 al-desktop kernel: [94142.567304] hub 7-3:1.0: USB hub found Apr 1 03:38:29 al-desktop kernel: [94142.569259] hub 7-3:1.0: 3 ports detected Apr 1 03:38:29 al-desktop kernel: [94142.852248] usb 7-3.1: new full-speed USB device number 3 using ohci-pci Apr 1 03:38:29 al-desktop kernel: [94142.949301] usb 7-3.1: New USB device found, idVendor=045e, idProduct=0289 Apr 1 03:38:29 al-desktop kernel: [94142.949308] usb 7-3.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 Apr 1 03:38:29 al-desktop kernel: [94142.982402] input: Microsoft X-Box pad v2 (US) as /devices/pci:00/:00:13.0/usb7/7-3/7-3.1/7-3.1:1.0/input/input23 Apr 1 03:38:29 al-desktop kernel: [94142.982503] usbcore: registered new interface driver xpad Apr 1 03:40:09 al-desktop kernel: [94242.318271] [ cut here ] Apr 1 03:40:09 al-desktop kernel: [94242.318280] WARNING: CPU: 3 PID: 16529 at /build/linux-_Kv5oI/linux-4.2.0/drivers/usb/core/urb.c:339 usb_submit_urb+0x51/0x70() Apr 1 03:40:09 al-desktop kernel: [94242.318282] URB 880106cbacc0 submitted while active Apr 1 03:40:09 al-desktop kernel: [94242.318283] Modules linked in: joydev xpad ff_memless nvidia_uvm(POE) rfcomm pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) rc_pinnacle_pctv_hd em28xx_rc tda18271 cxd2820r em28xx_dvb d vb_core em28xx binfmt_misc bnep snd_hda_codec_hdmi rc_hauppauge ir_kbd_i2c tuner_simple tuner_types input_leds tuner uvcvideo videobuf2_vmalloc kvm_amd videobuf2_memops kvm btusb videobuf2_core btrtl snd_seq_midi btbcm snd_seq_midi_event btintel snd_usb_audio snd_usbmidi_lib snd_hda_codec_via msp3400 snd_hda_codec_generic snd_rawmidi bluetooth nvidia(POE) snd_seq serio_raw snd_hda_intel snd_seq_device snd_hda_codec snd_hda_core snd_hwdep bttv k10temp tea575x tveeprom edac _core videobuf_dma_sg edac_mce_amd rc_core videobuf_core snd_bt87x v4l2_common videodev snd_pcm media i2c_algo_bit snd_timer i2c_piix4 snd soundcore drm shpchp wmi 8250_fintek asus_atk0110 mac_hid parport_pc ppdev lp parport autofs4 uas u sb_storage hid_generic usbhid hid pata_acpi psmouse pata_atiixp ahci libahci r8169 mii Apr 1 03:40:09 al-desktop kernel: [94242.318324] CPU: 3 PID: 16529 Comm: testrumble Tainted: P OE 4.2.0-34-generic #39-Ubuntu Apr 1 03:40:09 al-desktop kernel: [94242.318326] Hardware name: System manufacturer System Product Name/M4A79XTD EVO, BIOS 210206/17/2010 Apr 1 03:40:09 al-desktop kernel: [94242.318328] 4da02d75 88010a9c3ba8 817ebed3 Apr 1 03:40:09 al-desktop kernel: [94242.318330] 88010a9c3c00 88010a9c3be8 8107b986 Apr 1 03:40:09 al-desktop kernel: [94242.318331] 88010a9c3bd8 0010 880103216f08 88010a9c3cd0 Apr 1 03:40:09 al-desktop kernel: [94242.318333] Call Trace: Apr 1 03:40:09 al-desktop kernel: [94242.318337] [] dump_stack+0x45/0x57 Apr 1 03:40:09 al-desktop kernel: [94242.318340] [] warn_slowpath_common+0x86/0xc0 Apr 1 03:40:09 al-desktop kernel: [94242.318342] [] warn_slowpath_fmt+0x55/0x70 Apr 1 03:40:09 al-desktop kernel: [94242.318345] [] usb_submit_urb+0x51/0x70 Apr 1 03:40:09 al-desktop kernel: [94242.318348] [] xpad_play_effect+0x130/0x240 [xpad] Apr 1 03:40:09 al-desktop kernel: [94242.318351] [] ml_play_effects+0x104/0x6b0 [ff_memless] Apr 1 03:40:09 al-desktop kernel: [94242.318353] [] ml_ff_playback+0x85/0x100 [ff_memless] Apr 1 03:40:09 al-desktop kernel: [94242.318355] [] input_ff_eve
[Kernel-packages] [Bug 1564901] Re: xpad rumble causes full system hang
Yes, it works fine with that kernel. -- 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/1564901 Title: xpad rumble causes full system hang Status in linux package in Ubuntu: Confirmed Bug description: To reproduce: 1. Have a wired xbox controller. 2. Modify the SDL2 testrumble.c so it runs forever. (attached) 3. Build and run it. 4. Kill it with sigkill from another terminal. Expected result: The program should stop running. Actual result: Entire computer freezes. Soundcard continuously plays the last second of audio. No response from any input devices or the network. The bug can also be reproduced by playing the game Borderlands 2 while having a wired xbox controller connected. The system will randomly freeze in the exact same way. The bug has existed since at least 14.04. The last thing the kernel prints is this: Apr 1 03:38:29 al-desktop kernel: [94142.404218] usb 7-3: new full-speed USB device number 2 using ohci-pci Apr 1 03:38:29 al-desktop kernel: [94142.565264] usb 7-3: New USB device found, idVendor=045e, idProduct=0288 Apr 1 03:38:29 al-desktop kernel: [94142.565268] usb 7-3: New USB device strings: Mfr=0, Product=0, SerialNumber=0 Apr 1 03:38:29 al-desktop kernel: [94142.567304] hub 7-3:1.0: USB hub found Apr 1 03:38:29 al-desktop kernel: [94142.569259] hub 7-3:1.0: 3 ports detected Apr 1 03:38:29 al-desktop kernel: [94142.852248] usb 7-3.1: new full-speed USB device number 3 using ohci-pci Apr 1 03:38:29 al-desktop kernel: [94142.949301] usb 7-3.1: New USB device found, idVendor=045e, idProduct=0289 Apr 1 03:38:29 al-desktop kernel: [94142.949308] usb 7-3.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 Apr 1 03:38:29 al-desktop kernel: [94142.982402] input: Microsoft X-Box pad v2 (US) as /devices/pci:00/:00:13.0/usb7/7-3/7-3.1/7-3.1:1.0/input/input23 Apr 1 03:38:29 al-desktop kernel: [94142.982503] usbcore: registered new interface driver xpad Apr 1 03:40:09 al-desktop kernel: [94242.318271] [ cut here ] Apr 1 03:40:09 al-desktop kernel: [94242.318280] WARNING: CPU: 3 PID: 16529 at /build/linux-_Kv5oI/linux-4.2.0/drivers/usb/core/urb.c:339 usb_submit_urb+0x51/0x70() Apr 1 03:40:09 al-desktop kernel: [94242.318282] URB 880106cbacc0 submitted while active Apr 1 03:40:09 al-desktop kernel: [94242.318283] Modules linked in: joydev xpad ff_memless nvidia_uvm(POE) rfcomm pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) rc_pinnacle_pctv_hd em28xx_rc tda18271 cxd2820r em28xx_dvb d vb_core em28xx binfmt_misc bnep snd_hda_codec_hdmi rc_hauppauge ir_kbd_i2c tuner_simple tuner_types input_leds tuner uvcvideo videobuf2_vmalloc kvm_amd videobuf2_memops kvm btusb videobuf2_core btrtl snd_seq_midi btbcm snd_seq_midi_event btintel snd_usb_audio snd_usbmidi_lib snd_hda_codec_via msp3400 snd_hda_codec_generic snd_rawmidi bluetooth nvidia(POE) snd_seq serio_raw snd_hda_intel snd_seq_device snd_hda_codec snd_hda_core snd_hwdep bttv k10temp tea575x tveeprom edac _core videobuf_dma_sg edac_mce_amd rc_core videobuf_core snd_bt87x v4l2_common videodev snd_pcm media i2c_algo_bit snd_timer i2c_piix4 snd soundcore drm shpchp wmi 8250_fintek asus_atk0110 mac_hid parport_pc ppdev lp parport autofs4 uas u sb_storage hid_generic usbhid hid pata_acpi psmouse pata_atiixp ahci libahci r8169 mii Apr 1 03:40:09 al-desktop kernel: [94242.318324] CPU: 3 PID: 16529 Comm: testrumble Tainted: P OE 4.2.0-34-generic #39-Ubuntu Apr 1 03:40:09 al-desktop kernel: [94242.318326] Hardware name: System manufacturer System Product Name/M4A79XTD EVO, BIOS 210206/17/2010 Apr 1 03:40:09 al-desktop kernel: [94242.318328] 4da02d75 88010a9c3ba8 817ebed3 Apr 1 03:40:09 al-desktop kernel: [94242.318330] 88010a9c3c00 88010a9c3be8 8107b986 Apr 1 03:40:09 al-desktop kernel: [94242.318331] 88010a9c3bd8 0010 880103216f08 88010a9c3cd0 Apr 1 03:40:09 al-desktop kernel: [94242.318333] Call Trace: Apr 1 03:40:09 al-desktop kernel: [94242.318337] [] dump_stack+0x45/0x57 Apr 1 03:40:09 al-desktop kernel: [94242.318340] [] warn_slowpath_common+0x86/0xc0 Apr 1 03:40:09 al-desktop kernel: [94242.318342] [] warn_slowpath_fmt+0x55/0x70 Apr 1 03:40:09 al-desktop kernel: [94242.318345] [] usb_submit_urb+0x51/0x70 Apr 1 03:40:09 al-desktop kernel: [94242.318348] [] xpad_play_effect+0x130/0x240 [xpad] Apr 1 03:40:09 al-desktop kernel: [94242.318351] [] ml_play_effects+0x104/0x6b0 [ff_memless] Apr 1 03:40:09 al-desktop kernel: [94242.318353] [] ml_ff_playback+0x85/0x100 [ff_memless] Apr 1 03:40:09 al-desktop kernel: [94242.318355] [] input_ff_event+0x61/0x90 Apr 1 03:40:09 al-desktop kernel: [94242.318357] [] inp
[Kernel-packages] [Bug 1564901] Re: xpad rumble causes full system hang
For reference/impact assessment here's the steam thread where I found the patch: https://steamcommunity.com/app/233130/discussions/0/611702631210587760/ -- 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/1564901 Title: xpad rumble causes full system hang Status in linux package in Ubuntu: Confirmed Bug description: To reproduce: 1. Have a wired xbox controller. 2. Modify the SDL2 testrumble.c so it runs forever. (attached) 3. Build and run it. 4. Kill it with sigkill from another terminal. Expected result: The program should stop running. Actual result: Entire computer freezes. Soundcard continuously plays the last second of audio. No response from any input devices or the network. The bug can also be reproduced by playing the game Borderlands 2 while having a wired xbox controller connected. The system will randomly freeze in the exact same way. The bug has existed since at least 14.04. The last thing the kernel prints is this: Apr 1 03:38:29 al-desktop kernel: [94142.404218] usb 7-3: new full-speed USB device number 2 using ohci-pci Apr 1 03:38:29 al-desktop kernel: [94142.565264] usb 7-3: New USB device found, idVendor=045e, idProduct=0288 Apr 1 03:38:29 al-desktop kernel: [94142.565268] usb 7-3: New USB device strings: Mfr=0, Product=0, SerialNumber=0 Apr 1 03:38:29 al-desktop kernel: [94142.567304] hub 7-3:1.0: USB hub found Apr 1 03:38:29 al-desktop kernel: [94142.569259] hub 7-3:1.0: 3 ports detected Apr 1 03:38:29 al-desktop kernel: [94142.852248] usb 7-3.1: new full-speed USB device number 3 using ohci-pci Apr 1 03:38:29 al-desktop kernel: [94142.949301] usb 7-3.1: New USB device found, idVendor=045e, idProduct=0289 Apr 1 03:38:29 al-desktop kernel: [94142.949308] usb 7-3.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 Apr 1 03:38:29 al-desktop kernel: [94142.982402] input: Microsoft X-Box pad v2 (US) as /devices/pci:00/:00:13.0/usb7/7-3/7-3.1/7-3.1:1.0/input/input23 Apr 1 03:38:29 al-desktop kernel: [94142.982503] usbcore: registered new interface driver xpad Apr 1 03:40:09 al-desktop kernel: [94242.318271] [ cut here ] Apr 1 03:40:09 al-desktop kernel: [94242.318280] WARNING: CPU: 3 PID: 16529 at /build/linux-_Kv5oI/linux-4.2.0/drivers/usb/core/urb.c:339 usb_submit_urb+0x51/0x70() Apr 1 03:40:09 al-desktop kernel: [94242.318282] URB 880106cbacc0 submitted while active Apr 1 03:40:09 al-desktop kernel: [94242.318283] Modules linked in: joydev xpad ff_memless nvidia_uvm(POE) rfcomm pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) rc_pinnacle_pctv_hd em28xx_rc tda18271 cxd2820r em28xx_dvb d vb_core em28xx binfmt_misc bnep snd_hda_codec_hdmi rc_hauppauge ir_kbd_i2c tuner_simple tuner_types input_leds tuner uvcvideo videobuf2_vmalloc kvm_amd videobuf2_memops kvm btusb videobuf2_core btrtl snd_seq_midi btbcm snd_seq_midi_event btintel snd_usb_audio snd_usbmidi_lib snd_hda_codec_via msp3400 snd_hda_codec_generic snd_rawmidi bluetooth nvidia(POE) snd_seq serio_raw snd_hda_intel snd_seq_device snd_hda_codec snd_hda_core snd_hwdep bttv k10temp tea575x tveeprom edac _core videobuf_dma_sg edac_mce_amd rc_core videobuf_core snd_bt87x v4l2_common videodev snd_pcm media i2c_algo_bit snd_timer i2c_piix4 snd soundcore drm shpchp wmi 8250_fintek asus_atk0110 mac_hid parport_pc ppdev lp parport autofs4 uas u sb_storage hid_generic usbhid hid pata_acpi psmouse pata_atiixp ahci libahci r8169 mii Apr 1 03:40:09 al-desktop kernel: [94242.318324] CPU: 3 PID: 16529 Comm: testrumble Tainted: P OE 4.2.0-34-generic #39-Ubuntu Apr 1 03:40:09 al-desktop kernel: [94242.318326] Hardware name: System manufacturer System Product Name/M4A79XTD EVO, BIOS 210206/17/2010 Apr 1 03:40:09 al-desktop kernel: [94242.318328] 4da02d75 88010a9c3ba8 817ebed3 Apr 1 03:40:09 al-desktop kernel: [94242.318330] 88010a9c3c00 88010a9c3be8 8107b986 Apr 1 03:40:09 al-desktop kernel: [94242.318331] 88010a9c3bd8 0010 880103216f08 88010a9c3cd0 Apr 1 03:40:09 al-desktop kernel: [94242.318333] Call Trace: Apr 1 03:40:09 al-desktop kernel: [94242.318337] [] dump_stack+0x45/0x57 Apr 1 03:40:09 al-desktop kernel: [94242.318340] [] warn_slowpath_common+0x86/0xc0 Apr 1 03:40:09 al-desktop kernel: [94242.318342] [] warn_slowpath_fmt+0x55/0x70 Apr 1 03:40:09 al-desktop kernel: [94242.318345] [] usb_submit_urb+0x51/0x70 Apr 1 03:40:09 al-desktop kernel: [94242.318348] [] xpad_play_effect+0x130/0x240 [xpad] Apr 1 03:40:09 al-desktop kernel: [94242.318351] [] ml_play_effects+0x104/0x6b0 [ff_memless] Apr 1 03:40:09 al-desktop kernel: [94242.318353] [] ml_ff_playback+0x85/0x100 [ff_memless] Apr 1 03:40:09 al-desk
[Kernel-packages] [Bug 1575250] [NEW] close laptop lid = complete system freeze
Public bug reported: To reproduce: 1. Close laptop lid. 2. Wait a couple of minutes. 3. Open laptop lid. Result: the screen remains powered off and the system will not respond in any way. Pressing keys does nothing. Pressing the power button does nothing. There is no disk activity but the power light is lit. The only thing you can do is press the power button for four seconds or remove the battery. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-21-generic 4.4.0-21.37 [modified: boot/vmlinuz-4.4.0-21-generic] ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: al 1892 F pulseaudio CurrentDesktop: Unity Date: Tue Apr 26 16:46:08 2016 HibernationDevice: RESUME=UUID=8623f57e-2fc2-4a9a-bd35-73f33e1aeb59 InstallationDate: Installed on 2016-04-21 (4 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: LENOVO 20040M18 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic root=UUID=0f83fbb5-4903-4610-9f32-1ab22c935bb0 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-21-generic N/A linux-backports-modules-4.4.0-21-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/11/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 24CN61WW dmi.board.name: Caucasus2 dmi.board.vendor: LENOVO dmi.board.version: Rev 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Lenovo dmi.chassis.version: Rev 1.0 dmi.modalias: dmi:bvnLENOVO:bvr24CN61WW:bd08/11/2010:svnLENOVO:pn20040M18:pvrLenovoIdeapadS10-3t:rvnLENOVO:rnCaucasus2:rvrRev1.0:cvnLenovo:ct10:cvrRev1.0: dmi.product.name: 20040M18 dmi.product.version: Lenovo Ideapad S10-3t dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- 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/1575250 Title: close laptop lid = complete system freeze Status in linux package in Ubuntu: New Bug description: To reproduce: 1. Close laptop lid. 2. Wait a couple of minutes. 3. Open laptop lid. Result: the screen remains powered off and the system will not respond in any way. Pressing keys does nothing. Pressing the power button does nothing. There is no disk activity but the power light is lit. The only thing you can do is press the power button for four seconds or remove the battery. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-21-generic 4.4.0-21.37 [modified: boot/vmlinuz-4.4.0-21-generic] ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: al 1892 F pulseaudio CurrentDesktop: Unity Date: Tue Apr 26 16:46:08 2016 HibernationDevice: RESUME=UUID=8623f57e-2fc2-4a9a-bd35-73f33e1aeb59 InstallationDate: Installed on 2016-04-21 (4 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: LENOVO 20040M18 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic root=UUID=0f83fbb5-4903-4610-9f32-1ab22c935bb0 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-21-generic N/A linux-backports-modules-4.4.0-21-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/11/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 24CN61WW dmi.board.name: Caucasus2 dmi.board.vendor: LENOVO dmi.board.version: Rev 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Lenovo dmi.chassis.version: Rev 1.0 dmi.modalias: dmi:bvnLENOVO:bvr24CN61WW:bd08/11/2010:svnLENOVO:pn20040M18:pvrLenovoIdeapadS10-3t:rvnLENOVO:rnCaucasus2:rvrRev1.0:cvnLenovo:ct10:cvrRev1.0: dmi.product.name: 20040M18 dmi.product.version: Lenovo Ideapad S10-3t dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1575250/+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 1574018] Re: Atheros AR9285 wifi does not work after warm boot
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** 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/1574018 Title: Atheros AR9285 wifi does not work after warm boot Status in linux package in Ubuntu: Confirmed Bug description: Wifi works correctly after cold boot. After warm boot the wifi hardware is detected correctly but cannot see any access points. This bug report was generated after a warm boot, ie while the bug is happening. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-21-generic 4.4.0-21.37 [modified: boot/vmlinuz-4.4.0-21-generic] ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: al 1515 F pulseaudio CurrentDesktop: Unity Date: Sat Apr 23 14:44:03 2016 HibernationDevice: RESUME=UUID=8623f57e-2fc2-4a9a-bd35-73f33e1aeb59 InstallationDate: Installed on 2016-04-21 (1 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: LENOVO 20040M18 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic root=UUID=0f83fbb5-4903-4610-9f32-1ab22c935bb0 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-21-generic N/A linux-backports-modules-4.4.0-21-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/11/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 24CN61WW dmi.board.name: Caucasus2 dmi.board.vendor: LENOVO dmi.board.version: Rev 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Lenovo dmi.chassis.version: Rev 1.0 dmi.modalias: dmi:bvnLENOVO:bvr24CN61WW:bd08/11/2010:svnLENOVO:pn20040M18:pvrLenovoIdeapadS10-3t:rvnLENOVO:rnCaucasus2:rvrRev1.0:cvnLenovo:ct10:cvrRev1.0: dmi.product.name: 20040M18 dmi.product.version: Lenovo Ideapad S10-3t dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1574018/+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 1575250] Re: close laptop lid = complete system freeze
** Tags added: kernel-bug-exists-upstream ** 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/1575250 Title: close laptop lid = complete system freeze Status in linux package in Ubuntu: Confirmed Bug description: To reproduce: 1. Close laptop lid. 2. Wait a couple of minutes. 3. Open laptop lid. Result: the screen remains powered off and the system will not respond in any way. Pressing keys does nothing. Pressing the power button does nothing. There is no disk activity but the power light is lit. The only thing you can do is press the power button for four seconds or remove the battery. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-21-generic 4.4.0-21.37 [modified: boot/vmlinuz-4.4.0-21-generic] ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: al 1892 F pulseaudio CurrentDesktop: Unity Date: Tue Apr 26 16:46:08 2016 HibernationDevice: RESUME=UUID=8623f57e-2fc2-4a9a-bd35-73f33e1aeb59 InstallationDate: Installed on 2016-04-21 (4 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: LENOVO 20040M18 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic root=UUID=0f83fbb5-4903-4610-9f32-1ab22c935bb0 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-21-generic N/A linux-backports-modules-4.4.0-21-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/11/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 24CN61WW dmi.board.name: Caucasus2 dmi.board.vendor: LENOVO dmi.board.version: Rev 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Lenovo dmi.chassis.version: Rev 1.0 dmi.modalias: dmi:bvnLENOVO:bvr24CN61WW:bd08/11/2010:svnLENOVO:pn20040M18:pvrLenovoIdeapadS10-3t:rvnLENOVO:rnCaucasus2:rvrRev1.0:cvnLenovo:ct10:cvrRev1.0: dmi.product.name: 20040M18 dmi.product.version: Lenovo Ideapad S10-3t dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1575250/+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 1533804] [NEW] CPU fan speed regression since 15.04
Public bug reported: When running 14.04 my CPU fan speed increases relative to the CPU temperature, which keeps the temperature fairly constant. When running 15.04 or 15.10 the CPU fan speed is locked to the minimum until the temperature reaches 81 degrees, then it switches to maximum until the temperature falls below 72 degrees. Then it goes back to the minimum. This is both annoying and causes unnecessary stress to the hardware. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-23-generic 4.2.0-23.28 ProcVersionSignature: Ubuntu 4.2.0-23.28-generic 4.2.6 Uname: Linux 4.2.0-23-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Jan 13 19:13:51 2016 HibernationDevice: RESUME=UUID=5a0bdae5-ddc6-4b6f-aead-360c2949313a InstallationDate: Installed on 2015-07-12 (185 days ago) InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-23-generic root=UUID=283ec8d4-031f-4703-9de4-8dfe31132378 ro quiet splash RelatedPackageVersions: linux-restricted-modules-4.2.0-23-generic N/A linux-backports-modules-4.2.0-23-generic N/A linux-firmware1.149.3 RfKill: 1: hci1: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: Upgraded to wily on 2015-12-31 (12 days ago) dmi.bios.date: 11/25/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0704 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A79XTD EVO dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0X dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0704:bd11/25/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A79XTDEVO:rvrRevX.0X:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: linux (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 linux in Ubuntu. https://bugs.launchpad.net/bugs/1533804 Title: CPU fan speed regression since 15.04 Status in linux package in Ubuntu: New Bug description: When running 14.04 my CPU fan speed increases relative to the CPU temperature, which keeps the temperature fairly constant. When running 15.04 or 15.10 the CPU fan speed is locked to the minimum until the temperature reaches 81 degrees, then it switches to maximum until the temperature falls below 72 degrees. Then it goes back to the minimum. This is both annoying and causes unnecessary stress to the hardware. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-23-generic 4.2.0-23.28 ProcVersionSignature: Ubuntu 4.2.0-23.28-generic 4.2.6 Uname: Linux 4.2.0-23-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Jan 13 19:13:51 2016 HibernationDevice: RESUME=UUID=5a0bdae5-ddc6-4b6f-aead-360c2949313a InstallationDate: Installed on 2015-07-12 (185 days ago) InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-23-generic root=UUID=283ec8d4-031f-4703-9de4-8dfe31132378 ro quiet splash RelatedPackageVersions: linux-restricted-modules-4.2.0-23-generic N/A linux-backports-modules-4.2.0-23-generic N/A linux-firmware1.149.3 RfKill: 1: hci1: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: Upgraded to wily on 2015-12-31 (12 days ago) dmi.bios.date: 11/25/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0704 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A79XTD EVO dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0X dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0704:bd11/25/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A79XTDEVO:rvrRevX.0X:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.
[Kernel-packages] [Bug 1564901] Re: xpad rumble causes full system hang
Yes, I do, eg with Saints Row 3, the controller starts vibrating immediately and never stops. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-utopic in Ubuntu. https://bugs.launchpad.net/bugs/1564901 Title: xpad rumble causes full system hang Status in linux package in Ubuntu: In Progress Status in linux-lts-utopic package in Ubuntu: In Progress Status in linux-lts-vivid package in Ubuntu: In Progress Status in linux source package in Trusty: In Progress Status in linux source package in Wily: In Progress Status in linux source package in Xenial: In Progress Bug description: To reproduce: 1. Have a wired xbox controller. 2. Modify the SDL2 testrumble.c so it runs forever. (attached) 3. Build and run it. 4. Kill it with sigkill from another terminal. Expected result: The program should stop running. Actual result: Entire computer freezes. Soundcard continuously plays the last second of audio. No response from any input devices or the network. The bug can also be reproduced by playing the game Borderlands 2 while having a wired xbox controller connected. The system will randomly freeze in the exact same way. The bug has existed since at least 14.04. The last thing the kernel prints is this: Apr 1 03:38:29 al-desktop kernel: [94142.404218] usb 7-3: new full-speed USB device number 2 using ohci-pci Apr 1 03:38:29 al-desktop kernel: [94142.565264] usb 7-3: New USB device found, idVendor=045e, idProduct=0288 Apr 1 03:38:29 al-desktop kernel: [94142.565268] usb 7-3: New USB device strings: Mfr=0, Product=0, SerialNumber=0 Apr 1 03:38:29 al-desktop kernel: [94142.567304] hub 7-3:1.0: USB hub found Apr 1 03:38:29 al-desktop kernel: [94142.569259] hub 7-3:1.0: 3 ports detected Apr 1 03:38:29 al-desktop kernel: [94142.852248] usb 7-3.1: new full-speed USB device number 3 using ohci-pci Apr 1 03:38:29 al-desktop kernel: [94142.949301] usb 7-3.1: New USB device found, idVendor=045e, idProduct=0289 Apr 1 03:38:29 al-desktop kernel: [94142.949308] usb 7-3.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 Apr 1 03:38:29 al-desktop kernel: [94142.982402] input: Microsoft X-Box pad v2 (US) as /devices/pci:00/:00:13.0/usb7/7-3/7-3.1/7-3.1:1.0/input/input23 Apr 1 03:38:29 al-desktop kernel: [94142.982503] usbcore: registered new interface driver xpad Apr 1 03:40:09 al-desktop kernel: [94242.318271] [ cut here ] Apr 1 03:40:09 al-desktop kernel: [94242.318280] WARNING: CPU: 3 PID: 16529 at /build/linux-_Kv5oI/linux-4.2.0/drivers/usb/core/urb.c:339 usb_submit_urb+0x51/0x70() Apr 1 03:40:09 al-desktop kernel: [94242.318282] URB 880106cbacc0 submitted while active Apr 1 03:40:09 al-desktop kernel: [94242.318283] Modules linked in: joydev xpad ff_memless nvidia_uvm(POE) rfcomm pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) rc_pinnacle_pctv_hd em28xx_rc tda18271 cxd2820r em28xx_dvb d vb_core em28xx binfmt_misc bnep snd_hda_codec_hdmi rc_hauppauge ir_kbd_i2c tuner_simple tuner_types input_leds tuner uvcvideo videobuf2_vmalloc kvm_amd videobuf2_memops kvm btusb videobuf2_core btrtl snd_seq_midi btbcm snd_seq_midi_event btintel snd_usb_audio snd_usbmidi_lib snd_hda_codec_via msp3400 snd_hda_codec_generic snd_rawmidi bluetooth nvidia(POE) snd_seq serio_raw snd_hda_intel snd_seq_device snd_hda_codec snd_hda_core snd_hwdep bttv k10temp tea575x tveeprom edac _core videobuf_dma_sg edac_mce_amd rc_core videobuf_core snd_bt87x v4l2_common videodev snd_pcm media i2c_algo_bit snd_timer i2c_piix4 snd soundcore drm shpchp wmi 8250_fintek asus_atk0110 mac_hid parport_pc ppdev lp parport autofs4 uas u sb_storage hid_generic usbhid hid pata_acpi psmouse pata_atiixp ahci libahci r8169 mii Apr 1 03:40:09 al-desktop kernel: [94242.318324] CPU: 3 PID: 16529 Comm: testrumble Tainted: P OE 4.2.0-34-generic #39-Ubuntu Apr 1 03:40:09 al-desktop kernel: [94242.318326] Hardware name: System manufacturer System Product Name/M4A79XTD EVO, BIOS 210206/17/2010 Apr 1 03:40:09 al-desktop kernel: [94242.318328] 4da02d75 88010a9c3ba8 817ebed3 Apr 1 03:40:09 al-desktop kernel: [94242.318330] 88010a9c3c00 88010a9c3be8 8107b986 Apr 1 03:40:09 al-desktop kernel: [94242.318331] 88010a9c3bd8 0010 880103216f08 88010a9c3cd0 Apr 1 03:40:09 al-desktop kernel: [94242.318333] Call Trace: Apr 1 03:40:09 al-desktop kernel: [94242.318337] [] dump_stack+0x45/0x57 Apr 1 03:40:09 al-desktop kernel: [94242.318340] [] warn_slowpath_common+0x86/0xc0 Apr 1 03:40:09 al-desktop kernel: [94242.318342] [] warn_slowpath_fmt+0x55/0x70 Apr 1 03:40:09 al-desktop kernel: [94242.318345] [] usb_submit_urb+0x51/0x70 Apr 1 03:40:09 al-desktop kernel: [94242.318348] [] xpad_play_effect+
[Kernel-packages] [Bug 1574018] [NEW] Atheros AR9285 wifi does not work after warm boot
Public bug reported: Wifi works correctly after cold boot. After warm boot the wifi hardware is detected correctly but cannot see any access points. This bug report was generated after a warm boot, ie while the bug is happening. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-21-generic 4.4.0-21.37 [modified: boot/vmlinuz-4.4.0-21-generic] ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: al 1515 F pulseaudio CurrentDesktop: Unity Date: Sat Apr 23 14:44:03 2016 HibernationDevice: RESUME=UUID=8623f57e-2fc2-4a9a-bd35-73f33e1aeb59 InstallationDate: Installed on 2016-04-21 (1 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: LENOVO 20040M18 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic root=UUID=0f83fbb5-4903-4610-9f32-1ab22c935bb0 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-21-generic N/A linux-backports-modules-4.4.0-21-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/11/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 24CN61WW dmi.board.name: Caucasus2 dmi.board.vendor: LENOVO dmi.board.version: Rev 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Lenovo dmi.chassis.version: Rev 1.0 dmi.modalias: dmi:bvnLENOVO:bvr24CN61WW:bd08/11/2010:svnLENOVO:pn20040M18:pvrLenovoIdeapadS10-3t:rvnLENOVO:rnCaucasus2:rvrRev1.0:cvnLenovo:ct10:cvrRev1.0: dmi.product.name: 20040M18 dmi.product.version: Lenovo Ideapad S10-3t dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug xenial ** Description changed: - as title. + Wifi works correctly after cold boot. + + After warm boot the wifi hardware is detected correctly but cannot see + any access points. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-21-generic 4.4.0-21.37 [modified: boot/vmlinuz-4.4.0-21-generic] ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: al 1515 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: al 1515 F pulseaudio CurrentDesktop: Unity Date: Sat Apr 23 14:44:03 2016 HibernationDevice: RESUME=UUID=8623f57e-2fc2-4a9a-bd35-73f33e1aeb59 InstallationDate: Installed on 2016-04-21 (1 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: LENOVO 20040M18 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic root=UUID=0f83fbb5-4903-4610-9f32-1ab22c935bb0 ro quiet splash vt.handoff=7 RelatedPackageVersions: - linux-restricted-modules-4.4.0-21-generic N/A - linux-backports-modules-4.4.0-21-generic N/A - linux-firmware1.157 + linux-restricted-modules-4.4.0-21-generic N/A + linux-backports-modules-4.4.0-21-generic N/A + linux-firmware1.157 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/11/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 24CN61WW dmi.board.name: Caucasus2 dmi.board.vendor: LENOVO dmi.board.version: Rev 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Lenovo dmi.chassis.version: Rev 1.0 dmi.modalias: dmi:bvnLENOVO:bvr24CN61WW:bd08/11/2010:svnLENOVO:pn20040M18:pvrLenovoIdeapadS10-3t:rvnLENOVO:rnCaucasus2:rvrRev1.0:cvnLenovo:ct10:cvrRev1.0: dmi.product.name: 20040M18 dmi.product.version: Lenovo Ideapad S10-3t dmi.sys.vendor: LENOVO ** Description changed: Wifi works correctly after cold boot. After warm boot the wifi hardware is detected correctly but cannot see any access points. + + This bug report was generated after a warm boot, ie while the bug is + happening. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-21-generic 4.4.0-21.37 [modified: boot/vmlinuz-4.4.0-21-generic] ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: al 1515 F pulseaudio CurrentDesktop: Unity Date: Sat Apr 23 14:44:03 2016 HibernationDevice: RESUME=UUID=8623f57e-2fc2-4a9a-bd35-73f33e1aeb59 InstallationDate: Installed on 2016-04-21 (1 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: LENOVO 20040M1
[Kernel-packages] [Bug 1337641] [NEW] Oculus Rift "drifts" on recent kernels
Public bug reported: When running Oculus Rift compatible software, the HMD rotation seen by software drifts by a few degrees per second, even when the HMD is not moving at all (ie, it's sitting perfectly still on the desk). This is a regression in 3.13.0-27 and newer. Downgrading to 3.13.0-24 prevents the bug from happening. The bug happens after using the OR in hidraw mode (which is what the OVR SDK uses), and will even persist if you reboot into Windows without power cycling the device. OpenHMD is an alternative SDK for the Oculus Rift. When using OpenHMD in libusb mode the problem does not happen, unless you have previously used some software which opens the OR in hidraw mode. OpenHMD can also be compiled to use hidraw, and if you do that it just shows a black screen with the example. If you then run it in libusb mode, the drift happens. This bug has been reported on the Oculus forums: https://developer.oculusvr.com/forums/viewtopic.php?f=34&t=9689 To me this looks like a HID bug. Something is messing up the state of the hardware so badly that it will continue to report bad data even when using software that works correctly after a power cycle. Looking at the commits between -24 and -27 kernels I see a bunch of commits to HID which look like they might be responsible for this. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-30-generic 3.13.0-30.54 ProcVersionSignature: Ubuntu 3.13.0-30.54-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: al 1999 F pulseaudio /dev/snd/controlC1: al 1999 F pulseaudio /dev/snd/controlC0: al 1999 F pulseaudio CurrentDesktop: XFCE Date: Fri Jul 4 01:07:13 2014 HibernationDevice: RESUME=UUID=cd4b4f29-2984-430a-8556-26b5fd58d903 InstallationDate: Installed on 2014-06-29 (4 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-30-generic root=UUID=06500b4e-b446-411c-9a19-cfff649a7be4 ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.13.0-30-generic N/A linux-backports-modules-3.13.0-30-generic N/A linux-firmware 1.127.4 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0704 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A79XTD EVO dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0X dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0704:bd11/25/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A79XTDEVO:rvrRevX.0X:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug trusty -- 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/1337641 Title: Oculus Rift "drifts" on recent kernels Status in “linux” package in Ubuntu: Confirmed Bug description: When running Oculus Rift compatible software, the HMD rotation seen by software drifts by a few degrees per second, even when the HMD is not moving at all (ie, it's sitting perfectly still on the desk). This is a regression in 3.13.0-27 and newer. Downgrading to 3.13.0-24 prevents the bug from happening. The bug happens after using the OR in hidraw mode (which is what the OVR SDK uses), and will even persist if you reboot into Windows without power cycling the device. OpenHMD is an alternative SDK for the Oculus Rift. When using OpenHMD in libusb mode the problem does not happen, unless you have previously used some software which opens the OR in hidraw mode. OpenHMD can also be compiled to use hidraw, and if you do that it just shows a black screen with the example. If you then run it in libusb mode, the drift happens. This bug has been reported on the Oculus forums: https://developer.oculusvr.com/forums/viewtopic.php?f=34&t=9689 To me this looks like a HID bug. Something is messing up the state of the hardware so badly that it will continue to report bad data even when using software that works correctly after a power cycle. Looking at the commits between -24 and -27 kernels I
[Kernel-packages] [Bug 1337641] Re: Oculus Rift "drifts" on recent kernels
I forgot to mention this, but the way OpenHMD switches modes is by using the hidapi library, which has two versions for libusb and hidraw. You just link against the one you want. So the code is doing the exact same thing in each case, and the HID version of it doesn't work. That's why I think it is a HID bug. -- 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/1337641 Title: Oculus Rift "drifts" on recent kernels Status in “linux” package in Ubuntu: Confirmed Bug description: When running Oculus Rift compatible software, the HMD rotation seen by software drifts by a few degrees per second, even when the HMD is not moving at all (ie, it's sitting perfectly still on the desk). This is a regression in 3.13.0-27 and newer. Downgrading to 3.13.0-24 prevents the bug from happening. The bug happens after using the OR in hidraw mode (which is what the OVR SDK uses), and will even persist if you reboot into Windows without power cycling the device. OpenHMD is an alternative SDK for the Oculus Rift. When using OpenHMD in libusb mode the problem does not happen, unless you have previously used some software which opens the OR in hidraw mode. OpenHMD can also be compiled to use hidraw, and if you do that it just shows a black screen with the example. If you then run it in libusb mode, the drift happens. This bug has been reported on the Oculus forums: https://developer.oculusvr.com/forums/viewtopic.php?f=34&t=9689 To me this looks like a HID bug. Something is messing up the state of the hardware so badly that it will continue to report bad data even when using software that works correctly after a power cycle. Looking at the commits between -24 and -27 kernels I see a bunch of commits to HID which look like they might be responsible for this. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-30-generic 3.13.0-30.54 ProcVersionSignature: Ubuntu 3.13.0-30.54-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: al 1999 F pulseaudio /dev/snd/controlC1: al 1999 F pulseaudio /dev/snd/controlC0: al 1999 F pulseaudio CurrentDesktop: XFCE Date: Fri Jul 4 01:07:13 2014 HibernationDevice: RESUME=UUID=cd4b4f29-2984-430a-8556-26b5fd58d903 InstallationDate: Installed on 2014-06-29 (4 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-30-generic root=UUID=06500b4e-b446-411c-9a19-cfff649a7be4 ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.13.0-30-generic N/A linux-backports-modules-3.13.0-30-generic N/A linux-firmware 1.127.4 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0704 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A79XTD EVO dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0X dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0704:bd11/25/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A79XTDEVO:rvrRevX.0X:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1337641/+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 1337641] Re: Oculus Rift "drifts" on recent kernels
*** This bug is a duplicate of bug 1353021 *** https://bugs.launchpad.net/bugs/1353021 ** This bug has been marked a duplicate of bug 1353021 USB HIDRAW Feature Report Implementation for HID devices not working correctly in Ubuntu 14.04 -- 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/1337641 Title: Oculus Rift "drifts" on recent kernels Status in “linux” package in Ubuntu: Confirmed Bug description: When running Oculus Rift compatible software, the HMD rotation seen by software drifts by a few degrees per second, even when the HMD is not moving at all (ie, it's sitting perfectly still on the desk). This is a regression in 3.13.0-27 and newer. Downgrading to 3.13.0-24 prevents the bug from happening. The bug happens after using the OR in hidraw mode (which is what the OVR SDK uses), and will even persist if you reboot into Windows without power cycling the device. OpenHMD is an alternative SDK for the Oculus Rift. When using OpenHMD in libusb mode the problem does not happen, unless you have previously used some software which opens the OR in hidraw mode. OpenHMD can also be compiled to use hidraw, and if you do that it just shows a black screen with the example. If you then run it in libusb mode, the drift happens. This bug has been reported on the Oculus forums: https://developer.oculusvr.com/forums/viewtopic.php?f=34&t=9689 To me this looks like a HID bug. Something is messing up the state of the hardware so badly that it will continue to report bad data even when using software that works correctly after a power cycle. Looking at the commits between -24 and -27 kernels I see a bunch of commits to HID which look like they might be responsible for this. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-30-generic 3.13.0-30.54 ProcVersionSignature: Ubuntu 3.13.0-30.54-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: al 1999 F pulseaudio /dev/snd/controlC1: al 1999 F pulseaudio /dev/snd/controlC0: al 1999 F pulseaudio CurrentDesktop: XFCE Date: Fri Jul 4 01:07:13 2014 HibernationDevice: RESUME=UUID=cd4b4f29-2984-430a-8556-26b5fd58d903 InstallationDate: Installed on 2014-06-29 (4 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-30-generic root=UUID=06500b4e-b446-411c-9a19-cfff649a7be4 ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.13.0-30-generic N/A linux-backports-modules-3.13.0-30-generic N/A linux-firmware 1.127.4 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0704 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A79XTD EVO dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0X dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0704:bd11/25/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A79XTDEVO:rvrRevX.0X:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1337641/+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 1337641] Re: Oculus Rift "drifts" on recent kernels
This isn't a BIOS issue, it's been reproduced across multiple different hardwares including by the oculus developers themselves, and is a regression in the stable release. It's either a bug in the oculus driver code, or it's a bug in the kernel. ** Changed in: linux (Ubuntu) Status: Incomplete => New -- 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/1337641 Title: Oculus Rift "drifts" on recent kernels Status in “linux” package in Ubuntu: New Bug description: When running Oculus Rift compatible software, the HMD rotation seen by software drifts by a few degrees per second, even when the HMD is not moving at all (ie, it's sitting perfectly still on the desk). This is a regression in 3.13.0-27 and newer. Downgrading to 3.13.0-24 prevents the bug from happening. The bug happens after using the OR in hidraw mode (which is what the OVR SDK uses), and will even persist if you reboot into Windows without power cycling the device. OpenHMD is an alternative SDK for the Oculus Rift. When using OpenHMD in libusb mode the problem does not happen, unless you have previously used some software which opens the OR in hidraw mode. OpenHMD can also be compiled to use hidraw, and if you do that it just shows a black screen with the example. If you then run it in libusb mode, the drift happens. This bug has been reported on the Oculus forums: https://developer.oculusvr.com/forums/viewtopic.php?f=34&t=9689 To me this looks like a HID bug. Something is messing up the state of the hardware so badly that it will continue to report bad data even when using software that works correctly after a power cycle. Looking at the commits between -24 and -27 kernels I see a bunch of commits to HID which look like they might be responsible for this. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-30-generic 3.13.0-30.54 ProcVersionSignature: Ubuntu 3.13.0-30.54-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: al 1999 F pulseaudio /dev/snd/controlC1: al 1999 F pulseaudio /dev/snd/controlC0: al 1999 F pulseaudio CurrentDesktop: XFCE Date: Fri Jul 4 01:07:13 2014 HibernationDevice: RESUME=UUID=cd4b4f29-2984-430a-8556-26b5fd58d903 InstallationDate: Installed on 2014-06-29 (4 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-30-generic root=UUID=06500b4e-b446-411c-9a19-cfff649a7be4 ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.13.0-30-generic N/A linux-backports-modules-3.13.0-30-generic N/A linux-firmware 1.127.4 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0704 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A79XTD EVO dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0X dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0704:bd11/25/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A79XTDEVO:rvrRevX.0X:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1337641/+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 1284308] Re: Bogus "another operation in progress" error. Can't copy files from a bluetooth device
There is a much easier workaround. Just copy the files with terminal, or another file manager that isn't Nautilus. As such, I don't believe this is a fault with bluez or even gvfs, but with Nautilus or some other Gnome component. The really easy way to do it with Terminal: cd to the destination directory Type "cp" then a space Drag and drop all the files you want to copy from Nautilus to the terminal Type a space then "." then press enter. -- 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/1284308 Title: Bogus "another operation in progress" error. Can't copy files from a bluetooth device Status in “bluez” package in Ubuntu: Confirmed Bug description: I have upgraded to Ubuntu 13.10. And as usual, with the upgrade, a whole new bluetooth issue, which this times makes transferring files from the phone to the computer (which already was painful) completely impossible! How I reproduce (100% systematic): 1 - click on the Bluetooth icon in the notification area 2 - from the dropdown menu, choose "bluetooth settings" 3 - select the phone among the listed devices 4 - click on "Browse files" 5 - A Nautilus windows opens, allowing me to browse files on the phone. Open the DCIM/Camera folder 6 - Select a couple of files. Either drag and drop them, or copy and then paste them, into a folder on the computer => I systematically get an error, but it can be any of the two variants shown in the two screenshots (one says there was an error copying the file, the other says there was an error getting information about the file; in both cases the given reason is "another operation in progress". Note also that in one case there is a Retry button, in the other there is not - pure nonsense). I then "ejected" the phone with the eject button next to its name in Nautilus, and repeated the whole process. I randomly get any of three outcomes: - the one described above (MOST of the times) - at step 4, I get an error "This location could not be displayed. Another operation in progress", so I cannot even browse files or - at some point (not sure whether it was at step 4 above or when "ejecting" the phone) something CRASHES (I get the usual Ubuntu message informing me of that). ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3 Uname: Linux 3.11.0-17-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Mon Feb 24 21:24:05 2014 InstallationDate: Installed on 2013-10-11 (136 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) InterestingModules: bnep rfcomm btusb bluetooth MachineType: Acer Aspire V3-571G MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-17-generic root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to saucy on 2014-02-23 (1 days ago) dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.07 dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07: dmi.product.name: Aspire V3-571G dmi.product.version: V2.07 dmi.sys.vendor: Acer hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: A4:17:31:0D:4A:70 ACL MTU: 1022:8 SCO MTU: 183:5 UP RUNNING PSCAN ISCAN RX bytes:44318 acl:198 sco:0 events:355 errors:0 TX bytes:6132 acl:178 sco:0 commands:82 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1284308/+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 1284308] Re: Bogus "another operation in progress" error. Can't copy files from a bluetooth device
Today my workaround didn't work. This suggests the problem is in gvfsd or obex-data-server. ** Also affects: obex-data-server (Ubuntu) Importance: Undecided Status: New ** Also affects: gvfs (Ubuntu) Importance: Undecided Status: New ** Changed in: gvfs (Ubuntu) Status: New => Confirmed ** Changed in: obex-data-server (Ubuntu) Status: New => Confirmed -- 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/1284308 Title: Bogus "another operation in progress" error. Can't copy files from a bluetooth device Status in “bluez” package in Ubuntu: Confirmed Status in “gvfs” package in Ubuntu: Confirmed Status in “obex-data-server” package in Ubuntu: Confirmed Bug description: I have upgraded to Ubuntu 13.10. And as usual, with the upgrade, a whole new bluetooth issue, which this times makes transferring files from the phone to the computer (which already was painful) completely impossible! How I reproduce (100% systematic): 1 - click on the Bluetooth icon in the notification area 2 - from the dropdown menu, choose "bluetooth settings" 3 - select the phone among the listed devices 4 - click on "Browse files" 5 - A Nautilus windows opens, allowing me to browse files on the phone. Open the DCIM/Camera folder 6 - Select a couple of files. Either drag and drop them, or copy and then paste them, into a folder on the computer => I systematically get an error, but it can be any of the two variants shown in the two screenshots (one says there was an error copying the file, the other says there was an error getting information about the file; in both cases the given reason is "another operation in progress". Note also that in one case there is a Retry button, in the other there is not - pure nonsense). I then "ejected" the phone with the eject button next to its name in Nautilus, and repeated the whole process. I randomly get any of three outcomes: - the one described above (MOST of the times) - at step 4, I get an error "This location could not be displayed. Another operation in progress", so I cannot even browse files or - at some point (not sure whether it was at step 4 above or when "ejecting" the phone) something CRASHES (I get the usual Ubuntu message informing me of that). ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3 Uname: Linux 3.11.0-17-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Mon Feb 24 21:24:05 2014 InstallationDate: Installed on 2013-10-11 (136 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) InterestingModules: bnep rfcomm btusb bluetooth MachineType: Acer Aspire V3-571G MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-17-generic root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to saucy on 2014-02-23 (1 days ago) dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.07 dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07: dmi.product.name: Aspire V3-571G dmi.product.version: V2.07 dmi.sys.vendor: Acer hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: A4:17:31:0D:4A:70 ACL MTU: 1022:8 SCO MTU: 183:5 UP RUNNING PSCAN ISCAN RX bytes:44318 acl:198 sco:0 events:355 errors:0 TX bytes:6132 acl:178 sco:0 commands:82 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1284308/+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 1284308] Re: Bogus "another operation in progress" error. Can't copy files from a bluetooth device
Subsribed additional packages to try to get some eyes on this. -- 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/1284308 Title: Bogus "another operation in progress" error. Can't copy files from a bluetooth device Status in “bluez” package in Ubuntu: Confirmed Status in “gvfs” package in Ubuntu: Confirmed Status in “obex-data-server” package in Ubuntu: Confirmed Bug description: I have upgraded to Ubuntu 13.10. And as usual, with the upgrade, a whole new bluetooth issue, which this times makes transferring files from the phone to the computer (which already was painful) completely impossible! How I reproduce (100% systematic): 1 - click on the Bluetooth icon in the notification area 2 - from the dropdown menu, choose "bluetooth settings" 3 - select the phone among the listed devices 4 - click on "Browse files" 5 - A Nautilus windows opens, allowing me to browse files on the phone. Open the DCIM/Camera folder 6 - Select a couple of files. Either drag and drop them, or copy and then paste them, into a folder on the computer => I systematically get an error, but it can be any of the two variants shown in the two screenshots (one says there was an error copying the file, the other says there was an error getting information about the file; in both cases the given reason is "another operation in progress". Note also that in one case there is a Retry button, in the other there is not - pure nonsense). I then "ejected" the phone with the eject button next to its name in Nautilus, and repeated the whole process. I randomly get any of three outcomes: - the one described above (MOST of the times) - at step 4, I get an error "This location could not be displayed. Another operation in progress", so I cannot even browse files or - at some point (not sure whether it was at step 4 above or when "ejecting" the phone) something CRASHES (I get the usual Ubuntu message informing me of that). ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3 Uname: Linux 3.11.0-17-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Mon Feb 24 21:24:05 2014 InstallationDate: Installed on 2013-10-11 (136 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) InterestingModules: bnep rfcomm btusb bluetooth MachineType: Acer Aspire V3-571G MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-17-generic root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to saucy on 2014-02-23 (1 days ago) dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.07 dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07: dmi.product.name: Aspire V3-571G dmi.product.version: V2.07 dmi.sys.vendor: Acer hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: A4:17:31:0D:4A:70 ACL MTU: 1022:8 SCO MTU: 183:5 UP RUNNING PSCAN ISCAN RX bytes:44318 acl:198 sco:0 events:355 errors:0 TX bytes:6132 acl:178 sco:0 commands:82 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1284308/+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 1284308] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1284308/+attachment/4172995/+files/Dependencies.txt -- 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/1284308 Title: Bogus "another operation in progress" error. Can't copy files from a bluetooth device Status in “bluez” package in Ubuntu: Confirmed Status in “gvfs” package in Ubuntu: Confirmed Status in “obex-data-server” package in Ubuntu: Confirmed Bug description: I have upgraded to Ubuntu 13.10. And as usual, with the upgrade, a whole new bluetooth issue, which this times makes transferring files from the phone to the computer (which already was painful) completely impossible! How I reproduce (100% systematic): 1 - click on the Bluetooth icon in the notification area 2 - from the dropdown menu, choose "bluetooth settings" 3 - select the phone among the listed devices 4 - click on "Browse files" 5 - A Nautilus windows opens, allowing me to browse files on the phone. Open the DCIM/Camera folder 6 - Select a couple of files. Either drag and drop them, or copy and then paste them, into a folder on the computer => I systematically get an error, but it can be any of the two variants shown in the two screenshots (one says there was an error copying the file, the other says there was an error getting information about the file; in both cases the given reason is "another operation in progress". Note also that in one case there is a Retry button, in the other there is not - pure nonsense). I then "ejected" the phone with the eject button next to its name in Nautilus, and repeated the whole process. I randomly get any of three outcomes: - the one described above (MOST of the times) - at step 4, I get an error "This location could not be displayed. Another operation in progress", so I cannot even browse files or - at some point (not sure whether it was at step 4 above or when "ejecting" the phone) something CRASHES (I get the usual Ubuntu message informing me of that). ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3 Uname: Linux 3.11.0-17-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Mon Feb 24 21:24:05 2014 InstallationDate: Installed on 2013-10-11 (136 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) InterestingModules: bnep rfcomm btusb bluetooth MachineType: Acer Aspire V3-571G MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-17-generic root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to saucy on 2014-02-23 (1 days ago) dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.07 dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07: dmi.product.name: Aspire V3-571G dmi.product.version: V2.07 dmi.sys.vendor: Acer hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: A4:17:31:0D:4A:70 ACL MTU: 1022:8 SCO MTU: 183:5 UP RUNNING PSCAN ISCAN RX bytes:44318 acl:198 sco:0 events:355 errors:0 TX bytes:6132 acl:178 sco:0 commands:82 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1284308/+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 1284308] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1284308/+attachment/4172996/+files/Lspci.txt -- 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/1284308 Title: Bogus "another operation in progress" error. Can't copy files from a bluetooth device Status in “bluez” package in Ubuntu: Confirmed Status in “gvfs” package in Ubuntu: Confirmed Status in “obex-data-server” package in Ubuntu: Confirmed Bug description: I have upgraded to Ubuntu 13.10. And as usual, with the upgrade, a whole new bluetooth issue, which this times makes transferring files from the phone to the computer (which already was painful) completely impossible! How I reproduce (100% systematic): 1 - click on the Bluetooth icon in the notification area 2 - from the dropdown menu, choose "bluetooth settings" 3 - select the phone among the listed devices 4 - click on "Browse files" 5 - A Nautilus windows opens, allowing me to browse files on the phone. Open the DCIM/Camera folder 6 - Select a couple of files. Either drag and drop them, or copy and then paste them, into a folder on the computer => I systematically get an error, but it can be any of the two variants shown in the two screenshots (one says there was an error copying the file, the other says there was an error getting information about the file; in both cases the given reason is "another operation in progress". Note also that in one case there is a Retry button, in the other there is not - pure nonsense). I then "ejected" the phone with the eject button next to its name in Nautilus, and repeated the whole process. I randomly get any of three outcomes: - the one described above (MOST of the times) - at step 4, I get an error "This location could not be displayed. Another operation in progress", so I cannot even browse files or - at some point (not sure whether it was at step 4 above or when "ejecting" the phone) something CRASHES (I get the usual Ubuntu message informing me of that). ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3 Uname: Linux 3.11.0-17-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Mon Feb 24 21:24:05 2014 InstallationDate: Installed on 2013-10-11 (136 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) InterestingModules: bnep rfcomm btusb bluetooth MachineType: Acer Aspire V3-571G MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-17-generic root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to saucy on 2014-02-23 (1 days ago) dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.07 dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07: dmi.product.name: Aspire V3-571G dmi.product.version: V2.07 dmi.sys.vendor: Acer hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: A4:17:31:0D:4A:70 ACL MTU: 1022:8 SCO MTU: 183:5 UP RUNNING PSCAN ISCAN RX bytes:44318 acl:198 sco:0 events:355 errors:0 TX bytes:6132 acl:178 sco:0 commands:82 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1284308/+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 1284308] BootDmesg.txt
apport information ** Attachment added: "BootDmesg.txt" https://bugs.launchpad.net/bugs/1284308/+attachment/4172993/+files/BootDmesg.txt -- 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/1284308 Title: Bogus "another operation in progress" error. Can't copy files from a bluetooth device Status in “bluez” package in Ubuntu: Confirmed Status in “gvfs” package in Ubuntu: Confirmed Status in “obex-data-server” package in Ubuntu: Confirmed Bug description: I have upgraded to Ubuntu 13.10. And as usual, with the upgrade, a whole new bluetooth issue, which this times makes transferring files from the phone to the computer (which already was painful) completely impossible! How I reproduce (100% systematic): 1 - click on the Bluetooth icon in the notification area 2 - from the dropdown menu, choose "bluetooth settings" 3 - select the phone among the listed devices 4 - click on "Browse files" 5 - A Nautilus windows opens, allowing me to browse files on the phone. Open the DCIM/Camera folder 6 - Select a couple of files. Either drag and drop them, or copy and then paste them, into a folder on the computer => I systematically get an error, but it can be any of the two variants shown in the two screenshots (one says there was an error copying the file, the other says there was an error getting information about the file; in both cases the given reason is "another operation in progress". Note also that in one case there is a Retry button, in the other there is not - pure nonsense). I then "ejected" the phone with the eject button next to its name in Nautilus, and repeated the whole process. I randomly get any of three outcomes: - the one described above (MOST of the times) - at step 4, I get an error "This location could not be displayed. Another operation in progress", so I cannot even browse files or - at some point (not sure whether it was at step 4 above or when "ejecting" the phone) something CRASHES (I get the usual Ubuntu message informing me of that). ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3 Uname: Linux 3.11.0-17-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Mon Feb 24 21:24:05 2014 InstallationDate: Installed on 2013-10-11 (136 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) InterestingModules: bnep rfcomm btusb bluetooth MachineType: Acer Aspire V3-571G MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-17-generic root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to saucy on 2014-02-23 (1 days ago) dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.07 dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07: dmi.product.name: Aspire V3-571G dmi.product.version: V2.07 dmi.sys.vendor: Acer hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: A4:17:31:0D:4A:70 ACL MTU: 1022:8 SCO MTU: 183:5 UP RUNNING PSCAN ISCAN RX bytes:44318 acl:198 sco:0 events:355 errors:0 TX bytes:6132 acl:178 sco:0 commands:82 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1284308/+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 1284308] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1284308/+attachment/4172997/+files/Lsusb.txt -- 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/1284308 Title: Bogus "another operation in progress" error. Can't copy files from a bluetooth device Status in “bluez” package in Ubuntu: Confirmed Status in “gvfs” package in Ubuntu: Confirmed Status in “obex-data-server” package in Ubuntu: Confirmed Bug description: I have upgraded to Ubuntu 13.10. And as usual, with the upgrade, a whole new bluetooth issue, which this times makes transferring files from the phone to the computer (which already was painful) completely impossible! How I reproduce (100% systematic): 1 - click on the Bluetooth icon in the notification area 2 - from the dropdown menu, choose "bluetooth settings" 3 - select the phone among the listed devices 4 - click on "Browse files" 5 - A Nautilus windows opens, allowing me to browse files on the phone. Open the DCIM/Camera folder 6 - Select a couple of files. Either drag and drop them, or copy and then paste them, into a folder on the computer => I systematically get an error, but it can be any of the two variants shown in the two screenshots (one says there was an error copying the file, the other says there was an error getting information about the file; in both cases the given reason is "another operation in progress". Note also that in one case there is a Retry button, in the other there is not - pure nonsense). I then "ejected" the phone with the eject button next to its name in Nautilus, and repeated the whole process. I randomly get any of three outcomes: - the one described above (MOST of the times) - at step 4, I get an error "This location could not be displayed. Another operation in progress", so I cannot even browse files or - at some point (not sure whether it was at step 4 above or when "ejecting" the phone) something CRASHES (I get the usual Ubuntu message informing me of that). ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3 Uname: Linux 3.11.0-17-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Mon Feb 24 21:24:05 2014 InstallationDate: Installed on 2013-10-11 (136 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) InterestingModules: bnep rfcomm btusb bluetooth MachineType: Acer Aspire V3-571G MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-17-generic root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to saucy on 2014-02-23 (1 days ago) dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.07 dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07: dmi.product.name: Aspire V3-571G dmi.product.version: V2.07 dmi.sys.vendor: Acer hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: A4:17:31:0D:4A:70 ACL MTU: 1022:8 SCO MTU: 183:5 UP RUNNING PSCAN ISCAN RX bytes:44318 acl:198 sco:0 events:355 errors:0 TX bytes:6132 acl:178 sco:0 commands:82 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1284308/+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 1284308] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1284308/+attachment/4172994/+files/CurrentDmesg.txt -- 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/1284308 Title: Bogus "another operation in progress" error. Can't copy files from a bluetooth device Status in “bluez” package in Ubuntu: Confirmed Status in “gvfs” package in Ubuntu: Confirmed Status in “obex-data-server” package in Ubuntu: Confirmed Bug description: I have upgraded to Ubuntu 13.10. And as usual, with the upgrade, a whole new bluetooth issue, which this times makes transferring files from the phone to the computer (which already was painful) completely impossible! How I reproduce (100% systematic): 1 - click on the Bluetooth icon in the notification area 2 - from the dropdown menu, choose "bluetooth settings" 3 - select the phone among the listed devices 4 - click on "Browse files" 5 - A Nautilus windows opens, allowing me to browse files on the phone. Open the DCIM/Camera folder 6 - Select a couple of files. Either drag and drop them, or copy and then paste them, into a folder on the computer => I systematically get an error, but it can be any of the two variants shown in the two screenshots (one says there was an error copying the file, the other says there was an error getting information about the file; in both cases the given reason is "another operation in progress". Note also that in one case there is a Retry button, in the other there is not - pure nonsense). I then "ejected" the phone with the eject button next to its name in Nautilus, and repeated the whole process. I randomly get any of three outcomes: - the one described above (MOST of the times) - at step 4, I get an error "This location could not be displayed. Another operation in progress", so I cannot even browse files or - at some point (not sure whether it was at step 4 above or when "ejecting" the phone) something CRASHES (I get the usual Ubuntu message informing me of that). ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3 Uname: Linux 3.11.0-17-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Mon Feb 24 21:24:05 2014 InstallationDate: Installed on 2013-10-11 (136 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) InterestingModules: bnep rfcomm btusb bluetooth MachineType: Acer Aspire V3-571G MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-17-generic root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to saucy on 2014-02-23 (1 days ago) dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.07 dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07: dmi.product.name: Aspire V3-571G dmi.product.version: V2.07 dmi.sys.vendor: Acer hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: A4:17:31:0D:4A:70 ACL MTU: 1022:8 SCO MTU: 183:5 UP RUNNING PSCAN ISCAN RX bytes:44318 acl:198 sco:0 events:355 errors:0 TX bytes:6132 acl:178 sco:0 commands:82 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1284308/+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 1284308] Re: Bogus "another operation in progress" error. Can't copy files from a bluetooth device
ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2013-12-22 (228 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) InterestingModules: btusb rfcomm bnep bluetooth MachineType: ASUS All Series Package: obex-data-server PackageArchitecture: amd64 ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic.efi.signed root=UUID=e1e7d1a7-19e8-4203-ad6a-86a144db61bc ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Tags: trusty Uname: Linux 3.13.0-32-generic x86_64 UpgradeStatus: Upgraded to trusty on 2014-06-20 (49 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 04/10/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0401 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H87M-E dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0401:bd04/10/2013:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH87M-E:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS hciconfig: hci0: Type: BR/EDR Bus: USB BD Address: 00:0A:3A:56:79:E3 ACL MTU: 192:8 SCO MTU: 64:8 UP RUNNING PSCAN ISCAN RX bytes:7596474 acl:34665 sco:0 events:3541 errors:0 TX bytes:195498 acl:3728 sco:0 commands:44 errors:0 rfkill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no syslog: Aug 8 17:10:10 stuart-desktop bluetoothd[667]: Adapter /org/bluez/667/hci0 has been disabled Aug 8 17:27:48 stuart-desktop bluetoothd[667]: Adapter /org/bluez/667/hci0 has been enabled ** Tags added: apport-collected trusty -- 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/1284308 Title: Bogus "another operation in progress" error. Can't copy files from a bluetooth device Status in “bluez” package in Ubuntu: Confirmed Status in “gvfs” package in Ubuntu: Confirmed Status in “obex-data-server” package in Ubuntu: Confirmed Bug description: I have upgraded to Ubuntu 13.10. And as usual, with the upgrade, a whole new bluetooth issue, which this times makes transferring files from the phone to the computer (which already was painful) completely impossible! How I reproduce (100% systematic): 1 - click on the Bluetooth icon in the notification area 2 - from the dropdown menu, choose "bluetooth settings" 3 - select the phone among the listed devices 4 - click on "Browse files" 5 - A Nautilus windows opens, allowing me to browse files on the phone. Open the DCIM/Camera folder 6 - Select a couple of files. Either drag and drop them, or copy and then paste them, into a folder on the computer => I systematically get an error, but it can be any of the two variants shown in the two screenshots (one says there was an error copying the file, the other says there was an error getting information about the file; in both cases the given reason is "another operation in progress". Note also that in one case there is a Retry button, in the other there is not - pure nonsense). I then "ejected" the phone with the eject button next to its name in Nautilus, and repeated the whole process. I randomly get any of three outcomes: - the one described above (MOST of the times) - at step 4, I get an error "This location could not be displayed. Another operation in progress", so I cannot even browse files or - at some point (not sure whether it was at step 4 above or when "ejecting" the phone) something CRASHES (I get the usual Ubuntu message informing me of that). ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3 Uname: Linux 3.11.0-17-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Mon Feb 24 21:24:05 2014 InstallationDate: Installed on 2013-10-11 (136 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) InterestingModules: bnep rfcomm btusb bluetooth MachineType: Acer Aspire V3-571G MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-17-generic root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to saucy on 2014-02-23 (1 days ago) dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.ver
[Kernel-packages] [Bug 1284308] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1284308/+attachment/4172998/+files/ProcCpuinfo.txt -- 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/1284308 Title: Bogus "another operation in progress" error. Can't copy files from a bluetooth device Status in “bluez” package in Ubuntu: Confirmed Status in “gvfs” package in Ubuntu: Confirmed Status in “obex-data-server” package in Ubuntu: Confirmed Bug description: I have upgraded to Ubuntu 13.10. And as usual, with the upgrade, a whole new bluetooth issue, which this times makes transferring files from the phone to the computer (which already was painful) completely impossible! How I reproduce (100% systematic): 1 - click on the Bluetooth icon in the notification area 2 - from the dropdown menu, choose "bluetooth settings" 3 - select the phone among the listed devices 4 - click on "Browse files" 5 - A Nautilus windows opens, allowing me to browse files on the phone. Open the DCIM/Camera folder 6 - Select a couple of files. Either drag and drop them, or copy and then paste them, into a folder on the computer => I systematically get an error, but it can be any of the two variants shown in the two screenshots (one says there was an error copying the file, the other says there was an error getting information about the file; in both cases the given reason is "another operation in progress". Note also that in one case there is a Retry button, in the other there is not - pure nonsense). I then "ejected" the phone with the eject button next to its name in Nautilus, and repeated the whole process. I randomly get any of three outcomes: - the one described above (MOST of the times) - at step 4, I get an error "This location could not be displayed. Another operation in progress", so I cannot even browse files or - at some point (not sure whether it was at step 4 above or when "ejecting" the phone) something CRASHES (I get the usual Ubuntu message informing me of that). ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3 Uname: Linux 3.11.0-17-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Mon Feb 24 21:24:05 2014 InstallationDate: Installed on 2013-10-11 (136 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) InterestingModules: bnep rfcomm btusb bluetooth MachineType: Acer Aspire V3-571G MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-17-generic root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to saucy on 2014-02-23 (1 days ago) dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.07 dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07: dmi.product.name: Aspire V3-571G dmi.product.version: V2.07 dmi.sys.vendor: Acer hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: A4:17:31:0D:4A:70 ACL MTU: 1022:8 SCO MTU: 183:5 UP RUNNING PSCAN ISCAN RX bytes:44318 acl:198 sco:0 events:355 errors:0 TX bytes:6132 acl:178 sco:0 commands:82 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1284308/+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 1284308] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1284308/+attachment/4173001/+files/ProcModules.txt -- 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/1284308 Title: Bogus "another operation in progress" error. Can't copy files from a bluetooth device Status in “bluez” package in Ubuntu: Confirmed Status in “gvfs” package in Ubuntu: Confirmed Status in “obex-data-server” package in Ubuntu: Confirmed Bug description: I have upgraded to Ubuntu 13.10. And as usual, with the upgrade, a whole new bluetooth issue, which this times makes transferring files from the phone to the computer (which already was painful) completely impossible! How I reproduce (100% systematic): 1 - click on the Bluetooth icon in the notification area 2 - from the dropdown menu, choose "bluetooth settings" 3 - select the phone among the listed devices 4 - click on "Browse files" 5 - A Nautilus windows opens, allowing me to browse files on the phone. Open the DCIM/Camera folder 6 - Select a couple of files. Either drag and drop them, or copy and then paste them, into a folder on the computer => I systematically get an error, but it can be any of the two variants shown in the two screenshots (one says there was an error copying the file, the other says there was an error getting information about the file; in both cases the given reason is "another operation in progress". Note also that in one case there is a Retry button, in the other there is not - pure nonsense). I then "ejected" the phone with the eject button next to its name in Nautilus, and repeated the whole process. I randomly get any of three outcomes: - the one described above (MOST of the times) - at step 4, I get an error "This location could not be displayed. Another operation in progress", so I cannot even browse files or - at some point (not sure whether it was at step 4 above or when "ejecting" the phone) something CRASHES (I get the usual Ubuntu message informing me of that). ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3 Uname: Linux 3.11.0-17-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Mon Feb 24 21:24:05 2014 InstallationDate: Installed on 2013-10-11 (136 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) InterestingModules: bnep rfcomm btusb bluetooth MachineType: Acer Aspire V3-571G MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-17-generic root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to saucy on 2014-02-23 (1 days ago) dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.07 dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07: dmi.product.name: Aspire V3-571G dmi.product.version: V2.07 dmi.sys.vendor: Acer hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: A4:17:31:0D:4A:70 ACL MTU: 1022:8 SCO MTU: 183:5 UP RUNNING PSCAN ISCAN RX bytes:44318 acl:198 sco:0 events:355 errors:0 TX bytes:6132 acl:178 sco:0 commands:82 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1284308/+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 1284308] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1284308/+attachment/4173000/+files/ProcInterrupts.txt -- 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/1284308 Title: Bogus "another operation in progress" error. Can't copy files from a bluetooth device Status in “bluez” package in Ubuntu: Confirmed Status in “gvfs” package in Ubuntu: Confirmed Status in “obex-data-server” package in Ubuntu: Confirmed Bug description: I have upgraded to Ubuntu 13.10. And as usual, with the upgrade, a whole new bluetooth issue, which this times makes transferring files from the phone to the computer (which already was painful) completely impossible! How I reproduce (100% systematic): 1 - click on the Bluetooth icon in the notification area 2 - from the dropdown menu, choose "bluetooth settings" 3 - select the phone among the listed devices 4 - click on "Browse files" 5 - A Nautilus windows opens, allowing me to browse files on the phone. Open the DCIM/Camera folder 6 - Select a couple of files. Either drag and drop them, or copy and then paste them, into a folder on the computer => I systematically get an error, but it can be any of the two variants shown in the two screenshots (one says there was an error copying the file, the other says there was an error getting information about the file; in both cases the given reason is "another operation in progress". Note also that in one case there is a Retry button, in the other there is not - pure nonsense). I then "ejected" the phone with the eject button next to its name in Nautilus, and repeated the whole process. I randomly get any of three outcomes: - the one described above (MOST of the times) - at step 4, I get an error "This location could not be displayed. Another operation in progress", so I cannot even browse files or - at some point (not sure whether it was at step 4 above or when "ejecting" the phone) something CRASHES (I get the usual Ubuntu message informing me of that). ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3 Uname: Linux 3.11.0-17-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Mon Feb 24 21:24:05 2014 InstallationDate: Installed on 2013-10-11 (136 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) InterestingModules: bnep rfcomm btusb bluetooth MachineType: Acer Aspire V3-571G MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-17-generic root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to saucy on 2014-02-23 (1 days ago) dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.07 dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07: dmi.product.name: Aspire V3-571G dmi.product.version: V2.07 dmi.sys.vendor: Acer hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: A4:17:31:0D:4A:70 ACL MTU: 1022:8 SCO MTU: 183:5 UP RUNNING PSCAN ISCAN RX bytes:44318 acl:198 sco:0 events:355 errors:0 TX bytes:6132 acl:178 sco:0 commands:82 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1284308/+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 1284308] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1284308/+attachment/4173002/+files/UdevDb.txt -- 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/1284308 Title: Bogus "another operation in progress" error. Can't copy files from a bluetooth device Status in “bluez” package in Ubuntu: Confirmed Status in “gvfs” package in Ubuntu: Confirmed Status in “obex-data-server” package in Ubuntu: Confirmed Bug description: I have upgraded to Ubuntu 13.10. And as usual, with the upgrade, a whole new bluetooth issue, which this times makes transferring files from the phone to the computer (which already was painful) completely impossible! How I reproduce (100% systematic): 1 - click on the Bluetooth icon in the notification area 2 - from the dropdown menu, choose "bluetooth settings" 3 - select the phone among the listed devices 4 - click on "Browse files" 5 - A Nautilus windows opens, allowing me to browse files on the phone. Open the DCIM/Camera folder 6 - Select a couple of files. Either drag and drop them, or copy and then paste them, into a folder on the computer => I systematically get an error, but it can be any of the two variants shown in the two screenshots (one says there was an error copying the file, the other says there was an error getting information about the file; in both cases the given reason is "another operation in progress". Note also that in one case there is a Retry button, in the other there is not - pure nonsense). I then "ejected" the phone with the eject button next to its name in Nautilus, and repeated the whole process. I randomly get any of three outcomes: - the one described above (MOST of the times) - at step 4, I get an error "This location could not be displayed. Another operation in progress", so I cannot even browse files or - at some point (not sure whether it was at step 4 above or when "ejecting" the phone) something CRASHES (I get the usual Ubuntu message informing me of that). ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3 Uname: Linux 3.11.0-17-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Mon Feb 24 21:24:05 2014 InstallationDate: Installed on 2013-10-11 (136 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) InterestingModules: bnep rfcomm btusb bluetooth MachineType: Acer Aspire V3-571G MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-17-generic root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to saucy on 2014-02-23 (1 days ago) dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.07 dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07: dmi.product.name: Aspire V3-571G dmi.product.version: V2.07 dmi.sys.vendor: Acer hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: A4:17:31:0D:4A:70 ACL MTU: 1022:8 SCO MTU: 183:5 UP RUNNING PSCAN ISCAN RX bytes:44318 acl:198 sco:0 events:355 errors:0 TX bytes:6132 acl:178 sco:0 commands:82 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1284308/+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 1284308] getfacl.txt
apport information ** Attachment added: "getfacl.txt" https://bugs.launchpad.net/bugs/1284308/+attachment/4173004/+files/getfacl.txt -- 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/1284308 Title: Bogus "another operation in progress" error. Can't copy files from a bluetooth device Status in “bluez” package in Ubuntu: Confirmed Status in “gvfs” package in Ubuntu: Confirmed Status in “obex-data-server” package in Ubuntu: Confirmed Bug description: I have upgraded to Ubuntu 13.10. And as usual, with the upgrade, a whole new bluetooth issue, which this times makes transferring files from the phone to the computer (which already was painful) completely impossible! How I reproduce (100% systematic): 1 - click on the Bluetooth icon in the notification area 2 - from the dropdown menu, choose "bluetooth settings" 3 - select the phone among the listed devices 4 - click on "Browse files" 5 - A Nautilus windows opens, allowing me to browse files on the phone. Open the DCIM/Camera folder 6 - Select a couple of files. Either drag and drop them, or copy and then paste them, into a folder on the computer => I systematically get an error, but it can be any of the two variants shown in the two screenshots (one says there was an error copying the file, the other says there was an error getting information about the file; in both cases the given reason is "another operation in progress". Note also that in one case there is a Retry button, in the other there is not - pure nonsense). I then "ejected" the phone with the eject button next to its name in Nautilus, and repeated the whole process. I randomly get any of three outcomes: - the one described above (MOST of the times) - at step 4, I get an error "This location could not be displayed. Another operation in progress", so I cannot even browse files or - at some point (not sure whether it was at step 4 above or when "ejecting" the phone) something CRASHES (I get the usual Ubuntu message informing me of that). ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3 Uname: Linux 3.11.0-17-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Mon Feb 24 21:24:05 2014 InstallationDate: Installed on 2013-10-11 (136 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) InterestingModules: bnep rfcomm btusb bluetooth MachineType: Acer Aspire V3-571G MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-17-generic root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to saucy on 2014-02-23 (1 days ago) dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.07 dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07: dmi.product.name: Aspire V3-571G dmi.product.version: V2.07 dmi.sys.vendor: Acer hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: A4:17:31:0D:4A:70 ACL MTU: 1022:8 SCO MTU: 183:5 UP RUNNING PSCAN ISCAN RX bytes:44318 acl:198 sco:0 events:355 errors:0 TX bytes:6132 acl:178 sco:0 commands:82 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1284308/+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 1284308] UdevLog.txt
apport information ** Attachment added: "UdevLog.txt" https://bugs.launchpad.net/bugs/1284308/+attachment/4173003/+files/UdevLog.txt -- 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/1284308 Title: Bogus "another operation in progress" error. Can't copy files from a bluetooth device Status in “bluez” package in Ubuntu: Confirmed Status in “gvfs” package in Ubuntu: Confirmed Status in “obex-data-server” package in Ubuntu: Confirmed Bug description: I have upgraded to Ubuntu 13.10. And as usual, with the upgrade, a whole new bluetooth issue, which this times makes transferring files from the phone to the computer (which already was painful) completely impossible! How I reproduce (100% systematic): 1 - click on the Bluetooth icon in the notification area 2 - from the dropdown menu, choose "bluetooth settings" 3 - select the phone among the listed devices 4 - click on "Browse files" 5 - A Nautilus windows opens, allowing me to browse files on the phone. Open the DCIM/Camera folder 6 - Select a couple of files. Either drag and drop them, or copy and then paste them, into a folder on the computer => I systematically get an error, but it can be any of the two variants shown in the two screenshots (one says there was an error copying the file, the other says there was an error getting information about the file; in both cases the given reason is "another operation in progress". Note also that in one case there is a Retry button, in the other there is not - pure nonsense). I then "ejected" the phone with the eject button next to its name in Nautilus, and repeated the whole process. I randomly get any of three outcomes: - the one described above (MOST of the times) - at step 4, I get an error "This location could not be displayed. Another operation in progress", so I cannot even browse files or - at some point (not sure whether it was at step 4 above or when "ejecting" the phone) something CRASHES (I get the usual Ubuntu message informing me of that). ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3 Uname: Linux 3.11.0-17-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Mon Feb 24 21:24:05 2014 InstallationDate: Installed on 2013-10-11 (136 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) InterestingModules: bnep rfcomm btusb bluetooth MachineType: Acer Aspire V3-571G MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-17-generic root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to saucy on 2014-02-23 (1 days ago) dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.07 dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07: dmi.product.name: Aspire V3-571G dmi.product.version: V2.07 dmi.sys.vendor: Acer hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: A4:17:31:0D:4A:70 ACL MTU: 1022:8 SCO MTU: 183:5 UP RUNNING PSCAN ISCAN RX bytes:44318 acl:198 sco:0 events:355 errors:0 TX bytes:6132 acl:178 sco:0 commands:82 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1284308/+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 1284308] Re: Bogus "another operation in progress" error. Can't copy files from a bluetooth device
That didn't really attach anything useful, oh well. Here's the log snippet from ~/.cache/upstart/dbus/ showing the error happening: ** (zeitgeist-fts:2146): WARNING **: Unable to get info on application://nautilus-autostart.desktop ** Message: transfer of Image010.jpg to /tmp/gvfsobexftp-tmp-S9DAKX started ** Message: filename: /Memory card/Images/Image010.jpg (Image010.jpg) copying to /tmp/gvfsobexftp-tmp-S9DAKX (retval 2) ** Message: transfer of Image010.jpg to /tmp/gvfsobexftp-tmp-NM4FKX started ** Message: filename: /Memory card/Images/Image010.jpg (Image010.jpg) copying to /tmp/gvfsobexftp-tmp-NM4FKX (retval 2) ** Message: ChangeCurrentFolderToRoot failed ** Message: transfer got cancelled ** Message: transfer of Image010.jpg to /tmp/gvfsobexftp-tmp-9X2MKX started ** Message: filename: /Memory card/Images/Image010.jpg (Image010.jpg) copying to /tmp/gvfsobexftp-tmp-9X2MKX (retval 2) ** Message: ChangeCurrentFolderToRoot failed ** Message: transfer got cancelled ** Message: transfer of Image010.jpg to /tmp/gvfsobexftp-tmp-XTK5JX started ** Message: filename: /Memory card/Images/Image010.jpg (Image010.jpg) copying to /tmp/gvfsobexftp-tmp-XTK5JX (retval 2) ** Message: ChangeCurrentFolderToRoot failed ** Message: transfer got cancelled ** Message: transfer of Image010.jpg to /tmp/gvfsobexftp-tmp-3LWGKX started ** Message: filename: /Memory card/Images/Image010.jpg (Image010.jpg) copying to /tmp/gvfsobexftp-tmp-3LWGKX (retval 2) ** Message: ChangeCurrentFolderToRoot failed ** Message: transfer got cancelled ** Message: transfer of Image010.jpg to /tmp/gvfsobexftp-tmp-GYMKKX started ** Message: filename: /Memory card/Images/Image010.jpg (Image010.jpg) copying to /tmp/gvfsobexftp-tmp-GYMKKX (retval 2) ** Message: ChangeCurrentFolderToRoot failed ** Message: transfer got cancelled ** Message: transfer of Image010.jpg to /tmp/gvfsobexftp-tmp-W77BKX started ** Message: filename: /Memory card/Images/Image010.jpg (Image010.jpg) copying to /tmp/gvfsobexftp-tmp-W77BKX (retval 2) ** Message: ChangeCurrentFolderToRoot failed ** Message: transfer got cancelled ** Message: ChangeCurrentFolderToRoot failed ** (zeitgeist-fts:2146): WARNING **: Unable to get info on application://nautilus-autostart.desktop ** Message: transfer of Image010.jpg to /tmp/gvfsobexftp-tmp-RFE9JX started ** Message: filename: /Memory card/Images/Image010.jpg (Image010.jpg) copying to /tmp/gvfsobexftp-tmp-RFE9JX (retval 2) ** Message: transfer of Image010.jpg to /tmp/gvfsobexftp-tmp-284GKX started ** Message: filename: /Memory card/Images/Image010.jpg (Image010.jpg) copying to /tmp/gvfsobexftp-tmp-284GKX (retval 2) ** Message: ChangeCurrentFolderToRoot failed ** Message: transfer got cancelled ** Message: transfer of Image010.jpg to /tmp/gvfsobexftp-tmp-UP0AKX started ** Message: filename: /Memory card/Images/Image010.jpg (Image010.jpg) copying to /tmp/gvfsobexftp-tmp-UP0AKX (retval 2) ** Message: ChangeCurrentFolderToRoot failed ** Message: transfer got cancelled ** (zeitgeist-fts:2146): WARNING **: Unable to get info on application://nautilus-autostart.desktop ** Message: transfer of Image010.jpg to /tmp/gvfsobexftp-tmp-F3C5JX started ** Message: filename: /Memory card/Images/Image010.jpg (Image010.jpg) copying to /tmp/gvfsobexftp-tmp-F3C5JX (retval 2) ** Message: transfer of Image010.jpg to /tmp/gvfsobexftp-tmp-LVIFKX started ** Message: filename: /Memory card/Images/Image010.jpg (Image010.jpg) copying to /tmp/gvfsobexftp-tmp-LVIFKX (retval 2) ** Message: ChangeCurrentFolderToRoot failed ** Message: transfer got cancelled ** (zeitgeist-fts:2146): WARNING **: Unable to get info on application://nautilus-autostart.desktop ** Message: transfer of Image010.jpg to /tmp/gvfsobexftp-tmp-OQULKX started ** Message: filename: /Memory card/Images/Image010.jpg (Image010.jpg) copying to /tmp/gvfsobexftp-tmp-OQULKX (retval 2) ** Message: ChangeCurrentFolderToRoot failed ** Message: ChangeCurrentFolderToRoot failed ** Message: transfer of Image010.jpg to /tmp/gvfsobexftp-tmp-VWUIKX started ** Message: filename: /Memory card/Images/Image010.jpg (Image010.jpg) copying to /tmp/gvfsobexftp-tmp-VWUIKX (retval 2) The "ChangeCurrentFolderToRoot failed" appears to be harmless, for example when opening in eog this message is printed but the image still loads. "transfer got cancelled" appears to be the message which is ultimately printed when a transfer actually fails. -- 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/1284308 Title: Bogus "another operation in progress" error. Can't copy files from a bluetooth device Status in “bluez” package in Ubuntu: Confirmed Status in “gvfs” package in Ubuntu: Confirmed Status in “obex-data-server” package in Ubuntu: Confirmed Bug description: I have upgraded to Ubuntu 13.10. And as usual, with the upgrade, a whole new bluetooth issue, which this times makes transferring files fro
[Kernel-packages] [Bug 1073089] Re: ubuntu kernel does not support gadgetfs
Still broken in 14.04 -- 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/1073089 Title: ubuntu kernel does not support gadgetfs Status in linux package in Ubuntu: Triaged Bug description: The Ubuntu kernel does not appear to support gadgetfs: $ sudo modprobe g_mass_storage file=/tmp/fake_usb_disk FATAL: Error inserting g_mass_storage (/lib/modules/3.5.0-17-generic/kernel/drivers/usb/gadget/g_mass_storage.ko): No such device $ ll /lib/modules/3.5.0-17-generic/kernel/drivers/usb/gadget/g_mass_storage.ko -rw-r--r-- 1 root root 56436 oct 9 21:06 /lib/modules/3.5.0-17-generic/kernel/drivers/usb/gadget/g_mass_storage.ko $ This seems to have been resolved in Igloo (see bug 923674) so is presumably a case of a cherry-pick? --- ApportVersion: 2.6.1-0ubuntu6 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: james 3464 F pulseaudio /dev/snd/controlC0: james 3464 F pulseaudio DistroRelease: Ubuntu 12.10 HibernationDevice: RESUME=UUID=67e3cd44-242b-4bbf-918b-28fff81e0312 InstallationDate: Installed on 2010-10-21 (740 days ago) InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007) MachineType: LENOVO 2516CTO MarkForUpload: True NonfreeKernelModules: nvidia Package: linux-image-generic-pae 3.5.0.17.19 PackageArchitecture: i386 ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic root=UUID=7ad192e9-7b26-49d1-8e1c-fefc7dc495cb ro quiet splash ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 RelatedPackageVersions: linux-restricted-modules-3.5.0-17-generic N/A linux-backports-modules-3.5.0-17-generic N/A linux-firmware1.95 Tags: quantal running-unity Uname: Linux 3.5.0-17-generic i686 UpgradeStatus: Upgraded to quantal on 2012-09-30 (29 days ago) UserGroups: adm admin cdrom dialout kvm libvirtd lpadmin plugdev sambashare sbuild vboxusers dmi.bios.date: 08/27/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 6IET72WW (1.32 ) dmi.board.name: 2516CTO 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:bvr6IET72WW(1.32):bd08/27/2010:svnLENOVO:pn2516CTO:pvrThinkPadT410:rvnLENOVO:rn2516CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2516CTO dmi.product.version: ThinkPad T410 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1073089/+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 1575250] Re: system takes exactly five minutes to wake from suspend
Sure, just give me access to a build server where I can build the kernels for bisection. ** 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/1575250 Title: system takes exactly five minutes to wake from suspend Status in linux package in Ubuntu: Confirmed Bug description: To reproduce: 1. Close laptop lid. 2. Wait a couple of minutes. 3. Open laptop lid. Result: the screen remains powered off and the system will not respond in any way. Pressing keys does nothing. Pressing the power button does nothing. There is no disk activity but the power light is lit. After exactly five minutes (to the second) the system resumes. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-21-generic 4.4.0-21.37 [modified: boot/vmlinuz-4.4.0-21-generic] ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: al 1892 F pulseaudio CurrentDesktop: Unity Date: Tue Apr 26 16:46:08 2016 HibernationDevice: RESUME=UUID=8623f57e-2fc2-4a9a-bd35-73f33e1aeb59 InstallationDate: Installed on 2016-04-21 (4 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: LENOVO 20040M18 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic root=UUID=0f83fbb5-4903-4610-9f32-1ab22c935bb0 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-21-generic N/A linux-backports-modules-4.4.0-21-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/11/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 24CN61WW dmi.board.name: Caucasus2 dmi.board.vendor: LENOVO dmi.board.version: Rev 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Lenovo dmi.chassis.version: Rev 1.0 dmi.modalias: dmi:bvnLENOVO:bvr24CN61WW:bd08/11/2010:svnLENOVO:pn20040M18:pvrLenovoIdeapadS10-3t:rvnLENOVO:rnCaucasus2:rvrRev1.0:cvnLenovo:ct10:cvrRev1.0: dmi.product.name: 20040M18 dmi.product.version: Lenovo Ideapad S10-3t dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1575250/+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 1575250] Re: system takes exactly five minutes to wake from suspend
Since it looks like I am expected to fix this myself, why don't you just mark it triaged and assign it to me? ** Changed in: linux (Ubuntu) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Alistair Buxton (a-j-buxton) -- 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/1575250 Title: system takes exactly five minutes to wake from suspend Status in linux package in Ubuntu: In Progress Bug description: To reproduce: 1. Close laptop lid. 2. Wait a couple of minutes. 3. Open laptop lid. Result: the screen remains powered off and the system will not respond in any way. Pressing keys does nothing. Pressing the power button does nothing. There is no disk activity but the power light is lit. After exactly five minutes (to the second) the system resumes. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-21-generic 4.4.0-21.37 [modified: boot/vmlinuz-4.4.0-21-generic] ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: al 1892 F pulseaudio CurrentDesktop: Unity Date: Tue Apr 26 16:46:08 2016 HibernationDevice: RESUME=UUID=8623f57e-2fc2-4a9a-bd35-73f33e1aeb59 InstallationDate: Installed on 2016-04-21 (4 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: LENOVO 20040M18 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic root=UUID=0f83fbb5-4903-4610-9f32-1ab22c935bb0 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-21-generic N/A linux-backports-modules-4.4.0-21-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/11/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 24CN61WW dmi.board.name: Caucasus2 dmi.board.vendor: LENOVO dmi.board.version: Rev 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Lenovo dmi.chassis.version: Rev 1.0 dmi.modalias: dmi:bvnLENOVO:bvr24CN61WW:bd08/11/2010:svnLENOVO:pn20040M18:pvrLenovoIdeapadS10-3t:rvnLENOVO:rnCaucasus2:rvrRev1.0:cvnLenovo:ct10:cvrRev1.0: dmi.product.name: 20040M18 dmi.product.version: Lenovo Ideapad S10-3t dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1575250/+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 1575250] Re: system takes exactly five minutes to wake from suspend
I'm working on the bisect now. I already ruled out the suspected commit - the first bisect step blew right past it. Each build takes about 2.5 hours on an i7-3770 and there's another 10 to go, so I should find the answer in about about four days or so. -- 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/1575250 Title: system takes exactly five minutes to wake from suspend Status in linux package in Ubuntu: In Progress Bug description: To reproduce: 1. Close laptop lid. 2. Wait a couple of minutes. 3. Open laptop lid. Result: the screen remains powered off and the system will not respond in any way. Pressing keys does nothing. Pressing the power button does nothing. There is no disk activity but the power light is lit. After exactly five minutes (to the second) the system resumes. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-21-generic 4.4.0-21.37 [modified: boot/vmlinuz-4.4.0-21-generic] ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: al 1892 F pulseaudio CurrentDesktop: Unity Date: Tue Apr 26 16:46:08 2016 HibernationDevice: RESUME=UUID=8623f57e-2fc2-4a9a-bd35-73f33e1aeb59 InstallationDate: Installed on 2016-04-21 (4 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: LENOVO 20040M18 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic root=UUID=0f83fbb5-4903-4610-9f32-1ab22c935bb0 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-21-generic N/A linux-backports-modules-4.4.0-21-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/11/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 24CN61WW dmi.board.name: Caucasus2 dmi.board.vendor: LENOVO dmi.board.version: Rev 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Lenovo dmi.chassis.version: Rev 1.0 dmi.modalias: dmi:bvnLENOVO:bvr24CN61WW:bd08/11/2010:svnLENOVO:pn20040M18:pvrLenovoIdeapadS10-3t:rvnLENOVO:rnCaucasus2:rvrRev1.0:cvnLenovo:ct10:cvrRev1.0: dmi.product.name: 20040M18 dmi.product.version: Lenovo Ideapad S10-3t dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1575250/+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 1575250] Re: system takes exactly five minutes to wake from suspend
I completed the bisection and googling the resulting commit ID revealed that this bug has already been reported upstream. ** Bug watch added: Linux Kernel Bug Tracker #107151 http://bugzilla.kernel.org/show_bug.cgi?id=107151 ** Also affects: linux via http://bugzilla.kernel.org/show_bug.cgi?id=107151 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/1575250 Title: system takes exactly five minutes to wake from suspend Status in Linux: Unknown Status in linux package in Ubuntu: In Progress Bug description: To reproduce: 1. Close laptop lid. 2. Wait a couple of minutes. 3. Open laptop lid. Result: the screen remains powered off and the system will not respond in any way. Pressing keys does nothing. Pressing the power button does nothing. There is no disk activity but the power light is lit. After exactly five minutes (to the second) the system resumes. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-21-generic 4.4.0-21.37 [modified: boot/vmlinuz-4.4.0-21-generic] ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: al 1892 F pulseaudio CurrentDesktop: Unity Date: Tue Apr 26 16:46:08 2016 HibernationDevice: RESUME=UUID=8623f57e-2fc2-4a9a-bd35-73f33e1aeb59 InstallationDate: Installed on 2016-04-21 (4 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: LENOVO 20040M18 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic root=UUID=0f83fbb5-4903-4610-9f32-1ab22c935bb0 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-21-generic N/A linux-backports-modules-4.4.0-21-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/11/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 24CN61WW dmi.board.name: Caucasus2 dmi.board.vendor: LENOVO dmi.board.version: Rev 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Lenovo dmi.chassis.version: Rev 1.0 dmi.modalias: dmi:bvnLENOVO:bvr24CN61WW:bd08/11/2010:svnLENOVO:pn20040M18:pvrLenovoIdeapadS10-3t:rvnLENOVO:rnCaucasus2:rvrRev1.0:cvnLenovo:ct10:cvrRev1.0: dmi.product.name: 20040M18 dmi.product.version: Lenovo Ideapad S10-3t dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1575250/+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 1575250] Re: close laptop lid = complete system freeze
This is a regression since 14.04. Out of date bios is irrelevant. Please provide a citation for your claims of "buggy" and "insecure." ** 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/1575250 Title: close laptop lid = complete system freeze Status in linux package in Ubuntu: Confirmed Bug description: To reproduce: 1. Close laptop lid. 2. Wait a couple of minutes. 3. Open laptop lid. Result: the screen remains powered off and the system will not respond in any way. Pressing keys does nothing. Pressing the power button does nothing. There is no disk activity but the power light is lit. The only thing you can do is press the power button for four seconds or remove the battery. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-21-generic 4.4.0-21.37 [modified: boot/vmlinuz-4.4.0-21-generic] ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: al 1892 F pulseaudio CurrentDesktop: Unity Date: Tue Apr 26 16:46:08 2016 HibernationDevice: RESUME=UUID=8623f57e-2fc2-4a9a-bd35-73f33e1aeb59 InstallationDate: Installed on 2016-04-21 (4 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: LENOVO 20040M18 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic root=UUID=0f83fbb5-4903-4610-9f32-1ab22c935bb0 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-21-generic N/A linux-backports-modules-4.4.0-21-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/11/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 24CN61WW dmi.board.name: Caucasus2 dmi.board.vendor: LENOVO dmi.board.version: Rev 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Lenovo dmi.chassis.version: Rev 1.0 dmi.modalias: dmi:bvnLENOVO:bvr24CN61WW:bd08/11/2010:svnLENOVO:pn20040M18:pvrLenovoIdeapadS10-3t:rvnLENOVO:rnCaucasus2:rvrRev1.0:cvnLenovo:ct10:cvrRev1.0: dmi.product.name: 20040M18 dmi.product.version: Lenovo Ideapad S10-3t dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1575250/+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 1575250] Re: close laptop lid = complete system freeze
None of the links you provided support your claim that my BIOS is insecure or buggy. Have you tried actually reading the stuff you copy and paste every day? I would further point out that the last update for this system was released in 2010, at least four years before this bug was introduced. On top of that, no method for reflashing the BIOS of this system without installing Windows 7 or Windows XP exists, for which my system does not have a license. ** 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/1575250 Title: close laptop lid = complete system freeze Status in linux package in Ubuntu: Confirmed Bug description: To reproduce: 1. Close laptop lid. 2. Wait a couple of minutes. 3. Open laptop lid. Result: the screen remains powered off and the system will not respond in any way. Pressing keys does nothing. Pressing the power button does nothing. There is no disk activity but the power light is lit. The only thing you can do is press the power button for four seconds or remove the battery. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-21-generic 4.4.0-21.37 [modified: boot/vmlinuz-4.4.0-21-generic] ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: al 1892 F pulseaudio CurrentDesktop: Unity Date: Tue Apr 26 16:46:08 2016 HibernationDevice: RESUME=UUID=8623f57e-2fc2-4a9a-bd35-73f33e1aeb59 InstallationDate: Installed on 2016-04-21 (4 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: LENOVO 20040M18 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic root=UUID=0f83fbb5-4903-4610-9f32-1ab22c935bb0 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-21-generic N/A linux-backports-modules-4.4.0-21-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/11/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 24CN61WW dmi.board.name: Caucasus2 dmi.board.vendor: LENOVO dmi.board.version: Rev 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Lenovo dmi.chassis.version: Rev 1.0 dmi.modalias: dmi:bvnLENOVO:bvr24CN61WW:bd08/11/2010:svnLENOVO:pn20040M18:pvrLenovoIdeapadS10-3t:rvnLENOVO:rnCaucasus2:rvrRev1.0:cvnLenovo:ct10:cvrRev1.0: dmi.product.name: 20040M18 dmi.product.version: Lenovo Ideapad S10-3t dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1575250/+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 1575250] Re: close laptop lid = complete system freeze
If one actually reads the release notes (as I did yesterday) one will notice that there are no references to security fixes and the only two changes listed are described as a workaround and a fix for Windows XP respectively. Regardless, I have now obtained a copy of Windows and updated to the newest BIOS. As expected, it made absolutely no difference at all. Here is the output of the commands as requested: 24CN62WW # dmidecode 3.0 Getting SMBIOS data from sysfs. SMBIOS 2.5 present. 28 structures occupying 1356 bytes. Table at 0x000DF010. Handle 0x, DMI type 0, 24 bytes BIOS Information Vendor: LENOVO Version: 24CN62WW Release Date: 08/30/2010 Address: 0xE6950 Runtime Size: 104112 bytes ROM Size: 1024 kB Characteristics: ISA is supported PCI is supported PC Card (PCMCIA) is supported PNP is supported BIOS is upgradeable BIOS shadowing is allowed ESCD support is available Boot from CD is supported Selectable boot is supported Print screen service is supported (int 5h) 8042 keyboard services are supported (int 9h) Serial services are supported (int 14h) Printer services are supported (int 17h) ACPI is supported USB legacy is supported Smart battery is supported BIOS boot specification is supported Targeted content distribution is supported BIOS Revision: 0.62 Handle 0x0001, DMI type 1, 27 bytes System Information Manufacturer: LENOVO Product Name: 20040M18 Version: Lenovo Ideapad S10-3t Serial Number: 11S11012681ZZ0LR09H1AL UUID: 186CED41-A92F-6842-50AF-203040506099 Wake-up Type: Power Switch SKU Number: Not Specified Family: Not Specified Handle 0x0002, DMI type 2, 8 bytes Base Board Information Manufacturer: LENOVO Product Name: Caucasus2 Version: Rev 1.0 Serial Number: QB01774374 Handle 0x0003, DMI type 3, 17 bytes Chassis Information Manufacturer: Lenovo Type: Notebook Lock: Not Present Version: Rev 1.0 Serial Number: Asset Tag: No Asset Tag Boot-up State: Safe Power Supply State: Safe Thermal State: Safe Security Status: None OEM Information: 0x5525 Handle 0x0004, DMI type 4, 40 bytes Processor Information Socket Designation: U2E1 Type: Central Processor Family: Other Manufacturer: Intel ID: CA 06 01 00 FF FB E9 BF Version: CPU Version Voltage: 3.3 V External Clock: 166 MHz Max Speed: 1666 MHz Current Speed: 1666 MHz Status: Populated, Enabled Upgrade: ZIF Socket L1 Cache Handle: 0x0005 L2 Cache Handle: 0x0006 L3 Cache Handle: Not Provided Serial Number: Not Specified Asset Tag: Not Specified Part Number: Not Specified Core Count: 1 Core Enabled: 1 Thread Count: 2 Characteristics: 64-bit capable Handle 0x0005, DMI type 7, 19 bytes Cache Information Socket Designation: L1 Cache Configuration: Enabled, Socketed, Level 1 Operational Mode: Write Back Location: Internal Installed Size: 24 kB Maximum Size: 24 kB Supported SRAM Types: Burst Pipeline Burst Asynchronous Installed SRAM Type: Asynchronous Speed: Unknown Error Correction Type: Single-bit ECC System Type: Data Associativity: Other Handle 0x0006, DMI type 7, 19 bytes Cache Information Socket Designation: L2 Cache Configuration: Enabled, Socketed, Level 2 Operational Mode: Write Back Location: Internal Installed Size: 512 kB Maximum Size: 512 kB Supported SRAM Types: Burst Pipeline Burst Asynchronous Installed SRAM Type: Burst Speed: Unknown Error Correction Type: Single-bit ECC System Type: Unified Associativity: 8-way Set-associative Handle 0x0007, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: J2A1 Internal Connector Type: 9 Pin Dual Inline (pin 10 cut) External Reference Designator: COM 1 External Connector Type: DB-9 male Port Type: Serial Port 16550A Compatible Handle 0x0008, DMI typ
[Kernel-packages] [Bug 1575250] Re: close laptop lid = complete system freeze
4.7-rc2 does not work. The regression is somewhere between 3.9 and 4.0. -- 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/1575250 Title: close laptop lid = complete system freeze Status in linux package in Ubuntu: Incomplete Bug description: To reproduce: 1. Close laptop lid. 2. Wait a couple of minutes. 3. Open laptop lid. Result: the screen remains powered off and the system will not respond in any way. Pressing keys does nothing. Pressing the power button does nothing. There is no disk activity but the power light is lit. The only thing you can do is press the power button for four seconds or remove the battery. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-21-generic 4.4.0-21.37 [modified: boot/vmlinuz-4.4.0-21-generic] ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: al 1892 F pulseaudio CurrentDesktop: Unity Date: Tue Apr 26 16:46:08 2016 HibernationDevice: RESUME=UUID=8623f57e-2fc2-4a9a-bd35-73f33e1aeb59 InstallationDate: Installed on 2016-04-21 (4 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: LENOVO 20040M18 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic root=UUID=0f83fbb5-4903-4610-9f32-1ab22c935bb0 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-21-generic N/A linux-backports-modules-4.4.0-21-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/11/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 24CN61WW dmi.board.name: Caucasus2 dmi.board.vendor: LENOVO dmi.board.version: Rev 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Lenovo dmi.chassis.version: Rev 1.0 dmi.modalias: dmi:bvnLENOVO:bvr24CN61WW:bd08/11/2010:svnLENOVO:pn20040M18:pvrLenovoIdeapadS10-3t:rvnLENOVO:rnCaucasus2:rvrRev1.0:cvnLenovo:ct10:cvrRev1.0: dmi.product.name: 20040M18 dmi.product.version: Lenovo Ideapad S10-3t dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1575250/+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 1575250] Re: close laptop lid = complete system freeze
The last working kernel: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.17-utopic/ The first broken kernel: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.18-rc1-utopic/ Probably related: http://lkml.iu.edu/hypermail/linux/kernel/1410.1/02561.html -- 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/1575250 Title: close laptop lid = complete system freeze Status in linux package in Ubuntu: Incomplete Bug description: To reproduce: 1. Close laptop lid. 2. Wait a couple of minutes. 3. Open laptop lid. Result: the screen remains powered off and the system will not respond in any way. Pressing keys does nothing. Pressing the power button does nothing. There is no disk activity but the power light is lit. The only thing you can do is press the power button for four seconds or remove the battery. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-21-generic 4.4.0-21.37 [modified: boot/vmlinuz-4.4.0-21-generic] ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: al 1892 F pulseaudio CurrentDesktop: Unity Date: Tue Apr 26 16:46:08 2016 HibernationDevice: RESUME=UUID=8623f57e-2fc2-4a9a-bd35-73f33e1aeb59 InstallationDate: Installed on 2016-04-21 (4 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: LENOVO 20040M18 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic root=UUID=0f83fbb5-4903-4610-9f32-1ab22c935bb0 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-21-generic N/A linux-backports-modules-4.4.0-21-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/11/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 24CN61WW dmi.board.name: Caucasus2 dmi.board.vendor: LENOVO dmi.board.version: Rev 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Lenovo dmi.chassis.version: Rev 1.0 dmi.modalias: dmi:bvnLENOVO:bvr24CN61WW:bd08/11/2010:svnLENOVO:pn20040M18:pvrLenovoIdeapadS10-3t:rvnLENOVO:rnCaucasus2:rvrRev1.0:cvnLenovo:ct10:cvrRev1.0: dmi.product.name: 20040M18 dmi.product.version: Lenovo Ideapad S10-3t dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1575250/+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 1575250] Re: close laptop lid = complete system freeze
** 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/1575250 Title: close laptop lid = complete system freeze Status in linux package in Ubuntu: Confirmed Bug description: To reproduce: 1. Close laptop lid. 2. Wait a couple of minutes. 3. Open laptop lid. Result: the screen remains powered off and the system will not respond in any way. Pressing keys does nothing. Pressing the power button does nothing. There is no disk activity but the power light is lit. The only thing you can do is press the power button for four seconds or remove the battery. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-21-generic 4.4.0-21.37 [modified: boot/vmlinuz-4.4.0-21-generic] ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: al 1892 F pulseaudio CurrentDesktop: Unity Date: Tue Apr 26 16:46:08 2016 HibernationDevice: RESUME=UUID=8623f57e-2fc2-4a9a-bd35-73f33e1aeb59 InstallationDate: Installed on 2016-04-21 (4 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: LENOVO 20040M18 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic root=UUID=0f83fbb5-4903-4610-9f32-1ab22c935bb0 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-21-generic N/A linux-backports-modules-4.4.0-21-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/11/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 24CN61WW dmi.board.name: Caucasus2 dmi.board.vendor: LENOVO dmi.board.version: Rev 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Lenovo dmi.chassis.version: Rev 1.0 dmi.modalias: dmi:bvnLENOVO:bvr24CN61WW:bd08/11/2010:svnLENOVO:pn20040M18:pvrLenovoIdeapadS10-3t:rvnLENOVO:rnCaucasus2:rvrRev1.0:cvnLenovo:ct10:cvrRev1.0: dmi.product.name: 20040M18 dmi.product.version: Lenovo Ideapad S10-3t dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1575250/+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 1575250] Re: close laptop lid = complete system freeze
While messing around with this I noticed that the system does actually unsuspend on recent kernels after exactly five minutes. After unsuspending the system clock is five minutes slow, to the second. There are no useful messages in dmesg, syslog or journalctl. ** Summary changed: - close laptop lid = complete system freeze + system takes exactly five minutes to wake from suspend ** Description changed: To reproduce: 1. Close laptop lid. 2. Wait a couple of minutes. 3. Open laptop lid. Result: the screen remains powered off and the system will not respond in any way. Pressing keys does nothing. Pressing the power button does - nothing. There is no disk activity but the power light is lit. The only - thing you can do is press the power button for four seconds or remove - the battery. + nothing. There is no disk activity but the power light is lit. After + exactly five minutes (to the second) the system resumes. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-21-generic 4.4.0-21.37 [modified: boot/vmlinuz-4.4.0-21-generic] ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: al 1892 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: al 1892 F pulseaudio CurrentDesktop: Unity Date: Tue Apr 26 16:46:08 2016 HibernationDevice: RESUME=UUID=8623f57e-2fc2-4a9a-bd35-73f33e1aeb59 InstallationDate: Installed on 2016-04-21 (4 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: LENOVO 20040M18 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic root=UUID=0f83fbb5-4903-4610-9f32-1ab22c935bb0 ro quiet splash vt.handoff=7 RelatedPackageVersions: - linux-restricted-modules-4.4.0-21-generic N/A - linux-backports-modules-4.4.0-21-generic N/A - linux-firmware1.157 + linux-restricted-modules-4.4.0-21-generic N/A + linux-backports-modules-4.4.0-21-generic N/A + linux-firmware1.157 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/11/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 24CN61WW dmi.board.name: Caucasus2 dmi.board.vendor: LENOVO dmi.board.version: Rev 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Lenovo dmi.chassis.version: Rev 1.0 dmi.modalias: dmi:bvnLENOVO:bvr24CN61WW:bd08/11/2010:svnLENOVO:pn20040M18:pvrLenovoIdeapadS10-3t:rvnLENOVO:rnCaucasus2:rvrRev1.0:cvnLenovo:ct10:cvrRev1.0: dmi.product.name: 20040M18 dmi.product.version: Lenovo Ideapad S10-3t dmi.sys.vendor: LENOVO -- 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/1575250 Title: system takes exactly five minutes to wake from suspend Status in linux package in Ubuntu: Confirmed Bug description: To reproduce: 1. Close laptop lid. 2. Wait a couple of minutes. 3. Open laptop lid. Result: the screen remains powered off and the system will not respond in any way. Pressing keys does nothing. Pressing the power button does nothing. There is no disk activity but the power light is lit. After exactly five minutes (to the second) the system resumes. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-21-generic 4.4.0-21.37 [modified: boot/vmlinuz-4.4.0-21-generic] ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: al 1892 F pulseaudio CurrentDesktop: Unity Date: Tue Apr 26 16:46:08 2016 HibernationDevice: RESUME=UUID=8623f57e-2fc2-4a9a-bd35-73f33e1aeb59 InstallationDate: Installed on 2016-04-21 (4 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: LENOVO 20040M18 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic root=UUID=0f83fbb5-4903-4610-9f32-1ab22c935bb0 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-21-generic N/A linux-backports-modules-4.4.0-21-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/11/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 24CN61WW dmi.board.name: Caucasus2 dmi.board.vendor: LENOVO dmi.board.version: Rev 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Lenovo dmi.chassis.version: Rev 1.0 dmi.modalias: dmi:bvnLENOVO:bvr24CN61WW:bd08/1
[Kernel-packages] [Bug 1841040] Re: r8169 ethernet sometimes doesn't work after cold boot/boot
I can no longer reproduce this in 22.04. -- 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/1841040 Title: r8169 ethernet sometimes doesn't work after cold boot/boot Status in linux package in Ubuntu: Confirmed Bug description: Whenever the computer is rebooted there is a roughly 50% chance that the r8169 ethernet cannot negotiate a link. There is no relevant information in dmesg except for the "link down" message. The work around is to just keep rebooting the computer until it eventually works; sometimes this may take up to 7 reboots. The first set of attached log files were generated while the ethernet was working. The second set are generated on the 5.0 HWE kernel when the ethernet was NOT working. Note that this is a regression. Ubuntu 16.04 ran on this computer for three years without the ethernet doing this even once. Unloading and loading the r8169 module will eventually make it work. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-58-generic 4.15.0-58.64 ProcVersionSignature: Ubuntu 4.15.0-58.64-generic 4.15.18 Uname: Linux 4.15.0-58-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', '/dev/snd/pcmC2D0c', '/dev/snd/controlC2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/by-path', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu Aug 22 10:05:17 2019 HibernationDevice: RESUME=UUID=4ab51820-6203-45a8-a04d-07946b0fbe56 InstallationDate: Installed on 2013-12-22 (2068 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: ASUS All Series ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-58-generic root=UUID=e1e7d1a7-19e8-4203-ad6a-86a144db61bc ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-58-generic N/A linux-backports-modules-4.15.0-58-generic N/A linux-firmware 1.173.9 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2019-01-30 (203 days ago) dmi.bios.date: 06/18/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2201 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H87M-E dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2201:bd06/18/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH87M-E:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: al14985 F pulseaudio /dev/snd/controlC0: al14985 F pulseaudio /dev/snd/controlC1: al14985 F pulseaudio CurrentDesktop: Unity:Unity7:ubuntu DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=4ab51820-6203-45a8-a04d-07946b0fbe56 InstallationDate: Installed on 2013-12-22 (2068 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: ASUS All Series Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-25-generic root=UUID=e1e7d1a7-19e8-4203-ad6a-86a144db61bc ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-25.26~18.04.1-generic 5.0.18 RelatedPackageVersions: linux-restricted-modules-5.0.0-25-generic N/A linux-backports-modules-5.0.0-25-generic N/A linux-firmware1.173.9 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 5.0.0-25-generic x86_64 UpgradeStatus: Upgraded to bionic on 2019-01-30 (203 days ago) UserGroups: adm lpadmin sambashare sudo _MarkForUpload: True dmi.bios.date: 06/18/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2201 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H87M-E dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type:
[Kernel-packages] [Bug 2024305] [NEW] All GPU functionality stops working whenever an updated Nvidia driver is installed and until the system is rebooted
Public bug reported: To reproduce: 1. Install Ubuntu 2. Switch to Nvidia driver 3. Wait The default for Ubuntu is to install updates automatically in the background. Eventually an updated Nvidia driver will be installed, and then all graphics acceleration stops working for any new programs which are launched. Note that it continues working for anything that was already running. This results in the following things happening: 1. Any program that requires OpenGL will crash on startup. For example glxgears: ``` X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 152 (GLX) Minor opcode of failed request: 3 (X_GLXCreateContext) Value in failed request: 0x0 Serial number of failed request: 36 Current serial number in output stream: 37 ``` 2. Any program that uses CUDA will fail in a similar way. 3. Programs that can fall back to software rendering will do so. For example, Firefox will start using software rendering, causing it to max out several CPU cores on heavy websites like Discord. Expected Result: One of the following: 1. Don't automatically install driver updates in the background. 2. Install them in a way that doesn't prevent them from working until a reboot. 3. Display a message informing the user that the drivers were updated and requesting a reboot. User Impact It can be difficult for the user to notice this has happened for the following reasons: 1. There is no notification that the driver has been updated. 2. Most software will fall back to software rendering and just run slowly for no obvious reason. 3. Any software that was already running before the update will continue working properly. So then the user gets left with a system that runs really slowly until they notice there is a problem because a program won't run, or they happened to notice that Firefox is using 500% CPU. This may be some time after the driver was updated. It is difficult for the user to work out that they need to reboot. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: nvidia-driver-525 525.116.04-0ubuntu0.23.04.1 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Sun Jun 18 02:44:05 2023 InstallationDate: Installed on 2023-06-01 (16 days ago) InstallationMedia: Xubuntu 23.04 "Lunar Lobster" - Release amd64 (20230414.2) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: nvidia-graphics-drivers-525 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-525 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-525 in Ubuntu. https://bugs.launchpad.net/bugs/2024305 Title: All GPU functionality stops working whenever an updated Nvidia driver is installed and until the system is rebooted Status in nvidia-graphics-drivers-525 package in Ubuntu: New Bug description: To reproduce: 1. Install Ubuntu 2. Switch to Nvidia driver 3. Wait The default for Ubuntu is to install updates automatically in the background. Eventually an updated Nvidia driver will be installed, and then all graphics acceleration stops working for any new programs which are launched. Note that it continues working for anything that was already running. This results in the following things happening: 1. Any program that requires OpenGL will crash on startup. For example glxgears: ``` X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 152 (GLX) Minor opcode of failed request: 3 (X_GLXCreateContext) Value in failed request: 0x0 Serial number of failed request: 36 Current serial number in output stream: 37 ``` 2. Any program that uses CUDA will fail in a similar way. 3. Programs that can fall back to software rendering will do so. For example, Firefox will start using software rendering, causing it to max out several CPU cores on heavy websites like Discord. Expected Result: One of the following: 1. Don't automatically install driver updates in the background. 2. Install them in a way that doesn't prevent them from working until a reboot. 3. Display a message informing the user that the drivers were updated and requesting a reboot. User Impact It can be difficult for the user to notice this has happened for the following reasons: 1. There is no notification that the driver has been updated. 2. Most software will fall back to software rendering and just run slowly for no obvious reason. 3. Any software that was already running before the update will continue working properly. So th
