[Kernel-packages] [Bug 1858958] Re: fails on arm64 w/ 5.4 kernel: crash: cannot determine VA_BITS_ACTUAL: please use /proc/kcore

[Launchpad Bug Tracker]

This bug was fixed in the package crash - 7.2.6-1ubuntu3

---
crash (7.2.6-1ubuntu3) focal; urgency=medium

  * Rebuild with updated binutils, fixing an "illegal insruction" crash
on arm64. LP: #1859226.
  * Update the maintainer field for Ubuntu.

 -- dann frazier   Sat, 11 Jan 2020 09:36:27 -0700

** Changed in: crash (Ubuntu)
   Status: New => Fix Released

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

Title:
  fails on arm64 w/ 5.4 kernel: crash: cannot determine VA_BITS_ACTUAL:
  please use /proc/kcore

Status in crash package in Ubuntu:
  Fix Released

Bug description:
  crash autopkgtests have began to fail on arm64, as seen here:

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-focal/focal/arm64/c/crash/20191223_190616_50c73@/log.gz

  The significant difference between this test and the last successful
  one is that the host kernel has moved from 5.3 to 5.4. As crash needs
  to understand some internals of the kernel memory, it often needs
  updates to deal with new kernels.

  I've verified that the existing crash still works fine w/ a 5.3
  kernel[1], but does not w/ 5.4:

  $ sudo crash -st /usr/lib/debug/boot/vmlinux-$(uname -r)

  crash: cannot determine VA_BITS_ACTUAL: please use /proc/kcore

  However, note hte "please use /proc/kcore" - if I point crash at that
  instead of whatever it normally uses (/dev/mem?) it is able to start
  [2]. The same is also true w/ current upstream as of commit 7c2d41e
  btw - it fails w/o /proc/kcore and works with it.

  
  [1]
  ubuntu@d05-3:~$ sudo crash /usr/lib/debug/boot/vmlinux-5.3.0-26-generic 

  crash 7.2.6
  Copyright (C) 2002-2019  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 1999-2006  Hewlett-Packard Co
  Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
  Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
  Copyright (C) 2005, 2011  NEC Corporation
  Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
  Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
  This program is free software, covered by the GNU General Public License,
  and you are welcome to change it and/or distribute copies of it under
  certain conditions.  Enter "help copying" to see the conditions.
  This program has absolutely no warranty.  Enter "help warranty" for details.
   
  GNU gdb (GDB) 7.6
  Copyright (C) 2013 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "aarch64-unknown-linux-gnu"...

KERNEL: /usr/lib/debug/boot/vmlinux-5.3.0-26-generic
  DUMPFILE: /proc/kcore
  CPUS: 64
  DATE: Wed Jan  8 22:32:40 2020
UPTIME: 4 days, 20:46:37
  LOAD AVERAGE: 1.09, 0.76, 0.46
 TASKS: 836
  NODENAME: d05-3
   RELEASE: 5.3.0-26-generic
   VERSION: #28-Ubuntu SMP Wed Dec 18 05:39:18 UTC 2019
   MACHINE: aarch64  (unknown Mhz)
MEMORY: 127.7 GB
   PID: 19415
   COMMAND: "crash"
  TASK: 801464623b00  [THREAD_INFO: 801464623b00]
   CPU: 13
 STATE: TASK_RUNNING (ACTIVE)

  crash> quit

  [2]
  ubuntu@d05-3:~$ sudo crash -st /usr/lib/debug/boot/vmlinux-$(uname -r) 
/proc/kcore
  Thu Jan  9 00:20:20 2020

  ubuntu@d05-3:~$ sudo crash /usr/lib/debug/boot/vmlinux-$(uname -r)
  /proc/kcore

  crash 7.2.6
  Copyright (C) 2002-2019  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 1999-2006  Hewlett-Packard Co
  Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
  Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
  Copyright (C) 2005, 2011  NEC Corporation
  Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
  Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
  This program is free software, covered by the GNU General Public License,
  and you are welcome to change it and/or distribute copies of it under
  certain conditions.  Enter "help copying" to see the conditions.
  This program has absolutely no warranty.  Enter "help warranty" for details.
   
  GNU gdb (GDB) 7.6
  Copyright (C) 2013 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "aarch64-unknown-linux-gnu"...

KERNEL: /usr/lib/debug/boot/vmlinux-5.4.0-9-generic
  DUMPFILE: /proc/kcore
  CPUS: 64
  DATE: Thu Jan  9 00:20:57 2020
U

[Kernel-packages] [Bug 1859226] Re: crash reports Illegal instruction w/ newer binutils

[Launchpad Bug Tracker]

This bug was fixed in the package crash - 7.2.6-1ubuntu3

---
crash (7.2.6-1ubuntu3) focal; urgency=medium

  * Rebuild with updated binutils, fixing an "illegal insruction" crash
on arm64. LP: #1859226.
  * Update the maintainer field for Ubuntu.

 -- dann frazier   Sat, 11 Jan 2020 09:36:27 -0700

** Changed in: crash (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  crash reports Illegal instruction w/ newer binutils

Status in binutils package in Ubuntu:
  Fix Released
Status in crash package in Ubuntu:
  Fix Released

Bug description:
  crash 7.2.6-1ubuntu1 now fails on arm64 w/ an Illegal instruction:

  $ sudo crash -st /usr/lib/debug/boot/vmlinux-$(uname -r) /proc/kcore
  Illegal instruction

  The previous version of crash was 7.2.6-1build1. While there are no
  differences in the source code (just an autopkgtest update), it did
  not hit this:

  $ sudo crash -st /usr/lib/debug/boot/vmlinux-$(uname -r) /proc/kcore
  Fri Jan 10 19:31:59 2020

  I've verified that the significant difference is with the version of
  binutils used to build crash.

  2.33.50.20200107-1ubuntu1 - Illegal instruction
  2.33.1-6ubuntu3 - OK
  2.32.51.20190905-0ubuntu1 - OK

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1859226/+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 1850099] Re: Kernel 5.3.0-19 panic after upgrade to eoan ermine from disco dingo

[Brendan]

Yeah I would, but with the 5.3.0-26 update, it's now working again. Do
you still want me to try?

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

Title:
  Kernel 5.3.0-19 panic after upgrade to eoan ermine from disco dingo

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to eoan ermine, my laptop (Dell Precision 5510) got an error 
message stating 
  "Error: out of memory
  Press any key to continue..."

  After pressing a key, nothing changed. I left the room and came back
  to see that there was a kernel panic. I'll attach  picture as I
  couldn't copy/paste the console output.

  Description:  Ubuntu 19.10
  Release:  19.10

  linux-image-5.3.0-19-generic

  I expect the kernel to load without a panic.
  The kernel panicked.

  After rebooting and selecting an older kernel, I was able to boot and
  load the old kernel without issue (5.0.0-32-generic)

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-19-generic 5.3.0-19.20
  ProcVersionSignature: Ubuntu 5.0.0-32.34-generic 5.0.21
  Uname: Linux 5.0.0-32-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lost   1947 F pulseaudio
  CurrentDesktop: XFCE
  Date: Mon Oct 28 00:52:26 2019
  HibernationDevice: RESUME=UUID=0dba346e-043c-4e62-95a4-911a6a65e626
  InstallationDate: Installed on 2016-06-17 (1227 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f3:21d5 Elan Microelectronics Corp. Touchscreen
   Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 004: ID 1bcf:2b95 Sunplus Innovation Technology Inc. 
Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Precision 5510
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-32-generic 
root=/dev/mapper/xubuntu--vg-root ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-32-generic N/A
   linux-backports-modules-5.0.0-32-generic  N/A
   linux-firmware1.183.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/03/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.12.0
  dmi.board.name: 0WVDX2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A07
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.12.0:bd10/03/2019:svnDellInc.:pnPrecision5510:pvr:rvnDellInc.:rn0WVDX2:rvrA07:cvnDellInc.:ct9:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 5510
  dmi.product.sku: 06E5
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850099/+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 1829497] Re: Bluetooth not work

[Naël]

*** This bug is a duplicate of bug 1832087 ***
https://bugs.launchpad.net/bugs/1832087

** This bug has been marked a duplicate of bug 1832087
   Intel WIRELESS-AC 9260 (2526:0010) Wi-Fi doesn't work on kernel > 5.0.0-16

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

Title:
  Bluetooth not work

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Kernel 5.0.0-15 > Bluetooth on INTEL® WIRELESS-AC 9260 NOT WORK !!??
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  philippe   1644 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19.1
  InstallationDate: Installed on 2018-11-13 (185 days ago)
  InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180717
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 27c6:5395  
   Bus 001 Device 002: ID 8087:0025 Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 15 9570
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-15-generic 
root=UUID=1c90898a-7750-4a75-967f-b653a0db22aa ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.0.0-15.16~18.04.1-generic 5.0.6
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-15-generic N/A
   linux-backports-modules-5.0.0-15-generic  N/A
   linux-firmware1.173.6
  Tags:  tessa
  Uname: Linux 5.0.0-15-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/26/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.10.1
  dmi.board.name: 0D0T05
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.10.1:bd04/26/2019:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9570
  dmi.product.sku: 087C
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829497/+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 1829620] Re: intel-microcode on ASUS makes kernel stuck during loading initramfs on bionic-updates, bionic-security

[Jacob]

Dell XPS5510 with i7-6820HQ has exactly the same issue on Ubuntu 19.10 after 
fresh install, apt-update && apt-upgrade && reboot, gives purple screen / stuck 
at Loading initramfs.
Switching kernel works once but next reboot it's stuck again.

Update of BIOS via built in one time setup menu and USB stick seems to
have solved the issue. Not working bios version was 5.2.something and
working BIOS version is 1.13.1.

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

Title:
  intel-microcode on ASUS makes kernel stuck during loading initramfs on
  bionic-updates, bionic-security

Status in intel-microcode package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe package in Ubuntu:
  Confirmed
Status in linux-hwe-edge package in Ubuntu:
  Confirmed

Bug description:
  Description:
  - my system gets stuck at "Booting, Loading initramfs" (the first 2 lines of 
booting, after grub)
  - does not even show the enter cryptsetup passphrase
  - affected kernels:
  # apt list --installed |grep linux-signed
  WARNING: apt does not have a stable CLI interface. Use with caution in 
scripts.
  linux-signed-generic/bionic-security,bionic-updates,now 4.15.0.50.52 amd64 
[installed]
  linux-signed-generic-hwe-18.04/bionic-security,bionic-updates,now 
4.18.0.20.70 amd64 [installed]
  linux-signed-generic-hwe-18.04-edge/bionic-security,bionic-updates,now 
5.0.0.15.71 amd64 [installed]

  - the setup is not new, has been working perfectly before (about 7
  days since my last restart?)

  System:
  - HW: ASUS Zenbook 14 UX433FN
  - Ubuntu 18.04, runing latest HWE, fully updated
  - grub(-pc), cryptsetup (crypttab entries for custom encrypted LUKS setup),

  Suspected/possible cause?:
  - recent intel-microcode package update
  - recent kernel package updates

  Steps taken:
  - tried to remove "splash quiet" from grub/kernel cmd line (also tried adding 
nosplash, noplymouth)
  - completely removed nvidia drivers (apt purge *nvidia*)
  - completely purged and reinstalled grub (grup-pc)
  - completely purged and reinstalled all kernels (headers, modules, image, ..)
  - toggle BIOS "fastboot" (now using OFF)
  - toggle UEFI SecureBoot (now using ON)
  - remove plymouth (apt remove *plymouth* , but the workaround is working with 
plymouth installed)

  Workaround:
  - so far, I'm only able to boot with non-Ubuntu kernel! 
(linux-image-liquorix-amd64)
  - which needs "splash" option ON
  - reinstall cryptsetup & update-grub (as suggested in 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829620/comments/10 )

  I am not sure how to get you more debug info, as this setup has been
  working before, and it's a very eary boot-process bug, so I can't even
  access dmesg etc.

  EDIT:

  Hypothesis:
  Only affects ASUS with i7-8565U Whiskey Lake Intel CPU

  Upstream Bug Report:
  https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/issues/1

  WORKAROUND 1: disable intel microcode updates during boot
  From this bug: 
https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1759920
  1/ add the boot parameter: dis_ucode_ldr to /etc/default/grub
  2/ update-grub

  WORKAROUND 2: downgrade (and hold) intel-microcode to older version from 
bionic/main
  apt install --reinstall intel-microcode=3.20180312.0~ubuntu18.04.1

  WORKAROUND 3: upgrade BIOS
  Asus has released updated BIOSes, which probably include the newest 
microcode. After upgrading workarounds 1,2 are not needed. 
  Please NOTE, unlike workarounds 1,2, BIOS upgrade is permanent and cannot be 
(easily) reverted. 

  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: KDE
  DistroRelease: KDE neon 18.04
  InstallationDate: Installed on 2012-12-23 (2337 days ago)
  InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 
(20121017.1)
  Package: linux-hwe-edge (not installed)
  Tags:  bionic wayland-session
  Uname: Linux 5.0.0-17.1-liquorix-amd64 x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm libvirtd lpadmin netdev plugdev sudo vboxusers video
  _MarkForUpload: True
  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: KDE
  DistroRelease: KDE neon 18.04
  InstallationDate: Installed on 2012-12-23 (2339 days ago)
  InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 
(20121017.1)
  Package: linux-hwe-edge
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.0.0-15.16~18.04.1-generic 5.0.6
  Tags: third-party-packages bionic wayland-session
  Uname: Linux 5.0.0-15-generic x86_64
  UnreportableReason: Toto není oficiální KDE balík. Prosíme odstraňte všechny 
balíky třetích stran a zkuste to znovu.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups

[Kernel-packages] [Bug 1443924]

[akamiriub1]

http://crackingkeys.com/buildbox-crack-keygen/

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

Title:
  1814:0201 ieee80211 phy0: rt2x00queue_flush_queue:Warning - Queue 0
  failed to flush

Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  Triaged

Bug description:
  Philips i386 PC with rt2x00 pci is suffering loss of WiFi connectivity
  after installing 15.04 Beta.

  The system did work correctly with older Ubuntu versions (like 12.04)
  and had this problem show up after upgrading to Trusty (as I already
  reported in bug #1318837). Using Trusty the problem went away when
  switching from the stock 3.13.0-XX-generic kernel to builds of newer
  kernels (like 3.14.1-031401).

  Now the same problem shows up again after installing Vivid Beta. It seems to 
be the same problem reported for other Ubuntu releases (see bugs #1318837 and 
#1383555) and also the same problem of this upstream kernel bug:
  https://bugzilla.kernel.org/show_bug.cgi?id=61621

  Someone on kernel's bug mentions turning off MSI interrupts and I can confirm 
it did change the situation:
  - normally the system looses WiFi connectivity mere seconds after boot (eg. 
can't ping anything after boot)
  - if I boot with "pci=nomsi" the system will remain connected to the WiFi for 
a much longer period (eg. I am able to apt-get install something after boot)

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-extra-3.19.0-13-generic 3.19.0-13.13
  ProcVersionSignature: Ubuntu 3.19.0-13.13-generic 3.19.3
  Uname: Linux 3.19.0-13-generic i686
  ApportVersion: 2.17-0ubuntu2
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  luca   1997 F pulseaudio
  CurrentDesktop: LXDE
  Date: Tue Apr 14 14:19:19 2015
  HibernationDevice: RESUME=UUID=cbd1e136-ffc4-48b9-b2aa-c15264b9b132
  MachineType: Freeline Freeline Series
  ProcEnviron:
   LANGUAGE=en_US:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-13-generic 
root=UUID=6110f881-b32b-426d-910a-c63b355c179c ro quiet splash vt.handoff=7 
pci=nomsi
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-13-generic N/A
   linux-backports-modules-3.19.0-13-generic  N/A
   linux-firmware 1.143
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  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: 10/29/2004
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 6.00 PG
  dmi.board.name: Freeline Series
  dmi.board.vendor: Freeline
  dmi.board.version: Ver1.0
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd10/29/2004:svnFreeline:pnFreelineSeries:pvrVer1.0:rvnFreeline:rnFreelineSeries:rvrVer1.0:cvn:ct3:cvr:
  dmi.product.name: Freeline Series
  dmi.product.version: Ver1.0
  dmi.sys.vendor: Freeline

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

[akamiriub1]

BuildBox 3.0 Crack incl Serial Key {Updated} Windows (x86/x64)
BuildBox Crack is a delightful software which is used to generate games. More , 
deprived of programming and physical coding, you will be able to create as well 
as design a game. Add more, BuildBox is a very unpretentious tool for the 
creation of games. You can use it without any skill. So, you don’t need 
programming or scripting for the formation of games. You just need to import 
some images, then allocate them and in this means you can shape out your own 
game. These are the few steps to create a game with this software. Its features 
are so prepared to work. Correspondingly, the newest version is in the market 
now. Its new version comprises features which so authoritative to work. With 
the aid of this tool, you can start your personal business by becoming a solo 
businessperson.

 BuildBox Crack 3.0 with Registration Key + Activation Key
BuildBox Registration Key can effortlessly create any 2D game very easily. Its 
working ability is excellent. Likewise, it fulfills all the requirements of the 
users. It can edit gameplay, logic pieces, cataracts and abundant more to make 
somewhat flat and exceptional. Its work is so fast and it protects your 
valuable time. Few very famous games like Line Zen and Color Switch were 
created in just one week with the help of BuildBox. It makes you talented to 
create games for diverse platforms like Mac OS X, Windows, Android, iOS, Steam, 
and Amazon, etc. More, you will be able to create indie effects with trails and 
lighting only by BuildBox. So, it is the finest software than other game 
creators. Hence, we recommend you if to install BuildBox if you want to create 
games.

BuildBox 3.0 License Key {Apk & Patch} Mac
http://crackingkeys.com/buildbox-crack-keygen/
BuildBox License Key has a user’s friendly interface. So, its popularity is 
increasing day by day. Lots of peoples are using this software in the world 
owing to its organized features. It is the 1st choice of the users. It is as 
easy as you are making a powerpoint presentation. After the creation of your 
game, you can also add in it opponent, character, entity, effects, background 
as well as a power-up in just a few seconds. As well, by using BuildBox you can 
create games for PC, Console and for Mobiles. Now, this tool is freely 
accessible for dL. This software is 100 percent working. You can easily control 
the world physics and gameplay with the slider movements.

Also, visit MacActivators.com!

Important Features:
Use for the creation of games
Its boundaries are limitless and you can create any 2D games through its help
Without programming and manual coding, you will be able to create as well as 
design a game
It’s working ability is admirable
More, very modest and easy to use
Users can create games for dissimilar platforms like Mac OS X, Windows, 
Android, iOS, Steam, and Amazon, etc
Add more, it is 100 percent working
With the use of BuildBox, you can create professional-looking games
Work smoothly
It contains monetization as well as excision option
System Requirements:
Windows 7/ 8, 8.1 /10
Disk space should be 200MBs or more
RAM: 1GB
Multi-core processor: 2GHz
1024 into 768 display
How to Crack BuildBox 3.0?
First of all, click the download button which is given below
Then, disconnect the internet
After this, unpack and then install it
If running, stop it
Copy the license file
Paste at the given option
Click to activate
All is done
Enjoy!
Buildbox Crack 3.0 {Portable + Torrent} 100% Working

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

Title:
  1814:0201 ieee80211 phy0: rt2x00queue_flush_queue:Warning - Queue 0
  failed to flush

Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  Triaged

Bug description:
  Philips i386 PC with rt2x00 pci is suffering loss of WiFi connectivity
  after installing 15.04 Beta.

  The system did work correctly with older Ubuntu versions (like 12.04)
  and had this problem show up after upgrading to Trusty (as I already
  reported in bug #1318837). Using Trusty the problem went away when
  switching from the stock 3.13.0-XX-generic kernel to builds of newer
  kernels (like 3.14.1-031401).

  Now the same problem shows up again after installing Vivid Beta. It seems to 
be the same problem reported for other Ubuntu releases (see bugs #1318837 and 
#1383555) and also the same problem of this upstream kernel bug:
  https://bugzilla.kernel.org/show_bug.cgi?id=61621

  Someone on kernel's bug mentions turning off MSI interrupts and I can confirm 
it did change the situation:
  - normally the system looses WiFi connectivity mere seconds after boot (eg. 
can't ping anything after boot)
  - if I boot with "pci=nomsi" the system will remain connected to the WiFi for 
a much longer period (eg. I am able to apt-get install something after boot)

  ProblemType: Bug
  Dis

[Kernel-packages] [Bug 1858581] Re: xenial/linux-aws: 4.4.0-1101.112 -proposed tracker

[Ubuntu Kernel Bot]

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1858594
  packages:
main: linux-aws
meta: linux-meta-aws
  phase: Testing
  phase-changed: Thursday, 09. January 2020 17:18 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
-   security-signoff: Pending -- waiting for signoff
+   security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
xenial/linux-aws/aws-kernel: bug 1858580
  variant: debs

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

Title:
  xenial/linux-aws: 4.4.0-1101.112 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  In Progress
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  In Progress
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Xenial:
  Confirmed

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1858594
  packages:
main: linux-aws
meta: linux-meta-aws
  phase: Testing
  phase-changed: Thursday, 09. January 2020 17:18 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
xenial/linux-aws/aws-kernel: bug 1858580
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1858581/+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 1859223] Re: Firmware missing for Thinkpad X-series Bluetooth adapters, leads to headset HSP/HFP profiles not working

[Christian Reis]

** Summary changed:

- Firmware missing for Thinkpad X-series Bluetooth adapters, heads to headset 
HSP/HFP profiles not working
+ Firmware missing for Thinkpad X-series Bluetooth adapters, leads to headset 
HSP/HFP profiles not working

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

Title:
  Firmware missing for Thinkpad X-series Bluetooth adapters, leads to
  headset HSP/HFP profiles not working

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  Hello there, it's my third or fourth session spending hours trying to
  debug why a Bluetooth headset would not work in HSP/HFP mode on my
  x230. The failure more is super obscure because at the time of error
  the only thing you notice is that no audio comes through in either
  direction. Using the a2dp_sink profile works fine.

  The root cause for the problem is simply missing firmware, which dmesg
  hints at during bootup:

  Jan  7 04:11:12.809444 barbudinho kernel: [490029.978724] Bluetooth: hci0: 
BCM: chip id 63
  Jan  7 04:11:12.809460 barbudinho kernel: [490029.979639] Bluetooth: hci0: 
BCM: features 0x07
  Jan  7 04:11:12.825406 barbudinho kernel: [490029.995655] Bluetooth: hci0: 
BCM20702A
  Jan  7 04:11:12.829543 barbudinho kernel: [490029.996649] Bluetooth: hci0: 
BCM20702A1 (001.002.014) build 
  Jan  7 04:11:12.829560 barbudinho kernel: [490029.996671] bluetooth hci0: 
Direct firmware load for brcm/BCM20702A1-0a5c-21e6.hcd failed with error -2
  Jan  7 04:11:12.829566 barbudinho kernel: [490029.996673] Bluetooth: hci0: 
BCM: Patch brcm/BCM20702A1-0a5c-21e6.hcd not found

  
  There are at least two firmware packages missing for different common 
X-series adapters; this is referred to from 
https://plugable.com/2014/06/23/plugable-usb-bluetooth-adapter-solving-hfphsp-profile-issues-on-linux
 and also https://wiki.gentoo.org/wiki/Lenovo_Thinkpad_T430.

  The actual firmware locations from those are:

  - 0a5c:21e8 https://s3.amazonaws.com/plugable/bin/fw-0a5c_21e8.hcd
  - 0a5c:21e6 
http://dlcdnet.asus.com/pub/ASUS/misc/BT/Bluetooth_V1201650_WHQL_Win10.zip (see 
Bluetooth_V1201650_WHQL_Win10.zip)

  There is a lot of firmware collected here which may not be available
  on Ubuntu: https://github.com/winterheart/broadcom-bt-
  firmware/tree/master/brcm

  Related Debian bug: https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=801084

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1859223/+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 1858594] Re: xenial/linux: 4.4.0-172.202 -proposed tracker

[Ubuntu Kernel Bot]

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  packages:
main: linux
meta: linux-meta
signed: linux-signed
  phase: Testing
  phase-changed: Thursday, 09. January 2020 16:08 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
certification-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
-   security-signoff: Pending -- waiting for signoff
+   security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
trusty/linux-aws: bug 1858591
trusty/linux-lts-xenial: bug 1858592
xenial/linux-aws: bug 1858581
xenial/linux-cascade: bug 1858583
xenial/linux-fips: bug 1858589
xenial/linux-kvm: bug 1858584
xenial/linux-raspi2: bug 1858586
xenial/linux-snapdragon: bug 1858588
xenial/linux/caracalla-kernel: bug 1858577
xenial/linux/pc-kernel: bug 1858578
xenial/linux/stlouis-kernel: bug 1858579
  variant: debs

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

Title:
  xenial/linux: 4.4.0-172.202 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  In Progress
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  In Progress
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  packages:
main: linux
meta: linux-meta
signed: linux-signed
  phase: Testing
  phase-changed: Thursday, 09. January 2020 16:08 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
certification-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
trusty/linux-aws: bug 1858591
trusty/linux-lts-xenial: bug 1858592
xenial/linux-aws: bug 1858581
xenial/linux-cascade: bug 1858583
xenial/linux-fips: bug 1858589
xenial/linux-kvm: bug 1858584
xenial/linux-raspi2: bug 1858586
xenial/linux-snapdragon: bug 1858588
xenial/linux/caracalla-kernel: bug 1858577
xenial/linux/pc-kernel: bug 1858578
xenial/linux/stlouis-kernel: bug 1858579
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1858594/+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 1859226] Re: crash reports Illegal instruction w/ newer binutils

[dann frazier]

binutils (2.33.50.20200111-1ubuntu1) focal; urgency=medium

  * New upstream snapshot.

binutils (2.33.50.20200111-1) unstable; urgency=medium

  * New upstream snapshot.
  * Make autopkgtests cross-test-friendly (Steve Langasek).

 -- Matthias Klose   Sat, 11 Jan 2020 15:01:26 +0100

** Changed in: binutils (Ubuntu)
   Status: New => Fix Committed

** Changed in: binutils (Ubuntu)
   Status: Fix Committed => Fix Released

** Changed in: crash (Ubuntu)
   Status: New => In Progress

** Changed in: crash (Ubuntu)
 Assignee: (unassigned) => dann frazier (dannf)

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

Title:
  crash reports Illegal instruction w/ newer binutils

Status in binutils package in Ubuntu:
  Fix Released
Status in crash package in Ubuntu:
  In Progress

Bug description:
  crash 7.2.6-1ubuntu1 now fails on arm64 w/ an Illegal instruction:

  $ sudo crash -st /usr/lib/debug/boot/vmlinux-$(uname -r) /proc/kcore
  Illegal instruction

  The previous version of crash was 7.2.6-1build1. While there are no
  differences in the source code (just an autopkgtest update), it did
  not hit this:

  $ sudo crash -st /usr/lib/debug/boot/vmlinux-$(uname -r) /proc/kcore
  Fri Jan 10 19:31:59 2020

  I've verified that the significant difference is with the version of
  binutils used to build crash.

  2.33.50.20200107-1ubuntu1 - Illegal instruction
  2.33.1-6ubuntu3 - OK
  2.32.51.20190905-0ubuntu1 - OK

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1859226/+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 1854895] Re: touchpad stopped working after the update

[BenS]

*** This bug is a duplicate of bug 1854798 ***
https://bugs.launchpad.net/bugs/1854798

I had the same problem with linux-image-4.15.0-72 on a Dell XPS-12 (9Q33 model).
The temporary fix I applied (to ensure a working kernel wasn't deleted 
automaticall) was

  sudo apt-mark hold linux-image-4.15.0-72-generic

and I uninstalled linux-image-generic.

linux-image-4.15.0-74-generic has been released and the touchpad WORKS
fine for me now.

  sudo apt-mark unhold linux-image-4.15.0-72-generic
  sudo apt update
  sudo apt install linux-image-generic

ensured the 4.15.0-74 kernel, linux-modules and linux-modules-extra were
installed for 4.15.0-74.  You may or may not want to continue holding
the previous known working kernel version.

Note: When testing linux-image-4.15.0-74-generic I just installed it and
linux-modules, but my WiFi also requires linux-modules-extra.

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

Title:
  touchpad stopped working after the update

Status in Linux:
  New
Status in XOrg-Driver-Synaptics:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After the automatic software update the touchpad stopped working in my
  laptop.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-72-generic 4.15.0-72.81
  ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18
  Uname: Linux 4.15.0-72-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  anil   1722 F pulseaudio
   /dev/snd/controlC0:  anil   1722 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Dec  12 21:44:48 2019
  InstallationDate: Installed on 2018-12-21 (346 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Dell Inc. Inspiron 3542
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-72-generic 
root=UUID=a85be26b-aca7-48bd-b03b-6a99e1587772 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-72-generic N/A
   linux-backports-modules-4.15.0-72-generic  N/A
   linux-firmware 1.173.12
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/23/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A14
  dmi.board.name: 09V1VC
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A14
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA14:bd05/23/2018:svnDellInc.:pnInspiron3542:pvrNotSpecified:rvnDellInc.:rn09V1VC:rvrA14:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 3542
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1854895/+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 1859212] Re: Move pci-hyperv.ko from linux-modules-extra to support installation to Hyper-V using DDA

[TJ]

There are no logs required; this is a feature enhancement request

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

Title:
  Move pci-hyperv.ko from linux-modules-extra to support installation to
  Hyper-V using DDA

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Move "pci-hyperv.ko" to the primary kernel image package.

  Whilst attempting a 20.04 install into a Microsoft Windows Hyper-V
  guest that uses Discrete Device Assignment (DDA a.k.a. PCI pass-
  through) for 2x NVMe SSDs and Intel i350-T4 quad-port Gigabit Ethernet
  we found that the installer kernel (ubuntu-server) does not include
  the "drivers/pci/controller/pci-hyperv.ko" module that is required for
  Linux to discover the Hyper-V para-virtualised PCI bus.

  Eventually discovered the module in the installer ISO's
  /pool/main/l/linux/linux-modules-extra-`uname-r`_amd64.deb and were
  able to manually install it with:

  # udpkg --unpack /cdrom/pool/main/l/linux/linux-modules-extra-`uname 
-r`_amd64.deb
  # depmod

  After which it could be loaded ("pci-hyperv-intf.ko" is already
  installed):

  # modprobe pci-hyperv-intf
  # modprobe pci-hyperv

  At this point it is possible to use the NVMe devices.

  We used 'mdadm' to create a RAID-1 mirror and then returned to the
  installer and were able to use the partitioner to install the root
  file-system to NVMe, although it is worth noting that GRUB has to be
  installed to a Hyper-V virtual storage device (a Hyper-V file on NTFS)
  in order to boot since the guest UEFI nor GRUB can 'see' any PCI
  devices without help from a para-virtualisation driver.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859212/+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 1859287] Status changed to Confirmed

[Ubuntu Kernel Bot]

This change was made by a bot.

** Changed in: linux (Ubuntu)
   Status: New => 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/1859287

Title:
  iwlwifi broken for Killer Wi-Fi 6 AX1650i with 5.4/20.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi there,

  Laptop: Dell XPS 13 7390 2-in-1
  Built-in wireless: Killer Wi-Fi 6 AX1650i 160MHz

  iwlwifi worked fine with 19.10 but breaks when upgrading to 20.04.
  Firmware crashes after loading and interface doesn't show up.

  This is with:
  linux-image-5.4.0-9-generic   5.4.0-9.12
  linux-firmware 1.184

  I've noticed the driver was trying to load a more recent firmware:
  Direct firmware load for iwlwifi-Qu-b0-hr-b0-50.ucode failed with error -2

  I've downloaded this file from upstream iwlwifi firmware git and tried
  unloading/reloading iwlwifi. Driver crashes as well, but with a
  different error code.

  Best,
  - LM

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-9-generic 5.4.0-9.12
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  Uname: Linux 5.4.0-9-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lool   1579 F pulseaudio
   /dev/snd/pcmC0D0p:   lool   1579 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 11 15:02:08 2020
  InstallationDate: Installed on 2019-12-02 (39 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Dell Inc. XPS 13 7390 2-in-1
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-9-generic 
root=UUID=854f3bc2-da3a-4a3c-82a1-6b04a932bb29 ro pcie_aspm=off 
plymouth.force-scale=3 quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-9-generic N/A
   linux-backports-modules-5.4.0-9-generic  N/A
   linux-firmware   1.184
  RfKill:
   0: hci0: Bluetooth
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2020-01-11 (0 days ago)
  dmi.bios.date: 11/10/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.3
  dmi.board.name: 06CDVY
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.3:bd11/10/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn06CDVY:rvrA00:cvnDellInc.:ct31:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 7390 2-in-1
  dmi.product.sku: 08B0
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859287/+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 1859287] [NEW] iwlwifi broken for Killer Wi-Fi 6 AX1650i with 5.4/20.04

[Loïc Minier]

Public bug reported:

Hi there,

Laptop: Dell XPS 13 7390 2-in-1
Built-in wireless: Killer Wi-Fi 6 AX1650i 160MHz

iwlwifi worked fine with 19.10 but breaks when upgrading to 20.04.
Firmware crashes after loading and interface doesn't show up.

This is with:
linux-image-5.4.0-9-generic   5.4.0-9.12
linux-firmware 1.184

I've noticed the driver was trying to load a more recent firmware:
Direct firmware load for iwlwifi-Qu-b0-hr-b0-50.ucode failed with error -2

I've downloaded this file from upstream iwlwifi firmware git and tried
unloading/reloading iwlwifi. Driver crashes as well, but with a
different error code.

Best,
- LM

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-9-generic 5.4.0-9.12
ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
Uname: Linux 5.4.0-9-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu15
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  lool   1579 F pulseaudio
 /dev/snd/pcmC0D0p:   lool   1579 F...m pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Sat Jan 11 15:02:08 2020
InstallationDate: Installed on 2019-12-02 (39 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
MachineType: Dell Inc. XPS 13 7390 2-in-1
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-9-generic 
root=UUID=854f3bc2-da3a-4a3c-82a1-6b04a932bb29 ro pcie_aspm=off 
plymouth.force-scale=3 quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.4.0-9-generic N/A
 linux-backports-modules-5.4.0-9-generic  N/A
 linux-firmware   1.184
RfKill:
 0: hci0: Bluetooth
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
UpgradeStatus: Upgraded to focal on 2020-01-11 (0 days ago)
dmi.bios.date: 11/10/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.1.3
dmi.board.name: 06CDVY
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 31
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.3:bd11/10/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn06CDVY:rvrA00:cvnDellInc.:ct31:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 13 7390 2-in-1
dmi.product.sku: 08B0
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug focal

** Description changed:

  Hi there,
  
  Laptop: Dell XPS 13 7390 2-in-1
  Built-in wireless: Killer Wi-Fi 6 AX1650i 160MHz
  
  iwlwifi worked fine with 19.10 but breaks when upgrading to 20.04.
  Firmware crashes after loading and interface doesn't show up.
  
  This is with:
  linux-image-5.4.0-9-generic   5.4.0-9.12
  linux-firmware 1.184
  
  I've noticed the driver was trying to load a more recent firmware:
- Direct firmware load for iwlwifi-Qu-b0-hr-b0-49.ucode failed with error -2
+ Direct firmware load for iwlwifi-Qu-b0-hr-b0-50.ucode failed with error -2
  
  I've downloaded this file from upstream iwlwifi firmware git and tried
  unloading/reloading iwlwifi. Driver crashes as well, but with a
  different error code.
  
  Best,
  - LM
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-9-generic 5.4.0-9.12
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  Uname: Linux 5.4.0-9-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  lool   1579 F pulseaudio
-  /dev/snd/pcmC0D0p:   lool   1579 F...m pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  lool   1579 F pulseaudio
+  /dev/snd/pcmC0D0p:   lool   1579 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 11 15:02:08 2020
  InstallationDate: Installed on 2019-12-02 (39 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Dell Inc. XPS 13 7390 2-in-1
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=fr_FR.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=fr_FR.UTF-8
+  SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-9-generic 
root=UUID=854f3bc2-da3a-4a3c-82a1-6b04a932bb29 ro pcie_aspm=off 
plymouth.force-scale=3 quiet splash vt.handoff=7
  RelatedPackageVersions:
-  linux-restricted-modules-5.4.0-9-generic N/A
-  linux-backports-modules-5.4.0-9-generic  N/A
-  linux-firmware   1.184
+  linux-restricted-modules-5.4.0-9-generic N/A
+  linux-backports-modules-5.4.0-9-generic  N/A
+  linux-firmware   1.184
  RfKill:
-  0: hci0: Bluetooth
-   Soft blocked: no
-   Hard blocked: no
+  0: hci0: Bluetooth
+   Soft bloc

[Kernel-packages] [Bug 1859283] Status changed to Confirmed

[Ubuntu Kernel Bot]

This change was made by a bot.

** Changed in: linux (Ubuntu)
   Status: New => 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/1859283

Title:
  package linux-modules-5.3.0-26-generic (not installed) failed to
  install/upgrade: no se puede crear el nuevo fichero
  '/var/lib/dpkg/info/linux-modules-5.3.0-26-generic.list-new':
  Operación no permitida

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Is not posible update

  ProblemType: Package
  DistroRelease: Ubuntu 19.10
  Package: linux-modules-5.3.0-26-generic (not installed)
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alvaro 1157 F pulseaudio
  Date: Sat Jan 11 13:00:47 2020
  DpkgHistoryLog:
   Start-Date: 2020-01-11  13:00:42
   Commandline: packagekit role='install-packages'
   Requested-By: alvaro (1000)
   Install: leocad:amd64 (19.07.1-1), libqt5concurrent5:amd64 
(5.12.4+dfsg-4ubuntu1, automatic), linux-image-5.3.0-26-generic:amd64 
(5.3.0-26.28, automatic), linux-headers-5.3.0-26:amd64 (5.3.0-26.28, 
automatic), linux-headers-5.3.0-26-generic:amd64 (5.3.0-26.28, automatic), 
linux-modules-extra-5.3.0-26-generic:amd64 (5.3.0-26.28, automatic), 
linux-modules-5.3.0-26-generic:amd64 (5.3.0-26.28, automatic)
   Upgrade: linux-headers-generic:amd64 (5.3.0.24.28, 5.3.0.26.30), 
linux-image-generic:amd64 (5.3.0.24.28, 5.3.0.26.30), linux-generic:amd64 
(5.3.0.24.28, 5.3.0.26.30)
  DpkgTerminalLog:
   Preparando para desempaquetar 
.../0-linux-modules-5.3.0-26-generic_5.3.0-26.28_amd64.deb ...
   Desempaquetando linux-modules-5.3.0-26-generic (5.3.0-26.28) ...
   dpkg: error al procesar el archivo 
/tmp/apt-dpkg-install-LCVldB/0-linux-modules-5.3.0-26-generic_5.3.0-26.28_amd64.deb
 (--unpack):
no se puede crear el nuevo fichero 
'/var/lib/dpkg/info/linux-modules-5.3.0-26-generic.list-new': Operación no 
permitida
  ErrorMessage: no se puede crear el nuevo fichero 
'/var/lib/dpkg/info/linux-modules-5.3.0-26-generic.list-new': Operación no 
permitida
  InstallationDate: Installed on 2019-09-28 (104 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: TOSHIBA SATELLITE C855-21N
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=5b70d5f9-c5a5-4122-8a7a-3e80eea36553 ro 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.
  Python3Details: /usr/bin/python3.7, Python 3.7.5, python3-minimal, 3.7.5-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.17-1
  RelatedPackageVersions: grub-pc 2.04-1ubuntu12.1
  SourcePackage: linux
  Title: package linux-modules-5.3.0-26-generic (not installed) failed to 
install/upgrade: no se puede crear el nuevo fichero 
'/var/lib/dpkg/info/linux-modules-5.3.0-26-generic.list-new': Operación no 
permitida
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/17/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: 6.70
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: PLCSF8
  dmi.board.vendor: Intel
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvr6.70:bd07/17/2013:svnTOSHIBA:pnSATELLITEC855-21N:pvrPSCBWE-07900MCE:rvnIntel:rnPLCSF8:rvrType2-BoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
  dmi.product.family: Type1Family
  dmi.product.name: SATELLITE C855-21N
  dmi.product.sku: PSCBWE
  dmi.product.version: PSCBWE-07900MCE
  dmi.sys.vendor: TOSHIBA

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859283/+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 1859284] Status changed to Confirmed

[Ubuntu Kernel Bot]

This change was made by a bot.

** Changed in: linux (Ubuntu)
   Status: New => 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/1859284

Title:
  package linux-modules-5.3.0-26-generic (not installed) failed to
  install/upgrade: no se puede crear el nuevo fichero
  '/var/lib/dpkg/info/linux-modules-5.3.0-26-generic.list-new':
  Operación no permitida

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Is not posible update

  ProblemType: Package
  DistroRelease: Ubuntu 19.10
  Package: linux-modules-5.3.0-26-generic (not installed)
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alvaro 1157 F pulseaudio
  Date: Sat Jan 11 13:00:47 2020
  DpkgHistoryLog:
   Start-Date: 2020-01-11  13:00:42
   Commandline: packagekit role='install-packages'
   Requested-By: alvaro (1000)
   Install: leocad:amd64 (19.07.1-1), libqt5concurrent5:amd64 
(5.12.4+dfsg-4ubuntu1, automatic), linux-image-5.3.0-26-generic:amd64 
(5.3.0-26.28, automatic), linux-headers-5.3.0-26:amd64 (5.3.0-26.28, 
automatic), linux-headers-5.3.0-26-generic:amd64 (5.3.0-26.28, automatic), 
linux-modules-extra-5.3.0-26-generic:amd64 (5.3.0-26.28, automatic), 
linux-modules-5.3.0-26-generic:amd64 (5.3.0-26.28, automatic)
   Upgrade: linux-headers-generic:amd64 (5.3.0.24.28, 5.3.0.26.30), 
linux-image-generic:amd64 (5.3.0.24.28, 5.3.0.26.30), linux-generic:amd64 
(5.3.0.24.28, 5.3.0.26.30)
  DpkgTerminalLog:
   Preparando para desempaquetar 
.../0-linux-modules-5.3.0-26-generic_5.3.0-26.28_amd64.deb ...
   Desempaquetando linux-modules-5.3.0-26-generic (5.3.0-26.28) ...
   dpkg: error al procesar el archivo 
/tmp/apt-dpkg-install-LCVldB/0-linux-modules-5.3.0-26-generic_5.3.0-26.28_amd64.deb
 (--unpack):
no se puede crear el nuevo fichero 
'/var/lib/dpkg/info/linux-modules-5.3.0-26-generic.list-new': Operación no 
permitida
  ErrorMessage: no se puede crear el nuevo fichero 
'/var/lib/dpkg/info/linux-modules-5.3.0-26-generic.list-new': Operación no 
permitida
  InstallationDate: Installed on 2019-09-28 (104 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: TOSHIBA SATELLITE C855-21N
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=5b70d5f9-c5a5-4122-8a7a-3e80eea36553 ro 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.
  Python3Details: /usr/bin/python3.7, Python 3.7.5, python3-minimal, 3.7.5-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.17-1
  RelatedPackageVersions: grub-pc 2.04-1ubuntu12.1
  SourcePackage: linux
  Title: package linux-modules-5.3.0-26-generic (not installed) failed to 
install/upgrade: no se puede crear el nuevo fichero 
'/var/lib/dpkg/info/linux-modules-5.3.0-26-generic.list-new': Operación no 
permitida
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/17/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: 6.70
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: PLCSF8
  dmi.board.vendor: Intel
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvr6.70:bd07/17/2013:svnTOSHIBA:pnSATELLITEC855-21N:pvrPSCBWE-07900MCE:rvnIntel:rnPLCSF8:rvrType2-BoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
  dmi.product.family: Type1Family
  dmi.product.name: SATELLITE C855-21N
  dmi.product.sku: PSCBWE
  dmi.product.version: PSCBWE-07900MCE
  dmi.sys.vendor: TOSHIBA

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859284/+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 1859283] [NEW] package linux-modules-5.3.0-26-generic (not installed) failed to install/upgrade: no se puede crear el nuevo fichero '/var/lib/dpkg/info/linux-modules-5.3.0-26-ge

[Alvaro]

Public bug reported:

Is not posible update

ProblemType: Package
DistroRelease: Ubuntu 19.10
Package: linux-modules-5.3.0-26-generic (not installed)
ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
Uname: Linux 5.3.0-19-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  alvaro 1157 F pulseaudio
Date: Sat Jan 11 13:00:47 2020
DpkgHistoryLog:
 Start-Date: 2020-01-11  13:00:42
 Commandline: packagekit role='install-packages'
 Requested-By: alvaro (1000)
 Install: leocad:amd64 (19.07.1-1), libqt5concurrent5:amd64 
(5.12.4+dfsg-4ubuntu1, automatic), linux-image-5.3.0-26-generic:amd64 
(5.3.0-26.28, automatic), linux-headers-5.3.0-26:amd64 (5.3.0-26.28, 
automatic), linux-headers-5.3.0-26-generic:amd64 (5.3.0-26.28, automatic), 
linux-modules-extra-5.3.0-26-generic:amd64 (5.3.0-26.28, automatic), 
linux-modules-5.3.0-26-generic:amd64 (5.3.0-26.28, automatic)
 Upgrade: linux-headers-generic:amd64 (5.3.0.24.28, 5.3.0.26.30), 
linux-image-generic:amd64 (5.3.0.24.28, 5.3.0.26.30), linux-generic:amd64 
(5.3.0.24.28, 5.3.0.26.30)
DpkgTerminalLog:
 Preparando para desempaquetar 
.../0-linux-modules-5.3.0-26-generic_5.3.0-26.28_amd64.deb ...
 Desempaquetando linux-modules-5.3.0-26-generic (5.3.0-26.28) ...
 dpkg: error al procesar el archivo 
/tmp/apt-dpkg-install-LCVldB/0-linux-modules-5.3.0-26-generic_5.3.0-26.28_amd64.deb
 (--unpack):
  no se puede crear el nuevo fichero 
'/var/lib/dpkg/info/linux-modules-5.3.0-26-generic.list-new': Operación no 
permitida
ErrorMessage: no se puede crear el nuevo fichero 
'/var/lib/dpkg/info/linux-modules-5.3.0-26-generic.list-new': Operación no 
permitida
InstallationDate: Installed on 2019-09-28 (104 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
MachineType: TOSHIBA SATELLITE C855-21N
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=5b70d5f9-c5a5-4122-8a7a-3e80eea36553 ro 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.
Python3Details: /usr/bin/python3.7, Python 3.7.5, python3-minimal, 3.7.5-1
PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.17-1
RelatedPackageVersions: grub-pc 2.04-1ubuntu12.1
SourcePackage: linux
Title: package linux-modules-5.3.0-26-generic (not installed) failed to 
install/upgrade: no se puede crear el nuevo fichero 
'/var/lib/dpkg/info/linux-modules-5.3.0-26-generic.list-new': Operación no 
permitida
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/17/2013
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: 6.70
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: PLCSF8
dmi.board.vendor: Intel
dmi.board.version: Type2 - Board Version
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: OEM Chassis Manufacturer
dmi.chassis.version: OEM Chassis Version
dmi.modalias: 
dmi:bvnInsydeCorp.:bvr6.70:bd07/17/2013:svnTOSHIBA:pnSATELLITEC855-21N:pvrPSCBWE-07900MCE:rvnIntel:rnPLCSF8:rvrType2-BoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
dmi.product.family: Type1Family
dmi.product.name: SATELLITE C855-21N
dmi.product.sku: PSCBWE
dmi.product.version: PSCBWE-07900MCE
dmi.sys.vendor: TOSHIBA

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


** Tags: amd64 apport-package eoan

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

Title:
  package linux-modules-5.3.0-26-generic (not installed) failed to
  install/upgrade: no se puede crear el nuevo fichero
  '/var/lib/dpkg/info/linux-modules-5.3.0-26-generic.list-new':
  Operación no permitida

Status in linux package in Ubuntu:
  New

Bug description:
  Is not posible update

  ProblemType: Package
  DistroRelease: Ubuntu 19.10
  Package: linux-modules-5.3.0-26-generic (not installed)
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alvaro 1157 F pulseaudio
  Date: Sat Jan 11 13:00:47 2020
  DpkgHistoryLog:
   Start-Date: 2020-01-11  13:00:42
   Commandline: packagekit role='install-packages'
   Requested-By: alvaro (1000)
   Install: leocad:amd64 (19.07.1-1), libqt5concurrent5:amd64 
(5.12.4+dfsg-4ubuntu1, automatic), linux-image-5.3.0-26-generic:amd64 
(5.3.0-26.28, automatic), linux-headers-5.3.0-26:amd64 (5.3.0-26.28, 
automatic), linux-headers-5.3.0-26-generic:amd64 (5.3.0-26.28, automatic), 
linux-modules-extra-5.3.0-26-generic:amd64 (5.3.0-26.28, automatic), 
linux-modules-5.3.0-26-generic:amd64 (5.3.0-26.28, automatic)
   Upgrade: linux-headers-generic:amd64 (5.3.0.24.28, 5.3.0.26.30), 
linux-image-gen

[Kernel-packages] [Bug 1859284] [NEW] package linux-modules-5.3.0-26-generic (not installed) failed to install/upgrade: no se puede crear el nuevo fichero '/var/lib/dpkg/info/linux-modules-5.3.0-26-ge

[Alvaro]

Public bug reported:

Is not posible update

ProblemType: Package
DistroRelease: Ubuntu 19.10
Package: linux-modules-5.3.0-26-generic (not installed)
ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
Uname: Linux 5.3.0-19-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  alvaro 1157 F pulseaudio
Date: Sat Jan 11 13:00:47 2020
DpkgHistoryLog:
 Start-Date: 2020-01-11  13:00:42
 Commandline: packagekit role='install-packages'
 Requested-By: alvaro (1000)
 Install: leocad:amd64 (19.07.1-1), libqt5concurrent5:amd64 
(5.12.4+dfsg-4ubuntu1, automatic), linux-image-5.3.0-26-generic:amd64 
(5.3.0-26.28, automatic), linux-headers-5.3.0-26:amd64 (5.3.0-26.28, 
automatic), linux-headers-5.3.0-26-generic:amd64 (5.3.0-26.28, automatic), 
linux-modules-extra-5.3.0-26-generic:amd64 (5.3.0-26.28, automatic), 
linux-modules-5.3.0-26-generic:amd64 (5.3.0-26.28, automatic)
 Upgrade: linux-headers-generic:amd64 (5.3.0.24.28, 5.3.0.26.30), 
linux-image-generic:amd64 (5.3.0.24.28, 5.3.0.26.30), linux-generic:amd64 
(5.3.0.24.28, 5.3.0.26.30)
DpkgTerminalLog:
 Preparando para desempaquetar 
.../0-linux-modules-5.3.0-26-generic_5.3.0-26.28_amd64.deb ...
 Desempaquetando linux-modules-5.3.0-26-generic (5.3.0-26.28) ...
 dpkg: error al procesar el archivo 
/tmp/apt-dpkg-install-LCVldB/0-linux-modules-5.3.0-26-generic_5.3.0-26.28_amd64.deb
 (--unpack):
  no se puede crear el nuevo fichero 
'/var/lib/dpkg/info/linux-modules-5.3.0-26-generic.list-new': Operación no 
permitida
ErrorMessage: no se puede crear el nuevo fichero 
'/var/lib/dpkg/info/linux-modules-5.3.0-26-generic.list-new': Operación no 
permitida
InstallationDate: Installed on 2019-09-28 (104 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
MachineType: TOSHIBA SATELLITE C855-21N
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=5b70d5f9-c5a5-4122-8a7a-3e80eea36553 ro 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.
Python3Details: /usr/bin/python3.7, Python 3.7.5, python3-minimal, 3.7.5-1
PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.17-1
RelatedPackageVersions: grub-pc 2.04-1ubuntu12.1
SourcePackage: linux
Title: package linux-modules-5.3.0-26-generic (not installed) failed to 
install/upgrade: no se puede crear el nuevo fichero 
'/var/lib/dpkg/info/linux-modules-5.3.0-26-generic.list-new': Operación no 
permitida
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/17/2013
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: 6.70
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: PLCSF8
dmi.board.vendor: Intel
dmi.board.version: Type2 - Board Version
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: OEM Chassis Manufacturer
dmi.chassis.version: OEM Chassis Version
dmi.modalias: 
dmi:bvnInsydeCorp.:bvr6.70:bd07/17/2013:svnTOSHIBA:pnSATELLITEC855-21N:pvrPSCBWE-07900MCE:rvnIntel:rnPLCSF8:rvrType2-BoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
dmi.product.family: Type1Family
dmi.product.name: SATELLITE C855-21N
dmi.product.sku: PSCBWE
dmi.product.version: PSCBWE-07900MCE
dmi.sys.vendor: TOSHIBA

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


** Tags: amd64 apport-package eoan

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

Title:
  package linux-modules-5.3.0-26-generic (not installed) failed to
  install/upgrade: no se puede crear el nuevo fichero
  '/var/lib/dpkg/info/linux-modules-5.3.0-26-generic.list-new':
  Operación no permitida

Status in linux package in Ubuntu:
  New

Bug description:
  Is not posible update

  ProblemType: Package
  DistroRelease: Ubuntu 19.10
  Package: linux-modules-5.3.0-26-generic (not installed)
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alvaro 1157 F pulseaudio
  Date: Sat Jan 11 13:00:47 2020
  DpkgHistoryLog:
   Start-Date: 2020-01-11  13:00:42
   Commandline: packagekit role='install-packages'
   Requested-By: alvaro (1000)
   Install: leocad:amd64 (19.07.1-1), libqt5concurrent5:amd64 
(5.12.4+dfsg-4ubuntu1, automatic), linux-image-5.3.0-26-generic:amd64 
(5.3.0-26.28, automatic), linux-headers-5.3.0-26:amd64 (5.3.0-26.28, 
automatic), linux-headers-5.3.0-26-generic:amd64 (5.3.0-26.28, automatic), 
linux-modules-extra-5.3.0-26-generic:amd64 (5.3.0-26.28, automatic), 
linux-modules-5.3.0-26-generic:amd64 (5.3.0-26.28, automatic)
   Upgrade: linux-headers-generic:amd64 (5.3.0.24.28, 5.3.0.26.30), 
linux-image-gen

[Kernel-packages] [Bug 1758545] Re: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer

[Naël]

I can also report the same behavior, on a Clevo laptop running Ubuntu
20.04 (development version), kernel 5.3.0-24. Clevo does not currently
provide BIOS updates for this model, and it is unlikely that they ever
will.

The error is as reported by the OP, and repeats several times per second
on the standard error, which makes it impossible to use virtual consoles
and terminals:

  [timestamp] pcieport :00:1d.4: AER: PCIe Bus Error: severity=Uncorrected 
(Non-Fatal), type=Transaction Layer, (Requester ID)
  [timestamp] pcieport :00:1d.4: AER:   device [8086:9db4] error 
status/mask=0010/0001
  [timestamp] pcieport :00:1d.4: AER:[20] UnsupReq   (First)
  [timestamp] pcieport :00:1d.4: AER:   TLP Header: 3400 0410 
 80008000

I have followed the explanation given here for a very similar PCI
Express bus error:

  https://unix.stackexchange.com/a/369090

to give the option pci=nommconf to the kernel, in order to disable
memory-mapping the configuration space of the PCI device, and instead
use the original method of accessing this space through I/O ports, if I
understand correctly. This option can be given at startup (press E in
GRUB) and then in /etc/default/grub for subsequent boots
(GRUB_CMDLINE_LINUX_DEFAULT="quiet splash pci=nommconf").

The option works for me in working around the issue, and can hopefully
work for other users whose hardware won't be supported with a BIOS
update.

>From what I understand, the problem could come from the particular PCI
Express device (an Intel PCIe NVMe M.2 SSD, 760p Series, according to
lshw), from the PCI Express root controller, or from the interaction
between them.

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

Title:
  PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction
  Layer

Status in linux package in Ubuntu:
  Incomplete
Status in linux package in Arch Linux:
  New

Bug description:
  My dmesg gets completely spammed with the following messages appearing over 
and over again, and this keep increasing the size of log file. I can use 
pci=noaer parameter to suppress these annoying messages, but not sure what this 
parameter do, will it make my pc lost some function.Is this a bug? below is 
part of the dmesg infomation
  
--

  [  397.076509] pcieport :00:01.1: PCIe Bus Error: severity=Uncorrected 
(Non-Fatal), type=Transaction Layer, id=0009(Requester ID)
  [  397.076517] pcieport :00:01.1:   device [1022:15d3] error 
status/mask=0010/0440
  [  397.076522] pcieport :00:01.1:[20] Unsupported Request(First)
  [  397.076526] pcieport :00:01.1:   TLP Header: 3400 01001f10 
 8c548c54
  [  397.081907] pcieport :00:01.1: PCIe Bus Error: severity=Uncorrected 
(Non-Fatal), type=Transaction Layer, id=0009(Requester ID)
  [  397.081914] pcieport :00:01.1:   device [1022:15d3] error 
status/mask=0010/0440
  [  397.081918] pcieport :00:01.1:[20] Unsupported Request(First)
  [  397.081923] pcieport :00:01.1:   TLP Header: 3400 01001f10 
 8c548c54
  [  398.983368] pcieport :00:01.1: PCIe Bus Error: severity=Uncorrected 
(Non-Fatal), type=Transaction Layer, id=0009(Requester ID)
  [  398.983376] pcieport :00:01.1:   device [1022:15d3] error 
status/mask=0010/0440
  [  398.983381] pcieport :00:01.1:[20] Unsupported Request(First)
  [  398.983385] pcieport :00:01.1:   TLP Header: 3400 01001f10 
 8c548c54
  [  398.984773] pcieport :00:01.1: PCIe Bus Error: severity=Uncorrected 
(Non-Fatal), type=Transaction Layer, id=0009(Requester ID)
  [  398.984779] pcieport :00:01.1:   device [1022:15d3] error 
status/mask=0010/0440
  [  398.984783] pcieport :00:01.1:[20] Unsupported Request(First)
  [  398.984788] pcieport :00:01.1:   TLP Header: 3400 01001f10 
 8c548c54
  [  398.994170] pcieport :00:01.1: PCIe Bus Error: severity=Uncorrected 
(Non-Fatal), type=Transaction Layer, id=0009(Requester ID)
  [  398.994176] pcieport :00:01.1:   device [1022:15d3] error 
status/mask=0010/0440
  [  398.994180] pcieport :00:01.1:[20] Unsupported Request(First)
  [  398.994185] pcieport :00:01.1:   TLP Header: 3400 01001f10 
 8c548c54
  [  399.333957] pcieport :00:01.1: PCIe Bus Error: severity=Uncorrected 
(Non-Fatal), type=Transaction Layer, id=0009(Requester ID)
  [  399.333964] pcieport :00:01.1:   device [1022:15d3] error 
status/mask=0010/0440
  [  399.333968] pcieport :00:01.1:[20] Unsupported Request(First)
  [  399.333973] pcieport :00:01.1:   TLP Header: 3400 01001f10 
 8c548c54
  [  399.339347] pcieport :00:01.1: PCIe Bus Error: severity=Uncorrected

[Kernel-packages] [Bug 1589008] Re: Bluetooth freezing video playback In Ubuntu/Kubuntu 16.04

[Adam Nielsen]

It turned out that there was a firmware bluetooth issue with my Broadcom
device. I found the issue with `dmesg | grep -i bluetooth ` and I could
fix it by simply downloading the missing firmware from
https://github.com/winterheart/broadcom-bt-firmware - now everything
works.

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

Title:
  Bluetooth freezing video playback In Ubuntu/Kubuntu 16.04

Status in linux package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  In 16.04 when a bluetooth audio device is connected it freezes video
  playback and also no sound comes from online audio only streams. Issue
  does not exist with a wired headset.

  This issue does not exist with 15.10. All updates have been installed
  on 16.04 including backports but they have not fixed the issue.

  It is not browser specific and not website specific.

  It is not hardware specific as it affects my laptop with an intel 7260
  card and my pc with an intel 8260 card.

  The issue exists on both ubuntu and kubuntu 16.04.

  I have reported it on the ubuntu support forums and after
  investigation a moderator noticed changed in the kernel from 4.4 and
  4.2 that may becausing the issue and asked me to file a bug report.

  The ubuntu forum thread can be found here.
  http://ubuntuforums.org/showthread.php?t=2326672

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-23-generic 4.4.0-23.41
  ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10
  Uname: Linux 4.4.0-23-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  stephen1435 F pulseaudio
   /dev/snd/controlC0:  stephen1435 F pulseaudio
  CurrentDesktop: KDE
  Date: Fri Jun  3 23:50:00 2016
  HibernationDevice: RESUME=UUID=78e7aefc-d517-4c58-836f-a90f0b6017c6
  InstallationDate: Installed on 2016-05-06 (28 days ago)
  InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: MSI MS-7978
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-23-generic.efi.signed 
root=UUID=bccf2ca7-4e23-412a-ba10-7a3f915270dd ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-23-generic N/A
   linux-backports-modules-4.4.0-23-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-06-03 (0 days ago)
  dmi.bios.date: 05/16/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: C.60
  dmi.board.asset.tag: Default string
  dmi.board.name: H170 GAMING M3 (MS-7978)
  dmi.board.vendor: MSI
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrC.60:bd05/16/2016:svnMSI:pnMS-7978:pvr2.0:rvnMSI:rnH170GAMINGM3(MS-7978):rvr2.0:cvnMSI:ct3:cvr2.0:
  dmi.product.name: MS-7978
  dmi.product.version: 2.0
  dmi.sys.vendor: MSI

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1589008/+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 1685442] Re: Errors: flip_done timed out during boot-up; slow boot

[Mantas Kriaučiūnas]

** Tags added: bionic

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

Title:
  Errors:  flip_done timed out  during boot-up; slow boot

Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in linux package in Baltix:
  In Progress

Bug description:
  I had been running Ubuntu 16.04 LTS on many laptop computers
  (especially Dell D620, D630, E6400) with no problem.

  I created a Live USB with Ubuntu 16.04.2 LTS and tried it on a Dell
  D630.  It was very slow to boot up (about 90 seconds) as opposed to
  the 30-45 seconds it usually takes. For a few seconds there were error
  messages that included the phrase "flip_done timed out".

  When the Ubuntu desktop appeared, the mouse cursor hung for a while,
  but then came back to life. I didn't do much testing from there.  I
  did a Live session with the 16.04.2 LTS  on a different D630 laptop,
  and the same problem occureed.

  I Googled the problem, and found several hits.
  -
  On an Arch forum, someone reported the problem on a Dell D630, like mine. It 
also occured on other laptops:
  https://bbs.archlinux.org/viewtopic.php?id=218581

  The suggestion was that the bug was related to kernel version 4.8.x
  and the 965GM chipset, which is what the D630 has.

  So I tried Ubuntu Mate 16.04.2 on a Dell D620 (with a 945GM chipset) and the 
problem DID NOT occur.
  ---
  For a similar boot-up problem, Ubuntu Forum suggested going back to an 
earlier version of Ubuntu.
  https://ubuntuforums.org/showthread.php?t=2348892

  I tried Ubuntu Mate 16.04.1 (with the 4.4.0-31-generic kernel), and
  the problem did NOT occur.

  So I'm solving the problem for myself by using Ubuntu Mate 16.04.1 LTS rather 
than 16.04.2.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  test   2194 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=a754e82c-72cb-44d1-9fa4-58777803b24d
  InstallationDate: Installed on 2017-07-19 (0 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
  MachineType: Dell Inc. Latitude D630
  Package: linux (not installed)
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-36-generic 
root=UUID=2a3b3861-8ac7-41e0-86cf-999434bd112e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-36-generic N/A
   linux-backports-modules-4.8.0-36-generic  N/A
   linux-firmware1.157.8
  Tags:  xenial
  Uname: Linux 4.8.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 06/04/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A19
  dmi.board.name: 0KU184
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA19:bd06/04/2013:svnDellInc.:pnLatitudeD630:pvr:rvnDellInc.:rn0KU184:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Latitude D630
  dmi.sys.vendor: Dell Inc.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  test   2194 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=a754e82c-72cb-44d1-9fa4-58777803b24d
  InstallationDate: Installed on 2017-07-19 (0 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
  MachineType: Dell Inc. Latitude D630
  Package: linux (not installed)
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-36-generic 
root=UUID=2a3b3861-8ac7-41e0-86cf-999434bd112e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-36-generic N/A
   linux-backports-modules-4.8.0-36-generic  N/A
   linux-firmware 

[Kernel-packages] [Bug 1589008] Re: Bluetooth freezing video playback In Ubuntu/Kubuntu 16.04

[Adam Nielsen]

I can confirm this bug in 18.04. I had the issue a couple of weeks ago,
then everything suddenly worked, and now I have the problem again. I
restarted my pc multiple times, reconnected to my usb-bluetooth adapter,
tried every slot, rebootet bluetooth device, reinstalled headset driver,
but I don't get it to work again :/

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

Title:
  Bluetooth freezing video playback In Ubuntu/Kubuntu 16.04

Status in linux package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  In 16.04 when a bluetooth audio device is connected it freezes video
  playback and also no sound comes from online audio only streams. Issue
  does not exist with a wired headset.

  This issue does not exist with 15.10. All updates have been installed
  on 16.04 including backports but they have not fixed the issue.

  It is not browser specific and not website specific.

  It is not hardware specific as it affects my laptop with an intel 7260
  card and my pc with an intel 8260 card.

  The issue exists on both ubuntu and kubuntu 16.04.

  I have reported it on the ubuntu support forums and after
  investigation a moderator noticed changed in the kernel from 4.4 and
  4.2 that may becausing the issue and asked me to file a bug report.

  The ubuntu forum thread can be found here.
  http://ubuntuforums.org/showthread.php?t=2326672

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-23-generic 4.4.0-23.41
  ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10
  Uname: Linux 4.4.0-23-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  stephen1435 F pulseaudio
   /dev/snd/controlC0:  stephen1435 F pulseaudio
  CurrentDesktop: KDE
  Date: Fri Jun  3 23:50:00 2016
  HibernationDevice: RESUME=UUID=78e7aefc-d517-4c58-836f-a90f0b6017c6
  InstallationDate: Installed on 2016-05-06 (28 days ago)
  InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: MSI MS-7978
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-23-generic.efi.signed 
root=UUID=bccf2ca7-4e23-412a-ba10-7a3f915270dd ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-23-generic N/A
   linux-backports-modules-4.4.0-23-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-06-03 (0 days ago)
  dmi.bios.date: 05/16/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: C.60
  dmi.board.asset.tag: Default string
  dmi.board.name: H170 GAMING M3 (MS-7978)
  dmi.board.vendor: MSI
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrC.60:bd05/16/2016:svnMSI:pnMS-7978:pvr2.0:rvnMSI:rnH170GAMINGM3(MS-7978):rvr2.0:cvnMSI:ct3:cvr2.0:
  dmi.product.name: MS-7978
  dmi.product.version: 2.0
  dmi.sys.vendor: MSI

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