[Kernel-packages] [Bug 2036428] Re: Intel AX201 Bluetooth not available with 20230915.gitdfa11466-0ubuntu1

[Marcos Alano]

@Theo, maybe open another bug report?

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/2036428

Title:
  Intel AX201 Bluetooth not available with 20230915.gitdfa11466-0ubuntu1

Status in linux-firmware package in Ubuntu:
  Fix Released

Bug description:
  After upgrading linux-firmware to 20230915.gitdfa11466-0ubuntu1, my
  Intel AX201 Bluetooth controller is not available post-reboot.

  The device itself shows up here:

  $ lsusb | grep -i blue
  Bus 003 Device 005: ID 8087:0026 Intel Corp. AX201 Bluetooth

  But running e.g. `dmesg | grep -i bluetooth` returns no matches, and
  bluetoothctl finds no controllers.

  Reverting to the 20230323.gitbcdcfbcf-0ubuntu1.6 package restores full
  functionality.

  n.b. Possible duplicate of LP:2036348 - I am not in a position to
  confirm those symptoms yet, but will update later.

  Running mantic pre-release on amd64:

  $ lsb_release -rd
  No LSB modules are available.
  Description:  Ubuntu Mantic Minotaur (development branch)
  Release:  23.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2036428/+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 2036599] Re: Missing Bluetooth firmwares

[Marcos Alano]

I downloaded the previous version from Sep 15th and I could confirm the
firmware my chipset needs is not present, so that was the problem.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/2036599

Title:
  Missing Bluetooth firmwares

Status in linux-firmware package in Ubuntu:
  Incomplete

Bug description:
  The latest linux-firmware package version
  20230919.git3672ccab-0ubuntu1 is missing some Intel Bluetooth
  firmwares, in my case the firmware
  /lib/firmware/intel/ibt-0041-0041.sfi.zst, but others numbered like
  0040, etc. are missing too. I had to install an old version so my
  Bluetooth mouse could work.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-firmware 20230815.git0e048b06-0ubuntu1
  ProcVersionSignature: Ubuntu 6.5.0-6.6-generic 6.5.3
  Uname: Linux 6.5.0-6-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 19 09:42:39 2023
  Dependencies: firmware-sof-signed 2.2.6-1ubuntu1
  InstallationDate: Installed on 2021-11-26 (662 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-6-generic 
root=UUID=a15c1e1a-d162-4e98-98e6-bbc6e85a39c3 ro intel_iommu=on iommu=pt quiet 
splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-6-generic N/A
   linux-backports-modules-6.5.0-6-generic  N/A
   linux-firmware   20230815.git0e048b06-0ubuntu1
  SourcePackage: linux-firmware
  UpgradeStatus: Upgraded to mantic on 2023-08-18 (33 days ago)
  dmi.bios.date: 08/07/2023
  dmi.bios.release: 1.23
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.23.0
  dmi.board.name: 0836K6
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.23.0:bd08/07/2023:br1.23:svnDellInc.:pnDellG155511:pvr:rvnDellInc.:rn0836K6:rvrA00:cvnDellInc.:ct10:cvr:sku0A70:
  dmi.product.family: GSeries
  dmi.product.name: Dell G15 5511
  dmi.product.sku: 0A70
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2036599/+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 2036599] Re: Missing Bluetooth firmwares

[Marcos Alano]

Nice to know that was a real problem, not my incompetence. :) Yes, with
the latest package is working as intended. Thank you.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/2036599

Title:
  Missing Bluetooth firmwares

Status in linux-firmware package in Ubuntu:
  Incomplete

Bug description:
  The latest linux-firmware package version
  20230919.git3672ccab-0ubuntu1 is missing some Intel Bluetooth
  firmwares, in my case the firmware
  /lib/firmware/intel/ibt-0041-0041.sfi.zst, but others numbered like
  0040, etc. are missing too. I had to install an old version so my
  Bluetooth mouse could work.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-firmware 20230815.git0e048b06-0ubuntu1
  ProcVersionSignature: Ubuntu 6.5.0-6.6-generic 6.5.3
  Uname: Linux 6.5.0-6-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 19 09:42:39 2023
  Dependencies: firmware-sof-signed 2.2.6-1ubuntu1
  InstallationDate: Installed on 2021-11-26 (662 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-6-generic 
root=UUID=a15c1e1a-d162-4e98-98e6-bbc6e85a39c3 ro intel_iommu=on iommu=pt quiet 
splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-6-generic N/A
   linux-backports-modules-6.5.0-6-generic  N/A
   linux-firmware   20230815.git0e048b06-0ubuntu1
  SourcePackage: linux-firmware
  UpgradeStatus: Upgraded to mantic on 2023-08-18 (33 days ago)
  dmi.bios.date: 08/07/2023
  dmi.bios.release: 1.23
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.23.0
  dmi.board.name: 0836K6
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.23.0:bd08/07/2023:br1.23:svnDellInc.:pnDellG155511:pvr:rvnDellInc.:rn0836K6:rvrA00:cvnDellInc.:ct10:cvr:sku0A70:
  dmi.product.family: GSeries
  dmi.product.name: Dell G15 5511
  dmi.product.sku: 0A70
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2036599/+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 2036599] Re: Missing Bluetooth firmwares

[Marcos Alano]

@Juerg, no. I reinstalled the package and everything is working fine
now. Maybe some file system corruption? Anyway, I marked this issue as
incomplete.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/2036599

Title:
  Missing Bluetooth firmwares

Status in linux-firmware package in Ubuntu:
  Incomplete

Bug description:
  The latest linux-firmware package version
  20230919.git3672ccab-0ubuntu1 is missing some Intel Bluetooth
  firmwares, in my case the firmware
  /lib/firmware/intel/ibt-0041-0041.sfi.zst, but others numbered like
  0040, etc. are missing too. I had to install an old version so my
  Bluetooth mouse could work.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-firmware 20230815.git0e048b06-0ubuntu1
  ProcVersionSignature: Ubuntu 6.5.0-6.6-generic 6.5.3
  Uname: Linux 6.5.0-6-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 19 09:42:39 2023
  Dependencies: firmware-sof-signed 2.2.6-1ubuntu1
  InstallationDate: Installed on 2021-11-26 (662 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-6-generic 
root=UUID=a15c1e1a-d162-4e98-98e6-bbc6e85a39c3 ro intel_iommu=on iommu=pt quiet 
splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-6-generic N/A
   linux-backports-modules-6.5.0-6-generic  N/A
   linux-firmware   20230815.git0e048b06-0ubuntu1
  SourcePackage: linux-firmware
  UpgradeStatus: Upgraded to mantic on 2023-08-18 (33 days ago)
  dmi.bios.date: 08/07/2023
  dmi.bios.release: 1.23
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.23.0
  dmi.board.name: 0836K6
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.23.0:bd08/07/2023:br1.23:svnDellInc.:pnDellG155511:pvr:rvnDellInc.:rn0836K6:rvrA00:cvnDellInc.:ct10:cvr:sku0A70:
  dmi.product.family: GSeries
  dmi.product.name: Dell G15 5511
  dmi.product.sku: 0A70
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2036599/+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 2036599] Re: Missing Bluetooth firmwares

[Marcos Alano]

Hmmm... Strange... I got this problem a boot earlier:
set 19 08:53:11 glados kernel: Bluetooth: hci0: Debug lock is disabled
set 19 08:53:11 glados kernel: Bluetooth: hci0: Minimum firmware build 1 week 
10 2014
set 19 08:53:11 glados kernel: Bluetooth: hci0: Bootloader timestamp 2019.40 
buildtype 1 build 38
set 19 08:53:11 glados kernel: Bluetooth: hci0: Failed to load Intel firmware 
file intel/ibt-0041-0041.sfi (-2)
set 19 08:53:11 glados kernel: Bluetooth: hci0: Reading supported features 
failed (-56)
set 19 08:53:11 glados kernel: Bluetooth: hci0: Error reading debug features
set 19 08:53:11 glados kernel: Bluetooth: hci0: Failed to read MSFT supported 
features (-56)
And I checked and the firmware wasn't there, but I downgraded and upgraded 
again and seems it's back. Very strange...

** Changed in: linux-firmware (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/2036599

Title:
  Missing Bluetooth firmwares

Status in linux-firmware package in Ubuntu:
  Incomplete

Bug description:
  The latest linux-firmware package version
  20230919.git3672ccab-0ubuntu1 is missing some Intel Bluetooth
  firmwares, in my case the firmware
  /lib/firmware/intel/ibt-0041-0041.sfi.zst, but others numbered like
  0040, etc. are missing too. I had to install an old version so my
  Bluetooth mouse could work.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-firmware 20230815.git0e048b06-0ubuntu1
  ProcVersionSignature: Ubuntu 6.5.0-6.6-generic 6.5.3
  Uname: Linux 6.5.0-6-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 19 09:42:39 2023
  Dependencies: firmware-sof-signed 2.2.6-1ubuntu1
  InstallationDate: Installed on 2021-11-26 (662 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-6-generic 
root=UUID=a15c1e1a-d162-4e98-98e6-bbc6e85a39c3 ro intel_iommu=on iommu=pt quiet 
splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-6-generic N/A
   linux-backports-modules-6.5.0-6-generic  N/A
   linux-firmware   20230815.git0e048b06-0ubuntu1
  SourcePackage: linux-firmware
  UpgradeStatus: Upgraded to mantic on 2023-08-18 (33 days ago)
  dmi.bios.date: 08/07/2023
  dmi.bios.release: 1.23
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.23.0
  dmi.board.name: 0836K6
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.23.0:bd08/07/2023:br1.23:svnDellInc.:pnDellG155511:pvr:rvnDellInc.:rn0836K6:rvrA00:cvnDellInc.:ct10:cvr:sku0A70:
  dmi.product.family: GSeries
  dmi.product.name: Dell G15 5511
  dmi.product.sku: 0A70
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2036599/+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 2036599] Re: Missing Bluetooth firmwares

[Marcos Alano]

Hmmm... Strange... I got this problem a boot earlier:
set 19 08:53:11 glados kernel: Bluetooth: hci0: Debug lock is disabled
set 19 08:53:11 glados kernel: Bluetooth: hci0: Minimum firmware build 1 week 
10 2014
set 19 08:53:11 glados kernel: Bluetooth: hci0: Bootloader timestamp 2019.40 
buildtype 1 build 38
set 19 08:53:11 glados kernel: Bluetooth: hci0: Failed to load Intel firmware 
file intel/ibt-0041-0041.sfi (-2)
set 19 08:53:11 glados kernel: Bluetooth: hci0: Reading supported features 
failed (-56)
set 19 08:53:11 glados kernel: Bluetooth: hci0: Error reading debug features
set 19 08:53:11 glados kernel: Bluetooth: hci0: Failed to read MSFT supported 
features (-56)
And I checked and the firmware wasn't there, but I downgraded and upgraded 
again and seems it's back. Very strange...

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/2036599

Title:
  Missing Bluetooth firmwares

Status in linux-firmware package in Ubuntu:
  Incomplete

Bug description:
  The latest linux-firmware package version
  20230919.git3672ccab-0ubuntu1 is missing some Intel Bluetooth
  firmwares, in my case the firmware
  /lib/firmware/intel/ibt-0041-0041.sfi.zst, but others numbered like
  0040, etc. are missing too. I had to install an old version so my
  Bluetooth mouse could work.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-firmware 20230815.git0e048b06-0ubuntu1
  ProcVersionSignature: Ubuntu 6.5.0-6.6-generic 6.5.3
  Uname: Linux 6.5.0-6-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 19 09:42:39 2023
  Dependencies: firmware-sof-signed 2.2.6-1ubuntu1
  InstallationDate: Installed on 2021-11-26 (662 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-6-generic 
root=UUID=a15c1e1a-d162-4e98-98e6-bbc6e85a39c3 ro intel_iommu=on iommu=pt quiet 
splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-6-generic N/A
   linux-backports-modules-6.5.0-6-generic  N/A
   linux-firmware   20230815.git0e048b06-0ubuntu1
  SourcePackage: linux-firmware
  UpgradeStatus: Upgraded to mantic on 2023-08-18 (33 days ago)
  dmi.bios.date: 08/07/2023
  dmi.bios.release: 1.23
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.23.0
  dmi.board.name: 0836K6
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.23.0:bd08/07/2023:br1.23:svnDellInc.:pnDellG155511:pvr:rvnDellInc.:rn0836K6:rvrA00:cvnDellInc.:ct10:cvr:sku0A70:
  dmi.product.family: GSeries
  dmi.product.name: Dell G15 5511
  dmi.product.sku: 0A70
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2036599/+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 2036599] [NEW] Missing Bluetooth firmwares

[Marcos Alano]

Public bug reported:

The latest linux-firmware package version 20230919.git3672ccab-0ubuntu1
is missing some Intel Bluetooth firmwares, in my case the firmware
/lib/firmware/intel/ibt-0041-0041.sfi.zst, but others numbered like
0040, etc. are missing too. I had to install an old version so my
Bluetooth mouse could work.

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-firmware 20230815.git0e048b06-0ubuntu1
ProcVersionSignature: Ubuntu 6.5.0-6.6-generic 6.5.3
Uname: Linux 6.5.0-6-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Sep 19 09:42:39 2023
Dependencies: firmware-sof-signed 2.2.6-1ubuntu1
InstallationDate: Installed on 2021-11-26 (662 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-6-generic 
root=UUID=a15c1e1a-d162-4e98-98e6-bbc6e85a39c3 ro intel_iommu=on iommu=pt quiet 
splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-6.5.0-6-generic N/A
 linux-backports-modules-6.5.0-6-generic  N/A
 linux-firmware   20230815.git0e048b06-0ubuntu1
SourcePackage: linux-firmware
UpgradeStatus: Upgraded to mantic on 2023-08-18 (33 days ago)
dmi.bios.date: 08/07/2023
dmi.bios.release: 1.23
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.23.0
dmi.board.name: 0836K6
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.23.0:bd08/07/2023:br1.23:svnDellInc.:pnDellG155511:pvr:rvnDellInc.:rn0836K6:rvrA00:cvnDellInc.:ct10:cvr:sku0A70:
dmi.product.family: GSeries
dmi.product.name: Dell G15 5511
dmi.product.sku: 0A70
dmi.sys.vendor: Dell Inc.

** Affects: linux-firmware (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug mantic

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/2036599

Title:
  Missing Bluetooth firmwares

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  The latest linux-firmware package version
  20230919.git3672ccab-0ubuntu1 is missing some Intel Bluetooth
  firmwares, in my case the firmware
  /lib/firmware/intel/ibt-0041-0041.sfi.zst, but others numbered like
  0040, etc. are missing too. I had to install an old version so my
  Bluetooth mouse could work.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-firmware 20230815.git0e048b06-0ubuntu1
  ProcVersionSignature: Ubuntu 6.5.0-6.6-generic 6.5.3
  Uname: Linux 6.5.0-6-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 19 09:42:39 2023
  Dependencies: firmware-sof-signed 2.2.6-1ubuntu1
  InstallationDate: Installed on 2021-11-26 (662 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-6-generic 
root=UUID=a15c1e1a-d162-4e98-98e6-bbc6e85a39c3 ro intel_iommu=on iommu=pt quiet 
splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-6-generic N/A
   linux-backports-modules-6.5.0-6-generic  N/A
   linux-firmware   20230815.git0e048b06-0ubuntu1
  SourcePackage: linux-firmware
  UpgradeStatus: Upgraded to mantic on 2023-08-18 (33 days ago)
  dmi.bios.date: 08/07/2023
  dmi.bios.release: 1.23
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.23.0
  dmi.board.name: 0836K6
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.23.0:bd08/07/2023:br1.23:svnDellInc.:pnDellG155511:pvr:rvnDellInc.:rn0836K6:rvrA00:cvnDellInc.:ct10:cvr:sku0A70:
  dmi.product.family: GSeries
  dmi.product.name: Dell G15 5511
  dmi.product.sku: 0A70
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2036599/+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 2015289] [NEW] Websites getting lost the logged sessions

[Marcos Alano]

Public bug reported:

I updated to Firefox 112 from the Mozilla Team PPA and a strange thing
happened: Almost all (but not all) websites I had logged in (like
Netflix and Google) lost the session and I had to re-login. After I
rebooted the computer (forced closing the Firefox) I had to log in
again.

** Affects: firefox (Ubuntu)
 Importance: Undecided
 Status: New

** Package changed: linux (Ubuntu) => firefox (Ubuntu)

-- 
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/2015289

Title:
  Websites getting lost the logged sessions

Status in firefox package in Ubuntu:
  New

Bug description:
  I updated to Firefox 112 from the Mozilla Team PPA and a strange thing
  happened: Almost all (but not all) websites I had logged in (like
  Netflix and Google) lost the session and I had to re-login. After I
  rebooted the computer (forced closing the Firefox) I had to log in
  again.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2015289/+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 1991725] Re: fails to sign kernel modules

[Marcos Alano]

I tried the new version and worked perfectly.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
https://bugs.launchpad.net/bugs/1991725

Title:
  fails to sign kernel modules

Status in dkms package in Ubuntu:
  Confirmed

Bug description:
  Expected on kinetic:  dkms will sign built modules with MOK key if
  requested.

  What happens:
  dkms outputs "Binary kmod-sign not found, modules won't be signed"

  Fix:
  update dkms to 3.0.7:  https://github.com/dell/dkms/pull/242

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1991725/+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 1983409] Re: Please merge amd64-microcode 3.20220411.1 (main) from Debian unstable (non-free)

[Marcos Alano]

I was able to install both package with latest linux-firmware package:
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ NameVersion   Architecture Description
+++-===-=--=
ii  amd64-microcode 3.20220411.1ubuntu2   amd64Processor 
microcode firmware for AMD CPUs
ii  linux-firmware  20220819.git8413c63c-0ubuntu2 all  Firmware for 
Linux kernel drivers
(END)
It seems everything ok now.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1983409

Title:
  Please merge amd64-microcode 3.20220411.1 (main) from Debian unstable
  (non-free)

Status in amd64-microcode package in Ubuntu:
  Triaged
Status in linux-firmware package in Ubuntu:
  Fix Committed

Bug description:
  Request to update amd64-micrcode in kinetic from 3.20191218.1ubuntu2
  to 3.20220411.1ubuntu1.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/amd64-microcode/+bug/1983409/+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 1983409] Re: Please merge amd64-microcode 3.20220411.1 (main) from Debian unstable (non-free)

[Marcos Alano]

It seems amd64-microcode still conflicts with the latest version of 
linux-firmware, even with the breaks line.
➜ sudo apt install amd64-microcode  
agi='sudo apt install'
age='sudo apt'
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages were automatically installed and are no longer required:
  firmware-sof-signed linux-headers-generic-hwe-22.04
Use 'sudo apt autoremove' to remove them.
The following packages will be REMOVED:
  linux-firmware
The following NEW packages will be installed:
  amd64-microcode
0 upgraded, 1 newly installed, 1 to remove and 0 not upgraded.
Need to get 0 B/120 kB of archives.
After this operation, 924 MB disk space will be freed.
Do you want to continue? [Y/n] n
Abort.
My linux-firmware package is in the version 20220819.git8413c63c-0ubuntu1, that 
is theoretically higher than the version mentioned in the breaks field.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1983409

Title:
  Please merge amd64-microcode 3.20220411.1 (main) from Debian unstable
  (non-free)

Status in amd64-microcode package in Ubuntu:
  Triaged
Status in linux-firmware package in Ubuntu:
  Fix Committed

Bug description:
  Request to update amd64-micrcode in kinetic from 3.20191218.1ubuntu2
  to 3.20220411.1ubuntu1.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/amd64-microcode/+bug/1983409/+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 1982986] ProcEnviron.txt

[Marcos Alano]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1982986/+attachment/5605642/+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/1982986

Title:
  Black screen on Linux 5.19.0

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I'm trying to test Linux 5.19 using the packages released for Ubuntu Kinetic 
(the version I'm using right now), but I almost always get a black screen. 
First I thought it was NVIDIA kernel module (because I'm using NVIDIA GPU on my 
laptop) and after I changed to Intel GPU (with NVIDIA GPU as off-load) 
everything worked correctly, but the problem seems related to i915 module.
  --- 
  ProblemType: Bug
  ApportVersion: 2.22.0-0ubuntu4
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.10
  InstallationDate: Installed on 2021-11-26 (243 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  Tags:  kinetic
  Uname: Linux 5.18.14-051814-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: Upgraded to kinetic on 2022-06-14 (43 days ago)
  UserGroups: adm cdrom dip docker kvm libvirt lpadmin lxd plugdev sambashare 
sudo vboxusers
  _MarkForUpload: True
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2022-05-22T10:55:32.223191

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1982986/+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 1982986] Re: Black screen on Linux 5.19.0

[Marcos Alano]

apport information

** Tags added: apport-collected kinetic

** Description changed:

- I'm trying to test Linux 5.19 using the packages released for Ubuntu
- Kinetic (the version I'm using right now), but I almost always get a
- black screen. First I thought it was NVIDIA kernel module (because I'm
- using NVIDIA GPU on my laptop) and after I changed to Intel GPU (with
- NVIDIA GPU as off-load) everything worked correctly, but the problem
- seems related to i915 module.
+ I'm trying to test Linux 5.19 using the packages released for Ubuntu Kinetic 
(the version I'm using right now), but I almost always get a black screen. 
First I thought it was NVIDIA kernel module (because I'm using NVIDIA GPU on my 
laptop) and after I changed to Intel GPU (with NVIDIA GPU as off-load) 
everything worked correctly, but the problem seems related to i915 module.
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.22.0-0ubuntu4
+ Architecture: amd64
+ CasperMD5CheckResult: pass
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 22.10
+ InstallationDate: Installed on 2021-11-26 (243 days ago)
+ InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
+ NonfreeKernelModules: nvidia_modeset nvidia
+ Package: linux (not installed)
+ Tags:  kinetic
+ Uname: Linux 5.18.14-051814-generic x86_64
+ UnreportableReason: The running kernel is not an Ubuntu kernel
+ UpgradeStatus: Upgraded to kinetic on 2022-06-14 (43 days ago)
+ UserGroups: adm cdrom dip docker kvm libvirt lpadmin lxd plugdev sambashare 
sudo vboxusers
+ _MarkForUpload: True
+ modified.conffile..etc.default.apport:
+  # set this to 0 to disable apport, or to 1 to enable it
+  # you can temporarily override this with
+  # sudo service apport start force_start=1
+  enabled=0
+ mtime.conffile..etc.default.apport: 2022-05-22T10:55:32.223191

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1982986/+attachment/5605641/+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/1982986

Title:
  Black screen on Linux 5.19.0

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I'm trying to test Linux 5.19 using the packages released for Ubuntu Kinetic 
(the version I'm using right now), but I almost always get a black screen. 
First I thought it was NVIDIA kernel module (because I'm using NVIDIA GPU on my 
laptop) and after I changed to Intel GPU (with NVIDIA GPU as off-load) 
everything worked correctly, but the problem seems related to i915 module.
  --- 
  ProblemType: Bug
  ApportVersion: 2.22.0-0ubuntu4
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.10
  InstallationDate: Installed on 2021-11-26 (243 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  Tags:  kinetic
  Uname: Linux 5.18.14-051814-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: Upgraded to kinetic on 2022-06-14 (43 days ago)
  UserGroups: adm cdrom dip docker kvm libvirt lpadmin lxd plugdev sambashare 
sudo vboxusers
  _MarkForUpload: True
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2022-05-22T10:55:32.223191

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1982986/+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 1982986] Re: Black screen on Linux 5.19.0

[Marcos Alano]

journalctl -b -2 |grep i915  
jul 27 18:46:49 glados kernel: i915 :00:02.0: enabling device (0006 -> 0007)
jul 27 18:46:49 glados kernel: i915 :00:02.0: vgaarb: changed VGA decodes: 
olddecodes=io+mem,decodes=none:owns=mem
jul 27 18:46:49 glados kernel: i915 :00:02.0: [drm] Finished loading DMC 
firmware i915/tgl_dmc_ver2_12.bin (v2.12)
jul 27 18:46:49 glados kernel: mei_hdcp 
:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound :00:02.0 (ops 
i915_hdcp_component_ops [i915])
jul 27 18:46:49 glados kernel: i915 :00:02.0: [drm] failed to retrieve link 
info, disabling eDP
jul 27 18:46:49 glados kernel: mei_pxp 
:00:16.0-fbf6fcf1-96cf-4e2e-a6a6-1bab8cbe36b1: bound :00:02.0 (ops 
i915_pxp_tee_component_ops [i915])
jul 27 18:46:49 glados kernel: i915 :00:02.0: [drm] Protected Xe Path (PXP) 
protected content support initialized
jul 27 18:46:51 glados kernel: [drm] Initialized i915 1.6.0 20201103 for 
:00:02.0 on minor 0
jul 27 18:46:51 glados kernel: sof-audio-pci-intel-tgl :00:1f.3: bound 
:00:02.0 (ops i915_audio_component_bind_ops [i915])
jul 27 18:46:51 glados kernel: i915 :00:02.0: [drm] Cannot find any crtc or 
sizes
jul 27 18:46:51 glados kernel: i915 :00:02.0: [drm] Cannot find any crtc or 
sizes

-- 
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/1982986

Title:
  Black screen on Linux 5.19.0

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I'm trying to test Linux 5.19 using the packages released for Ubuntu
  Kinetic (the version I'm using right now), but I almost always get a
  black screen. First I thought it was NVIDIA kernel module (because I'm
  using NVIDIA GPU on my laptop) and after I changed to Intel GPU (with
  NVIDIA GPU as off-load) everything worked correctly, but the problem
  seems related to i915 module.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1982986/+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 1982986] Re: Black screen on Linux 5.19.0

[Marcos Alano]

Added the Linux boot messages when booting with Intel GPU

** Attachment added: "kernel-5.19.0-intel.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1982986/+attachment/5605639/+files/kernel-5.19.0-intel.log

-- 
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/1982986

Title:
  Black screen on Linux 5.19.0

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I'm trying to test Linux 5.19 using the packages released for Ubuntu
  Kinetic (the version I'm using right now), but I almost always get a
  black screen. First I thought it was NVIDIA kernel module (because I'm
  using NVIDIA GPU on my laptop) and after I changed to Intel GPU (with
  NVIDIA GPU as off-load) everything worked correctly, but the problem
  seems related to i915 module.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1982986/+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 1982986] [NEW] Black screen on Linux 5.19.0

[Marcos Alano]

Public bug reported:

I'm trying to test Linux 5.19 using the packages released for Ubuntu
Kinetic (the version I'm using right now), but I almost always get a
black screen. First I thought it was NVIDIA kernel module (because I'm
using NVIDIA GPU on my laptop) and after I changed to Intel GPU (with
NVIDIA GPU as off-load) everything worked correctly, but the problem
seems related to i915 module.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Incomplete

** Attachment added: "kernel-5.19.0.log"
   
https://bugs.launchpad.net/bugs/1982986/+attachment/5605638/+files/kernel-5.19.0.log

-- 
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/1982986

Title:
  Black screen on Linux 5.19.0

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I'm trying to test Linux 5.19 using the packages released for Ubuntu
  Kinetic (the version I'm using right now), but I almost always get a
  black screen. First I thought it was NVIDIA kernel module (because I'm
  using NVIDIA GPU on my laptop) and after I changed to Intel GPU (with
  NVIDIA GPU as off-load) everything worked correctly, but the problem
  seems related to i915 module.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1982986/+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 1969247] Re: fallocate with FALLOC_FL_ZERO_RANGE produces zero-size files on zfs in Jammy

[Marcos Alano]

In deed. It's a good question why it is taking so long between proposed
and updates repositories. Anyone knows why the delay?

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1969247

Title:
  fallocate with FALLOC_FL_ZERO_RANGE produces zero-size files on zfs in
  Jammy

Status in Native ZFS for Linux:
  Fix Released
Status in mysql-8.0 package in Ubuntu:
  Invalid
Status in zfs-linux package in Ubuntu:
  Fix Released
Status in zfs-linux source package in Jammy:
  Fix Committed

Bug description:
  [Summary]

  When running Jammy on zfs or LXD with a zfs pool on a Jammy host,
  fallocate creates a zero-sized file.

  The issue was originally found when installing mysql on LXD, where
  fallocate would create a zero-sized ib_logfile1 file. The original
  information in this bug is based on that.

  [Steps to Reproduce]

  touch foo.img
  fallocate -z -l 10M foo.img
  ls -la foo.img

  On a non-zfs Jammy system this will show something like:
  -rw-r--r-- 1 root root 10M ...

  while on zfs it will show:
  -rw-rw-r-- 1 root root 0 ...

  [Original Description]
  I came across this error when testing various mysql setups in an LXD 
container and managed to reproduce it consistently. I'm unable to reproduce on 
Ubuntu desktop or server though since the prerequisites are probably handled 
properly there.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: mysql-server-8.0 8.0.28-0ubuntu0.20.04.3
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.23
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Apr 15 21:31:09 2022
  Dmesg:

  ErrorMessage: installed mysql-server-8.0 package post-installation script 
subprocess returned error exit status 1
  KernLog:

  Logs.var.log.daemon.log:

  MySQLConf.etc.mysql.conf.d.mysql.cnf: [mysql]
  MySQLConf.etc.mysql.conf.d.mysqldump.cnf:
   [mysqldump]
   quick
   quote-names
   max_allowed_packet   = 16M
  MySQLConf.etc.mysql.my.cnf: Error: [Errno 40] Too many levels of symbolic 
links: '/etc/mysql/my.cnf'
  MySQLVarLibDirListing: ['ibdata1', 'ib_logfile0', '#innodb_temp', 
'debian-5.7.flag', '#ib_16384_0.dblwr', 'client-cert.pem', 'undo_001', 
'server-cert.pem', 'mysql.ibd', '#ib_16384_1.dblwr', 'client-key.pem', 
'ca-key.pem', 'sys', 'private_key.pem', 'mysql', 'undo_002', 'binlog.index', 
'performance_schema', 'ib_buffer_pool', 'auto.cnf', 'ib_logfile1', 
'public_key.pem', 'ca.pem', 'server-key.pem']
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic 
root=UUID=93666562-b5e4-4fb4-ba8c-7b42a3e6bf61 ro quiet splash 
mem_sleep_default=deep vt.handoff=7
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.6
  SourcePackage: mysql-8.0
  Title: package mysql-server-8.0 8.0.28-0ubuntu0.20.04.3 failed to 
install/upgrade: installed mysql-server-8.0 package post-installation script 
subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/zfs/+bug/1969247/+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 1969247] Re: fallocate with FALLOC_FL_ZERO_RANGE produces zero-size files on zfs in Jammy

[Marcos Alano]

@lvoytek

The fix was released 19th, April

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1969247

Title:
  fallocate with FALLOC_FL_ZERO_RANGE produces zero-size files on zfs in
  Jammy

Status in Native ZFS for Linux:
  Fix Released
Status in mysql-8.0 package in Ubuntu:
  Invalid
Status in zfs-linux package in Ubuntu:
  Fix Released
Status in zfs-linux source package in Jammy:
  Fix Committed

Bug description:
  [Summary]

  When running Jammy on zfs or LXD with a zfs pool on a Jammy host,
  fallocate creates a zero-sized file.

  The issue was originally found when installing mysql on LXD, where
  fallocate would create a zero-sized ib_logfile1 file. The original
  information in this bug is based on that.

  [Steps to Reproduce]

  touch foo.img
  fallocate -z -l 10M foo.img
  ls -la foo.img

  On a non-zfs Jammy system this will show something like:
  -rw-r--r-- 1 root root 10M ...

  while on zfs it will show:
  -rw-rw-r-- 1 root root 0 ...

  [Original Description]
  I came across this error when testing various mysql setups in an LXD 
container and managed to reproduce it consistently. I'm unable to reproduce on 
Ubuntu desktop or server though since the prerequisites are probably handled 
properly there.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: mysql-server-8.0 8.0.28-0ubuntu0.20.04.3
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.23
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Apr 15 21:31:09 2022
  Dmesg:

  ErrorMessage: installed mysql-server-8.0 package post-installation script 
subprocess returned error exit status 1
  KernLog:

  Logs.var.log.daemon.log:

  MySQLConf.etc.mysql.conf.d.mysql.cnf: [mysql]
  MySQLConf.etc.mysql.conf.d.mysqldump.cnf:
   [mysqldump]
   quick
   quote-names
   max_allowed_packet   = 16M
  MySQLConf.etc.mysql.my.cnf: Error: [Errno 40] Too many levels of symbolic 
links: '/etc/mysql/my.cnf'
  MySQLVarLibDirListing: ['ibdata1', 'ib_logfile0', '#innodb_temp', 
'debian-5.7.flag', '#ib_16384_0.dblwr', 'client-cert.pem', 'undo_001', 
'server-cert.pem', 'mysql.ibd', '#ib_16384_1.dblwr', 'client-key.pem', 
'ca-key.pem', 'sys', 'private_key.pem', 'mysql', 'undo_002', 'binlog.index', 
'performance_schema', 'ib_buffer_pool', 'auto.cnf', 'ib_logfile1', 
'public_key.pem', 'ca.pem', 'server-key.pem']
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic 
root=UUID=93666562-b5e4-4fb4-ba8c-7b42a3e6bf61 ro quiet splash 
mem_sleep_default=deep vt.handoff=7
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.6
  SourcePackage: mysql-8.0
  Title: package mysql-server-8.0 8.0.28-0ubuntu0.20.04.3 failed to 
install/upgrade: installed mysql-server-8.0 package post-installation script 
subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/zfs/+bug/1969247/+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 1969966] ProcEnviron.txt

[Marcos Alano]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1969966/+attachment/5584726/+files/ProcEnviron.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-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1969966

Title:
  No support for Intel Killer AX1675i

Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  New

Bug description:
  I just installed a Intel Killer AX1675i Wifi+Bluetooth card in my Dell G15 
5511 laptop but can't get WiFi or Bluetooth.
  About WiFi I get these logs:
  ➜ sudo dmesg|grep wifi -i
  [4.917786] Loading modules backported from iwlwifi
  [4.917787] iwlwifi-stack-public:master:9858:4c7cba27
  [4.984194] Intel(R) Wireless WiFi driver for Linux
  [4.985038] iwlwifi :00:14.3: enabling device ( -> 0002)
  [4.996087] iwlwifi: No config found for PCI dev 43f0/1672, rev=0x351, 
rfid=0x2010d000
  [4.996123] iwlwifi: probe of :00:14.3 failed with error -22
  About Bluetooth I get these logs:
  ➜ sudo dmesg|grep bluetooth -i
  [4.977780] Bluetooth: Core ver 2.22
  [4.977793] NET: Registered PF_BLUETOOTH protocol family
  [4.977794] Bluetooth: HCI device and connection manager initialized
  [4.977799] Bluetooth: HCI socket layer initialized
  [4.977800] Bluetooth: L2CAP socket layer initialized
  [4.977803] Bluetooth: SCO socket layer initialized
  [5.002780] Bluetooth: hci0: Bootloader revision 0.3 build 0 week 30 2018
  [5.003784] Bluetooth: hci0: Device revision is 0
  [5.003787] Bluetooth: hci0: Secure boot is enabled
  [5.003788] Bluetooth: hci0: OTP lock is enabled
  [5.003788] Bluetooth: hci0: API lock is enabled
  [5.003789] Bluetooth: hci0: Debug lock is disabled
  [5.003789] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
  [5.006774] Bluetooth: hci0: Failed to load Intel firmware file 
intel/ibt-19-0-3.sfi (-2)
  [5.007774] Bluetooth: hci0: MSFT supported features length mismatch
  [7.023197] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [7.023201] Bluetooth: BNEP filters: protocol multicast
  [7.023204] Bluetooth: BNEP socket layer initialized
  I'm in doubt about WiFi, since the message doesn't mention a missing 
firmware, but Bluetooth is very clear about it.

  
  I'm using Ubuntu 22.04 LTS with bleeding edge kernel 5.17.4. I also tried 
with 5.18rc1 but no change
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Dependencies: firmware-sof-signed 2.0-1ubuntu3
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2021-11-26 (152 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux-firmware 20220329.git681281e4-0ubuntu1
  PackageArchitecture: all
  RebootRequiredPkgs: Error: path contained symlinks.
  Tags:  jammy
  Uname: Linux 5.17.4-051704-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: Upgraded to jammy on 2022-02-03 (83 days ago)
  UserGroups: adm cdrom dip docker kvm libvirt lpadmin lxd plugdev sambashare 
sudo vboxusers
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1969966/+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 1969966] Re: No support for Intel Killer AX1675i

[Marcos Alano]

apport information

** Tags added: apport-collected jammy

** Description changed:

  I just installed a Intel Killer AX1675i Wifi+Bluetooth card in my Dell G15 
5511 laptop but can't get WiFi or Bluetooth.
  About WiFi I get these logs:
  ➜ sudo dmesg|grep wifi -i
  [4.917786] Loading modules backported from iwlwifi
  [4.917787] iwlwifi-stack-public:master:9858:4c7cba27
  [4.984194] Intel(R) Wireless WiFi driver for Linux
  [4.985038] iwlwifi :00:14.3: enabling device ( -> 0002)
  [4.996087] iwlwifi: No config found for PCI dev 43f0/1672, rev=0x351, 
rfid=0x2010d000
  [4.996123] iwlwifi: probe of :00:14.3 failed with error -22
  About Bluetooth I get these logs:
  ➜ sudo dmesg|grep bluetooth -i
  [4.977780] Bluetooth: Core ver 2.22
  [4.977793] NET: Registered PF_BLUETOOTH protocol family
  [4.977794] Bluetooth: HCI device and connection manager initialized
  [4.977799] Bluetooth: HCI socket layer initialized
  [4.977800] Bluetooth: L2CAP socket layer initialized
  [4.977803] Bluetooth: SCO socket layer initialized
  [5.002780] Bluetooth: hci0: Bootloader revision 0.3 build 0 week 30 2018
  [5.003784] Bluetooth: hci0: Device revision is 0
  [5.003787] Bluetooth: hci0: Secure boot is enabled
  [5.003788] Bluetooth: hci0: OTP lock is enabled
  [5.003788] Bluetooth: hci0: API lock is enabled
  [5.003789] Bluetooth: hci0: Debug lock is disabled
  [5.003789] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
  [5.006774] Bluetooth: hci0: Failed to load Intel firmware file 
intel/ibt-19-0-3.sfi (-2)
  [5.007774] Bluetooth: hci0: MSFT supported features length mismatch
  [7.023197] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [7.023201] Bluetooth: BNEP filters: protocol multicast
  [7.023204] Bluetooth: BNEP socket layer initialized
  I'm in doubt about WiFi, since the message doesn't mention a missing 
firmware, but Bluetooth is very clear about it.
  
  
  I'm using Ubuntu 22.04 LTS with bleeding edge kernel 5.17.4. I also tried 
with 5.18rc1 but no change
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu82
+ Architecture: amd64
+ CasperMD5CheckResult: pass
+ CurrentDesktop: ubuntu:GNOME
+ Dependencies: firmware-sof-signed 2.0-1ubuntu3
+ DistroRelease: Ubuntu 22.04
+ InstallationDate: Installed on 2021-11-26 (152 days ago)
+ InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
+ NonfreeKernelModules: nvidia_modeset nvidia
+ Package: linux-firmware 20220329.git681281e4-0ubuntu1
+ PackageArchitecture: all
+ RebootRequiredPkgs: Error: path contained symlinks.
+ Tags:  jammy
+ Uname: Linux 5.17.4-051704-generic x86_64
+ UnreportableReason: The running kernel is not an Ubuntu kernel
+ UpgradeStatus: Upgraded to jammy on 2022-02-03 (83 days ago)
+ UserGroups: adm cdrom dip docker kvm libvirt lpadmin lxd plugdev sambashare 
sudo vboxusers
+ _MarkForUpload: True

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1969966/+attachment/5584725/+files/ProcCpuinfoMinimal.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1969966

Title:
  No support for Intel Killer AX1675i

Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  New

Bug description:
  I just installed a Intel Killer AX1675i Wifi+Bluetooth card in my Dell G15 
5511 laptop but can't get WiFi or Bluetooth.
  About WiFi I get these logs:
  ➜ sudo dmesg|grep wifi -i
  [4.917786] Loading modules backported from iwlwifi
  [4.917787] iwlwifi-stack-public:master:9858:4c7cba27
  [4.984194] Intel(R) Wireless WiFi driver for Linux
  [4.985038] iwlwifi :00:14.3: enabling device ( -> 0002)
  [4.996087] iwlwifi: No config found for PCI dev 43f0/1672, rev=0x351, 
rfid=0x2010d000
  [4.996123] iwlwifi: probe of :00:14.3 failed with error -22
  About Bluetooth I get these logs:
  ➜ sudo dmesg|grep bluetooth -i
  [4.977780] Bluetooth: Core ver 2.22
  [4.977793] NET: Registered PF_BLUETOOTH protocol family
  [4.977794] Bluetooth: HCI device and connection manager initialized
  [4.977799] Bluetooth: HCI socket layer initialized
  [4.977800] Bluetooth: L2CAP socket layer initialized
  [4.977803] Bluetooth: SCO socket layer initialized
  [5.002780] Bluetooth: hci0: Bootloader revision 0.3 build 0 week 30 2018
  [5.003784] Bluetooth: hci0: Device revision is 0
  [5.003787] Bluetooth: hci0: Secure boot is enabled
  [5.003788] Bluetooth: hci0: OTP lock is enabled
  [5.003788] Bluetooth: hci0: API lock is enabled
  [5.003789] Bluetooth: hci0: Debug lock is disabled
  [5.003789] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
  [5.006774] Bluetooth: hci0: Failed to load Intel firmware file 
intel/ibt-19-0-3.sfi (-2)
  [5.007774] Bluetooth: hci0: MSFT suppor

[Kernel-packages] [Bug 1876632] Re: [nvidia] Corrupted/missing shell textures when switching users or resuming from suspend

[Marcos Alano]

I executed 'journalctl -b -f' to get the logs (they are in the file) and
executed systemctl suspend.

** Attachment added: "gistfile1.txt"
   
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1876632/+attachment/5583559/+files/gistfile1.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu.
https://bugs.launchpad.net/bugs/1876632

Title:
  [nvidia] Corrupted/missing shell textures when switching users or
  resuming from suspend

Status in GNOME Shell:
  Unknown
Status in Mutter:
  Unknown
Status in OEM Priority Project:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Triaged
Status in mutter package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-510 package in Ubuntu:
  Triaged

Bug description:
  [Impact]

  The Nvidia driver corrupts and/or forgets its textures when resuming
  from suspend, by design. Documented here:

  
https://www.khronos.org/registry/OpenGL/extensions/NV/NV_robustness_video_memory_purge.txt

  Although it's so awkward to implement everywhere that realistically
  compositors will never support it fully. Instead we're waiting for an
  Nvidia driver fix.

  *NOTE* that this is actually not a common problem because the system
  must be using Nvidia as the primary GPU to be affected. So generally
  only desktop users will encounter the bug, not laptops. And even then,
  only desktops that use suspend/resume and VT switching may trigger it,
  if ever. Even in development the bug cannot be reproduced reliably.

  [Workarounds]

  * Always log into a Xorg session and if corruption occurs then type:
  Alt+F2, R, Enter

  *
  
https://download.nvidia.com/XFree86/Linux-x86_64/510.54/README/powermanagement.html#PreserveAllVide719f0

  [Test Plan]

  [Where problems could occur]

  [Original Bug Report]

  I recently installed ubuntu 20.04 on my computer, and I am running
  into an issue when I do the following:

  * Login with a user on desktop
  * Select switch user, and login as second user
  * Switch user again, and return to original user

  At this point, text and icons in the menubar / sidebar are corrupted.
  Text and icons in normal windows appear correctly. I have attached a
  screenshot of what this looks like.

  Screenshots: https://imgur.com/a/3ZFDLMc

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
  Uname: Linux 5.4.0-28-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..09.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:09:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
   GCC version:
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May  3 18:12:45 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: ASUSTeK Computer Inc. GP104 [GeForce GTX 1070] [1043:85a0]
  InstallationDate: Installed on 2020-05-03 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Gigabyte Technology Co., Ltd. AX370-Gaming
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-28-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/19/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F3
  dmi.board.asset.tag: Default string
  dmi.board.name: AX370-Gaming-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: se1
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF3:bd06/19/2017:svnGigabyteTechnologyCo.,Ltd.:pnAX370-Gaming:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAX370-Gaming-CF:rvrse1:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: AX370-Gaming
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.s

[Kernel-packages] [Bug 1876632] Re: [nvidia] Corrupted/missing shell textures when switching users or resuming from suspend

[Marcos Alano]

@os369510,

Here is the content of the file as requested.

```
ResmanDebugLevel: 4294967295
RmLogonRC: 1
ModifyDeviceFiles: 1
DeviceFileUID: 0
DeviceFileGID: 0
DeviceFileMode: 438
InitializeSystemMemoryAllocations: 1
UsePageAttributeTable: 4294967295
EnableMSI: 1
RegisterForACPIEvents: 1
EnablePCIeGen3: 0
MemoryPoolSize: 0
KMallocHeapMaxSize: 0
VMallocHeapMaxSize: 0
IgnoreMMIOCheck: 0
TCEBypassMode: 0
EnableStreamMemOPs: 0
EnableUserNUMAManagement: 1
NvLinkDisable: 0
RmProfilingAdminOnly: 1
PreserveVideoMemoryAllocations: 1
EnableS0ixPowerManagement: 0
S0ixPowerManagementVideoMemoryThreshold: 256
DynamicPowerManagement: 3
DynamicPowerManagementVideoMemoryThreshold: 200
RegisterPCIDriver: 1
EnablePCIERelaxedOrderingMode: 0
EnableGpuFirmware: 18
EnableDbgBreakpoint: 0
RegistryDwords: ""
RegistryDwordsPerDevice: ""
RmMsg: ""
GpuBlacklist: ""
TemporaryFilePath: "/run"
ExcludedGpus: ""
```

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu.
https://bugs.launchpad.net/bugs/1876632

Title:
  [nvidia] Corrupted/missing shell textures when switching users or
  resuming from suspend

Status in GNOME Shell:
  Unknown
Status in Mutter:
  Unknown
Status in OEM Priority Project:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Triaged
Status in mutter package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-510 package in Ubuntu:
  Triaged

Bug description:
  [Impact]

  The Nvidia driver corrupts and/or forgets its textures when resuming
  from suspend, by design. Documented here:

  
https://www.khronos.org/registry/OpenGL/extensions/NV/NV_robustness_video_memory_purge.txt

  Although it's so awkward to implement everywhere that realistically
  compositors will never support it fully. Instead we're waiting for an
  Nvidia driver fix.

  *NOTE* that this is actually not a common problem because the system
  must be using Nvidia as the primary GPU to be affected. So generally
  only desktop users will encounter the bug, not laptops. And even then,
  only desktops that use suspend/resume and VT switching may trigger it,
  if ever. Even in development the bug cannot be reproduced reliably.

  [Workarounds]

  * Always log into a Xorg session and if corruption occurs then type:
  Alt+F2, R, Enter

  *
  
https://download.nvidia.com/XFree86/Linux-x86_64/510.54/README/powermanagement.html#PreserveAllVide719f0

  [Test Plan]

  [Where problems could occur]

  [Original Bug Report]

  I recently installed ubuntu 20.04 on my computer, and I am running
  into an issue when I do the following:

  * Login with a user on desktop
  * Select switch user, and login as second user
  * Switch user again, and return to original user

  At this point, text and icons in the menubar / sidebar are corrupted.
  Text and icons in normal windows appear correctly. I have attached a
  screenshot of what this looks like.

  Screenshots: https://imgur.com/a/3ZFDLMc

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
  Uname: Linux 5.4.0-28-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..09.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:09:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
   GCC version:
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May  3 18:12:45 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: ASUSTeK Computer Inc. GP104 [GeForce GTX 1070] [1043:85a0]
  InstallationDate: Installed on 2020-05-03 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Gigabyte Technology Co., Ltd. AX370-Gaming
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-28-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/19/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F3
  d

[Kernel-packages] [Bug 1876632] Re: [nvidia] Corrupted/missing shell textures when switching users or resuming from suspend

[Marcos Alano]

I tried to set both options mentioned on comment #11 and with X11 after resume 
I got corrupted lock screen and corrupted shell. I had to restart shell with 
alt+f2 and type r. Furthermore, I think this is the kind of problem the bug 
talks about.
I have a laptop with an option on BIOS to always use the NVIDIA card instead of 
hybrid approach, so in some cases laptops will be affected too because they act 
as desktops in this aspect.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu.
https://bugs.launchpad.net/bugs/1876632

Title:
  [nvidia] Corrupted/missing shell textures when switching users or
  resuming from suspend

Status in GNOME Shell:
  Unknown
Status in Mutter:
  Unknown
Status in OEM Priority Project:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Triaged
Status in mutter package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-460 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-510 package in Ubuntu:
  Triaged

Bug description:
  [Impact]

  The Nvidia driver corrupts and/or forgets its textures when resuming
  from suspend, by design. Documented here:

  
https://www.khronos.org/registry/OpenGL/extensions/NV/NV_robustness_video_memory_purge.txt

  Although it's so awkward to implement everywhere that realistically
  compositors will never support it fully. Instead we're waiting for an
  Nvidia driver fix.

  *NOTE* that this is actually not a common problem because the system
  must be using Nvidia as the primary GPU to be affected. So generally
  only desktop users will encounter the bug, not laptops. And even then,
  only desktops that use suspend/resume and VT switching may trigger it,
  if ever. Even in development the bug cannot be reproduced reliably.

  [Workarounds]

  * Always log into a Xorg session and if corruption occurs then type:
  Alt+F2, R, Enter

  *
  
https://download.nvidia.com/XFree86/Linux-x86_64/510.54/README/powermanagement.html#PreserveAllVide719f0

  [Test Plan]

  [Where problems could occur]

  [Original Bug Report]

  I recently installed ubuntu 20.04 on my computer, and I am running
  into an issue when I do the following:

  * Login with a user on desktop
  * Select switch user, and login as second user
  * Switch user again, and return to original user

  At this point, text and icons in the menubar / sidebar are corrupted.
  Text and icons in normal windows appear correctly. I have attached a
  screenshot of what this looks like.

  Screenshots: https://imgur.com/a/3ZFDLMc

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
  Uname: Linux 5.4.0-28-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..09.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:09:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
   GCC version:
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May  3 18:12:45 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: ASUSTeK Computer Inc. GP104 [GeForce GTX 1070] [1043:85a0]
  InstallationDate: Installed on 2020-05-03 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Gigabyte Technology Co., Ltd. AX370-Gaming
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-28-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/19/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F3
  dmi.board.asset.tag: Default string
  dmi.board.name: AX370-Gaming-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: se1
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF3:bd06/19/2017:svnGigabyteTechnologyCo.,Ltd.:pnAX370-Gaming:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAX370-Gaming-CF:rvr

[Kernel-packages] [Bug 1969966] Re: No support for Intel Killer AX1675i

[Marcos Alano]

** Description changed:

  I just installed a Intel Killer AX1675i Wifi+Bluetooth card in my Dell G15 
5511 laptop but can't get WiFi or Bluetooth.
  About WiFi I get these logs:
- ➜ sudo dmesg|grep wifi -i   
+ ➜ sudo dmesg|grep wifi -i
  [4.917786] Loading modules backported from iwlwifi
  [4.917787] iwlwifi-stack-public:master:9858:4c7cba27
  [4.984194] Intel(R) Wireless WiFi driver for Linux
  [4.985038] iwlwifi :00:14.3: enabling device ( -> 0002)
  [4.996087] iwlwifi: No config found for PCI dev 43f0/1672, rev=0x351, 
rfid=0x2010d000
  [4.996123] iwlwifi: probe of :00:14.3 failed with error -22
  About Bluetooth I get these logs:
  ➜ sudo dmesg|grep bluetooth -i
  [4.977780] Bluetooth: Core ver 2.22
  [4.977793] NET: Registered PF_BLUETOOTH protocol family
  [4.977794] Bluetooth: HCI device and connection manager initialized
  [4.977799] Bluetooth: HCI socket layer initialized
  [4.977800] Bluetooth: L2CAP socket layer initialized
  [4.977803] Bluetooth: SCO socket layer initialized
  [5.002780] Bluetooth: hci0: Bootloader revision 0.3 build 0 week 30 2018
  [5.003784] Bluetooth: hci0: Device revision is 0
  [5.003787] Bluetooth: hci0: Secure boot is enabled
  [5.003788] Bluetooth: hci0: OTP lock is enabled
  [5.003788] Bluetooth: hci0: API lock is enabled
  [5.003789] Bluetooth: hci0: Debug lock is disabled
  [5.003789] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
  [5.006774] Bluetooth: hci0: Failed to load Intel firmware file 
intel/ibt-19-0-3.sfi (-2)
  [5.007774] Bluetooth: hci0: MSFT supported features length mismatch
  [7.023197] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [7.023201] Bluetooth: BNEP filters: protocol multicast
  [7.023204] Bluetooth: BNEP socket layer initialized
  I'm in doubt about WiFi, since the message doesn't mention a missing 
firmware, but Bluetooth is very clear about it.
+ 
+ 
+ I'm using Ubuntu 22.04 LTS with bleeding edge kernel 5.17.4. I also tried 
with 5.18rc1 but no change

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1969966

Title:
  No support for Intel Killer AX1675i

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  I just installed a Intel Killer AX1675i Wifi+Bluetooth card in my Dell G15 
5511 laptop but can't get WiFi or Bluetooth.
  About WiFi I get these logs:
  ➜ sudo dmesg|grep wifi -i
  [4.917786] Loading modules backported from iwlwifi
  [4.917787] iwlwifi-stack-public:master:9858:4c7cba27
  [4.984194] Intel(R) Wireless WiFi driver for Linux
  [4.985038] iwlwifi :00:14.3: enabling device ( -> 0002)
  [4.996087] iwlwifi: No config found for PCI dev 43f0/1672, rev=0x351, 
rfid=0x2010d000
  [4.996123] iwlwifi: probe of :00:14.3 failed with error -22
  About Bluetooth I get these logs:
  ➜ sudo dmesg|grep bluetooth -i
  [4.977780] Bluetooth: Core ver 2.22
  [4.977793] NET: Registered PF_BLUETOOTH protocol family
  [4.977794] Bluetooth: HCI device and connection manager initialized
  [4.977799] Bluetooth: HCI socket layer initialized
  [4.977800] Bluetooth: L2CAP socket layer initialized
  [4.977803] Bluetooth: SCO socket layer initialized
  [5.002780] Bluetooth: hci0: Bootloader revision 0.3 build 0 week 30 2018
  [5.003784] Bluetooth: hci0: Device revision is 0
  [5.003787] Bluetooth: hci0: Secure boot is enabled
  [5.003788] Bluetooth: hci0: OTP lock is enabled
  [5.003788] Bluetooth: hci0: API lock is enabled
  [5.003789] Bluetooth: hci0: Debug lock is disabled
  [5.003789] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
  [5.006774] Bluetooth: hci0: Failed to load Intel firmware file 
intel/ibt-19-0-3.sfi (-2)
  [5.007774] Bluetooth: hci0: MSFT supported features length mismatch
  [7.023197] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [7.023201] Bluetooth: BNEP filters: protocol multicast
  [7.023204] Bluetooth: BNEP socket layer initialized
  I'm in doubt about WiFi, since the message doesn't mention a missing 
firmware, but Bluetooth is very clear about it.

  
  I'm using Ubuntu 22.04 LTS with bleeding edge kernel 5.17.4. I also tried 
with 5.18rc1 but no change

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1969966/+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 1969966] Re: No support for Intel Killer AX1675i

[Marcos Alano]

I loaded the iwlwifi module with debug=1 option to get more details. I hope it 
helps
➜ sudo dmesg|grep wifi -i  
[6.484062] Loading modules backported from iwlwifi
[6.484063] iwlwifi-stack-public:master:9858:4c7cba27
[6.576473] Intel(R) Wireless WiFi driver for Linux
[6.577121] iwlwifi :00:14.3: enabling device ( -> 0002)
[6.585684] iwlwifi: No config found for PCI dev 43f0/1672, rev=0x351, 
rfid=0x2010d000
[6.585742] iwlwifi: probe of :00:14.3 failed with error -22
[  177.897898] Intel(R) Wireless WiFi driver for Linux
[  177.898344] iwlwifi :00:14.3: iwl_trans_pcie_alloc HW REV: 0x351
[  177.898865] iwlwifi :00:14.3: iwl_pcie_set_interrupt_capa MSI-X enabled. 
16 interrupt vectors were allocated
[  177.898867] iwlwifi :00:14.3: iwl_pcie_set_interrupt_capa MSI-X enabled 
with rx queues 15, vec mask 0x0
[  177.899758] iwlwifi :00:14.3: iwl_pcie_prepare_card_hw 
iwl_trans_prepare_card_hw enter
[  177.899782] iwlwifi :00:14.3: iwl_pcie_set_hw_ready hardware ready
[  177.899797] iwlwifi: No config found for PCI dev 43f0/1672, rev=0x351, 
rfid=0x2010d000
[  177.899803] iwlwifi :00:14.3: iwl_pcie_rx_free Free NULL rx context
[  177.899814] iwlwifi: probe of :00:14.3 failed with error -22

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1969966

Title:
  No support for Intel Killer AX1675i

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  I just installed a Intel Killer AX1675i Wifi+Bluetooth card in my Dell G15 
5511 laptop but can't get WiFi or Bluetooth.
  About WiFi I get these logs:
  ➜ sudo dmesg|grep wifi -i   
  [4.917786] Loading modules backported from iwlwifi
  [4.917787] iwlwifi-stack-public:master:9858:4c7cba27
  [4.984194] Intel(R) Wireless WiFi driver for Linux
  [4.985038] iwlwifi :00:14.3: enabling device ( -> 0002)
  [4.996087] iwlwifi: No config found for PCI dev 43f0/1672, rev=0x351, 
rfid=0x2010d000
  [4.996123] iwlwifi: probe of :00:14.3 failed with error -22
  About Bluetooth I get these logs:
  ➜ sudo dmesg|grep bluetooth -i
  [4.977780] Bluetooth: Core ver 2.22
  [4.977793] NET: Registered PF_BLUETOOTH protocol family
  [4.977794] Bluetooth: HCI device and connection manager initialized
  [4.977799] Bluetooth: HCI socket layer initialized
  [4.977800] Bluetooth: L2CAP socket layer initialized
  [4.977803] Bluetooth: SCO socket layer initialized
  [5.002780] Bluetooth: hci0: Bootloader revision 0.3 build 0 week 30 2018
  [5.003784] Bluetooth: hci0: Device revision is 0
  [5.003787] Bluetooth: hci0: Secure boot is enabled
  [5.003788] Bluetooth: hci0: OTP lock is enabled
  [5.003788] Bluetooth: hci0: API lock is enabled
  [5.003789] Bluetooth: hci0: Debug lock is disabled
  [5.003789] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
  [5.006774] Bluetooth: hci0: Failed to load Intel firmware file 
intel/ibt-19-0-3.sfi (-2)
  [5.007774] Bluetooth: hci0: MSFT supported features length mismatch
  [7.023197] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [7.023201] Bluetooth: BNEP filters: protocol multicast
  [7.023204] Bluetooth: BNEP socket layer initialized
  I'm in doubt about WiFi, since the message doesn't mention a missing 
firmware, but Bluetooth is very clear about it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1969966/+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 1969966] [NEW] No support for Intel Killer AX1675i

[Marcos Alano]

Public bug reported:

I just installed a Intel Killer AX1675i Wifi+Bluetooth card in my Dell G15 5511 
laptop but can't get WiFi or Bluetooth.
About WiFi I get these logs:
➜ sudo dmesg|grep wifi -i   
[4.917786] Loading modules backported from iwlwifi
[4.917787] iwlwifi-stack-public:master:9858:4c7cba27
[4.984194] Intel(R) Wireless WiFi driver for Linux
[4.985038] iwlwifi :00:14.3: enabling device ( -> 0002)
[4.996087] iwlwifi: No config found for PCI dev 43f0/1672, rev=0x351, 
rfid=0x2010d000
[4.996123] iwlwifi: probe of :00:14.3 failed with error -22
About Bluetooth I get these logs:
➜ sudo dmesg|grep bluetooth -i
[4.977780] Bluetooth: Core ver 2.22
[4.977793] NET: Registered PF_BLUETOOTH protocol family
[4.977794] Bluetooth: HCI device and connection manager initialized
[4.977799] Bluetooth: HCI socket layer initialized
[4.977800] Bluetooth: L2CAP socket layer initialized
[4.977803] Bluetooth: SCO socket layer initialized
[5.002780] Bluetooth: hci0: Bootloader revision 0.3 build 0 week 30 2018
[5.003784] Bluetooth: hci0: Device revision is 0
[5.003787] Bluetooth: hci0: Secure boot is enabled
[5.003788] Bluetooth: hci0: OTP lock is enabled
[5.003788] Bluetooth: hci0: API lock is enabled
[5.003789] Bluetooth: hci0: Debug lock is disabled
[5.003789] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[5.006774] Bluetooth: hci0: Failed to load Intel firmware file 
intel/ibt-19-0-3.sfi (-2)
[5.007774] Bluetooth: hci0: MSFT supported features length mismatch
[7.023197] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[7.023201] Bluetooth: BNEP filters: protocol multicast
[7.023204] Bluetooth: BNEP socket layer initialized
I'm in doubt about WiFi, since the message doesn't mention a missing firmware, 
but Bluetooth is very clear about it.

** Affects: linux-firmware (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1969966

Title:
  No support for Intel Killer AX1675i

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  I just installed a Intel Killer AX1675i Wifi+Bluetooth card in my Dell G15 
5511 laptop but can't get WiFi or Bluetooth.
  About WiFi I get these logs:
  ➜ sudo dmesg|grep wifi -i   
  [4.917786] Loading modules backported from iwlwifi
  [4.917787] iwlwifi-stack-public:master:9858:4c7cba27
  [4.984194] Intel(R) Wireless WiFi driver for Linux
  [4.985038] iwlwifi :00:14.3: enabling device ( -> 0002)
  [4.996087] iwlwifi: No config found for PCI dev 43f0/1672, rev=0x351, 
rfid=0x2010d000
  [4.996123] iwlwifi: probe of :00:14.3 failed with error -22
  About Bluetooth I get these logs:
  ➜ sudo dmesg|grep bluetooth -i
  [4.977780] Bluetooth: Core ver 2.22
  [4.977793] NET: Registered PF_BLUETOOTH protocol family
  [4.977794] Bluetooth: HCI device and connection manager initialized
  [4.977799] Bluetooth: HCI socket layer initialized
  [4.977800] Bluetooth: L2CAP socket layer initialized
  [4.977803] Bluetooth: SCO socket layer initialized
  [5.002780] Bluetooth: hci0: Bootloader revision 0.3 build 0 week 30 2018
  [5.003784] Bluetooth: hci0: Device revision is 0
  [5.003787] Bluetooth: hci0: Secure boot is enabled
  [5.003788] Bluetooth: hci0: OTP lock is enabled
  [5.003788] Bluetooth: hci0: API lock is enabled
  [5.003789] Bluetooth: hci0: Debug lock is disabled
  [5.003789] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
  [5.006774] Bluetooth: hci0: Failed to load Intel firmware file 
intel/ibt-19-0-3.sfi (-2)
  [5.007774] Bluetooth: hci0: MSFT supported features length mismatch
  [7.023197] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [7.023201] Bluetooth: BNEP filters: protocol multicast
  [7.023204] Bluetooth: BNEP socket layer initialized
  I'm in doubt about WiFi, since the message doesn't mention a missing 
firmware, but Bluetooth is very clear about it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1969966/+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 1953328] ProcEnviron.txt

[Marcos Alano]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1953328/+attachment/5545711/+files/ProcEnviron.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/1953328

Title:
  Can't monitor fan speed with my Dell G15

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I own a Dell G15 5511. The G15 series is a budget-friendly version of 
Alienware series.
  My problem is I can't get the fan speed using either lm-sensors or GNOME 
applets (GNOME extensions Vitals or System Monitor).
  I think I find out why: the dell-smm-hwmon and i8k kernel modules don't 
support G15 series (or even Alienware). They support Latitude, XPS, Inspiron 
and other series, but not G15/Alienware (I think is the same wiring).
  The need is to open a kernel bug to add support for this product lines. I 
tried to open an issue in Kernel's Bugzilla, but it said to me to look up for 
distro's issue tracking. Since I use Ubuntu, here I am.
  I will be happy to provide any command exit and execute any debug procedure 
you may need.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-11-26 (9 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  RebootRequiredPkgs: Error: path contained symlinks.
  Tags:  impish
  Uname: Linux 5.15.5-051505-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo 
vboxusers
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953328/+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 1953328] Re: Can't monitor fan speed with my Dell G15

[Marcos Alano]

apport information

** Tags added: apport-collected impish

** Description changed:

  I own a Dell G15 5511. The G15 series is a budget-friendly version of 
Alienware series.
  My problem is I can't get the fan speed using either lm-sensors or GNOME 
applets (GNOME extensions Vitals or System Monitor).
  I think I find out why: the dell-smm-hwmon and i8k kernel modules don't 
support G15 series (or even Alienware). They support Latitude, XPS, Inspiron 
and other series, but not G15/Alienware (I think is the same wiring).
  The need is to open a kernel bug to add support for this product lines. I 
tried to open an issue in Kernel's Bugzilla, but it said to me to look up for 
distro's issue tracking. Since I use Ubuntu, here I am.
  I will be happy to provide any command exit and execute any debug procedure 
you may need.
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu71
+ Architecture: amd64
+ CasperMD5CheckResult: pass
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 21.10
+ InstallationDate: Installed on 2021-11-26 (9 days ago)
+ InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
+ NonfreeKernelModules: nvidia_modeset nvidia
+ Package: linux (not installed)
+ RebootRequiredPkgs: Error: path contained symlinks.
+ Tags:  impish
+ Uname: Linux 5.15.5-051505-generic x86_64
+ UnreportableReason: The running kernel is not an Ubuntu kernel
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo 
vboxusers
+ _MarkForUpload: True

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1953328/+attachment/5545710/+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/1953328

Title:
  Can't monitor fan speed with my Dell G15

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I own a Dell G15 5511. The G15 series is a budget-friendly version of 
Alienware series.
  My problem is I can't get the fan speed using either lm-sensors or GNOME 
applets (GNOME extensions Vitals or System Monitor).
  I think I find out why: the dell-smm-hwmon and i8k kernel modules don't 
support G15 series (or even Alienware). They support Latitude, XPS, Inspiron 
and other series, but not G15/Alienware (I think is the same wiring).
  The need is to open a kernel bug to add support for this product lines. I 
tried to open an issue in Kernel's Bugzilla, but it said to me to look up for 
distro's issue tracking. Since I use Ubuntu, here I am.
  I will be happy to provide any command exit and execute any debug procedure 
you may need.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-11-26 (9 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  RebootRequiredPkgs: Error: path contained symlinks.
  Tags:  impish
  Uname: Linux 5.15.5-051505-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo 
vboxusers
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953328/+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 1904638] Re: Xbox Series X|S controller doesn't work and Xbox icon still blinks after pairing

[Marcos Alano]

I'm using the 5.10-rc4 and the problem still occurs. Seems (but I'm
probably wrong) the controoler is using another MAC address.

** Attachment added: "dmesg.txt"
   
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1904638/+attachment/5435972/+files/dmesg.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1904638

Title:
  Xbox Series X|S controller doesn't work and Xbox icon still blinks
  after pairing

Status in bluez package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have Xbox Series X|S controller and the Xbox icon still blinks after
  the successful pairing.

  I'm using Ubuntu 20.10 updated with BlueZ latest release. I'm
  following this bug closely and I can provide any information you need
  and do any tests you want.

  
  mhalano@glados:~$ lsb_release -rd
  Description:  Ubuntu 20.10
  Release:  20.10

  mhalano@glados:~$ apt policy bluez
  bluez:
Installed: 5.55-0ubuntu1.1
Candidate: 5.55-0ubuntu1.1
Version table:
   *** 5.55-0ubuntu1.1 500
  500 http://br.archive.ubuntu.com/ubuntu groovy-proposed/main amd64 
Packages
  100 /var/lib/dpkg/status
   5.55-0ubuntu1 500
  500 http://br.archive.ubuntu.com/ubuntu groovy/main amd64 Packages
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2020-10-23 (25 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. Inspiron 5590
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-30-generic 
root=UUID=1e3484bb-be3c-4f5d-be22-044d9df06a4a ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-30.32-generic 5.8.17
  Tags:  groovy package-from-proposed
  Uname: Linux 5.8.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/13/2020
  dmi.bios.release: 1.11
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.11.0
  dmi.board.name: 0XRXN9
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A04
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.11.0:bd08/13/2020:br1.11:svnDellInc.:pnInspiron5590:pvr:rvnDellInc.:rn0XRXN9:rvrA04:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5590
  dmi.product.sku: 0957
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 14:F6:D8:6A:A3:F0  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN 
RX bytes:5307486 acl:57516 sco:0 events:78636 errors:0
TX bytes:18701 acl:357 sco:0 commands:841 errors:0
  mtime.conffile..etc.bluetooth.main.conf: 2020-11-04T10:53:00.842656

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1904638/+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 1904638] Re: Xbox Series X|S controller doesn't work and Xbox icon still blinks after pairing

[Marcos Alano]

I noticed a very strange behavior where the controller loops between
connected and disconnected. It was a known problem with Xbox One
controller and to fix that you needed to disable ERTM, but I already did
it (I also have a Xbox One Controller).

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1904638

Title:
  Xbox Series X|S controller doesn't work and Xbox icon still blinks
  after pairing

Status in bluez package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have Xbox Series X|S controller and the Xbox icon still blinks after
  the successful pairing.

  I'm using Ubuntu 20.10 updated with BlueZ latest release. I'm
  following this bug closely and I can provide any information you need
  and do any tests you want.

  
  mhalano@glados:~$ lsb_release -rd
  Description:  Ubuntu 20.10
  Release:  20.10

  mhalano@glados:~$ apt policy bluez
  bluez:
Installed: 5.55-0ubuntu1.1
Candidate: 5.55-0ubuntu1.1
Version table:
   *** 5.55-0ubuntu1.1 500
  500 http://br.archive.ubuntu.com/ubuntu groovy-proposed/main amd64 
Packages
  100 /var/lib/dpkg/status
   5.55-0ubuntu1 500
  500 http://br.archive.ubuntu.com/ubuntu groovy/main amd64 Packages
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2020-10-23 (25 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. Inspiron 5590
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-30-generic 
root=UUID=1e3484bb-be3c-4f5d-be22-044d9df06a4a ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-30.32-generic 5.8.17
  Tags:  groovy package-from-proposed
  Uname: Linux 5.8.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/13/2020
  dmi.bios.release: 1.11
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.11.0
  dmi.board.name: 0XRXN9
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A04
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.11.0:bd08/13/2020:br1.11:svnDellInc.:pnInspiron5590:pvr:rvnDellInc.:rn0XRXN9:rvrA04:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5590
  dmi.product.sku: 0957
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 14:F6:D8:6A:A3:F0  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN 
RX bytes:5307486 acl:57516 sco:0 events:78636 errors:0
TX bytes:18701 acl:357 sco:0 commands:841 errors:0
  mtime.conffile..etc.bluetooth.main.conf: 2020-11-04T10:53:00.842656

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1904638/+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 1904638] modified.conffile..etc.bluetooth.main.conf.txt

[Marcos Alano]

apport information

** Attachment added: "modified.conffile..etc.bluetooth.main.conf.txt"
   
https://bugs.launchpad.net/bugs/1904638/+attachment/5435618/+files/modified.conffile..etc.bluetooth.main.conf.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1904638

Title:
  Xbox Series X|S controller doesn't work and Xbox icon still blinks
  after pairing

Status in bluez package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have Xbox Series X|S controller and the Xbox icon still blinks after
  the successful pairing.

  I'm using Ubuntu 20.10 updated with BlueZ latest release. I'm
  following this bug closely and I can provide any information you need
  and do any tests you want.

  
  mhalano@glados:~$ lsb_release -rd
  Description:  Ubuntu 20.10
  Release:  20.10

  mhalano@glados:~$ apt policy bluez
  bluez:
Installed: 5.55-0ubuntu1.1
Candidate: 5.55-0ubuntu1.1
Version table:
   *** 5.55-0ubuntu1.1 500
  500 http://br.archive.ubuntu.com/ubuntu groovy-proposed/main amd64 
Packages
  100 /var/lib/dpkg/status
   5.55-0ubuntu1 500
  500 http://br.archive.ubuntu.com/ubuntu groovy/main amd64 Packages
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2020-10-23 (25 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. Inspiron 5590
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-30-generic 
root=UUID=1e3484bb-be3c-4f5d-be22-044d9df06a4a ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-30.32-generic 5.8.17
  Tags:  groovy package-from-proposed
  Uname: Linux 5.8.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/13/2020
  dmi.bios.release: 1.11
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.11.0
  dmi.board.name: 0XRXN9
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A04
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.11.0:bd08/13/2020:br1.11:svnDellInc.:pnInspiron5590:pvr:rvnDellInc.:rn0XRXN9:rvrA04:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5590
  dmi.product.sku: 0957
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 14:F6:D8:6A:A3:F0  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN 
RX bytes:5307486 acl:57516 sco:0 events:78636 errors:0
TX bytes:18701 acl:357 sco:0 commands:841 errors:0
  mtime.conffile..etc.bluetooth.main.conf: 2020-11-04T10:53:00.842656

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1904638/+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 1904638] syslog.txt

[Marcos Alano]

apport information

** Attachment added: "syslog.txt"
   https://bugs.launchpad.net/bugs/1904638/+attachment/5435620/+files/syslog.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1904638

Title:
  Xbox Series X|S controller doesn't work and Xbox icon still blinks
  after pairing

Status in bluez package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have Xbox Series X|S controller and the Xbox icon still blinks after
  the successful pairing.

  I'm using Ubuntu 20.10 updated with BlueZ latest release. I'm
  following this bug closely and I can provide any information you need
  and do any tests you want.

  
  mhalano@glados:~$ lsb_release -rd
  Description:  Ubuntu 20.10
  Release:  20.10

  mhalano@glados:~$ apt policy bluez
  bluez:
Installed: 5.55-0ubuntu1.1
Candidate: 5.55-0ubuntu1.1
Version table:
   *** 5.55-0ubuntu1.1 500
  500 http://br.archive.ubuntu.com/ubuntu groovy-proposed/main amd64 
Packages
  100 /var/lib/dpkg/status
   5.55-0ubuntu1 500
  500 http://br.archive.ubuntu.com/ubuntu groovy/main amd64 Packages
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2020-10-23 (25 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. Inspiron 5590
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-30-generic 
root=UUID=1e3484bb-be3c-4f5d-be22-044d9df06a4a ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-30.32-generic 5.8.17
  Tags:  groovy package-from-proposed
  Uname: Linux 5.8.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/13/2020
  dmi.bios.release: 1.11
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.11.0
  dmi.board.name: 0XRXN9
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A04
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.11.0:bd08/13/2020:br1.11:svnDellInc.:pnInspiron5590:pvr:rvnDellInc.:rn0XRXN9:rvrA04:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5590
  dmi.product.sku: 0957
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 14:F6:D8:6A:A3:F0  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN 
RX bytes:5307486 acl:57516 sco:0 events:78636 errors:0
TX bytes:18701 acl:357 sco:0 commands:841 errors:0
  mtime.conffile..etc.bluetooth.main.conf: 2020-11-04T10:53:00.842656

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1904638/+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 1904638] Re: Xbox Series X|S controller doesn't work and Xbox icon still blinks after pairing

[Marcos Alano]

** Attachment added: "lspci.txt"
   
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1904638/+attachment/5435621/+files/lspci.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1904638

Title:
  Xbox Series X|S controller doesn't work and Xbox icon still blinks
  after pairing

Status in bluez package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have Xbox Series X|S controller and the Xbox icon still blinks after
  the successful pairing.

  I'm using Ubuntu 20.10 updated with BlueZ latest release. I'm
  following this bug closely and I can provide any information you need
  and do any tests you want.

  
  mhalano@glados:~$ lsb_release -rd
  Description:  Ubuntu 20.10
  Release:  20.10

  mhalano@glados:~$ apt policy bluez
  bluez:
Installed: 5.55-0ubuntu1.1
Candidate: 5.55-0ubuntu1.1
Version table:
   *** 5.55-0ubuntu1.1 500
  500 http://br.archive.ubuntu.com/ubuntu groovy-proposed/main amd64 
Packages
  100 /var/lib/dpkg/status
   5.55-0ubuntu1 500
  500 http://br.archive.ubuntu.com/ubuntu groovy/main amd64 Packages
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2020-10-23 (25 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. Inspiron 5590
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-30-generic 
root=UUID=1e3484bb-be3c-4f5d-be22-044d9df06a4a ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-30.32-generic 5.8.17
  Tags:  groovy package-from-proposed
  Uname: Linux 5.8.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/13/2020
  dmi.bios.release: 1.11
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.11.0
  dmi.board.name: 0XRXN9
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A04
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.11.0:bd08/13/2020:br1.11:svnDellInc.:pnInspiron5590:pvr:rvnDellInc.:rn0XRXN9:rvrA04:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5590
  dmi.product.sku: 0957
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 14:F6:D8:6A:A3:F0  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN 
RX bytes:5307486 acl:57516 sco:0 events:78636 errors:0
TX bytes:18701 acl:357 sco:0 commands:841 errors:0
  mtime.conffile..etc.bluetooth.main.conf: 2020-11-04T10:53:00.842656

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1904638/+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 1904638] rfkill.txt

[Marcos Alano]

apport information

** Attachment added: "rfkill.txt"
   https://bugs.launchpad.net/bugs/1904638/+attachment/5435619/+files/rfkill.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1904638

Title:
  Xbox Series X|S controller doesn't work and Xbox icon still blinks
  after pairing

Status in bluez package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have Xbox Series X|S controller and the Xbox icon still blinks after
  the successful pairing.

  I'm using Ubuntu 20.10 updated with BlueZ latest release. I'm
  following this bug closely and I can provide any information you need
  and do any tests you want.

  
  mhalano@glados:~$ lsb_release -rd
  Description:  Ubuntu 20.10
  Release:  20.10

  mhalano@glados:~$ apt policy bluez
  bluez:
Installed: 5.55-0ubuntu1.1
Candidate: 5.55-0ubuntu1.1
Version table:
   *** 5.55-0ubuntu1.1 500
  500 http://br.archive.ubuntu.com/ubuntu groovy-proposed/main amd64 
Packages
  100 /var/lib/dpkg/status
   5.55-0ubuntu1 500
  500 http://br.archive.ubuntu.com/ubuntu groovy/main amd64 Packages
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2020-10-23 (25 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. Inspiron 5590
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-30-generic 
root=UUID=1e3484bb-be3c-4f5d-be22-044d9df06a4a ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-30.32-generic 5.8.17
  Tags:  groovy package-from-proposed
  Uname: Linux 5.8.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/13/2020
  dmi.bios.release: 1.11
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.11.0
  dmi.board.name: 0XRXN9
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A04
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.11.0:bd08/13/2020:br1.11:svnDellInc.:pnInspiron5590:pvr:rvnDellInc.:rn0XRXN9:rvrA04:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5590
  dmi.product.sku: 0957
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 14:F6:D8:6A:A3:F0  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN 
RX bytes:5307486 acl:57516 sco:0 events:78636 errors:0
TX bytes:18701 acl:357 sco:0 commands:841 errors:0
  mtime.conffile..etc.bluetooth.main.conf: 2020-11-04T10:53:00.842656

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1904638/+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 1904638] acpidump.txt

[Marcos Alano]

apport information

** Attachment added: "acpidump.txt"
   
https://bugs.launchpad.net/bugs/1904638/+attachment/5435616/+files/acpidump.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1904638

Title:
  Xbox Series X|S controller doesn't work and Xbox icon still blinks
  after pairing

Status in bluez package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have Xbox Series X|S controller and the Xbox icon still blinks after
  the successful pairing.

  I'm using Ubuntu 20.10 updated with BlueZ latest release. I'm
  following this bug closely and I can provide any information you need
  and do any tests you want.

  
  mhalano@glados:~$ lsb_release -rd
  Description:  Ubuntu 20.10
  Release:  20.10

  mhalano@glados:~$ apt policy bluez
  bluez:
Installed: 5.55-0ubuntu1.1
Candidate: 5.55-0ubuntu1.1
Version table:
   *** 5.55-0ubuntu1.1 500
  500 http://br.archive.ubuntu.com/ubuntu groovy-proposed/main amd64 
Packages
  100 /var/lib/dpkg/status
   5.55-0ubuntu1 500
  500 http://br.archive.ubuntu.com/ubuntu groovy/main amd64 Packages
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2020-10-23 (25 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. Inspiron 5590
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-30-generic 
root=UUID=1e3484bb-be3c-4f5d-be22-044d9df06a4a ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-30.32-generic 5.8.17
  Tags:  groovy package-from-proposed
  Uname: Linux 5.8.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/13/2020
  dmi.bios.release: 1.11
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.11.0
  dmi.board.name: 0XRXN9
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A04
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.11.0:bd08/13/2020:br1.11:svnDellInc.:pnInspiron5590:pvr:rvnDellInc.:rn0XRXN9:rvrA04:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5590
  dmi.product.sku: 0957
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 14:F6:D8:6A:A3:F0  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN 
RX bytes:5307486 acl:57516 sco:0 events:78636 errors:0
TX bytes:18701 acl:357 sco:0 commands:841 errors:0
  mtime.conffile..etc.bluetooth.main.conf: 2020-11-04T10:53:00.842656

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1904638/+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 1904638] getfacl.txt

[Marcos Alano]

apport information

** Attachment added: "getfacl.txt"
   
https://bugs.launchpad.net/bugs/1904638/+attachment/5435617/+files/getfacl.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1904638

Title:
  Xbox Series X|S controller doesn't work and Xbox icon still blinks
  after pairing

Status in bluez package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have Xbox Series X|S controller and the Xbox icon still blinks after
  the successful pairing.

  I'm using Ubuntu 20.10 updated with BlueZ latest release. I'm
  following this bug closely and I can provide any information you need
  and do any tests you want.

  
  mhalano@glados:~$ lsb_release -rd
  Description:  Ubuntu 20.10
  Release:  20.10

  mhalano@glados:~$ apt policy bluez
  bluez:
Installed: 5.55-0ubuntu1.1
Candidate: 5.55-0ubuntu1.1
Version table:
   *** 5.55-0ubuntu1.1 500
  500 http://br.archive.ubuntu.com/ubuntu groovy-proposed/main amd64 
Packages
  100 /var/lib/dpkg/status
   5.55-0ubuntu1 500
  500 http://br.archive.ubuntu.com/ubuntu groovy/main amd64 Packages
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2020-10-23 (25 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. Inspiron 5590
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-30-generic 
root=UUID=1e3484bb-be3c-4f5d-be22-044d9df06a4a ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-30.32-generic 5.8.17
  Tags:  groovy package-from-proposed
  Uname: Linux 5.8.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/13/2020
  dmi.bios.release: 1.11
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.11.0
  dmi.board.name: 0XRXN9
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A04
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.11.0:bd08/13/2020:br1.11:svnDellInc.:pnInspiron5590:pvr:rvnDellInc.:rn0XRXN9:rvrA04:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5590
  dmi.product.sku: 0957
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 14:F6:D8:6A:A3:F0  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN 
RX bytes:5307486 acl:57516 sco:0 events:78636 errors:0
TX bytes:18701 acl:357 sco:0 commands:841 errors:0
  mtime.conffile..etc.bluetooth.main.conf: 2020-11-04T10:53:00.842656

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1904638/+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 1904638] UdevDb.txt

[Marcos Alano]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1904638/+attachment/5435615/+files/UdevDb.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1904638

Title:
  Xbox Series X|S controller doesn't work and Xbox icon still blinks
  after pairing

Status in bluez package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have Xbox Series X|S controller and the Xbox icon still blinks after
  the successful pairing.

  I'm using Ubuntu 20.10 updated with BlueZ latest release. I'm
  following this bug closely and I can provide any information you need
  and do any tests you want.

  
  mhalano@glados:~$ lsb_release -rd
  Description:  Ubuntu 20.10
  Release:  20.10

  mhalano@glados:~$ apt policy bluez
  bluez:
Installed: 5.55-0ubuntu1.1
Candidate: 5.55-0ubuntu1.1
Version table:
   *** 5.55-0ubuntu1.1 500
  500 http://br.archive.ubuntu.com/ubuntu groovy-proposed/main amd64 
Packages
  100 /var/lib/dpkg/status
   5.55-0ubuntu1 500
  500 http://br.archive.ubuntu.com/ubuntu groovy/main amd64 Packages
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2020-10-23 (25 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. Inspiron 5590
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-30-generic 
root=UUID=1e3484bb-be3c-4f5d-be22-044d9df06a4a ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-30.32-generic 5.8.17
  Tags:  groovy package-from-proposed
  Uname: Linux 5.8.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/13/2020
  dmi.bios.release: 1.11
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.11.0
  dmi.board.name: 0XRXN9
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A04
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.11.0:bd08/13/2020:br1.11:svnDellInc.:pnInspiron5590:pvr:rvnDellInc.:rn0XRXN9:rvrA04:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5590
  dmi.product.sku: 0957
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 14:F6:D8:6A:A3:F0  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN 
RX bytes:5307486 acl:57516 sco:0 events:78636 errors:0
TX bytes:18701 acl:357 sco:0 commands:841 errors:0
  mtime.conffile..etc.bluetooth.main.conf: 2020-11-04T10:53:00.842656

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1904638/+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 1904638] ProcModules.txt

[Marcos Alano]

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1904638/+attachment/5435614/+files/ProcModules.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1904638

Title:
  Xbox Series X|S controller doesn't work and Xbox icon still blinks
  after pairing

Status in bluez package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have Xbox Series X|S controller and the Xbox icon still blinks after
  the successful pairing.

  I'm using Ubuntu 20.10 updated with BlueZ latest release. I'm
  following this bug closely and I can provide any information you need
  and do any tests you want.

  
  mhalano@glados:~$ lsb_release -rd
  Description:  Ubuntu 20.10
  Release:  20.10

  mhalano@glados:~$ apt policy bluez
  bluez:
Installed: 5.55-0ubuntu1.1
Candidate: 5.55-0ubuntu1.1
Version table:
   *** 5.55-0ubuntu1.1 500
  500 http://br.archive.ubuntu.com/ubuntu groovy-proposed/main amd64 
Packages
  100 /var/lib/dpkg/status
   5.55-0ubuntu1 500
  500 http://br.archive.ubuntu.com/ubuntu groovy/main amd64 Packages
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2020-10-23 (25 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. Inspiron 5590
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-30-generic 
root=UUID=1e3484bb-be3c-4f5d-be22-044d9df06a4a ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-30.32-generic 5.8.17
  Tags:  groovy package-from-proposed
  Uname: Linux 5.8.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/13/2020
  dmi.bios.release: 1.11
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.11.0
  dmi.board.name: 0XRXN9
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A04
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.11.0:bd08/13/2020:br1.11:svnDellInc.:pnInspiron5590:pvr:rvnDellInc.:rn0XRXN9:rvrA04:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5590
  dmi.product.sku: 0957
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 14:F6:D8:6A:A3:F0  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN 
RX bytes:5307486 acl:57516 sco:0 events:78636 errors:0
TX bytes:18701 acl:357 sco:0 commands:841 errors:0
  mtime.conffile..etc.bluetooth.main.conf: 2020-11-04T10:53:00.842656

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1904638/+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 1904638] Lsusb-v.txt

[Marcos Alano]

apport information

** Attachment added: "Lsusb-v.txt"
   
https://bugs.launchpad.net/bugs/1904638/+attachment/5435609/+files/Lsusb-v.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1904638

Title:
  Xbox Series X|S controller doesn't work and Xbox icon still blinks
  after pairing

Status in bluez package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have Xbox Series X|S controller and the Xbox icon still blinks after
  the successful pairing.

  I'm using Ubuntu 20.10 updated with BlueZ latest release. I'm
  following this bug closely and I can provide any information you need
  and do any tests you want.

  
  mhalano@glados:~$ lsb_release -rd
  Description:  Ubuntu 20.10
  Release:  20.10

  mhalano@glados:~$ apt policy bluez
  bluez:
Installed: 5.55-0ubuntu1.1
Candidate: 5.55-0ubuntu1.1
Version table:
   *** 5.55-0ubuntu1.1 500
  500 http://br.archive.ubuntu.com/ubuntu groovy-proposed/main amd64 
Packages
  100 /var/lib/dpkg/status
   5.55-0ubuntu1 500
  500 http://br.archive.ubuntu.com/ubuntu groovy/main amd64 Packages
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2020-10-23 (25 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. Inspiron 5590
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-30-generic 
root=UUID=1e3484bb-be3c-4f5d-be22-044d9df06a4a ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-30.32-generic 5.8.17
  Tags:  groovy package-from-proposed
  Uname: Linux 5.8.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/13/2020
  dmi.bios.release: 1.11
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.11.0
  dmi.board.name: 0XRXN9
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A04
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.11.0:bd08/13/2020:br1.11:svnDellInc.:pnInspiron5590:pvr:rvnDellInc.:rn0XRXN9:rvrA04:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5590
  dmi.product.sku: 0957
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 14:F6:D8:6A:A3:F0  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN 
RX bytes:5307486 acl:57516 sco:0 events:78636 errors:0
TX bytes:18701 acl:357 sco:0 commands:841 errors:0
  mtime.conffile..etc.bluetooth.main.conf: 2020-11-04T10:53:00.842656

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1904638/+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 1904638] ProcEnviron.txt

[Marcos Alano]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1904638/+attachment/5435612/+files/ProcEnviron.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1904638

Title:
  Xbox Series X|S controller doesn't work and Xbox icon still blinks
  after pairing

Status in bluez package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have Xbox Series X|S controller and the Xbox icon still blinks after
  the successful pairing.

  I'm using Ubuntu 20.10 updated with BlueZ latest release. I'm
  following this bug closely and I can provide any information you need
  and do any tests you want.

  
  mhalano@glados:~$ lsb_release -rd
  Description:  Ubuntu 20.10
  Release:  20.10

  mhalano@glados:~$ apt policy bluez
  bluez:
Installed: 5.55-0ubuntu1.1
Candidate: 5.55-0ubuntu1.1
Version table:
   *** 5.55-0ubuntu1.1 500
  500 http://br.archive.ubuntu.com/ubuntu groovy-proposed/main amd64 
Packages
  100 /var/lib/dpkg/status
   5.55-0ubuntu1 500
  500 http://br.archive.ubuntu.com/ubuntu groovy/main amd64 Packages
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2020-10-23 (25 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. Inspiron 5590
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-30-generic 
root=UUID=1e3484bb-be3c-4f5d-be22-044d9df06a4a ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-30.32-generic 5.8.17
  Tags:  groovy package-from-proposed
  Uname: Linux 5.8.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/13/2020
  dmi.bios.release: 1.11
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.11.0
  dmi.board.name: 0XRXN9
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A04
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.11.0:bd08/13/2020:br1.11:svnDellInc.:pnInspiron5590:pvr:rvnDellInc.:rn0XRXN9:rvrA04:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5590
  dmi.product.sku: 0957
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 14:F6:D8:6A:A3:F0  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN 
RX bytes:5307486 acl:57516 sco:0 events:78636 errors:0
TX bytes:18701 acl:357 sco:0 commands:841 errors:0
  mtime.conffile..etc.bluetooth.main.conf: 2020-11-04T10:53:00.842656

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1904638/+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 1904638] ProcCpuinfo.txt

[Marcos Alano]

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1904638/+attachment/5435610/+files/ProcCpuinfo.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1904638

Title:
  Xbox Series X|S controller doesn't work and Xbox icon still blinks
  after pairing

Status in bluez package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have Xbox Series X|S controller and the Xbox icon still blinks after
  the successful pairing.

  I'm using Ubuntu 20.10 updated with BlueZ latest release. I'm
  following this bug closely and I can provide any information you need
  and do any tests you want.

  
  mhalano@glados:~$ lsb_release -rd
  Description:  Ubuntu 20.10
  Release:  20.10

  mhalano@glados:~$ apt policy bluez
  bluez:
Installed: 5.55-0ubuntu1.1
Candidate: 5.55-0ubuntu1.1
Version table:
   *** 5.55-0ubuntu1.1 500
  500 http://br.archive.ubuntu.com/ubuntu groovy-proposed/main amd64 
Packages
  100 /var/lib/dpkg/status
   5.55-0ubuntu1 500
  500 http://br.archive.ubuntu.com/ubuntu groovy/main amd64 Packages
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2020-10-23 (25 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. Inspiron 5590
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-30-generic 
root=UUID=1e3484bb-be3c-4f5d-be22-044d9df06a4a ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-30.32-generic 5.8.17
  Tags:  groovy package-from-proposed
  Uname: Linux 5.8.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/13/2020
  dmi.bios.release: 1.11
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.11.0
  dmi.board.name: 0XRXN9
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A04
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.11.0:bd08/13/2020:br1.11:svnDellInc.:pnInspiron5590:pvr:rvnDellInc.:rn0XRXN9:rvrA04:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5590
  dmi.product.sku: 0957
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 14:F6:D8:6A:A3:F0  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN 
RX bytes:5307486 acl:57516 sco:0 events:78636 errors:0
TX bytes:18701 acl:357 sco:0 commands:841 errors:0
  mtime.conffile..etc.bluetooth.main.conf: 2020-11-04T10:53:00.842656

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1904638/+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 1904638] ProcCpuinfoMinimal.txt

[Marcos Alano]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1904638/+attachment/5435611/+files/ProcCpuinfoMinimal.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1904638

Title:
  Xbox Series X|S controller doesn't work and Xbox icon still blinks
  after pairing

Status in bluez package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have Xbox Series X|S controller and the Xbox icon still blinks after
  the successful pairing.

  I'm using Ubuntu 20.10 updated with BlueZ latest release. I'm
  following this bug closely and I can provide any information you need
  and do any tests you want.

  
  mhalano@glados:~$ lsb_release -rd
  Description:  Ubuntu 20.10
  Release:  20.10

  mhalano@glados:~$ apt policy bluez
  bluez:
Installed: 5.55-0ubuntu1.1
Candidate: 5.55-0ubuntu1.1
Version table:
   *** 5.55-0ubuntu1.1 500
  500 http://br.archive.ubuntu.com/ubuntu groovy-proposed/main amd64 
Packages
  100 /var/lib/dpkg/status
   5.55-0ubuntu1 500
  500 http://br.archive.ubuntu.com/ubuntu groovy/main amd64 Packages
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2020-10-23 (25 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. Inspiron 5590
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-30-generic 
root=UUID=1e3484bb-be3c-4f5d-be22-044d9df06a4a ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-30.32-generic 5.8.17
  Tags:  groovy package-from-proposed
  Uname: Linux 5.8.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/13/2020
  dmi.bios.release: 1.11
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.11.0
  dmi.board.name: 0XRXN9
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A04
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.11.0:bd08/13/2020:br1.11:svnDellInc.:pnInspiron5590:pvr:rvnDellInc.:rn0XRXN9:rvrA04:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5590
  dmi.product.sku: 0957
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 14:F6:D8:6A:A3:F0  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN 
RX bytes:5307486 acl:57516 sco:0 events:78636 errors:0
TX bytes:18701 acl:357 sco:0 commands:841 errors:0
  mtime.conffile..etc.bluetooth.main.conf: 2020-11-04T10:53:00.842656

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1904638/+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 1904638] ProcInterrupts.txt

[Marcos Alano]

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1904638/+attachment/5435613/+files/ProcInterrupts.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1904638

Title:
  Xbox Series X|S controller doesn't work and Xbox icon still blinks
  after pairing

Status in bluez package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have Xbox Series X|S controller and the Xbox icon still blinks after
  the successful pairing.

  I'm using Ubuntu 20.10 updated with BlueZ latest release. I'm
  following this bug closely and I can provide any information you need
  and do any tests you want.

  
  mhalano@glados:~$ lsb_release -rd
  Description:  Ubuntu 20.10
  Release:  20.10

  mhalano@glados:~$ apt policy bluez
  bluez:
Installed: 5.55-0ubuntu1.1
Candidate: 5.55-0ubuntu1.1
Version table:
   *** 5.55-0ubuntu1.1 500
  500 http://br.archive.ubuntu.com/ubuntu groovy-proposed/main amd64 
Packages
  100 /var/lib/dpkg/status
   5.55-0ubuntu1 500
  500 http://br.archive.ubuntu.com/ubuntu groovy/main amd64 Packages
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2020-10-23 (25 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. Inspiron 5590
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-30-generic 
root=UUID=1e3484bb-be3c-4f5d-be22-044d9df06a4a ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-30.32-generic 5.8.17
  Tags:  groovy package-from-proposed
  Uname: Linux 5.8.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/13/2020
  dmi.bios.release: 1.11
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.11.0
  dmi.board.name: 0XRXN9
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A04
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.11.0:bd08/13/2020:br1.11:svnDellInc.:pnInspiron5590:pvr:rvnDellInc.:rn0XRXN9:rvrA04:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5590
  dmi.product.sku: 0957
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 14:F6:D8:6A:A3:F0  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN 
RX bytes:5307486 acl:57516 sco:0 events:78636 errors:0
TX bytes:18701 acl:357 sco:0 commands:841 errors:0
  mtime.conffile..etc.bluetooth.main.conf: 2020-11-04T10:53:00.842656

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1904638/+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 1904638] Re: Xbox Series X|S controller doesn't work and Xbox icon still blinks after pairing

[Marcos Alano]

** Attachment added: "journal.txt"
   
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1904638/+attachment/5435623/+files/journal.txt

** Changed in: bluez (Ubuntu)
   Status: Incomplete => Confirmed

** Changed in: linux (Ubuntu)
   Status: Incomplete => Confirmed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1904638

Title:
  Xbox Series X|S controller doesn't work and Xbox icon still blinks
  after pairing

Status in bluez package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have Xbox Series X|S controller and the Xbox icon still blinks after
  the successful pairing.

  I'm using Ubuntu 20.10 updated with BlueZ latest release. I'm
  following this bug closely and I can provide any information you need
  and do any tests you want.

  
  mhalano@glados:~$ lsb_release -rd
  Description:  Ubuntu 20.10
  Release:  20.10

  mhalano@glados:~$ apt policy bluez
  bluez:
Installed: 5.55-0ubuntu1.1
Candidate: 5.55-0ubuntu1.1
Version table:
   *** 5.55-0ubuntu1.1 500
  500 http://br.archive.ubuntu.com/ubuntu groovy-proposed/main amd64 
Packages
  100 /var/lib/dpkg/status
   5.55-0ubuntu1 500
  500 http://br.archive.ubuntu.com/ubuntu groovy/main amd64 Packages
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2020-10-23 (25 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. Inspiron 5590
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-30-generic 
root=UUID=1e3484bb-be3c-4f5d-be22-044d9df06a4a ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-30.32-generic 5.8.17
  Tags:  groovy package-from-proposed
  Uname: Linux 5.8.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/13/2020
  dmi.bios.release: 1.11
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.11.0
  dmi.board.name: 0XRXN9
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A04
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.11.0:bd08/13/2020:br1.11:svnDellInc.:pnInspiron5590:pvr:rvnDellInc.:rn0XRXN9:rvrA04:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5590
  dmi.product.sku: 0957
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 14:F6:D8:6A:A3:F0  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN 
RX bytes:5307486 acl:57516 sco:0 events:78636 errors:0
TX bytes:18701 acl:357 sco:0 commands:841 errors:0
  mtime.conffile..etc.bluetooth.main.conf: 2020-11-04T10:53:00.842656

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1904638/+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 1904638] Re: Xbox Series X|S controller doesn't work and Xbox icon still blinks after pairing

[Marcos Alano]

** Attachment added: "lsusb.txt"
   
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1904638/+attachment/5435622/+files/lsusb.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1904638

Title:
  Xbox Series X|S controller doesn't work and Xbox icon still blinks
  after pairing

Status in bluez package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have Xbox Series X|S controller and the Xbox icon still blinks after
  the successful pairing.

  I'm using Ubuntu 20.10 updated with BlueZ latest release. I'm
  following this bug closely and I can provide any information you need
  and do any tests you want.

  
  mhalano@glados:~$ lsb_release -rd
  Description:  Ubuntu 20.10
  Release:  20.10

  mhalano@glados:~$ apt policy bluez
  bluez:
Installed: 5.55-0ubuntu1.1
Candidate: 5.55-0ubuntu1.1
Version table:
   *** 5.55-0ubuntu1.1 500
  500 http://br.archive.ubuntu.com/ubuntu groovy-proposed/main amd64 
Packages
  100 /var/lib/dpkg/status
   5.55-0ubuntu1 500
  500 http://br.archive.ubuntu.com/ubuntu groovy/main amd64 Packages
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2020-10-23 (25 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. Inspiron 5590
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-30-generic 
root=UUID=1e3484bb-be3c-4f5d-be22-044d9df06a4a ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-30.32-generic 5.8.17
  Tags:  groovy package-from-proposed
  Uname: Linux 5.8.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/13/2020
  dmi.bios.release: 1.11
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.11.0
  dmi.board.name: 0XRXN9
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A04
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.11.0:bd08/13/2020:br1.11:svnDellInc.:pnInspiron5590:pvr:rvnDellInc.:rn0XRXN9:rvrA04:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5590
  dmi.product.sku: 0957
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 14:F6:D8:6A:A3:F0  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN 
RX bytes:5307486 acl:57516 sco:0 events:78636 errors:0
TX bytes:18701 acl:357 sco:0 commands:841 errors:0
  mtime.conffile..etc.bluetooth.main.conf: 2020-11-04T10:53:00.842656

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1904638/+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 1904638] Dependencies.txt

[Marcos Alano]

apport information

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1904638/+attachment/5435604/+files/Dependencies.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1904638

Title:
  Xbox Series X|S controller doesn't work and Xbox icon still blinks
  after pairing

Status in bluez package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have Xbox Series X|S controller and the Xbox icon still blinks after
  the successful pairing.

  I'm using Ubuntu 20.10 updated with BlueZ latest release. I'm
  following this bug closely and I can provide any information you need
  and do any tests you want.

  
  mhalano@glados:~$ lsb_release -rd
  Description:  Ubuntu 20.10
  Release:  20.10

  mhalano@glados:~$ apt policy bluez
  bluez:
Installed: 5.55-0ubuntu1.1
Candidate: 5.55-0ubuntu1.1
Version table:
   *** 5.55-0ubuntu1.1 500
  500 http://br.archive.ubuntu.com/ubuntu groovy-proposed/main amd64 
Packages
  100 /var/lib/dpkg/status
   5.55-0ubuntu1 500
  500 http://br.archive.ubuntu.com/ubuntu groovy/main amd64 Packages
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2020-10-23 (25 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. Inspiron 5590
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-30-generic 
root=UUID=1e3484bb-be3c-4f5d-be22-044d9df06a4a ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-30.32-generic 5.8.17
  Tags:  groovy package-from-proposed
  Uname: Linux 5.8.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/13/2020
  dmi.bios.release: 1.11
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.11.0
  dmi.board.name: 0XRXN9
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A04
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.11.0:bd08/13/2020:br1.11:svnDellInc.:pnInspiron5590:pvr:rvnDellInc.:rn0XRXN9:rvrA04:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5590
  dmi.product.sku: 0957
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 14:F6:D8:6A:A3:F0  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN 
RX bytes:5307486 acl:57516 sco:0 events:78636 errors:0
TX bytes:18701 acl:357 sco:0 commands:841 errors:0
  mtime.conffile..etc.bluetooth.main.conf: 2020-11-04T10:53:00.842656

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1904638/+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 1904638] Lsusb-t.txt

[Marcos Alano]

apport information

** Attachment added: "Lsusb-t.txt"
   
https://bugs.launchpad.net/bugs/1904638/+attachment/5435608/+files/Lsusb-t.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1904638

Title:
  Xbox Series X|S controller doesn't work and Xbox icon still blinks
  after pairing

Status in bluez package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have Xbox Series X|S controller and the Xbox icon still blinks after
  the successful pairing.

  I'm using Ubuntu 20.10 updated with BlueZ latest release. I'm
  following this bug closely and I can provide any information you need
  and do any tests you want.

  
  mhalano@glados:~$ lsb_release -rd
  Description:  Ubuntu 20.10
  Release:  20.10

  mhalano@glados:~$ apt policy bluez
  bluez:
Installed: 5.55-0ubuntu1.1
Candidate: 5.55-0ubuntu1.1
Version table:
   *** 5.55-0ubuntu1.1 500
  500 http://br.archive.ubuntu.com/ubuntu groovy-proposed/main amd64 
Packages
  100 /var/lib/dpkg/status
   5.55-0ubuntu1 500
  500 http://br.archive.ubuntu.com/ubuntu groovy/main amd64 Packages
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2020-10-23 (25 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. Inspiron 5590
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-30-generic 
root=UUID=1e3484bb-be3c-4f5d-be22-044d9df06a4a ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-30.32-generic 5.8.17
  Tags:  groovy package-from-proposed
  Uname: Linux 5.8.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/13/2020
  dmi.bios.release: 1.11
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.11.0
  dmi.board.name: 0XRXN9
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A04
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.11.0:bd08/13/2020:br1.11:svnDellInc.:pnInspiron5590:pvr:rvnDellInc.:rn0XRXN9:rvrA04:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5590
  dmi.product.sku: 0957
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 14:F6:D8:6A:A3:F0  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN 
RX bytes:5307486 acl:57516 sco:0 events:78636 errors:0
TX bytes:18701 acl:357 sco:0 commands:841 errors:0
  mtime.conffile..etc.bluetooth.main.conf: 2020-11-04T10:53:00.842656

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1904638/+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 1904638] Lsusb.txt

[Marcos Alano]

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1904638/+attachment/5435607/+files/Lsusb.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1904638

Title:
  Xbox Series X|S controller doesn't work and Xbox icon still blinks
  after pairing

Status in bluez package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have Xbox Series X|S controller and the Xbox icon still blinks after
  the successful pairing.

  I'm using Ubuntu 20.10 updated with BlueZ latest release. I'm
  following this bug closely and I can provide any information you need
  and do any tests you want.

  
  mhalano@glados:~$ lsb_release -rd
  Description:  Ubuntu 20.10
  Release:  20.10

  mhalano@glados:~$ apt policy bluez
  bluez:
Installed: 5.55-0ubuntu1.1
Candidate: 5.55-0ubuntu1.1
Version table:
   *** 5.55-0ubuntu1.1 500
  500 http://br.archive.ubuntu.com/ubuntu groovy-proposed/main amd64 
Packages
  100 /var/lib/dpkg/status
   5.55-0ubuntu1 500
  500 http://br.archive.ubuntu.com/ubuntu groovy/main amd64 Packages
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2020-10-23 (25 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. Inspiron 5590
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-30-generic 
root=UUID=1e3484bb-be3c-4f5d-be22-044d9df06a4a ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-30.32-generic 5.8.17
  Tags:  groovy package-from-proposed
  Uname: Linux 5.8.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/13/2020
  dmi.bios.release: 1.11
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.11.0
  dmi.board.name: 0XRXN9
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A04
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.11.0:bd08/13/2020:br1.11:svnDellInc.:pnInspiron5590:pvr:rvnDellInc.:rn0XRXN9:rvrA04:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5590
  dmi.product.sku: 0957
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 14:F6:D8:6A:A3:F0  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN 
RX bytes:5307486 acl:57516 sco:0 events:78636 errors:0
TX bytes:18701 acl:357 sco:0 commands:841 errors:0
  mtime.conffile..etc.bluetooth.main.conf: 2020-11-04T10:53:00.842656

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1904638/+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 1904638] Lspci-vt.txt

[Marcos Alano]

apport information

** Attachment added: "Lspci-vt.txt"
   
https://bugs.launchpad.net/bugs/1904638/+attachment/5435606/+files/Lspci-vt.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1904638

Title:
  Xbox Series X|S controller doesn't work and Xbox icon still blinks
  after pairing

Status in bluez package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have Xbox Series X|S controller and the Xbox icon still blinks after
  the successful pairing.

  I'm using Ubuntu 20.10 updated with BlueZ latest release. I'm
  following this bug closely and I can provide any information you need
  and do any tests you want.

  
  mhalano@glados:~$ lsb_release -rd
  Description:  Ubuntu 20.10
  Release:  20.10

  mhalano@glados:~$ apt policy bluez
  bluez:
Installed: 5.55-0ubuntu1.1
Candidate: 5.55-0ubuntu1.1
Version table:
   *** 5.55-0ubuntu1.1 500
  500 http://br.archive.ubuntu.com/ubuntu groovy-proposed/main amd64 
Packages
  100 /var/lib/dpkg/status
   5.55-0ubuntu1 500
  500 http://br.archive.ubuntu.com/ubuntu groovy/main amd64 Packages
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2020-10-23 (25 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. Inspiron 5590
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-30-generic 
root=UUID=1e3484bb-be3c-4f5d-be22-044d9df06a4a ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-30.32-generic 5.8.17
  Tags:  groovy package-from-proposed
  Uname: Linux 5.8.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/13/2020
  dmi.bios.release: 1.11
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.11.0
  dmi.board.name: 0XRXN9
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A04
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.11.0:bd08/13/2020:br1.11:svnDellInc.:pnInspiron5590:pvr:rvnDellInc.:rn0XRXN9:rvrA04:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5590
  dmi.product.sku: 0957
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 14:F6:D8:6A:A3:F0  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN 
RX bytes:5307486 acl:57516 sco:0 events:78636 errors:0
TX bytes:18701 acl:357 sco:0 commands:841 errors:0
  mtime.conffile..etc.bluetooth.main.conf: 2020-11-04T10:53:00.842656

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1904638/+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 1904638] Lspci.txt

[Marcos Alano]

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1904638/+attachment/5435605/+files/Lspci.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1904638

Title:
  Xbox Series X|S controller doesn't work and Xbox icon still blinks
  after pairing

Status in bluez package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have Xbox Series X|S controller and the Xbox icon still blinks after
  the successful pairing.

  I'm using Ubuntu 20.10 updated with BlueZ latest release. I'm
  following this bug closely and I can provide any information you need
  and do any tests you want.

  
  mhalano@glados:~$ lsb_release -rd
  Description:  Ubuntu 20.10
  Release:  20.10

  mhalano@glados:~$ apt policy bluez
  bluez:
Installed: 5.55-0ubuntu1.1
Candidate: 5.55-0ubuntu1.1
Version table:
   *** 5.55-0ubuntu1.1 500
  500 http://br.archive.ubuntu.com/ubuntu groovy-proposed/main amd64 
Packages
  100 /var/lib/dpkg/status
   5.55-0ubuntu1 500
  500 http://br.archive.ubuntu.com/ubuntu groovy/main amd64 Packages
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2020-10-23 (25 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. Inspiron 5590
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-30-generic 
root=UUID=1e3484bb-be3c-4f5d-be22-044d9df06a4a ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-30.32-generic 5.8.17
  Tags:  groovy package-from-proposed
  Uname: Linux 5.8.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/13/2020
  dmi.bios.release: 1.11
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.11.0
  dmi.board.name: 0XRXN9
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A04
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.11.0:bd08/13/2020:br1.11:svnDellInc.:pnInspiron5590:pvr:rvnDellInc.:rn0XRXN9:rvrA04:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5590
  dmi.product.sku: 0957
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 14:F6:D8:6A:A3:F0  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN 
RX bytes:5307486 acl:57516 sco:0 events:78636 errors:0
TX bytes:18701 acl:357 sco:0 commands:841 errors:0
  mtime.conffile..etc.bluetooth.main.conf: 2020-11-04T10:53:00.842656

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1904638/+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 1904638] Re: Xbox Series X|S controller doesn't work and Xbox icon still blinks after pairing

[Marcos Alano]

apport information

** Tags added: apport-collected package-from-proposed

** Description changed:

  I have Xbox Series X|S controller and the Xbox icon still blinks after
  the successful pairing.
  
  I'm using Ubuntu 20.10 updated with BlueZ latest release. I'm following
  this bug closely and I can provide any information you need and do any
  tests you want.
  
  
  mhalano@glados:~$ lsb_release -rd
  Description:  Ubuntu 20.10
  Release:  20.10
  
  mhalano@glados:~$ apt policy bluez
  bluez:
Installed: 5.55-0ubuntu1.1
Candidate: 5.55-0ubuntu1.1
Version table:
   *** 5.55-0ubuntu1.1 500
  500 http://br.archive.ubuntu.com/ubuntu groovy-proposed/main amd64 
Packages
  100 /var/lib/dpkg/status
   5.55-0ubuntu1 500
  500 http://br.archive.ubuntu.com/ubuntu groovy/main amd64 Packages
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu50.2
+ Architecture: amd64
+ CasperMD5CheckResult: skip
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 20.10
+ InstallationDate: Installed on 2020-10-23 (25 days ago)
+ InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
+ InterestingModules: rfcomm bnep btusb bluetooth
+ MachineType: Dell Inc. Inspiron 5590
+ NonfreeKernelModules: nvidia_modeset nvidia
+ Package: linux
+ PackageArchitecture: amd64
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-30-generic 
root=UUID=1e3484bb-be3c-4f5d-be22-044d9df06a4a ro quiet splash vt.handoff=7
+ ProcVersionSignature: Ubuntu 5.8.0-30.32-generic 5.8.17
+ Tags:  groovy package-from-proposed
+ Uname: Linux 5.8.0-30-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 08/13/2020
+ dmi.bios.release: 1.11
+ dmi.bios.vendor: Dell Inc.
+ dmi.bios.version: 1.11.0
+ dmi.board.name: 0XRXN9
+ dmi.board.vendor: Dell Inc.
+ dmi.board.version: A04
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: Dell Inc.
+ dmi.modalias: 
dmi:bvnDellInc.:bvr1.11.0:bd08/13/2020:br1.11:svnDellInc.:pnInspiron5590:pvr:rvnDellInc.:rn0XRXN9:rvrA04:cvnDellInc.:ct10:cvr:
+ dmi.product.family: Inspiron
+ dmi.product.name: Inspiron 5590
+ dmi.product.sku: 0957
+ dmi.sys.vendor: Dell Inc.
+ hciconfig:
+  hci0:Type: Primary  Bus: USB
+   BD Address: 14:F6:D8:6A:A3:F0  ACL MTU: 1021:4  SCO MTU: 96:6
+   UP RUNNING PSCAN ISCAN 
+   RX bytes:5307486 acl:57516 sco:0 events:78636 errors:0
+   TX bytes:18701 acl:357 sco:0 commands:841 errors:0
+ mtime.conffile..etc.bluetooth.main.conf: 2020-11-04T10:53:00.842656

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1904638/+attachment/5435603/+files/CurrentDmesg.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1904638

Title:
  Xbox Series X|S controller doesn't work and Xbox icon still blinks
  after pairing

Status in bluez package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have Xbox Series X|S controller and the Xbox icon still blinks after
  the successful pairing.

  I'm using Ubuntu 20.10 updated with BlueZ latest release. I'm
  following this bug closely and I can provide any information you need
  and do any tests you want.

  
  mhalano@glados:~$ lsb_release -rd
  Description:  Ubuntu 20.10
  Release:  20.10

  mhalano@glados:~$ apt policy bluez
  bluez:
Installed: 5.55-0ubuntu1.1
Candidate: 5.55-0ubuntu1.1
Version table:
   *** 5.55-0ubuntu1.1 500
  500 http://br.archive.ubuntu.com/ubuntu groovy-proposed/main amd64 
Packages
  100 /var/lib/dpkg/status
   5.55-0ubuntu1 500
  500 http://br.archive.ubuntu.com/ubuntu groovy/main amd64 Packages
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2020-10-23 (25 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. Inspiron 5590
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-30-generic 
root=UUID=1e3484bb-be3c-4f5d-be22-044d9df06a4a ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-30.32-generic 5.8.17
  Tags:  groovy package-from-proposed
  Uname: Linux 5.8.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/13/2020
  dmi.bios.release: 1.11
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.11.0
  dmi.board.name: 0XRXN9
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A04
  dmi.chassis.type: 10
  dmi.chassis.vendor:

[Kernel-packages] [Bug 1904638] Re: Xbox Series X|S controller doesn't pair

[Marcos Alano]

I'm able to pair via command line, the problem the manin LED still blinks and 
the controller doesn't work (using jstest-gtk for test).
[MX Master 3]# pair 98:7A:14:D9:68:15
Attempting to pair with 98:7A:14:D9:68:15
[CHG] Device 98:7A:14:D9:68:15 Connected: yes
[CHG] Device 98:7A:14:D9:68:15 UUIDs: 0001-5f60-4c4f-9c83-a7953298d40d
[CHG] Device 98:7A:14:D9:68:15 UUIDs: 1800--1000-8000-00805f9b34fb
[CHG] Device 98:7A:14:D9:68:15 UUIDs: 1801--1000-8000-00805f9b34fb
[CHG] Device 98:7A:14:D9:68:15 UUIDs: 180a--1000-8000-00805f9b34fb
[CHG] Device 98:7A:14:D9:68:15 UUIDs: 180f--1000-8000-00805f9b34fb
[CHG] Device 98:7A:14:D9:68:15 UUIDs: 1812--1000-8000-00805f9b34fb
[CHG] Device 98:7A:14:D9:68:15 ServicesResolved: yes
[CHG] Device 98:7A:14:D9:68:15 Paired: yes
[NEW] Primary Service (Handle 0xeb71)
/org/bluez/hci0/dev_98_7A_14_D9_68_15/service0008
1801--1000-8000-00805f9b34fb
Generic Attribute Profile
[NEW] Primary Service (Handle 0xeb71)
/org/bluez/hci0/dev_98_7A_14_D9_68_15/service0009
180a--1000-8000-00805f9b34fb
Device Information
[NEW] Characteristic (Handle 0xab5b)
/org/bluez/hci0/dev_98_7A_14_D9_68_15/service0009/char000a
2a29--1000-8000-00805f9b34fb
Manufacturer Name String
[NEW] Characteristic (Handle 0xab5b)
/org/bluez/hci0/dev_98_7A_14_D9_68_15/service0009/char000c
2a50--1000-8000-00805f9b34fb
PnP ID
[NEW] Characteristic (Handle 0xab5b)
/org/bluez/hci0/dev_98_7A_14_D9_68_15/service0009/char000e
2a26--1000-8000-00805f9b34fb
Firmware Revision String
[NEW] Characteristic (Handle 0xab5b)
/org/bluez/hci0/dev_98_7A_14_D9_68_15/service0009/char0010
2a25--1000-8000-00805f9b34fb
Serial Number String
[NEW] Primary Service (Handle 0xeb71)
/org/bluez/hci0/dev_98_7A_14_D9_68_15/service0012
180f--1000-8000-00805f9b34fb
Battery Service
[NEW] Characteristic (Handle 0xab5b)
/org/bluez/hci0/dev_98_7A_14_D9_68_15/service0012/char0013
2a19--1000-8000-00805f9b34fb
Battery Level
[NEW] Descriptor (Handle 0x8400)
/org/bluez/hci0/dev_98_7A_14_D9_68_15/service0012/char0013/desc0015
2902--1000-8000-00805f9b34fb
Client Characteristic Configuration
[NEW] Primary Service (Handle 0xeb71)
/org/bluez/hci0/dev_98_7A_14_D9_68_15/service0024
0001-5f60-4c4f-9c83-a7953298d40d
Vendor specific
[NEW] Characteristic (Handle 0xab5b)
/org/bluez/hci0/dev_98_7A_14_D9_68_15/service0024/char0025
0002-5f60-4c4f-9c83-a7953298d40d
Vendor specific
[NEW] Characteristic (Handle 0xab5b)
/org/bluez/hci0/dev_98_7A_14_D9_68_15/service0024/char0027
0003-5f60-4c4f-9c83-a7953298d40d
Vendor specific
[NEW] Characteristic (Handle 0xab5b)
/org/bluez/hci0/dev_98_7A_14_D9_68_15/service0024/char0029
0004-5f60-4c4f-9c83-a7953298d40d
Vendor specific
Pairing successful
[CHG] Device 98:7A:14:D9:68:15 Modalias: usb:v045Ep0B13d0505
[CHG] Device 98:7A:14:D9:68:15 Name: Xbox Wireless Controller 987A14D96815
[CHG] Device 98:7A:14:D9:68:15 Alias: Xbox Wireless Controller 987A14D96815

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1904638

Title:
  Xbox Series X|S controller doesn't pair

Status in bluez package in Ubuntu:
  New

Bug description:
  I have Xbox Series X|S controller and the Xbox icon still blinks after
  the successful pairing.

  I'm using Ubuntu 20.10 updated with BlueZ latest release. I'm
  following this bug closely and I can provide any information you need
  and do any tests you want.

  
  mhalano@glados:~$ lsb_release -rd
  Description:  Ubuntu 20.10
  Release:  20.10

  mhalano@glados:~$ apt policy bluez
  bluez:
Installed: 5.55-0ubuntu1.1
Candidate: 5.55-0ubuntu1.1
Version table:
   *** 5.55-0ubuntu1.1 500
  500 http://br.archive.ubuntu.com/ubuntu groovy-proposed/main amd64 
Packages
  100 /var/lib/dpkg/status
   5.55-0ubuntu1 500
  500 http://br.archive.ubuntu.com/ubuntu groovy/main amd64 Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1904638/+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 1904638] Re: Xbox Series X|S controller doesn't pair

[Marcos Alano]

[bluetooth]# pair 98:7A:14:D9:68:15
Attempting to pair with 98:7A:14:D9:68:15
Failed to pair: org.bluez.Error.ConnectionAttemptFailed
[DEL] Primary Service (Handle 0x1cf3)
/org/bluez/hci0/dev_98_7A_14_D9_68_15/service0008
1801--1000-8000-00805f9b34fb
Generic Attribute Profile
[DEL] Characteristic (Handle 0xce00)
/org/bluez/hci0/dev_98_7A_14_D9_68_15/service0009/char000a
2a29--1000-8000-00805f9b34fb
Manufacturer Name String
[DEL] Characteristic (Handle 0xce00)
/org/bluez/hci0/dev_98_7A_14_D9_68_15/service0009/char000c
2a50--1000-8000-00805f9b34fb
PnP ID
[DEL] Characteristic (Handle 0xce00)
/org/bluez/hci0/dev_98_7A_14_D9_68_15/service0009/char000e
2a26--1000-8000-00805f9b34fb
Firmware Revision String
[DEL] Characteristic (Handle 0xce00)
/org/bluez/hci0/dev_98_7A_14_D9_68_15/service0009/char0010
2a25--1000-8000-00805f9b34fb
Serial Number String
[DEL] Primary Service (Handle 0x20c0)
/org/bluez/hci0/dev_98_7A_14_D9_68_15/service0009
180a--1000-8000-00805f9b34fb
Device Information
[DEL] Descriptor (Handle 0x16e0)
/org/bluez/hci0/dev_98_7A_14_D9_68_15/service0012/char0013/desc0015
2902--1000-8000-00805f9b34fb
Client Characteristic Configuration
[DEL] Characteristic (Handle 0xce00)
/org/bluez/hci0/dev_98_7A_14_D9_68_15/service0012/char0013
2a19--1000-8000-00805f9b34fb
Battery Level
[DEL] Primary Service (Handle 0xf3c0)
/org/bluez/hci0/dev_98_7A_14_D9_68_15/service0012
180f--1000-8000-00805f9b34fb
Battery Service
[DEL] Characteristic (Handle 0xce00)
/org/bluez/hci0/dev_98_7A_14_D9_68_15/service0024/char0025
0002-5f60-4c4f-9c83-a7953298d40d
Vendor specific
[DEL] Characteristic (Handle 0xce00)
/org/bluez/hci0/dev_98_7A_14_D9_68_15/service0024/char0027
0003-5f60-4c4f-9c83-a7953298d40d
Vendor specific
[DEL] Characteristic (Handle 0xce00)
/org/bluez/hci0/dev_98_7A_14_D9_68_15/service0024/char0029
0004-5f60-4c4f-9c83-a7953298d40d
Vendor specific
[DEL] Primary Service (Handle 0x86d0)
/org/bluez/hci0/dev_98_7A_14_D9_68_15/service0024
0001-5f60-4c4f-9c83-a7953298d40d
Vendor specific
[DEL] Device 98:7A:14:D9:68:15 Xbox Wireless Controller 987A14D96815

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1904638

Title:
  Xbox Series X|S controller doesn't pair

Status in bluez package in Ubuntu:
  New

Bug description:
  I have Xbox Series X|S controller and the Xbox icon still blinks after
  the successful pairing.

  I'm using Ubuntu 20.10 updated with BlueZ latest release. I'm
  following this bug closely and I can provide any information you need
  and do any tests you want.

  
  mhalano@glados:~$ lsb_release -rd
  Description:  Ubuntu 20.10
  Release:  20.10

  mhalano@glados:~$ apt policy bluez
  bluez:
Installed: 5.55-0ubuntu1.1
Candidate: 5.55-0ubuntu1.1
Version table:
   *** 5.55-0ubuntu1.1 500
  500 http://br.archive.ubuntu.com/ubuntu groovy-proposed/main amd64 
Packages
  100 /var/lib/dpkg/status
   5.55-0ubuntu1 500
  500 http://br.archive.ubuntu.com/ubuntu groovy/main amd64 Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1904638/+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 1904638] Re: Xbox Series X|S controller doesn't pair

[Marcos Alano]

[Xbox Wireless Controller 987A14D96815]# info 98:7A:14:D9:68:15
Device 98:7A:14:D9:68:15 (public)
Name: Xbox Wireless Controller 987A14D96815
Alias: Xbox Wireless Controller 987A14D96815
Appearance: 0x03c4
Icon: input-gaming
Paired: yes
Trusted: no
Blocked: no
Connected: yes
WakeAllowed: no
LegacyPairing: no
UUID: Vendor specific   (0001-5f60-4c4f-9c83-a7953298d40d)
UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb)
UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb)
UUID: Device Information(180a--1000-8000-00805f9b34fb)
UUID: Battery Service   (180f--1000-8000-00805f9b34fb)
UUID: Human Interface Device(1812--1000-8000-00805f9b34fb)
Modalias: usb:v045Ep0B13d0505
ManufacturerData Key: 0x0006
ManufacturerData Value:
  00   .   
RSSI: -45
TxPower: 20
Battery Percentage: 0x32 (50)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1904638

Title:
  Xbox Series X|S controller doesn't pair

Status in bluez package in Ubuntu:
  New

Bug description:
  I have Xbox Series X|S controller and the Xbox icon still blinks after
  the successful pairing.

  I'm using Ubuntu 20.10 updated with BlueZ latest release. I'm
  following this bug closely and I can provide any information you need
  and do any tests you want.

  
  mhalano@glados:~$ lsb_release -rd
  Description:  Ubuntu 20.10
  Release:  20.10

  mhalano@glados:~$ apt policy bluez
  bluez:
Installed: 5.55-0ubuntu1.1
Candidate: 5.55-0ubuntu1.1
Version table:
   *** 5.55-0ubuntu1.1 500
  500 http://br.archive.ubuntu.com/ubuntu groovy-proposed/main amd64 
Packages
  100 /var/lib/dpkg/status
   5.55-0ubuntu1 500
  500 http://br.archive.ubuntu.com/ubuntu groovy/main amd64 Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1904638/+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 1904638] [NEW] Xbox Series X|S controller doesn't pair

[Marcos Alano]

Public bug reported:

I have Xbox Series X|S controller and the Xbox icon still blinks after
the successful pairing.

I'm using Ubuntu 20.10 updated with BlueZ latest release. I'm following
this bug closely and I can provide any information you need and do any
tests you want.


mhalano@glados:~$ lsb_release -rd
Description:Ubuntu 20.10
Release:20.10

mhalano@glados:~$ apt policy bluez
bluez:
  Installed: 5.55-0ubuntu1.1
  Candidate: 5.55-0ubuntu1.1
  Version table:
 *** 5.55-0ubuntu1.1 500
500 http://br.archive.ubuntu.com/ubuntu groovy-proposed/main amd64 
Packages
100 /var/lib/dpkg/status
 5.55-0ubuntu1 500
500 http://br.archive.ubuntu.com/ubuntu groovy/main amd64 Packages

** Affects: bluez (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1904638

Title:
  Xbox Series X|S controller doesn't pair

Status in bluez package in Ubuntu:
  New

Bug description:
  I have Xbox Series X|S controller and the Xbox icon still blinks after
  the successful pairing.

  I'm using Ubuntu 20.10 updated with BlueZ latest release. I'm
  following this bug closely and I can provide any information you need
  and do any tests you want.

  
  mhalano@glados:~$ lsb_release -rd
  Description:  Ubuntu 20.10
  Release:  20.10

  mhalano@glados:~$ apt policy bluez
  bluez:
Installed: 5.55-0ubuntu1.1
Candidate: 5.55-0ubuntu1.1
Version table:
   *** 5.55-0ubuntu1.1 500
  500 http://br.archive.ubuntu.com/ubuntu groovy-proposed/main amd64 
Packages
  100 /var/lib/dpkg/status
   5.55-0ubuntu1 500
  500 http://br.archive.ubuntu.com/ubuntu groovy/main amd64 Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1904638/+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 1769423] Re: Xbox One S Bluetooth Controller Won't Connect

[Marcos Alano]

Could we have this workaround enabled out-of-the-box?

-- 
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/1769423

Title:
  Xbox One S Bluetooth Controller Won't Connect

Status in linux package in Ubuntu:
  Expired

Bug description:
  When attempting to connect a bluetooth xbox controller the controller
  would fail to connect. Either, an error message saying "This device
  could not be connected" or the controller would connect, then
  disconnect constantly.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-21-lowlatency 4.15.0-21.22
  ProcVersionSignature: Ubuntu 4.15.0-21.22-lowlatency 4.15.17
  Uname: Linux 4.15.0-21-lowlatency x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sun May  6 13:52:05 2018
  InstallationDate: Installed on 2018-04-17 (18 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
  SourcePackage: linux-signed
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1769423/+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 1635115] Re: grub fails zfs root filesystem detection due to failed checksum

[Marcos Alano]

I'm having the same problem with Ubuntu 20.4 after update my kernel.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1635115

Title:
  grub fails zfs root filesystem detection due to failed checksum

Status in grub2 package in Ubuntu:
  Confirmed
Status in zfs-linux package in Ubuntu:
  Won't Fix

Bug description:
  root@q-1-d.sv1:~# lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  root@q-1-d.sv1:~# apt-cache policy grub2-common
  grub2-common:
Installed: 2.02~beta2-36ubuntu3.2
Candidate: 2.02~beta2-36ubuntu3.2
Version table:
   *** 2.02~beta2-36ubuntu3.2 500
  500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   2.02~beta2-36ubuntu3 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  
  I followed https://github.com/zfsonlinux/zfs/wiki/Ubuntu-16.04-Root-on-ZFS to 
make a ZFS native root disk system.  

  Installation went fine, systems works like a champ... but then, after
  a while, it's time to apt-get update ; apt-get upgrade to update my
  kernel.  That apt-get install fails because grub can't detect it's
  root file system:

  root@q-2-d.sv1:~# grub-probe /
  grub-probe: error: unknown filesystem.

  Strange, this use to work.  Add in a -vv and I see:

  grub-core/kern/fs.c:56: Detecting zfs...
  grub-core/osdep/hostdisk.c:415: opening the device `/dev/sda1' in 
open_device()
  grub-core/fs/zfs/zfs.c:1192: label ok 0
  grub-core/osdep/hostdisk.c:394: reusing open device `/dev/sda1'
  grub-core/fs/zfs/zfs.c:1007: check 2 passed
  grub-core/fs/zfs/zfs.c:1018: check 3 passed
  grub-core/fs/zfs/zfs.c:1025: check 4 passed
  grub-core/fs/zfs/zfs.c:1035: check 6 passed
  grub-core/fs/zfs/zfs.c:1043: check 7 passed
  grub-core/fs/zfs/zfs.c:1054: check 8 passed
  grub-core/fs/zfs/zfs.c:1064: check 9 passed
  grub-core/fs/zfs/zfs.c:1086: check 11 passed
  grub-core/fs/zfs/zfs.c:1112: check 10 passed
  grub-core/fs/zfs/zfs.c:1128: str=com.delphix:hole_birth
  grub-core/fs/zfs/zfs.c:1128: str=com.delphix:embedded_data
  grub-core/fs/zfs/zfs.c:1137: check 12 passed (feature flags)
  grub-core/fs/zfs/zfs.c:1875: zio_read: E 0: size 2048/2048
  grub-core/fs/zfs/zfs.c:1898: endian = -1
  grub-core/fs/zfs/zfs.c:595: dva=8, b00258
  grub-core/osdep/hostdisk.c:394: reusing open device `/dev/sda1'
  grub-core/fs/zfs/zfs.c:442: checksum fletcher4 verification failed
  grub-core/fs/zfs/zfs.c:447: actual checksum 0059d95adad1 6322fba304b3 
00430f321ad7f439 21e873b51c15e3bc
  grub-core/fs/zfs/zfs.c:452: expected checksum 00035ca143fb 
062fc3a48ff8 0005b49e0d96b07e 03841abf1fed586a
  grub-core/fs/zfs/zfs.c:1919: incorrect checksum
  grub-core/kern/fs.c:78: zfs detection failed.

  Now here's the fun part.  Rebooting the system will fix the checksum
  issue for a short amount of time.  Here is what it looks like
  immediately after a reboot:

  root@q-1-d.sv1:~# grub-probe /
  zfs

  grub-core/kern/fs.c:56: Detecting zfs...
  grub-core/osdep/hostdisk.c:415: opening the device `/dev/sda1' in 
open_device()
  grub-core/fs/zfs/zfs.c:1192: label ok 0
  grub-core/osdep/hostdisk.c:394: reusing open device `/dev/sda1'
  grub-core/fs/zfs/zfs.c:1007: check 2 passed
  grub-core/fs/zfs/zfs.c:1018: check 3 passed
  grub-core/fs/zfs/zfs.c:1025: check 4 passed
  grub-core/fs/zfs/zfs.c:1035: check 6 passed
  grub-core/fs/zfs/zfs.c:1043: check 7 passed
  grub-core/fs/zfs/zfs.c:1054: check 8 passed
  grub-core/fs/zfs/zfs.c:1064: check 9 passed
  grub-core/fs/zfs/zfs.c:1086: check 11 passed
  grub-core/fs/zfs/zfs.c:1112: check 10 passed
  grub-core/fs/zfs/zfs.c:1128: str=com.delphix:hole_birth
  grub-core/fs/zfs/zfs.c:1128: str=com.delphix:embedded_data
  grub-core/fs/zfs/zfs.c:1137: check 12 passed (feature flags)
  grub-core/fs/zfs/zfs.c:1875: zio_read: E 0: size 2048/2048
  grub-core/fs/zfs/zfs.c:1898: endian = -1
  grub-core/fs/zfs/zfs.c:595: dva=8, c001c0
  grub-core/osdep/hostdisk.c:394: reusing open device `/dev/sda1'
  grub-core/fs/zfs/zfs.c:2678: endian = -1, blkid=0
  grub-core/fs/zfs/zfs.c:2020: endian = -1
  grub-core/fs/zfs/zfs.c:2051: endian = -1
  grub-core/fs/zfs/zfs.c:1875: zio_read: E 0: size 16384/4096
  grub-core/fs/zfs/zfs.c:1898: endian = -1
  grub-core/fs/zfs/zfs.c:595: dva=8, c001b8
  grub-core/osdep/hostdisk.c:394: reusing open device `/dev/sda1'
  grub-core/fs/zfs/zfs.c:2020: endian = 1
  grub-core/fs/zfs/zfs.c:2046: endian = 1
  grub-core/fs/zfs/zfs.c:1875: zio_read: E 0: size 16384/4096
  grub-core/fs/zfs/zfs.c:1898: endian = 1
  grub-core/fs/zfs/zfs.c:595: dva=8, c001a0
  grub-core/fs/zfs/zfs.c:2682: alive
  grub-core/fs/zfs/zfs.c:2493: looking for 'features_for_read'
  grub-core/fs/zfs/zfs.c:2020: endian = 1
  grub-core/fs/zfs/zfs.c:2046: endian = 1
  grub-core/fs/zfs/zfs.c:1875: zio_read: E 0: size 16384/4096
  grub-core/fs/zfs/zfs.c:1898: endia

[Kernel-packages] [Bug 1664062] Re: Can't load intel-rng module

[Marcos Alano]

I have the same problem with i7 7th gen. using a fresh Artful
installation.

-- 
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/1664062

Title:
  Can't load intel-rng module

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a laptop with Haswell processor which has a hardware random number 
generator. I confirmed that with the command 'grep rdrand /proc/cpuinfo'.
  The problem is when I try to load the 'intel-rng' kernel module to use the 
device with rngd daemon, it says 'no such device'. I'm not a great Linux 
expert, but the problem seems the PCI IDs for my computer's chipset isn't on 
module, so become impossible to detect the device. I tried the same with 
4.10rc7 kernel from PPA and the problem continues. I'm having a problem how to 
which PCI device contains RNG support and how create a new modalias to bypass 
the detection. If I could do that, I could report exactly what is the PCI IDs 
to correct the RNG detection.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.9.0-16-generic 4.9.0-16.17
  ProcVersionSignature: Ubuntu 4.9.0-16.17-generic 4.9.6
  Uname: Linux 4.9.0-16-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  marcos 6288 F pulseaudio
   /dev/snd/controlC1:  marcos 6288 F pulseaudio
   /dev/snd/controlC0:  marcos 6288 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Feb 12 19:06:49 2017
  HibernationDevice: RESUME=UUID=120c9111-82df-448d-a8d1-dc6b4822f7ac
  InstallationDate: Installed on 2016-08-03 (192 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Dell Inc. Inspiron 5437
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.9.0-16-generic 
root=UUID=7b80ab6d-8a48-4582-ace8-0b11e10026b6 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.9.0-16-generic N/A
   linux-backports-modules-4.9.0-16-generic  N/A
   linux-firmware1.162
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/07/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 03X56P
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A10
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd06/07/2016:svnDellInc.:pnInspiron5437:pvrNotSpecified:rvnDellInc.:rn03X56P:rvrA10:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 5437
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1664062/+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

Re: [Kernel-packages] [Bug 1521173] Re: AER: Corrected error received: id=00e0

[Marcos Alano]

I entered on BIOS and set the option "Fastboot" to "through". I would
like people check what value is selected for this option and change to
check if error persists. Some people could help me on that?

On Fri, Nov 10, 2017 at 10:37 AM, Sasha Stadnik
<1521...@bugs.launchpad.net> wrote:
> I had the same problem on Linux Lubuntu 17.10 (4.13.0-16-generic)
> Asus X550VXK Intel i7, Nvidia Geforce GTX 950M
>
> First at all i had black screen, temporary added "nomodeset" to grub
> menu solved it.
>
> pci=noaer helped me to get rid of "PCIe Bus Error: severity=Corrected,
> type=Physical Layer"
>
> After that i had wifi problems (often loses connections etc), posts below 
> helped me to fix wifi
> https://forum.manjaro.org/t/wifi-fails-time-to-time-rtl8821ae/28914/9
> the same in 
> https://medium.com/@elmaxx/rtl8821ae-wifi-drivers-in-ubuntu-16-04-4c1286524afa
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1521173
>
> Title:
>   AER: Corrected error received: id=00e0
>
> Status in Linux:
>   Unknown
> Status in linux package in Ubuntu:
>   Confirmed
> Status in linux source package in Xenial:
>   Triaged
>
> Bug description:
>   Note: Current workaround is to add pci=noaer to your kernel command
>   line:
>
>   1) edit /etc/default/grub and and add pci=noaer to the line starting with 
> GRUB_CMDLINE_LINUX_DEFAULT. It will look like this:
>   GRUB_CMDLINE_LINUX_DEFAULT="quiet splash pci=noaer"
>   2) run "sudo update-grub"
>   3) reboot
>
>   
>
>   My dmesg gets completely spammed with the following messages appearing
>   over and over again. It stops after one s3 cycle; it only happens
>   after reboot.
>
>   [ 5315.986588] pcieport :00:1c.0: AER: Corrected error received: id=00e0
>   [ 5315.987249] pcieport :00:1c.0: can't find device of ID00e0
>   [ 5315.995632] pcieport :00:1c.0: AER: Corrected error received: id=00e0
>   [ 5315.995664] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, 
> type=Physical Layer, id=00e0(Receiver ID)
>   [ 5315.995674] pcieport :00:1c.0:   device [8086:9d14] error 
> status/mask=0001/2000
>   [ 5315.995683] pcieport :00:1c.0:[ 0] Receiver Error
>   [ 5316.002772] pcieport :00:1c.0: AER: Corrected error received: id=00e0
>   [ 5316.002811] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, 
> type=Physical Layer, id=00e0(Receiver ID)
>   [ 5316.002826] pcieport :00:1c.0:   device [8086:9d14] error 
> status/mask=0001/2000
>   [ 5316.002838] pcieport :00:1c.0:[ 0] Receiver Error
>   [ 5316.009926] pcieport :00:1c.0: AER: Corrected error received: id=00e0
>   [ 5316.009964] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, 
> type=Physical Layer, id=00e0(Receiver ID)
>   [ 5316.009979] pcieport :00:1c.0:   device [8086:9d14] error 
> status/mask=0001/2000
>   [ 5316.009991] pcieport :00:1c.0:[ 0] Receiver Error
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 16.04
>   Package: linux-image-4.2.0-19-generic 4.2.0-19.23 [modified: 
> boot/vmlinuz-4.2.0-19-generic]
>   ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
>   Uname: Linux 4.2.0-19-generic x86_64
>   ApportVersion: 2.19.2-0ubuntu8
>   Architecture: amd64
>   AudioDevicesInUse:
>USERPID ACCESS COMMAND
>/dev/snd/pcmC0D0c:   david  1502 F...m pulseaudio
>/dev/snd/controlC0:  david  1502 F pulseaudio
>   CurrentDesktop: Unity
>   Date: Mon Nov 30 13:19:00 2015
>   EcryptfsInUse: Yes
>   HibernationDevice: RESUME=UUID=fe528b90-b4eb-4a20-82bd-6a03b79cfb14
>   InstallationDate: Installed on 2015-11-28 (2 days ago)
>   InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151127)
>   MachineType: Dell Inc. Inspiron 13-7359
>   ProcFB: 0 inteldrmfb
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic.efi.signed 
> root=UUID=94d54f88-5d18-4e2b-960a-8717d6e618bb ro noprompt persistent quiet 
> splash vt.handoff=7
>   RelatedPackageVersions:
>linux-restricted-modules-4.2.0-19-generic N/A
>linux-backports-modules-4.2.0-19-generic  N/A
>linux-firmware1.153
>   SourcePackage: linux
>   UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 08/07/2015
>   dmi.bios.vendor: Dell Inc.
>   dmi.bios.version: 01.00.00
>   dmi.board.name: 0NT3WX
>   dmi.board.vendor: Dell Inc.
>   dmi.board.version: A00
>   dmi.chassis.type: 9
>   dmi.chassis.vendor: Dell Inc.
>   dmi.modalias: 
> dmi:bvnDellInc.:bvr01.00.00:bd08/07/2015:svnDellInc.:pnInspiron13-7359:pvr:rvnDellInc.:rn0NT3WX:rvrA00:cvnDellInc.:ct9:cvr:
>   dmi.product.name: Inspiron 13-7359
>   dmi.sys.vendor: Dell Inc.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/linux/+bug/1521173/+subscriptions


-- 
Marcos H. Alano
Linux System Administrator
marcoshal...@gmail.com

-- 
You rece

[Kernel-packages] [Bug 1521173] Re: AER: Corrected error received: id=00e0

[Marcos Alano]

This message just occurs to me when I set the "Fastboot" option on BIOS
to "Minimal" instead of "Through". I think the Linux isn't ready yet for
Fastboot feature.

-- 
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/1521173

Title:
  AER: Corrected error received: id=00e0

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Triaged

Bug description:
  Note: Current workaround is to add pci=noaer to your kernel command
  line:

  1) edit /etc/default/grub and and add pci=noaer to the line starting with 
GRUB_CMDLINE_LINUX_DEFAULT. It will look like this: 
  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash pci=noaer"
  2) run "sudo update-grub"
  3) reboot

  

  My dmesg gets completely spammed with the following messages appearing
  over and over again. It stops after one s3 cycle; it only happens
  after reboot.

  [ 5315.986588] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5315.987249] pcieport :00:1c.0: can't find device of ID00e0
  [ 5315.995632] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5315.995664] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e0(Receiver ID)
  [ 5315.995674] pcieport :00:1c.0:   device [8086:9d14] error 
status/mask=0001/2000
  [ 5315.995683] pcieport :00:1c.0:[ 0] Receiver Error
  [ 5316.002772] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5316.002811] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e0(Receiver ID)
  [ 5316.002826] pcieport :00:1c.0:   device [8086:9d14] error 
status/mask=0001/2000
  [ 5316.002838] pcieport :00:1c.0:[ 0] Receiver Error
  [ 5316.009926] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5316.009964] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e0(Receiver ID)
  [ 5316.009979] pcieport :00:1c.0:   device [8086:9d14] error 
status/mask=0001/2000
  [ 5316.009991] pcieport :00:1c.0:[ 0] Receiver Error

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.2.0-19-generic 4.2.0-19.23 [modified: 
boot/vmlinuz-4.2.0-19-generic]
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Uname: Linux 4.2.0-19-generic x86_64
  ApportVersion: 2.19.2-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   david  1502 F...m pulseaudio
   /dev/snd/controlC0:  david  1502 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Nov 30 13:19:00 2015
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=fe528b90-b4eb-4a20-82bd-6a03b79cfb14
  InstallationDate: Installed on 2015-11-28 (2 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151127)
  MachineType: Dell Inc. Inspiron 13-7359
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic.efi.signed 
root=UUID=94d54f88-5d18-4e2b-960a-8717d6e618bb ro noprompt persistent quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-19-generic N/A
   linux-backports-modules-4.2.0-19-generic  N/A
   linux-firmware1.153
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/07/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.00.00
  dmi.board.name: 0NT3WX
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.00.00:bd08/07/2015:svnDellInc.:pnInspiron13-7359:pvr:rvnDellInc.:rn0NT3WX:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 13-7359
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1521173/+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 1521173] Re: AER: Corrected error received: id=00e0

[Marcos Alano]

I'm using Ubuntu 17.10 on a i7 Skylake and using the "pci=noaer"tip the
message goes away. Now I need to find out what this option means to see
if I'm losing something.

-- 
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/1521173

Title:
  AER: Corrected error received: id=00e0

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Triaged

Bug description:
  Note: Current workaround is to add pci=noaer to your kernel command
  line:

  1) edit /etc/default/grub and and add pci=noaer to the line starting with 
GRUB_CMDLINE_LINUX_DEFAULT. It will look like this: 
  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash pci=noaer"
  2) run "sudo update-grub"
  3) reboot

  

  My dmesg gets completely spammed with the following messages appearing
  over and over again. It stops after one s3 cycle; it only happens
  after reboot.

  [ 5315.986588] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5315.987249] pcieport :00:1c.0: can't find device of ID00e0
  [ 5315.995632] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5315.995664] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e0(Receiver ID)
  [ 5315.995674] pcieport :00:1c.0:   device [8086:9d14] error 
status/mask=0001/2000
  [ 5315.995683] pcieport :00:1c.0:[ 0] Receiver Error
  [ 5316.002772] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5316.002811] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e0(Receiver ID)
  [ 5316.002826] pcieport :00:1c.0:   device [8086:9d14] error 
status/mask=0001/2000
  [ 5316.002838] pcieport :00:1c.0:[ 0] Receiver Error
  [ 5316.009926] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5316.009964] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e0(Receiver ID)
  [ 5316.009979] pcieport :00:1c.0:   device [8086:9d14] error 
status/mask=0001/2000
  [ 5316.009991] pcieport :00:1c.0:[ 0] Receiver Error

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.2.0-19-generic 4.2.0-19.23 [modified: 
boot/vmlinuz-4.2.0-19-generic]
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Uname: Linux 4.2.0-19-generic x86_64
  ApportVersion: 2.19.2-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   david  1502 F...m pulseaudio
   /dev/snd/controlC0:  david  1502 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Nov 30 13:19:00 2015
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=fe528b90-b4eb-4a20-82bd-6a03b79cfb14
  InstallationDate: Installed on 2015-11-28 (2 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151127)
  MachineType: Dell Inc. Inspiron 13-7359
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic.efi.signed 
root=UUID=94d54f88-5d18-4e2b-960a-8717d6e618bb ro noprompt persistent quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-19-generic N/A
   linux-backports-modules-4.2.0-19-generic  N/A
   linux-firmware1.153
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/07/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.00.00
  dmi.board.name: 0NT3WX
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.00.00:bd08/07/2015:svnDellInc.:pnInspiron13-7359:pvr:rvnDellInc.:rn0NT3WX:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 13-7359
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1521173/+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 1676070] UdevDb.txt

[Marcos Alano]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1676070/+attachment/4845808/+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/1676070

Title:
  Wrong button's map for Logitech M560

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I opened this bug a long time ago for Ubuntu 15.10. Now I installed a
  fresh Ubuntu 17.04 beta 2 and used xev to detect the button codes for
  this mouse and still use the wrong codes.

  Some mouses come with buttons on the wheel, so you can move the wheel
  to left and right and the mouse execute clicks.

  The problem is: to this clicks work on browser as back and forward
  functions, the buttons need to produce the codes 8 (back) and 9
  (forward). I know that because I also have a Logitech M325 mouse which
  has buttons on wheel's side and works out-of-the-box on the browser,
  emitting codes 8 and 9.

  The Logitech M560 mouse has this buttons on wheel's side, but produces
  codes 6 (left side) and 7 (right side). So out-of-the-box, this
  wheel's side buttons just work to scroll for left and right. Even this
  is less useful than "back" and "forward" browser's buttons, I could
  agree if the lateral buttons (code 10 and 11), do the "back" forward"
  functions, but I think the best option is to remap the wheel's side
  buttons to code 8 and 9, to work as back and forward.

  My kernel version is:
  Ubuntu 4.10.0-14.16-generic 4.10.3
  --- 
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  marcos26749 F pulseaudio
  CurrentDesktop: Unity:Unity7
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-03-24 (1 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321)
  MachineType: Dell Inc. Vostro 1520
  NonfreeKernelModules: nvidia_uvm nvidia wl
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-13-generic 
root=UUID=5c3580d4-f0b6-4702-b515-95868d8f69f5 ro quiet splash
  ProcVersionSignature: Ubuntu 4.10.0-13.15-generic 4.10.1
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-13-generic N/A
   linux-backports-modules-4.10.0-13-generic  N/A
   linux-firmware 1.164
  Tags:  zesty
  Uname: Linux 4.10.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/05/2010
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0T808J
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd03/05/2010:svnDellInc.:pnVostro1520:pvrNull:rvnDellInc.:rn0T808J:rvr:cvnDellInc.:ct8:cvrN/A:
  dmi.product.name: Vostro 1520
  dmi.product.version: Null
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1676070/+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 1676070] ProcModules.txt

[Marcos Alano]

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1676070/+attachment/4845805/+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/1676070

Title:
  Wrong button's map for Logitech M560

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I opened this bug a long time ago for Ubuntu 15.10. Now I installed a
  fresh Ubuntu 17.04 beta 2 and used xev to detect the button codes for
  this mouse and still use the wrong codes.

  Some mouses come with buttons on the wheel, so you can move the wheel
  to left and right and the mouse execute clicks.

  The problem is: to this clicks work on browser as back and forward
  functions, the buttons need to produce the codes 8 (back) and 9
  (forward). I know that because I also have a Logitech M325 mouse which
  has buttons on wheel's side and works out-of-the-box on the browser,
  emitting codes 8 and 9.

  The Logitech M560 mouse has this buttons on wheel's side, but produces
  codes 6 (left side) and 7 (right side). So out-of-the-box, this
  wheel's side buttons just work to scroll for left and right. Even this
  is less useful than "back" and "forward" browser's buttons, I could
  agree if the lateral buttons (code 10 and 11), do the "back" forward"
  functions, but I think the best option is to remap the wheel's side
  buttons to code 8 and 9, to work as back and forward.

  My kernel version is:
  Ubuntu 4.10.0-14.16-generic 4.10.3
  --- 
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  marcos26749 F pulseaudio
  CurrentDesktop: Unity:Unity7
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-03-24 (1 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321)
  MachineType: Dell Inc. Vostro 1520
  NonfreeKernelModules: nvidia_uvm nvidia wl
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-13-generic 
root=UUID=5c3580d4-f0b6-4702-b515-95868d8f69f5 ro quiet splash
  ProcVersionSignature: Ubuntu 4.10.0-13.15-generic 4.10.1
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-13-generic N/A
   linux-backports-modules-4.10.0-13-generic  N/A
   linux-firmware 1.164
  Tags:  zesty
  Uname: Linux 4.10.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/05/2010
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0T808J
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd03/05/2010:svnDellInc.:pnVostro1520:pvrNull:rvnDellInc.:rn0T808J:rvr:cvnDellInc.:ct8:cvrN/A:
  dmi.product.name: Vostro 1520
  dmi.product.version: Null
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1676070/+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 1676070] RfKill.txt

[Marcos Alano]

apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1676070/+attachment/4845807/+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/1676070

Title:
  Wrong button's map for Logitech M560

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I opened this bug a long time ago for Ubuntu 15.10. Now I installed a
  fresh Ubuntu 17.04 beta 2 and used xev to detect the button codes for
  this mouse and still use the wrong codes.

  Some mouses come with buttons on the wheel, so you can move the wheel
  to left and right and the mouse execute clicks.

  The problem is: to this clicks work on browser as back and forward
  functions, the buttons need to produce the codes 8 (back) and 9
  (forward). I know that because I also have a Logitech M325 mouse which
  has buttons on wheel's side and works out-of-the-box on the browser,
  emitting codes 8 and 9.

  The Logitech M560 mouse has this buttons on wheel's side, but produces
  codes 6 (left side) and 7 (right side). So out-of-the-box, this
  wheel's side buttons just work to scroll for left and right. Even this
  is less useful than "back" and "forward" browser's buttons, I could
  agree if the lateral buttons (code 10 and 11), do the "back" forward"
  functions, but I think the best option is to remap the wheel's side
  buttons to code 8 and 9, to work as back and forward.

  My kernel version is:
  Ubuntu 4.10.0-14.16-generic 4.10.3
  --- 
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  marcos26749 F pulseaudio
  CurrentDesktop: Unity:Unity7
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-03-24 (1 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321)
  MachineType: Dell Inc. Vostro 1520
  NonfreeKernelModules: nvidia_uvm nvidia wl
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-13-generic 
root=UUID=5c3580d4-f0b6-4702-b515-95868d8f69f5 ro quiet splash
  ProcVersionSignature: Ubuntu 4.10.0-13.15-generic 4.10.1
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-13-generic N/A
   linux-backports-modules-4.10.0-13-generic  N/A
   linux-firmware 1.164
  Tags:  zesty
  Uname: Linux 4.10.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/05/2010
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0T808J
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd03/05/2010:svnDellInc.:pnVostro1520:pvrNull:rvnDellInc.:rn0T808J:rvr:cvnDellInc.:ct8:cvrN/A:
  dmi.product.name: Vostro 1520
  dmi.product.version: Null
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1676070/+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 1676070] ProcInterrupts.txt

[Marcos Alano]

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1676070/+attachment/4845804/+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/1676070

Title:
  Wrong button's map for Logitech M560

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I opened this bug a long time ago for Ubuntu 15.10. Now I installed a
  fresh Ubuntu 17.04 beta 2 and used xev to detect the button codes for
  this mouse and still use the wrong codes.

  Some mouses come with buttons on the wheel, so you can move the wheel
  to left and right and the mouse execute clicks.

  The problem is: to this clicks work on browser as back and forward
  functions, the buttons need to produce the codes 8 (back) and 9
  (forward). I know that because I also have a Logitech M325 mouse which
  has buttons on wheel's side and works out-of-the-box on the browser,
  emitting codes 8 and 9.

  The Logitech M560 mouse has this buttons on wheel's side, but produces
  codes 6 (left side) and 7 (right side). So out-of-the-box, this
  wheel's side buttons just work to scroll for left and right. Even this
  is less useful than "back" and "forward" browser's buttons, I could
  agree if the lateral buttons (code 10 and 11), do the "back" forward"
  functions, but I think the best option is to remap the wheel's side
  buttons to code 8 and 9, to work as back and forward.

  My kernel version is:
  Ubuntu 4.10.0-14.16-generic 4.10.3
  --- 
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  marcos26749 F pulseaudio
  CurrentDesktop: Unity:Unity7
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-03-24 (1 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321)
  MachineType: Dell Inc. Vostro 1520
  NonfreeKernelModules: nvidia_uvm nvidia wl
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-13-generic 
root=UUID=5c3580d4-f0b6-4702-b515-95868d8f69f5 ro quiet splash
  ProcVersionSignature: Ubuntu 4.10.0-13.15-generic 4.10.1
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-13-generic N/A
   linux-backports-modules-4.10.0-13-generic  N/A
   linux-firmware 1.164
  Tags:  zesty
  Uname: Linux 4.10.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/05/2010
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0T808J
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd03/05/2010:svnDellInc.:pnVostro1520:pvrNull:rvnDellInc.:rn0T808J:rvr:cvnDellInc.:ct8:cvrN/A:
  dmi.product.name: Vostro 1520
  dmi.product.version: Null
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1676070/+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 1676070] ProcCpuinfo.txt

[Marcos Alano]

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1676070/+attachment/4845802/+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/1676070

Title:
  Wrong button's map for Logitech M560

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I opened this bug a long time ago for Ubuntu 15.10. Now I installed a
  fresh Ubuntu 17.04 beta 2 and used xev to detect the button codes for
  this mouse and still use the wrong codes.

  Some mouses come with buttons on the wheel, so you can move the wheel
  to left and right and the mouse execute clicks.

  The problem is: to this clicks work on browser as back and forward
  functions, the buttons need to produce the codes 8 (back) and 9
  (forward). I know that because I also have a Logitech M325 mouse which
  has buttons on wheel's side and works out-of-the-box on the browser,
  emitting codes 8 and 9.

  The Logitech M560 mouse has this buttons on wheel's side, but produces
  codes 6 (left side) and 7 (right side). So out-of-the-box, this
  wheel's side buttons just work to scroll for left and right. Even this
  is less useful than "back" and "forward" browser's buttons, I could
  agree if the lateral buttons (code 10 and 11), do the "back" forward"
  functions, but I think the best option is to remap the wheel's side
  buttons to code 8 and 9, to work as back and forward.

  My kernel version is:
  Ubuntu 4.10.0-14.16-generic 4.10.3
  --- 
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  marcos26749 F pulseaudio
  CurrentDesktop: Unity:Unity7
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-03-24 (1 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321)
  MachineType: Dell Inc. Vostro 1520
  NonfreeKernelModules: nvidia_uvm nvidia wl
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-13-generic 
root=UUID=5c3580d4-f0b6-4702-b515-95868d8f69f5 ro quiet splash
  ProcVersionSignature: Ubuntu 4.10.0-13.15-generic 4.10.1
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-13-generic N/A
   linux-backports-modules-4.10.0-13-generic  N/A
   linux-firmware 1.164
  Tags:  zesty
  Uname: Linux 4.10.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/05/2010
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0T808J
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd03/05/2010:svnDellInc.:pnVostro1520:pvrNull:rvnDellInc.:rn0T808J:rvr:cvnDellInc.:ct8:cvrN/A:
  dmi.product.name: Vostro 1520
  dmi.product.version: Null
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1676070/+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 1676070] ProcEnviron.txt

[Marcos Alano]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1676070/+attachment/4845803/+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/1676070

Title:
  Wrong button's map for Logitech M560

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I opened this bug a long time ago for Ubuntu 15.10. Now I installed a
  fresh Ubuntu 17.04 beta 2 and used xev to detect the button codes for
  this mouse and still use the wrong codes.

  Some mouses come with buttons on the wheel, so you can move the wheel
  to left and right and the mouse execute clicks.

  The problem is: to this clicks work on browser as back and forward
  functions, the buttons need to produce the codes 8 (back) and 9
  (forward). I know that because I also have a Logitech M325 mouse which
  has buttons on wheel's side and works out-of-the-box on the browser,
  emitting codes 8 and 9.

  The Logitech M560 mouse has this buttons on wheel's side, but produces
  codes 6 (left side) and 7 (right side). So out-of-the-box, this
  wheel's side buttons just work to scroll for left and right. Even this
  is less useful than "back" and "forward" browser's buttons, I could
  agree if the lateral buttons (code 10 and 11), do the "back" forward"
  functions, but I think the best option is to remap the wheel's side
  buttons to code 8 and 9, to work as back and forward.

  My kernel version is:
  Ubuntu 4.10.0-14.16-generic 4.10.3
  --- 
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  marcos26749 F pulseaudio
  CurrentDesktop: Unity:Unity7
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-03-24 (1 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321)
  MachineType: Dell Inc. Vostro 1520
  NonfreeKernelModules: nvidia_uvm nvidia wl
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-13-generic 
root=UUID=5c3580d4-f0b6-4702-b515-95868d8f69f5 ro quiet splash
  ProcVersionSignature: Ubuntu 4.10.0-13.15-generic 4.10.1
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-13-generic N/A
   linux-backports-modules-4.10.0-13-generic  N/A
   linux-firmware 1.164
  Tags:  zesty
  Uname: Linux 4.10.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/05/2010
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0T808J
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd03/05/2010:svnDellInc.:pnVostro1520:pvrNull:rvnDellInc.:rn0T808J:rvr:cvnDellInc.:ct8:cvrN/A:
  dmi.product.name: Vostro 1520
  dmi.product.version: Null
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1676070/+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 1676070] PulseList.txt

[Marcos Alano]

apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1676070/+attachment/4845806/+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/1676070

Title:
  Wrong button's map for Logitech M560

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I opened this bug a long time ago for Ubuntu 15.10. Now I installed a
  fresh Ubuntu 17.04 beta 2 and used xev to detect the button codes for
  this mouse and still use the wrong codes.

  Some mouses come with buttons on the wheel, so you can move the wheel
  to left and right and the mouse execute clicks.

  The problem is: to this clicks work on browser as back and forward
  functions, the buttons need to produce the codes 8 (back) and 9
  (forward). I know that because I also have a Logitech M325 mouse which
  has buttons on wheel's side and works out-of-the-box on the browser,
  emitting codes 8 and 9.

  The Logitech M560 mouse has this buttons on wheel's side, but produces
  codes 6 (left side) and 7 (right side). So out-of-the-box, this
  wheel's side buttons just work to scroll for left and right. Even this
  is less useful than "back" and "forward" browser's buttons, I could
  agree if the lateral buttons (code 10 and 11), do the "back" forward"
  functions, but I think the best option is to remap the wheel's side
  buttons to code 8 and 9, to work as back and forward.

  My kernel version is:
  Ubuntu 4.10.0-14.16-generic 4.10.3
  --- 
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  marcos26749 F pulseaudio
  CurrentDesktop: Unity:Unity7
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-03-24 (1 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321)
  MachineType: Dell Inc. Vostro 1520
  NonfreeKernelModules: nvidia_uvm nvidia wl
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-13-generic 
root=UUID=5c3580d4-f0b6-4702-b515-95868d8f69f5 ro quiet splash
  ProcVersionSignature: Ubuntu 4.10.0-13.15-generic 4.10.1
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-13-generic N/A
   linux-backports-modules-4.10.0-13-generic  N/A
   linux-firmware 1.164
  Tags:  zesty
  Uname: Linux 4.10.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/05/2010
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0T808J
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd03/05/2010:svnDellInc.:pnVostro1520:pvrNull:rvnDellInc.:rn0T808J:rvr:cvnDellInc.:ct8:cvrN/A:
  dmi.product.name: Vostro 1520
  dmi.product.version: Null
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1676070/+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 1676070] Lsusb.txt

[Marcos Alano]

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1676070/+attachment/4845801/+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/1676070

Title:
  Wrong button's map for Logitech M560

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I opened this bug a long time ago for Ubuntu 15.10. Now I installed a
  fresh Ubuntu 17.04 beta 2 and used xev to detect the button codes for
  this mouse and still use the wrong codes.

  Some mouses come with buttons on the wheel, so you can move the wheel
  to left and right and the mouse execute clicks.

  The problem is: to this clicks work on browser as back and forward
  functions, the buttons need to produce the codes 8 (back) and 9
  (forward). I know that because I also have a Logitech M325 mouse which
  has buttons on wheel's side and works out-of-the-box on the browser,
  emitting codes 8 and 9.

  The Logitech M560 mouse has this buttons on wheel's side, but produces
  codes 6 (left side) and 7 (right side). So out-of-the-box, this
  wheel's side buttons just work to scroll for left and right. Even this
  is less useful than "back" and "forward" browser's buttons, I could
  agree if the lateral buttons (code 10 and 11), do the "back" forward"
  functions, but I think the best option is to remap the wheel's side
  buttons to code 8 and 9, to work as back and forward.

  My kernel version is:
  Ubuntu 4.10.0-14.16-generic 4.10.3
  --- 
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  marcos26749 F pulseaudio
  CurrentDesktop: Unity:Unity7
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-03-24 (1 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321)
  MachineType: Dell Inc. Vostro 1520
  NonfreeKernelModules: nvidia_uvm nvidia wl
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-13-generic 
root=UUID=5c3580d4-f0b6-4702-b515-95868d8f69f5 ro quiet splash
  ProcVersionSignature: Ubuntu 4.10.0-13.15-generic 4.10.1
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-13-generic N/A
   linux-backports-modules-4.10.0-13-generic  N/A
   linux-firmware 1.164
  Tags:  zesty
  Uname: Linux 4.10.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/05/2010
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0T808J
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd03/05/2010:svnDellInc.:pnVostro1520:pvrNull:rvnDellInc.:rn0T808J:rvr:cvnDellInc.:ct8:cvrN/A:
  dmi.product.name: Vostro 1520
  dmi.product.version: Null
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1676070/+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 1676070] WifiSyslog.txt

[Marcos Alano]

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1676070/+attachment/4845809/+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/1676070

Title:
  Wrong button's map for Logitech M560

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I opened this bug a long time ago for Ubuntu 15.10. Now I installed a
  fresh Ubuntu 17.04 beta 2 and used xev to detect the button codes for
  this mouse and still use the wrong codes.

  Some mouses come with buttons on the wheel, so you can move the wheel
  to left and right and the mouse execute clicks.

  The problem is: to this clicks work on browser as back and forward
  functions, the buttons need to produce the codes 8 (back) and 9
  (forward). I know that because I also have a Logitech M325 mouse which
  has buttons on wheel's side and works out-of-the-box on the browser,
  emitting codes 8 and 9.

  The Logitech M560 mouse has this buttons on wheel's side, but produces
  codes 6 (left side) and 7 (right side). So out-of-the-box, this
  wheel's side buttons just work to scroll for left and right. Even this
  is less useful than "back" and "forward" browser's buttons, I could
  agree if the lateral buttons (code 10 and 11), do the "back" forward"
  functions, but I think the best option is to remap the wheel's side
  buttons to code 8 and 9, to work as back and forward.

  My kernel version is:
  Ubuntu 4.10.0-14.16-generic 4.10.3
  --- 
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  marcos26749 F pulseaudio
  CurrentDesktop: Unity:Unity7
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-03-24 (1 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321)
  MachineType: Dell Inc. Vostro 1520
  NonfreeKernelModules: nvidia_uvm nvidia wl
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-13-generic 
root=UUID=5c3580d4-f0b6-4702-b515-95868d8f69f5 ro quiet splash
  ProcVersionSignature: Ubuntu 4.10.0-13.15-generic 4.10.1
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-13-generic N/A
   linux-backports-modules-4.10.0-13-generic  N/A
   linux-firmware 1.164
  Tags:  zesty
  Uname: Linux 4.10.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/05/2010
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0T808J
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd03/05/2010:svnDellInc.:pnVostro1520:pvrNull:rvnDellInc.:rn0T808J:rvr:cvnDellInc.:ct8:cvrN/A:
  dmi.product.name: Vostro 1520
  dmi.product.version: Null
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1676070/+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 1676070] IwConfig.txt

[Marcos Alano]

apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1676070/+attachment/4845798/+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/1676070

Title:
  Wrong button's map for Logitech M560

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I opened this bug a long time ago for Ubuntu 15.10. Now I installed a
  fresh Ubuntu 17.04 beta 2 and used xev to detect the button codes for
  this mouse and still use the wrong codes.

  Some mouses come with buttons on the wheel, so you can move the wheel
  to left and right and the mouse execute clicks.

  The problem is: to this clicks work on browser as back and forward
  functions, the buttons need to produce the codes 8 (back) and 9
  (forward). I know that because I also have a Logitech M325 mouse which
  has buttons on wheel's side and works out-of-the-box on the browser,
  emitting codes 8 and 9.

  The Logitech M560 mouse has this buttons on wheel's side, but produces
  codes 6 (left side) and 7 (right side). So out-of-the-box, this
  wheel's side buttons just work to scroll for left and right. Even this
  is less useful than "back" and "forward" browser's buttons, I could
  agree if the lateral buttons (code 10 and 11), do the "back" forward"
  functions, but I think the best option is to remap the wheel's side
  buttons to code 8 and 9, to work as back and forward.

  My kernel version is:
  Ubuntu 4.10.0-14.16-generic 4.10.3
  --- 
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  marcos26749 F pulseaudio
  CurrentDesktop: Unity:Unity7
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-03-24 (1 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321)
  MachineType: Dell Inc. Vostro 1520
  NonfreeKernelModules: nvidia_uvm nvidia wl
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-13-generic 
root=UUID=5c3580d4-f0b6-4702-b515-95868d8f69f5 ro quiet splash
  ProcVersionSignature: Ubuntu 4.10.0-13.15-generic 4.10.1
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-13-generic N/A
   linux-backports-modules-4.10.0-13-generic  N/A
   linux-firmware 1.164
  Tags:  zesty
  Uname: Linux 4.10.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/05/2010
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0T808J
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd03/05/2010:svnDellInc.:pnVostro1520:pvrNull:rvnDellInc.:rn0T808J:rvr:cvnDellInc.:ct8:cvrN/A:
  dmi.product.name: Vostro 1520
  dmi.product.version: Null
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1676070/+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 1676070] JournalErrors.txt

[Marcos Alano]

apport information

** Attachment added: "JournalErrors.txt"
   
https://bugs.launchpad.net/bugs/1676070/+attachment/4845799/+files/JournalErrors.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1676070

Title:
  Wrong button's map for Logitech M560

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I opened this bug a long time ago for Ubuntu 15.10. Now I installed a
  fresh Ubuntu 17.04 beta 2 and used xev to detect the button codes for
  this mouse and still use the wrong codes.

  Some mouses come with buttons on the wheel, so you can move the wheel
  to left and right and the mouse execute clicks.

  The problem is: to this clicks work on browser as back and forward
  functions, the buttons need to produce the codes 8 (back) and 9
  (forward). I know that because I also have a Logitech M325 mouse which
  has buttons on wheel's side and works out-of-the-box on the browser,
  emitting codes 8 and 9.

  The Logitech M560 mouse has this buttons on wheel's side, but produces
  codes 6 (left side) and 7 (right side). So out-of-the-box, this
  wheel's side buttons just work to scroll for left and right. Even this
  is less useful than "back" and "forward" browser's buttons, I could
  agree if the lateral buttons (code 10 and 11), do the "back" forward"
  functions, but I think the best option is to remap the wheel's side
  buttons to code 8 and 9, to work as back and forward.

  My kernel version is:
  Ubuntu 4.10.0-14.16-generic 4.10.3
  --- 
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  marcos26749 F pulseaudio
  CurrentDesktop: Unity:Unity7
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-03-24 (1 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321)
  MachineType: Dell Inc. Vostro 1520
  NonfreeKernelModules: nvidia_uvm nvidia wl
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-13-generic 
root=UUID=5c3580d4-f0b6-4702-b515-95868d8f69f5 ro quiet splash
  ProcVersionSignature: Ubuntu 4.10.0-13.15-generic 4.10.1
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-13-generic N/A
   linux-backports-modules-4.10.0-13-generic  N/A
   linux-firmware 1.164
  Tags:  zesty
  Uname: Linux 4.10.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/05/2010
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0T808J
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd03/05/2010:svnDellInc.:pnVostro1520:pvrNull:rvnDellInc.:rn0T808J:rvr:cvnDellInc.:ct8:cvrN/A:
  dmi.product.name: Vostro 1520
  dmi.product.version: Null
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1676070/+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 1676070] CRDA.txt

[Marcos Alano]

apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1676070/+attachment/4845796/+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/1676070

Title:
  Wrong button's map for Logitech M560

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I opened this bug a long time ago for Ubuntu 15.10. Now I installed a
  fresh Ubuntu 17.04 beta 2 and used xev to detect the button codes for
  this mouse and still use the wrong codes.

  Some mouses come with buttons on the wheel, so you can move the wheel
  to left and right and the mouse execute clicks.

  The problem is: to this clicks work on browser as back and forward
  functions, the buttons need to produce the codes 8 (back) and 9
  (forward). I know that because I also have a Logitech M325 mouse which
  has buttons on wheel's side and works out-of-the-box on the browser,
  emitting codes 8 and 9.

  The Logitech M560 mouse has this buttons on wheel's side, but produces
  codes 6 (left side) and 7 (right side). So out-of-the-box, this
  wheel's side buttons just work to scroll for left and right. Even this
  is less useful than "back" and "forward" browser's buttons, I could
  agree if the lateral buttons (code 10 and 11), do the "back" forward"
  functions, but I think the best option is to remap the wheel's side
  buttons to code 8 and 9, to work as back and forward.

  My kernel version is:
  Ubuntu 4.10.0-14.16-generic 4.10.3
  --- 
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  marcos26749 F pulseaudio
  CurrentDesktop: Unity:Unity7
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-03-24 (1 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321)
  MachineType: Dell Inc. Vostro 1520
  NonfreeKernelModules: nvidia_uvm nvidia wl
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-13-generic 
root=UUID=5c3580d4-f0b6-4702-b515-95868d8f69f5 ro quiet splash
  ProcVersionSignature: Ubuntu 4.10.0-13.15-generic 4.10.1
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-13-generic N/A
   linux-backports-modules-4.10.0-13-generic  N/A
   linux-firmware 1.164
  Tags:  zesty
  Uname: Linux 4.10.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/05/2010
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0T808J
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd03/05/2010:svnDellInc.:pnVostro1520:pvrNull:rvnDellInc.:rn0T808J:rvr:cvnDellInc.:ct8:cvrN/A:
  dmi.product.name: Vostro 1520
  dmi.product.version: Null
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1676070/+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 1676070] Lspci.txt

[Marcos Alano]

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1676070/+attachment/4845800/+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/1676070

Title:
  Wrong button's map for Logitech M560

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I opened this bug a long time ago for Ubuntu 15.10. Now I installed a
  fresh Ubuntu 17.04 beta 2 and used xev to detect the button codes for
  this mouse and still use the wrong codes.

  Some mouses come with buttons on the wheel, so you can move the wheel
  to left and right and the mouse execute clicks.

  The problem is: to this clicks work on browser as back and forward
  functions, the buttons need to produce the codes 8 (back) and 9
  (forward). I know that because I also have a Logitech M325 mouse which
  has buttons on wheel's side and works out-of-the-box on the browser,
  emitting codes 8 and 9.

  The Logitech M560 mouse has this buttons on wheel's side, but produces
  codes 6 (left side) and 7 (right side). So out-of-the-box, this
  wheel's side buttons just work to scroll for left and right. Even this
  is less useful than "back" and "forward" browser's buttons, I could
  agree if the lateral buttons (code 10 and 11), do the "back" forward"
  functions, but I think the best option is to remap the wheel's side
  buttons to code 8 and 9, to work as back and forward.

  My kernel version is:
  Ubuntu 4.10.0-14.16-generic 4.10.3
  --- 
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  marcos26749 F pulseaudio
  CurrentDesktop: Unity:Unity7
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-03-24 (1 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321)
  MachineType: Dell Inc. Vostro 1520
  NonfreeKernelModules: nvidia_uvm nvidia wl
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-13-generic 
root=UUID=5c3580d4-f0b6-4702-b515-95868d8f69f5 ro quiet splash
  ProcVersionSignature: Ubuntu 4.10.0-13.15-generic 4.10.1
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-13-generic N/A
   linux-backports-modules-4.10.0-13-generic  N/A
   linux-firmware 1.164
  Tags:  zesty
  Uname: Linux 4.10.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/05/2010
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0T808J
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd03/05/2010:svnDellInc.:pnVostro1520:pvrNull:rvnDellInc.:rn0T808J:rvr:cvnDellInc.:ct8:cvrN/A:
  dmi.product.name: Vostro 1520
  dmi.product.version: Null
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1676070/+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 1676070] CurrentDmesg.txt

[Marcos Alano]

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1676070/+attachment/4845797/+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/1676070

Title:
  Wrong button's map for Logitech M560

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I opened this bug a long time ago for Ubuntu 15.10. Now I installed a
  fresh Ubuntu 17.04 beta 2 and used xev to detect the button codes for
  this mouse and still use the wrong codes.

  Some mouses come with buttons on the wheel, so you can move the wheel
  to left and right and the mouse execute clicks.

  The problem is: to this clicks work on browser as back and forward
  functions, the buttons need to produce the codes 8 (back) and 9
  (forward). I know that because I also have a Logitech M325 mouse which
  has buttons on wheel's side and works out-of-the-box on the browser,
  emitting codes 8 and 9.

  The Logitech M560 mouse has this buttons on wheel's side, but produces
  codes 6 (left side) and 7 (right side). So out-of-the-box, this
  wheel's side buttons just work to scroll for left and right. Even this
  is less useful than "back" and "forward" browser's buttons, I could
  agree if the lateral buttons (code 10 and 11), do the "back" forward"
  functions, but I think the best option is to remap the wheel's side
  buttons to code 8 and 9, to work as back and forward.

  My kernel version is:
  Ubuntu 4.10.0-14.16-generic 4.10.3
  --- 
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  marcos26749 F pulseaudio
  CurrentDesktop: Unity:Unity7
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-03-24 (1 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321)
  MachineType: Dell Inc. Vostro 1520
  NonfreeKernelModules: nvidia_uvm nvidia wl
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-13-generic 
root=UUID=5c3580d4-f0b6-4702-b515-95868d8f69f5 ro quiet splash
  ProcVersionSignature: Ubuntu 4.10.0-13.15-generic 4.10.1
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-13-generic N/A
   linux-backports-modules-4.10.0-13-generic  N/A
   linux-firmware 1.164
  Tags:  zesty
  Uname: Linux 4.10.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/05/2010
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0T808J
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd03/05/2010:svnDellInc.:pnVostro1520:pvrNull:rvnDellInc.:rn0T808J:rvr:cvnDellInc.:ct8:cvrN/A:
  dmi.product.name: Vostro 1520
  dmi.product.version: Null
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1676070/+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 1676070] Re: Wrong button's map for Logitech M560

[Marcos Alano]

apport information

** Tags added: apport-collected zesty

** Description changed:

  I opened this bug a long time ago for Ubuntu 15.10. Now I installed a
  fresh Ubuntu 17.04 beta 2 and used xev to detect the button codes for
  this mouse and still use the wrong codes.
  
  Some mouses come with buttons on the wheel, so you can move the wheel to
  left and right and the mouse execute clicks.
  
  The problem is: to this clicks work on browser as back and forward
  functions, the buttons need to produce the codes 8 (back) and 9
  (forward). I know that because I also have a Logitech M325 mouse which
  has buttons on wheel's side and works out-of-the-box on the browser,
  emitting codes 8 and 9.
  
  The Logitech M560 mouse has this buttons on wheel's side, but produces
  codes 6 (left side) and 7 (right side). So out-of-the-box, this wheel's
  side buttons just work to scroll for left and right. Even this is less
  useful than "back" and "forward" browser's buttons, I could agree if the
  lateral buttons (code 10 and 11), do the "back" forward" functions, but
  I think the best option is to remap the wheel's side buttons to code 8
  and 9, to work as back and forward.
  
  My kernel version is:
  Ubuntu 4.10.0-14.16-generic 4.10.3
+ --- 
+ ApportVersion: 2.20.4-0ubuntu2
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  marcos26749 F pulseaudio
+ CurrentDesktop: Unity:Unity7
+ DistroRelease: Ubuntu 17.04
+ InstallationDate: Installed on 2017-03-24 (1 days ago)
+ InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321)
+ MachineType: Dell Inc. Vostro 1520
+ NonfreeKernelModules: nvidia_uvm nvidia wl
+ Package: linux (not installed)
+ ProcFB:
+  
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-13-generic 
root=UUID=5c3580d4-f0b6-4702-b515-95868d8f69f5 ro quiet splash
+ ProcVersionSignature: Ubuntu 4.10.0-13.15-generic 4.10.1
+ RelatedPackageVersions:
+  linux-restricted-modules-4.10.0-13-generic N/A
+  linux-backports-modules-4.10.0-13-generic  N/A
+  linux-firmware 1.164
+ Tags:  zesty
+ Uname: Linux 4.10.0-13-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 03/05/2010
+ dmi.bios.vendor: Dell Inc.
+ dmi.bios.version: A08
+ dmi.board.name: 0T808J
+ dmi.board.vendor: Dell Inc.
+ dmi.chassis.type: 8
+ dmi.chassis.vendor: Dell Inc.
+ dmi.chassis.version: N/A
+ dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd03/05/2010:svnDellInc.:pnVostro1520:pvrNull:rvnDellInc.:rn0T808J:rvr:cvnDellInc.:ct8:cvrN/A:
+ dmi.product.name: Vostro 1520
+ dmi.product.version: Null
+ dmi.sys.vendor: Dell Inc.

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1676070/+attachment/4845795/+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/1676070

Title:
  Wrong button's map for Logitech M560

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I opened this bug a long time ago for Ubuntu 15.10. Now I installed a
  fresh Ubuntu 17.04 beta 2 and used xev to detect the button codes for
  this mouse and still use the wrong codes.

  Some mouses come with buttons on the wheel, so you can move the wheel
  to left and right and the mouse execute clicks.

  The problem is: to this clicks work on browser as back and forward
  functions, the buttons need to produce the codes 8 (back) and 9
  (forward). I know that because I also have a Logitech M325 mouse which
  has buttons on wheel's side and works out-of-the-box on the browser,
  emitting codes 8 and 9.

  The Logitech M560 mouse has this buttons on wheel's side, but produces
  codes 6 (left side) and 7 (right side). So out-of-the-box, this
  wheel's side buttons just work to scroll for left and right. Even this
  is less useful than "back" and "forward" browser's buttons, I could
  agree if the lateral buttons (code 10 and 11), do the "back" forward"
  functions, but I think the best option is to remap the wheel's side
  buttons to code 8 and 9, to work as back and forward.

  My kernel version is:
  Ubuntu 4.10.0-14.16-generic 4.10.3
  --- 
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  marcos26749 F pulseaudio
  CurrentDesktop: Unity:Unity7
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-03-24 (1 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321)
  MachineType: Dell Inc. Vostro 1520
  NonfreeKernelModules: nvidia_uvm nvidia wl
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-13-generic 
root=UUID=5c3580d4-f0b6-4702-b515-95868d8f69f5 ro quiet splash
  ProcVersionSignature: Ubuntu 4.10.0-13.15-generic 4.10.1
  Relat

[Kernel-packages] [Bug 1676070] [NEW] Wrong button's map for Logitech M560

[Marcos Alano]

Public bug reported:

I opened this bug a long time ago for Ubuntu 15.10. Now I installed a
fresh Ubuntu 17.04 beta 2 and used xev to detect the button codes for
this mouse and still use the wrong codes.

Some mouses come with buttons on the wheel, so you can move the wheel to
left and right and the mouse execute clicks.

The problem is: to this clicks work on browser as back and forward
functions, the buttons need to produce the codes 8 (back) and 9
(forward). I know that because I also have a Logitech M325 mouse which
has buttons on wheel's side and works out-of-the-box on the browser,
emitting codes 8 and 9.

The Logitech M560 mouse has this buttons on wheel's side, but produces
codes 6 (left side) and 7 (right side). So out-of-the-box, this wheel's
side buttons just work to scroll for left and right. Even this is less
useful than "back" and "forward" browser's buttons, I could agree if the
lateral buttons (code 10 and 11), do the "back" forward" functions, but
I think the best option is to remap the wheel's side buttons to code 8
and 9, to work as back and forward.

My kernel version is:
Ubuntu 4.10.0-14.16-generic 4.10.3

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New

** Attachment added: "lspci-vnvn.log"
   
https://bugs.launchpad.net/bugs/1676070/+attachment/4845777/+files/lspci-vnvn.log

-- 
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/1676070

Title:
  Wrong button's map for Logitech M560

Status in linux package in Ubuntu:
  New

Bug description:
  I opened this bug a long time ago for Ubuntu 15.10. Now I installed a
  fresh Ubuntu 17.04 beta 2 and used xev to detect the button codes for
  this mouse and still use the wrong codes.

  Some mouses come with buttons on the wheel, so you can move the wheel
  to left and right and the mouse execute clicks.

  The problem is: to this clicks work on browser as back and forward
  functions, the buttons need to produce the codes 8 (back) and 9
  (forward). I know that because I also have a Logitech M325 mouse which
  has buttons on wheel's side and works out-of-the-box on the browser,
  emitting codes 8 and 9.

  The Logitech M560 mouse has this buttons on wheel's side, but produces
  codes 6 (left side) and 7 (right side). So out-of-the-box, this
  wheel's side buttons just work to scroll for left and right. Even this
  is less useful than "back" and "forward" browser's buttons, I could
  agree if the lateral buttons (code 10 and 11), do the "back" forward"
  functions, but I think the best option is to remap the wheel's side
  buttons to code 8 and 9, to work as back and forward.

  My kernel version is:
  Ubuntu 4.10.0-14.16-generic 4.10.3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1676070/+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 1094744] Re: MS Sculpt Touch Mouse needs to be re-paired periodically

[Marcos Alano]

How the status of this problem on a clean system with Ubuntu 16.04 or
16.10 or even 17.04?

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1094744

Title:
  MS Sculpt Touch Mouse needs to be re-paired periodically

Status in GNOME Bluetooth:
  Fix Released
Status in blueman package in Ubuntu:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed
Status in gnome-bluetooth package in Ubuntu:
  Fix Released
Status in blueman source package in Precise:
  Confirmed
Status in bluez source package in Precise:
  Confirmed
Status in gnome-bluetooth source package in Precise:
  Fix Released
Status in blueman source package in Quantal:
  Invalid
Status in bluez source package in Quantal:
  Won't Fix
Status in gnome-bluetooth source package in Quantal:
  Fix Released
Status in blueman source package in Raring:
  Invalid
Status in bluez source package in Raring:
  Won't Fix
Status in gnome-bluetooth source package in Raring:
  Won't Fix
Status in bluez package in Fedora:
  Unknown

Bug description:
  [Impact] The patch makes Microsoft Wedge/Sculpt Touch mice stay connected.
  [Test Case] Get a Microsoft Wedge/Sculpt Touch mouse, pair it, restart 
session, watch it automatically re-pair.
  [Regression Potential] Little. The patched piece of XML is only relevant to 
hardware having the same ID.

  When you don't use the mouse for a long enough time, the mouse
  disconnects and won't reconnect. I have to go into bluetooth settings,
  remove it, and re-pair it.

  1)
  ~ % lsb_release -rd
  Description:  Ubuntu 12.04.1 LTS
  Release:  12.04

  2)
  ~ % apt-cache policy bluez
  bluez:
    Installed: 4.98-2ubuntu7
    Candidate: 4.98-2ubuntu7
    Version table:
   *** 4.98-2ubuntu7 0
  500 http://us.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages
  100 /var/lib/dpkg/status

  3)
  I expected the mouse to reconnect automatically, or at least after I try to 
reconnect manually through the bluetooth settings.

  4)
  I have to re-pair the mouse in order to use it again. Turning the mouse off 
and on doesn't work either.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-bluetooth/+bug/1094744/+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 1664062] Re: Can't load intel-rng module

[Marcos Alano]

** 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/1664062

Title:
  Can't load intel-rng module

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a laptop with Haswell processor which has a hardware random number 
generator. I confirmed that with the command 'grep rdrand /proc/cpuinfo'.
  The problem is when I try to load the 'intel-rng' kernel module to use the 
device with rngd daemon, it says 'no such device'. I'm not a great Linux 
expert, but the problem seems the PCI IDs for my computer's chipset isn't on 
module, so become impossible to detect the device. I tried the same with 
4.10rc7 kernel from PPA and the problem continues. I'm having a problem how to 
which PCI device contains RNG support and how create a new modalias to bypass 
the detection. If I could do that, I could report exactly what is the PCI IDs 
to correct the RNG detection.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.9.0-16-generic 4.9.0-16.17
  ProcVersionSignature: Ubuntu 4.9.0-16.17-generic 4.9.6
  Uname: Linux 4.9.0-16-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  marcos 6288 F pulseaudio
   /dev/snd/controlC1:  marcos 6288 F pulseaudio
   /dev/snd/controlC0:  marcos 6288 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Feb 12 19:06:49 2017
  HibernationDevice: RESUME=UUID=120c9111-82df-448d-a8d1-dc6b4822f7ac
  InstallationDate: Installed on 2016-08-03 (192 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Dell Inc. Inspiron 5437
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.9.0-16-generic 
root=UUID=7b80ab6d-8a48-4582-ace8-0b11e10026b6 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.9.0-16-generic N/A
   linux-backports-modules-4.9.0-16-generic  N/A
   linux-firmware1.162
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/07/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 03X56P
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A10
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd06/07/2016:svnDellInc.:pnInspiron5437:pvrNotSpecified:rvnDellInc.:rn03X56P:rvrA10:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 5437
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1664062/+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 1664062] [NEW] Can't load intel-rng module

[Marcos Alano]

Public bug reported:

I have a laptop with Haswell processor which has a hardware random number 
generator. I confirmed that with the command 'grep rdrand /proc/cpuinfo'.
The problem is when I try to load the 'intel-rng' kernel module to use the 
device with rngd daemon, it says 'no such device'. I'm not a great Linux 
expert, but the problem seems the PCI IDs for my computer's chipset isn't on 
module, so become impossible to detect the device. I tried the same with 
4.10rc7 kernel from PPA and the problem continues. I'm having a problem how to 
which PCI device contains RNG support and how create a new modalias to bypass 
the detection. If I could do that, I could report exactly what is the PCI IDs 
to correct the RNG detection.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: linux-image-4.9.0-16-generic 4.9.0-16.17
ProcVersionSignature: Ubuntu 4.9.0-16.17-generic 4.9.6
Uname: Linux 4.9.0-16-generic x86_64
ApportVersion: 2.20.4-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC2:  marcos 6288 F pulseaudio
 /dev/snd/controlC1:  marcos 6288 F pulseaudio
 /dev/snd/controlC0:  marcos 6288 F pulseaudio
CurrentDesktop: Unity
Date: Sun Feb 12 19:06:49 2017
HibernationDevice: RESUME=UUID=120c9111-82df-448d-a8d1-dc6b4822f7ac
InstallationDate: Installed on 2016-08-03 (192 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
MachineType: Dell Inc. Inspiron 5437
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.9.0-16-generic 
root=UUID=7b80ab6d-8a48-4582-ace8-0b11e10026b6 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.9.0-16-generic N/A
 linux-backports-modules-4.9.0-16-generic  N/A
 linux-firmware1.162
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/07/2016
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A10
dmi.board.name: 03X56P
dmi.board.vendor: Dell Inc.
dmi.board.version: A10
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd06/07/2016:svnDellInc.:pnInspiron5437:pvrNotSpecified:rvnDellInc.:rn03X56P:rvrA10:cvnDellInc.:ct8:cvrNotSpecified:
dmi.product.name: Inspiron 5437
dmi.product.version: Not Specified
dmi.sys.vendor: Dell Inc.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug package-from-proposed zesty

-- 
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/1664062

Title:
  Can't load intel-rng module

Status in linux package in Ubuntu:
  New

Bug description:
  I have a laptop with Haswell processor which has a hardware random number 
generator. I confirmed that with the command 'grep rdrand /proc/cpuinfo'.
  The problem is when I try to load the 'intel-rng' kernel module to use the 
device with rngd daemon, it says 'no such device'. I'm not a great Linux 
expert, but the problem seems the PCI IDs for my computer's chipset isn't on 
module, so become impossible to detect the device. I tried the same with 
4.10rc7 kernel from PPA and the problem continues. I'm having a problem how to 
which PCI device contains RNG support and how create a new modalias to bypass 
the detection. If I could do that, I could report exactly what is the PCI IDs 
to correct the RNG detection.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.9.0-16-generic 4.9.0-16.17
  ProcVersionSignature: Ubuntu 4.9.0-16.17-generic 4.9.6
  Uname: Linux 4.9.0-16-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  marcos 6288 F pulseaudio
   /dev/snd/controlC1:  marcos 6288 F pulseaudio
   /dev/snd/controlC0:  marcos 6288 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Feb 12 19:06:49 2017
  HibernationDevice: RESUME=UUID=120c9111-82df-448d-a8d1-dc6b4822f7ac
  InstallationDate: Installed on 2016-08-03 (192 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Dell Inc. Inspiron 5437
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.9.0-16-generic 
root=UUID=7b80ab6d-8a48-4582-ace8-0b11e10026b6 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.9.0-16-generic N/A
   linux-backports-modules-4.9.0-16-generic  N/A
   linux-firmware1.162
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/07/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 03X56P
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A10
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:

[Kernel-packages] [Bug 1094744] Re: MS Sculpt Touch Mouse needs to be re-paired periodically

[Marcos Alano]

Mark,

I fixed this bug in may 2015:
https://bugzilla.gnome.org/show_bug.cgi?id=749443

Version 3.16 (used in Ubuntu 15.10 (Wily) didn't come with the patch and
no one backported.

Version 3.18 (used in Ubuntu 16.04 (Xenial) come with the patch.

Best regards and sorry for any trouble.

** Bug watch added: GNOME Bug Tracker #749443
   https://bugzilla.gnome.org/show_bug.cgi?id=749443

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1094744

Title:
  MS Sculpt Touch Mouse needs to be re-paired periodically

Status in GNOME Bluetooth:
  Fix Released
Status in bluez package in Ubuntu:
  Confirmed
Status in gnome-bluetooth package in Ubuntu:
  Fix Released
Status in bluez source package in Precise:
  Confirmed
Status in gnome-bluetooth source package in Precise:
  Fix Released
Status in bluez source package in Quantal:
  Won't Fix
Status in gnome-bluetooth source package in Quantal:
  Fix Released
Status in bluez source package in Raring:
  Won't Fix
Status in gnome-bluetooth source package in Raring:
  Won't Fix
Status in bluez package in Fedora:
  Unknown

Bug description:
  [Impact] The patch makes Microsoft Wedge/Sculpt Touch mice stay connected.
  [Test Case] Get a Microsoft Wedge/Sculpt Touch mouse, pair it, restart 
session, watch it automatically re-pair.
  [Regression Potential] Little. The patched piece of XML is only relevant to 
hardware having the same ID.

  When you don't use the mouse for a long enough time, the mouse
  disconnects and won't reconnect. I have to go into bluetooth settings,
  remove it, and re-pair it.

  1)
  ~ % lsb_release -rd
  Description:  Ubuntu 12.04.1 LTS
  Release:  12.04

  2)
  ~ % apt-cache policy bluez
  bluez:
    Installed: 4.98-2ubuntu7
    Candidate: 4.98-2ubuntu7
    Version table:
   *** 4.98-2ubuntu7 0
  500 http://us.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages
  100 /var/lib/dpkg/status

  3)
  I expected the mouse to reconnect automatically, or at least after I try to 
reconnect manually through the bluetooth settings.

  4)
  I have to re-pair the mouse in order to use it again. Turning the mouse off 
and on doesn't work either.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-bluetooth/+bug/1094744/+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

Re: [Kernel-packages] [Bug 1094744] Re: MS Sculpt Touch Mouse needs to be re-paired periodically

[Marcos Alano]

Hi David,

In the version 3.18 of gnome-bluetooth this OUI is already added. May
be someone could backport the patch?

2015-10-23 16:04 GMT-02:00 Marcos Alano :
> Thanks David.
>
> I will check this and create and submit a patch.
>
> Cheers.
>
> 2015-10-23 15:49 GMT-02:00 David Cesarino de Sousa 
> <1094...@bugs.launchpad.net>:
>> Hi Marcos,
>>
>> I did a clean install of 15.10 yesterday, so I also used that
>> opportunity to test this issue. In short, pairing using the user
>> interface still did not work, but adding the OUI to the XML file was
>> enough to persist the connection across reboots and suspends. No need to
>> use the command line foo I did in #59.
>>
>> To be fully precise, this is what I did:
>>
>> 1. Clean install Ubuntu 15.10.
>> 2. Pair using the bluetooth icon in the top right at the desktop.
>> 3. Try suspend or reboot. It did not work (connection even refused to set up 
>> without removing and adding the device again).
>> 4. Added the OUI to the XML file as this, under the Microsoft Mice section:
>>
>> 
>>
>> 5. Reboot.
>>
>> After this, the connection is now persisting across reboots and
>> suspends. It would be nice for other users if they didn't need to edit
>> the XML and the user interface did all that was needed automatically,
>> but I'm satisfied it works easily now.
>>
>> Cheers.
>>
>> --
>> You received this bug notification because you are subscribed to the bug
>> report.
>> https://bugs.launchpad.net/bugs/1094744
>>
>> Title:
>>   MS Sculpt Touch Mouse needs to be re-paired periodically
>>
>> Status in GNOME Bluetooth:
>>   Fix Released
>> Status in bluez package in Ubuntu:
>>   Confirmed
>> Status in gnome-bluetooth package in Ubuntu:
>>   Fix Released
>> Status in bluez source package in Precise:
>>   Confirmed
>> Status in gnome-bluetooth source package in Precise:
>>   Fix Released
>> Status in bluez source package in Quantal:
>>   Won't Fix
>> Status in gnome-bluetooth source package in Quantal:
>>   Fix Released
>> Status in bluez source package in Raring:
>>   Won't Fix
>> Status in gnome-bluetooth source package in Raring:
>>   Won't Fix
>> Status in bluez package in Fedora:
>>   Unknown
>>
>> Bug description:
>>   [Impact] The patch makes Microsoft Wedge/Sculpt Touch mice stay connected.
>>   [Test Case] Get a Microsoft Wedge/Sculpt Touch mouse, pair it, restart 
>> session, watch it automatically re-pair.
>>   [Regression Potential] Little. The patched piece of XML is only relevant 
>> to hardware having the same ID.
>>
>>   When you don't use the mouse for a long enough time, the mouse
>>   disconnects and won't reconnect. I have to go into bluetooth settings,
>>   remove it, and re-pair it.
>>
>>   1)
>>   ~ % lsb_release -rd
>>   Description:  Ubuntu 12.04.1 LTS
>>   Release:  12.04
>>
>>   2)
>>   ~ % apt-cache policy bluez
>>   bluez:
>> Installed: 4.98-2ubuntu7
>> Candidate: 4.98-2ubuntu7
>> Version table:
>>*** 4.98-2ubuntu7 0
>>   500 http://us.archive.ubuntu.com/ubuntu/ precise/main amd64 
>> Packages
>>   100 /var/lib/dpkg/status
>>
>>   3)
>>   I expected the mouse to reconnect automatically, or at least after I try 
>> to reconnect manually through the bluetooth settings.
>>
>>   4)
>>   I have to re-pair the mouse in order to use it again. Turning the mouse 
>> off and on doesn't work either.
>>
>> To manage notifications about this bug go to:
>> https://bugs.launchpad.net/gnome-bluetooth/+bug/1094744/+subscriptions
>
>
>
> --
> Marcos Alano
> --
> P: Por que este email é tão curto?
> R: http://five.sentenc.es
> --


-- 
Marcos Alano
--
P: Por que este email é tão curto?
R: http://five.sentenc.es
--

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1094744

Title:
  MS Sculpt Touch Mouse needs to be re-paired periodically

Status in GNOME Bluetooth:
  Fix Released
Status in bluez package in Ubuntu:
  Confirmed
Status in gnome-bluetooth package in Ubuntu:
  Fix Released
Status in bluez source package in Precise:
  Confirmed
Status in gnome-bluetooth source package in Precise:
  Fix Released
Sta

Re: [Kernel-packages] [Bug 1094744] Re: MS Sculpt Touch Mouse needs to be re-paired periodically

[Marcos Alano]

Thanks David.

I will check this and create and submit a patch.

Cheers.

2015-10-23 15:49 GMT-02:00 David Cesarino de Sousa <1094...@bugs.launchpad.net>:
> Hi Marcos,
>
> I did a clean install of 15.10 yesterday, so I also used that
> opportunity to test this issue. In short, pairing using the user
> interface still did not work, but adding the OUI to the XML file was
> enough to persist the connection across reboots and suspends. No need to
> use the command line foo I did in #59.
>
> To be fully precise, this is what I did:
>
> 1. Clean install Ubuntu 15.10.
> 2. Pair using the bluetooth icon in the top right at the desktop.
> 3. Try suspend or reboot. It did not work (connection even refused to set up 
> without removing and adding the device again).
> 4. Added the OUI to the XML file as this, under the Microsoft Mice section:
>
> 
>
> 5. Reboot.
>
> After this, the connection is now persisting across reboots and
> suspends. It would be nice for other users if they didn't need to edit
> the XML and the user interface did all that was needed automatically,
> but I'm satisfied it works easily now.
>
> Cheers.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1094744
>
> Title:
>   MS Sculpt Touch Mouse needs to be re-paired periodically
>
> Status in GNOME Bluetooth:
>   Fix Released
> Status in bluez package in Ubuntu:
>   Confirmed
> Status in gnome-bluetooth package in Ubuntu:
>   Fix Released
> Status in bluez source package in Precise:
>   Confirmed
> Status in gnome-bluetooth source package in Precise:
>   Fix Released
> Status in bluez source package in Quantal:
>   Won't Fix
> Status in gnome-bluetooth source package in Quantal:
>   Fix Released
> Status in bluez source package in Raring:
>   Won't Fix
> Status in gnome-bluetooth source package in Raring:
>   Won't Fix
> Status in bluez package in Fedora:
>   Unknown
>
> Bug description:
>   [Impact] The patch makes Microsoft Wedge/Sculpt Touch mice stay connected.
>   [Test Case] Get a Microsoft Wedge/Sculpt Touch mouse, pair it, restart 
> session, watch it automatically re-pair.
>   [Regression Potential] Little. The patched piece of XML is only relevant to 
> hardware having the same ID.
>
>   When you don't use the mouse for a long enough time, the mouse
>   disconnects and won't reconnect. I have to go into bluetooth settings,
>   remove it, and re-pair it.
>
>   1)
>   ~ % lsb_release -rd
>   Description:  Ubuntu 12.04.1 LTS
>   Release:  12.04
>
>   2)
>   ~ % apt-cache policy bluez
>   bluez:
> Installed: 4.98-2ubuntu7
> Candidate: 4.98-2ubuntu7
> Version table:
>*** 4.98-2ubuntu7 0
>   500 http://us.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages
>   100 /var/lib/dpkg/status
>
>   3)
>   I expected the mouse to reconnect automatically, or at least after I try to 
> reconnect manually through the bluetooth settings.
>
>   4)
>   I have to re-pair the mouse in order to use it again. Turning the mouse off 
> and on doesn't work either.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/gnome-bluetooth/+bug/1094744/+subscriptions


-- 
Marcos Alano
--
P: Por que este email é tão curto?
R: http://five.sentenc.es
--

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1094744

Title:
  MS Sculpt Touch Mouse needs to be re-paired periodically

Status in GNOME Bluetooth:
  Fix Released
Status in bluez package in Ubuntu:
  Confirmed
Status in gnome-bluetooth package in Ubuntu:
  Fix Released
Status in bluez source package in Precise:
  Confirmed
Status in gnome-bluetooth source package in Precise:
  Fix Released
Status in bluez source package in Quantal:
  Won't Fix
Status in gnome-bluetooth source package in Quantal:
  Fix Released
Status in bluez source package in Raring:
  Won't Fix
Status in gnome-bluetooth source package in Raring:
  Won't Fix
Status in bluez package in Fedora:
  Unknown

Bug description:
  [Impact] The patch makes Microsoft Wedge/Sculpt Touch mice stay connected.
  [Test Case] Get a Microsoft Wedge/Sculpt Touch mouse, pair it, restart 
session, watch it automatically re-pair.
  [Regression Potential] Little. The patched piece of XML is only relevant to 
hardware having the same ID.

  When you don't use the mouse for a long enough time, the mouse
  disconnects and won't reconnect. I have to go into bluetooth settings,
  remove it, and re-pair it.

[Kernel-packages] [Bug 1506271] [NEW] Wrong map for Logitech M560 mouse buttons

[Marcos Alano]

Public bug reported:

I bought a Logitech M560 mouse and used 'xev' to see button codes. This
mouse has a problem what I think need to be corrected in the kernel
module. The tilt wheel (wheel with left and right buttons) has the
buttons mapped for 6 (left) and 7 (right). I think the correct codes
should be 8 (left) and 9 (right). This is because the Ubuntu uses the
codes 8 and 9 to back and forward in web pages. I know that because I
have a Logitech M325 mouse and the tilt wheel works out-of-the-box. I'm
using Ubuntu 15.10 beta 2 with all updates.

** 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/1506271

Title:
  Wrong map for Logitech M560 mouse buttons

Status in linux package in Ubuntu:
  New

Bug description:
  I bought a Logitech M560 mouse and used 'xev' to see button codes.
  This mouse has a problem what I think need to be corrected in the
  kernel module. The tilt wheel (wheel with left and right buttons) has
  the buttons mapped for 6 (left) and 7 (right). I think the correct
  codes should be 8 (left) and 9 (right). This is because the Ubuntu
  uses the codes 8 and 9 to back and forward in web pages. I know that
  because I have a Logitech M325 mouse and the tilt wheel works out-of-
  the-box. I'm using Ubuntu 15.10 beta 2 with all updates.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1506271/+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 584934] Re: lis3lv02d does not detect free fall

[Marcos Alano]

This bug still present in new versions? May be we can close this bug.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/584934

Title:
  lis3lv02d does not detect free fall

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  I'm testing on a HP Elitebook 8440p. I used the tool from the kernel
  sources (2.6.34) - hpfall.c When imitating free fall the tool remained
  blocked waiting for /dev/freefall and no free fall was registered. So
  it looks like a kernel module issue. Here is the output from ls -lR
  /sys/devices/platform/lis3lv02d/:

  /sys/devices/platform/lis3lv02d/:
  total 0
  -rw-r--r-- 1 root root 4096 2010-05-24 15:23 calibrate
  drwxr-xr-x 3 root root0 2010-05-24 15:08 input
  -r--r--r-- 1 root root 4096 2010-05-24 15:23 modalias
  -r--r--r-- 1 root root 4096 2010-05-24 15:23 position
  drwxr-xr-x 2 root root0 2010-05-24 15:23 power
  -r--r--r-- 1 root root 4096 2010-05-24 15:23 rate
  lrwxrwxrwx 1 root root0 2010-05-24 15:23 subsystem -> 
../../../bus/platform
  -rw-r--r-- 1 root root 4096 2010-05-24 15:23 uevent

  /sys/devices/platform/lis3lv02d/input:
  total 0
  drwxr-xr-x 7 root root 0 2010-05-24 15:08 input6

  /sys/devices/platform/lis3lv02d/input/input6:
  total 0
  drwxr-xr-x 2 root root0 2010-05-24 15:29 capabilities
  lrwxrwxrwx 1 root root0 2010-05-24 15:29 device -> ../../../lis3lv02d
  drwxr-xr-x 3 root root0 2010-05-24 15:08 event6
  drwxr-xr-x 2 root root0 2010-05-24 15:29 id
  drwxr-xr-x 3 root root0 2010-05-24 15:08 js0
  -r--r--r-- 1 root root 4096 2010-05-24 15:29 modalias
  -r--r--r-- 1 root root 4096 2010-05-24 15:29 name
  -r--r--r-- 1 root root 4096 2010-05-24 15:29 phys
  drwxr-xr-x 2 root root0 2010-05-24 15:29 power
  lrwxrwxrwx 1 root root0 2010-05-24 15:29 subsystem -> 
../../../../../class/input
  -rw-r--r-- 1 root root 4096 2010-05-24 15:29 uevent
  -r--r--r-- 1 root root 4096 2010-05-24 15:29 uniq

  /sys/devices/platform/lis3lv02d/input/input6/capabilities:
  total 0
  -r--r--r-- 1 root root 4096 2010-05-24 15:29 abs
  -r--r--r-- 1 root root 4096 2010-05-24 15:29 ev
  -r--r--r-- 1 root root 4096 2010-05-24 15:29 ff
  -r--r--r-- 1 root root 4096 2010-05-24 15:29 key
  -r--r--r-- 1 root root 4096 2010-05-24 15:29 led
  -r--r--r-- 1 root root 4096 2010-05-24 15:29 msc
  -r--r--r-- 1 root root 4096 2010-05-24 15:29 rel
  -r--r--r-- 1 root root 4096 2010-05-24 15:29 snd
  -r--r--r-- 1 root root 4096 2010-05-24 15:29 sw

  /sys/devices/platform/lis3lv02d/input/input6/event6:
  total 0
  -r--r--r-- 1 root root 4096 2010-05-24 15:29 dev
  lrwxrwxrwx 1 root root0 2010-05-24 15:29 device -> ../../input6
  drwxr-xr-x 2 root root0 2010-05-24 15:29 power
  lrwxrwxrwx 1 root root0 2010-05-24 15:22 subsystem -> 
../../../../../../class/input
  -rw-r--r-- 1 root root 4096 2010-05-24 15:22 uevent

  /sys/devices/platform/lis3lv02d/input/input6/event6/power:
  total 0
  -rw-r--r-- 1 root root 4096 2010-05-24 15:29 wakeup

  /sys/devices/platform/lis3lv02d/input/input6/id:
  total 0
  -r--r--r-- 1 root root 4096 2010-05-24 15:29 bustype
  -r--r--r-- 1 root root 4096 2010-05-24 15:29 product
  -r--r--r-- 1 root root 4096 2010-05-24 15:29 vendor
  -r--r--r-- 1 root root 4096 2010-05-24 15:29 version

  /sys/devices/platform/lis3lv02d/input/input6/js0:
  total 0
  -r--r--r-- 1 root root 4096 2010-05-24 15:29 dev
  lrwxrwxrwx 1 root root0 2010-05-24 15:29 device -> ../../input6
  drwxr-xr-x 2 root root0 2010-05-24 15:29 power
  lrwxrwxrwx 1 root root0 2010-05-24 15:22 subsystem -> 
../../../../../../class/input
  -rw-r--r-- 1 root root 4096 2010-05-24 15:22 uevent

  /sys/devices/platform/lis3lv02d/input/input6/js0/power:
  total 0
  -rw-r--r-- 1 root root 4096 2010-05-24 15:29 wakeup

  /sys/devices/platform/lis3lv02d/input/input6/power:
  total 0
  -rw-r--r-- 1 root root 4096 2010-05-24 15:29 wakeup

  /sys/devices/platform/lis3lv02d/power:
  total 0
  -rw-r--r-- 1 root root 4096 2010-05-24 15:29 wakeup

  sleftest is not present.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: linux-image-2.6.32-22-generic 2.6.32-22.33
  Regression: No
  Reproducible: Yes
  ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2
  Uname: Linux 2.6.32-22-generic x86_64
  NonfreeKernelModules: nvidia
  AlsaVersion:
   Advanced Linux Sound Architecture Driver Version 1.0.22.1.
   Compiled on Apr 29 2010 for kernel 2.6.32-22-generic (SMP).
  AplayDevices:
    List of PLAYBACK Hardware Devices 
   card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
     Subdevices: 1/1
     Subdevice #0: subdevice #0
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
     Subdevices: 2/2
     Subdevice #0: subdevice #0
     Subdevice #1: subdevice #1
  AudioDevicesInUse:
 

Re: [Kernel-packages] [Bug 1094744] Re: MS Sculpt Touch Mouse needs to be re-paired periodically

[Marcos Alano]

Did you try add the OUI for your mouse in
/usr/share/gnome-bluetooth/pin-code-database.xml? I thinks there is
many differents OUIs for this model.

PS.: Post your OUI here so I can create and send a patch.

2015-09-05 18:19 GMT-03:00 Rael :
> On 14.04 LTS, bought one of this, and I'm facing this issue.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1094744
>
> Title:
>   MS Sculpt Touch Mouse needs to be re-paired periodically
>
> Status in GNOME Bluetooth:
>   Fix Released
> Status in bluez package in Ubuntu:
>   Confirmed
> Status in gnome-bluetooth package in Ubuntu:
>   Fix Released
> Status in bluez source package in Precise:
>   Confirmed
> Status in gnome-bluetooth source package in Precise:
>   Fix Released
> Status in bluez source package in Quantal:
>   Won't Fix
> Status in gnome-bluetooth source package in Quantal:
>   Fix Released
> Status in bluez source package in Raring:
>   Won't Fix
> Status in gnome-bluetooth source package in Raring:
>   Won't Fix
> Status in bluez package in Fedora:
>   Unknown
>
> Bug description:
>   [Impact] The patch makes Microsoft Wedge/Sculpt Touch mice stay connected.
>   [Test Case] Get a Microsoft Wedge/Sculpt Touch mouse, pair it, restart 
> session, watch it automatically re-pair.
>   [Regression Potential] Little. The patched piece of XML is only relevant to 
> hardware having the same ID.
>
>   When you don't use the mouse for a long enough time, the mouse
>   disconnects and won't reconnect. I have to go into bluetooth settings,
>   remove it, and re-pair it.
>
>   1)
>   ~ % lsb_release -rd
>   Description:  Ubuntu 12.04.1 LTS
>   Release:  12.04
>
>   2)
>   ~ % apt-cache policy bluez
>   bluez:
> Installed: 4.98-2ubuntu7
> Candidate: 4.98-2ubuntu7
> Version table:
>*** 4.98-2ubuntu7 0
>   500 http://us.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages
>   100 /var/lib/dpkg/status
>
>   3)
>   I expected the mouse to reconnect automatically, or at least after I try to 
> reconnect manually through the bluetooth settings.
>
>   4)
>   I have to re-pair the mouse in order to use it again. Turning the mouse off 
> and on doesn't work either.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/gnome-bluetooth/+bug/1094744/+subscriptions


-- 
Marcos Alano
--
P: Por que este email é tão curto?
R: http://five.sentenc.es
--

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1094744

Title:
  MS Sculpt Touch Mouse needs to be re-paired periodically

Status in GNOME Bluetooth:
  Fix Released
Status in bluez package in Ubuntu:
  Confirmed
Status in gnome-bluetooth package in Ubuntu:
  Fix Released
Status in bluez source package in Precise:
  Confirmed
Status in gnome-bluetooth source package in Precise:
  Fix Released
Status in bluez source package in Quantal:
  Won't Fix
Status in gnome-bluetooth source package in Quantal:
  Fix Released
Status in bluez source package in Raring:
  Won't Fix
Status in gnome-bluetooth source package in Raring:
  Won't Fix
Status in bluez package in Fedora:
  Unknown

Bug description:
  [Impact] The patch makes Microsoft Wedge/Sculpt Touch mice stay connected.
  [Test Case] Get a Microsoft Wedge/Sculpt Touch mouse, pair it, restart 
session, watch it automatically re-pair.
  [Regression Potential] Little. The patched piece of XML is only relevant to 
hardware having the same ID.

  When you don't use the mouse for a long enough time, the mouse
  disconnects and won't reconnect. I have to go into bluetooth settings,
  remove it, and re-pair it.

  1)
  ~ % lsb_release -rd
  Description:  Ubuntu 12.04.1 LTS
  Release:  12.04

  2)
  ~ % apt-cache policy bluez
  bluez:
    Installed: 4.98-2ubuntu7
    Candidate: 4.98-2ubuntu7
    Version table:
   *** 4.98-2ubuntu7 0
  500 http://us.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages
  100 /var/lib/dpkg/status

  3)
  I expected the mouse to reconnect automatically, or at least after I try to 
reconnect manually through the bluetooth settings.

  4)
  I have to re-pair the mouse in order to use it again. Turning the mouse off 
and on doesn't work either.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-bluetooth/+bug/1094744/+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

Re: [Kernel-packages] [Bug 1188647] Re: Please change intel_pstate default to disable

[Marcos Alano]

I think we need to know if intel_pstate is more stable in 4.x series,
because the new releases. If it keeps unstable may be disable by
default is the better choice.

2015-08-27 14:33 GMT-03:00 Colin Ian King <1188...@bugs.launchpad.net>:
> Enabling intel-pstate on the 3.13 kernel was deemed problematic for
> several reasons. However, I have backported all of the changes upto
> 4.2-rc8 to 3.13 and re-enabled the intel-pstate driver for testing. I
> have performed a boot smoke test with this kernel and I think it needs
> some deeper testing to see if it resolves your issues.
>
> The kernel packages can be found in:
>
> http://kernel.ubuntu.com/~cking/intel-pstate
>
> Please can you see if these help.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1188647
>
> Title:
>   Please change intel_pstate default to disable
>
> Status in linux package in Ubuntu:
>   Fix Released
>
> Bug description:
>   3.9 introduced a new default governor on SandyBridge CPUs called
>   INTEL_PSTATE which, when built in and enabled (the default), removes
>   all other governors (like our usual default, ondemand). 3.10 extended
>   this to Ivybridge generation CPUs.
>
>   In theory, this isn't an awful thing, as the new Intel pstate governor
>   should be higher performance and give better power savings.  In
>   theory.
>
>   In practice, it drives my CPUs to max frequency nearly constantly,
>   spins my fans like mad and, somehow, does all of this while also
>   eating enough CPU time in kernel threads to make my machine choppy,
>   unresponsive, and unable to do simple things like play videos when I
>   get off work.
>
>   Therefore, I propose that we, for now, toggle intel_pstate to disable
>   by default (I am using intel_pstate=disable on my command line right
>   now, with great success), so it's still built in, and people can play
>   with it, but it's off by default.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 13.10
>   Package: linux-image-3.9.0-4-generic 3.9.0-4.9
>   ProcVersionSignature: Ubuntu 3.9.0-4.9-generic 3.9.4
>   Uname: Linux 3.9.0-4-generic x86_64
>   ApportVersion: 2.10.2-0ubuntu1
>   Architecture: amd64
>   AudioDevicesInUse:
>USERPID ACCESS COMMAND
>/dev/snd/controlC0:  adconrad   2574 F pulseaudio
>   CurrentDmesg:
>[   30.633035] init: plymouth-stop pre-start process (2079) terminated 
> with status 1
>[   36.086916] br0: port 1(eth0) entered forwarding state
>   Date: Fri Jun  7 08:48:56 2013
>   HibernationDevice: RESUME=UUID=73040efa-baec-458a-8307-3bca07b26c3c
>   InstallationDate: Installed on 2012-12-09 (179 days ago)
>   InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20121209)
>   MachineType: LENOVO 4173LPB
>   MarkForUpload: True
>   ProcFB: 0 inteldrmfb
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.9.0-4-generic 
> root=UUID=aad5-ef31-4428-973f-71740fc7cb6a ro intel_pstate=disable quiet 
> splash vt.handoff=7
>   RelatedPackageVersions:
>linux-restricted-modules-3.9.0-4-generic N/A
>linux-backports-modules-3.9.0-4-generic  N/A
>linux-firmware   1.109
>   SourcePackage: linux
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 09/13/2012
>   dmi.bios.vendor: LENOVO
>   dmi.bios.version: 8CET55WW (1.35 )
>   dmi.board.asset.tag: Not Available
>   dmi.board.name: 4173LPB
>   dmi.board.vendor: LENOVO
>   dmi.board.version: Not Available
>   dmi.chassis.asset.tag: No Asset Information
>   dmi.chassis.type: 10
>   dmi.chassis.vendor: LENOVO
>   dmi.chassis.version: Not Available
>   dmi.modalias: 
> dmi:bvnLENOVO:bvr8CET55WW(1.35):bd09/13/2012:svnLENOVO:pn4173LPB:pvrThinkPadT420s:rvnLENOVO:rn4173LPB:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
>   dmi.product.name: 4173LPB
>   dmi.product.version: ThinkPad T420s
>   dmi.sys.vendor: LENOVO
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1188647/+subscriptions


-- 
Marcos Alano
--
P: Por que este email é tão curto?
R: http://five.sentenc.es
--

-- 
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/1188647

Title:
  Please change intel_pstate default to disable

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  3.9 introduced a new default governor on SandyBridge CPUs called
  INTEL_PSTATE which, when built in and enabled (the default), removes
  all other governors (like our us

Re: [Kernel-packages] [Bug 1094744] Re: MS Sculpt Touch Mouse needs to be re-paired periodically

[Marcos Alano]

Ok. Please do more tests in a clean installation and let us know about
the results.

Cheers.

2015-05-17 19:47 GMT-03:00 Marcos Alano :
> Sorry for this problem. The address "30:59:B7:" seems correct. Can you
> check the batteries? That is a long shot, but may be can be the
> problem.
>
> 2015-05-17 19:12 GMT-03:00 David Cesarino de Sousa 
> <1094...@bugs.launchpad.net>:
>> Marcos, thanks for your help.
>>
>> That output was to show that the mouse unpairs after a suspend/reboot.
>> If I follow the two steps I said before, I get the correct, expected
>> status (paired), and I can move my mouse. See relevant output now that
>> it is connected:
>>
>> [ /org/bluez/663/hci0 ]
>> Discovering = 0
>> UUIDs = 0x1000 0x1001 0x112d 0x1112 0x111f 0x111e 0x110c 0x110e 0x110a 
>> 0x110b
>> Pairable = 1
>> PairableTimeout = 0
>> DiscoverableTimeout = 180
>> Name = zurg-0
>> Class = 0
>> Address = C4:17:FE:EF:D8:A4
>> Powered = 1
>> Discoverable = 0
>> Devices = dev_30_59_B7_73_B6_C6
>> [ /org/bluez/663/hci0/dev_30_59_B7_73_B6_C6 ]
>> Paired = 1
>> Vendor = 0x045e
>> Services = dbus.Array([], signature=dbus.Signature('o'), 
>> variant_level=1)
>> Trusted = 1
>> Class = 0x002580
>> Address = 30:59:B7:73:B6:C6
>> Adapter = /org/bluez/663/hci0
>> Version = 0x0129
>> UUIDs = 0x1000 0x1124 0x1200
>> Blocked = 0
>> Icon = input-mouse
>> Name = Microsoft Sculpt Comfort Mouse
>> Connected = 1
>> Alias = Microsoft Sculpt Comfort Mouse
>> Product = 0x07a2
>>
>> The file currently reads this in the Microsoft mice section of the XML
>> (I've tried with name as well):
>>
>> 
>> 
>> 
>> 
>>
>> It still unpairs after a reboot or suspend. Changing to the adapter
>> address (oui="C4:17:FE:") does not make any difference. As you can see,
>> I can reconnect/repair, but I'd like it to be automatic.
>>
>> Sorry if I wasn't clear enough. Thank you.
>>
>> --
>> You received this bug notification because you are subscribed to the bug
>> report.
>> https://bugs.launchpad.net/bugs/1094744
>>
>> Title:
>>   MS Sculpt Touch Mouse needs to be re-paired periodically
>>
>> Status in GNOME Bluetooth:
>>   Fix Released
>> Status in bluez package in Ubuntu:
>>   Confirmed
>> Status in gnome-bluetooth package in Ubuntu:
>>   Fix Released
>> Status in bluez source package in Precise:
>>   Confirmed
>> Status in gnome-bluetooth source package in Precise:
>>   Fix Released
>> Status in bluez source package in Quantal:
>>   Won't Fix
>> Status in gnome-bluetooth source package in Quantal:
>>   Fix Released
>> Status in bluez source package in Raring:
>>   Won't Fix
>> Status in gnome-bluetooth source package in Raring:
>>   Won't Fix
>> Status in bluez package in Fedora:
>>   Unknown
>>
>> Bug description:
>>   [Impact] The patch makes Microsoft Wedge/Sculpt Touch mice stay connected.
>>   [Test Case] Get a Microsoft Wedge/Sculpt Touch mouse, pair it, restart 
>> session, watch it automatically re-pair.
>>   [Regression Potential] Little. The patched piece of XML is only relevant 
>> to hardware having the same ID.
>>
>>   When you don't use the mouse for a long enough time, the mouse
>>   disconnects and won't reconnect. I have to go into bluetooth settings,
>>   remove it, and re-pair it.
>>
>>   1)
>>   ~ % lsb_release -rd
>>   Description:  Ubuntu 12.04.1 LTS
>>   Release:  12.04
>>
>>   2)
>>   ~ % apt-cache policy bluez
>>   bluez:
>> Installed: 4.98-2ubuntu7
>> Candidate: 4.98-2ubuntu7
>> Version table:
>>*** 4.98-2ubuntu7 0
>>   500 http://us.archive.ubuntu.com/ubuntu/ precise/main amd64 
>> Packages
>>   100 /var/lib/dpkg/status
>>
>>   3)
>>   I expected the mouse to reconnect automatically, or at least after I try 
>> to reconnect manually through the bluetooth settings.
>>
>>   4)
>>   I have to re-pair the mouse in order to use it again. Turning the mouse 
>> off and on doesn't work either.
>>
>> To manage notifications about this bug go to:
>> https://bugs.launchpad.net/gnome-bluetooth/+bug/1094744/+subscriptions
>
>

Re: [Kernel-packages] [Bug 1094744] Re: MS Sculpt Touch Mouse needs to be re-paired periodically

[Marcos Alano]

Sorry for this problem. The address "30:59:B7:" seems correct. Can you
check the batteries? That is a long shot, but may be can be the
problem.

2015-05-17 19:12 GMT-03:00 David Cesarino de Sousa <1094...@bugs.launchpad.net>:
> Marcos, thanks for your help.
>
> That output was to show that the mouse unpairs after a suspend/reboot.
> If I follow the two steps I said before, I get the correct, expected
> status (paired), and I can move my mouse. See relevant output now that
> it is connected:
>
> [ /org/bluez/663/hci0 ]
> Discovering = 0
> UUIDs = 0x1000 0x1001 0x112d 0x1112 0x111f 0x111e 0x110c 0x110e 0x110a 
> 0x110b
> Pairable = 1
> PairableTimeout = 0
> DiscoverableTimeout = 180
> Name = zurg-0
> Class = 0
> Address = C4:17:FE:EF:D8:A4
> Powered = 1
> Discoverable = 0
> Devices = dev_30_59_B7_73_B6_C6
> [ /org/bluez/663/hci0/dev_30_59_B7_73_B6_C6 ]
> Paired = 1
> Vendor = 0x045e
> Services = dbus.Array([], signature=dbus.Signature('o'), 
> variant_level=1)
> Trusted = 1
> Class = 0x002580
> Address = 30:59:B7:73:B6:C6
> Adapter = /org/bluez/663/hci0
> Version = 0x0129
> UUIDs = 0x1000 0x1124 0x1200
> Blocked = 0
> Icon = input-mouse
> Name = Microsoft Sculpt Comfort Mouse
> Connected = 1
> Alias = Microsoft Sculpt Comfort Mouse
> Product = 0x07a2
>
> The file currently reads this in the Microsoft mice section of the XML
> (I've tried with name as well):
>
> 
> 
> 
> 
>
> It still unpairs after a reboot or suspend. Changing to the adapter
> address (oui="C4:17:FE:") does not make any difference. As you can see,
> I can reconnect/repair, but I'd like it to be automatic.
>
> Sorry if I wasn't clear enough. Thank you.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1094744
>
> Title:
>   MS Sculpt Touch Mouse needs to be re-paired periodically
>
> Status in GNOME Bluetooth:
>   Fix Released
> Status in bluez package in Ubuntu:
>   Confirmed
> Status in gnome-bluetooth package in Ubuntu:
>   Fix Released
> Status in bluez source package in Precise:
>   Confirmed
> Status in gnome-bluetooth source package in Precise:
>   Fix Released
> Status in bluez source package in Quantal:
>   Won't Fix
> Status in gnome-bluetooth source package in Quantal:
>   Fix Released
> Status in bluez source package in Raring:
>   Won't Fix
> Status in gnome-bluetooth source package in Raring:
>   Won't Fix
> Status in bluez package in Fedora:
>   Unknown
>
> Bug description:
>   [Impact] The patch makes Microsoft Wedge/Sculpt Touch mice stay connected.
>   [Test Case] Get a Microsoft Wedge/Sculpt Touch mouse, pair it, restart 
> session, watch it automatically re-pair.
>   [Regression Potential] Little. The patched piece of XML is only relevant to 
> hardware having the same ID.
>
>   When you don't use the mouse for a long enough time, the mouse
>   disconnects and won't reconnect. I have to go into bluetooth settings,
>   remove it, and re-pair it.
>
>   1)
>   ~ % lsb_release -rd
>   Description:  Ubuntu 12.04.1 LTS
>   Release:  12.04
>
>   2)
>   ~ % apt-cache policy bluez
>   bluez:
> Installed: 4.98-2ubuntu7
> Candidate: 4.98-2ubuntu7
> Version table:
>*** 4.98-2ubuntu7 0
>   500 http://us.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages
>   100 /var/lib/dpkg/status
>
>   3)
>   I expected the mouse to reconnect automatically, or at least after I try to 
> reconnect manually through the bluetooth settings.
>
>   4)
>   I have to re-pair the mouse in order to use it again. Turning the mouse off 
> and on doesn't work either.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/gnome-bluetooth/+bug/1094744/+subscriptions


-- 
Marcos Alano
--
P: Por que este email é tão curto?
R: http://five.sentenc.es
--

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1094744

Title:
  MS Sculpt Touch Mouse needs to be re-paired periodically

Status in GNOME Bluetooth:
  Fix Released
Status in bluez package in Ubuntu:
  Confirmed
Status in gnome-bluetooth package in Ubuntu:
  Fix Released
Status in bluez source package in Precise:
  Confirmed
Status in gnome-bluetooth source package in Pr

Re: [Kernel-packages] [Bug 1094744] Re: MS Sculpt Touch Mouse needs to be re-paired periodically

[Marcos Alano]

David,

Please connect and pair the mouse. After that execute
"bluez-list-devices". If you check the lines:
Connected = 0
Paired = 0
You'll see the mouse is not even connected. The address is the same as
computer Bluetooth adapter so probably because that the line you put
in the file is wrong.

Cheers.



2015-05-17 15:32 GMT-03:00 David Cesarino de Sousa <1094...@bugs.launchpad.net>:
> I have the Sculpt Comfort Bluetooth mouse as well (model H3S-3), and
> the connection is not surviving suspends or reboots on Vivid (15.04). To
> fix, I need to:
>
> 1. Put the mouse into pairing mode (holding the bottom button).
> 2. Go to the Bluetooth setting for the mouse and activate the "Connection" 
> switch.
>
> This _always_ works. Simply trying to connect by activating the
> "Connection" switch _never_ works.
>
> I've tried adding the following line to "/usr/share/gnome-bluetooth/pin-
> code-database.xml":
>
> 
>
> Because this information appears in "bluez-list-devices":
>
> [ /org/bluez/661/hci0 ]
> Devices = dev_30_59_B7_73_B6_C6
> UUIDs = 0x1000 0x1001 0x112d 0x1112 0x111f 0x111e 0x110c 0x110e 0x110a 
> 0x110b
> Address = C4:17:FE:EF:D8:A4
> Name = ubuntu-0
> Powered = 1
> Class = 0
> Pairable = 1
> Discoverable = 0
> DiscoverableTimeout = 180
> PairableTimeout = 0
> Discovering = 0
> [ /org/bluez/661/hci0/dev_30_59_B7_73_B6_C6 ]
> UUIDs = 0x1000 0x1124 0x1200
> Address = 30:59:B7:73:B6:C6
> Name = Microsoft Sculpt Comfort Mouse
> Icon = input-mouse
> Connected = 0
> Paired = 0
> Alias = Microsoft Sculpt Comfort Mouse
> Adapter = /org/bluez/661/hci0
> Trusted = 1
> Version = 0x0129
> Blocked = 0
> Vendor = 0x045e
> Product = 0x07a2
> Class = 0x000580
> Services = dbus.Array([], signature=dbus.Signature('o'), 
> variant_level=1)
>
> But the connection is still lost after a reboot or suspend, and I still
> need to put it into pairing mode to connect.
>
> Any help is appreciated.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1094744
>
> Title:
>   MS Sculpt Touch Mouse needs to be re-paired periodically
>
> Status in GNOME Bluetooth:
>   Fix Released
> Status in bluez package in Ubuntu:
>   Confirmed
> Status in gnome-bluetooth package in Ubuntu:
>   Fix Released
> Status in bluez source package in Precise:
>   Confirmed
> Status in gnome-bluetooth source package in Precise:
>   Fix Released
> Status in bluez source package in Quantal:
>   Won't Fix
> Status in gnome-bluetooth source package in Quantal:
>   Fix Released
> Status in bluez source package in Raring:
>   Won't Fix
> Status in gnome-bluetooth source package in Raring:
>   Won't Fix
> Status in bluez package in Fedora:
>   Unknown
>
> Bug description:
>   [Impact] The patch makes Microsoft Wedge/Sculpt Touch mice stay connected.
>   [Test Case] Get a Microsoft Wedge/Sculpt Touch mouse, pair it, restart 
> session, watch it automatically re-pair.
>   [Regression Potential] Little. The patched piece of XML is only relevant to 
> hardware having the same ID.
>
>   When you don't use the mouse for a long enough time, the mouse
>   disconnects and won't reconnect. I have to go into bluetooth settings,
>   remove it, and re-pair it.
>
>   1)
>   ~ % lsb_release -rd
>   Description:  Ubuntu 12.04.1 LTS
>   Release:  12.04
>
>   2)
>   ~ % apt-cache policy bluez
>   bluez:
> Installed: 4.98-2ubuntu7
> Candidate: 4.98-2ubuntu7
> Version table:
>*** 4.98-2ubuntu7 0
>   500 http://us.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages
>       100 /var/lib/dpkg/status
>
>   3)
>   I expected the mouse to reconnect automatically, or at least after I try to 
> reconnect manually through the bluetooth settings.
>
>   4)
>   I have to re-pair the mouse in order to use it again. Turning the mouse off 
> and on doesn't work either.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/gnome-bluetooth/+bug/1094744/+subscriptions


-- 
Marcos Alano
--
P: Por que este email é tão curto?
R: http://five.sentenc.es
--

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1094744

Title:
  MS Sculpt Touch Mouse needs to be re-pa

Re: [Kernel-packages] [Bug 1094744] Re: MS Sculpt Touch Mouse needs to be re-paired periodically

[Marcos Alano]

I submitted a patch for gnome-bluetooth to add the address of your
device in the PIN DB.

2015-05-15 13:19 GMT-03:00 Mark Thornton <1094...@bugs.launchpad.net>:
> Working (for now). Pairing now survived a reboot.
>
> Thanks,
> Mark
>
> On Friday, 15 May 2015, Marcos Alano <1094...@bugs.launchpad.net> wrote:
>
>> Thanks Mark, help me so much. :)
>>
>> The problem is in the Bluetooth device address: The prefix (which
>> indicates the manufacturer) is different for your mouse. So the
>> workaround is add this line in the file
>> /usr/share/gnome-bluetooth/pin-code-database.xml (close to the Wedge
>> mouse entrance):
>> 
>> Restart the system and try again to check if the problem persists. If
>> work well I will submit a patch for gnome-bluetooth.
>>
>> Thanks for report this bug. :)
>>
>>
>> 2015-05-15 12:21 GMT-03:00 Mark Thornton <1094...@bugs.launchpad.net
>> >:
>> > Does this help? Note it is the same mouse that originally gave problems
>> > when this bug first appeared. It is also appearing twice in the list of
>> > devices (there is only one).
>> >
>> > Thanks,
>> > Mark
>> >
>> > mthornton@mark-PBL21:~$ bluez-list-devices
>> > [ /org/bluez/863/hci0 ]
>> > Address = 00:02:72:C6:AE:86
>> > Powered = 1
>> > UUIDs = 0x1000 0x1000 0x1001 0x1001 0x1112 0x111f 0x111e 0x110c
>> 0x110e
>> > 0x110a 0x110b
>> > Class = 0
>> > DiscoverableTimeout = 180
>> > Discovering = 0
>> > Name = mark-PBL21-1
>> > PairableTimeout = 0
>> > Discoverable = 0
>> > Devices = dev_28_18_78_5D_C1_65
>> > Pairable = 1
>> > [ /org/bluez/863/hci0/dev_28_18_78_5D_C1_65 ]
>> > Address = 28:18:78:5D:C1:65
>> > Paired = 1
>> > Version = 0x0129
>> > UUIDs = 0x1000 0x1124 0x1200
>> > Product = 0x07a2
>> > Icon = input-mouse
>> > Trusted = 1
>> > Connected = 1
>> > Vendor = 0x045e
>> > Adapter = /org/bluez/863/hci0
>> > Alias = Microsoft Sculpt Comfort Mouse
>> > Services = dbus.Array([], signature=dbus.Signature('o'),
>> > variant_level=1)
>> > Class = 0x002580
>> > Name = Microsoft Sculpt Comfort Mouse
>> > Blocked = 0
>> >
>> > [ /org/bluez/863/hci1 ]
>> > Address = DC:85:DE:05:4F:6E
>> > Powered = 1
>> > UUIDs = 0x1000 0x1001 0x1112 0x111f 0x111e 0x110c 0x110e 0x110a
>> 0x110b
>> > Class = 0
>> > DiscoverableTimeout = 180
>> > Discovering = 0
>> > Name = mark-PBL21-0
>> > PairableTimeout = 0
>> > Discoverable = 0
>> > Devices = dev_28_18_78_5D_C1_65
>> > Pairable = 1
>> > [ /org/bluez/863/hci1/dev_28_18_78_5D_C1_65 ]
>> > Address = 28:18:78:5D:C1:65
>> > Paired = 0
>> > Version = 0x0129
>> > UUIDs = 0x1000 0x1124 0x1200
>> > Product = 0x07a2
>> > Icon = input-mouse
>> > Trusted = 1
>> > Connected = 0
>> > Vendor = 0x045e
>> > Adapter = /org/bluez/863/hci1
>> > Alias = Microsoft Sculpt Comfort Mouse
>> > Services = dbus.Array([], signature=dbus.Signature('o'),
>> > variant_level=1)
>> > Class = 0x000580
>> > Name = Microsoft Sculpt Comfort Mouse
>> > Blocked = 0
>> >
>> >
>> > On Friday, 15 May 2015, Marcos Alano <1094...@bugs.launchpad.net
>> > wrote:
>> >
>> >> Mark, can you find the address of your Sculpt mouse using the command
>> >> bluez-list-devices? If the address prefix is different I need submit a
>> >> new patch (but I can post a workaround as well).
>> >>
>> >> --
>> >> You received this bug notification because you are subscribed to the bug
>> >> report.
>> >> https://bugs.launchpad.net/bugs/1094744
>> >>
>> >> Title:
>> >>   MS Sculpt Touch Mouse needs to be re-paired periodically
>> >>
>> >> Status in GNOME Bluetooth:
>> >>   Fix Released
>> >> Status in bluez package in Ubuntu:
>> >>   Confirmed
>> >> Status in gnome-bluetooth package in Ubuntu:
>> >>   Fix Released
>&

Re: [Kernel-packages] [Bug 1094744] Re: MS Sculpt Touch Mouse needs to be re-paired periodically

[Marcos Alano]

Thanks Mark, help me so much. :)

The problem is in the Bluetooth device address: The prefix (which
indicates the manufacturer) is different for your mouse. So the
workaround is add this line in the file
/usr/share/gnome-bluetooth/pin-code-database.xml (close to the Wedge
mouse entrance):

Restart the system and try again to check if the problem persists. If
work well I will submit a patch for gnome-bluetooth.

Thanks for report this bug. :)


2015-05-15 12:21 GMT-03:00 Mark Thornton <1094...@bugs.launchpad.net>:
> Does this help? Note it is the same mouse that originally gave problems
> when this bug first appeared. It is also appearing twice in the list of
> devices (there is only one).
>
> Thanks,
> Mark
>
> mthornton@mark-PBL21:~$ bluez-list-devices
> [ /org/bluez/863/hci0 ]
> Address = 00:02:72:C6:AE:86
> Powered = 1
> UUIDs = 0x1000 0x1000 0x1001 0x1001 0x1112 0x111f 0x111e 0x110c 0x110e
> 0x110a 0x110b
> Class = 0
> DiscoverableTimeout = 180
> Discovering = 0
> Name = mark-PBL21-1
> PairableTimeout = 0
> Discoverable = 0
> Devices = dev_28_18_78_5D_C1_65
> Pairable = 1
> [ /org/bluez/863/hci0/dev_28_18_78_5D_C1_65 ]
> Address = 28:18:78:5D:C1:65
> Paired = 1
> Version = 0x0129
> UUIDs = 0x1000 0x1124 0x1200
> Product = 0x07a2
> Icon = input-mouse
> Trusted = 1
> Connected = 1
> Vendor = 0x045e
> Adapter = /org/bluez/863/hci0
> Alias = Microsoft Sculpt Comfort Mouse
> Services = dbus.Array([], signature=dbus.Signature('o'),
> variant_level=1)
> Class = 0x002580
> Name = Microsoft Sculpt Comfort Mouse
> Blocked = 0
>
> [ /org/bluez/863/hci1 ]
> Address = DC:85:DE:05:4F:6E
> Powered = 1
> UUIDs = 0x1000 0x1001 0x1112 0x111f 0x111e 0x110c 0x110e 0x110a 0x110b
> Class = 0
> DiscoverableTimeout = 180
> Discovering = 0
> Name = mark-PBL21-0
> PairableTimeout = 0
> Discoverable = 0
> Devices = dev_28_18_78_5D_C1_65
> Pairable = 1
> [ /org/bluez/863/hci1/dev_28_18_78_5D_C1_65 ]
> Address = 28:18:78:5D:C1:65
> Paired = 0
> Version = 0x0129
> UUIDs = 0x1000 0x1124 0x1200
> Product = 0x07a2
> Icon = input-mouse
> Trusted = 1
> Connected = 0
> Vendor = 0x045e
> Adapter = /org/bluez/863/hci1
> Alias = Microsoft Sculpt Comfort Mouse
> Services = dbus.Array([], signature=dbus.Signature('o'),
> variant_level=1)
> Class = 0x000580
> Name = Microsoft Sculpt Comfort Mouse
> Blocked = 0
>
>
> On Friday, 15 May 2015, Marcos Alano <1094...@bugs.launchpad.net> wrote:
>
>> Mark, can you find the address of your Sculpt mouse using the command
>> bluez-list-devices? If the address prefix is different I need submit a
>> new patch (but I can post a workaround as well).
>>
>> --
>> You received this bug notification because you are subscribed to the bug
>> report.
>> https://bugs.launchpad.net/bugs/1094744
>>
>> Title:
>>   MS Sculpt Touch Mouse needs to be re-paired periodically
>>
>> Status in GNOME Bluetooth:
>>   Fix Released
>> Status in bluez package in Ubuntu:
>>   Confirmed
>> Status in gnome-bluetooth package in Ubuntu:
>>   Fix Released
>> Status in bluez source package in Precise:
>>   Confirmed
>> Status in gnome-bluetooth source package in Precise:
>>   Fix Released
>> Status in bluez source package in Quantal:
>>   Won't Fix
>> Status in gnome-bluetooth source package in Quantal:
>>   Fix Released
>> Status in bluez source package in Raring:
>>   Won't Fix
>> Status in gnome-bluetooth source package in Raring:
>>   Won't Fix
>> Status in bluez package in Fedora:
>>   Unknown
>>
>> Bug description:
>>   [Impact] The patch makes Microsoft Wedge/Sculpt Touch mice stay
>> connected.
>>   [Test Case] Get a Microsoft Wedge/Sculpt Touch mouse, pair it, restart
>> session, watch it automatically re-pair.
>>   [Regression Potential] Little. The patched piece of XML is only relevant
>> to hardware having the same ID.
>>
>>   When you don't use the mouse for a long enough time, the mouse
>>   disconnects and won't reconnect. I have to go into bluetooth settings,
>>   remove it, and re-pair it.
>>
>>   1)
>>   ~ % lsb_release -rd
>>   Description:  Ubuntu 12.04.1 LTS
>>   Release:  12.04
>>
>>   2)
>>   ~ % apt-

[Kernel-packages] [Bug 1094744] Re: MS Sculpt Touch Mouse needs to be re-paired periodically

[Marcos Alano]

Mark, can you find the address of your Sculpt mouse using the command
bluez-list-devices? If the address prefix is different I need submit a
new patch (but I can post a workaround as well).

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1094744

Title:
  MS Sculpt Touch Mouse needs to be re-paired periodically

Status in GNOME Bluetooth:
  Fix Released
Status in bluez package in Ubuntu:
  Confirmed
Status in gnome-bluetooth package in Ubuntu:
  Fix Released
Status in bluez source package in Precise:
  Confirmed
Status in gnome-bluetooth source package in Precise:
  Fix Released
Status in bluez source package in Quantal:
  Won't Fix
Status in gnome-bluetooth source package in Quantal:
  Fix Released
Status in bluez source package in Raring:
  Won't Fix
Status in gnome-bluetooth source package in Raring:
  Won't Fix
Status in bluez package in Fedora:
  Unknown

Bug description:
  [Impact] The patch makes Microsoft Wedge/Sculpt Touch mice stay connected.
  [Test Case] Get a Microsoft Wedge/Sculpt Touch mouse, pair it, restart 
session, watch it automatically re-pair.
  [Regression Potential] Little. The patched piece of XML is only relevant to 
hardware having the same ID.

  When you don't use the mouse for a long enough time, the mouse
  disconnects and won't reconnect. I have to go into bluetooth settings,
  remove it, and re-pair it.

  1)
  ~ % lsb_release -rd
  Description:  Ubuntu 12.04.1 LTS
  Release:  12.04

  2)
  ~ % apt-cache policy bluez
  bluez:
    Installed: 4.98-2ubuntu7
    Candidate: 4.98-2ubuntu7
    Version table:
   *** 4.98-2ubuntu7 0
  500 http://us.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages
  100 /var/lib/dpkg/status

  3)
  I expected the mouse to reconnect automatically, or at least after I try to 
reconnect manually through the bluetooth settings.

  4)
  I have to re-pair the mouse in order to use it again. Turning the mouse off 
and on doesn't work either.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-bluetooth/+bug/1094744/+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