[Kernel-packages] [Bug 1944018] Re: ath11k_pci sometimes crashes on suspend/resume on Dell XPS 13 9310

2022-01-23 Thread Matt Austin
It appears installing linux-oem-20.04c resolves this issue for me (it
installs kernel 5.13).

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

Title:
  ath11k_pci sometimes crashes on suspend/resume on Dell XPS 13 9310

Status in linux-oem-5.10 package in Ubuntu:
  Confirmed

Bug description:
  Sometimes when my Dell XPS 13 9310 resumes from suspend, the display
  fails to show anything for a short while. When the display does show,
  the wireless network is no longer working.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-modules-5.10.0-1045-oem 5.10.0-1045.47
  ProcVersionSignature: Ubuntu 5.10.0-1045.47-oem 5.10.46
  Uname: Linux 5.10.0-1045-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Sat Sep 18 12:04:49 2021
  Dependencies:
   
  InstallationDate: Installed on 2021-09-13 (4 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  SourcePackage: linux-oem-5.10
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.10/+bug/1944018/+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 1951034] [NEW] XPS 9310: wifi adapter not working when using linux-image-5.13.0-1019-oem (was working in linux-image-5.13.0-1017-oem)

2021-11-15 Thread Matt Austin
Public bug reported:

I have been using linux-oem-20.04c with my XPS 9310 with no problems,
but the recent update to 5.13.0-1019-oem caused my wifi to become
inoperative (ath11k_pci, 72:00.0 Network controller: Qualcomm Device
1101 (rev 01)). Choosing 5.13.0-1017-oem from the grub menu is my
current work around as the wifi is still working there.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.13.0-1019-oem 5.13.0-1019.23
ProcVersionSignature: Ubuntu 5.13.0-1017.21-oem 5.13.14
Uname: Linux 5.13.0-1017-oem x86_64
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: GNOME
Date: Tue Nov 16 08:10:20 2021
InstallationDate: Installed on 2021-09-13 (63 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
SourcePackage: linux-signed-oem-5.13
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: linux-signed-oem-5.13 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal wayland-session

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

Title:
  XPS 9310: wifi adapter not working when using linux-
  image-5.13.0-1019-oem (was working in linux-image-5.13.0-1017-oem)

Status in linux-signed-oem-5.13 package in Ubuntu:
  New

Bug description:
  I have been using linux-oem-20.04c with my XPS 9310 with no problems,
  but the recent update to 5.13.0-1019-oem caused my wifi to become
  inoperative (ath11k_pci, 72:00.0 Network controller: Qualcomm Device
  1101 (rev 01)). Choosing 5.13.0-1017-oem from the grub menu is my
  current work around as the wifi is still working there.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.13.0-1019-oem 5.13.0-1019.23
  ProcVersionSignature: Ubuntu 5.13.0-1017.21-oem 5.13.14
  Uname: Linux 5.13.0-1017-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Tue Nov 16 08:10:20 2021
  InstallationDate: Installed on 2021-09-13 (63 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  SourcePackage: linux-signed-oem-5.13
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-oem-5.13/+bug/1951034/+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 1944018] Re: ath11k_pci sometimes crashes on suspend/resume on Dell XPS 13 9310

2021-09-18 Thread Matt Austin
I should also note that after this happens, attempting to "rmmod
ath11k_pci" results in a wait of several minutes before then getting a
segmentation fault error.

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

Title:
  ath11k_pci sometimes crashes on suspend/resume on Dell XPS 13 9310

Status in linux-oem-5.10 package in Ubuntu:
  New

Bug description:
  Sometimes when my Dell XPS 13 9310 resumes from suspend, the display
  fails to show anything for a short while. When the display does show,
  the wireless network is no longer working.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-modules-5.10.0-1045-oem 5.10.0-1045.47
  ProcVersionSignature: Ubuntu 5.10.0-1045.47-oem 5.10.46
  Uname: Linux 5.10.0-1045-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Sat Sep 18 12:04:49 2021
  Dependencies:
   
  InstallationDate: Installed on 2021-09-13 (4 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  SourcePackage: linux-oem-5.10
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.10/+bug/1944018/+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 1944018] Re: ath11k_pci sometimes crashes on suspend/resume on Dell XPS 13 9310

2021-09-17 Thread Matt Austin
Adding log snippet form kernel.log - where the following is repeated:

Sep 18 11:46:57 perseverance kernel: [314619.796128] ath11k_pci :72:00.0: 
wmi command 16387 timeout
Sep 18 11:46:57 perseverance kernel: [314619.796134] ath11k_pci :72:00.0: 
failed to send WMI_PDEV_SET_PARAM cmd
Sep 18 11:46:57 perseverance kernel: [314619.796139] ath11k_pci :72:00.0: 
failed to enable PMF QOS: (-11


** Attachment added: "kernal-snippet.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.10/+bug/1944018/+attachment/5526093/+files/kernal-snippet.log

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

Title:
  ath11k_pci sometimes crashes on suspend/resume on Dell XPS 13 9310

Status in linux-oem-5.10 package in Ubuntu:
  New

Bug description:
  Sometimes when my Dell XPS 13 9310 resumes from suspend, the display
  fails to show anything for a short while. When the display does show,
  the wireless network is no longer working.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-modules-5.10.0-1045-oem 5.10.0-1045.47
  ProcVersionSignature: Ubuntu 5.10.0-1045.47-oem 5.10.46
  Uname: Linux 5.10.0-1045-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Sat Sep 18 12:04:49 2021
  Dependencies:
   
  InstallationDate: Installed on 2021-09-13 (4 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  SourcePackage: linux-oem-5.10
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.10/+bug/1944018/+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 1944018] [NEW] ath11k_pci sometimes crashes on suspend/resume on Dell XPS 13 9310

2021-09-17 Thread Matt Austin
Public bug reported:

Sometimes when my Dell XPS 13 9310 resumes from suspend, the display
fails to show anything for a short while. When the display does show,
the wireless network is no longer working.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-modules-5.10.0-1045-oem 5.10.0-1045.47
ProcVersionSignature: Ubuntu 5.10.0-1045.47-oem 5.10.46
Uname: Linux 5.10.0-1045-oem x86_64
ApportVersion: 2.20.11-0ubuntu27.20
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: GNOME
Date: Sat Sep 18 12:04:49 2021
Dependencies:
 
InstallationDate: Installed on 2021-09-13 (4 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
SourcePackage: linux-oem-5.10
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal wayland-session

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

Title:
  ath11k_pci sometimes crashes on suspend/resume on Dell XPS 13 9310

Status in linux-oem-5.10 package in Ubuntu:
  New

Bug description:
  Sometimes when my Dell XPS 13 9310 resumes from suspend, the display
  fails to show anything for a short while. When the display does show,
  the wireless network is no longer working.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-modules-5.10.0-1045-oem 5.10.0-1045.47
  ProcVersionSignature: Ubuntu 5.10.0-1045.47-oem 5.10.46
  Uname: Linux 5.10.0-1045-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Sat Sep 18 12:04:49 2021
  Dependencies:
   
  InstallationDate: Installed on 2021-09-13 (4 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  SourcePackage: linux-oem-5.10
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.10/+bug/1944018/+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 1874567] Re: [nvidia] Rotating secondary monitor to portrait fails, results in landscape

2020-07-25 Thread Matt Austin
Thank you for fixing this bug. Installing mutter 3.36.4-0ubuntu0.20.04.1
and libmutter 3.36.4-0ubuntu0.20.04.1 from focal-proposed has resolved
this issue for me.

Note: The updated libmutter from focal-proposed also had to be
explicitly installed by me, as it was not automatically pulled in when
updating mutter.

Steps:
1) Enabled focal-proposed
2) apt update
3) apt install mutter libmutter
4) Disabled focal-proposed
5) Removed ~/.config/monitors.xml and ~gdm/config/monitors.xml
6) Rebooted
7) After login, I successfully applied my desired monitor configuration 
(changing the primary monitor and setting other monitor to portrait 
orientation).


Side notes:
1) I still had to copy ~/.config/monitors.xml to ~gdm/.config/monitors.xml for 
the correct primary monitor and orientation to be set on the login screen.
2) After applying the display configuration, the icons in the top-right of the 
gnome panel appeared blured (network/bluetooth). This was resolved by applying 
150% fractional scaling and then applying 100% scaling again in the gnome 
display settings. I haven't had time to reproduce this to know if it's a 
one-off or ongoing bug.

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

Title:
  [nvidia] Rotating secondary monitor to portrait fails, results in
  landscape

Status in OEM Priority Project:
  New
Status in gnome-control-center package in Ubuntu:
  Won't Fix
Status in mutter package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Won't Fix
Status in gnome-control-center source package in Focal:
  Won't Fix
Status in mutter source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-340 source package in Focal:
  Won't Fix
Status in nvidia-graphics-drivers-435 source package in Focal:
  Won't Fix
Status in nvidia-graphics-drivers-440 source package in Focal:
  Won't Fix

Bug description:
  [ Impact ]

  I have two monitors, with the secondary one rotated in a portrait
  orientation. Using the nvidia 440 drivers, the orientation is not
  applied when configuring in gnome settings (the displays go blank for
  a second, and then reappear in landscape orientation).

  Using nvidia settings, I can set the monitor rotation and offset
  correctly, however these settings do not persist on next boot (even
  when selecting to save to xorg.conf).

  When using the nouveau drivers, the orientation is applied correctly
  in gnome settings, and is persisted.

  [ Test case ]

  1. Install nvidia drivers
  2. Configure an external monitor to be in portrait mode in 
gnome-control-center
  3. Apply the configuration
  4. Expect configuration is properly working

  [ Regression potential ]

  Wrong screen size is set and panning is used.

  

  ProblemType: BugDistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.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:  gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Fri Apr 24 08:30:41 2020
  DistUpgraded: 2020-04-20 18:27:13,972 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 440.64, 5.4.0-26-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GK106 [GeForce GTX 660] [10de:11c0] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: Micro-Star International Co., Ltd. [MSI] GK106 [GeForce GTX 
660] [1462:2871]
  InstallationDate: Installed on 2018-05-01 (723 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Shuttle Inc. SZ77
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=d2c17cee-7c37-429f-9cbb-9484a159f182 ro quiet splash 
vt.handoff=7SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to focal on 2020-04-20 (3 days ago)
  dmi.bios.date: 10/13/2014
  dmi.bios.vendor: American Megatrends Inc.
  

[Kernel-packages] [Bug 1849405] Re: Repeated keypresses from bluetooth keyboard

2019-10-30 Thread Matt Austin
I've now been using an Xorg session rather than Wayland and haven't seen
the repeated keys issue. I do get some very nasty screen tearing when
scrolling (e.g. websites) on Xorg however, so ideally I'd like to
continue using Wayland.

Does that mean that this is likely a mutter bug, rather than bluez?

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

Title:
  Repeated keypresses from bluetooth keyboard

Status in bluez package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  I have a Microsoft Surface bluetooth keyboard, and semi-frequently
  (e.g. around every 10-15mins) end up with repeated keypresses being
  made (e.g. apppt get update).

  This seems to happen when the machine is under slight stress, or when
  a new notification pops up in gnome, so it could be related to wayland
  possibly - but even if wayland or other processes are causing stress,
  I should imagine the bluetooth hid driver should not cause repeated
  key presses.

  Please let me know if you require further information about my
  environment, it's difficult to know where to begin with determining
  which process is the root cause of this.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3.2
  ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21
  Uname: Linux 5.0.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  Date: Wed Oct 23 09:38:20 2019
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. Latitude 7480
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-32-generic 
root=/dev/mapper/sarasota--kf--vg-root ro quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/04/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.15.1
  dmi.board.name: 00F6D3
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.15.1:bd07/04/2019:svnDellInc.:pnLatitude7480:pvr:rvnDellInc.:rn00F6D3:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 7480
  dmi.product.sku: 07A0
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: F8:63:3F:E9:51:8C  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN 
RX bytes:1658613 acl:66750 sco:0 events:15708 errors:0
TX bytes:605292 acl:98 sco:0 commands:2484 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1849405/+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 1849405] [NEW] Repeated keypresses from bluetooth keyboard

2019-10-22 Thread Matt Austin
Public bug reported:

I have a Microsoft Surface bluetooth keyboard, and semi-frequently (e.g.
around every 10-15mins) end up with repeated keypresses being made (e.g.
apppt get update).

This seems to happen when the machine is under slight stress, or when a
new notification pops up in gnome, so it could be related to wayland
possibly - but even if wayland or other processes are causing stress, I
should imagine the bluetooth hid driver should not cause repeated key
presses.

Please let me know if you require further information about my
environment, it's difficult to know where to begin with determining
which process is the root cause of this.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: bluez 5.48-0ubuntu3.2
ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21
Uname: Linux 5.0.0-32-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
Date: Wed Oct 23 09:38:20 2019
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: Dell Inc. Latitude 7480
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-32-generic 
root=/dev/mapper/sarasota--kf--vg-root ro quiet splash vt.handoff=1
SourcePackage: bluez
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/04/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.15.1
dmi.board.name: 00F6D3
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.15.1:bd07/04/2019:svnDellInc.:pnLatitude7480:pvr:rvnDellInc.:rn00F6D3:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: Latitude
dmi.product.name: Latitude 7480
dmi.product.sku: 07A0
dmi.sys.vendor: Dell Inc.
hciconfig:
 hci0:  Type: Primary  Bus: USB
BD Address: F8:63:3F:E9:51:8C  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN 
RX bytes:1658613 acl:66750 sco:0 events:15708 errors:0
TX bytes:605292 acl:98 sco:0 commands:2484 errors:0

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


** Tags: amd64 apport-bug bionic

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

Title:
  Repeated keypresses from bluetooth keyboard

Status in bluez package in Ubuntu:
  New

Bug description:
  I have a Microsoft Surface bluetooth keyboard, and semi-frequently
  (e.g. around every 10-15mins) end up with repeated keypresses being
  made (e.g. apppt get update).

  This seems to happen when the machine is under slight stress, or when
  a new notification pops up in gnome, so it could be related to wayland
  possibly - but even if wayland or other processes are causing stress,
  I should imagine the bluetooth hid driver should not cause repeated
  key presses.

  Please let me know if you require further information about my
  environment, it's difficult to know where to begin with determining
  which process is the root cause of this.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3.2
  ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21
  Uname: Linux 5.0.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  Date: Wed Oct 23 09:38:20 2019
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. Latitude 7480
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-32-generic 
root=/dev/mapper/sarasota--kf--vg-root ro quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/04/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.15.1
  dmi.board.name: 00F6D3
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.15.1:bd07/04/2019:svnDellInc.:pnLatitude7480:pvr:rvnDellInc.:rn00F6D3:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 7480
  dmi.product.sku: 07A0
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: F8:63:3F:E9:51:8C  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN 
RX bytes:1658613 acl:66750 sco:0 events:15708 errors:0
TX bytes:605292 acl:98 sco:0 commands:2484 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1849405/+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 1572659] Re: bcmwl driver does not work with kernel 4.4.0-21 when secure boot enabled

2016-05-06 Thread Matt Austin
Same problem continues with 4.4.0-22.

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

Title:
  bcmwl driver does not work with kernel 4.4.0-21 when secure boot
  enabled

Status in bcmwl package in Ubuntu:
  Confirmed

Bug description:
  After updating ubuntu 16.04 to latest kernel 4.4.0-21, bcmwl driver
  (package bcmwl-kernel-source) does not load and wifi not work.

  sudo modprobe wl
  modprobe: ERROR: could not insert 'wl': Required key not available

  If I boot with kernel 4.4.0-18 - bcmwl loads normally and wifi works.

  If secure boot disabled - bcmwl loads normally with kernel 4.4.0-21
  and wifi works.

  
  ---
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2015-12-02 (140 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  NonfreeKernelModules: wl
  Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu8
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Tags:  xenial
  Uname: Linux 4.4.0-18-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-03-03 (47 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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