[Touch-packages] [Bug 2037906] Re: [Intel AX201] Bluetooth LE not working after upgrade from 22.04 to 23.10
- played with linux-image-6.5.0-1003-intel-opt -bluetooth stopped working at all - installed linux 6.5.0-13-generic - installed linux-modules-extra-6.5.0-13-generic - after reboot everything was fixed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2037906 Title: [Intel AX201] Bluetooth LE not working after upgrade from 22.04 to 23.10 Status in Linux Firmware: New Status in bluez package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: syslog: 2023-09-20T09:32:54.138852+02:00 zaionc kernel: [ 13.539860] Bluetooth: hci0: Waiting for firmware download to complete 2023-09-20T09:32:54.138857+02:00 zaionc kernel: [ 13.540223] Bluetooth: hci0: Firmware loaded in 1706498 usecs 2023-09-20T09:32:54.138858+02:00 zaionc kernel: [ 13.540278] Bluetooth: hci0: Waiting for device to boot 2023-09-20T09:32:54.154894+02:00 zaionc kernel: [ 13.555430] Bluetooth: hci0: Malformed MSFT vendor event: 0x02 2023-09-20T09:32:54.154908+02:00 zaionc kernel: [ 13.555482] Bluetooth: hci0: Device booted in 14872 usecs 2023-09-20T09:32:54.154910+02:00 zaionc kernel: [ 13.555913] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-19-0-4.ddc 2023-09-20T09:32:54.158856+02:00 zaionc kernel: [ 13.558300] Bluetooth: hci0: Applying Intel DDC parameters completed 2023-09-20T09:32:54.158859+02:00 zaionc kernel: [ 13.559326] Bluetooth: hci0: Firmware revision 0.4 build 249 week 27 2023 lshw: *-usb:5 description: Bluetooth wireless interface product: AX201 Bluetooth vendor: Intel Corp. physical id: a bus info: usb@3:a version: 0.02 capabilities: bluetooth usb-2.01 configuration: driver=btusb maxpower=100mA speed=12Mbit/s root@zaionc:~# hcitool lescan Set scan parameters failed: Input/output error At first bluetooth stopped working at all due to Ubuntu bug = missing firmware. It was fixed recently and now the bluetooth module seems fine, but the whole BTLE part is not available. Particularly I cannot detect/pair Logitech M720 mouse. Platform: ThinkPad T14 Gen 2i --- ProblemType: Bug ApportVersion: 2.27.0-0ubuntu4 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.10 InstallationDate: Installed on 2022-05-28 (494 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) InterestingModules: rfcomm bnep btusb bluetooth MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']} Package: linux PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-5-generic root=UUID=d0002130-adf6-4f18-93b1-fda536d8b499 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 RebootRequiredPkgs: Error: path contained symlinks. Tags: mantic Uname: Linux 6.5.0-5-generic x86_64 UpgradeStatus: Upgraded to mantic on 2023-09-03 (30 days ago) UserGroups: adm cdrom dialout dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/10/2023 dmi.bios.release: 1.56 dmi.bios.vendor: LENOVO dmi.bios.version: N34ET56W (1.56 ) dmi.board.asset.tag: Not Available dmi.board.name: 20W000AMPB dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.42 dmi.modalias: dmi:bvnLENOVO:bvrN34ET56W(1.56):bd05/10/2023:br1.56:efr1.42:svnLENOVO:pn20W000AMPB:pvrThinkPadT14Gen2i:rvnLENOVO:rn20W000AMPB:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20W0_BU_Think_FM_ThinkPadT14Gen2i: dmi.product.family: ThinkPad T14 Gen 2i dmi.product.name: 20W000AMPB dmi.product.sku: LENOVO_MT_20W0_BU_Think_FM_ThinkPad T14 Gen 2i dmi.product.version: ThinkPad T14 Gen 2i dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: A0:E7:0B:23:70:E8 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:22183 acl:0 sco:0 events:3531 errors:0 TX bytes:821193 acl:0 sco:0 commands:3510 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/linux-firmware/+bug/2037906/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2037906] Re: [Intel AX201] Bluetooth LE not working after upgrade from 22.04 to 23.10
ok- I just saw I needed to mark the bug as Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2037906 Title: [Intel AX201] Bluetooth LE not working after upgrade from 22.04 to 23.10 Status in Linux Firmware: New Status in bluez package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: syslog: 2023-09-20T09:32:54.138852+02:00 zaionc kernel: [ 13.539860] Bluetooth: hci0: Waiting for firmware download to complete 2023-09-20T09:32:54.138857+02:00 zaionc kernel: [ 13.540223] Bluetooth: hci0: Firmware loaded in 1706498 usecs 2023-09-20T09:32:54.138858+02:00 zaionc kernel: [ 13.540278] Bluetooth: hci0: Waiting for device to boot 2023-09-20T09:32:54.154894+02:00 zaionc kernel: [ 13.555430] Bluetooth: hci0: Malformed MSFT vendor event: 0x02 2023-09-20T09:32:54.154908+02:00 zaionc kernel: [ 13.555482] Bluetooth: hci0: Device booted in 14872 usecs 2023-09-20T09:32:54.154910+02:00 zaionc kernel: [ 13.555913] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-19-0-4.ddc 2023-09-20T09:32:54.158856+02:00 zaionc kernel: [ 13.558300] Bluetooth: hci0: Applying Intel DDC parameters completed 2023-09-20T09:32:54.158859+02:00 zaionc kernel: [ 13.559326] Bluetooth: hci0: Firmware revision 0.4 build 249 week 27 2023 lshw: *-usb:5 description: Bluetooth wireless interface product: AX201 Bluetooth vendor: Intel Corp. physical id: a bus info: usb@3:a version: 0.02 capabilities: bluetooth usb-2.01 configuration: driver=btusb maxpower=100mA speed=12Mbit/s root@zaionc:~# hcitool lescan Set scan parameters failed: Input/output error At first bluetooth stopped working at all due to Ubuntu bug = missing firmware. It was fixed recently and now the bluetooth module seems fine, but the whole BTLE part is not available. Particularly I cannot detect/pair Logitech M720 mouse. Platform: ThinkPad T14 Gen 2i --- ProblemType: Bug ApportVersion: 2.27.0-0ubuntu4 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.10 InstallationDate: Installed on 2022-05-28 (494 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) InterestingModules: rfcomm bnep btusb bluetooth MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']} Package: linux PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-5-generic root=UUID=d0002130-adf6-4f18-93b1-fda536d8b499 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 RebootRequiredPkgs: Error: path contained symlinks. Tags: mantic Uname: Linux 6.5.0-5-generic x86_64 UpgradeStatus: Upgraded to mantic on 2023-09-03 (30 days ago) UserGroups: adm cdrom dialout dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/10/2023 dmi.bios.release: 1.56 dmi.bios.vendor: LENOVO dmi.bios.version: N34ET56W (1.56 ) dmi.board.asset.tag: Not Available dmi.board.name: 20W000AMPB dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.42 dmi.modalias: dmi:bvnLENOVO:bvrN34ET56W(1.56):bd05/10/2023:br1.56:efr1.42:svnLENOVO:pn20W000AMPB:pvrThinkPadT14Gen2i:rvnLENOVO:rn20W000AMPB:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20W0_BU_Think_FM_ThinkPadT14Gen2i: dmi.product.family: ThinkPad T14 Gen 2i dmi.product.name: 20W000AMPB dmi.product.sku: LENOVO_MT_20W0_BU_Think_FM_ThinkPad T14 Gen 2i dmi.product.version: ThinkPad T14 Gen 2i dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: A0:E7:0B:23:70:E8 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:22183 acl:0 sco:0 events:3531 errors:0 TX bytes:821193 acl:0 sco:0 commands:3510 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/linux-firmware/+bug/2037906/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2037906] Re: [Intel AX201] Bluetooth LE not working after upgrade from 22.04 to 23.10
Is there anything else I can provide? ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2037906 Title: [Intel AX201] Bluetooth LE not working after upgrade from 22.04 to 23.10 Status in Linux Firmware: New Status in bluez package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: syslog: 2023-09-20T09:32:54.138852+02:00 zaionc kernel: [ 13.539860] Bluetooth: hci0: Waiting for firmware download to complete 2023-09-20T09:32:54.138857+02:00 zaionc kernel: [ 13.540223] Bluetooth: hci0: Firmware loaded in 1706498 usecs 2023-09-20T09:32:54.138858+02:00 zaionc kernel: [ 13.540278] Bluetooth: hci0: Waiting for device to boot 2023-09-20T09:32:54.154894+02:00 zaionc kernel: [ 13.555430] Bluetooth: hci0: Malformed MSFT vendor event: 0x02 2023-09-20T09:32:54.154908+02:00 zaionc kernel: [ 13.555482] Bluetooth: hci0: Device booted in 14872 usecs 2023-09-20T09:32:54.154910+02:00 zaionc kernel: [ 13.555913] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-19-0-4.ddc 2023-09-20T09:32:54.158856+02:00 zaionc kernel: [ 13.558300] Bluetooth: hci0: Applying Intel DDC parameters completed 2023-09-20T09:32:54.158859+02:00 zaionc kernel: [ 13.559326] Bluetooth: hci0: Firmware revision 0.4 build 249 week 27 2023 lshw: *-usb:5 description: Bluetooth wireless interface product: AX201 Bluetooth vendor: Intel Corp. physical id: a bus info: usb@3:a version: 0.02 capabilities: bluetooth usb-2.01 configuration: driver=btusb maxpower=100mA speed=12Mbit/s root@zaionc:~# hcitool lescan Set scan parameters failed: Input/output error At first bluetooth stopped working at all due to Ubuntu bug = missing firmware. It was fixed recently and now the bluetooth module seems fine, but the whole BTLE part is not available. Particularly I cannot detect/pair Logitech M720 mouse. Platform: ThinkPad T14 Gen 2i --- ProblemType: Bug ApportVersion: 2.27.0-0ubuntu4 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.10 InstallationDate: Installed on 2022-05-28 (494 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) InterestingModules: rfcomm bnep btusb bluetooth MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']} Package: linux PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-5-generic root=UUID=d0002130-adf6-4f18-93b1-fda536d8b499 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 RebootRequiredPkgs: Error: path contained symlinks. Tags: mantic Uname: Linux 6.5.0-5-generic x86_64 UpgradeStatus: Upgraded to mantic on 2023-09-03 (30 days ago) UserGroups: adm cdrom dialout dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/10/2023 dmi.bios.release: 1.56 dmi.bios.vendor: LENOVO dmi.bios.version: N34ET56W (1.56 ) dmi.board.asset.tag: Not Available dmi.board.name: 20W000AMPB dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.42 dmi.modalias: dmi:bvnLENOVO:bvrN34ET56W(1.56):bd05/10/2023:br1.56:efr1.42:svnLENOVO:pn20W000AMPB:pvrThinkPadT14Gen2i:rvnLENOVO:rn20W000AMPB:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20W0_BU_Think_FM_ThinkPadT14Gen2i: dmi.product.family: ThinkPad T14 Gen 2i dmi.product.name: 20W000AMPB dmi.product.sku: LENOVO_MT_20W0_BU_Think_FM_ThinkPad T14 Gen 2i dmi.product.version: ThinkPad T14 Gen 2i dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: A0:E7:0B:23:70:E8 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:22183 acl:0 sco:0 events:3531 errors:0 TX bytes:821193 acl:0 sco:0 commands:3510 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/linux-firmware/+bug/2037906/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2037906] Re: [Intel AX201] Bluetooth LE not working after upgrade from 22.04 to 23.10
** Also affects: linux-firmware Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2037906 Title: [Intel AX201] Bluetooth LE not working after upgrade from 22.04 to 23.10 Status in Linux Firmware: New Status in bluez package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: syslog: 2023-09-20T09:32:54.138852+02:00 zaionc kernel: [ 13.539860] Bluetooth: hci0: Waiting for firmware download to complete 2023-09-20T09:32:54.138857+02:00 zaionc kernel: [ 13.540223] Bluetooth: hci0: Firmware loaded in 1706498 usecs 2023-09-20T09:32:54.138858+02:00 zaionc kernel: [ 13.540278] Bluetooth: hci0: Waiting for device to boot 2023-09-20T09:32:54.154894+02:00 zaionc kernel: [ 13.555430] Bluetooth: hci0: Malformed MSFT vendor event: 0x02 2023-09-20T09:32:54.154908+02:00 zaionc kernel: [ 13.555482] Bluetooth: hci0: Device booted in 14872 usecs 2023-09-20T09:32:54.154910+02:00 zaionc kernel: [ 13.555913] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-19-0-4.ddc 2023-09-20T09:32:54.158856+02:00 zaionc kernel: [ 13.558300] Bluetooth: hci0: Applying Intel DDC parameters completed 2023-09-20T09:32:54.158859+02:00 zaionc kernel: [ 13.559326] Bluetooth: hci0: Firmware revision 0.4 build 249 week 27 2023 lshw: *-usb:5 description: Bluetooth wireless interface product: AX201 Bluetooth vendor: Intel Corp. physical id: a bus info: usb@3:a version: 0.02 capabilities: bluetooth usb-2.01 configuration: driver=btusb maxpower=100mA speed=12Mbit/s root@zaionc:~# hcitool lescan Set scan parameters failed: Input/output error At first bluetooth stopped working at all due to Ubuntu bug = missing firmware. It was fixed recently and now the bluetooth module seems fine, but the whole BTLE part is not available. Particularly I cannot detect/pair Logitech M720 mouse. Platform: ThinkPad T14 Gen 2i --- ProblemType: Bug ApportVersion: 2.27.0-0ubuntu4 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.10 InstallationDate: Installed on 2022-05-28 (494 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) InterestingModules: rfcomm bnep btusb bluetooth MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']} Package: linux PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-5-generic root=UUID=d0002130-adf6-4f18-93b1-fda536d8b499 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 RebootRequiredPkgs: Error: path contained symlinks. Tags: mantic Uname: Linux 6.5.0-5-generic x86_64 UpgradeStatus: Upgraded to mantic on 2023-09-03 (30 days ago) UserGroups: adm cdrom dialout dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/10/2023 dmi.bios.release: 1.56 dmi.bios.vendor: LENOVO dmi.bios.version: N34ET56W (1.56 ) dmi.board.asset.tag: Not Available dmi.board.name: 20W000AMPB dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.42 dmi.modalias: dmi:bvnLENOVO:bvrN34ET56W(1.56):bd05/10/2023:br1.56:efr1.42:svnLENOVO:pn20W000AMPB:pvrThinkPadT14Gen2i:rvnLENOVO:rn20W000AMPB:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20W0_BU_Think_FM_ThinkPadT14Gen2i: dmi.product.family: ThinkPad T14 Gen 2i dmi.product.name: 20W000AMPB dmi.product.sku: LENOVO_MT_20W0_BU_Think_FM_ThinkPad T14 Gen 2i dmi.product.version: ThinkPad T14 Gen 2i dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: A0:E7:0B:23:70:E8 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:22183 acl:0 sco:0 events:3531 errors:0 TX bytes:821193 acl:0 sco:0 commands:3510 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/linux-firmware/+bug/2037906/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2037906] syslog.txt
apport information ** Attachment added: "syslog.txt" https://bugs.launchpad.net/bugs/2037906/+attachment/5706618/+files/syslog.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2037906 Title: [Intel AX201] Bluetooth LE not working after upgrade from 22.04 to 23.10 Status in bluez package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: syslog: 2023-09-20T09:32:54.138852+02:00 zaionc kernel: [ 13.539860] Bluetooth: hci0: Waiting for firmware download to complete 2023-09-20T09:32:54.138857+02:00 zaionc kernel: [ 13.540223] Bluetooth: hci0: Firmware loaded in 1706498 usecs 2023-09-20T09:32:54.138858+02:00 zaionc kernel: [ 13.540278] Bluetooth: hci0: Waiting for device to boot 2023-09-20T09:32:54.154894+02:00 zaionc kernel: [ 13.555430] Bluetooth: hci0: Malformed MSFT vendor event: 0x02 2023-09-20T09:32:54.154908+02:00 zaionc kernel: [ 13.555482] Bluetooth: hci0: Device booted in 14872 usecs 2023-09-20T09:32:54.154910+02:00 zaionc kernel: [ 13.555913] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-19-0-4.ddc 2023-09-20T09:32:54.158856+02:00 zaionc kernel: [ 13.558300] Bluetooth: hci0: Applying Intel DDC parameters completed 2023-09-20T09:32:54.158859+02:00 zaionc kernel: [ 13.559326] Bluetooth: hci0: Firmware revision 0.4 build 249 week 27 2023 lshw: *-usb:5 description: Bluetooth wireless interface product: AX201 Bluetooth vendor: Intel Corp. physical id: a bus info: usb@3:a version: 0.02 capabilities: bluetooth usb-2.01 configuration: driver=btusb maxpower=100mA speed=12Mbit/s root@zaionc:~# hcitool lescan Set scan parameters failed: Input/output error At first bluetooth stopped working at all due to Ubuntu bug = missing firmware. It was fixed recently and now the bluetooth module seems fine, but the whole BTLE part is not available. Particularly I cannot detect/pair Logitech M720 mouse. Platform: ThinkPad T14 Gen 2i --- ProblemType: Bug ApportVersion: 2.27.0-0ubuntu4 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.10 InstallationDate: Installed on 2022-05-28 (494 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) InterestingModules: rfcomm bnep btusb bluetooth MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']} Package: linux PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-5-generic root=UUID=d0002130-adf6-4f18-93b1-fda536d8b499 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 RebootRequiredPkgs: Error: path contained symlinks. Tags: mantic Uname: Linux 6.5.0-5-generic x86_64 UpgradeStatus: Upgraded to mantic on 2023-09-03 (30 days ago) UserGroups: adm cdrom dialout dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/10/2023 dmi.bios.release: 1.56 dmi.bios.vendor: LENOVO dmi.bios.version: N34ET56W (1.56 ) dmi.board.asset.tag: Not Available dmi.board.name: 20W000AMPB dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.42 dmi.modalias: dmi:bvnLENOVO:bvrN34ET56W(1.56):bd05/10/2023:br1.56:efr1.42:svnLENOVO:pn20W000AMPB:pvrThinkPadT14Gen2i:rvnLENOVO:rn20W000AMPB:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20W0_BU_Think_FM_ThinkPadT14Gen2i: dmi.product.family: ThinkPad T14 Gen 2i dmi.product.name: 20W000AMPB dmi.product.sku: LENOVO_MT_20W0_BU_Think_FM_ThinkPad T14 Gen 2i dmi.product.version: ThinkPad T14 Gen 2i dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: A0:E7:0B:23:70:E8 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:22183 acl:0 sco:0 events:3531 errors:0 TX bytes:821193 acl:0 sco:0 commands:3510 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2037906/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2037906] rfkill.txt
apport information ** Attachment added: "rfkill.txt" https://bugs.launchpad.net/bugs/2037906/+attachment/5706617/+files/rfkill.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2037906 Title: [Intel AX201] Bluetooth LE not working after upgrade from 22.04 to 23.10 Status in bluez package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: syslog: 2023-09-20T09:32:54.138852+02:00 zaionc kernel: [ 13.539860] Bluetooth: hci0: Waiting for firmware download to complete 2023-09-20T09:32:54.138857+02:00 zaionc kernel: [ 13.540223] Bluetooth: hci0: Firmware loaded in 1706498 usecs 2023-09-20T09:32:54.138858+02:00 zaionc kernel: [ 13.540278] Bluetooth: hci0: Waiting for device to boot 2023-09-20T09:32:54.154894+02:00 zaionc kernel: [ 13.555430] Bluetooth: hci0: Malformed MSFT vendor event: 0x02 2023-09-20T09:32:54.154908+02:00 zaionc kernel: [ 13.555482] Bluetooth: hci0: Device booted in 14872 usecs 2023-09-20T09:32:54.154910+02:00 zaionc kernel: [ 13.555913] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-19-0-4.ddc 2023-09-20T09:32:54.158856+02:00 zaionc kernel: [ 13.558300] Bluetooth: hci0: Applying Intel DDC parameters completed 2023-09-20T09:32:54.158859+02:00 zaionc kernel: [ 13.559326] Bluetooth: hci0: Firmware revision 0.4 build 249 week 27 2023 lshw: *-usb:5 description: Bluetooth wireless interface product: AX201 Bluetooth vendor: Intel Corp. physical id: a bus info: usb@3:a version: 0.02 capabilities: bluetooth usb-2.01 configuration: driver=btusb maxpower=100mA speed=12Mbit/s root@zaionc:~# hcitool lescan Set scan parameters failed: Input/output error At first bluetooth stopped working at all due to Ubuntu bug = missing firmware. It was fixed recently and now the bluetooth module seems fine, but the whole BTLE part is not available. Particularly I cannot detect/pair Logitech M720 mouse. Platform: ThinkPad T14 Gen 2i --- ProblemType: Bug ApportVersion: 2.27.0-0ubuntu4 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.10 InstallationDate: Installed on 2022-05-28 (494 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) InterestingModules: rfcomm bnep btusb bluetooth MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']} Package: linux PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-5-generic root=UUID=d0002130-adf6-4f18-93b1-fda536d8b499 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 RebootRequiredPkgs: Error: path contained symlinks. Tags: mantic Uname: Linux 6.5.0-5-generic x86_64 UpgradeStatus: Upgraded to mantic on 2023-09-03 (30 days ago) UserGroups: adm cdrom dialout dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/10/2023 dmi.bios.release: 1.56 dmi.bios.vendor: LENOVO dmi.bios.version: N34ET56W (1.56 ) dmi.board.asset.tag: Not Available dmi.board.name: 20W000AMPB dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.42 dmi.modalias: dmi:bvnLENOVO:bvrN34ET56W(1.56):bd05/10/2023:br1.56:efr1.42:svnLENOVO:pn20W000AMPB:pvrThinkPadT14Gen2i:rvnLENOVO:rn20W000AMPB:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20W0_BU_Think_FM_ThinkPadT14Gen2i: dmi.product.family: ThinkPad T14 Gen 2i dmi.product.name: 20W000AMPB dmi.product.sku: LENOVO_MT_20W0_BU_Think_FM_ThinkPad T14 Gen 2i dmi.product.version: ThinkPad T14 Gen 2i dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: A0:E7:0B:23:70:E8 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:22183 acl:0 sco:0 events:3531 errors:0 TX bytes:821193 acl:0 sco:0 commands:3510 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2037906/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2037906] getfacl.txt
apport information ** Attachment added: "getfacl.txt" https://bugs.launchpad.net/bugs/2037906/+attachment/5706616/+files/getfacl.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2037906 Title: [Intel AX201] Bluetooth LE not working after upgrade from 22.04 to 23.10 Status in bluez package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: syslog: 2023-09-20T09:32:54.138852+02:00 zaionc kernel: [ 13.539860] Bluetooth: hci0: Waiting for firmware download to complete 2023-09-20T09:32:54.138857+02:00 zaionc kernel: [ 13.540223] Bluetooth: hci0: Firmware loaded in 1706498 usecs 2023-09-20T09:32:54.138858+02:00 zaionc kernel: [ 13.540278] Bluetooth: hci0: Waiting for device to boot 2023-09-20T09:32:54.154894+02:00 zaionc kernel: [ 13.555430] Bluetooth: hci0: Malformed MSFT vendor event: 0x02 2023-09-20T09:32:54.154908+02:00 zaionc kernel: [ 13.555482] Bluetooth: hci0: Device booted in 14872 usecs 2023-09-20T09:32:54.154910+02:00 zaionc kernel: [ 13.555913] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-19-0-4.ddc 2023-09-20T09:32:54.158856+02:00 zaionc kernel: [ 13.558300] Bluetooth: hci0: Applying Intel DDC parameters completed 2023-09-20T09:32:54.158859+02:00 zaionc kernel: [ 13.559326] Bluetooth: hci0: Firmware revision 0.4 build 249 week 27 2023 lshw: *-usb:5 description: Bluetooth wireless interface product: AX201 Bluetooth vendor: Intel Corp. physical id: a bus info: usb@3:a version: 0.02 capabilities: bluetooth usb-2.01 configuration: driver=btusb maxpower=100mA speed=12Mbit/s root@zaionc:~# hcitool lescan Set scan parameters failed: Input/output error At first bluetooth stopped working at all due to Ubuntu bug = missing firmware. It was fixed recently and now the bluetooth module seems fine, but the whole BTLE part is not available. Particularly I cannot detect/pair Logitech M720 mouse. Platform: ThinkPad T14 Gen 2i --- ProblemType: Bug ApportVersion: 2.27.0-0ubuntu4 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.10 InstallationDate: Installed on 2022-05-28 (494 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) InterestingModules: rfcomm bnep btusb bluetooth MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']} Package: linux PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-5-generic root=UUID=d0002130-adf6-4f18-93b1-fda536d8b499 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 RebootRequiredPkgs: Error: path contained symlinks. Tags: mantic Uname: Linux 6.5.0-5-generic x86_64 UpgradeStatus: Upgraded to mantic on 2023-09-03 (30 days ago) UserGroups: adm cdrom dialout dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/10/2023 dmi.bios.release: 1.56 dmi.bios.vendor: LENOVO dmi.bios.version: N34ET56W (1.56 ) dmi.board.asset.tag: Not Available dmi.board.name: 20W000AMPB dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.42 dmi.modalias: dmi:bvnLENOVO:bvrN34ET56W(1.56):bd05/10/2023:br1.56:efr1.42:svnLENOVO:pn20W000AMPB:pvrThinkPadT14Gen2i:rvnLENOVO:rn20W000AMPB:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20W0_BU_Think_FM_ThinkPadT14Gen2i: dmi.product.family: ThinkPad T14 Gen 2i dmi.product.name: 20W000AMPB dmi.product.sku: LENOVO_MT_20W0_BU_Think_FM_ThinkPad T14 Gen 2i dmi.product.version: ThinkPad T14 Gen 2i dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: A0:E7:0B:23:70:E8 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:22183 acl:0 sco:0 events:3531 errors:0 TX bytes:821193 acl:0 sco:0 commands:3510 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2037906/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2037906] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/2037906/+attachment/5706614/+files/acpidump.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2037906 Title: [Intel AX201] Bluetooth LE not working after upgrade from 22.04 to 23.10 Status in bluez package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: syslog: 2023-09-20T09:32:54.138852+02:00 zaionc kernel: [ 13.539860] Bluetooth: hci0: Waiting for firmware download to complete 2023-09-20T09:32:54.138857+02:00 zaionc kernel: [ 13.540223] Bluetooth: hci0: Firmware loaded in 1706498 usecs 2023-09-20T09:32:54.138858+02:00 zaionc kernel: [ 13.540278] Bluetooth: hci0: Waiting for device to boot 2023-09-20T09:32:54.154894+02:00 zaionc kernel: [ 13.555430] Bluetooth: hci0: Malformed MSFT vendor event: 0x02 2023-09-20T09:32:54.154908+02:00 zaionc kernel: [ 13.555482] Bluetooth: hci0: Device booted in 14872 usecs 2023-09-20T09:32:54.154910+02:00 zaionc kernel: [ 13.555913] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-19-0-4.ddc 2023-09-20T09:32:54.158856+02:00 zaionc kernel: [ 13.558300] Bluetooth: hci0: Applying Intel DDC parameters completed 2023-09-20T09:32:54.158859+02:00 zaionc kernel: [ 13.559326] Bluetooth: hci0: Firmware revision 0.4 build 249 week 27 2023 lshw: *-usb:5 description: Bluetooth wireless interface product: AX201 Bluetooth vendor: Intel Corp. physical id: a bus info: usb@3:a version: 0.02 capabilities: bluetooth usb-2.01 configuration: driver=btusb maxpower=100mA speed=12Mbit/s root@zaionc:~# hcitool lescan Set scan parameters failed: Input/output error At first bluetooth stopped working at all due to Ubuntu bug = missing firmware. It was fixed recently and now the bluetooth module seems fine, but the whole BTLE part is not available. Particularly I cannot detect/pair Logitech M720 mouse. Platform: ThinkPad T14 Gen 2i --- ProblemType: Bug ApportVersion: 2.27.0-0ubuntu4 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.10 InstallationDate: Installed on 2022-05-28 (494 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) InterestingModules: rfcomm bnep btusb bluetooth MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']} Package: linux PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-5-generic root=UUID=d0002130-adf6-4f18-93b1-fda536d8b499 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 RebootRequiredPkgs: Error: path contained symlinks. Tags: mantic Uname: Linux 6.5.0-5-generic x86_64 UpgradeStatus: Upgraded to mantic on 2023-09-03 (30 days ago) UserGroups: adm cdrom dialout dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/10/2023 dmi.bios.release: 1.56 dmi.bios.vendor: LENOVO dmi.bios.version: N34ET56W (1.56 ) dmi.board.asset.tag: Not Available dmi.board.name: 20W000AMPB dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.42 dmi.modalias: dmi:bvnLENOVO:bvrN34ET56W(1.56):bd05/10/2023:br1.56:efr1.42:svnLENOVO:pn20W000AMPB:pvrThinkPadT14Gen2i:rvnLENOVO:rn20W000AMPB:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20W0_BU_Think_FM_ThinkPadT14Gen2i: dmi.product.family: ThinkPad T14 Gen 2i dmi.product.name: 20W000AMPB dmi.product.sku: LENOVO_MT_20W0_BU_Think_FM_ThinkPad T14 Gen 2i dmi.product.version: ThinkPad T14 Gen 2i dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: A0:E7:0B:23:70:E8 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:22183 acl:0 sco:0 events:3531 errors:0 TX bytes:821193 acl:0 sco:0 commands:3510 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2037906/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2037906] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/2037906/+attachment/5706613/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2037906 Title: [Intel AX201] Bluetooth LE not working after upgrade from 22.04 to 23.10 Status in bluez package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: syslog: 2023-09-20T09:32:54.138852+02:00 zaionc kernel: [ 13.539860] Bluetooth: hci0: Waiting for firmware download to complete 2023-09-20T09:32:54.138857+02:00 zaionc kernel: [ 13.540223] Bluetooth: hci0: Firmware loaded in 1706498 usecs 2023-09-20T09:32:54.138858+02:00 zaionc kernel: [ 13.540278] Bluetooth: hci0: Waiting for device to boot 2023-09-20T09:32:54.154894+02:00 zaionc kernel: [ 13.555430] Bluetooth: hci0: Malformed MSFT vendor event: 0x02 2023-09-20T09:32:54.154908+02:00 zaionc kernel: [ 13.555482] Bluetooth: hci0: Device booted in 14872 usecs 2023-09-20T09:32:54.154910+02:00 zaionc kernel: [ 13.555913] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-19-0-4.ddc 2023-09-20T09:32:54.158856+02:00 zaionc kernel: [ 13.558300] Bluetooth: hci0: Applying Intel DDC parameters completed 2023-09-20T09:32:54.158859+02:00 zaionc kernel: [ 13.559326] Bluetooth: hci0: Firmware revision 0.4 build 249 week 27 2023 lshw: *-usb:5 description: Bluetooth wireless interface product: AX201 Bluetooth vendor: Intel Corp. physical id: a bus info: usb@3:a version: 0.02 capabilities: bluetooth usb-2.01 configuration: driver=btusb maxpower=100mA speed=12Mbit/s root@zaionc:~# hcitool lescan Set scan parameters failed: Input/output error At first bluetooth stopped working at all due to Ubuntu bug = missing firmware. It was fixed recently and now the bluetooth module seems fine, but the whole BTLE part is not available. Particularly I cannot detect/pair Logitech M720 mouse. Platform: ThinkPad T14 Gen 2i --- ProblemType: Bug ApportVersion: 2.27.0-0ubuntu4 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.10 InstallationDate: Installed on 2022-05-28 (494 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) InterestingModules: rfcomm bnep btusb bluetooth MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']} Package: linux PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-5-generic root=UUID=d0002130-adf6-4f18-93b1-fda536d8b499 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 RebootRequiredPkgs: Error: path contained symlinks. Tags: mantic Uname: Linux 6.5.0-5-generic x86_64 UpgradeStatus: Upgraded to mantic on 2023-09-03 (30 days ago) UserGroups: adm cdrom dialout dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/10/2023 dmi.bios.release: 1.56 dmi.bios.vendor: LENOVO dmi.bios.version: N34ET56W (1.56 ) dmi.board.asset.tag: Not Available dmi.board.name: 20W000AMPB dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.42 dmi.modalias: dmi:bvnLENOVO:bvrN34ET56W(1.56):bd05/10/2023:br1.56:efr1.42:svnLENOVO:pn20W000AMPB:pvrThinkPadT14Gen2i:rvnLENOVO:rn20W000AMPB:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20W0_BU_Think_FM_ThinkPadT14Gen2i: dmi.product.family: ThinkPad T14 Gen 2i dmi.product.name: 20W000AMPB dmi.product.sku: LENOVO_MT_20W0_BU_Think_FM_ThinkPad T14 Gen 2i dmi.product.version: ThinkPad T14 Gen 2i dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: A0:E7:0B:23:70:E8 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:22183 acl:0 sco:0 events:3531 errors:0 TX bytes:821193 acl:0 sco:0 commands:3510 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2037906/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2037906] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/2037906/+attachment/5706612/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2037906 Title: [Intel AX201] Bluetooth LE not working after upgrade from 22.04 to 23.10 Status in bluez package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: syslog: 2023-09-20T09:32:54.138852+02:00 zaionc kernel: [ 13.539860] Bluetooth: hci0: Waiting for firmware download to complete 2023-09-20T09:32:54.138857+02:00 zaionc kernel: [ 13.540223] Bluetooth: hci0: Firmware loaded in 1706498 usecs 2023-09-20T09:32:54.138858+02:00 zaionc kernel: [ 13.540278] Bluetooth: hci0: Waiting for device to boot 2023-09-20T09:32:54.154894+02:00 zaionc kernel: [ 13.555430] Bluetooth: hci0: Malformed MSFT vendor event: 0x02 2023-09-20T09:32:54.154908+02:00 zaionc kernel: [ 13.555482] Bluetooth: hci0: Device booted in 14872 usecs 2023-09-20T09:32:54.154910+02:00 zaionc kernel: [ 13.555913] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-19-0-4.ddc 2023-09-20T09:32:54.158856+02:00 zaionc kernel: [ 13.558300] Bluetooth: hci0: Applying Intel DDC parameters completed 2023-09-20T09:32:54.158859+02:00 zaionc kernel: [ 13.559326] Bluetooth: hci0: Firmware revision 0.4 build 249 week 27 2023 lshw: *-usb:5 description: Bluetooth wireless interface product: AX201 Bluetooth vendor: Intel Corp. physical id: a bus info: usb@3:a version: 0.02 capabilities: bluetooth usb-2.01 configuration: driver=btusb maxpower=100mA speed=12Mbit/s root@zaionc:~# hcitool lescan Set scan parameters failed: Input/output error At first bluetooth stopped working at all due to Ubuntu bug = missing firmware. It was fixed recently and now the bluetooth module seems fine, but the whole BTLE part is not available. Particularly I cannot detect/pair Logitech M720 mouse. Platform: ThinkPad T14 Gen 2i --- ProblemType: Bug ApportVersion: 2.27.0-0ubuntu4 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.10 InstallationDate: Installed on 2022-05-28 (494 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) InterestingModules: rfcomm bnep btusb bluetooth MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']} Package: linux PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-5-generic root=UUID=d0002130-adf6-4f18-93b1-fda536d8b499 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 RebootRequiredPkgs: Error: path contained symlinks. Tags: mantic Uname: Linux 6.5.0-5-generic x86_64 UpgradeStatus: Upgraded to mantic on 2023-09-03 (30 days ago) UserGroups: adm cdrom dialout dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/10/2023 dmi.bios.release: 1.56 dmi.bios.vendor: LENOVO dmi.bios.version: N34ET56W (1.56 ) dmi.board.asset.tag: Not Available dmi.board.name: 20W000AMPB dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.42 dmi.modalias: dmi:bvnLENOVO:bvrN34ET56W(1.56):bd05/10/2023:br1.56:efr1.42:svnLENOVO:pn20W000AMPB:pvrThinkPadT14Gen2i:rvnLENOVO:rn20W000AMPB:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20W0_BU_Think_FM_ThinkPadT14Gen2i: dmi.product.family: ThinkPad T14 Gen 2i dmi.product.name: 20W000AMPB dmi.product.sku: LENOVO_MT_20W0_BU_Think_FM_ThinkPad T14 Gen 2i dmi.product.version: ThinkPad T14 Gen 2i dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: A0:E7:0B:23:70:E8 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:22183 acl:0 sco:0 events:3531 errors:0 TX bytes:821193 acl:0 sco:0 commands:3510 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2037906/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2037906] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/2037906/+attachment/5706611/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2037906 Title: [Intel AX201] Bluetooth LE not working after upgrade from 22.04 to 23.10 Status in bluez package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: syslog: 2023-09-20T09:32:54.138852+02:00 zaionc kernel: [ 13.539860] Bluetooth: hci0: Waiting for firmware download to complete 2023-09-20T09:32:54.138857+02:00 zaionc kernel: [ 13.540223] Bluetooth: hci0: Firmware loaded in 1706498 usecs 2023-09-20T09:32:54.138858+02:00 zaionc kernel: [ 13.540278] Bluetooth: hci0: Waiting for device to boot 2023-09-20T09:32:54.154894+02:00 zaionc kernel: [ 13.555430] Bluetooth: hci0: Malformed MSFT vendor event: 0x02 2023-09-20T09:32:54.154908+02:00 zaionc kernel: [ 13.555482] Bluetooth: hci0: Device booted in 14872 usecs 2023-09-20T09:32:54.154910+02:00 zaionc kernel: [ 13.555913] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-19-0-4.ddc 2023-09-20T09:32:54.158856+02:00 zaionc kernel: [ 13.558300] Bluetooth: hci0: Applying Intel DDC parameters completed 2023-09-20T09:32:54.158859+02:00 zaionc kernel: [ 13.559326] Bluetooth: hci0: Firmware revision 0.4 build 249 week 27 2023 lshw: *-usb:5 description: Bluetooth wireless interface product: AX201 Bluetooth vendor: Intel Corp. physical id: a bus info: usb@3:a version: 0.02 capabilities: bluetooth usb-2.01 configuration: driver=btusb maxpower=100mA speed=12Mbit/s root@zaionc:~# hcitool lescan Set scan parameters failed: Input/output error At first bluetooth stopped working at all due to Ubuntu bug = missing firmware. It was fixed recently and now the bluetooth module seems fine, but the whole BTLE part is not available. Particularly I cannot detect/pair Logitech M720 mouse. Platform: ThinkPad T14 Gen 2i --- ProblemType: Bug ApportVersion: 2.27.0-0ubuntu4 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.10 InstallationDate: Installed on 2022-05-28 (494 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) InterestingModules: rfcomm bnep btusb bluetooth MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']} Package: linux PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-5-generic root=UUID=d0002130-adf6-4f18-93b1-fda536d8b499 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 RebootRequiredPkgs: Error: path contained symlinks. Tags: mantic Uname: Linux 6.5.0-5-generic x86_64 UpgradeStatus: Upgraded to mantic on 2023-09-03 (30 days ago) UserGroups: adm cdrom dialout dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/10/2023 dmi.bios.release: 1.56 dmi.bios.vendor: LENOVO dmi.bios.version: N34ET56W (1.56 ) dmi.board.asset.tag: Not Available dmi.board.name: 20W000AMPB dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.42 dmi.modalias: dmi:bvnLENOVO:bvrN34ET56W(1.56):bd05/10/2023:br1.56:efr1.42:svnLENOVO:pn20W000AMPB:pvrThinkPadT14Gen2i:rvnLENOVO:rn20W000AMPB:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20W0_BU_Think_FM_ThinkPadT14Gen2i: dmi.product.family: ThinkPad T14 Gen 2i dmi.product.name: 20W000AMPB dmi.product.sku: LENOVO_MT_20W0_BU_Think_FM_ThinkPad T14 Gen 2i dmi.product.version: ThinkPad T14 Gen 2i dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: A0:E7:0B:23:70:E8 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:22183 acl:0 sco:0 events:3531 errors:0 TX bytes:821193 acl:0 sco:0 commands:3510 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2037906/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2037906] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/2037906/+attachment/5706610/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2037906 Title: [Intel AX201] Bluetooth LE not working after upgrade from 22.04 to 23.10 Status in bluez package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: syslog: 2023-09-20T09:32:54.138852+02:00 zaionc kernel: [ 13.539860] Bluetooth: hci0: Waiting for firmware download to complete 2023-09-20T09:32:54.138857+02:00 zaionc kernel: [ 13.540223] Bluetooth: hci0: Firmware loaded in 1706498 usecs 2023-09-20T09:32:54.138858+02:00 zaionc kernel: [ 13.540278] Bluetooth: hci0: Waiting for device to boot 2023-09-20T09:32:54.154894+02:00 zaionc kernel: [ 13.555430] Bluetooth: hci0: Malformed MSFT vendor event: 0x02 2023-09-20T09:32:54.154908+02:00 zaionc kernel: [ 13.555482] Bluetooth: hci0: Device booted in 14872 usecs 2023-09-20T09:32:54.154910+02:00 zaionc kernel: [ 13.555913] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-19-0-4.ddc 2023-09-20T09:32:54.158856+02:00 zaionc kernel: [ 13.558300] Bluetooth: hci0: Applying Intel DDC parameters completed 2023-09-20T09:32:54.158859+02:00 zaionc kernel: [ 13.559326] Bluetooth: hci0: Firmware revision 0.4 build 249 week 27 2023 lshw: *-usb:5 description: Bluetooth wireless interface product: AX201 Bluetooth vendor: Intel Corp. physical id: a bus info: usb@3:a version: 0.02 capabilities: bluetooth usb-2.01 configuration: driver=btusb maxpower=100mA speed=12Mbit/s root@zaionc:~# hcitool lescan Set scan parameters failed: Input/output error At first bluetooth stopped working at all due to Ubuntu bug = missing firmware. It was fixed recently and now the bluetooth module seems fine, but the whole BTLE part is not available. Particularly I cannot detect/pair Logitech M720 mouse. Platform: ThinkPad T14 Gen 2i --- ProblemType: Bug ApportVersion: 2.27.0-0ubuntu4 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.10 InstallationDate: Installed on 2022-05-28 (494 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) InterestingModules: rfcomm bnep btusb bluetooth MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']} Package: linux PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-5-generic root=UUID=d0002130-adf6-4f18-93b1-fda536d8b499 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 RebootRequiredPkgs: Error: path contained symlinks. Tags: mantic Uname: Linux 6.5.0-5-generic x86_64 UpgradeStatus: Upgraded to mantic on 2023-09-03 (30 days ago) UserGroups: adm cdrom dialout dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/10/2023 dmi.bios.release: 1.56 dmi.bios.vendor: LENOVO dmi.bios.version: N34ET56W (1.56 ) dmi.board.asset.tag: Not Available dmi.board.name: 20W000AMPB dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.42 dmi.modalias: dmi:bvnLENOVO:bvrN34ET56W(1.56):bd05/10/2023:br1.56:efr1.42:svnLENOVO:pn20W000AMPB:pvrThinkPadT14Gen2i:rvnLENOVO:rn20W000AMPB:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20W0_BU_Think_FM_ThinkPadT14Gen2i: dmi.product.family: ThinkPad T14 Gen 2i dmi.product.name: 20W000AMPB dmi.product.sku: LENOVO_MT_20W0_BU_Think_FM_ThinkPad T14 Gen 2i dmi.product.version: ThinkPad T14 Gen 2i dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: A0:E7:0B:23:70:E8 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:22183 acl:0 sco:0 events:3531 errors:0 TX bytes:821193 acl:0 sco:0 commands:3510 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2037906/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2037906] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/2037906/+attachment/5706609/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2037906 Title: [Intel AX201] Bluetooth LE not working after upgrade from 22.04 to 23.10 Status in bluez package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: syslog: 2023-09-20T09:32:54.138852+02:00 zaionc kernel: [ 13.539860] Bluetooth: hci0: Waiting for firmware download to complete 2023-09-20T09:32:54.138857+02:00 zaionc kernel: [ 13.540223] Bluetooth: hci0: Firmware loaded in 1706498 usecs 2023-09-20T09:32:54.138858+02:00 zaionc kernel: [ 13.540278] Bluetooth: hci0: Waiting for device to boot 2023-09-20T09:32:54.154894+02:00 zaionc kernel: [ 13.555430] Bluetooth: hci0: Malformed MSFT vendor event: 0x02 2023-09-20T09:32:54.154908+02:00 zaionc kernel: [ 13.555482] Bluetooth: hci0: Device booted in 14872 usecs 2023-09-20T09:32:54.154910+02:00 zaionc kernel: [ 13.555913] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-19-0-4.ddc 2023-09-20T09:32:54.158856+02:00 zaionc kernel: [ 13.558300] Bluetooth: hci0: Applying Intel DDC parameters completed 2023-09-20T09:32:54.158859+02:00 zaionc kernel: [ 13.559326] Bluetooth: hci0: Firmware revision 0.4 build 249 week 27 2023 lshw: *-usb:5 description: Bluetooth wireless interface product: AX201 Bluetooth vendor: Intel Corp. physical id: a bus info: usb@3:a version: 0.02 capabilities: bluetooth usb-2.01 configuration: driver=btusb maxpower=100mA speed=12Mbit/s root@zaionc:~# hcitool lescan Set scan parameters failed: Input/output error At first bluetooth stopped working at all due to Ubuntu bug = missing firmware. It was fixed recently and now the bluetooth module seems fine, but the whole BTLE part is not available. Particularly I cannot detect/pair Logitech M720 mouse. Platform: ThinkPad T14 Gen 2i --- ProblemType: Bug ApportVersion: 2.27.0-0ubuntu4 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.10 InstallationDate: Installed on 2022-05-28 (494 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) InterestingModules: rfcomm bnep btusb bluetooth MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']} Package: linux PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-5-generic root=UUID=d0002130-adf6-4f18-93b1-fda536d8b499 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 RebootRequiredPkgs: Error: path contained symlinks. Tags: mantic Uname: Linux 6.5.0-5-generic x86_64 UpgradeStatus: Upgraded to mantic on 2023-09-03 (30 days ago) UserGroups: adm cdrom dialout dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/10/2023 dmi.bios.release: 1.56 dmi.bios.vendor: LENOVO dmi.bios.version: N34ET56W (1.56 ) dmi.board.asset.tag: Not Available dmi.board.name: 20W000AMPB dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.42 dmi.modalias: dmi:bvnLENOVO:bvrN34ET56W(1.56):bd05/10/2023:br1.56:efr1.42:svnLENOVO:pn20W000AMPB:pvrThinkPadT14Gen2i:rvnLENOVO:rn20W000AMPB:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20W0_BU_Think_FM_ThinkPadT14Gen2i: dmi.product.family: ThinkPad T14 Gen 2i dmi.product.name: 20W000AMPB dmi.product.sku: LENOVO_MT_20W0_BU_Think_FM_ThinkPad T14 Gen 2i dmi.product.version: ThinkPad T14 Gen 2i dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: A0:E7:0B:23:70:E8 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:22183 acl:0 sco:0 events:3531 errors:0 TX bytes:821193 acl:0 sco:0 commands:3510 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2037906/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2037906] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/2037906/+attachment/5706608/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2037906 Title: [Intel AX201] Bluetooth LE not working after upgrade from 22.04 to 23.10 Status in bluez package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: syslog: 2023-09-20T09:32:54.138852+02:00 zaionc kernel: [ 13.539860] Bluetooth: hci0: Waiting for firmware download to complete 2023-09-20T09:32:54.138857+02:00 zaionc kernel: [ 13.540223] Bluetooth: hci0: Firmware loaded in 1706498 usecs 2023-09-20T09:32:54.138858+02:00 zaionc kernel: [ 13.540278] Bluetooth: hci0: Waiting for device to boot 2023-09-20T09:32:54.154894+02:00 zaionc kernel: [ 13.555430] Bluetooth: hci0: Malformed MSFT vendor event: 0x02 2023-09-20T09:32:54.154908+02:00 zaionc kernel: [ 13.555482] Bluetooth: hci0: Device booted in 14872 usecs 2023-09-20T09:32:54.154910+02:00 zaionc kernel: [ 13.555913] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-19-0-4.ddc 2023-09-20T09:32:54.158856+02:00 zaionc kernel: [ 13.558300] Bluetooth: hci0: Applying Intel DDC parameters completed 2023-09-20T09:32:54.158859+02:00 zaionc kernel: [ 13.559326] Bluetooth: hci0: Firmware revision 0.4 build 249 week 27 2023 lshw: *-usb:5 description: Bluetooth wireless interface product: AX201 Bluetooth vendor: Intel Corp. physical id: a bus info: usb@3:a version: 0.02 capabilities: bluetooth usb-2.01 configuration: driver=btusb maxpower=100mA speed=12Mbit/s root@zaionc:~# hcitool lescan Set scan parameters failed: Input/output error At first bluetooth stopped working at all due to Ubuntu bug = missing firmware. It was fixed recently and now the bluetooth module seems fine, but the whole BTLE part is not available. Particularly I cannot detect/pair Logitech M720 mouse. Platform: ThinkPad T14 Gen 2i --- ProblemType: Bug ApportVersion: 2.27.0-0ubuntu4 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.10 InstallationDate: Installed on 2022-05-28 (494 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) InterestingModules: rfcomm bnep btusb bluetooth MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']} Package: linux PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-5-generic root=UUID=d0002130-adf6-4f18-93b1-fda536d8b499 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 RebootRequiredPkgs: Error: path contained symlinks. Tags: mantic Uname: Linux 6.5.0-5-generic x86_64 UpgradeStatus: Upgraded to mantic on 2023-09-03 (30 days ago) UserGroups: adm cdrom dialout dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/10/2023 dmi.bios.release: 1.56 dmi.bios.vendor: LENOVO dmi.bios.version: N34ET56W (1.56 ) dmi.board.asset.tag: Not Available dmi.board.name: 20W000AMPB dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.42 dmi.modalias: dmi:bvnLENOVO:bvrN34ET56W(1.56):bd05/10/2023:br1.56:efr1.42:svnLENOVO:pn20W000AMPB:pvrThinkPadT14Gen2i:rvnLENOVO:rn20W000AMPB:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20W0_BU_Think_FM_ThinkPadT14Gen2i: dmi.product.family: ThinkPad T14 Gen 2i dmi.product.name: 20W000AMPB dmi.product.sku: LENOVO_MT_20W0_BU_Think_FM_ThinkPad T14 Gen 2i dmi.product.version: ThinkPad T14 Gen 2i dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: A0:E7:0B:23:70:E8 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:22183 acl:0 sco:0 events:3531 errors:0 TX bytes:821193 acl:0 sco:0 commands:3510 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2037906/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2037906] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/2037906/+attachment/5706607/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2037906 Title: [Intel AX201] Bluetooth LE not working after upgrade from 22.04 to 23.10 Status in bluez package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: syslog: 2023-09-20T09:32:54.138852+02:00 zaionc kernel: [ 13.539860] Bluetooth: hci0: Waiting for firmware download to complete 2023-09-20T09:32:54.138857+02:00 zaionc kernel: [ 13.540223] Bluetooth: hci0: Firmware loaded in 1706498 usecs 2023-09-20T09:32:54.138858+02:00 zaionc kernel: [ 13.540278] Bluetooth: hci0: Waiting for device to boot 2023-09-20T09:32:54.154894+02:00 zaionc kernel: [ 13.555430] Bluetooth: hci0: Malformed MSFT vendor event: 0x02 2023-09-20T09:32:54.154908+02:00 zaionc kernel: [ 13.555482] Bluetooth: hci0: Device booted in 14872 usecs 2023-09-20T09:32:54.154910+02:00 zaionc kernel: [ 13.555913] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-19-0-4.ddc 2023-09-20T09:32:54.158856+02:00 zaionc kernel: [ 13.558300] Bluetooth: hci0: Applying Intel DDC parameters completed 2023-09-20T09:32:54.158859+02:00 zaionc kernel: [ 13.559326] Bluetooth: hci0: Firmware revision 0.4 build 249 week 27 2023 lshw: *-usb:5 description: Bluetooth wireless interface product: AX201 Bluetooth vendor: Intel Corp. physical id: a bus info: usb@3:a version: 0.02 capabilities: bluetooth usb-2.01 configuration: driver=btusb maxpower=100mA speed=12Mbit/s root@zaionc:~# hcitool lescan Set scan parameters failed: Input/output error At first bluetooth stopped working at all due to Ubuntu bug = missing firmware. It was fixed recently and now the bluetooth module seems fine, but the whole BTLE part is not available. Particularly I cannot detect/pair Logitech M720 mouse. Platform: ThinkPad T14 Gen 2i --- ProblemType: Bug ApportVersion: 2.27.0-0ubuntu4 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.10 InstallationDate: Installed on 2022-05-28 (494 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) InterestingModules: rfcomm bnep btusb bluetooth MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']} Package: linux PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-5-generic root=UUID=d0002130-adf6-4f18-93b1-fda536d8b499 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 RebootRequiredPkgs: Error: path contained symlinks. Tags: mantic Uname: Linux 6.5.0-5-generic x86_64 UpgradeStatus: Upgraded to mantic on 2023-09-03 (30 days ago) UserGroups: adm cdrom dialout dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/10/2023 dmi.bios.release: 1.56 dmi.bios.vendor: LENOVO dmi.bios.version: N34ET56W (1.56 ) dmi.board.asset.tag: Not Available dmi.board.name: 20W000AMPB dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.42 dmi.modalias: dmi:bvnLENOVO:bvrN34ET56W(1.56):bd05/10/2023:br1.56:efr1.42:svnLENOVO:pn20W000AMPB:pvrThinkPadT14Gen2i:rvnLENOVO:rn20W000AMPB:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20W0_BU_Think_FM_ThinkPadT14Gen2i: dmi.product.family: ThinkPad T14 Gen 2i dmi.product.name: 20W000AMPB dmi.product.sku: LENOVO_MT_20W0_BU_Think_FM_ThinkPad T14 Gen 2i dmi.product.version: ThinkPad T14 Gen 2i dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: A0:E7:0B:23:70:E8 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:22183 acl:0 sco:0 events:3531 errors:0 TX bytes:821193 acl:0 sco:0 commands:3510 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2037906/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2037906] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/2037906/+attachment/5706606/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2037906 Title: [Intel AX201] Bluetooth LE not working after upgrade from 22.04 to 23.10 Status in bluez package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: syslog: 2023-09-20T09:32:54.138852+02:00 zaionc kernel: [ 13.539860] Bluetooth: hci0: Waiting for firmware download to complete 2023-09-20T09:32:54.138857+02:00 zaionc kernel: [ 13.540223] Bluetooth: hci0: Firmware loaded in 1706498 usecs 2023-09-20T09:32:54.138858+02:00 zaionc kernel: [ 13.540278] Bluetooth: hci0: Waiting for device to boot 2023-09-20T09:32:54.154894+02:00 zaionc kernel: [ 13.555430] Bluetooth: hci0: Malformed MSFT vendor event: 0x02 2023-09-20T09:32:54.154908+02:00 zaionc kernel: [ 13.555482] Bluetooth: hci0: Device booted in 14872 usecs 2023-09-20T09:32:54.154910+02:00 zaionc kernel: [ 13.555913] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-19-0-4.ddc 2023-09-20T09:32:54.158856+02:00 zaionc kernel: [ 13.558300] Bluetooth: hci0: Applying Intel DDC parameters completed 2023-09-20T09:32:54.158859+02:00 zaionc kernel: [ 13.559326] Bluetooth: hci0: Firmware revision 0.4 build 249 week 27 2023 lshw: *-usb:5 description: Bluetooth wireless interface product: AX201 Bluetooth vendor: Intel Corp. physical id: a bus info: usb@3:a version: 0.02 capabilities: bluetooth usb-2.01 configuration: driver=btusb maxpower=100mA speed=12Mbit/s root@zaionc:~# hcitool lescan Set scan parameters failed: Input/output error At first bluetooth stopped working at all due to Ubuntu bug = missing firmware. It was fixed recently and now the bluetooth module seems fine, but the whole BTLE part is not available. Particularly I cannot detect/pair Logitech M720 mouse. Platform: ThinkPad T14 Gen 2i --- ProblemType: Bug ApportVersion: 2.27.0-0ubuntu4 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.10 InstallationDate: Installed on 2022-05-28 (494 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) InterestingModules: rfcomm bnep btusb bluetooth MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']} Package: linux PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-5-generic root=UUID=d0002130-adf6-4f18-93b1-fda536d8b499 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 RebootRequiredPkgs: Error: path contained symlinks. Tags: mantic Uname: Linux 6.5.0-5-generic x86_64 UpgradeStatus: Upgraded to mantic on 2023-09-03 (30 days ago) UserGroups: adm cdrom dialout dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/10/2023 dmi.bios.release: 1.56 dmi.bios.vendor: LENOVO dmi.bios.version: N34ET56W (1.56 ) dmi.board.asset.tag: Not Available dmi.board.name: 20W000AMPB dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.42 dmi.modalias: dmi:bvnLENOVO:bvrN34ET56W(1.56):bd05/10/2023:br1.56:efr1.42:svnLENOVO:pn20W000AMPB:pvrThinkPadT14Gen2i:rvnLENOVO:rn20W000AMPB:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20W0_BU_Think_FM_ThinkPadT14Gen2i: dmi.product.family: ThinkPad T14 Gen 2i dmi.product.name: 20W000AMPB dmi.product.sku: LENOVO_MT_20W0_BU_Think_FM_ThinkPad T14 Gen 2i dmi.product.version: ThinkPad T14 Gen 2i dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: A0:E7:0B:23:70:E8 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:22183 acl:0 sco:0 events:3531 errors:0 TX bytes:821193 acl:0 sco:0 commands:3510 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2037906/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2037906] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/2037906/+attachment/5706605/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2037906 Title: [Intel AX201] Bluetooth LE not working after upgrade from 22.04 to 23.10 Status in bluez package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: syslog: 2023-09-20T09:32:54.138852+02:00 zaionc kernel: [ 13.539860] Bluetooth: hci0: Waiting for firmware download to complete 2023-09-20T09:32:54.138857+02:00 zaionc kernel: [ 13.540223] Bluetooth: hci0: Firmware loaded in 1706498 usecs 2023-09-20T09:32:54.138858+02:00 zaionc kernel: [ 13.540278] Bluetooth: hci0: Waiting for device to boot 2023-09-20T09:32:54.154894+02:00 zaionc kernel: [ 13.555430] Bluetooth: hci0: Malformed MSFT vendor event: 0x02 2023-09-20T09:32:54.154908+02:00 zaionc kernel: [ 13.555482] Bluetooth: hci0: Device booted in 14872 usecs 2023-09-20T09:32:54.154910+02:00 zaionc kernel: [ 13.555913] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-19-0-4.ddc 2023-09-20T09:32:54.158856+02:00 zaionc kernel: [ 13.558300] Bluetooth: hci0: Applying Intel DDC parameters completed 2023-09-20T09:32:54.158859+02:00 zaionc kernel: [ 13.559326] Bluetooth: hci0: Firmware revision 0.4 build 249 week 27 2023 lshw: *-usb:5 description: Bluetooth wireless interface product: AX201 Bluetooth vendor: Intel Corp. physical id: a bus info: usb@3:a version: 0.02 capabilities: bluetooth usb-2.01 configuration: driver=btusb maxpower=100mA speed=12Mbit/s root@zaionc:~# hcitool lescan Set scan parameters failed: Input/output error At first bluetooth stopped working at all due to Ubuntu bug = missing firmware. It was fixed recently and now the bluetooth module seems fine, but the whole BTLE part is not available. Particularly I cannot detect/pair Logitech M720 mouse. Platform: ThinkPad T14 Gen 2i --- ProblemType: Bug ApportVersion: 2.27.0-0ubuntu4 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.10 InstallationDate: Installed on 2022-05-28 (494 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) InterestingModules: rfcomm bnep btusb bluetooth MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']} Package: linux PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-5-generic root=UUID=d0002130-adf6-4f18-93b1-fda536d8b499 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 RebootRequiredPkgs: Error: path contained symlinks. Tags: mantic Uname: Linux 6.5.0-5-generic x86_64 UpgradeStatus: Upgraded to mantic on 2023-09-03 (30 days ago) UserGroups: adm cdrom dialout dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/10/2023 dmi.bios.release: 1.56 dmi.bios.vendor: LENOVO dmi.bios.version: N34ET56W (1.56 ) dmi.board.asset.tag: Not Available dmi.board.name: 20W000AMPB dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.42 dmi.modalias: dmi:bvnLENOVO:bvrN34ET56W(1.56):bd05/10/2023:br1.56:efr1.42:svnLENOVO:pn20W000AMPB:pvrThinkPadT14Gen2i:rvnLENOVO:rn20W000AMPB:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20W0_BU_Think_FM_ThinkPadT14Gen2i: dmi.product.family: ThinkPad T14 Gen 2i dmi.product.name: 20W000AMPB dmi.product.sku: LENOVO_MT_20W0_BU_Think_FM_ThinkPad T14 Gen 2i dmi.product.version: ThinkPad T14 Gen 2i dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: A0:E7:0B:23:70:E8 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:22183 acl:0 sco:0 events:3531 errors:0 TX bytes:821193 acl:0 sco:0 commands:3510 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2037906/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2037906] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/2037906/+attachment/5706604/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2037906 Title: [Intel AX201] Bluetooth LE not working after upgrade from 22.04 to 23.10 Status in bluez package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: syslog: 2023-09-20T09:32:54.138852+02:00 zaionc kernel: [ 13.539860] Bluetooth: hci0: Waiting for firmware download to complete 2023-09-20T09:32:54.138857+02:00 zaionc kernel: [ 13.540223] Bluetooth: hci0: Firmware loaded in 1706498 usecs 2023-09-20T09:32:54.138858+02:00 zaionc kernel: [ 13.540278] Bluetooth: hci0: Waiting for device to boot 2023-09-20T09:32:54.154894+02:00 zaionc kernel: [ 13.555430] Bluetooth: hci0: Malformed MSFT vendor event: 0x02 2023-09-20T09:32:54.154908+02:00 zaionc kernel: [ 13.555482] Bluetooth: hci0: Device booted in 14872 usecs 2023-09-20T09:32:54.154910+02:00 zaionc kernel: [ 13.555913] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-19-0-4.ddc 2023-09-20T09:32:54.158856+02:00 zaionc kernel: [ 13.558300] Bluetooth: hci0: Applying Intel DDC parameters completed 2023-09-20T09:32:54.158859+02:00 zaionc kernel: [ 13.559326] Bluetooth: hci0: Firmware revision 0.4 build 249 week 27 2023 lshw: *-usb:5 description: Bluetooth wireless interface product: AX201 Bluetooth vendor: Intel Corp. physical id: a bus info: usb@3:a version: 0.02 capabilities: bluetooth usb-2.01 configuration: driver=btusb maxpower=100mA speed=12Mbit/s root@zaionc:~# hcitool lescan Set scan parameters failed: Input/output error At first bluetooth stopped working at all due to Ubuntu bug = missing firmware. It was fixed recently and now the bluetooth module seems fine, but the whole BTLE part is not available. Particularly I cannot detect/pair Logitech M720 mouse. Platform: ThinkPad T14 Gen 2i --- ProblemType: Bug ApportVersion: 2.27.0-0ubuntu4 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.10 InstallationDate: Installed on 2022-05-28 (494 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) InterestingModules: rfcomm bnep btusb bluetooth MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']} Package: linux PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-5-generic root=UUID=d0002130-adf6-4f18-93b1-fda536d8b499 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 RebootRequiredPkgs: Error: path contained symlinks. Tags: mantic Uname: Linux 6.5.0-5-generic x86_64 UpgradeStatus: Upgraded to mantic on 2023-09-03 (30 days ago) UserGroups: adm cdrom dialout dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/10/2023 dmi.bios.release: 1.56 dmi.bios.vendor: LENOVO dmi.bios.version: N34ET56W (1.56 ) dmi.board.asset.tag: Not Available dmi.board.name: 20W000AMPB dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.42 dmi.modalias: dmi:bvnLENOVO:bvrN34ET56W(1.56):bd05/10/2023:br1.56:efr1.42:svnLENOVO:pn20W000AMPB:pvrThinkPadT14Gen2i:rvnLENOVO:rn20W000AMPB:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20W0_BU_Think_FM_ThinkPadT14Gen2i: dmi.product.family: ThinkPad T14 Gen 2i dmi.product.name: 20W000AMPB dmi.product.sku: LENOVO_MT_20W0_BU_Think_FM_ThinkPad T14 Gen 2i dmi.product.version: ThinkPad T14 Gen 2i dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: A0:E7:0B:23:70:E8 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:22183 acl:0 sco:0 events:3531 errors:0 TX bytes:821193 acl:0 sco:0 commands:3510 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2037906/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2037906] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/2037906/+attachment/5706603/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2037906 Title: [Intel AX201] Bluetooth LE not working after upgrade from 22.04 to 23.10 Status in bluez package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: syslog: 2023-09-20T09:32:54.138852+02:00 zaionc kernel: [ 13.539860] Bluetooth: hci0: Waiting for firmware download to complete 2023-09-20T09:32:54.138857+02:00 zaionc kernel: [ 13.540223] Bluetooth: hci0: Firmware loaded in 1706498 usecs 2023-09-20T09:32:54.138858+02:00 zaionc kernel: [ 13.540278] Bluetooth: hci0: Waiting for device to boot 2023-09-20T09:32:54.154894+02:00 zaionc kernel: [ 13.555430] Bluetooth: hci0: Malformed MSFT vendor event: 0x02 2023-09-20T09:32:54.154908+02:00 zaionc kernel: [ 13.555482] Bluetooth: hci0: Device booted in 14872 usecs 2023-09-20T09:32:54.154910+02:00 zaionc kernel: [ 13.555913] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-19-0-4.ddc 2023-09-20T09:32:54.158856+02:00 zaionc kernel: [ 13.558300] Bluetooth: hci0: Applying Intel DDC parameters completed 2023-09-20T09:32:54.158859+02:00 zaionc kernel: [ 13.559326] Bluetooth: hci0: Firmware revision 0.4 build 249 week 27 2023 lshw: *-usb:5 description: Bluetooth wireless interface product: AX201 Bluetooth vendor: Intel Corp. physical id: a bus info: usb@3:a version: 0.02 capabilities: bluetooth usb-2.01 configuration: driver=btusb maxpower=100mA speed=12Mbit/s root@zaionc:~# hcitool lescan Set scan parameters failed: Input/output error At first bluetooth stopped working at all due to Ubuntu bug = missing firmware. It was fixed recently and now the bluetooth module seems fine, but the whole BTLE part is not available. Particularly I cannot detect/pair Logitech M720 mouse. Platform: ThinkPad T14 Gen 2i --- ProblemType: Bug ApportVersion: 2.27.0-0ubuntu4 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.10 InstallationDate: Installed on 2022-05-28 (494 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) InterestingModules: rfcomm bnep btusb bluetooth MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']} Package: linux PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-5-generic root=UUID=d0002130-adf6-4f18-93b1-fda536d8b499 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 RebootRequiredPkgs: Error: path contained symlinks. Tags: mantic Uname: Linux 6.5.0-5-generic x86_64 UpgradeStatus: Upgraded to mantic on 2023-09-03 (30 days ago) UserGroups: adm cdrom dialout dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/10/2023 dmi.bios.release: 1.56 dmi.bios.vendor: LENOVO dmi.bios.version: N34ET56W (1.56 ) dmi.board.asset.tag: Not Available dmi.board.name: 20W000AMPB dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.42 dmi.modalias: dmi:bvnLENOVO:bvrN34ET56W(1.56):bd05/10/2023:br1.56:efr1.42:svnLENOVO:pn20W000AMPB:pvrThinkPadT14Gen2i:rvnLENOVO:rn20W000AMPB:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20W0_BU_Think_FM_ThinkPadT14Gen2i: dmi.product.family: ThinkPad T14 Gen 2i dmi.product.name: 20W000AMPB dmi.product.sku: LENOVO_MT_20W0_BU_Think_FM_ThinkPad T14 Gen 2i dmi.product.version: ThinkPad T14 Gen 2i dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: A0:E7:0B:23:70:E8 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:22183 acl:0 sco:0 events:3531 errors:0 TX bytes:821193 acl:0 sco:0 commands:3510 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2037906/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2037906] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/2037906/+attachment/5706602/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2037906 Title: [Intel AX201] Bluetooth LE not working after upgrade from 22.04 to 23.10 Status in bluez package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: syslog: 2023-09-20T09:32:54.138852+02:00 zaionc kernel: [ 13.539860] Bluetooth: hci0: Waiting for firmware download to complete 2023-09-20T09:32:54.138857+02:00 zaionc kernel: [ 13.540223] Bluetooth: hci0: Firmware loaded in 1706498 usecs 2023-09-20T09:32:54.138858+02:00 zaionc kernel: [ 13.540278] Bluetooth: hci0: Waiting for device to boot 2023-09-20T09:32:54.154894+02:00 zaionc kernel: [ 13.555430] Bluetooth: hci0: Malformed MSFT vendor event: 0x02 2023-09-20T09:32:54.154908+02:00 zaionc kernel: [ 13.555482] Bluetooth: hci0: Device booted in 14872 usecs 2023-09-20T09:32:54.154910+02:00 zaionc kernel: [ 13.555913] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-19-0-4.ddc 2023-09-20T09:32:54.158856+02:00 zaionc kernel: [ 13.558300] Bluetooth: hci0: Applying Intel DDC parameters completed 2023-09-20T09:32:54.158859+02:00 zaionc kernel: [ 13.559326] Bluetooth: hci0: Firmware revision 0.4 build 249 week 27 2023 lshw: *-usb:5 description: Bluetooth wireless interface product: AX201 Bluetooth vendor: Intel Corp. physical id: a bus info: usb@3:a version: 0.02 capabilities: bluetooth usb-2.01 configuration: driver=btusb maxpower=100mA speed=12Mbit/s root@zaionc:~# hcitool lescan Set scan parameters failed: Input/output error At first bluetooth stopped working at all due to Ubuntu bug = missing firmware. It was fixed recently and now the bluetooth module seems fine, but the whole BTLE part is not available. Particularly I cannot detect/pair Logitech M720 mouse. Platform: ThinkPad T14 Gen 2i --- ProblemType: Bug ApportVersion: 2.27.0-0ubuntu4 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.10 InstallationDate: Installed on 2022-05-28 (494 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) InterestingModules: rfcomm bnep btusb bluetooth MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']} Package: linux PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-5-generic root=UUID=d0002130-adf6-4f18-93b1-fda536d8b499 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 RebootRequiredPkgs: Error: path contained symlinks. Tags: mantic Uname: Linux 6.5.0-5-generic x86_64 UpgradeStatus: Upgraded to mantic on 2023-09-03 (30 days ago) UserGroups: adm cdrom dialout dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/10/2023 dmi.bios.release: 1.56 dmi.bios.vendor: LENOVO dmi.bios.version: N34ET56W (1.56 ) dmi.board.asset.tag: Not Available dmi.board.name: 20W000AMPB dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.42 dmi.modalias: dmi:bvnLENOVO:bvrN34ET56W(1.56):bd05/10/2023:br1.56:efr1.42:svnLENOVO:pn20W000AMPB:pvrThinkPadT14Gen2i:rvnLENOVO:rn20W000AMPB:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20W0_BU_Think_FM_ThinkPadT14Gen2i: dmi.product.family: ThinkPad T14 Gen 2i dmi.product.name: 20W000AMPB dmi.product.sku: LENOVO_MT_20W0_BU_Think_FM_ThinkPad T14 Gen 2i dmi.product.version: ThinkPad T14 Gen 2i dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: A0:E7:0B:23:70:E8 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:22183 acl:0 sco:0 events:3531 errors:0 TX bytes:821193 acl:0 sco:0 commands:3510 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2037906/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2037906] Re: [Intel AX201] Bluetooth LE not working after upgrade from 22.04 to 23.10
apport information ** Tags added: apport-collected ** Description changed: syslog: 2023-09-20T09:32:54.138852+02:00 zaionc kernel: [ 13.539860] Bluetooth: hci0: Waiting for firmware download to complete 2023-09-20T09:32:54.138857+02:00 zaionc kernel: [ 13.540223] Bluetooth: hci0: Firmware loaded in 1706498 usecs 2023-09-20T09:32:54.138858+02:00 zaionc kernel: [ 13.540278] Bluetooth: hci0: Waiting for device to boot 2023-09-20T09:32:54.154894+02:00 zaionc kernel: [ 13.555430] Bluetooth: hci0: Malformed MSFT vendor event: 0x02 2023-09-20T09:32:54.154908+02:00 zaionc kernel: [ 13.555482] Bluetooth: hci0: Device booted in 14872 usecs 2023-09-20T09:32:54.154910+02:00 zaionc kernel: [ 13.555913] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-19-0-4.ddc 2023-09-20T09:32:54.158856+02:00 zaionc kernel: [ 13.558300] Bluetooth: hci0: Applying Intel DDC parameters completed 2023-09-20T09:32:54.158859+02:00 zaionc kernel: [ 13.559326] Bluetooth: hci0: Firmware revision 0.4 build 249 week 27 2023 lshw: *-usb:5 description: Bluetooth wireless interface product: AX201 Bluetooth vendor: Intel Corp. physical id: a bus info: usb@3:a version: 0.02 capabilities: bluetooth usb-2.01 configuration: driver=btusb maxpower=100mA speed=12Mbit/s root@zaionc:~# hcitool lescan Set scan parameters failed: Input/output error At first bluetooth stopped working at all due to Ubuntu bug = missing firmware. It was fixed recently and now the bluetooth module seems fine, but the whole BTLE part is not available. Particularly I cannot detect/pair Logitech M720 mouse. Platform: ThinkPad T14 Gen 2i + --- + ProblemType: Bug + ApportVersion: 2.27.0-0ubuntu4 + Architecture: amd64 + CasperMD5CheckResult: pass + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 23.10 + InstallationDate: Installed on 2022-05-28 (494 days ago) + InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) + InterestingModules: rfcomm bnep btusb bluetooth + MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']} + Package: linux + PackageArchitecture: amd64 + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-5-generic root=UUID=d0002130-adf6-4f18-93b1-fda536d8b499 ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 + RebootRequiredPkgs: Error: path contained symlinks. + Tags: mantic + Uname: Linux 6.5.0-5-generic x86_64 + UpgradeStatus: Upgraded to mantic on 2023-09-03 (30 days ago) + UserGroups: adm cdrom dialout dip docker lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 05/10/2023 + dmi.bios.release: 1.56 + dmi.bios.vendor: LENOVO + dmi.bios.version: N34ET56W (1.56 ) + dmi.board.asset.tag: Not Available + dmi.board.name: 20W000AMPB + dmi.board.vendor: LENOVO + dmi.board.version: SDK0J40697 WIN + dmi.chassis.asset.tag: No Asset Information + dmi.chassis.type: 10 + dmi.chassis.vendor: LENOVO + dmi.chassis.version: None + dmi.ec.firmware.release: 1.42 + dmi.modalias: dmi:bvnLENOVO:bvrN34ET56W(1.56):bd05/10/2023:br1.56:efr1.42:svnLENOVO:pn20W000AMPB:pvrThinkPadT14Gen2i:rvnLENOVO:rn20W000AMPB:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20W0_BU_Think_FM_ThinkPadT14Gen2i: + dmi.product.family: ThinkPad T14 Gen 2i + dmi.product.name: 20W000AMPB + dmi.product.sku: LENOVO_MT_20W0_BU_Think_FM_ThinkPad T14 Gen 2i + dmi.product.version: ThinkPad T14 Gen 2i + dmi.sys.vendor: LENOVO + hciconfig: + hci0:Type: Primary Bus: USB + BD Address: A0:E7:0B:23:70:E8 ACL MTU: 1021:4 SCO MTU: 96:6 + UP RUNNING + RX bytes:22183 acl:0 sco:0 events:3531 errors:0 + TX bytes:821193 acl:0 sco:0 commands:3510 errors:0 ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/2037906/+attachment/5706601/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2037906 Title: [Intel AX201] Bluetooth LE not working after upgrade from 22.04 to 23.10 Status in bluez package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: syslog: 2023-09-20T09:32:54.138852+02:00 zaionc kernel: [ 13.539860] Bluetooth: hci0: Waiting for firmware download to complete 2023-09-20T09:32:54.138857+02:00 zaionc kernel: [ 13.540223] Bluetooth: hci0: Firmware loaded in 1706498 usecs 2023-09-20T09:32:54.138858+02:00 zaionc kernel: [ 13.540278] Bluetooth: hci0: Waiting for device to boot 2023-09-20T09:32:54.154894+02:00 zaionc kernel: [ 13.555430] Bluetooth: hci0: Malformed MSFT vendor event: 0x02 2023-09-20T09:32:54.154908+02:00 zaionc kernel: [ 13.555482] Bluetooth: hci0: Device booted in 14872 usecs
[Touch-packages] [Bug 2004477] Re: cryptography pkg 39.0.0 incompatible with pyOpenSSL 21.0.0 - crashes ensue
Do you have any ideas on how to solve your problem? I have exactly the same problem, that is related to HPLIP and ProtonVPN. In order to install the drivers for HPLIP (after upgrade the system to Kubuntu 22.04 LTS) it was necessary to reinstall python3 and upgrade pip and openssl to 22.1.0 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/2004477 Title: cryptography pkg 39.0.0 incompatible with pyOpenSSL 21.0.0 - crashes ensue Status in openssl package in Ubuntu: Invalid Bug description: crypto.py crashes when starting protonvpn: $ protonvpn-cli connect SE1 Tue Jan 31 07:08:04 AM EST 2023 Traceback (most recent call last): File "/usr/bin/protonvpn-cli", line 11, in load_entry_point('protonvpn-cli==3.13.0', 'console_scripts', 'protonvpn-cli')() File "/usr/lib/python3/dist-packages/protonvpn_cli/main.py", line 20, in main from .cli import ProtonVPNCLI File "/usr/lib/python3/dist-packages/protonvpn_cli/cli.py", line 4, in from proton.constants import VERSION as proton_version File "/usr/lib/python3/dist-packages/proton/__init__.py", line 1, in from .api import Session # noqa File "/usr/lib/python3/dist-packages/proton/api.py", line 21, in from .cert_pinning import TLSPinningAdapter File "/usr/lib/python3/dist-packages/proton/cert_pinning.py", line 5, in from OpenSSL import crypto File "/usr/lib/python3/dist-packages/OpenSSL/__init__.py", line 8, in from OpenSSL import crypto, SSL File "/usr/lib/python3/dist-packages/OpenSSL/crypto.py", line 3279, in _lib.OpenSSL_add_all_algorithms() AttributeError: module 'lib' has no attribute 'OpenSSL_add_all_algorithms' Tue Jan 31 07:08:05 AM EST 2023 c.f. https://askubuntu.com/questions/1450578/couldnt-launch-proton-vpn but downgrading openssl package is not desirable for security reasons. per https://github.com/pyca/cryptography/issues/7959 and other hits on search, cryptography package 39.0.0 is incompatible with pyOpenSSL 21.0.0; cryptography 38.0.4 works with 21.0.0; cryptography 39.0.0 requires 22.1.0 or greater. Installed packages are python3-cryptography 3.4.8-1ubuntu2 and 21.0.0-1 python3-openssl Currently, python3-openssl 22.1.0 is not available from repo. $ lsb_release -rd: Description: Ubuntu 22.04.1 LTS Release: 22.04 $ apt-cache policy python3-openssl python3-openssl: Installed: 21.0.0-1 Candidate: 21.0.0-1 Version table: *** 21.0.0-1 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu jammy/main i386 Packages 100 /var/lib/dpkg/status $ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/2004477/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1845046] Re: Bluetooth headphones default to low quality headset mode and fail to switch to A2DP when selected
The fix works for me! Thank you very much for fixing this bug, really appreciated! It appears that dependencies of the new Bluez packages are also compatible with Debian GNU/Linux. Since I use Debian, I confirm that installing fixed Ubuntu package on Debian 11 (testing right now) also fixes the problem. Thank you again for fixing this <3 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1845046 Title: Bluetooth headphones default to low quality headset mode and fail to switch to A2DP when selected Status in bluez package in Ubuntu: Fix Released Status in bluez source package in Bionic: Fix Released Status in bluez source package in Eoan: Fix Released Status in bluez source package in Focal: Fix Released Bug description: [Impact] Whenever I turn on my headphones they'll connect to my computer but I'm able to hear the input audio from my microphone and low quality output audio. I have to disconnect the headphones in the bluetooth devices and reconnect for it to fix the problem. [Test Case] 0. Set up your Bluetooth headphones with Ubuntu. 1. Turn off the headphones. 2. Turn on the headphones. 3. In Settings>Sound verify they have reconnected in A2DP mode (stereo, high quality, no microphone support). [Regression Potential] Low. Only the headset code path is affected and the fix has already been released for some time in BlueZ 5.51 onward. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1845046/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1769386] Re: Cable network does not get recognized anymore, wifi works
I think I have the same issue on my nettop using "Pegatron RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller". It doesn't work out of the box on neither Ubuntu Server (bionic) nor Arch, but I used to run Ubuntu Server on this hardware around a year ago without any problems. Someone else downgraded their kernel from 4.15 to 4.14 on Arch to solve this issue after updating, with identical hardware. I'm linking some pastes that were requested in the IRC channel. modinfo r8168 (I tried to fix things by installing r8168-dkms) > paste.ubuntu.com/p/2spYWX5t4k/ modinfo r8169 (I was asked to unload r8168 and load r1869) > https://paste.ubuntu.com/p/jg9rbKThWZ/ dhclient -v (it also takes 5 minutes to boot, until it times out) &> https://paste.ubuntu.com/p/D3JpycKrq3/ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1769386 Title: Cable network does not get recognized anymore, wifi works Status in network-manager package in Ubuntu: Confirmed Status in Arch Linux: New Bug description: ubuntu 16.04 LTS cable does not connect anymore, wifi working ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.6-0ubuntu0.16.04.2 ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-39-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 CurrentDesktop: Unity Date: Sat May 5 19:27:18 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-09-30 (217 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) IpRoute: default via 192.168.1.1 dev wlp3s0 proto static metric 600 169.254.0.0/16 dev wlp3s0 scope link metric 1000 192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.2 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICETYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH wlp3s0wifi connected /org/freedesktop/NetworkManager/Devices/1 WiFi-2.4-3569 7103236e-31c4-43d6-871d-14f3cda4b657 /org/freedesktop/NetworkManager/ActiveConnection/1 enp2s0f1 ethernet disconnected /org/freedesktop/NetworkManager/Devices/2 -- ---- loloopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.6connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1769386/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1769386] Re: Cable network does not get recognized anymore, wifi works
** Also affects: archlinux Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1769386 Title: Cable network does not get recognized anymore, wifi works Status in network-manager package in Ubuntu: Confirmed Status in Arch Linux: New Bug description: ubuntu 16.04 LTS cable does not connect anymore, wifi working ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.6-0ubuntu0.16.04.2 ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-39-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 CurrentDesktop: Unity Date: Sat May 5 19:27:18 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-09-30 (217 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) IpRoute: default via 192.168.1.1 dev wlp3s0 proto static metric 600 169.254.0.0/16 dev wlp3s0 scope link metric 1000 192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.2 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICETYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH wlp3s0wifi connected /org/freedesktop/NetworkManager/Devices/1 WiFi-2.4-3569 7103236e-31c4-43d6-871d-14f3cda4b657 /org/freedesktop/NetworkManager/ActiveConnection/1 enp2s0f1 ethernet disconnected /org/freedesktop/NetworkManager/Devices/2 -- ---- loloopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.6connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1769386/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1553685] Re: Lenovo Y700-17ISK subwoofer doesn't work
Doesn't work on my Lenovo Y700-15ISK on Ubuntu 17.10. Please help us :( -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1553685 Title: Lenovo Y700-17ISK subwoofer doesn't work Status in alsa-driver package in Ubuntu: Confirmed Bug description: Lenovo Y700-17ISK (Intel Core i7-6700HQ/RAM 16GB/SSD 512GB/Nvidia GTX960M 4GB) Operating system: Ubuntu 16.04 (xenial-desktop-amd64.iso 04-Mar-2016, kernel 4.4.0-10-generic, nvidia 361.28) Problem: Notebook subwoofer doesn't work. Judging from alsa-info.sh output, there is no pin declared for the bass output by BIOS. Please find a zip file attached: 'alsa-info_hdajackretask-unconnected-pins' ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-10-generic 4.4.0-10.25 ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3 Uname: Linux 4.4.0-10-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aljosa 1776 F pulseaudio CurrentDesktop: Unity Date: Sun Mar 6 11:02:21 2016 HibernationDevice: RESUME=UUID=ac022671-63df-40ae-bffe-66fff3b35125 InstallationDate: Installed on 2016-03-05 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160304) MachineType: LENOVO 80Q0 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-10-generic.efi.signed root=UUID=aa4325c4-4b4c-4372-b8ca-a66c3e5b2aa6 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-10-generic N/A linux-backports-modules-4.4.0-10-generic N/A linux-firmware1.156 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/31/2016 dmi.bios.vendor: LENOVO dmi.bios.version: CDCN30WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Allsparks 7A dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad Y700-17ISK dmi.modalias: dmi:bvnLENOVO:bvrCDCN30WW:bd01/31/2016:svnLENOVO:pn80Q0:pvrLenovoideapadY700-17ISK:rvnLENOVO:rnAllsparks7A:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapadY700-17ISK: dmi.product.name: 80Q0 dmi.product.version: Lenovo ideapad Y700-17ISK dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1553685/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1659684] Re: Leftover mount in /etc/mtab pointing to /var/lib/ureadahead/debugfs/tracing after some runs of apt dist-upgrade followed by a reboot
Since it seems this bug manifests itself only after certain 'apt upgrade' runs that call ureadahead triggers, would backporting the fix from Vivid ureadahead package ver. 0.100.0-19 be an option to resolve it? I'm thinking of the fix for https://bugs.launchpad.net/ubuntu/+source/ureadahead/+bug/777224 and the non-systemd change done to http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/vivid/ureadahead/vivid/revision/32#debian/rules -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ureadahead in Ubuntu. https://bugs.launchpad.net/bugs/1659684 Title: Leftover mount in /etc/mtab pointing to /var/lib/ureadahead/debugfs/tracing after some runs of apt dist- upgrade followed by a reboot Status in ureadahead package in Ubuntu: Confirmed Bug description: After a patching and a reboot cycle (possibly only the ones that involve running ureadahead triggers) a leftover mount entry is present in /etc/mtab pointing to /var/lib/ureadahead/debugfs/tracing root@localhost:~$ mount /dev/mapper/sysvg-root on / type ext4 (rw,errors=remount-ro) proc on /proc type proc (rw,noexec,nosuid,nodev) sysfs on /sys type sysfs (rw,noexec,nosuid,nodev) none on /sys/fs/cgroup type tmpfs (rw) none on /sys/fs/fuse/connections type fusectl (rw) none on /sys/kernel/debug type debugfs (rw) none on /sys/kernel/security type securityfs (rw) udev on /dev type devtmpfs (rw,mode=0755) devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=0620) tmpfs on /run type tmpfs (rw,noexec,nosuid,size=10%,mode=0755) none on /run/lock type tmpfs (rw,noexec,nosuid,nodev,size=5242880) none on /run/shm type tmpfs (rw,nosuid,nodev) none on /run/user type tmpfs (rw,noexec,nosuid,nodev,size=104857600,mode=0755) none on /sys/fs/pstore type pstore (rw) tracefs on /var/lib/ureadahead/debugfs/tracing type tracefs (rw,relatime) /dev/sda1 on /boot type ext4 (rw) systemd on /sys/fs/cgroup/systemd type cgroup (rw,noexec,nosuid,nodev,none,name=systemd) root@localhost:~$ mount | grep tracefs tracefs on /var/lib/ureadahead/debugfs/tracing type tracefs (rw,relatime) But that mount point doesn't exist root@localhost:~$ ls -lha /var/lib/ureadahead/debugfs/ total 8.0K drwxr-xr-x 2 root root 4.0K Jan 27 11:36 . drwxr-xr-x 3 root root 4.0K Jan 27 11:16 .. That mtab entry can be removed by running 'umount /var/lib/ureadahead/debugfs/tracing', but only after creating that mount point first root@localhost:~$ mkdir /var/lib/ureadahead/debugfs/tracing root@localhost:~$ ls -lh /var/lib/ureadahead/debugfs/ total 4.0K drwxr-xr-x 2 root root 4.0K Jan 27 11:28 tracing root@localhost:~$ umount /var/lib/ureadahead/debugfs/tracing umount: /var/lib/ureadahead/debugfs/tracing: not mounted root@localhost:~$ mount | grep tracefs root@localhost:~$ mount /dev/mapper/sysvg-root on / type ext4 (rw,errors=remount-ro) proc on /proc type proc (rw,noexec,nosuid,nodev) sysfs on /sys type sysfs (rw,noexec,nosuid,nodev) none on /sys/fs/cgroup type tmpfs (rw) none on /sys/fs/fuse/connections type fusectl (rw) none on /sys/kernel/debug type debugfs (rw) none on /sys/kernel/security type securityfs (rw) udev on /dev type devtmpfs (rw,mode=0755) devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=0620) tmpfs on /run type tmpfs (rw,noexec,nosuid,size=10%,mode=0755) none on /run/lock type tmpfs (rw,noexec,nosuid,nodev,size=5242880) none on /run/shm type tmpfs (rw,nosuid,nodev) none on /run/user type tmpfs (rw,noexec,nosuid,nodev,size=104857600,mode=0755) none on /sys/fs/pstore type pstore (rw) /dev/sda1 on /boot type ext4 (rw) systemd on /sys/fs/cgroup/systemd type cgroup (rw,noexec,nosuid,nodev,none,name=systemd) I'm experiencing this on several Ubuntu 14.04 servers, running on a VMware cluster. Package versions worth noting are: ureadahead 0.100.0-16 linux-image-4.4.0-59-generic4.4.0-59.80~14.04.1 open-vm-tools 2:9.4.0-1280544-5ubuntu6.2 This also causes #1516451 and may be related to #499773 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ureadahead/+bug/1659684/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1671663] [NEW] Error next
Public bug reported: next error infect iso ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-42.45-generic 4.8.17 Uname: Linux 4.8.0-42-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl nvidia_uvm wl nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 367.57 Mon Oct 3 20:37:01 PDT 2016 GCC version: gcc version 6.2.0 20161005 (Ubuntu 6.2.0-5ubuntu12) .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Fri Mar 10 01:45:56 2017 DistUpgraded: Fresh install DistroCodename: yakkety DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.8.0-42-generic, x86_64: installed bcmwl, 6.30.223.248+bdcom, 4.8.0-42-generic, x86_64: installed nvidia-367, 367.57, 4.8.0-42-generic, x86_64: installed GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:5001] NVIDIA Corporation GF108M [GeForce GT 630M] [10de:0de9] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo GF108M [GeForce GT 630M] [17aa:5001] InstallationDate: Installed on 2017-03-08 (1 days ago) InstallationMedia: Ubuntu-Kylin 16.10 "Yakkety Yak" - Release amd64 (20161012.3) MachineType: LENOVO 32593TG ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-42-generic root=UUID=635cf8fd-f7ab-4a83-b9aa-2221195e9279 ro locale=zh_CN quiet splash crashkernel=384M-:128M vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/08/2012 dmi.bios.vendor: LENOVO dmi.bios.version: H0ET30WW (1.12 ) dmi.board.asset.tag: Not Available dmi.board.name: 32593TG 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:bvrH0ET30WW(1.12):bd05/08/2012:svnLENOVO:pn32593TG:pvrThinkPadEdgeE530:rvnLENOVO:rn32593TG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 32593TG dmi.product.version: ThinkPad Edge E530 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.10.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.10.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2 xserver.bootTime: Fri Mar 10 01:23:55 2017 xserver.configfile: /etc/X11/xorg.conf xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-1ubuntu6.1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 third-party-packages ubuntu uec-images yakkety -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1671663 Title: Error next Status in xorg package in Ubuntu: New Bug description: next error infect iso ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-42.45-generic 4.8.17 Uname: Linux 4.8.0-42-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl nvidia_uvm wl nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 367.57 Mon Oct 3 20:37:01 PDT 2016 GCC version: gcc version 6.2.0 20161005 (Ubuntu 6.2.0-5ubuntu12) .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
[Touch-packages] [Bug 1671209] [NEW] Error
Public bug reported: Error language in Ubuntu. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-41.44-generic 4.8.17 Uname: Linux 4.8.0-41-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 367.57 Mon Oct 3 20:37:01 PDT 2016 GCC version: gcc version 6.2.0 20161005 (Ubuntu 6.2.0-5ubuntu12) .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Wed Mar 8 20:19:35 2017 DistUpgraded: Fresh install DistroCodename: yakkety DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.8.0-41-generic, x86_64: installed nvidia-367, 367.57, 4.8.0-41-generic, x86_64: installed GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:5001] NVIDIA Corporation GF108M [GeForce GT 630M] [10de:0de9] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo GF108M [GeForce GT 630M] [17aa:5001] InstallationDate: Installed on 2017-03-08 (0 days ago) InstallationMedia: Ubuntu-Kylin 16.10 "Yakkety Yak" - Release amd64 (20161012.3) MachineType: LENOVO 32593TG ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-41-generic root=UUID=635cf8fd-f7ab-4a83-b9aa-2221195e9279 ro locale=zh_CN quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/08/2012 dmi.bios.vendor: LENOVO dmi.bios.version: H0ET30WW (1.12 ) dmi.board.asset.tag: Not Available dmi.board.name: 32593TG 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:bvrH0ET30WW(1.12):bd05/08/2012:svnLENOVO:pn32593TG:pvrThinkPadEdgeE530:rvnLENOVO:rn32593TG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 32593TG dmi.product.version: ThinkPad Edge E530 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.10.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.10.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2 xserver.bootTime: Wed Mar 8 20:00:42 2017 xserver.configfile: /etc/X11/xorg.conf xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-1ubuntu6.1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu yakkety -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1671209 Title: Error Status in xorg package in Ubuntu: New Bug description: Error language in Ubuntu. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-41.44-generic 4.8.17 Uname: Linux 4.8.0-41-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 367.57 Mon Oct 3 20:37:01 PDT 2016 GCC version: gcc version 6.2.0 20161005 (Ubuntu 6.2.0-5ubuntu12) .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Wed Mar 8 20:19:35 2017 DistUpgraded: Fresh install DistroCodename: yakkety DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.8.0-41-generic, x86_64: installed nvidia-367, 367.57, 4.8.0-41-generic, x86_64: installed GraphicsCard: Intel
[Touch-packages] [Bug 1670051] [NEW] Errors
Public bug reported: Error in grafic, aplication end VPN. I need hellp. I need aktualization. Ubuntu Kylin 16.10 32 bit ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-39.42-generic 4.8.17 Uname: Linux 4.8.0-39-generic i686 NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Jest katalogiem: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86 Kernel Module 367.57 Mon Oct 3 19:34:43 PDT 2016 GCC version: gcc version 6.2.0 20161005 (Ubuntu 6.2.0-5ubuntu12) .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu8.2 Architecture: i386 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sat Mar 4 22:03:09 2017 DistUpgraded: Fresh install DistroCodename: yakkety DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.8.0-39-generic, i686: installed nvidia-367, 367.57, 4.8.0-39-generic, i686: installed GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:5001] NVIDIA Corporation GF108M [GeForce GT 630M] [10de:0de9] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo GF108M [GeForce GT 630M] [17aa:5001] InstallationDate: Installed on 2017-03-01 (3 days ago) InstallationMedia: Ubuntu-Kylin 16.10 "Yakkety Yak" - Release i386 (20161012.3) MachineType: LENOVO 32593TG ProcEnviron: LANGUAGE=pl PATH=(custom, no user) LANG=pl_PL.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-39-generic root=UUID=722bc970-9eb7-4fe3-8cf0-a1848855717d ro locale=zh_CN quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/08/2012 dmi.bios.vendor: LENOVO dmi.bios.version: H0ET30WW (1.12 ) dmi.board.asset.tag: Not Available dmi.board.name: 32593TG 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:bvrH0ET30WW(1.12):bd05/08/2012:svnLENOVO:pn32593TG:pvrThinkPadEdgeE530:rvnLENOVO:rn32593TG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 32593TG dmi.product.version: ThinkPad Edge E530 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2 version.libdrm2: libdrm2 2.4.70-1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.10.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2 xserver.bootTime: Sat Mar 4 17:42:43 2017 xserver.configfile: /etc/X11/xorg.conf xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-1ubuntu6 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug compiz-0.9 i386 ubuntu yakkety -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1670051 Title: Errors Status in xorg package in Ubuntu: New Bug description: Error in grafic, aplication end VPN. I need hellp. I need aktualization. Ubuntu Kylin 16.10 32 bit ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-39.42-generic 4.8.17 Uname: Linux 4.8.0-39-generic i686 NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Jest katalogiem: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86 Kernel Module 367.57 Mon Oct 3 19:34:43 PDT 2016 GCC version: gcc version 6.2.0 20161005 (Ubuntu 6.2.0-5ubuntu12) .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu8.2 Architecture: i386 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sat Mar 4 22:03:09 2017 DistUpgraded: Fresh install DistroCodename: yakkety
[Touch-packages] [Bug 499773] Re: Race with ureadahead can mean that /var/lib/ureadahead/debugfs appears in /etc/mtab
For me it's the mtab entry for tracefs on a non-existing mount point in /var/lib/ureadahead/debugfs/tracing that is causing problems. It does affect VMware snapshots when quiescing is required too. Since it's a different entry then in this post I opened a new bug report in #1659684 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mountall in Ubuntu. https://bugs.launchpad.net/bugs/499773 Title: Race with ureadahead can mean that /var/lib/ureadahead/debugfs appears in /etc/mtab Status in mountall package in Ubuntu: Triaged Bug description: When the system is booted, the mountall process may notice a temporarily-mounted file system at /var/lib/ureadahead/debugfs and record that fact in /etc/mtab. Later in the boot process, this file system is unmounted, but mountall doesn't record unmounts, so it never "forgets" this path when it's unmounted. Mountall should if necessary remove this mount from mtab. To confirm on your system that it is indeed not really mounted, look for it in /proc/self/mountinfo Otherwise this may be due to a crash of the ureadahead process during boot. original report Binary package hint: ureadahead $ mount /dev/sda1 on / type ext3 (rw,relatime,errors=remount-ro) proc on /proc type proc (rw) none on /sys type sysfs (rw,noexec,nosuid,nodev) none on /sys/fs/fuse/connections type fusectl (rw) none on /sys/kernel/debug type debugfs (rw) none on /sys/kernel/security type securityfs (rw) udev on /dev type tmpfs (rw,mode=0755) none on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=0620) none on /dev/shm type tmpfs (rw,nosuid,nodev) none on /var/run type tmpfs (rw,nosuid,mode=0755) none on /var/lock type tmpfs (rw,noexec,nosuid,nodev) none on /lib/init/rw type tmpfs (rw,nosuid,mode=0755) none on /var/lib/ureadahead/debugfs type debugfs (rw) /dev/sda6 on /home type ext4 (rw,relatime) binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,noexec,nosuid,nodev) gvfs-fuse-daemon on /home/hildeb/.gvfs type fuse.gvfs-fuse-daemon (rw,nosuid,nodev,user=hildeb) /var/lib/ureadahead/debugfs is left lingering around. It's use is somewhat limited, since most Ubuntu users are not kernel developers -- if it's used as intended: http://kerneltrap.org/node/4394 ProblemType: Bug Architecture: amd64 Date: Wed Dec 23 11:04:11 2009 DistroRelease: Ubuntu 9.10 NonfreeKernelModules: nvidia Package: ureadahead 0.90.3-2 ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-17.54-generic SourcePackage: ureadahead Uname: Linux 2.6.31-17-generic x86_64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/499773/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1659684] Re: Leftover mount in /etc/mtab pointing to /var/lib/ureadahead/debugfs/tracing after some runs of apt dist-upgrade followed by a reboot
Just to note, 'mountall' also clears that mtab entry, but it also nukes contents of /tmp in the process, which might not be good if someone is running Passenger, which apparently keeps socket files in there (i.e. /tmp/passenger.1.0.xxx/generation-0/request ) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ureadahead in Ubuntu. https://bugs.launchpad.net/bugs/1659684 Title: Leftover mount in /etc/mtab pointing to /var/lib/ureadahead/debugfs/tracing after some runs of apt dist- upgrade followed by a reboot Status in ureadahead package in Ubuntu: New Bug description: After a patching and a reboot cycle (possibly only the ones that involve running ureadahead triggers) a leftover mount entry is present in /etc/mtab pointing to /var/lib/ureadahead/debugfs/tracing root@localhost:~$ mount /dev/mapper/sysvg-root on / type ext4 (rw,errors=remount-ro) proc on /proc type proc (rw,noexec,nosuid,nodev) sysfs on /sys type sysfs (rw,noexec,nosuid,nodev) none on /sys/fs/cgroup type tmpfs (rw) none on /sys/fs/fuse/connections type fusectl (rw) none on /sys/kernel/debug type debugfs (rw) none on /sys/kernel/security type securityfs (rw) udev on /dev type devtmpfs (rw,mode=0755) devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=0620) tmpfs on /run type tmpfs (rw,noexec,nosuid,size=10%,mode=0755) none on /run/lock type tmpfs (rw,noexec,nosuid,nodev,size=5242880) none on /run/shm type tmpfs (rw,nosuid,nodev) none on /run/user type tmpfs (rw,noexec,nosuid,nodev,size=104857600,mode=0755) none on /sys/fs/pstore type pstore (rw) tracefs on /var/lib/ureadahead/debugfs/tracing type tracefs (rw,relatime) /dev/sda1 on /boot type ext4 (rw) systemd on /sys/fs/cgroup/systemd type cgroup (rw,noexec,nosuid,nodev,none,name=systemd) root@localhost:~$ mount | grep tracefs tracefs on /var/lib/ureadahead/debugfs/tracing type tracefs (rw,relatime) But that mount point doesn't exist root@localhost:~$ ls -lha /var/lib/ureadahead/debugfs/ total 8.0K drwxr-xr-x 2 root root 4.0K Jan 27 11:36 . drwxr-xr-x 3 root root 4.0K Jan 27 11:16 .. That mtab entry can be removed by running 'umount /var/lib/ureadahead/debugfs/tracing', but only after creating that mount point first root@localhost:~$ mkdir /var/lib/ureadahead/debugfs/tracing root@localhost:~$ ls -lh /var/lib/ureadahead/debugfs/ total 4.0K drwxr-xr-x 2 root root 4.0K Jan 27 11:28 tracing root@localhost:~$ umount /var/lib/ureadahead/debugfs/tracing umount: /var/lib/ureadahead/debugfs/tracing: not mounted root@localhost:~$ mount | grep tracefs root@localhost:~$ mount /dev/mapper/sysvg-root on / type ext4 (rw,errors=remount-ro) proc on /proc type proc (rw,noexec,nosuid,nodev) sysfs on /sys type sysfs (rw,noexec,nosuid,nodev) none on /sys/fs/cgroup type tmpfs (rw) none on /sys/fs/fuse/connections type fusectl (rw) none on /sys/kernel/debug type debugfs (rw) none on /sys/kernel/security type securityfs (rw) udev on /dev type devtmpfs (rw,mode=0755) devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=0620) tmpfs on /run type tmpfs (rw,noexec,nosuid,size=10%,mode=0755) none on /run/lock type tmpfs (rw,noexec,nosuid,nodev,size=5242880) none on /run/shm type tmpfs (rw,nosuid,nodev) none on /run/user type tmpfs (rw,noexec,nosuid,nodev,size=104857600,mode=0755) none on /sys/fs/pstore type pstore (rw) /dev/sda1 on /boot type ext4 (rw) systemd on /sys/fs/cgroup/systemd type cgroup (rw,noexec,nosuid,nodev,none,name=systemd) I'm experiencing this on several Ubuntu 14.04 servers, running on a VMware cluster. Package versions worth noting are: ureadahead 0.100.0-16 linux-image-4.4.0-59-generic4.4.0-59.80~14.04.1 open-vm-tools 2:9.4.0-1280544-5ubuntu6.2 This also causes #1516451 and may be related to #499773 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ureadahead/+bug/1659684/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1659684] [NEW] Leftover mount in /etc/mtab pointing to /var/lib/ureadahead/debugfs/tracing after some runs of apt dist-upgrade followed by a reboot
Public bug reported: After a patching and a reboot cycle (possibly only the ones that involve running ureadahead triggers) a leftover mount entry is present in /etc/mtab pointing to /var/lib/ureadahead/debugfs/tracing root@localhost:~$ mount /dev/mapper/sysvg-root on / type ext4 (rw,errors=remount-ro) proc on /proc type proc (rw,noexec,nosuid,nodev) sysfs on /sys type sysfs (rw,noexec,nosuid,nodev) none on /sys/fs/cgroup type tmpfs (rw) none on /sys/fs/fuse/connections type fusectl (rw) none on /sys/kernel/debug type debugfs (rw) none on /sys/kernel/security type securityfs (rw) udev on /dev type devtmpfs (rw,mode=0755) devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=0620) tmpfs on /run type tmpfs (rw,noexec,nosuid,size=10%,mode=0755) none on /run/lock type tmpfs (rw,noexec,nosuid,nodev,size=5242880) none on /run/shm type tmpfs (rw,nosuid,nodev) none on /run/user type tmpfs (rw,noexec,nosuid,nodev,size=104857600,mode=0755) none on /sys/fs/pstore type pstore (rw) tracefs on /var/lib/ureadahead/debugfs/tracing type tracefs (rw,relatime) /dev/sda1 on /boot type ext4 (rw) systemd on /sys/fs/cgroup/systemd type cgroup (rw,noexec,nosuid,nodev,none,name=systemd) root@localhost:~$ mount | grep tracefs tracefs on /var/lib/ureadahead/debugfs/tracing type tracefs (rw,relatime) But that mount point doesn't exist root@localhost:~$ ls -lha /var/lib/ureadahead/debugfs/ total 8.0K drwxr-xr-x 2 root root 4.0K Jan 27 11:36 . drwxr-xr-x 3 root root 4.0K Jan 27 11:16 .. That mtab entry can be removed by running 'umount /var/lib/ureadahead/debugfs/tracing', but only after creating that mount point first root@localhost:~$ mkdir /var/lib/ureadahead/debugfs/tracing root@localhost:~$ ls -lh /var/lib/ureadahead/debugfs/ total 4.0K drwxr-xr-x 2 root root 4.0K Jan 27 11:28 tracing root@localhost:~$ umount /var/lib/ureadahead/debugfs/tracing umount: /var/lib/ureadahead/debugfs/tracing: not mounted root@localhost:~$ mount | grep tracefs root@localhost:~$ mount /dev/mapper/sysvg-root on / type ext4 (rw,errors=remount-ro) proc on /proc type proc (rw,noexec,nosuid,nodev) sysfs on /sys type sysfs (rw,noexec,nosuid,nodev) none on /sys/fs/cgroup type tmpfs (rw) none on /sys/fs/fuse/connections type fusectl (rw) none on /sys/kernel/debug type debugfs (rw) none on /sys/kernel/security type securityfs (rw) udev on /dev type devtmpfs (rw,mode=0755) devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=0620) tmpfs on /run type tmpfs (rw,noexec,nosuid,size=10%,mode=0755) none on /run/lock type tmpfs (rw,noexec,nosuid,nodev,size=5242880) none on /run/shm type tmpfs (rw,nosuid,nodev) none on /run/user type tmpfs (rw,noexec,nosuid,nodev,size=104857600,mode=0755) none on /sys/fs/pstore type pstore (rw) /dev/sda1 on /boot type ext4 (rw) systemd on /sys/fs/cgroup/systemd type cgroup (rw,noexec,nosuid,nodev,none,name=systemd) I'm experiencing this on several Ubuntu 14.04 servers, running on a VMware cluster. Package versions worth noting are: ureadahead 0.100.0-16 linux-image-4.4.0-59-generic4.4.0-59.80~14.04.1 open-vm-tools 2:9.4.0-1280544-5ubuntu6.2 This also causes #1516451 and may be related to #499773 ** Affects: ureadahead (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ureadahead in Ubuntu. https://bugs.launchpad.net/bugs/1659684 Title: Leftover mount in /etc/mtab pointing to /var/lib/ureadahead/debugfs/tracing after some runs of apt dist- upgrade followed by a reboot Status in ureadahead package in Ubuntu: New Bug description: After a patching and a reboot cycle (possibly only the ones that involve running ureadahead triggers) a leftover mount entry is present in /etc/mtab pointing to /var/lib/ureadahead/debugfs/tracing root@localhost:~$ mount /dev/mapper/sysvg-root on / type ext4 (rw,errors=remount-ro) proc on /proc type proc (rw,noexec,nosuid,nodev) sysfs on /sys type sysfs (rw,noexec,nosuid,nodev) none on /sys/fs/cgroup type tmpfs (rw) none on /sys/fs/fuse/connections type fusectl (rw) none on /sys/kernel/debug type debugfs (rw) none on /sys/kernel/security type securityfs (rw) udev on /dev type devtmpfs (rw,mode=0755) devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=0620) tmpfs on /run type tmpfs (rw,noexec,nosuid,size=10%,mode=0755) none on /run/lock type tmpfs (rw,noexec,nosuid,nodev,size=5242880) none on /run/shm type tmpfs (rw,nosuid,nodev) none on /run/user type tmpfs (rw,noexec,nosuid,nodev,size=104857600,mode=0755) none on /sys/fs/pstore type pstore (rw) tracefs on /var/lib/ureadahead/debugfs/tracing type tracefs (rw,relatime) /dev/sda1 on /boot type ext4 (rw) systemd on /sys/fs/cgroup/systemd type cgroup
[Touch-packages] [Bug 1583861] Re: Keyboard backlight isn't properly restored after idle on systems with hardwired configuration
Hi all, I've got Dell Latitude E7470: #uname -a Linux E7470 4.4.0-31-generic #50-Ubuntu SMP Wed Jul 13 00:07:12 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux #dpkg -s upower | grep -i 'status\|version' Status: install ok installed Version: 0.99.4-2ubuntu0.3 #dpkg -s unity-settings-daemon | grep -i 'status\|version' Status: install ok installed Version: 15.04.1+16.04.20160701-0ubuntu1 My Keyboard lights all time (doesn't time-out). I can disable it by FN+F10, but it will light again after boot/resume/unlock-weak-up. When I boot to BIOS all is OK. It time-outs after 10 seconds. Should I perform any additional steps (i.e. packages reconfiguration) ? Regards Grzesiek -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1583861 Title: Keyboard backlight isn't properly restored after idle on systems with hardwired configuration Status in Dell Sputnik: New Status in Upower: Unknown Status in gnome-settings-daemon package in Ubuntu: Confirmed Status in unity-settings-daemon package in Ubuntu: Fix Released Status in upower package in Ubuntu: Fix Released Status in gnome-settings-daemon source package in Xenial: Confirmed Status in unity-settings-daemon source package in Xenial: Fix Released Status in upower source package in Xenial: Fix Committed Bug description: In Dell or ThinkPad (for these you need a kernel which includes fix for lp:1574498) notebooks with keyboard backlight, the keybindings to control the keyboard backlight don't emit any event to the userland, about the state change, nor they request userland to change it (as it happens in other models which emits KEY_KBDILLUM{UP,DOWN,TOGGLE} events), this causes unity/gnome-settings daemon not to restore the proper backlight after idle. Steps to reproduce: 0) ensure your keyboard backlight is on, and gdbus call --system --dest org.freedesktop.UPower \ --object-path /org/freedesktop/UPower/KbdBacklight \ --method org.freedesktop.UPower.KbdBacklight.GetBrightness returns a value != from 0. If not, just call the SetBrightness method with a positive value, to turn on the backlight. Now turn off the keyboard backlight (or set it to another level) using the laptop keys, and run: gsettings set org.gnome.desktop.session idle-delay 1 to make things easier to test. 2) Wait one second and the screensaver should start. Wait the screen to be turned off. If you just changed the brightness level at the step above, once the screen is turned off, also the keyboard backlight should be turned off too. 3) Now press a key or move the mouse. Expected behavior: 4) The keyboard backlight should be set back to the previous level (so it should stay off or go back to the level you set before the idle timeout happened). Actual behavior: 5) The backlight is set to the level it had at point 0). To reset the idle-delay, just call gsettings reset org.gnome.desktop.session idle-delay To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1583861/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1556493] [NEW] package perl-modules 5.20.2-6ubuntu0.2 failed to install/upgrade: package perl-modules is already installed and configured
*** This bug is a duplicate of bug 1556491 *** https://bugs.launchpad.net/bugs/1556491 Public bug reported: This is a stacionary computer, bug report when i try upgrade system ProblemType: Package DistroRelease: Ubuntu 15.10 Package: perl-modules 5.20.2-6ubuntu0.2 ProcVersionSignature: Ubuntu 4.2.0-30.36-generic 4.2.8-ckt3 Uname: Linux 4.2.0-30-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 AptdaemonVersion: 1.1.1+bzr982-0ubuntu14 Architecture: amd64 Date: Sat Mar 12 19:51:24 2016 DuplicateSignature: package:perl-modules:5.20.2-6ubuntu0.2:package perl-modules is already installed and configured ErrorMessage: package perl-modules is already installed and configured InstallationDate: Installed on 2015-11-01 (132 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.2ubuntu5.1 apt 1.0.10.2ubuntu1 SourcePackage: perl Title: package perl-modules 5.20.2-6ubuntu0.2 failed to install/upgrade: package perl-modules is already installed and configured UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: perl (Ubuntu) Importance: Undecided Status: New ** Tags: already-installed amd64 apport-package wily -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to perl in Ubuntu. https://bugs.launchpad.net/bugs/1556493 Title: package perl-modules 5.20.2-6ubuntu0.2 failed to install/upgrade: package perl-modules is already installed and configured Status in perl package in Ubuntu: New Bug description: This is a stacionary computer, bug report when i try upgrade system ProblemType: Package DistroRelease: Ubuntu 15.10 Package: perl-modules 5.20.2-6ubuntu0.2 ProcVersionSignature: Ubuntu 4.2.0-30.36-generic 4.2.8-ckt3 Uname: Linux 4.2.0-30-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 AptdaemonVersion: 1.1.1+bzr982-0ubuntu14 Architecture: amd64 Date: Sat Mar 12 19:51:24 2016 DuplicateSignature: package:perl-modules:5.20.2-6ubuntu0.2:package perl-modules is already installed and configured ErrorMessage: package perl-modules is already installed and configured InstallationDate: Installed on 2015-11-01 (132 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.2ubuntu5.1 apt 1.0.10.2ubuntu1 SourcePackage: perl Title: package perl-modules 5.20.2-6ubuntu0.2 failed to install/upgrade: package perl-modules is already installed and configured UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/perl/+bug/1556493/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1449282] Re: xserver-allow-tcp=true feature doesn't work with Xorg version 1.17.0
I was wondering if this fix will also be applied to LTS Enablement Stacks on Trusty? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1449282 Title: xserver-allow-tcp=true feature doesn't work with Xorg version 1.17.0 Status in Light Display Manager: Fix Released Status in Light Display Manager 1.10 series: Fix Committed Status in Light Display Manager 1.14 series: Fix Released Status in Light Display Manager 1.16 series: Fix Released Status in Light Display Manager 1.2 series: Won't Fix Status in lightdm package in Ubuntu: Fix Released Status in lightdm source package in Vivid: Fix Committed Status in lightdm source package in Wily: Fix Released Bug description: [Impact] xserver-allow-tcp=true option no longer works with X.org 1.17. [Test Case] 1. Edit /etc/lightdm/lightdm.conf and set [SeatDefaults] xserver-allow-tcp=true 2. Start LightDM 3. Attempt to connect to the X server using TCP Expected result: Able to connect Observed result: Unable to connect [Regression potential] Low. X.org changed their default behaviour from listen by default to listen if "-listen tcp" is passed as a command line flag. This is just the equivalent change in LightDM. Since this is a new flag to X.org if a user was to use another X server there is a risk it would not understand that flag. However it seems unlikely since X.org is the only actively developed X server. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1449282/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1424059] Re: libosmesa6 conflicts with libglapi-mesa-lts-utopic
I just run into this bug.It also is present with vivid version of LTS enablement stack. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1424059 Title: libosmesa6 conflicts with libglapi-mesa-lts-utopic Status in mesa package in Ubuntu: Confirmed Status in mesa-lts-utopic package in Ubuntu: Confirmed Bug description: [Description] libosmesa6 10.1.3-0ubuntu0.3 amd64 can't be installed because it depends on libglapi-mesa (= 10.1.3-0ubuntu0.3), but libglapi-mesa-lts-utopic 10.3.2-0ubuntu1~trusty2 amd64 is '10.3.2-0ubuntu1' not '10.1.3-0ubuntu0.3'. [Test Case] sudo aptitude install libosmesa6 The following NEW packages will be installed: libglapi-mesa{a} libosmesa6 0 packages upgraded, 2 newly installed, 0 to remove and 0 not upgraded. Need to get 1,009 kB of archives. After unpacking 3,682 kB will be used. The following packages have unmet dependencies: xserver-xorg-lts-utopic : Conflicts: libglapi-mesa (= 0~) but 10.1.3-0ubuntu0.3 is to be installed. libglapi-mesa-lts-utopic : Conflicts: libglapi-mesa but 10.1.3-0ubuntu0.3 is to be installed. [Possible solution] Include utopic's libosmesa(-dev) in the LTS enablement stack, so versions match. [Reverse dependencies] libosmesa6-dev desmume crossover wine recommends libosmesa6 ... ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libglapi-mesa-lts-utopic 10.3.2-0ubuntu1~trusty2 ProcVersionSignature: Ubuntu 3.16.0-31.41~14.04.1-generic 3.16.7-ckt5 Uname: Linux 3.16.0-31-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 CurrentDesktop: Unity Date: Fri Feb 20 15:45:52 2015 Dependencies: gcc-4.9-base 4.9.1-0ubuntu1 libc6 2.19-0ubuntu6.5 libgcc1 1:4.9.1-0ubuntu1 multiarch-support 2.19-0ubuntu6.5 InstallationDate: Installed on 2015-02-08 (12 days ago) InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 (20150203.2) SourcePackage: mesa-lts-utopic UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1424059/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1400626] Re: Please backport xtrans, libdrm, x11proto-{fonts, core} packages for 14.04.2
@16 Hi Timo, Try: sudo apt-get install libgl1-mesa-glx-lts-utopic xserver-xorg-lts-utopic xserver-xorg-core-lts-utopic Reagards -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1400626 Title: Please backport xtrans, libdrm, x11proto-{fonts,core} packages for 14.04.2 Status in libdrm package in Ubuntu: In Progress Status in llvm-toolchain-snapshot package in Ubuntu: Invalid Status in x11proto-core package in Ubuntu: New Status in x11proto-fonts package in Ubuntu: New Status in xorg package in Ubuntu: In Progress Status in xtrans package in Ubuntu: In Progress Status in libdrm source package in Trusty: Fix Released Status in llvm-toolchain-snapshot source package in Trusty: Fix Committed Status in x11proto-core source package in Trusty: Fix Released Status in x11proto-fonts source package in Trusty: Fix Released Status in xorg source package in Trusty: Fix Committed Status in xtrans source package in Trusty: Fix Released Bug description: In order to upload the new xorg-server we need to backport the following packages from utopic: libdrm x11proto-core x11proto-fonts xtrans libdrm 2.4.52-1-2.4.56-1 seems to have the following changes: - Hides private symbols from all libdrm libraries - fixes MSAA on Hawaii (radeon). - Adds cherryview pci-ids (intel). - Makes libdrm-nouveau threadsafe with concurrent access to the drm fd. - Fixes to exynos and freedreno. - Enables building libdrm-freedreno1 and libdrm-exynos1 x11proto-core's main change appears to be changing from the 'pointer' type to 'void *': https://launchpadlibrarian.net/173873109/x11proto-core_7.0.24-1_7.0.26-1.diff.gz x11proto-fonts' main change is the same as x11proto-core, but the documentation is reformatted too: https://launchpadlibrarian.net/173873038/x11proto-fonts_2.1.2-1_2.1.3-1.diff.gz xtrans seems to have 2 minor changes, increase default unix pipe size and add support for systemd socket activation: https://launchpadlibrarian.net/173873112/xtrans_1.3.2-1_1.3.4-1.diff.gz xorg needs to be slightly updated, to allow xserver-xorg to provide the unrenamed lts-utopic, and to allow xorg to be installed with the renamed xorg-server. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1400626/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1401648] [NEW] Prime profiles stop working after upgrade to newer nvidia driver
Public bug reported: Hi! Today I upgraded nvidia driver to nvidia 331.113 and nvidia does not seem to work anymore. I have optimus mode laptop, so my Intel works fine, but I cannot switch to NVidia using nvidia-settings. When I try, the application asks me to log out and in again. If I do this, the screen flickers and falls back to intel. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Thu Dec 11 20:38:27 2014 DistUpgraded: 2014-10-22 17:37:34,054 DEBUG enabling apt cron job DistroCodename: utopic DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7: added nvidia-331, 331.113: added nvidia-331-uvm, 331.113: added virtualbox, 4.3.18, 3.13.0-24-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3977] NVIDIA Corporation GK107M [GeForce GTX 660M] [10de:0fd4] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3977] InstallationDate: Installed on 2014-04-05 (250 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140405) MachineType: LENOVO 20132 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=8a09eb42-b431-491c-8eb8-692d800ef5c6 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to utopic on 2014-10-22 (50 days ago) dmi.bios.date: 10/11/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 5DCN90WW(V8.01) dmi.board.asset.tag: No Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: 3193WIN8 STD MLT dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad Y580 dmi.modalias: dmi:bvnLENOVO:bvr5DCN90WW(V8.01):bd10/11/2012:svnLENOVO:pn20132:pvrLenovoIdeaPadY580:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadY580: dmi.product.name: 20132 dmi.product.version: Lenovo IdeaPad Y580 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu4.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Thu Dec 11 20:03:05 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 826 vendor LGD xserver.version: 2:1.16.0-1ubuntu1.2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 nvidia optimus ubuntu utopic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1401648 Title: Prime profiles stop working after upgrade to newer nvidia driver Status in xorg package in Ubuntu: New Bug description: Hi! Today I upgraded nvidia driver to nvidia 331.113 and nvidia does not seem to work anymore. I have optimus mode laptop, so my Intel works fine, but I cannot switch to NVidia using nvidia-settings. When I try, the application asks me to log out and in again. If I do this, the screen flickers and falls back to intel. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Thu Dec 11 20:38:27 2014 DistUpgraded: 2014-10-22 17:37:34,054 DEBUG enabling apt cron job DistroCodename: utopic DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7: added nvidia-331, 331.113: added nvidia-331-uvm, 331.113: added virtualbox,
[Touch-packages] [Bug 1401648] Re: Prime profiles stop working after upgrade to newer nvidia driver
I just noticed I am running kernel 3.13.0-24, but linux- headers-3.13.0-24 are not in the respository... the latest version is linux-headers-3.13.0-23... When installing the nvidia driver, the install script complains it cannot build the module because source for current kernel is not installed. Can this be the reason? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1401648 Title: Prime profiles stop working after upgrade to newer nvidia driver Status in xorg package in Ubuntu: New Bug description: Hi! Today I upgraded nvidia driver to nvidia 331.113 and nvidia does not seem to work anymore. I have optimus mode laptop, so my Intel works fine, but I cannot switch to NVidia using nvidia-settings. When I try, the application asks me to log out and in again. If I do this, the screen flickers and falls back to intel. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Thu Dec 11 20:38:27 2014 DistUpgraded: 2014-10-22 17:37:34,054 DEBUG enabling apt cron job DistroCodename: utopic DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7: added nvidia-331, 331.113: added nvidia-331-uvm, 331.113: added virtualbox, 4.3.18, 3.13.0-24-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3977] NVIDIA Corporation GK107M [GeForce GTX 660M] [10de:0fd4] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3977] InstallationDate: Installed on 2014-04-05 (250 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140405) MachineType: LENOVO 20132 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=8a09eb42-b431-491c-8eb8-692d800ef5c6 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to utopic on 2014-10-22 (50 days ago) dmi.bios.date: 10/11/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 5DCN90WW(V8.01) dmi.board.asset.tag: No Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: 3193WIN8 STD MLT dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad Y580 dmi.modalias: dmi:bvnLENOVO:bvr5DCN90WW(V8.01):bd10/11/2012:svnLENOVO:pn20132:pvrLenovoIdeaPadY580:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadY580: dmi.product.name: 20132 dmi.product.version: Lenovo IdeaPad Y580 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu4.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Thu Dec 11 20:03:05 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 826 vendor LGD xserver.version: 2:1.16.0-1ubuntu1.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1401648/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1401648] Re: Prime profiles stop working after upgrade to newer nvidia driver
I discovered that I have been running on old kernel since upgrade to 14.10. Installing newest kernel+ headers and reinstalling nvidia drivers solved the case. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1401648 Title: Prime profiles stop working after upgrade to newer nvidia driver Status in xorg package in Ubuntu: New Bug description: Hi! Today I upgraded nvidia driver to nvidia 331.113 and nvidia does not seem to work anymore. I have optimus mode laptop, so my Intel works fine, but I cannot switch to NVidia using nvidia-settings. When I try, the application asks me to log out and in again. If I do this, the screen flickers and falls back to intel. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Thu Dec 11 20:38:27 2014 DistUpgraded: 2014-10-22 17:37:34,054 DEBUG enabling apt cron job DistroCodename: utopic DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7: added nvidia-331, 331.113: added nvidia-331-uvm, 331.113: added virtualbox, 4.3.18, 3.13.0-24-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3977] NVIDIA Corporation GK107M [GeForce GTX 660M] [10de:0fd4] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3977] InstallationDate: Installed on 2014-04-05 (250 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140405) MachineType: LENOVO 20132 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=8a09eb42-b431-491c-8eb8-692d800ef5c6 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to utopic on 2014-10-22 (50 days ago) dmi.bios.date: 10/11/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 5DCN90WW(V8.01) dmi.board.asset.tag: No Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: 3193WIN8 STD MLT dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad Y580 dmi.modalias: dmi:bvnLENOVO:bvr5DCN90WW(V8.01):bd10/11/2012:svnLENOVO:pn20132:pvrLenovoIdeaPadY580:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadY580: dmi.product.name: 20132 dmi.product.version: Lenovo IdeaPad Y580 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu4.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Thu Dec 11 20:03:05 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 826 vendor LGD xserver.version: 2:1.16.0-1ubuntu1.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1401648/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1382510] Re: systemd-logind upstart script breaks if libpam-systemd is installed for more than one arch
I've installed packages: http://launchpadlibrarian.net/188726673/libsystemd-daemon0_204-5ubuntu20.8_amd64.deb http://launchpadlibrarian.net/188726662/systemd-services_204-5ubuntu20.8_amd64.deb http://launchpadlibrarian.net/188727128/libpam-systemd_204-5ubuntu20.8_i386.deb http://launchpadlibrarian.net/18872/libpam-systemd_204-5ubuntu20.8_amd64.deb and the issue is resolved for me. Thanks. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1382510 Title: systemd-logind upstart script breaks if libpam-systemd is installed for more than one arch Status in “systemd” package in Ubuntu: Fix Released Status in “systemd” source package in Trusty: Fix Committed Bug description: /etc/init/systemd-logind.conf contains the following: # only start if PAM module is actually available, not if libpam-systemd is # removed but not purged [ -e /lib/*/security/pam_systemd.so ] || { stop; exit 0; } Which is a wrongly written script. It assumes that there is at most one file matching the wildcard. It is not true in my system. If your system have both libpam-systemd:amd64 and libpam-systemd:i386 then: # ls /lib/*/security/pam_systemd.so /lib/i386-linux-gnu/security/pam_systemd.so /lib/x86_64-linux-gnu/security/pam_systemd.so and you get the following: # cat /var/log/upstart/systemd-logind.log /proc/self/fd/9: 4: [: /lib/i386-linux-gnu/security/pam_systemd.so: unexpected operator systemd-logind stop/pre-start, process 2462 systemd-logind does not start at all. This causes many bad things to happen later. There are many ways to fix this. For my purposes I removed the faulty line from the file. I don't know what is the expected behaviour. Maybe this one: ls /lib/*/security/pam_systemd.so /dev/null || { stop; exit 0; } This bug might be the root cause of other bugs. Like this one: #1372187 (and #1377727) SRU TEST CASE = - On an amd64 system, run sudo apt-get install libpam-systemd:i386 - Then run sudo restart systemd-logind - On current trusty this will result in stop/waiting, with the error in /var/log/upstart/systemd-logind.log as above. - With this fix this will result in start/running and no error. My system info: # lsb_release -rd Description: Ubuntu 14.04.1 LTS Release: 14.04 # apt-cache policy libpam-systemd libpam-systemd: Installed: 204-5ubuntu20.7 Candidate: 204-5ubuntu20.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1382510/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1382510] [NEW] systemd-logind upstart script is flawed
Public bug reported: /etc/init/systemd-logind.conf contains the following: # only start if PAM module is actually available, not if libpam-systemd is # removed but not purged [ -e /lib/*/security/pam_systemd.so ] || { stop; exit 0; } Which is a wrongly written script. It assumes that there is at most one file matching the wildcard. It is not true in my system. If your system have both libpam-systemd:amd64 and libpam-systemd:i386 then: # ls /lib/*/security/pam_systemd.so /lib/i386-linux-gnu/security/pam_systemd.so /lib/x86_64-linux-gnu/security/pam_systemd.so and you get the following: # cat /var/log/upstart/systemd-logind.log /proc/self/fd/9: 4: [: /lib/i386-linux-gnu/security/pam_systemd.so: unexpected operator systemd-logind stop/pre-start, process 2462 systemd-logind does not start at all. This causes many bad things to happen later. There are many ways to fix this. For my purposes I removed the faulty line from the file. I don't know what is the expected behaviour. Maybe this one: ls /lib/*/security/pam_systemd.so /dev/null || { stop; exit 0; } This bug might be the root cause of other bugs. Like this one: #1372187 (and #1377727) My system info: # lsb_release -rd Description:Ubuntu 14.04.1 LTS Release:14.04 # apt-cache policy libpam-systemd libpam-systemd: Installed: 204-5ubuntu20.7 Candidate: 204-5ubuntu20.7 ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1382510 Title: systemd-logind upstart script is flawed Status in “systemd” package in Ubuntu: New Bug description: /etc/init/systemd-logind.conf contains the following: # only start if PAM module is actually available, not if libpam-systemd is # removed but not purged [ -e /lib/*/security/pam_systemd.so ] || { stop; exit 0; } Which is a wrongly written script. It assumes that there is at most one file matching the wildcard. It is not true in my system. If your system have both libpam-systemd:amd64 and libpam-systemd:i386 then: # ls /lib/*/security/pam_systemd.so /lib/i386-linux-gnu/security/pam_systemd.so /lib/x86_64-linux-gnu/security/pam_systemd.so and you get the following: # cat /var/log/upstart/systemd-logind.log /proc/self/fd/9: 4: [: /lib/i386-linux-gnu/security/pam_systemd.so: unexpected operator systemd-logind stop/pre-start, process 2462 systemd-logind does not start at all. This causes many bad things to happen later. There are many ways to fix this. For my purposes I removed the faulty line from the file. I don't know what is the expected behaviour. Maybe this one: ls /lib/*/security/pam_systemd.so /dev/null || { stop; exit 0; } This bug might be the root cause of other bugs. Like this one: #1372187 (and #1377727) My system info: # lsb_release -rd Description: Ubuntu 14.04.1 LTS Release: 14.04 # apt-cache policy libpam-systemd libpam-systemd: Installed: 204-5ubuntu20.7 Candidate: 204-5ubuntu20.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1382510/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1375663] [NEW] curl handles EINTR wrong
Public bug reported: Our application using libcurl for http communication was behaving awkward and after thorough investigation we found that in some cases it doesn't retry a poll after EINTR. Later we found, that this is a bug in libcurl and that it was repaired in this upstream patch: https://github.com/bagder/curl/commit/97d2e4bd75d1be26b48f37900b7b719c418e0ac6 # lsb_release -rd Description:Ubuntu 14.04.1 LTS Release:14.04 # apt-cache policy curl curl: Installed: 7.35.0-1ubuntu2.1 Candidate: 7.35.0-1ubuntu2.1 ** Affects: curl (Ubuntu) Importance: Undecided Status: New ** Patch added: fix_timeout_return_value.patch https://bugs.launchpad.net/bugs/1375663/+attachment/4220043/+files/fix_timeout_return_value.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to curl in Ubuntu. https://bugs.launchpad.net/bugs/1375663 Title: curl handles EINTR wrong Status in “curl” package in Ubuntu: New Bug description: Our application using libcurl for http communication was behaving awkward and after thorough investigation we found that in some cases it doesn't retry a poll after EINTR. Later we found, that this is a bug in libcurl and that it was repaired in this upstream patch: https://github.com/bagder/curl/commit/97d2e4bd75d1be26b48f37900b7b719c418e0ac6 # lsb_release -rd Description: Ubuntu 14.04.1 LTS Release: 14.04 # apt-cache policy curl curl: Installed: 7.35.0-1ubuntu2.1 Candidate: 7.35.0-1ubuntu2.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1375663/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1311881] Re: dual screen ubuntu 14.04, second screen only partially displaying desktop
I had simmilar issue. I deisabled the gpu-manager.conf, deleted old xorg.conf, used aticonfig --initial to create a new config file, logged in and used amdcccle to make final adjustments. I dont really understand this but it seems that there is some problem with randr. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1311881 Title: dual screen ubuntu 14.04, second screen only partially displaying desktop Status in “xorg” package in Ubuntu: Confirmed Bug description: The second screen on my 2 monitor Ubuntu 14.04 setup is only partially showing any of the desktop. The primary screen is a 22 1680*1050 and the secondary screen is 1920*1200. The primary screen has a complete and true 1680*1050 desktop, but the secondary screen only shows 1 of the 1920*1200 screen down the left vertical. The rest of the desktop is obscured under some black window, with only the mouse being displayed as it travels through that screen. Any windows or items below that black area, can be interacted with, and the mouse indicates their presence with resize/minimise and other hints, but they do not display over the black area. The system was working perfectly fine in 13.10 and this issue only occurred after I upgraded to 14.04 and, faced with a failed to start session bug on the login screen, resorted to an apt-get install ubuntu-desktop to get my desktop up and running. My graphics card is an ATI Radeon HD 6670 and my monitors are Samsung Syncmaster 2232bw (22) and Dell UM2412M. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: fglrx .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Wed Apr 23 21:51:03 2014 DistUpgraded: 2014-04-23 18:43:48,762 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Turks XT [Radeon HD 6670/7670] [1002:6758] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:0443] InstallationDate: Installed on 2012-09-24 (576 days ago) InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 (20120823.1) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=1aff935b-13e8-475e-a845-3d816a582db2 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to trusty on 2014-04-23 (0 days ago) dmi.bios.date: 03/23/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1103 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M5A78L-M/USB3 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.:bvr1103:bd03/23/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM5A78L-M/USB3:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1 version.fglrx-installer: fglrx-installer N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Wed Apr 23 22:38:29 2014 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory AIGLX error: failed to open /usr/X11R6/lib64/modules/dri/fglrx_dri.so, error[/usr/X11R6/lib64/modules/dri/fglrx_dri.so: cannot open shared object file: No such file or directory] AIGLX error: failed to open