[Kernel-packages] [Bug 1861289] [NEW] No virtual terminals and NAutoVTs=6 setting ineffective
Public bug reported: This is not the same bug as #1758512 - that bug is about an unresponsive key combination, this bug is reproducible without pressing any key- combination. Reproduce: Using Ubuntu 19.10. Manually modified /etc/systemd/logind.conf by uncommenting this: [Login] NAutoVTs=6 ReserveVT=6 According to man logind.conf this would result 6 virtual terminals spawned. Bug behaviour: Reboot and run $ sudo fgconsole --next-available 3 Expected: Given I've configured 6 auto virtual terminals this number should be higher than 6. Bug behaviour Reboot and run: $ sudo chvt 3 Got a screen with a black background and a single blinking cursor at upper left corner Expected: Seeing a login prompt ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1861289 Title: No virtual terminals and NAutoVTs=6 setting ineffective Status in linux package in Ubuntu: New Bug description: This is not the same bug as #1758512 - that bug is about an unresponsive key combination, this bug is reproducible without pressing any key-combination. Reproduce: Using Ubuntu 19.10. Manually modified /etc/systemd/logind.conf by uncommenting this: [Login] NAutoVTs=6 ReserveVT=6 According to man logind.conf this would result 6 virtual terminals spawned. Bug behaviour: Reboot and run $ sudo fgconsole --next-available 3 Expected: Given I've configured 6 auto virtual terminals this number should be higher than 6. Bug behaviour Reboot and run: $ sudo chvt 3 Got a screen with a black background and a single blinking cursor at upper left corner Expected: Seeing a login prompt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861289/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1861289] Re: No virtual terminals and NAutoVTs=6 setting ineffective
apport information ** Tags added: apport-collected eoan ** Description changed: This is not the same bug as #1758512 - that bug is about an unresponsive key combination, this bug is reproducible without pressing any key- combination. Reproduce: Using Ubuntu 19.10. Manually modified /etc/systemd/logind.conf by uncommenting this: [Login] NAutoVTs=6 ReserveVT=6 According to man logind.conf this would result 6 virtual terminals spawned. Bug behaviour: Reboot and run $ sudo fgconsole --next-available 3 Expected: Given I've configured 6 auto virtual terminals this number should be higher than 6. Bug behaviour Reboot and run: $ sudo chvt 3 Got a screen with a black background and a single blinking cursor at upper left corner Expected: Seeing a login prompt + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu8.2 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: weiwu 1703 F pulseaudio + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 19.10 + InstallationDate: Installed on 2019-06-11 (232 days ago) + InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) + MachineType: LENOVO 20KHS1BP00 + Package: linux (not installed) + ProcFB: 0 i915drmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=UUID=b9df6bda-4eaa-4420-9573-12ab02da707d ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 + RelatedPackageVersions: + linux-restricted-modules-5.3.0-26-generic N/A + linux-backports-modules-5.3.0-26-generic N/A + linux-firmware1.183.3 + Tags: eoan + Uname: Linux 5.3.0-26-generic x86_64 + UpgradeStatus: Upgraded to eoan on 2019-11-15 (75 days ago) + UserGroups: adm cdrom dialout dip lp lpadmin plugdev sambashare staff sudo + _MarkForUpload: True + dmi.bios.date: 06/25/2018 + dmi.bios.vendor: LENOVO + dmi.bios.version: N23ET50W (1.25 ) + dmi.board.asset.tag: Not Available + dmi.board.name: 20KHS1BP00 + 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.modalias: dmi:bvnLENOVO:bvrN23ET50W(1.25):bd06/25/2018:svnLENOVO:pn20KHS1BP00:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHS1BP00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: + dmi.product.family: ThinkPad X1 Carbon 6th + dmi.product.name: 20KHS1BP00 + dmi.product.sku: LENOVO_MT_20KH_BU_Think_FM_ThinkPad X1 Carbon 6th + dmi.product.version: ThinkPad X1 Carbon 6th + dmi.sys.vendor: LENOVO ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1861289/+attachment/5323827/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1861289 Title: No virtual terminals and NAutoVTs=6 setting ineffective Status in linux package in Ubuntu: Confirmed Bug description: This is not the same bug as #1758512 - that bug is about an unresponsive key combination, this bug is reproducible without pressing any key-combination. Reproduce: Using Ubuntu 19.10. Manually modified /etc/systemd/logind.conf by uncommenting this: [Login] NAutoVTs=6 ReserveVT=6 According to man logind.conf this would result 6 virtual terminals spawned. Bug behaviour: Reboot and run $ sudo fgconsole --next-available 3 Expected: Given I've configured 6 auto virtual terminals this number should be higher than 6. Bug behaviour Reboot and run: $ sudo chvt 3 Got a screen with a black background and a single blinking cursor at upper left corner Expected: Seeing a login prompt --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: weiwu 1703 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-06-11 (232 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 20KHS1BP00 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=UUID=b9df6bda-4eaa-4420-9573-12ab02da707d ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 RelatedPackageVersions: linux-restricted-modules-5.3.0-26-generic N/A linux-backports-modules-5.3.0-26-generic N/A linux-firmware1.183.3 Tags: eoan Uname: Linux 5.3.0-26-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-11-15 (75 days ago) UserGroups: adm cdrom dialout dip lp lpadmin plugdev sambashare staff sudo _MarkForUpload: True dmi.bios.date: 06/25/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET50W (1.25 ) dm
[Kernel-packages] [Bug 1861289] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1861289/+attachment/5323829/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1861289 Title: No virtual terminals and NAutoVTs=6 setting ineffective Status in linux package in Ubuntu: Confirmed Bug description: This is not the same bug as #1758512 - that bug is about an unresponsive key combination, this bug is reproducible without pressing any key-combination. Reproduce: Using Ubuntu 19.10. Manually modified /etc/systemd/logind.conf by uncommenting this: [Login] NAutoVTs=6 ReserveVT=6 According to man logind.conf this would result 6 virtual terminals spawned. Bug behaviour: Reboot and run $ sudo fgconsole --next-available 3 Expected: Given I've configured 6 auto virtual terminals this number should be higher than 6. Bug behaviour Reboot and run: $ sudo chvt 3 Got a screen with a black background and a single blinking cursor at upper left corner Expected: Seeing a login prompt --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: weiwu 1703 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-06-11 (232 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 20KHS1BP00 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=UUID=b9df6bda-4eaa-4420-9573-12ab02da707d ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 RelatedPackageVersions: linux-restricted-modules-5.3.0-26-generic N/A linux-backports-modules-5.3.0-26-generic N/A linux-firmware1.183.3 Tags: eoan Uname: Linux 5.3.0-26-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-11-15 (75 days ago) UserGroups: adm cdrom dialout dip lp lpadmin plugdev sambashare staff sudo _MarkForUpload: True dmi.bios.date: 06/25/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET50W (1.25 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KHS1BP00 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.modalias: dmi:bvnLENOVO:bvrN23ET50W(1.25):bd06/25/2018:svnLENOVO:pn20KHS1BP00:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHS1BP00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 6th dmi.product.name: 20KHS1BP00 dmi.product.sku: LENOVO_MT_20KH_BU_Think_FM_ThinkPad X1 Carbon 6th dmi.product.version: ThinkPad X1 Carbon 6th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861289/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1861289] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1861289/+attachment/5323832/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1861289 Title: No virtual terminals and NAutoVTs=6 setting ineffective Status in linux package in Ubuntu: Confirmed Bug description: This is not the same bug as #1758512 - that bug is about an unresponsive key combination, this bug is reproducible without pressing any key-combination. Reproduce: Using Ubuntu 19.10. Manually modified /etc/systemd/logind.conf by uncommenting this: [Login] NAutoVTs=6 ReserveVT=6 According to man logind.conf this would result 6 virtual terminals spawned. Bug behaviour: Reboot and run $ sudo fgconsole --next-available 3 Expected: Given I've configured 6 auto virtual terminals this number should be higher than 6. Bug behaviour Reboot and run: $ sudo chvt 3 Got a screen with a black background and a single blinking cursor at upper left corner Expected: Seeing a login prompt --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: weiwu 1703 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-06-11 (232 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 20KHS1BP00 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=UUID=b9df6bda-4eaa-4420-9573-12ab02da707d ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 RelatedPackageVersions: linux-restricted-modules-5.3.0-26-generic N/A linux-backports-modules-5.3.0-26-generic N/A linux-firmware1.183.3 Tags: eoan Uname: Linux 5.3.0-26-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-11-15 (75 days ago) UserGroups: adm cdrom dialout dip lp lpadmin plugdev sambashare staff sudo _MarkForUpload: True dmi.bios.date: 06/25/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET50W (1.25 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KHS1BP00 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.modalias: dmi:bvnLENOVO:bvrN23ET50W(1.25):bd06/25/2018:svnLENOVO:pn20KHS1BP00:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHS1BP00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 6th dmi.product.name: 20KHS1BP00 dmi.product.sku: LENOVO_MT_20KH_BU_Think_FM_ThinkPad X1 Carbon 6th dmi.product.version: ThinkPad X1 Carbon 6th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861289/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1861289] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1861289/+attachment/5323837/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1861289 Title: No virtual terminals and NAutoVTs=6 setting ineffective Status in linux package in Ubuntu: Confirmed Bug description: This is not the same bug as #1758512 - that bug is about an unresponsive key combination, this bug is reproducible without pressing any key-combination. Reproduce: Using Ubuntu 19.10. Manually modified /etc/systemd/logind.conf by uncommenting this: [Login] NAutoVTs=6 ReserveVT=6 According to man logind.conf this would result 6 virtual terminals spawned. Bug behaviour: Reboot and run $ sudo fgconsole --next-available 3 Expected: Given I've configured 6 auto virtual terminals this number should be higher than 6. Bug behaviour Reboot and run: $ sudo chvt 3 Got a screen with a black background and a single blinking cursor at upper left corner Expected: Seeing a login prompt --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: weiwu 1703 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-06-11 (232 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 20KHS1BP00 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=UUID=b9df6bda-4eaa-4420-9573-12ab02da707d ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 RelatedPackageVersions: linux-restricted-modules-5.3.0-26-generic N/A linux-backports-modules-5.3.0-26-generic N/A linux-firmware1.183.3 Tags: eoan Uname: Linux 5.3.0-26-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-11-15 (75 days ago) UserGroups: adm cdrom dialout dip lp lpadmin plugdev sambashare staff sudo _MarkForUpload: True dmi.bios.date: 06/25/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET50W (1.25 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KHS1BP00 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.modalias: dmi:bvnLENOVO:bvrN23ET50W(1.25):bd06/25/2018:svnLENOVO:pn20KHS1BP00:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHS1BP00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 6th dmi.product.name: 20KHS1BP00 dmi.product.sku: LENOVO_MT_20KH_BU_Think_FM_ThinkPad X1 Carbon 6th dmi.product.version: ThinkPad X1 Carbon 6th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861289/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1861289] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1861289/+attachment/5323838/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1861289 Title: No virtual terminals and NAutoVTs=6 setting ineffective Status in linux package in Ubuntu: Confirmed Bug description: This is not the same bug as #1758512 - that bug is about an unresponsive key combination, this bug is reproducible without pressing any key-combination. Reproduce: Using Ubuntu 19.10. Manually modified /etc/systemd/logind.conf by uncommenting this: [Login] NAutoVTs=6 ReserveVT=6 According to man logind.conf this would result 6 virtual terminals spawned. Bug behaviour: Reboot and run $ sudo fgconsole --next-available 3 Expected: Given I've configured 6 auto virtual terminals this number should be higher than 6. Bug behaviour Reboot and run: $ sudo chvt 3 Got a screen with a black background and a single blinking cursor at upper left corner Expected: Seeing a login prompt --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: weiwu 1703 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-06-11 (232 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 20KHS1BP00 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=UUID=b9df6bda-4eaa-4420-9573-12ab02da707d ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 RelatedPackageVersions: linux-restricted-modules-5.3.0-26-generic N/A linux-backports-modules-5.3.0-26-generic N/A linux-firmware1.183.3 Tags: eoan Uname: Linux 5.3.0-26-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-11-15 (75 days ago) UserGroups: adm cdrom dialout dip lp lpadmin plugdev sambashare staff sudo _MarkForUpload: True dmi.bios.date: 06/25/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET50W (1.25 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KHS1BP00 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.modalias: dmi:bvnLENOVO:bvrN23ET50W(1.25):bd06/25/2018:svnLENOVO:pn20KHS1BP00:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHS1BP00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 6th dmi.product.name: 20KHS1BP00 dmi.product.sku: LENOVO_MT_20KH_BU_Think_FM_ThinkPad X1 Carbon 6th dmi.product.version: ThinkPad X1 Carbon 6th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861289/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1861289] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1861289/+attachment/5323828/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1861289 Title: No virtual terminals and NAutoVTs=6 setting ineffective Status in linux package in Ubuntu: Confirmed Bug description: This is not the same bug as #1758512 - that bug is about an unresponsive key combination, this bug is reproducible without pressing any key-combination. Reproduce: Using Ubuntu 19.10. Manually modified /etc/systemd/logind.conf by uncommenting this: [Login] NAutoVTs=6 ReserveVT=6 According to man logind.conf this would result 6 virtual terminals spawned. Bug behaviour: Reboot and run $ sudo fgconsole --next-available 3 Expected: Given I've configured 6 auto virtual terminals this number should be higher than 6. Bug behaviour Reboot and run: $ sudo chvt 3 Got a screen with a black background and a single blinking cursor at upper left corner Expected: Seeing a login prompt --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: weiwu 1703 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-06-11 (232 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 20KHS1BP00 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=UUID=b9df6bda-4eaa-4420-9573-12ab02da707d ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 RelatedPackageVersions: linux-restricted-modules-5.3.0-26-generic N/A linux-backports-modules-5.3.0-26-generic N/A linux-firmware1.183.3 Tags: eoan Uname: Linux 5.3.0-26-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-11-15 (75 days ago) UserGroups: adm cdrom dialout dip lp lpadmin plugdev sambashare staff sudo _MarkForUpload: True dmi.bios.date: 06/25/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET50W (1.25 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KHS1BP00 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.modalias: dmi:bvnLENOVO:bvrN23ET50W(1.25):bd06/25/2018:svnLENOVO:pn20KHS1BP00:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHS1BP00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 6th dmi.product.name: 20KHS1BP00 dmi.product.sku: LENOVO_MT_20KH_BU_Think_FM_ThinkPad X1 Carbon 6th dmi.product.version: ThinkPad X1 Carbon 6th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861289/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1861289] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1861289/+attachment/5323834/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1861289 Title: No virtual terminals and NAutoVTs=6 setting ineffective Status in linux package in Ubuntu: Confirmed Bug description: This is not the same bug as #1758512 - that bug is about an unresponsive key combination, this bug is reproducible without pressing any key-combination. Reproduce: Using Ubuntu 19.10. Manually modified /etc/systemd/logind.conf by uncommenting this: [Login] NAutoVTs=6 ReserveVT=6 According to man logind.conf this would result 6 virtual terminals spawned. Bug behaviour: Reboot and run $ sudo fgconsole --next-available 3 Expected: Given I've configured 6 auto virtual terminals this number should be higher than 6. Bug behaviour Reboot and run: $ sudo chvt 3 Got a screen with a black background and a single blinking cursor at upper left corner Expected: Seeing a login prompt --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: weiwu 1703 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-06-11 (232 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 20KHS1BP00 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=UUID=b9df6bda-4eaa-4420-9573-12ab02da707d ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 RelatedPackageVersions: linux-restricted-modules-5.3.0-26-generic N/A linux-backports-modules-5.3.0-26-generic N/A linux-firmware1.183.3 Tags: eoan Uname: Linux 5.3.0-26-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-11-15 (75 days ago) UserGroups: adm cdrom dialout dip lp lpadmin plugdev sambashare staff sudo _MarkForUpload: True dmi.bios.date: 06/25/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET50W (1.25 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KHS1BP00 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.modalias: dmi:bvnLENOVO:bvrN23ET50W(1.25):bd06/25/2018:svnLENOVO:pn20KHS1BP00:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHS1BP00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 6th dmi.product.name: 20KHS1BP00 dmi.product.sku: LENOVO_MT_20KH_BU_Think_FM_ThinkPad X1 Carbon 6th dmi.product.version: ThinkPad X1 Carbon 6th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861289/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1861289] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1861289/+attachment/5323836/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1861289 Title: No virtual terminals and NAutoVTs=6 setting ineffective Status in linux package in Ubuntu: Confirmed Bug description: This is not the same bug as #1758512 - that bug is about an unresponsive key combination, this bug is reproducible without pressing any key-combination. Reproduce: Using Ubuntu 19.10. Manually modified /etc/systemd/logind.conf by uncommenting this: [Login] NAutoVTs=6 ReserveVT=6 According to man logind.conf this would result 6 virtual terminals spawned. Bug behaviour: Reboot and run $ sudo fgconsole --next-available 3 Expected: Given I've configured 6 auto virtual terminals this number should be higher than 6. Bug behaviour Reboot and run: $ sudo chvt 3 Got a screen with a black background and a single blinking cursor at upper left corner Expected: Seeing a login prompt --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: weiwu 1703 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-06-11 (232 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 20KHS1BP00 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=UUID=b9df6bda-4eaa-4420-9573-12ab02da707d ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 RelatedPackageVersions: linux-restricted-modules-5.3.0-26-generic N/A linux-backports-modules-5.3.0-26-generic N/A linux-firmware1.183.3 Tags: eoan Uname: Linux 5.3.0-26-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-11-15 (75 days ago) UserGroups: adm cdrom dialout dip lp lpadmin plugdev sambashare staff sudo _MarkForUpload: True dmi.bios.date: 06/25/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET50W (1.25 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KHS1BP00 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.modalias: dmi:bvnLENOVO:bvrN23ET50W(1.25):bd06/25/2018:svnLENOVO:pn20KHS1BP00:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHS1BP00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 6th dmi.product.name: 20KHS1BP00 dmi.product.sku: LENOVO_MT_20KH_BU_Think_FM_ThinkPad X1 Carbon 6th dmi.product.version: ThinkPad X1 Carbon 6th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861289/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1861289] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1861289/+attachment/5323841/+files/WifiSyslog.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1861289 Title: No virtual terminals and NAutoVTs=6 setting ineffective Status in linux package in Ubuntu: Confirmed Bug description: This is not the same bug as #1758512 - that bug is about an unresponsive key combination, this bug is reproducible without pressing any key-combination. Reproduce: Using Ubuntu 19.10. Manually modified /etc/systemd/logind.conf by uncommenting this: [Login] NAutoVTs=6 ReserveVT=6 According to man logind.conf this would result 6 virtual terminals spawned. Bug behaviour: Reboot and run $ sudo fgconsole --next-available 3 Expected: Given I've configured 6 auto virtual terminals this number should be higher than 6. Bug behaviour Reboot and run: $ sudo chvt 3 Got a screen with a black background and a single blinking cursor at upper left corner Expected: Seeing a login prompt --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: weiwu 1703 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-06-11 (232 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 20KHS1BP00 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=UUID=b9df6bda-4eaa-4420-9573-12ab02da707d ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 RelatedPackageVersions: linux-restricted-modules-5.3.0-26-generic N/A linux-backports-modules-5.3.0-26-generic N/A linux-firmware1.183.3 Tags: eoan Uname: Linux 5.3.0-26-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-11-15 (75 days ago) UserGroups: adm cdrom dialout dip lp lpadmin plugdev sambashare staff sudo _MarkForUpload: True dmi.bios.date: 06/25/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET50W (1.25 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KHS1BP00 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.modalias: dmi:bvnLENOVO:bvrN23ET50W(1.25):bd06/25/2018:svnLENOVO:pn20KHS1BP00:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHS1BP00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 6th dmi.product.name: 20KHS1BP00 dmi.product.sku: LENOVO_MT_20KH_BU_Think_FM_ThinkPad X1 Carbon 6th dmi.product.version: ThinkPad X1 Carbon 6th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861289/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1861289] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1861289/+attachment/5323835/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1861289 Title: No virtual terminals and NAutoVTs=6 setting ineffective Status in linux package in Ubuntu: Confirmed Bug description: This is not the same bug as #1758512 - that bug is about an unresponsive key combination, this bug is reproducible without pressing any key-combination. Reproduce: Using Ubuntu 19.10. Manually modified /etc/systemd/logind.conf by uncommenting this: [Login] NAutoVTs=6 ReserveVT=6 According to man logind.conf this would result 6 virtual terminals spawned. Bug behaviour: Reboot and run $ sudo fgconsole --next-available 3 Expected: Given I've configured 6 auto virtual terminals this number should be higher than 6. Bug behaviour Reboot and run: $ sudo chvt 3 Got a screen with a black background and a single blinking cursor at upper left corner Expected: Seeing a login prompt --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: weiwu 1703 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-06-11 (232 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 20KHS1BP00 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=UUID=b9df6bda-4eaa-4420-9573-12ab02da707d ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 RelatedPackageVersions: linux-restricted-modules-5.3.0-26-generic N/A linux-backports-modules-5.3.0-26-generic N/A linux-firmware1.183.3 Tags: eoan Uname: Linux 5.3.0-26-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-11-15 (75 days ago) UserGroups: adm cdrom dialout dip lp lpadmin plugdev sambashare staff sudo _MarkForUpload: True dmi.bios.date: 06/25/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET50W (1.25 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KHS1BP00 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.modalias: dmi:bvnLENOVO:bvrN23ET50W(1.25):bd06/25/2018:svnLENOVO:pn20KHS1BP00:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHS1BP00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 6th dmi.product.name: 20KHS1BP00 dmi.product.sku: LENOVO_MT_20KH_BU_Think_FM_ThinkPad X1 Carbon 6th dmi.product.version: ThinkPad X1 Carbon 6th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861289/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1861289] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1861289/+attachment/5323830/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1861289 Title: No virtual terminals and NAutoVTs=6 setting ineffective Status in linux package in Ubuntu: Confirmed Bug description: This is not the same bug as #1758512 - that bug is about an unresponsive key combination, this bug is reproducible without pressing any key-combination. Reproduce: Using Ubuntu 19.10. Manually modified /etc/systemd/logind.conf by uncommenting this: [Login] NAutoVTs=6 ReserveVT=6 According to man logind.conf this would result 6 virtual terminals spawned. Bug behaviour: Reboot and run $ sudo fgconsole --next-available 3 Expected: Given I've configured 6 auto virtual terminals this number should be higher than 6. Bug behaviour Reboot and run: $ sudo chvt 3 Got a screen with a black background and a single blinking cursor at upper left corner Expected: Seeing a login prompt --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: weiwu 1703 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-06-11 (232 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 20KHS1BP00 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=UUID=b9df6bda-4eaa-4420-9573-12ab02da707d ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 RelatedPackageVersions: linux-restricted-modules-5.3.0-26-generic N/A linux-backports-modules-5.3.0-26-generic N/A linux-firmware1.183.3 Tags: eoan Uname: Linux 5.3.0-26-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-11-15 (75 days ago) UserGroups: adm cdrom dialout dip lp lpadmin plugdev sambashare staff sudo _MarkForUpload: True dmi.bios.date: 06/25/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET50W (1.25 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KHS1BP00 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.modalias: dmi:bvnLENOVO:bvrN23ET50W(1.25):bd06/25/2018:svnLENOVO:pn20KHS1BP00:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHS1BP00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 6th dmi.product.name: 20KHS1BP00 dmi.product.sku: LENOVO_MT_20KH_BU_Think_FM_ThinkPad X1 Carbon 6th dmi.product.version: ThinkPad X1 Carbon 6th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861289/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1861289] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1861289/+attachment/5323840/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1861289 Title: No virtual terminals and NAutoVTs=6 setting ineffective Status in linux package in Ubuntu: Confirmed Bug description: This is not the same bug as #1758512 - that bug is about an unresponsive key combination, this bug is reproducible without pressing any key-combination. Reproduce: Using Ubuntu 19.10. Manually modified /etc/systemd/logind.conf by uncommenting this: [Login] NAutoVTs=6 ReserveVT=6 According to man logind.conf this would result 6 virtual terminals spawned. Bug behaviour: Reboot and run $ sudo fgconsole --next-available 3 Expected: Given I've configured 6 auto virtual terminals this number should be higher than 6. Bug behaviour Reboot and run: $ sudo chvt 3 Got a screen with a black background and a single blinking cursor at upper left corner Expected: Seeing a login prompt --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: weiwu 1703 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-06-11 (232 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 20KHS1BP00 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=UUID=b9df6bda-4eaa-4420-9573-12ab02da707d ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 RelatedPackageVersions: linux-restricted-modules-5.3.0-26-generic N/A linux-backports-modules-5.3.0-26-generic N/A linux-firmware1.183.3 Tags: eoan Uname: Linux 5.3.0-26-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-11-15 (75 days ago) UserGroups: adm cdrom dialout dip lp lpadmin plugdev sambashare staff sudo _MarkForUpload: True dmi.bios.date: 06/25/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET50W (1.25 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KHS1BP00 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.modalias: dmi:bvnLENOVO:bvrN23ET50W(1.25):bd06/25/2018:svnLENOVO:pn20KHS1BP00:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHS1BP00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 6th dmi.product.name: 20KHS1BP00 dmi.product.sku: LENOVO_MT_20KH_BU_Think_FM_ThinkPad X1 Carbon 6th dmi.product.version: ThinkPad X1 Carbon 6th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861289/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1861289] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1861289/+attachment/5323831/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1861289 Title: No virtual terminals and NAutoVTs=6 setting ineffective Status in linux package in Ubuntu: Confirmed Bug description: This is not the same bug as #1758512 - that bug is about an unresponsive key combination, this bug is reproducible without pressing any key-combination. Reproduce: Using Ubuntu 19.10. Manually modified /etc/systemd/logind.conf by uncommenting this: [Login] NAutoVTs=6 ReserveVT=6 According to man logind.conf this would result 6 virtual terminals spawned. Bug behaviour: Reboot and run $ sudo fgconsole --next-available 3 Expected: Given I've configured 6 auto virtual terminals this number should be higher than 6. Bug behaviour Reboot and run: $ sudo chvt 3 Got a screen with a black background and a single blinking cursor at upper left corner Expected: Seeing a login prompt --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: weiwu 1703 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-06-11 (232 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 20KHS1BP00 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=UUID=b9df6bda-4eaa-4420-9573-12ab02da707d ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 RelatedPackageVersions: linux-restricted-modules-5.3.0-26-generic N/A linux-backports-modules-5.3.0-26-generic N/A linux-firmware1.183.3 Tags: eoan Uname: Linux 5.3.0-26-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-11-15 (75 days ago) UserGroups: adm cdrom dialout dip lp lpadmin plugdev sambashare staff sudo _MarkForUpload: True dmi.bios.date: 06/25/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET50W (1.25 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KHS1BP00 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.modalias: dmi:bvnLENOVO:bvrN23ET50W(1.25):bd06/25/2018:svnLENOVO:pn20KHS1BP00:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHS1BP00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 6th dmi.product.name: 20KHS1BP00 dmi.product.sku: LENOVO_MT_20KH_BU_Think_FM_ThinkPad X1 Carbon 6th dmi.product.version: ThinkPad X1 Carbon 6th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861289/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1861289] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1861289/+attachment/5323839/+files/RfKill.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1861289 Title: No virtual terminals and NAutoVTs=6 setting ineffective Status in linux package in Ubuntu: Confirmed Bug description: This is not the same bug as #1758512 - that bug is about an unresponsive key combination, this bug is reproducible without pressing any key-combination. Reproduce: Using Ubuntu 19.10. Manually modified /etc/systemd/logind.conf by uncommenting this: [Login] NAutoVTs=6 ReserveVT=6 According to man logind.conf this would result 6 virtual terminals spawned. Bug behaviour: Reboot and run $ sudo fgconsole --next-available 3 Expected: Given I've configured 6 auto virtual terminals this number should be higher than 6. Bug behaviour Reboot and run: $ sudo chvt 3 Got a screen with a black background and a single blinking cursor at upper left corner Expected: Seeing a login prompt --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: weiwu 1703 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-06-11 (232 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 20KHS1BP00 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=UUID=b9df6bda-4eaa-4420-9573-12ab02da707d ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 RelatedPackageVersions: linux-restricted-modules-5.3.0-26-generic N/A linux-backports-modules-5.3.0-26-generic N/A linux-firmware1.183.3 Tags: eoan Uname: Linux 5.3.0-26-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-11-15 (75 days ago) UserGroups: adm cdrom dialout dip lp lpadmin plugdev sambashare staff sudo _MarkForUpload: True dmi.bios.date: 06/25/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET50W (1.25 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KHS1BP00 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.modalias: dmi:bvnLENOVO:bvrN23ET50W(1.25):bd06/25/2018:svnLENOVO:pn20KHS1BP00:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHS1BP00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 6th dmi.product.name: 20KHS1BP00 dmi.product.sku: LENOVO_MT_20KH_BU_Think_FM_ThinkPad X1 Carbon 6th dmi.product.version: ThinkPad X1 Carbon 6th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861289/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1861289] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1861289/+attachment/5323833/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1861289 Title: No virtual terminals and NAutoVTs=6 setting ineffective Status in linux package in Ubuntu: Confirmed Bug description: This is not the same bug as #1758512 - that bug is about an unresponsive key combination, this bug is reproducible without pressing any key-combination. Reproduce: Using Ubuntu 19.10. Manually modified /etc/systemd/logind.conf by uncommenting this: [Login] NAutoVTs=6 ReserveVT=6 According to man logind.conf this would result 6 virtual terminals spawned. Bug behaviour: Reboot and run $ sudo fgconsole --next-available 3 Expected: Given I've configured 6 auto virtual terminals this number should be higher than 6. Bug behaviour Reboot and run: $ sudo chvt 3 Got a screen with a black background and a single blinking cursor at upper left corner Expected: Seeing a login prompt --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: weiwu 1703 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-06-11 (232 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 20KHS1BP00 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=UUID=b9df6bda-4eaa-4420-9573-12ab02da707d ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 RelatedPackageVersions: linux-restricted-modules-5.3.0-26-generic N/A linux-backports-modules-5.3.0-26-generic N/A linux-firmware1.183.3 Tags: eoan Uname: Linux 5.3.0-26-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-11-15 (75 days ago) UserGroups: adm cdrom dialout dip lp lpadmin plugdev sambashare staff sudo _MarkForUpload: True dmi.bios.date: 06/25/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET50W (1.25 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KHS1BP00 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.modalias: dmi:bvnLENOVO:bvrN23ET50W(1.25):bd06/25/2018:svnLENOVO:pn20KHS1BP00:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHS1BP00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 6th dmi.product.name: 20KHS1BP00 dmi.product.sku: LENOVO_MT_20KH_BU_Think_FM_ThinkPad X1 Carbon 6th dmi.product.version: ThinkPad X1 Carbon 6th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861289/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1322396] Re: light sensor misjudge ambience light
tested on 3.15.0-031500rc5-generic. The censor still misjudge ambience light, and flickers the screen when there are no noticable light change. ** Tags added: kernel-bug-exists-upstream ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1322396 Title: light sensor misjudge ambience light Status in “linux” package in Ubuntu: Confirmed Bug description: Running Ubuntu 14.04 on bModo12 (same hardware as WeTab). When running on battery, the screen changes brightness frequently, by itself, while there are little change in ambience light. In fact, if I just place it stablly on the table and observe from distance, it turns bright and dark all by itself happyly, once a few seconds. It is unbearable to use. I installed brightness control applet "indicator-brightness", and hoped manual control overwrites automatic ambience light sensor. But no, automatic sensor overwrites manual setting. If I set brightness to 10, for example, it is bright for one second, and back to darkness. I urgenly need a workaround - a method to turn off light sensor and force always brightest light output. Kindly offer a workaround before solving this bug. Thanks! My hardware and system is the same when I reported bug 1318639 - and the bug always exists since I installed the OS in day 1. Inform me if you insist on a new machine-generated PC/OS information set. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1322396/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1322396] Re: light sensor misjudge ambience light
Can anyone provide a workaround first? For example how to prevent light sensor from working at all, disable the module or kernel feature that uses it. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1322396 Title: light sensor misjudge ambience light Status in “linux” package in Ubuntu: Confirmed Bug description: Running Ubuntu 14.04 on bModo12 (same hardware as WeTab). When running on battery, the screen changes brightness frequently, by itself, while there are little change in ambience light. In fact, if I just place it stablly on the table and observe from distance, it turns bright and dark all by itself happyly, once a few seconds. It is unbearable to use. I installed brightness control applet "indicator-brightness", and hoped manual control overwrites automatic ambience light sensor. But no, automatic sensor overwrites manual setting. If I set brightness to 10, for example, it is bright for one second, and back to darkness. I urgenly need a workaround - a method to turn off light sensor and force always brightest light output. Kindly offer a workaround before solving this bug. Thanks! My hardware and system is the same when I reported bug 1318639 - and the bug always exists since I installed the OS in day 1. Inform me if you insist on a new machine-generated PC/OS information set. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1322396/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1326885] [NEW] desktop start rotated
Public bug reported: Running Ubuntu 14.04 on bModo12 (same hardware as WeTab). Right after login the screen rotates to rightwards (no matter what direction the screen is actually at). I had to run this everytime: $ xrandr -o normal Note this is not gravity sensor at work. If gravity sensor is at work, and turned screen leftwards or rightwards, 'xrandr -o normal' will not have any effect. Expected behaviour: the desktop rotation is decided by gravity sensor, or, without its input, defaults to normal. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1326885 Title: desktop start rotated Status in “linux” package in Ubuntu: New Bug description: Running Ubuntu 14.04 on bModo12 (same hardware as WeTab). Right after login the screen rotates to rightwards (no matter what direction the screen is actually at). I had to run this everytime: $ xrandr -o normal Note this is not gravity sensor at work. If gravity sensor is at work, and turned screen leftwards or rightwards, 'xrandr -o normal' will not have any effect. Expected behaviour: the desktop rotation is decided by gravity sensor, or, without its input, defaults to normal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1326885/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1326885] Re: desktop start rotated
apport information ** Tags added: apport-collected trusty ** Description changed: Running Ubuntu 14.04 on bModo12 (same hardware as WeTab). Right after login the screen rotates to rightwards (no matter what direction the screen is actually at). I had to run this everytime: $ xrandr -o normal Note this is not gravity sensor at work. If gravity sensor is at work, and turned screen leftwards or rightwards, 'xrandr -o normal' will not have any effect. - Expected behaviour: the desktop rotation is decided by gravity sensor, - or, without its input, defaults to normal. + Expected behaviour: the desktop rotation is decided by gravity sensor, or, without its input, defaults to normal. + --- + ApportVersion: 2.14.1-0ubuntu3.2 + Architecture: amd64 + CurrentDesktop: Unity + DistroRelease: Ubuntu 14.04 + InstallationDate: Installed on 2014-04-28 (38 days ago) + InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) + Package: linux (not installed) + Tags: trusty + Uname: Linux 3.15.0-031500rc5-generic x86_64 + UnreportableReason: The running kernel is not an Ubuntu kernel + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1326885/+attachment/4125982/+files/ProcEnviron.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Description changed: Running Ubuntu 14.04 on bModo12 (same hardware as WeTab). Right after login the screen rotates to rightwards (no matter what direction the screen is actually at). I had to run this everytime: $ xrandr -o normal Note this is not gravity sensor at work. If gravity sensor is at work, and turned screen leftwards or rightwards, 'xrandr -o normal' will not have any effect. - Expected behaviour: the desktop rotation is decided by gravity sensor, or, without its input, defaults to normal. - --- + Expected behaviour: the desktop rotation should be decided by gravity sensor, or, without its input, defaults to normal. If it is intended that even without gravity sensor input the desktop should rotate anyway, then it should do so since login screen, not to change orientation right after login. + --- ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2014-04-28 (38 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) Package: linux (not installed) Tags: trusty Uname: Linux 3.15.0-031500rc5-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True ** Description changed: Running Ubuntu 14.04 on bModo12 (same hardware as WeTab). Right after login the screen rotates to rightwards (no matter what direction the screen is actually at). I had to run this everytime: $ xrandr -o normal Note this is not gravity sensor at work. If gravity sensor is at work, and turned screen leftwards or rightwards, 'xrandr -o normal' will not have any effect. - Expected behaviour: the desktop rotation should be decided by gravity sensor, or, without its input, defaults to normal. If it is intended that even without gravity sensor input the desktop should rotate anyway, then it should do so since login screen, not to change orientation right after login. + Expected behaviour: the desktop rotation should be decided by gravity sensor, or, without its input, defaults to normal. If it is intended that even without gravity sensor input the desktop should rotate anyway (because it consider itself running on a tablet) then it should do so since login screen, not to change orientation right after login. --- ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2014-04-28 (38 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) Package: linux (not installed) Tags: trusty Uname: Linux 3.15.0-031500rc5-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1326885 Title: desktop start rotated Status in “linux” package in Ubuntu: Confirmed Bug description: Running Ubuntu 14.04 on bModo12 (same hardware as WeTab). Right after login the screen rotates to rightwards (no matter what direction the screen is actually at). I had to run this everytime: $ xrandr -o n
[Kernel-packages] [Bug 1326885] Re: desktop start rotated kernel-bug-exists-upstream
I was expecting you to ask me to try development kernel - I am a sysop and I do not think this is a kernel issue, more like you automatically require trying development kernel - so, in fact when I collect data I was already using development kernel. And yes for sure I experience this problem using Ubuntu's release kernel as well. Can you add to the workflow to check whether or not the bug report already uses latest kernel, before asking for testing on latest kernel? ** Tags added: kernel-bug-exists-upstream ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1326885 Title: desktop start rotated Status in “linux” package in Ubuntu: Confirmed Bug description: Running Ubuntu 14.04 on bModo12 (same hardware as WeTab). Right after login the screen rotates to rightwards (no matter what direction the screen is actually at). I had to run this everytime: $ xrandr -o normal Note this is not gravity sensor at work. If gravity sensor is at work, and turned screen leftwards or rightwards, 'xrandr -o normal' will not have any effect. Expected behaviour: the desktop rotation should be decided by gravity sensor, or, without its input, defaults to normal. If it is intended that even without gravity sensor input the desktop should rotate anyway (because it consider itself running on a tablet) then it should do so since login screen, not to change orientation right after login. --- ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2014-04-28 (38 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) Package: linux (not installed) Tags: trusty Uname: Linux 3.15.0-031500rc5-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1326885/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1123943] Re: Chrontel CH7036 chip not supported
The procedure on http://lackofalucidmind-en.blogspot.de/2014/01/hdmi- output.html if followed strictly except git-checking out latest code, not the specified revision, works on Ubuntu 14.04 64-bit too. Verified. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1123943 Title: Chrontel CH7036 chip not supported Status in “linux” package in Ubuntu: Triaged Bug description: I'm running a WeTab with ubuntu and the ch7036 chip is not supported. There is a driver for the chromebook (called chrontel), but that driver is more or less a hacked daemon that sends some data to the chip and gives me the following error message: Found device ID 0x56 Found revision ID 0x81 Mode 1366x786 (44) 1366y786, dot clock 6930 -Hsync -Vsync H: start 1414, end 1446, skew 0, total 1456 V: start 771, end 777, total 793 State: 0 Firmware size = 3295 bytes. State: 2 State: 3 Timeout waiting for MCU to return EDID CH7036 MCU ver 1.41, Device 56 rev 1 capability 0x1 EDID timed out: Ignore HPD because EDID failed just after firmware load Get EDOD Failed (initial block) using 640x480@60 Could not find a useful resolution. Maybe hardware problem. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-6.11-generic 3.8.0-rc7 Uname: Linux 3.8.0-6-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.8-0ubuntu4 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz Date: Wed Feb 13 10:46:06 2013 DistUpgraded: Fresh install DistroCodename: raring DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller [8086:a011] (prog-if 00 [VGA controller]) Subsystem: Device [1b0a:00c7] Subsystem: Device [1b0a:00c7] InstallationDate: Installed on 2013-02-08 (4 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2) MachineType: PEGATRON WeTab MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-6-generic root=UUID=7cedb257-8646-45d8-a06b-c1a32d485cec ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/19/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: Lucid-GE-133 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: WeTab dmi.board.vendor: PEGATRON dmi.board.version: 30011578 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 1 dmi.chassis.vendor: PEGATRON dmi.chassis.version: TT116A01 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrLucid-GE-133:bd11/19/2010:svnPEGATRON:pnWeTab:pvrTT116A01:rvnPEGATRON:rnWeTab:rvr30011578:cvnPEGATRON:ct1:cvrTT116A01: dmi.product.name: WeTab dmi.product.version: TT116A01 dmi.sys.vendor: PEGATRON version.compiz: compiz 1:0.9.9~daily13.02.08-0ubuntu1 version.libdrm2: libdrm2 2.4.42-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.13.2-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.2-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.6-0ubuntu2 xserver.bootTime: Wed Feb 13 10:45:09 2013 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.13.2-0ubuntu2 xserver.video_driver: intel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1123943/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1318639] [NEW] Bluetooth mouse connects but does not move pointer
Public bug reported: Ubuntu 14.04. Bluetooth add new device wizard finished without any error. Bluetooth applet shows Bluetooth enabled. The applet shows that the mouse is connected too, if user (me) click it once. It can auto- reconnect this way on reboot. Whenever it is 'connected', power applet can show the batter remains for the mouse - and when the mouse's batter depletes, the power applet knows it and report correctly. The problem: cursor doesn't move. In fact, if I boot into Windows 8.0 on the same host, the cursor moves. The same mouse works fine on Windows XP too.It doesn't have on/off switch. dmesg: Code: [ 129.914221] Bluetooth: HIDP (Human Interface Emulation) ver 1.2 [ 129.914256] Bluetooth: HIDP socket layer initialized [ 129.916595] hid-generic 0005:0A5C:0001.0005: unknown main item tag 0x0 [ 129.953134] input: Bluetooth Mouse as /devices/pci:00/:00:1d.1/usb6/6-1/6-1:1.0/bluetooth/hci0/hci0:21/input14 [ 129.954447] hid-generic 0005:0A5C:0001.0005: input,hidraw4: BLUETOOTH HID v0.1e Keyboard [Bluetooth Mouse] on 74:f0:6d:81:bd:72 The device mentioned in dmesg does not exist as a file node in that path (perhaps wasn't supposed to): Code: $ ls /devices/pci:00/:00:1d.1/usb6/6-1/6-1:1.0/bluetooth/hci0/hci0:21/input14 ls: no se puede acceder a /devices/pci:00/:00:1d.1/usb6/6-1/6-1:1.0/bluetooth/hci0/hci0:21/input14: No existe el archivo o el directorio XINPUT has: Code: $ xinput ⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)] ⎜ ↳ eGalax Inc. USB TouchController id=9[slave pointer (2)] ⎜ ↳ eGalax Inc. USB TouchController Pen id=10 [slave pointer (2)] ⎜ ↳ Logitech USB Trackballid=11 [slave pointer (2)] ⎜ ↳ Bluetooth Mouse id=17 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Button id=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Button id=8[slave keyboard (3)] ↳ Heng Yu Technology Poker II id=12 [slave keyboard (3)] ↳ Heng Yu Technology Poker II id=13 [slave keyboard (3)] ↳ USB 2.0 Cameraid=14 [slave keyboard (3)] ↳ Asus Laptop extra buttons id=15 [slave keyboard (3)] ↳ AT Translated Set 2 keyboard id=16 [slave keyboard (3)] Attempt to enable device id=17 has no effect. I am afraid it is always enabled: Code: $ xinput --enable 17 It seems the mouse device does not send any data to the host when the cursor not moving. The following CODE demonstrate that: 1. computer boots without mouse3 device (mouse not 'oiled' by Windows) 2. user click bluetooth mouse and mouse3 device come to exist, that means mouse3 is the USB mouse 3. but it doesn't generate any data when moving, compare to a real mouse mouse2 Code: $ ls by-idevent1 event12 event4 event7 js0 mouse1 by-path event10 event2 event5 event8 micemouse2 event0 event11 event3 event6 event9 mouse0 $ ls by-idevent1 event12 event3 event6 event9 mouse0 mouse3 by-path event10 event13 event4 event7 js0 mouse1 event0 event11 event2 event5 event8 micemouse2 $ sudo -i # od < /dev/input/mouse3 ^C # od < /dev/input/mouse2 000 177430 034000 17 174070 034377 177364 171070 034375 020 177766 171070 034375 176765 173070 034373 176367 174470 040 034374 175367 175070 034373 175775 176470 034375 177375 060 177470 034377 17 177470 014377 000377 176470 014377 100 000771 172430 014001 000764 172030 014002 000766 173030 120 014001 001371 175030 014001 000775 177030 014001 000377 ^C The most singular thing that happened is: in one occassion, I boot into Windows 8 and use the mouse, when I reboot back, the cursor go on moving for a few minutes and mute. It seems, using it in Windows 'oils' the mouse. But I couldn't repeatly reproduce this. I am very certain about this. The cursor doesn't move even right after the first time add-new- bluetooth device wizard quit successfully, the single one time it worked, is after Windows 8 oiled it. My devices are: $ lspci 00:00.0 Host bridge: Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx DMI Bridge 00:02.0 VGA compatible controller: Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller 00:02.1 Display controller: Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller 00:1a.0 USB controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #4 (rev 04) 00:1a.1 USB controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #5 (r
[Kernel-packages] [Bug 1318639] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1318639/+attachment/4110602/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1318639 Title: Bluetooth mouse connects but does not move pointer Status in “linux” package in Ubuntu: Confirmed Bug description: Ubuntu 14.04. Bluetooth add new device wizard finished without any error. Bluetooth applet shows Bluetooth enabled. The applet shows that the mouse is connected too, if user (me) click it once. It can auto- reconnect this way on reboot. Whenever it is 'connected', power applet can show the batter remains for the mouse - and when the mouse's batter depletes, the power applet knows it and report correctly. The problem: cursor doesn't move. In fact, if I boot into Windows 8.0 on the same host, the cursor moves. The same mouse works fine on Windows XP too.It doesn't have on/off switch. dmesg: Code: [ 129.914221] Bluetooth: HIDP (Human Interface Emulation) ver 1.2 [ 129.914256] Bluetooth: HIDP socket layer initialized [ 129.916595] hid-generic 0005:0A5C:0001.0005: unknown main item tag 0x0 [ 129.953134] input: Bluetooth Mouse as /devices/pci:00/:00:1d.1/usb6/6-1/6-1:1.0/bluetooth/hci0/hci0:21/input14 [ 129.954447] hid-generic 0005:0A5C:0001.0005: input,hidraw4: BLUETOOTH HID v0.1e Keyboard [Bluetooth Mouse] on 74:f0:6d:81:bd:72 The device mentioned in dmesg does not exist as a file node in that path (perhaps wasn't supposed to): Code: $ ls /devices/pci:00/:00:1d.1/usb6/6-1/6-1:1.0/bluetooth/hci0/hci0:21/input14 ls: no se puede acceder a /devices/pci:00/:00:1d.1/usb6/6-1/6-1:1.0/bluetooth/hci0/hci0:21/input14: No existe el archivo o el directorio XINPUT has: Code: $ xinput ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ eGalax Inc. USB TouchController id=9[slave pointer (2)] ⎜ ↳ eGalax Inc. USB TouchController Pen id=10 [slave pointer (2)] ⎜ ↳ Logitech USB Trackball id=11 [slave pointer (2)] ⎜ ↳ Bluetooth Mouse id=17 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Buttonid=8[slave keyboard (3)] ↳ Heng Yu Technology Poker II id=12 [slave keyboard (3)] ↳ Heng Yu Technology Poker II id=13 [slave keyboard (3)] ↳ USB 2.0 Camera id=14 [slave keyboard (3)] ↳ Asus Laptop extra buttons id=15 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=16 [slave keyboard (3)] Attempt to enable device id=17 has no effect. I am afraid it is always enabled: Code: $ xinput --enable 17 It seems the mouse device does not send any data to the host when the cursor not moving. The following CODE demonstrate that: 1. computer boots, /dev/inputs/mouse3 device does not exist 2. user click bluetooth mouse and /dev/inputs/mouse3 device come to exist, that means mouse3 is the bluetooth 3. but it doesn't generate any data when moving, compare to a real USB mouse mouse2 Code: $ ls by-idevent1 event12 event4 event7 js0 mouse1 by-path event10 event2 event5 event8 micemouse2 event0 event11 event3 event6 event9 mouse0 $ ls by-idevent1 event12 event3 event6 event9 mouse0 mouse3 by-path event10 event13 event4 event7 js0 mouse1 event0 event11 event2 event5 event8 micemouse2 $ sudo -i # od < /dev/input/mouse3 ^C # od < /dev/input/mouse2 000 177430 034000 17 174070 034377 177364 171070 034375 020 177766 171070 034375 176765 173070 034373 176367 174470 040 034374 175367 175070 034373 175775 176470 034375 177375 060 177470 034377 17 177470 014377 000377 176470 014377 100 000771 172430 014001 000764 172030 014002 000766 173030 120 014001 001371 175030 014001 000775 177030 014001 000377 ^C The most singular thing that happened is: in one occassion, I boot into Windows 8 and use the mouse, when I reboot back, the cursor go on moving for a few minutes and mute. It seems, using it in Windows 'oils' the mouse. But I couldn't repeatly reproduce this. I am very certain about this. The cursor doesn't move even right aft
[Kernel-packages] [Bug 1318639] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1318639/+attachment/4110605/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1318639 Title: Bluetooth mouse connects but does not move pointer Status in “linux” package in Ubuntu: Confirmed Bug description: Ubuntu 14.04. Bluetooth add new device wizard finished without any error. Bluetooth applet shows Bluetooth enabled. The applet shows that the mouse is connected too, if user (me) click it once. It can auto- reconnect this way on reboot. Whenever it is 'connected', power applet can show the batter remains for the mouse - and when the mouse's batter depletes, the power applet knows it and report correctly. The problem: cursor doesn't move. In fact, if I boot into Windows 8.0 on the same host, the cursor moves. The same mouse works fine on Windows XP too.It doesn't have on/off switch. dmesg: Code: [ 129.914221] Bluetooth: HIDP (Human Interface Emulation) ver 1.2 [ 129.914256] Bluetooth: HIDP socket layer initialized [ 129.916595] hid-generic 0005:0A5C:0001.0005: unknown main item tag 0x0 [ 129.953134] input: Bluetooth Mouse as /devices/pci:00/:00:1d.1/usb6/6-1/6-1:1.0/bluetooth/hci0/hci0:21/input14 [ 129.954447] hid-generic 0005:0A5C:0001.0005: input,hidraw4: BLUETOOTH HID v0.1e Keyboard [Bluetooth Mouse] on 74:f0:6d:81:bd:72 The device mentioned in dmesg does not exist as a file node in that path (perhaps wasn't supposed to): Code: $ ls /devices/pci:00/:00:1d.1/usb6/6-1/6-1:1.0/bluetooth/hci0/hci0:21/input14 ls: no se puede acceder a /devices/pci:00/:00:1d.1/usb6/6-1/6-1:1.0/bluetooth/hci0/hci0:21/input14: No existe el archivo o el directorio XINPUT has: Code: $ xinput ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ eGalax Inc. USB TouchController id=9[slave pointer (2)] ⎜ ↳ eGalax Inc. USB TouchController Pen id=10 [slave pointer (2)] ⎜ ↳ Logitech USB Trackball id=11 [slave pointer (2)] ⎜ ↳ Bluetooth Mouse id=17 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Buttonid=8[slave keyboard (3)] ↳ Heng Yu Technology Poker II id=12 [slave keyboard (3)] ↳ Heng Yu Technology Poker II id=13 [slave keyboard (3)] ↳ USB 2.0 Camera id=14 [slave keyboard (3)] ↳ Asus Laptop extra buttons id=15 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=16 [slave keyboard (3)] Attempt to enable device id=17 has no effect. I am afraid it is always enabled: Code: $ xinput --enable 17 It seems the mouse device does not send any data to the host when the cursor not moving. The following CODE demonstrate that: 1. computer boots, /dev/inputs/mouse3 device does not exist 2. user click bluetooth mouse and /dev/inputs/mouse3 device come to exist, that means mouse3 is the bluetooth 3. but it doesn't generate any data when moving, compare to a real USB mouse mouse2 Code: $ ls by-idevent1 event12 event4 event7 js0 mouse1 by-path event10 event2 event5 event8 micemouse2 event0 event11 event3 event6 event9 mouse0 $ ls by-idevent1 event12 event3 event6 event9 mouse0 mouse3 by-path event10 event13 event4 event7 js0 mouse1 event0 event11 event2 event5 event8 micemouse2 $ sudo -i # od < /dev/input/mouse3 ^C # od < /dev/input/mouse2 000 177430 034000 17 174070 034377 177364 171070 034375 020 177766 171070 034375 176765 173070 034373 176367 174470 040 034374 175367 175070 034373 175775 176470 034375 177375 060 177470 034377 17 177470 014377 000377 176470 014377 100 000771 172430 014001 000764 172030 014002 000766 173030 120 014001 001371 175030 014001 000775 177030 014001 000377 ^C The most singular thing that happened is: in one occassion, I boot into Windows 8 and use the mouse, when I reboot back, the cursor go on moving for a few minutes and mute. It seems, using it in Windows 'oils' the mouse. But I couldn't repeatly reproduce this. I am very certain about this. The cursor doesn't move even right after the first
[Kernel-packages] [Bug 1318639] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1318639/+attachment/4110601/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1318639 Title: Bluetooth mouse connects but does not move pointer Status in “linux” package in Ubuntu: Confirmed Bug description: Ubuntu 14.04. Bluetooth add new device wizard finished without any error. Bluetooth applet shows Bluetooth enabled. The applet shows that the mouse is connected too, if user (me) click it once. It can auto- reconnect this way on reboot. Whenever it is 'connected', power applet can show the batter remains for the mouse - and when the mouse's batter depletes, the power applet knows it and report correctly. The problem: cursor doesn't move. In fact, if I boot into Windows 8.0 on the same host, the cursor moves. The same mouse works fine on Windows XP too.It doesn't have on/off switch. dmesg: Code: [ 129.914221] Bluetooth: HIDP (Human Interface Emulation) ver 1.2 [ 129.914256] Bluetooth: HIDP socket layer initialized [ 129.916595] hid-generic 0005:0A5C:0001.0005: unknown main item tag 0x0 [ 129.953134] input: Bluetooth Mouse as /devices/pci:00/:00:1d.1/usb6/6-1/6-1:1.0/bluetooth/hci0/hci0:21/input14 [ 129.954447] hid-generic 0005:0A5C:0001.0005: input,hidraw4: BLUETOOTH HID v0.1e Keyboard [Bluetooth Mouse] on 74:f0:6d:81:bd:72 The device mentioned in dmesg does not exist as a file node in that path (perhaps wasn't supposed to): Code: $ ls /devices/pci:00/:00:1d.1/usb6/6-1/6-1:1.0/bluetooth/hci0/hci0:21/input14 ls: no se puede acceder a /devices/pci:00/:00:1d.1/usb6/6-1/6-1:1.0/bluetooth/hci0/hci0:21/input14: No existe el archivo o el directorio XINPUT has: Code: $ xinput ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ eGalax Inc. USB TouchController id=9[slave pointer (2)] ⎜ ↳ eGalax Inc. USB TouchController Pen id=10 [slave pointer (2)] ⎜ ↳ Logitech USB Trackball id=11 [slave pointer (2)] ⎜ ↳ Bluetooth Mouse id=17 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Buttonid=8[slave keyboard (3)] ↳ Heng Yu Technology Poker II id=12 [slave keyboard (3)] ↳ Heng Yu Technology Poker II id=13 [slave keyboard (3)] ↳ USB 2.0 Camera id=14 [slave keyboard (3)] ↳ Asus Laptop extra buttons id=15 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=16 [slave keyboard (3)] Attempt to enable device id=17 has no effect. I am afraid it is always enabled: Code: $ xinput --enable 17 It seems the mouse device does not send any data to the host when the cursor not moving. The following CODE demonstrate that: 1. computer boots, /dev/inputs/mouse3 device does not exist 2. user click bluetooth mouse and /dev/inputs/mouse3 device come to exist, that means mouse3 is the bluetooth 3. but it doesn't generate any data when moving, compare to a real USB mouse mouse2 Code: $ ls by-idevent1 event12 event4 event7 js0 mouse1 by-path event10 event2 event5 event8 micemouse2 event0 event11 event3 event6 event9 mouse0 $ ls by-idevent1 event12 event3 event6 event9 mouse0 mouse3 by-path event10 event13 event4 event7 js0 mouse1 event0 event11 event2 event5 event8 micemouse2 $ sudo -i # od < /dev/input/mouse3 ^C # od < /dev/input/mouse2 000 177430 034000 17 174070 034377 177364 171070 034375 020 177766 171070 034375 176765 173070 034373 176367 174470 040 034374 175367 175070 034373 175775 176470 034375 177375 060 177470 034377 17 177470 014377 000377 176470 014377 100 000771 172430 014001 000764 172030 014002 000766 173030 120 014001 001371 175030 014001 000775 177030 014001 000377 ^C The most singular thing that happened is: in one occassion, I boot into Windows 8 and use the mouse, when I reboot back, the cursor go on moving for a few minutes and mute. It seems, using it in Windows 'oils' the mouse. But I couldn't repeatly reproduce this. I am very certain about this. The cursor doesn't move even right after the first ti
[Kernel-packages] [Bug 1318639] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1318639/+attachment/4110604/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1318639 Title: Bluetooth mouse connects but does not move pointer Status in “linux” package in Ubuntu: Confirmed Bug description: Ubuntu 14.04. Bluetooth add new device wizard finished without any error. Bluetooth applet shows Bluetooth enabled. The applet shows that the mouse is connected too, if user (me) click it once. It can auto- reconnect this way on reboot. Whenever it is 'connected', power applet can show the batter remains for the mouse - and when the mouse's batter depletes, the power applet knows it and report correctly. The problem: cursor doesn't move. In fact, if I boot into Windows 8.0 on the same host, the cursor moves. The same mouse works fine on Windows XP too.It doesn't have on/off switch. dmesg: Code: [ 129.914221] Bluetooth: HIDP (Human Interface Emulation) ver 1.2 [ 129.914256] Bluetooth: HIDP socket layer initialized [ 129.916595] hid-generic 0005:0A5C:0001.0005: unknown main item tag 0x0 [ 129.953134] input: Bluetooth Mouse as /devices/pci:00/:00:1d.1/usb6/6-1/6-1:1.0/bluetooth/hci0/hci0:21/input14 [ 129.954447] hid-generic 0005:0A5C:0001.0005: input,hidraw4: BLUETOOTH HID v0.1e Keyboard [Bluetooth Mouse] on 74:f0:6d:81:bd:72 The device mentioned in dmesg does not exist as a file node in that path (perhaps wasn't supposed to): Code: $ ls /devices/pci:00/:00:1d.1/usb6/6-1/6-1:1.0/bluetooth/hci0/hci0:21/input14 ls: no se puede acceder a /devices/pci:00/:00:1d.1/usb6/6-1/6-1:1.0/bluetooth/hci0/hci0:21/input14: No existe el archivo o el directorio XINPUT has: Code: $ xinput ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ eGalax Inc. USB TouchController id=9[slave pointer (2)] ⎜ ↳ eGalax Inc. USB TouchController Pen id=10 [slave pointer (2)] ⎜ ↳ Logitech USB Trackball id=11 [slave pointer (2)] ⎜ ↳ Bluetooth Mouse id=17 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Buttonid=8[slave keyboard (3)] ↳ Heng Yu Technology Poker II id=12 [slave keyboard (3)] ↳ Heng Yu Technology Poker II id=13 [slave keyboard (3)] ↳ USB 2.0 Camera id=14 [slave keyboard (3)] ↳ Asus Laptop extra buttons id=15 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=16 [slave keyboard (3)] Attempt to enable device id=17 has no effect. I am afraid it is always enabled: Code: $ xinput --enable 17 It seems the mouse device does not send any data to the host when the cursor not moving. The following CODE demonstrate that: 1. computer boots, /dev/inputs/mouse3 device does not exist 2. user click bluetooth mouse and /dev/inputs/mouse3 device come to exist, that means mouse3 is the bluetooth 3. but it doesn't generate any data when moving, compare to a real USB mouse mouse2 Code: $ ls by-idevent1 event12 event4 event7 js0 mouse1 by-path event10 event2 event5 event8 micemouse2 event0 event11 event3 event6 event9 mouse0 $ ls by-idevent1 event12 event3 event6 event9 mouse0 mouse3 by-path event10 event13 event4 event7 js0 mouse1 event0 event11 event2 event5 event8 micemouse2 $ sudo -i # od < /dev/input/mouse3 ^C # od < /dev/input/mouse2 000 177430 034000 17 174070 034377 177364 171070 034375 020 177766 171070 034375 176765 173070 034373 176367 174470 040 034374 175367 175070 034373 175775 176470 034375 177375 060 177470 034377 17 177470 014377 000377 176470 014377 100 000771 172430 014001 000764 172030 014002 000766 173030 120 014001 001371 175030 014001 000775 177030 014001 000377 ^C The most singular thing that happened is: in one occassion, I boot into Windows 8 and use the mouse, when I reboot back, the cursor go on moving for a few minutes and mute. It seems, using it in Windows 'oils' the mouse. But I couldn't repeatly reproduce this. I am very certain about this. The cursor doesn't move even right after the first
[Kernel-packages] [Bug 1318639] BootDmesg.txt
apport information ** Attachment added: "BootDmesg.txt" https://bugs.launchpad.net/bugs/1318639/+attachment/4110600/+files/BootDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1318639 Title: Bluetooth mouse connects but does not move pointer Status in “linux” package in Ubuntu: Confirmed Bug description: Ubuntu 14.04. Bluetooth add new device wizard finished without any error. Bluetooth applet shows Bluetooth enabled. The applet shows that the mouse is connected too, if user (me) click it once. It can auto- reconnect this way on reboot. Whenever it is 'connected', power applet can show the batter remains for the mouse - and when the mouse's batter depletes, the power applet knows it and report correctly. The problem: cursor doesn't move. In fact, if I boot into Windows 8.0 on the same host, the cursor moves. The same mouse works fine on Windows XP too.It doesn't have on/off switch. dmesg: Code: [ 129.914221] Bluetooth: HIDP (Human Interface Emulation) ver 1.2 [ 129.914256] Bluetooth: HIDP socket layer initialized [ 129.916595] hid-generic 0005:0A5C:0001.0005: unknown main item tag 0x0 [ 129.953134] input: Bluetooth Mouse as /devices/pci:00/:00:1d.1/usb6/6-1/6-1:1.0/bluetooth/hci0/hci0:21/input14 [ 129.954447] hid-generic 0005:0A5C:0001.0005: input,hidraw4: BLUETOOTH HID v0.1e Keyboard [Bluetooth Mouse] on 74:f0:6d:81:bd:72 The device mentioned in dmesg does not exist as a file node in that path (perhaps wasn't supposed to): Code: $ ls /devices/pci:00/:00:1d.1/usb6/6-1/6-1:1.0/bluetooth/hci0/hci0:21/input14 ls: no se puede acceder a /devices/pci:00/:00:1d.1/usb6/6-1/6-1:1.0/bluetooth/hci0/hci0:21/input14: No existe el archivo o el directorio XINPUT has: Code: $ xinput ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ eGalax Inc. USB TouchController id=9[slave pointer (2)] ⎜ ↳ eGalax Inc. USB TouchController Pen id=10 [slave pointer (2)] ⎜ ↳ Logitech USB Trackball id=11 [slave pointer (2)] ⎜ ↳ Bluetooth Mouse id=17 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Buttonid=8[slave keyboard (3)] ↳ Heng Yu Technology Poker II id=12 [slave keyboard (3)] ↳ Heng Yu Technology Poker II id=13 [slave keyboard (3)] ↳ USB 2.0 Camera id=14 [slave keyboard (3)] ↳ Asus Laptop extra buttons id=15 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=16 [slave keyboard (3)] Attempt to enable device id=17 has no effect. I am afraid it is always enabled: Code: $ xinput --enable 17 It seems the mouse device does not send any data to the host when the cursor not moving. The following CODE demonstrate that: 1. computer boots, /dev/inputs/mouse3 device does not exist 2. user click bluetooth mouse and /dev/inputs/mouse3 device come to exist, that means mouse3 is the bluetooth 3. but it doesn't generate any data when moving, compare to a real USB mouse mouse2 Code: $ ls by-idevent1 event12 event4 event7 js0 mouse1 by-path event10 event2 event5 event8 micemouse2 event0 event11 event3 event6 event9 mouse0 $ ls by-idevent1 event12 event3 event6 event9 mouse0 mouse3 by-path event10 event13 event4 event7 js0 mouse1 event0 event11 event2 event5 event8 micemouse2 $ sudo -i # od < /dev/input/mouse3 ^C # od < /dev/input/mouse2 000 177430 034000 17 174070 034377 177364 171070 034375 020 177766 171070 034375 176765 173070 034373 176367 174470 040 034374 175367 175070 034373 175775 176470 034375 177375 060 177470 034377 17 177470 014377 000377 176470 014377 100 000771 172430 014001 000764 172030 014002 000766 173030 120 014001 001371 175030 014001 000775 177030 014001 000377 ^C The most singular thing that happened is: in one occassion, I boot into Windows 8 and use the mouse, when I reboot back, the cursor go on moving for a few minutes and mute. It seems, using it in Windows 'oils' the mouse. But I couldn't repeatly reproduce this. I am very certain about this. The cursor doesn't move even right after the
[Kernel-packages] [Bug 1318639] Re: Bluetooth mouse connects but does not move pointer
apport information ** Tags added: apport-collected trusty ** Description changed: Ubuntu 14.04. Bluetooth add new device wizard finished without any error. Bluetooth applet shows Bluetooth enabled. The applet shows that the mouse is connected too, if user (me) click it once. It can auto- reconnect this way on reboot. Whenever it is 'connected', power applet can show the batter remains for the mouse - and when the mouse's batter depletes, the power applet knows it and report correctly. The problem: cursor doesn't move. In fact, if I boot into Windows 8.0 on the same host, the cursor moves. The same mouse works fine on Windows XP too.It doesn't have on/off switch. dmesg: Code: [ 129.914221] Bluetooth: HIDP (Human Interface Emulation) ver 1.2 [ 129.914256] Bluetooth: HIDP socket layer initialized [ 129.916595] hid-generic 0005:0A5C:0001.0005: unknown main item tag 0x0 [ 129.953134] input: Bluetooth Mouse as /devices/pci:00/:00:1d.1/usb6/6-1/6-1:1.0/bluetooth/hci0/hci0:21/input14 [ 129.954447] hid-generic 0005:0A5C:0001.0005: input,hidraw4: BLUETOOTH HID v0.1e Keyboard [Bluetooth Mouse] on 74:f0:6d:81:bd:72 The device mentioned in dmesg does not exist as a file node in that path (perhaps wasn't supposed to): Code: $ ls /devices/pci:00/:00:1d.1/usb6/6-1/6-1:1.0/bluetooth/hci0/hci0:21/input14 ls: no se puede acceder a /devices/pci:00/:00:1d.1/usb6/6-1/6-1:1.0/bluetooth/hci0/hci0:21/input14: No existe el archivo o el directorio XINPUT has: Code: $ xinput ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ eGalax Inc. USB TouchController id=9[slave pointer (2)] ⎜ ↳ eGalax Inc. USB TouchController Pen id=10 [slave pointer (2)] ⎜ ↳ Logitech USB Trackball id=11 [slave pointer (2)] ⎜ ↳ Bluetooth Mouse id=17 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Buttonid=8[slave keyboard (3)] ↳ Heng Yu Technology Poker II id=12 [slave keyboard (3)] ↳ Heng Yu Technology Poker II id=13 [slave keyboard (3)] ↳ USB 2.0 Camera id=14 [slave keyboard (3)] ↳ Asus Laptop extra buttons id=15 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=16 [slave keyboard (3)] Attempt to enable device id=17 has no effect. I am afraid it is always enabled: Code: $ xinput --enable 17 It seems the mouse device does not send any data to the host when the cursor not moving. The following CODE demonstrate that: 1. computer boots without mouse3 device (mouse not 'oiled' by Windows) 2. user click bluetooth mouse and mouse3 device come to exist, that means mouse3 is the USB mouse 3. but it doesn't generate any data when moving, compare to a real mouse mouse2 Code: $ ls by-idevent1 event12 event4 event7 js0 mouse1 by-path event10 event2 event5 event8 micemouse2 event0 event11 event3 event6 event9 mouse0 $ ls by-idevent1 event12 event3 event6 event9 mouse0 mouse3 by-path event10 event13 event4 event7 js0 mouse1 event0 event11 event2 event5 event8 micemouse2 $ sudo -i # od < /dev/input/mouse3 ^C # od < /dev/input/mouse2 000 177430 034000 17 174070 034377 177364 171070 034375 020 177766 171070 034375 176765 173070 034373 176367 174470 040 034374 175367 175070 034373 175775 176470 034375 177375 060 177470 034377 17 177470 014377 000377 176470 014377 100 000771 172430 014001 000764 172030 014002 000766 173030 120 014001 001371 175030 014001 000775 177030 014001 000377 ^C The most singular thing that happened is: in one occassion, I boot into Windows 8 and use the mouse, when I reboot back, the cursor go on moving for a few minutes and mute. It seems, using it in Windows 'oils' the mouse. But I couldn't repeatly reproduce this. I am very certain about this. The cursor doesn't move even right after the first time add-new- bluetooth device wizard quit successfully, the single one time it worked, is after Windows 8 oiled it. My devices are: $ lspci 00:00.0 Host bridge: Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx DMI Bridge 00:02.0 VGA compatible controller: Intel Corporation Atom Processor D4xx
[Kernel-packages] [Bug 1318639] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1318639/+attachment/4110611/+files/RfKill.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1318639 Title: Bluetooth mouse connects but does not move pointer Status in “linux” package in Ubuntu: Confirmed Bug description: Ubuntu 14.04. Bluetooth add new device wizard finished without any error. Bluetooth applet shows Bluetooth enabled. The applet shows that the mouse is connected too, if user (me) click it once. It can auto- reconnect this way on reboot. Whenever it is 'connected', power applet can show the batter remains for the mouse - and when the mouse's batter depletes, the power applet knows it and report correctly. The problem: cursor doesn't move. In fact, if I boot into Windows 8.0 on the same host, the cursor moves. The same mouse works fine on Windows XP too.It doesn't have on/off switch. dmesg: Code: [ 129.914221] Bluetooth: HIDP (Human Interface Emulation) ver 1.2 [ 129.914256] Bluetooth: HIDP socket layer initialized [ 129.916595] hid-generic 0005:0A5C:0001.0005: unknown main item tag 0x0 [ 129.953134] input: Bluetooth Mouse as /devices/pci:00/:00:1d.1/usb6/6-1/6-1:1.0/bluetooth/hci0/hci0:21/input14 [ 129.954447] hid-generic 0005:0A5C:0001.0005: input,hidraw4: BLUETOOTH HID v0.1e Keyboard [Bluetooth Mouse] on 74:f0:6d:81:bd:72 The device mentioned in dmesg does not exist as a file node in that path (perhaps wasn't supposed to): Code: $ ls /devices/pci:00/:00:1d.1/usb6/6-1/6-1:1.0/bluetooth/hci0/hci0:21/input14 ls: no se puede acceder a /devices/pci:00/:00:1d.1/usb6/6-1/6-1:1.0/bluetooth/hci0/hci0:21/input14: No existe el archivo o el directorio XINPUT has: Code: $ xinput ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ eGalax Inc. USB TouchController id=9[slave pointer (2)] ⎜ ↳ eGalax Inc. USB TouchController Pen id=10 [slave pointer (2)] ⎜ ↳ Logitech USB Trackball id=11 [slave pointer (2)] ⎜ ↳ Bluetooth Mouse id=17 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Buttonid=8[slave keyboard (3)] ↳ Heng Yu Technology Poker II id=12 [slave keyboard (3)] ↳ Heng Yu Technology Poker II id=13 [slave keyboard (3)] ↳ USB 2.0 Camera id=14 [slave keyboard (3)] ↳ Asus Laptop extra buttons id=15 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=16 [slave keyboard (3)] Attempt to enable device id=17 has no effect. I am afraid it is always enabled: Code: $ xinput --enable 17 It seems the mouse device does not send any data to the host when the cursor not moving. The following CODE demonstrate that: 1. computer boots, /dev/inputs/mouse3 device does not exist 2. user click bluetooth mouse and /dev/inputs/mouse3 device come to exist, that means mouse3 is the bluetooth 3. but it doesn't generate any data when moving, compare to a real USB mouse mouse2 Code: $ ls by-idevent1 event12 event4 event7 js0 mouse1 by-path event10 event2 event5 event8 micemouse2 event0 event11 event3 event6 event9 mouse0 $ ls by-idevent1 event12 event3 event6 event9 mouse0 mouse3 by-path event10 event13 event4 event7 js0 mouse1 event0 event11 event2 event5 event8 micemouse2 $ sudo -i # od < /dev/input/mouse3 ^C # od < /dev/input/mouse2 000 177430 034000 17 174070 034377 177364 171070 034375 020 177766 171070 034375 176765 173070 034373 176367 174470 040 034374 175367 175070 034373 175775 176470 034375 177375 060 177470 034377 17 177470 014377 000377 176470 014377 100 000771 172430 014001 000764 172030 014002 000766 173030 120 014001 001371 175030 014001 000775 177030 014001 000377 ^C The most singular thing that happened is: in one occassion, I boot into Windows 8 and use the mouse, when I reboot back, the cursor go on moving for a few minutes and mute. It seems, using it in Windows 'oils' the mouse. But I couldn't repeatly reproduce this. I am very certain about this. The cursor doesn't move even right after the first
[Kernel-packages] [Bug 1318639] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1318639/+attachment/4110606/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1318639 Title: Bluetooth mouse connects but does not move pointer Status in “linux” package in Ubuntu: Confirmed Bug description: Ubuntu 14.04. Bluetooth add new device wizard finished without any error. Bluetooth applet shows Bluetooth enabled. The applet shows that the mouse is connected too, if user (me) click it once. It can auto- reconnect this way on reboot. Whenever it is 'connected', power applet can show the batter remains for the mouse - and when the mouse's batter depletes, the power applet knows it and report correctly. The problem: cursor doesn't move. In fact, if I boot into Windows 8.0 on the same host, the cursor moves. The same mouse works fine on Windows XP too.It doesn't have on/off switch. dmesg: Code: [ 129.914221] Bluetooth: HIDP (Human Interface Emulation) ver 1.2 [ 129.914256] Bluetooth: HIDP socket layer initialized [ 129.916595] hid-generic 0005:0A5C:0001.0005: unknown main item tag 0x0 [ 129.953134] input: Bluetooth Mouse as /devices/pci:00/:00:1d.1/usb6/6-1/6-1:1.0/bluetooth/hci0/hci0:21/input14 [ 129.954447] hid-generic 0005:0A5C:0001.0005: input,hidraw4: BLUETOOTH HID v0.1e Keyboard [Bluetooth Mouse] on 74:f0:6d:81:bd:72 The device mentioned in dmesg does not exist as a file node in that path (perhaps wasn't supposed to): Code: $ ls /devices/pci:00/:00:1d.1/usb6/6-1/6-1:1.0/bluetooth/hci0/hci0:21/input14 ls: no se puede acceder a /devices/pci:00/:00:1d.1/usb6/6-1/6-1:1.0/bluetooth/hci0/hci0:21/input14: No existe el archivo o el directorio XINPUT has: Code: $ xinput ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ eGalax Inc. USB TouchController id=9[slave pointer (2)] ⎜ ↳ eGalax Inc. USB TouchController Pen id=10 [slave pointer (2)] ⎜ ↳ Logitech USB Trackball id=11 [slave pointer (2)] ⎜ ↳ Bluetooth Mouse id=17 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Buttonid=8[slave keyboard (3)] ↳ Heng Yu Technology Poker II id=12 [slave keyboard (3)] ↳ Heng Yu Technology Poker II id=13 [slave keyboard (3)] ↳ USB 2.0 Camera id=14 [slave keyboard (3)] ↳ Asus Laptop extra buttons id=15 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=16 [slave keyboard (3)] Attempt to enable device id=17 has no effect. I am afraid it is always enabled: Code: $ xinput --enable 17 It seems the mouse device does not send any data to the host when the cursor not moving. The following CODE demonstrate that: 1. computer boots, /dev/inputs/mouse3 device does not exist 2. user click bluetooth mouse and /dev/inputs/mouse3 device come to exist, that means mouse3 is the bluetooth 3. but it doesn't generate any data when moving, compare to a real USB mouse mouse2 Code: $ ls by-idevent1 event12 event4 event7 js0 mouse1 by-path event10 event2 event5 event8 micemouse2 event0 event11 event3 event6 event9 mouse0 $ ls by-idevent1 event12 event3 event6 event9 mouse0 mouse3 by-path event10 event13 event4 event7 js0 mouse1 event0 event11 event2 event5 event8 micemouse2 $ sudo -i # od < /dev/input/mouse3 ^C # od < /dev/input/mouse2 000 177430 034000 17 174070 034377 177364 171070 034375 020 177766 171070 034375 176765 173070 034373 176367 174470 040 034374 175367 175070 034373 175775 176470 034375 177375 060 177470 034377 17 177470 014377 000377 176470 014377 100 000771 172430 014001 000764 172030 014002 000766 173030 120 014001 001371 175030 014001 000775 177030 014001 000377 ^C The most singular thing that happened is: in one occassion, I boot into Windows 8 and use the mouse, when I reboot back, the cursor go on moving for a few minutes and mute. It seems, using it in Windows 'oils' the mouse. But I couldn't repeatly reproduce this. I am very certain about this. The cursor doesn't move even right after
[Kernel-packages] [Bug 1318639] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1318639/+attachment/4110607/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1318639 Title: Bluetooth mouse connects but does not move pointer Status in “linux” package in Ubuntu: Confirmed Bug description: Ubuntu 14.04. Bluetooth add new device wizard finished without any error. Bluetooth applet shows Bluetooth enabled. The applet shows that the mouse is connected too, if user (me) click it once. It can auto- reconnect this way on reboot. Whenever it is 'connected', power applet can show the batter remains for the mouse - and when the mouse's batter depletes, the power applet knows it and report correctly. The problem: cursor doesn't move. In fact, if I boot into Windows 8.0 on the same host, the cursor moves. The same mouse works fine on Windows XP too.It doesn't have on/off switch. dmesg: Code: [ 129.914221] Bluetooth: HIDP (Human Interface Emulation) ver 1.2 [ 129.914256] Bluetooth: HIDP socket layer initialized [ 129.916595] hid-generic 0005:0A5C:0001.0005: unknown main item tag 0x0 [ 129.953134] input: Bluetooth Mouse as /devices/pci:00/:00:1d.1/usb6/6-1/6-1:1.0/bluetooth/hci0/hci0:21/input14 [ 129.954447] hid-generic 0005:0A5C:0001.0005: input,hidraw4: BLUETOOTH HID v0.1e Keyboard [Bluetooth Mouse] on 74:f0:6d:81:bd:72 The device mentioned in dmesg does not exist as a file node in that path (perhaps wasn't supposed to): Code: $ ls /devices/pci:00/:00:1d.1/usb6/6-1/6-1:1.0/bluetooth/hci0/hci0:21/input14 ls: no se puede acceder a /devices/pci:00/:00:1d.1/usb6/6-1/6-1:1.0/bluetooth/hci0/hci0:21/input14: No existe el archivo o el directorio XINPUT has: Code: $ xinput ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ eGalax Inc. USB TouchController id=9[slave pointer (2)] ⎜ ↳ eGalax Inc. USB TouchController Pen id=10 [slave pointer (2)] ⎜ ↳ Logitech USB Trackball id=11 [slave pointer (2)] ⎜ ↳ Bluetooth Mouse id=17 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Buttonid=8[slave keyboard (3)] ↳ Heng Yu Technology Poker II id=12 [slave keyboard (3)] ↳ Heng Yu Technology Poker II id=13 [slave keyboard (3)] ↳ USB 2.0 Camera id=14 [slave keyboard (3)] ↳ Asus Laptop extra buttons id=15 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=16 [slave keyboard (3)] Attempt to enable device id=17 has no effect. I am afraid it is always enabled: Code: $ xinput --enable 17 It seems the mouse device does not send any data to the host when the cursor not moving. The following CODE demonstrate that: 1. computer boots, /dev/inputs/mouse3 device does not exist 2. user click bluetooth mouse and /dev/inputs/mouse3 device come to exist, that means mouse3 is the bluetooth 3. but it doesn't generate any data when moving, compare to a real USB mouse mouse2 Code: $ ls by-idevent1 event12 event4 event7 js0 mouse1 by-path event10 event2 event5 event8 micemouse2 event0 event11 event3 event6 event9 mouse0 $ ls by-idevent1 event12 event3 event6 event9 mouse0 mouse3 by-path event10 event13 event4 event7 js0 mouse1 event0 event11 event2 event5 event8 micemouse2 $ sudo -i # od < /dev/input/mouse3 ^C # od < /dev/input/mouse2 000 177430 034000 17 174070 034377 177364 171070 034375 020 177766 171070 034375 176765 173070 034373 176367 174470 040 034374 175367 175070 034373 175775 176470 034375 177375 060 177470 034377 17 177470 014377 000377 176470 014377 100 000771 172430 014001 000764 172030 014002 000766 173030 120 014001 001371 175030 014001 000775 177030 014001 000377 ^C The most singular thing that happened is: in one occassion, I boot into Windows 8 and use the mouse, when I reboot back, the cursor go on moving for a few minutes and mute. It seems, using it in Windows 'oils' the mouse. But I couldn't repeatly reproduce this. I am very certain about this. The cursor doesn't move even right after
[Kernel-packages] [Bug 1318639] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1318639/+attachment/4110610/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1318639 Title: Bluetooth mouse connects but does not move pointer Status in “linux” package in Ubuntu: Confirmed Bug description: Ubuntu 14.04. Bluetooth add new device wizard finished without any error. Bluetooth applet shows Bluetooth enabled. The applet shows that the mouse is connected too, if user (me) click it once. It can auto- reconnect this way on reboot. Whenever it is 'connected', power applet can show the batter remains for the mouse - and when the mouse's batter depletes, the power applet knows it and report correctly. The problem: cursor doesn't move. In fact, if I boot into Windows 8.0 on the same host, the cursor moves. The same mouse works fine on Windows XP too.It doesn't have on/off switch. dmesg: Code: [ 129.914221] Bluetooth: HIDP (Human Interface Emulation) ver 1.2 [ 129.914256] Bluetooth: HIDP socket layer initialized [ 129.916595] hid-generic 0005:0A5C:0001.0005: unknown main item tag 0x0 [ 129.953134] input: Bluetooth Mouse as /devices/pci:00/:00:1d.1/usb6/6-1/6-1:1.0/bluetooth/hci0/hci0:21/input14 [ 129.954447] hid-generic 0005:0A5C:0001.0005: input,hidraw4: BLUETOOTH HID v0.1e Keyboard [Bluetooth Mouse] on 74:f0:6d:81:bd:72 The device mentioned in dmesg does not exist as a file node in that path (perhaps wasn't supposed to): Code: $ ls /devices/pci:00/:00:1d.1/usb6/6-1/6-1:1.0/bluetooth/hci0/hci0:21/input14 ls: no se puede acceder a /devices/pci:00/:00:1d.1/usb6/6-1/6-1:1.0/bluetooth/hci0/hci0:21/input14: No existe el archivo o el directorio XINPUT has: Code: $ xinput ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ eGalax Inc. USB TouchController id=9[slave pointer (2)] ⎜ ↳ eGalax Inc. USB TouchController Pen id=10 [slave pointer (2)] ⎜ ↳ Logitech USB Trackball id=11 [slave pointer (2)] ⎜ ↳ Bluetooth Mouse id=17 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Buttonid=8[slave keyboard (3)] ↳ Heng Yu Technology Poker II id=12 [slave keyboard (3)] ↳ Heng Yu Technology Poker II id=13 [slave keyboard (3)] ↳ USB 2.0 Camera id=14 [slave keyboard (3)] ↳ Asus Laptop extra buttons id=15 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=16 [slave keyboard (3)] Attempt to enable device id=17 has no effect. I am afraid it is always enabled: Code: $ xinput --enable 17 It seems the mouse device does not send any data to the host when the cursor not moving. The following CODE demonstrate that: 1. computer boots, /dev/inputs/mouse3 device does not exist 2. user click bluetooth mouse and /dev/inputs/mouse3 device come to exist, that means mouse3 is the bluetooth 3. but it doesn't generate any data when moving, compare to a real USB mouse mouse2 Code: $ ls by-idevent1 event12 event4 event7 js0 mouse1 by-path event10 event2 event5 event8 micemouse2 event0 event11 event3 event6 event9 mouse0 $ ls by-idevent1 event12 event3 event6 event9 mouse0 mouse3 by-path event10 event13 event4 event7 js0 mouse1 event0 event11 event2 event5 event8 micemouse2 $ sudo -i # od < /dev/input/mouse3 ^C # od < /dev/input/mouse2 000 177430 034000 17 174070 034377 177364 171070 034375 020 177766 171070 034375 176765 173070 034373 176367 174470 040 034374 175367 175070 034373 175775 176470 034375 177375 060 177470 034377 17 177470 014377 000377 176470 014377 100 000771 172430 014001 000764 172030 014002 000766 173030 120 014001 001371 175030 014001 000775 177030 014001 000377 ^C The most singular thing that happened is: in one occassion, I boot into Windows 8 and use the mouse, when I reboot back, the cursor go on moving for a few minutes and mute. It seems, using it in Windows 'oils' the mouse. But I couldn't repeatly reproduce this. I am very certain about this. The cursor doesn't move even right after the
[Kernel-packages] [Bug 1318639] UdevLog.txt
apport information ** Attachment added: "UdevLog.txt" https://bugs.launchpad.net/bugs/1318639/+attachment/4110613/+files/UdevLog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1318639 Title: Bluetooth mouse connects but does not move pointer Status in “linux” package in Ubuntu: Confirmed Bug description: Ubuntu 14.04. Bluetooth add new device wizard finished without any error. Bluetooth applet shows Bluetooth enabled. The applet shows that the mouse is connected too, if user (me) click it once. It can auto- reconnect this way on reboot. Whenever it is 'connected', power applet can show the batter remains for the mouse - and when the mouse's batter depletes, the power applet knows it and report correctly. The problem: cursor doesn't move. In fact, if I boot into Windows 8.0 on the same host, the cursor moves. The same mouse works fine on Windows XP too.It doesn't have on/off switch. dmesg: Code: [ 129.914221] Bluetooth: HIDP (Human Interface Emulation) ver 1.2 [ 129.914256] Bluetooth: HIDP socket layer initialized [ 129.916595] hid-generic 0005:0A5C:0001.0005: unknown main item tag 0x0 [ 129.953134] input: Bluetooth Mouse as /devices/pci:00/:00:1d.1/usb6/6-1/6-1:1.0/bluetooth/hci0/hci0:21/input14 [ 129.954447] hid-generic 0005:0A5C:0001.0005: input,hidraw4: BLUETOOTH HID v0.1e Keyboard [Bluetooth Mouse] on 74:f0:6d:81:bd:72 The device mentioned in dmesg does not exist as a file node in that path (perhaps wasn't supposed to): Code: $ ls /devices/pci:00/:00:1d.1/usb6/6-1/6-1:1.0/bluetooth/hci0/hci0:21/input14 ls: no se puede acceder a /devices/pci:00/:00:1d.1/usb6/6-1/6-1:1.0/bluetooth/hci0/hci0:21/input14: No existe el archivo o el directorio XINPUT has: Code: $ xinput ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ eGalax Inc. USB TouchController id=9[slave pointer (2)] ⎜ ↳ eGalax Inc. USB TouchController Pen id=10 [slave pointer (2)] ⎜ ↳ Logitech USB Trackball id=11 [slave pointer (2)] ⎜ ↳ Bluetooth Mouse id=17 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Buttonid=8[slave keyboard (3)] ↳ Heng Yu Technology Poker II id=12 [slave keyboard (3)] ↳ Heng Yu Technology Poker II id=13 [slave keyboard (3)] ↳ USB 2.0 Camera id=14 [slave keyboard (3)] ↳ Asus Laptop extra buttons id=15 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=16 [slave keyboard (3)] Attempt to enable device id=17 has no effect. I am afraid it is always enabled: Code: $ xinput --enable 17 It seems the mouse device does not send any data to the host when the cursor not moving. The following CODE demonstrate that: 1. computer boots, /dev/inputs/mouse3 device does not exist 2. user click bluetooth mouse and /dev/inputs/mouse3 device come to exist, that means mouse3 is the bluetooth 3. but it doesn't generate any data when moving, compare to a real USB mouse mouse2 Code: $ ls by-idevent1 event12 event4 event7 js0 mouse1 by-path event10 event2 event5 event8 micemouse2 event0 event11 event3 event6 event9 mouse0 $ ls by-idevent1 event12 event3 event6 event9 mouse0 mouse3 by-path event10 event13 event4 event7 js0 mouse1 event0 event11 event2 event5 event8 micemouse2 $ sudo -i # od < /dev/input/mouse3 ^C # od < /dev/input/mouse2 000 177430 034000 17 174070 034377 177364 171070 034375 020 177766 171070 034375 176765 173070 034373 176367 174470 040 034374 175367 175070 034373 175775 176470 034375 177375 060 177470 034377 17 177470 014377 000377 176470 014377 100 000771 172430 014001 000764 172030 014002 000766 173030 120 014001 001371 175030 014001 000775 177030 014001 000377 ^C The most singular thing that happened is: in one occassion, I boot into Windows 8 and use the mouse, when I reboot back, the cursor go on moving for a few minutes and mute. It seems, using it in Windows 'oils' the mouse. But I couldn't repeatly reproduce this. I am very certain about this. The cursor doesn't move even right after the fir
[Kernel-packages] [Bug 1318639] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1318639/+attachment/4110603/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1318639 Title: Bluetooth mouse connects but does not move pointer Status in “linux” package in Ubuntu: Confirmed Bug description: Ubuntu 14.04. Bluetooth add new device wizard finished without any error. Bluetooth applet shows Bluetooth enabled. The applet shows that the mouse is connected too, if user (me) click it once. It can auto- reconnect this way on reboot. Whenever it is 'connected', power applet can show the batter remains for the mouse - and when the mouse's batter depletes, the power applet knows it and report correctly. The problem: cursor doesn't move. In fact, if I boot into Windows 8.0 on the same host, the cursor moves. The same mouse works fine on Windows XP too.It doesn't have on/off switch. dmesg: Code: [ 129.914221] Bluetooth: HIDP (Human Interface Emulation) ver 1.2 [ 129.914256] Bluetooth: HIDP socket layer initialized [ 129.916595] hid-generic 0005:0A5C:0001.0005: unknown main item tag 0x0 [ 129.953134] input: Bluetooth Mouse as /devices/pci:00/:00:1d.1/usb6/6-1/6-1:1.0/bluetooth/hci0/hci0:21/input14 [ 129.954447] hid-generic 0005:0A5C:0001.0005: input,hidraw4: BLUETOOTH HID v0.1e Keyboard [Bluetooth Mouse] on 74:f0:6d:81:bd:72 The device mentioned in dmesg does not exist as a file node in that path (perhaps wasn't supposed to): Code: $ ls /devices/pci:00/:00:1d.1/usb6/6-1/6-1:1.0/bluetooth/hci0/hci0:21/input14 ls: no se puede acceder a /devices/pci:00/:00:1d.1/usb6/6-1/6-1:1.0/bluetooth/hci0/hci0:21/input14: No existe el archivo o el directorio XINPUT has: Code: $ xinput ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ eGalax Inc. USB TouchController id=9[slave pointer (2)] ⎜ ↳ eGalax Inc. USB TouchController Pen id=10 [slave pointer (2)] ⎜ ↳ Logitech USB Trackball id=11 [slave pointer (2)] ⎜ ↳ Bluetooth Mouse id=17 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Buttonid=8[slave keyboard (3)] ↳ Heng Yu Technology Poker II id=12 [slave keyboard (3)] ↳ Heng Yu Technology Poker II id=13 [slave keyboard (3)] ↳ USB 2.0 Camera id=14 [slave keyboard (3)] ↳ Asus Laptop extra buttons id=15 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=16 [slave keyboard (3)] Attempt to enable device id=17 has no effect. I am afraid it is always enabled: Code: $ xinput --enable 17 It seems the mouse device does not send any data to the host when the cursor not moving. The following CODE demonstrate that: 1. computer boots, /dev/inputs/mouse3 device does not exist 2. user click bluetooth mouse and /dev/inputs/mouse3 device come to exist, that means mouse3 is the bluetooth 3. but it doesn't generate any data when moving, compare to a real USB mouse mouse2 Code: $ ls by-idevent1 event12 event4 event7 js0 mouse1 by-path event10 event2 event5 event8 micemouse2 event0 event11 event3 event6 event9 mouse0 $ ls by-idevent1 event12 event3 event6 event9 mouse0 mouse3 by-path event10 event13 event4 event7 js0 mouse1 event0 event11 event2 event5 event8 micemouse2 $ sudo -i # od < /dev/input/mouse3 ^C # od < /dev/input/mouse2 000 177430 034000 17 174070 034377 177364 171070 034375 020 177766 171070 034375 176765 173070 034373 176367 174470 040 034374 175367 175070 034373 175775 176470 034375 177375 060 177470 034377 17 177470 014377 000377 176470 014377 100 000771 172430 014001 000764 172030 014002 000766 173030 120 014001 001371 175030 014001 000775 177030 014001 000377 ^C The most singular thing that happened is: in one occassion, I boot into Windows 8 and use the mouse, when I reboot back, the cursor go on moving for a few minutes and mute. It seems, using it in Windows 'oils' the mouse. But I couldn't repeatly reproduce this. I am very certain about this. The cursor doesn't move even right after the f
[Kernel-packages] [Bug 1318639] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1318639/+attachment/4110608/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1318639 Title: Bluetooth mouse connects but does not move pointer Status in “linux” package in Ubuntu: Confirmed Bug description: Ubuntu 14.04. Bluetooth add new device wizard finished without any error. Bluetooth applet shows Bluetooth enabled. The applet shows that the mouse is connected too, if user (me) click it once. It can auto- reconnect this way on reboot. Whenever it is 'connected', power applet can show the batter remains for the mouse - and when the mouse's batter depletes, the power applet knows it and report correctly. The problem: cursor doesn't move. In fact, if I boot into Windows 8.0 on the same host, the cursor moves. The same mouse works fine on Windows XP too.It doesn't have on/off switch. dmesg: Code: [ 129.914221] Bluetooth: HIDP (Human Interface Emulation) ver 1.2 [ 129.914256] Bluetooth: HIDP socket layer initialized [ 129.916595] hid-generic 0005:0A5C:0001.0005: unknown main item tag 0x0 [ 129.953134] input: Bluetooth Mouse as /devices/pci:00/:00:1d.1/usb6/6-1/6-1:1.0/bluetooth/hci0/hci0:21/input14 [ 129.954447] hid-generic 0005:0A5C:0001.0005: input,hidraw4: BLUETOOTH HID v0.1e Keyboard [Bluetooth Mouse] on 74:f0:6d:81:bd:72 The device mentioned in dmesg does not exist as a file node in that path (perhaps wasn't supposed to): Code: $ ls /devices/pci:00/:00:1d.1/usb6/6-1/6-1:1.0/bluetooth/hci0/hci0:21/input14 ls: no se puede acceder a /devices/pci:00/:00:1d.1/usb6/6-1/6-1:1.0/bluetooth/hci0/hci0:21/input14: No existe el archivo o el directorio XINPUT has: Code: $ xinput ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ eGalax Inc. USB TouchController id=9[slave pointer (2)] ⎜ ↳ eGalax Inc. USB TouchController Pen id=10 [slave pointer (2)] ⎜ ↳ Logitech USB Trackball id=11 [slave pointer (2)] ⎜ ↳ Bluetooth Mouse id=17 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Buttonid=8[slave keyboard (3)] ↳ Heng Yu Technology Poker II id=12 [slave keyboard (3)] ↳ Heng Yu Technology Poker II id=13 [slave keyboard (3)] ↳ USB 2.0 Camera id=14 [slave keyboard (3)] ↳ Asus Laptop extra buttons id=15 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=16 [slave keyboard (3)] Attempt to enable device id=17 has no effect. I am afraid it is always enabled: Code: $ xinput --enable 17 It seems the mouse device does not send any data to the host when the cursor not moving. The following CODE demonstrate that: 1. computer boots, /dev/inputs/mouse3 device does not exist 2. user click bluetooth mouse and /dev/inputs/mouse3 device come to exist, that means mouse3 is the bluetooth 3. but it doesn't generate any data when moving, compare to a real USB mouse mouse2 Code: $ ls by-idevent1 event12 event4 event7 js0 mouse1 by-path event10 event2 event5 event8 micemouse2 event0 event11 event3 event6 event9 mouse0 $ ls by-idevent1 event12 event3 event6 event9 mouse0 mouse3 by-path event10 event13 event4 event7 js0 mouse1 event0 event11 event2 event5 event8 micemouse2 $ sudo -i # od < /dev/input/mouse3 ^C # od < /dev/input/mouse2 000 177430 034000 17 174070 034377 177364 171070 034375 020 177766 171070 034375 176765 173070 034373 176367 174470 040 034374 175367 175070 034373 175775 176470 034375 177375 060 177470 034377 17 177470 014377 000377 176470 014377 100 000771 172430 014001 000764 172030 014002 000766 173030 120 014001 001371 175030 014001 000775 177030 014001 000377 ^C The most singular thing that happened is: in one occassion, I boot into Windows 8 and use the mouse, when I reboot back, the cursor go on moving for a few minutes and mute. It seems, using it in Windows 'oils' the mouse. But I couldn't repeatly reproduce this. I am very certain about this. The cursor doesn't move even right
[Kernel-packages] [Bug 1318639] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1318639/+attachment/4110614/+files/WifiSyslog.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Description changed: Ubuntu 14.04. Bluetooth add new device wizard finished without any error. Bluetooth applet shows Bluetooth enabled. The applet shows that the mouse is connected too, if user (me) click it once. It can auto- reconnect this way on reboot. Whenever it is 'connected', power applet can show the batter remains for the mouse - and when the mouse's batter depletes, the power applet knows it and report correctly. The problem: cursor doesn't move. In fact, if I boot into Windows 8.0 on the same host, the cursor moves. The same mouse works fine on Windows XP too.It doesn't have on/off switch. dmesg: Code: [ 129.914221] Bluetooth: HIDP (Human Interface Emulation) ver 1.2 [ 129.914256] Bluetooth: HIDP socket layer initialized [ 129.916595] hid-generic 0005:0A5C:0001.0005: unknown main item tag 0x0 [ 129.953134] input: Bluetooth Mouse as /devices/pci:00/:00:1d.1/usb6/6-1/6-1:1.0/bluetooth/hci0/hci0:21/input14 [ 129.954447] hid-generic 0005:0A5C:0001.0005: input,hidraw4: BLUETOOTH HID v0.1e Keyboard [Bluetooth Mouse] on 74:f0:6d:81:bd:72 The device mentioned in dmesg does not exist as a file node in that path (perhaps wasn't supposed to): Code: $ ls /devices/pci:00/:00:1d.1/usb6/6-1/6-1:1.0/bluetooth/hci0/hci0:21/input14 ls: no se puede acceder a /devices/pci:00/:00:1d.1/usb6/6-1/6-1:1.0/bluetooth/hci0/hci0:21/input14: No existe el archivo o el directorio XINPUT has: Code: $ xinput ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ eGalax Inc. USB TouchController id=9[slave pointer (2)] ⎜ ↳ eGalax Inc. USB TouchController Pen id=10 [slave pointer (2)] ⎜ ↳ Logitech USB Trackball id=11 [slave pointer (2)] ⎜ ↳ Bluetooth Mouse id=17 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] - ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] - ↳ Power Buttonid=6[slave keyboard (3)] - ↳ Video Bus id=7[slave keyboard (3)] - ↳ Power Buttonid=8[slave keyboard (3)] - ↳ Heng Yu Technology Poker II id=12 [slave keyboard (3)] - ↳ Heng Yu Technology Poker II id=13 [slave keyboard (3)] - ↳ USB 2.0 Camera id=14 [slave keyboard (3)] - ↳ Asus Laptop extra buttons id=15 [slave keyboard (3)] - ↳ AT Translated Set 2 keyboardid=16 [slave keyboard (3)] + ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] + ↳ Power Buttonid=6[slave keyboard (3)] + ↳ Video Bus id=7[slave keyboard (3)] + ↳ Power Buttonid=8[slave keyboard (3)] + ↳ Heng Yu Technology Poker II id=12 [slave keyboard (3)] + ↳ Heng Yu Technology Poker II id=13 [slave keyboard (3)] + ↳ USB 2.0 Camera id=14 [slave keyboard (3)] + ↳ Asus Laptop extra buttons id=15 [slave keyboard (3)] + ↳ AT Translated Set 2 keyboardid=16 [slave keyboard (3)] Attempt to enable device id=17 has no effect. I am afraid it is always enabled: Code: $ xinput --enable 17 It seems the mouse device does not send any data to the host when the cursor not moving. The following CODE demonstrate that: - 1. computer boots without mouse3 device (mouse not 'oiled' by Windows) - 2. user click bluetooth mouse and mouse3 device come to exist, that means mouse3 is the USB mouse - 3. but it doesn't generate any data when moving, compare to a real mouse mouse2 + 1. computer boots, /dev/inputs/mouse3 device does not exist + 2. user click bluetooth mouse and /dev/inputs/mouse3 device come to exist, that means mouse3 is the bluetooth + 3. but it doesn't generate any data when moving, compare to a real USB mouse mouse2 Code: $ ls by-idevent1 event12 event4 event7 js0 mouse1 by-path event10 event2 event5 event8 micemouse2 event0 event11 event3 event6 event9 mouse0 - $ ls + $ ls by-idevent1 event12 event3 event6 event9 mouse0 mouse3 by-path event10 event13 event4 event7 js0 mouse1
[Kernel-packages] [Bug 1318639] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1318639/+attachment/4110612/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1318639 Title: Bluetooth mouse connects but does not move pointer Status in “linux” package in Ubuntu: Confirmed Bug description: Ubuntu 14.04. Bluetooth add new device wizard finished without any error. Bluetooth applet shows Bluetooth enabled. The applet shows that the mouse is connected too, if user (me) click it once. It can auto- reconnect this way on reboot. Whenever it is 'connected', power applet can show the batter remains for the mouse - and when the mouse's batter depletes, the power applet knows it and report correctly. The problem: cursor doesn't move. In fact, if I boot into Windows 8.0 on the same host, the cursor moves. The same mouse works fine on Windows XP too.It doesn't have on/off switch. dmesg: Code: [ 129.914221] Bluetooth: HIDP (Human Interface Emulation) ver 1.2 [ 129.914256] Bluetooth: HIDP socket layer initialized [ 129.916595] hid-generic 0005:0A5C:0001.0005: unknown main item tag 0x0 [ 129.953134] input: Bluetooth Mouse as /devices/pci:00/:00:1d.1/usb6/6-1/6-1:1.0/bluetooth/hci0/hci0:21/input14 [ 129.954447] hid-generic 0005:0A5C:0001.0005: input,hidraw4: BLUETOOTH HID v0.1e Keyboard [Bluetooth Mouse] on 74:f0:6d:81:bd:72 The device mentioned in dmesg does not exist as a file node in that path (perhaps wasn't supposed to): Code: $ ls /devices/pci:00/:00:1d.1/usb6/6-1/6-1:1.0/bluetooth/hci0/hci0:21/input14 ls: no se puede acceder a /devices/pci:00/:00:1d.1/usb6/6-1/6-1:1.0/bluetooth/hci0/hci0:21/input14: No existe el archivo o el directorio XINPUT has: Code: $ xinput ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ eGalax Inc. USB TouchController id=9[slave pointer (2)] ⎜ ↳ eGalax Inc. USB TouchController Pen id=10 [slave pointer (2)] ⎜ ↳ Logitech USB Trackball id=11 [slave pointer (2)] ⎜ ↳ Bluetooth Mouse id=17 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Buttonid=8[slave keyboard (3)] ↳ Heng Yu Technology Poker II id=12 [slave keyboard (3)] ↳ Heng Yu Technology Poker II id=13 [slave keyboard (3)] ↳ USB 2.0 Camera id=14 [slave keyboard (3)] ↳ Asus Laptop extra buttons id=15 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=16 [slave keyboard (3)] Attempt to enable device id=17 has no effect. I am afraid it is always enabled: Code: $ xinput --enable 17 It seems the mouse device does not send any data to the host when the cursor not moving. The following CODE demonstrate that: 1. computer boots, /dev/inputs/mouse3 device does not exist 2. user click bluetooth mouse and /dev/inputs/mouse3 device come to exist, that means mouse3 is the bluetooth 3. but it doesn't generate any data when moving, compare to a real USB mouse mouse2 Code: $ ls by-idevent1 event12 event4 event7 js0 mouse1 by-path event10 event2 event5 event8 micemouse2 event0 event11 event3 event6 event9 mouse0 $ ls by-idevent1 event12 event3 event6 event9 mouse0 mouse3 by-path event10 event13 event4 event7 js0 mouse1 event0 event11 event2 event5 event8 micemouse2 $ sudo -i # od < /dev/input/mouse3 ^C # od < /dev/input/mouse2 000 177430 034000 17 174070 034377 177364 171070 034375 020 177766 171070 034375 176765 173070 034373 176367 174470 040 034374 175367 175070 034373 175775 176470 034375 177375 060 177470 034377 17 177470 014377 000377 176470 014377 100 000771 172430 014001 000764 172030 014002 000766 173030 120 014001 001371 175030 014001 000775 177030 014001 000377 ^C The most singular thing that happened is: in one occassion, I boot into Windows 8 and use the mouse, when I reboot back, the cursor go on moving for a few minutes and mute. It seems, using it in Windows 'oils' the mouse. But I couldn't repeatly reproduce this. I am very certain about this. The cursor doesn't move even right after the first
[Kernel-packages] [Bug 1318639] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1318639/+attachment/4110609/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1318639 Title: Bluetooth mouse connects but does not move pointer Status in “linux” package in Ubuntu: Confirmed Bug description: Ubuntu 14.04. Bluetooth add new device wizard finished without any error. Bluetooth applet shows Bluetooth enabled. The applet shows that the mouse is connected too, if user (me) click it once. It can auto- reconnect this way on reboot. Whenever it is 'connected', power applet can show the batter remains for the mouse - and when the mouse's batter depletes, the power applet knows it and report correctly. The problem: cursor doesn't move. In fact, if I boot into Windows 8.0 on the same host, the cursor moves. The same mouse works fine on Windows XP too.It doesn't have on/off switch. dmesg: Code: [ 129.914221] Bluetooth: HIDP (Human Interface Emulation) ver 1.2 [ 129.914256] Bluetooth: HIDP socket layer initialized [ 129.916595] hid-generic 0005:0A5C:0001.0005: unknown main item tag 0x0 [ 129.953134] input: Bluetooth Mouse as /devices/pci:00/:00:1d.1/usb6/6-1/6-1:1.0/bluetooth/hci0/hci0:21/input14 [ 129.954447] hid-generic 0005:0A5C:0001.0005: input,hidraw4: BLUETOOTH HID v0.1e Keyboard [Bluetooth Mouse] on 74:f0:6d:81:bd:72 The device mentioned in dmesg does not exist as a file node in that path (perhaps wasn't supposed to): Code: $ ls /devices/pci:00/:00:1d.1/usb6/6-1/6-1:1.0/bluetooth/hci0/hci0:21/input14 ls: no se puede acceder a /devices/pci:00/:00:1d.1/usb6/6-1/6-1:1.0/bluetooth/hci0/hci0:21/input14: No existe el archivo o el directorio XINPUT has: Code: $ xinput ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ eGalax Inc. USB TouchController id=9[slave pointer (2)] ⎜ ↳ eGalax Inc. USB TouchController Pen id=10 [slave pointer (2)] ⎜ ↳ Logitech USB Trackball id=11 [slave pointer (2)] ⎜ ↳ Bluetooth Mouse id=17 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Buttonid=8[slave keyboard (3)] ↳ Heng Yu Technology Poker II id=12 [slave keyboard (3)] ↳ Heng Yu Technology Poker II id=13 [slave keyboard (3)] ↳ USB 2.0 Camera id=14 [slave keyboard (3)] ↳ Asus Laptop extra buttons id=15 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=16 [slave keyboard (3)] Attempt to enable device id=17 has no effect. I am afraid it is always enabled: Code: $ xinput --enable 17 It seems the mouse device does not send any data to the host when the cursor not moving. The following CODE demonstrate that: 1. computer boots, /dev/inputs/mouse3 device does not exist 2. user click bluetooth mouse and /dev/inputs/mouse3 device come to exist, that means mouse3 is the bluetooth 3. but it doesn't generate any data when moving, compare to a real USB mouse mouse2 Code: $ ls by-idevent1 event12 event4 event7 js0 mouse1 by-path event10 event2 event5 event8 micemouse2 event0 event11 event3 event6 event9 mouse0 $ ls by-idevent1 event12 event3 event6 event9 mouse0 mouse3 by-path event10 event13 event4 event7 js0 mouse1 event0 event11 event2 event5 event8 micemouse2 $ sudo -i # od < /dev/input/mouse3 ^C # od < /dev/input/mouse2 000 177430 034000 17 174070 034377 177364 171070 034375 020 177766 171070 034375 176765 173070 034373 176367 174470 040 034374 175367 175070 034373 175775 176470 034375 177375 060 177470 034377 17 177470 014377 000377 176470 014377 100 000771 172430 014001 000764 172030 014002 000766 173030 120 014001 001371 175030 014001 000775 177030 014001 000377 ^C The most singular thing that happened is: in one occassion, I boot into Windows 8 and use the mouse, when I reboot back, the cursor go on moving for a few minutes and mute. It seems, using it in Windows 'oils' the mouse. But I couldn't repeatly reproduce this. I am very certain about this. The cursor doesn't move even right after
[Kernel-packages] [Bug 1318639] Re: Bluetooth mouse connects but does not move pointer
** Description changed: Ubuntu 14.04. Bluetooth add new device wizard finished without any error. Bluetooth applet shows Bluetooth enabled. The applet shows that the mouse is connected too, if user (me) click it once. It can auto- reconnect this way on reboot. Whenever it is 'connected', power applet can show the batter remains for the mouse - and when the mouse's batter depletes, the power applet knows it and report correctly. The problem: cursor doesn't move. In fact, if I boot into Windows 8.0 on the same host, the cursor moves. The same mouse works fine on Windows XP too.It doesn't have on/off switch. dmesg: Code: [ 129.914221] Bluetooth: HIDP (Human Interface Emulation) ver 1.2 [ 129.914256] Bluetooth: HIDP socket layer initialized [ 129.916595] hid-generic 0005:0A5C:0001.0005: unknown main item tag 0x0 [ 129.953134] input: Bluetooth Mouse as /devices/pci:00/:00:1d.1/usb6/6-1/6-1:1.0/bluetooth/hci0/hci0:21/input14 [ 129.954447] hid-generic 0005:0A5C:0001.0005: input,hidraw4: BLUETOOTH HID v0.1e Keyboard [Bluetooth Mouse] on 74:f0:6d:81:bd:72 The device mentioned in dmesg does not exist as a file node in that path (perhaps wasn't supposed to): Code: $ ls /devices/pci:00/:00:1d.1/usb6/6-1/6-1:1.0/bluetooth/hci0/hci0:21/input14 ls: no se puede acceder a /devices/pci:00/:00:1d.1/usb6/6-1/6-1:1.0/bluetooth/hci0/hci0:21/input14: No existe el archivo o el directorio XINPUT has: Code: $ xinput ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ eGalax Inc. USB TouchController id=9[slave pointer (2)] ⎜ ↳ eGalax Inc. USB TouchController Pen id=10 [slave pointer (2)] ⎜ ↳ Logitech USB Trackball id=11 [slave pointer (2)] ⎜ ↳ Bluetooth Mouse id=17 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Buttonid=8[slave keyboard (3)] ↳ Heng Yu Technology Poker II id=12 [slave keyboard (3)] ↳ Heng Yu Technology Poker II id=13 [slave keyboard (3)] ↳ USB 2.0 Camera id=14 [slave keyboard (3)] ↳ Asus Laptop extra buttons id=15 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=16 [slave keyboard (3)] Attempt to enable device id=17 has no effect. I am afraid it is always enabled: Code: $ xinput --enable 17 It seems the mouse device does not send any data to the host when the cursor not moving. The following CODE demonstrate that: 1. computer boots, /dev/inputs/mouse3 device does not exist 2. user click bluetooth mouse and /dev/inputs/mouse3 device come to exist, that means mouse3 is the bluetooth 3. but it doesn't generate any data when moving, compare to a real USB mouse mouse2 Code: $ ls by-idevent1 event12 event4 event7 js0 mouse1 by-path event10 event2 event5 event8 micemouse2 event0 event11 event3 event6 event9 mouse0 $ ls by-idevent1 event12 event3 event6 event9 mouse0 mouse3 by-path event10 event13 event4 event7 js0 mouse1 event0 event11 event2 event5 event8 micemouse2 $ sudo -i # od < /dev/input/mouse3 ^C # od < /dev/input/mouse2 000 177430 034000 17 174070 034377 177364 171070 034375 020 177766 171070 034375 176765 173070 034373 176367 174470 040 034374 175367 175070 034373 175775 176470 034375 177375 060 177470 034377 17 177470 014377 000377 176470 014377 100 000771 172430 014001 000764 172030 014002 000766 173030 120 014001 001371 175030 014001 000775 177030 014001 000377 ^C The most singular thing that happened is: in one occassion, I boot into Windows 8 and use the mouse, when I reboot back, the cursor go on moving for a few minutes and mute. It seems, using it in Windows 'oils' the mouse. But I couldn't repeatly reproduce this. I am very certain about this. The cursor doesn't move even right after the first time add-new- bluetooth device wizard quit successfully, the single one time it worked, is after Windows 8 oiled it. - My devices are: - - $ lspci - 00:00.0 Host bridge: Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx DMI Bridge - 00:02.0 VGA compatible controller: Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller - 00:02.1
[Kernel-packages] [Bug 1318639] Re: Bluetooth mouse connects but does not move pointer
** Description changed: Ubuntu 14.04. Bluetooth add new device wizard finished without any error. Bluetooth applet shows Bluetooth enabled. The applet shows that the mouse is connected too, if user (me) click it once. It can auto- reconnect this way on reboot. Whenever it is 'connected', power applet can show the batter remains for the mouse - and when the mouse's batter depletes, the power applet knows it and report correctly. The problem: cursor doesn't move. In fact, if I boot into Windows 8.0 on the same host, the cursor moves. The same mouse works fine on Windows XP too.It doesn't have on/off switch. dmesg: Code: [ 129.914221] Bluetooth: HIDP (Human Interface Emulation) ver 1.2 [ 129.914256] Bluetooth: HIDP socket layer initialized [ 129.916595] hid-generic 0005:0A5C:0001.0005: unknown main item tag 0x0 [ 129.953134] input: Bluetooth Mouse as /devices/pci:00/:00:1d.1/usb6/6-1/6-1:1.0/bluetooth/hci0/hci0:21/input14 [ 129.954447] hid-generic 0005:0A5C:0001.0005: input,hidraw4: BLUETOOTH HID v0.1e Keyboard [Bluetooth Mouse] on 74:f0:6d:81:bd:72 The device mentioned in dmesg does not exist as a file node in that path (perhaps wasn't supposed to): Code: $ ls /devices/pci:00/:00:1d.1/usb6/6-1/6-1:1.0/bluetooth/hci0/hci0:21/input14 ls: no se puede acceder a /devices/pci:00/:00:1d.1/usb6/6-1/6-1:1.0/bluetooth/hci0/hci0:21/input14: No existe el archivo o el directorio XINPUT has: Code: $ xinput ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ eGalax Inc. USB TouchController id=9[slave pointer (2)] ⎜ ↳ eGalax Inc. USB TouchController Pen id=10 [slave pointer (2)] ⎜ ↳ Logitech USB Trackball id=11 [slave pointer (2)] ⎜ ↳ Bluetooth Mouse id=17 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Buttonid=8[slave keyboard (3)] ↳ Heng Yu Technology Poker II id=12 [slave keyboard (3)] ↳ Heng Yu Technology Poker II id=13 [slave keyboard (3)] ↳ USB 2.0 Camera id=14 [slave keyboard (3)] ↳ Asus Laptop extra buttons id=15 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=16 [slave keyboard (3)] Attempt to enable device id=17 has no effect. I am afraid it is always enabled: Code: $ xinput --enable 17 It seems the mouse device does not send any data to the host when the cursor not moving. The following CODE demonstrate that: 1. computer boots, /dev/inputs/mouse3 device does not exist 2. user click bluetooth mouse and /dev/inputs/mouse3 device come to exist, that means mouse3 is the bluetooth 3. but it doesn't generate any data when moving, compare to a real USB mouse mouse2 Code: $ ls by-idevent1 event12 event4 event7 js0 mouse1 by-path event10 event2 event5 event8 micemouse2 event0 event11 event3 event6 event9 mouse0 $ ls by-idevent1 event12 event3 event6 event9 mouse0 mouse3 by-path event10 event13 event4 event7 js0 mouse1 event0 event11 event2 event5 event8 micemouse2 $ sudo -i # od < /dev/input/mouse3 ^C # od < /dev/input/mouse2 000 177430 034000 17 174070 034377 177364 171070 034375 020 177766 171070 034375 176765 173070 034373 176367 174470 040 034374 175367 175070 034373 175775 176470 034375 177375 060 177470 034377 17 177470 014377 000377 176470 014377 100 000771 172430 014001 000764 172030 014002 000766 173030 120 014001 001371 175030 014001 000775 177030 014001 000377 ^C The most singular thing that happened is: in one occassion, I boot into Windows 8 and use the mouse, when I reboot back, the cursor go on moving for a few minutes and mute. It seems, using it in Windows 'oils' the mouse. But I couldn't repeatly reproduce this. I am very certain about this. The cursor doesn't move even right after the first time add-new- bluetooth device wizard quit successfully, the single one time it worked, is after Windows 8 oiled it. + On another behavior: power applet seems to prevent the mouse going + sleep, which it does by itself in a few minutes in Windows - until all + power drains out from the mouse, but it is a trivial problem that I can + afford not to solve. + --- Ap
[Kernel-packages] [Bug 1318639] Re: Bluetooth mouse connects but does not move pointer
With the kernel you suggested, 3.15.0-031500rc5-generic, the bluetooth applet does not show up. If I manually enable bluetooth (it started inactive) in control panel, the user interface says "bluetooth inactive" even though the knob is turned on -> hints activation failed. The controls for adding new bluetooth devices are gray. There is of course no mouse-battery power indicator. ** Tags added: kernel-unable-to-test-upstream ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1318639 Title: Bluetooth mouse connects but does not move pointer Status in “linux” package in Ubuntu: Confirmed Bug description: Ubuntu 14.04. Bluetooth add new device wizard finished without any error. Bluetooth applet shows Bluetooth enabled. The applet shows that the mouse is connected too, if user (me) click it once. It can auto- reconnect this way on reboot. Whenever it is 'connected', power applet can show the batter remains for the mouse - and when the mouse's batter depletes, the power applet knows it and report correctly. The problem: cursor doesn't move. In fact, if I boot into Windows 8.0 on the same host, the cursor moves. The same mouse works fine on Windows XP too.It doesn't have on/off switch. dmesg: Code: [ 129.914221] Bluetooth: HIDP (Human Interface Emulation) ver 1.2 [ 129.914256] Bluetooth: HIDP socket layer initialized [ 129.916595] hid-generic 0005:0A5C:0001.0005: unknown main item tag 0x0 [ 129.953134] input: Bluetooth Mouse as /devices/pci:00/:00:1d.1/usb6/6-1/6-1:1.0/bluetooth/hci0/hci0:21/input14 [ 129.954447] hid-generic 0005:0A5C:0001.0005: input,hidraw4: BLUETOOTH HID v0.1e Keyboard [Bluetooth Mouse] on 74:f0:6d:81:bd:72 The device mentioned in dmesg does not exist as a file node in that path (perhaps wasn't supposed to): Code: $ ls /devices/pci:00/:00:1d.1/usb6/6-1/6-1:1.0/bluetooth/hci0/hci0:21/input14 ls: no se puede acceder a /devices/pci:00/:00:1d.1/usb6/6-1/6-1:1.0/bluetooth/hci0/hci0:21/input14: No existe el archivo o el directorio XINPUT has: Code: $ xinput ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ eGalax Inc. USB TouchController id=9[slave pointer (2)] ⎜ ↳ eGalax Inc. USB TouchController Pen id=10 [slave pointer (2)] ⎜ ↳ Logitech USB Trackball id=11 [slave pointer (2)] ⎜ ↳ Bluetooth Mouse id=17 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Buttonid=8[slave keyboard (3)] ↳ Heng Yu Technology Poker II id=12 [slave keyboard (3)] ↳ Heng Yu Technology Poker II id=13 [slave keyboard (3)] ↳ USB 2.0 Camera id=14 [slave keyboard (3)] ↳ Asus Laptop extra buttons id=15 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=16 [slave keyboard (3)] Attempt to enable device id=17 has no effect. I am afraid it is always enabled: Code: $ xinput --enable 17 It seems the mouse device does not send any data to the host when the cursor not moving. The following CODE demonstrate that: 1. computer boots, /dev/inputs/mouse3 device does not exist 2. user click bluetooth mouse and /dev/inputs/mouse3 device come to exist, that means mouse3 is the bluetooth 3. but it doesn't generate any data when moving, compare to a real USB mouse mouse2 Code: $ ls by-idevent1 event12 event4 event7 js0 mouse1 by-path event10 event2 event5 event8 micemouse2 event0 event11 event3 event6 event9 mouse0 $ ls by-idevent1 event12 event3 event6 event9 mouse0 mouse3 by-path event10 event13 event4 event7 js0 mouse1 event0 event11 event2 event5 event8 micemouse2 $ sudo -i # od < /dev/input/mouse3 ^C # od < /dev/input/mouse2 000 177430 034000 17 174070 034377 177364 171070 034375 020 177766 171070 034375 176765 173070 034373 176367 174470 040 034374 175367 175070 034373 175775 176470 034375 177375 060 177470 034377 17 177470 014377 000377 176470 014377 100 000771 172430 014001 000764 172030 014002 000766 173030 120 014001 001371 175030 014001 000775 177030 014001
[Kernel-packages] [Bug 1123943] Re: Chrontel CH7036 chip not supported
@carli I guess it is easier and more useful to push for a change from Debian side, since multiple desk distros depend on Debian. Maybe close this one and re-file it in Debian? I don't know packaging to try it myself. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1123943 Title: Chrontel CH7036 chip not supported Status in “linux” package in Ubuntu: Triaged Bug description: I'm running a WeTab with ubuntu and the ch7036 chip is not supported. There is a driver for the chromebook (called chrontel), but that driver is more or less a hacked daemon that sends some data to the chip and gives me the following error message: Found device ID 0x56 Found revision ID 0x81 Mode 1366x786 (44) 1366y786, dot clock 6930 -Hsync -Vsync H: start 1414, end 1446, skew 0, total 1456 V: start 771, end 777, total 793 State: 0 Firmware size = 3295 bytes. State: 2 State: 3 Timeout waiting for MCU to return EDID CH7036 MCU ver 1.41, Device 56 rev 1 capability 0x1 EDID timed out: Ignore HPD because EDID failed just after firmware load Get EDOD Failed (initial block) using 640x480@60 Could not find a useful resolution. Maybe hardware problem. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-6.11-generic 3.8.0-rc7 Uname: Linux 3.8.0-6-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.8-0ubuntu4 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz Date: Wed Feb 13 10:46:06 2013 DistUpgraded: Fresh install DistroCodename: raring DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller [8086:a011] (prog-if 00 [VGA controller]) Subsystem: Device [1b0a:00c7] Subsystem: Device [1b0a:00c7] InstallationDate: Installed on 2013-02-08 (4 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2) MachineType: PEGATRON WeTab MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-6-generic root=UUID=7cedb257-8646-45d8-a06b-c1a32d485cec ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/19/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: Lucid-GE-133 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: WeTab dmi.board.vendor: PEGATRON dmi.board.version: 30011578 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 1 dmi.chassis.vendor: PEGATRON dmi.chassis.version: TT116A01 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrLucid-GE-133:bd11/19/2010:svnPEGATRON:pnWeTab:pvrTT116A01:rvnPEGATRON:rnWeTab:rvr30011578:cvnPEGATRON:ct1:cvrTT116A01: dmi.product.name: WeTab dmi.product.version: TT116A01 dmi.sys.vendor: PEGATRON version.compiz: compiz 1:0.9.9~daily13.02.08-0ubuntu1 version.libdrm2: libdrm2 2.4.42-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.13.2-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.2-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.6-0ubuntu2 xserver.bootTime: Wed Feb 13 10:45:09 2013 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.13.2-0ubuntu2 xserver.video_driver: intel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1123943/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1322396] [NEW] light sensor misjudge ambience light
Public bug reported: Running Ubuntu 14.04 on bModo12 (same hardware as WeTab). When running on battery, the screen changes brightness frequently, by itself, while there are little change in ambience light. In fact, if I just place it stablly on the table and observe from distance, it turns bright and dark all by itself happyly, once a few seconds. It is unbearable to use. I installed brightness control applet "indicator-brightness", and hoped manual control overwrites automatic ambience light sensor. But no, automatic sensor overwrites manual setting. If I set brightness to 10, for example, it is bright for one second, and back to darkness. I urgenly need a workaround - a method to turn off light sensor and force always brightest light output. Kindly offer a workaround before solving this bug. Thanks! My hardware and system is the same when I reported bug 1318639 - and the bug always exists since I installed the OS in day 1. Inform me if you insist on a new machine-generated PC/OS information set. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1322396 Title: light sensor misjudge ambience light Status in “linux” package in Ubuntu: New Bug description: Running Ubuntu 14.04 on bModo12 (same hardware as WeTab). When running on battery, the screen changes brightness frequently, by itself, while there are little change in ambience light. In fact, if I just place it stablly on the table and observe from distance, it turns bright and dark all by itself happyly, once a few seconds. It is unbearable to use. I installed brightness control applet "indicator-brightness", and hoped manual control overwrites automatic ambience light sensor. But no, automatic sensor overwrites manual setting. If I set brightness to 10, for example, it is bright for one second, and back to darkness. I urgenly need a workaround - a method to turn off light sensor and force always brightest light output. Kindly offer a workaround before solving this bug. Thanks! My hardware and system is the same when I reported bug 1318639 - and the bug always exists since I installed the OS in day 1. Inform me if you insist on a new machine-generated PC/OS information set. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1322396/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1123943] Re: Chrontel CH7036 chip not supported
Did any one try to make this work on Ubuntu 14.04? On a different issue, does anyone know of a driver for Broadcom Crystal HD 1080p? VD920H it is, lspci lists: 02:00.0 Multimedia controller: Broadcom Corporation BCM70015 Video Decoder [Crystal HD] How can I take advantage of that with VLC or mplayer? I know it is off- topic, but googling 10 minutes there is no right place to discuss this issue. Maybe you can throw me a link and I´ll discuss it elsewhere. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1123943 Title: Chrontel CH7036 chip not supported Status in “linux” package in Ubuntu: Triaged Bug description: I'm running a WeTab with ubuntu and the ch7036 chip is not supported. There is a driver for the chromebook (called chrontel), but that driver is more or less a hacked daemon that sends some data to the chip and gives me the following error message: Found device ID 0x56 Found revision ID 0x81 Mode 1366x786 (44) 1366y786, dot clock 6930 -Hsync -Vsync H: start 1414, end 1446, skew 0, total 1456 V: start 771, end 777, total 793 State: 0 Firmware size = 3295 bytes. State: 2 State: 3 Timeout waiting for MCU to return EDID CH7036 MCU ver 1.41, Device 56 rev 1 capability 0x1 EDID timed out: Ignore HPD because EDID failed just after firmware load Get EDOD Failed (initial block) using 640x480@60 Could not find a useful resolution. Maybe hardware problem. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-6.11-generic 3.8.0-rc7 Uname: Linux 3.8.0-6-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.8-0ubuntu4 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz Date: Wed Feb 13 10:46:06 2013 DistUpgraded: Fresh install DistroCodename: raring DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller [8086:a011] (prog-if 00 [VGA controller]) Subsystem: Device [1b0a:00c7] Subsystem: Device [1b0a:00c7] InstallationDate: Installed on 2013-02-08 (4 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2) MachineType: PEGATRON WeTab MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-6-generic root=UUID=7cedb257-8646-45d8-a06b-c1a32d485cec ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/19/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: Lucid-GE-133 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: WeTab dmi.board.vendor: PEGATRON dmi.board.version: 30011578 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 1 dmi.chassis.vendor: PEGATRON dmi.chassis.version: TT116A01 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrLucid-GE-133:bd11/19/2010:svnPEGATRON:pnWeTab:pvrTT116A01:rvnPEGATRON:rnWeTab:rvr30011578:cvnPEGATRON:ct1:cvrTT116A01: dmi.product.name: WeTab dmi.product.version: TT116A01 dmi.sys.vendor: PEGATRON version.compiz: compiz 1:0.9.9~daily13.02.08-0ubuntu1 version.libdrm2: libdrm2 2.4.42-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.13.2-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.2-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.6-0ubuntu2 xserver.bootTime: Wed Feb 13 10:45:09 2013 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.13.2-0ubuntu2 xserver.video_driver: intel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1123943/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1123943] Re: Chrontel CH7036 chip not supported
A few days ago there was a post of a different workaround: Installing the Chrontel Ch7036/HDMI - Output on Ubuntu http://lackofalucidmind-en.blogspot.de/2014/01/hdmi-output.html I tried following the instruction myself and to my surprise once the executable is launched (/usr/sbin/ch7036_start) it turns off my HDMI which was originally on (I had rebooted to Windows and had turned it on, and rebooted to Linux while it is still on). Perhaps that's because I am not using a chrome book. I used an x86-64 tablet, bModo 12, designed for Windows 7. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1123943 Title: Chrontel CH7036 chip not supported Status in “linux” package in Ubuntu: Triaged Bug description: I'm running a WeTab with ubuntu and the ch7036 chip is not supported. There is a driver for the chromebook (called chrontel), but that driver is more or less a hacked daemon that sends some data to the chip and gives me the following error message: Found device ID 0x56 Found revision ID 0x81 Mode 1366x786 (44) 1366y786, dot clock 6930 -Hsync -Vsync H: start 1414, end 1446, skew 0, total 1456 V: start 771, end 777, total 793 State: 0 Firmware size = 3295 bytes. State: 2 State: 3 Timeout waiting for MCU to return EDID CH7036 MCU ver 1.41, Device 56 rev 1 capability 0x1 EDID timed out: Ignore HPD because EDID failed just after firmware load Get EDOD Failed (initial block) using 640x480@60 Could not find a useful resolution. Maybe hardware problem. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-6.11-generic 3.8.0-rc7 Uname: Linux 3.8.0-6-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.8-0ubuntu4 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz Date: Wed Feb 13 10:46:06 2013 DistUpgraded: Fresh install DistroCodename: raring DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller [8086:a011] (prog-if 00 [VGA controller]) Subsystem: Device [1b0a:00c7] Subsystem: Device [1b0a:00c7] InstallationDate: Installed on 2013-02-08 (4 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2) MachineType: PEGATRON WeTab MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-6-generic root=UUID=7cedb257-8646-45d8-a06b-c1a32d485cec ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/19/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: Lucid-GE-133 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: WeTab dmi.board.vendor: PEGATRON dmi.board.version: 30011578 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 1 dmi.chassis.vendor: PEGATRON dmi.chassis.version: TT116A01 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrLucid-GE-133:bd11/19/2010:svnPEGATRON:pnWeTab:pvrTT116A01:rvnPEGATRON:rnWeTab:rvr30011578:cvnPEGATRON:ct1:cvrTT116A01: dmi.product.name: WeTab dmi.product.version: TT116A01 dmi.sys.vendor: PEGATRON version.compiz: compiz 1:0.9.9~daily13.02.08-0ubuntu1 version.libdrm2: libdrm2 2.4.42-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.13.2-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.2-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.6-0ubuntu2 xserver.bootTime: Wed Feb 13 10:45:09 2013 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.13.2-0ubuntu2 xserver.video_driver: intel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1123943/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1123943] Re: Chrontel CH7036 chip not supported
If I had HDMI turned off to start with, your method would not turn it on. There was no error message in the complete process following your instruction, but HDMI display shows 'no signal'. $ sudo /usr/sbin/ch7036_start /usr/sbin/ch7036_monitor: starts Found device ID 0x56 Found revision ID 0x81 Mode 1024x768 (95) 1024x768, dot clock 6500 -Hsync -Vsync H: start 1048, end 1184, skew 0, total 1344 V: start 771, end 777, total 806 Firmware size = 3295 bytes. As said, the device works on Windows 7. I down-tuned the resolution, because even on Windows 7, the max resolution offered for HDMI is 1280x720, smaller than LVDS's native resolution and CH7036's advertised max resolution (both are 1366x768). As you can see the resolution is 1024x768, that means in Linux I down- tuned it even lower than Windows 7, because in xrandr, the next resolution below 1366x768 is 1024x768. I was rather surprised when I look up the specs of WeTab and found that bModo has exactly the same configuration, including CPU type, memory, hard disk space and resolution. It really look like bModo 12 is just another casing of WeTab. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1123943 Title: Chrontel CH7036 chip not supported Status in “linux” package in Ubuntu: Triaged Bug description: I'm running a WeTab with ubuntu and the ch7036 chip is not supported. There is a driver for the chromebook (called chrontel), but that driver is more or less a hacked daemon that sends some data to the chip and gives me the following error message: Found device ID 0x56 Found revision ID 0x81 Mode 1366x786 (44) 1366y786, dot clock 6930 -Hsync -Vsync H: start 1414, end 1446, skew 0, total 1456 V: start 771, end 777, total 793 State: 0 Firmware size = 3295 bytes. State: 2 State: 3 Timeout waiting for MCU to return EDID CH7036 MCU ver 1.41, Device 56 rev 1 capability 0x1 EDID timed out: Ignore HPD because EDID failed just after firmware load Get EDOD Failed (initial block) using 640x480@60 Could not find a useful resolution. Maybe hardware problem. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-6.11-generic 3.8.0-rc7 Uname: Linux 3.8.0-6-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.8-0ubuntu4 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz Date: Wed Feb 13 10:46:06 2013 DistUpgraded: Fresh install DistroCodename: raring DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller [8086:a011] (prog-if 00 [VGA controller]) Subsystem: Device [1b0a:00c7] Subsystem: Device [1b0a:00c7] InstallationDate: Installed on 2013-02-08 (4 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2) MachineType: PEGATRON WeTab MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-6-generic root=UUID=7cedb257-8646-45d8-a06b-c1a32d485cec ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/19/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: Lucid-GE-133 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: WeTab dmi.board.vendor: PEGATRON dmi.board.version: 30011578 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 1 dmi.chassis.vendor: PEGATRON dmi.chassis.version: TT116A01 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrLucid-GE-133:bd11/19/2010:svnPEGATRON:pnWeTab:pvrTT116A01:rvnPEGATRON:rnWeTab:rvr30011578:cvnPEGATRON:ct1:cvrTT116A01: dmi.product.name: WeTab dmi.product.version: TT116A01 dmi.sys.vendor: PEGATRON version.compiz: compiz 1:0.9.9~daily13.02.08-0ubuntu1 version.libdrm2: libdrm2 2.4.42-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.13.2-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.2-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.6-0ubuntu2 xserver.bootTime: Wed Feb 13 10:45:09 2013 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.13.2-0ubuntu2 xserver.vid
[Kernel-packages] [Bug 1326885] Re: desktop start rotated
I won't report again with latest kernel because (from my experience) I do not expect it to be solved (or that it solved because of people reporting bugs), but I still provide the following information to save the time for those who wish to find a workaround - I do not know a workaround, but I know the following would not work: The following methods would not prevent the desktop to rotate automatically after login: - delete /lib/udev/accelerometer - comment out the only line in /lib/udev/rules.d/61-accelerometer.rules Since the rotate-after-login does not alter input matrix, which is still horizental, touch-screen will be useless right after login, until you rotate the screen back (with xrandr -o randr). If, instead of preventing auto-rotate-after-login, you wish to rotate input matrix as well to make the machine at least usable, the following command would not work: $ xinput set-prop 9 --type=float "Coordinate Transformation Matrix" 0 -1 1 1 0 0 0 0 1 The effect of that command is zero: input matrix remain the same (horizental) while the screen is auto-rotated to vertical. If you wish to study the issue, a starting point is the accelerometer device, which can be found in /proc/bus/input/devices Find out the event device (in my case event4) then you can find out which driver drives it by: $ cat /sys/devices/platform/asus_laptop/input/input4/device/driver -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1326885 Title: desktop start rotated Status in “linux” package in Ubuntu: Incomplete Bug description: Running Ubuntu 14.04 on bModo12 (same hardware as WeTab). Right after login the screen rotates to rightwards (no matter what direction the screen is actually at). I had to run this everytime: $ xrandr -o normal Note this is not gravity sensor at work. If gravity sensor is at work, and turned screen leftwards or rightwards, 'xrandr -o normal' will not have any effect. Expected behaviour: the desktop rotation should be decided by gravity sensor, or, without its input, defaults to normal. If it is intended that even without gravity sensor input the desktop should rotate anyway (because it consider itself running on a tablet) then it should do so since login screen, not to change orientation right after login. --- ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2014-04-28 (38 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) Package: linux (not installed) Tags: trusty Uname: Linux 3.15.0-031500rc5-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1326885/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1326885] Re: desktop start rotated
I noticed this bug is marked as kernel-bug-exists-upstream -- I do not think this is a kernel bug, because everything was fine before login, a kernel bug should exhabit before login. Also that it only affects after- login, not affecting screen rotation during the session. But I am no expert to remove that tag with confidence. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1326885 Title: desktop start rotated Status in “linux” package in Ubuntu: Incomplete Bug description: Running Ubuntu 14.04 on bModo12 (same hardware as WeTab). Right after login the screen rotates to rightwards (no matter what direction the screen is actually at). I had to run this everytime: $ xrandr -o normal Note this is not gravity sensor at work. If gravity sensor is at work, and turned screen leftwards or rightwards, 'xrandr -o normal' will not have any effect. Expected behaviour: the desktop rotation should be decided by gravity sensor, or, without its input, defaults to normal. If it is intended that even without gravity sensor input the desktop should rotate anyway (because it consider itself running on a tablet) then it should do so since login screen, not to change orientation right after login. --- ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2014-04-28 (38 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) Package: linux (not installed) Tags: trusty Uname: Linux 3.15.0-031500rc5-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1326885/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1914858] [NEW] autoamtically suspend right after login - when booted with Thinkpad lid closed
Public bug reported: Reproduce: 0. Make sure the laptop is being charged by external power. 1. Boot with the lid closed (e.g. by starting reboot and close the lid). 2. When login screen presents, then login with password 3. Ubuntu 20.10 goes to sleep. Hit a key to wake it. dmesg attached at the end. 3 used to be reliably reproducible but now is sometimes reproducible. the dmesg was collected when this bug happened. Notes: - The laptop ThinkPad-X1-Carbon-6th is upgraded from 20.04. - The "Energy" setting in gnome-control-center is set to suspend only in battery mode. -- [ 76.499494] PM: suspend entry (s2idle) [ 76.536273] Filesystems sync: 0.036 seconds [ 76.544283] Freezing user space processes ... (elapsed 0.004 seconds) done. [ 76.548306] OOM killer disabled. [ 76.548307] Freezing remaining freezable tasks ... (elapsed 0.048 seconds) done. [ 76.597228] printk: Suspending console(s) (use no_console_suspend to debug) [ 76.717831] e1000e: EEE TX LPI TIMER: 0011 [ 79.349561] usb usb3: root hub lost power or was reset [ 79.349565] usb usb4: root hub lost power or was reset [ 79.480262] ACPI: EC: interrupt blocked [ 81.656861] ACPI: EC: interrupt unblocked [ 84.645047] usb usb3: root hub lost power or was reset [ 84.645052] usb usb4: root hub lost power or was reset [ 87.491291] e1000e :00:1f.6 enp0s31f6: Failed to disable ULP [ 87.603196] OOM killer enabled. [ 87.603198] Restarting tasks ... [ 87.603397] pci_bus :07: Allocating resources [ 87.603425] pci_bus :3b: Allocating resources [ 87.616426] mei_hdcp :00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound :00:02.0 (ops i915_hdcp_component_ops [i915]) [ 87.620031] done. [ 87.631119] thermal thermal_zone5: failed to read out thermal zone (-61) [ 87.775462] PM: suspend exit [ 87.906564] e1000e :00:1f.6 enp0s31f6: NIC Link is Down [ 88.108092] iwlwifi :02:00.0: Applying debug destination EXTERNAL_DRAM [ 88.241926] iwlwifi :02:00.0: Applying debug destination EXTERNAL_DRAM [ 88.309721] iwlwifi :02:00.0: FW already configured (0) - re-configuring [ 90.965280] e1000e :00:1f.6 enp0s31f6: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None [ 90.965334] IPv6: ADDRCONF(NETDEV_CHANGE): enp0s31f6: link becomes ready. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-42-generic 5.4.0-42.46 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair wl ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: a 2194 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Feb 6 21:48:20 2021 MachineType: LENOVO 20KHS1BP00 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=a77757cf-4a1b-4a8b-964a-bea19ccac95a ro nouveau.modeset=0 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.9 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/20/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET71W (1.46 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KHS1BP00 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.modalias: dmi:bvnLENOVO:bvrN23ET71W(1.46):bd02/20/2020:svnLENOVO:pn20KHS1BP00:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHS1BP00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 6th dmi.product.name: 20KHS1BP00 dmi.product.sku: LENOVO_MT_20KH_BU_Think_FM_ThinkPad X1 Carbon 6th dmi.product.version: ThinkPad X1 Carbon 6th dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1914858 Title: autoamtically suspend right after login - when booted with Thinkpad lid closed Status in linux package in Ubuntu: Confirmed Bug description: Reproduce: 0. Make sure the laptop is being charged by external power. 1. Boot with the lid closed (e.g. by starting reboot and close the lid). 2. When login screen presents, then login with password 3. Ubuntu 20.10 goes to sleep. Hit a key to wake it. dmesg attached at the end. 3 used to be reliably reproducible but now is sometimes reproducible. the dmesg was collected when this bug happened. Notes: - The laptop ThinkPad-X1-Carbon-6th is upgraded from 20.04. - The "Energy" setting in gnome-control-center is set to suspend only in battery mode. -- [ 76.499494] PM: suspend
[Kernel-packages] [Bug 1914858] Re: autoamtically suspend right after login - when booted with Thinkpad lid closed
** Description changed: - Reproduce: - 0. Make sure the laptop is being charged by external power. + 0. Make sure the laptop is being charged by an external power. + 1. Boot with the lid closed (e.g. by starting reboot and close the lid). + 2. When login screen presents, then login with password - 3. Ubuntu 20.10 goes to sleep. Hit a key to wake it. dmesg attached at the end. - 3 used to be reliably reproducible but now is sometimes reproducible. - the dmesg was collected when this bug happened. + 3a. Ubuntu 20.10 goes to sleep. Hit a key to wake it. dmesg attached at + the end. + + 3b. Ubuntu 20.04 sometimes go to sleep (10%). + + The following dmesg is collected from Ubuntu 20.10 where this can be reliably reproduced. However since I can't solve this I had to + downgrade to Ubuntu 20.04 where the attached debug info (produced + by `ubuntu-bug linux`) is collected. Notes: - - The laptop ThinkPad-X1-Carbon-6th is upgraded from 20.04. - - The "Energy" setting in gnome-control-center is set to suspend only in battery mode. + - The "Energy" setting in gnome-control-center is set to suspend only in + battery mode, but the bug is reproduced with external power. -- [ 76.499494] PM: suspend entry (s2idle) [ 76.536273] Filesystems sync: 0.036 seconds [ 76.544283] Freezing user space processes ... (elapsed 0.004 seconds) done. [ 76.548306] OOM killer disabled. [ 76.548307] Freezing remaining freezable tasks ... (elapsed 0.048 seconds) done. [ 76.597228] printk: Suspending console(s) (use no_console_suspend to debug) [ 76.717831] e1000e: EEE TX LPI TIMER: 0011 [ 79.349561] usb usb3: root hub lost power or was reset [ 79.349565] usb usb4: root hub lost power or was reset [ 79.480262] ACPI: EC: interrupt blocked [ 81.656861] ACPI: EC: interrupt unblocked [ 84.645047] usb usb3: root hub lost power or was reset [ 84.645052] usb usb4: root hub lost power or was reset [ 87.491291] e1000e :00:1f.6 enp0s31f6: Failed to disable ULP [ 87.603196] OOM killer enabled. [ 87.603198] Restarting tasks ... [ 87.603397] pci_bus :07: Allocating resources [ 87.603425] pci_bus :3b: Allocating resources [ 87.616426] mei_hdcp :00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound :00:02.0 (ops i915_hdcp_component_ops [i915]) [ 87.620031] done. [ 87.631119] thermal thermal_zone5: failed to read out thermal zone (-61) [ 87.775462] PM: suspend exit [ 87.906564] e1000e :00:1f.6 enp0s31f6: NIC Link is Down [ 88.108092] iwlwifi :02:00.0: Applying debug destination EXTERNAL_DRAM [ 88.241926] iwlwifi :02:00.0: Applying debug destination EXTERNAL_DRAM [ 88.309721] iwlwifi :02:00.0: FW already configured (0) - re-configuring [ 90.965280] e1000e :00:1f.6 enp0s31f6: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None [ 90.965334] IPv6: ADDRCONF(NETDEV_CHANGE): enp0s31f6: link becomes ready. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-42-generic 5.4.0-42.46 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair wl ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: a 2194 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: a 2194 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Feb 6 21:48:20 2021 MachineType: LENOVO 20KHS1BP00 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=a77757cf-4a1b-4a8b-964a-bea19ccac95a ro nouveau.modeset=0 RelatedPackageVersions: - linux-restricted-modules-5.4.0-42-generic N/A - linux-backports-modules-5.4.0-42-generic N/A - linux-firmware1.187.9 + linux-restricted-modules-5.4.0-42-generic N/A + linux-backports-modules-5.4.0-42-generic N/A + linux-firmware1.187.9 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/20/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET71W (1.46 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KHS1BP00 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.modalias: dmi:bvnLENOVO:bvrN23ET71W(1.46):bd02/20/2020:svnLENOVO:pn20KHS1BP00:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHS1BP00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 6th dmi.product.name: 20KHS1BP00 dmi.product.sku: LENOVO_MT_20KH_BU_Think_FM_ThinkPad X1 Carbon 6th dmi.product.version: ThinkPad X1 Carbon 6th dmi.sys.vendor: LENOVO -- You received this bug notification bec
