[Kernel-packages] [Bug 1955344] Re: touchpad not detetcted in lenovo ideapad slim 3 in ubuntu

2021-12-25 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: linux-signed-hwe-5.11 (Ubuntu)
   Status: New => Confirmed

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

Title:
  touchpad not detetcted in lenovo ideapad slim 3 in ubuntu

Status in linux-signed-hwe-5.11 package in Ubuntu:
  Confirmed

Bug description:
  Touchpad is not detected in lenovo ideapad slim 3 in ubuntu which I' using in 
dual boot with windows 10. However external mouse is working. Below are the 
details of os installed in my PC.
  1)
  Description:  Ubuntu 20.04.3 LTS
  Release:  20.04
  2)
  apt-cache policy mousepad
  mousepad:
Installed: 0.4.2-1
Candidate: 0.4.2-1
Version table:
   *** 0.4.2-1 500
  500 http://in.archive.ubuntu.com/ubuntu focal/universe amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.11.0-43-generic 5.11.0-43.47~20.04.2
  ProcVersionSignature: Ubuntu 5.11.0-43.47~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-43-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Dec 19 20:16:23 2021
  InstallationDate: Installed on 2021-11-14 (35 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  SourcePackage: linux-signed-hwe-5.11
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.11/+bug/1955344/+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 1955754] [NEW] No WiFi hardware detected in kernel 5.11

2021-12-25 Thread BlackDalek
Public bug reported:

I have a bad branch kernel installed 5.12.5-051205-generic I need to get 
rid of it and change to kernel version 5.11.0-43-generic.
However, I have no WiFi hardware detected when booted into 5.11 kernel from 
grub menu.
I can ONLY get my WiFi hardware to detect in kernel 5.12
I only have network access through ethernet cable while booted into kernel 5.11

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.11.0-43-generic 5.11.0-43.47~20.04.2
ProcVersionSignature: Ubuntu 5.11.0-43.47~20.04.2-generic 5.11.22
Uname: Linux 5.11.0-43-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sun Dec 26 15:08:13 2021
InstallationDate: Installed on 2021-09-25 (91 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
SourcePackage: linux-signed-hwe-5.11
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: linux-signed-hwe-5.11 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal

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

Title:
  No WiFi hardware detected in kernel 5.11

Status in linux-signed-hwe-5.11 package in Ubuntu:
  New

Bug description:
  I have a bad branch kernel installed 5.12.5-051205-generic I need to get 
rid of it and change to kernel version 5.11.0-43-generic.
  However, I have no WiFi hardware detected when booted into 5.11 kernel from 
grub menu.
  I can ONLY get my WiFi hardware to detect in kernel 5.12
  I only have network access through ethernet cable while booted into kernel 
5.11

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.11.0-43-generic 5.11.0-43.47~20.04.2
  ProcVersionSignature: Ubuntu 5.11.0-43.47~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-43-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Dec 26 15:08:13 2021
  InstallationDate: Installed on 2021-09-25 (91 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  SourcePackage: linux-signed-hwe-5.11
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.11/+bug/1955754/+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 1948960] Re: nvidia-driver-XXX-server packaging: Demote nvidia-settings to "Suggests"

2021-12-25 Thread David North
** Changed in: nvidia-graphics-drivers-418-server (Ubuntu)
   Status: New => In Progress

** Changed in: nvidia-graphics-drivers-418-server (Ubuntu)
 Assignee: (unassigned) => David North (nort85)

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

Title:
  nvidia-driver-XXX-server packaging: Demote nvidia-settings to
  "Suggests"

Status in nvidia-graphics-drivers-418-server package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
  Fix Committed
Status in nvidia-graphics-drivers-460-server package in Ubuntu:
  Fix Committed
Status in nvidia-graphics-drivers-470-server package in Ubuntu:
  Fix Committed
Status in nvidia-graphics-drivers-418-server source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-450-server source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-460-server source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-470-server source package in Bionic:
  Fix Committed
Status in nvidia-graphics-drivers-418-server source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-450-server source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-460-server source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-470-server source package in Focal:
  Fix Committed
Status in nvidia-graphics-drivers-418-server source package in Hirsute:
  Fix Committed
Status in nvidia-graphics-drivers-450-server source package in Hirsute:
  Fix Committed
Status in nvidia-graphics-drivers-460-server source package in Hirsute:
  Fix Committed
Status in nvidia-graphics-drivers-470-server source package in Hirsute:
  Fix Committed
Status in nvidia-graphics-drivers-418-server source package in Impish:
  Fix Committed
Status in nvidia-graphics-drivers-450-server source package in Impish:
  Fix Committed
Status in nvidia-graphics-drivers-460-server source package in Impish:
  Fix Committed
Status in nvidia-graphics-drivers-470-server source package in Impish:
  Fix Committed

Bug description:
  [Impact]
  This release demotes nvidia-settings and nvidia-prime from "Recommends"
  to "Suggests" dependencies for the -server NVIDIA drivers, for the following 
reasons:

  - The Ubuntu default behavior is to install "recommended" packages.
  - The -server packages are associated with TRDs, which are generally used on 
Tesla GPUs, which are generally used on servers.
  - nvidia-settings pulls in many GUI bits which are generally not relevant to 
servers.

  
  [Test Case]
  Installing the main metapackage should be possible without pulling in
  the two above mentioned dependencies.

  [Regression Potential]
  Low, as no change other than dropping the two dependencies is involved.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418-server/+bug/1948960/+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 1637709] Re: Lenovo Ideapad 100 webcam always on

2021-12-25 Thread Stefan Mihajlovski
This seems to be a problem on all 100-15IBD laptops and most people just
run guvcview or some kind of app that accesses the camera and the light
stops being on but is there any permanent solution because it's annoying
to constantly do that

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

Title:
  Lenovo Ideapad 100 webcam always on

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a lenovo Ideapad 100 model 15IBD 80 QQ
  The webcam led it stays always on from when i start the pc, it stops only, it 
seems, when i open some software that has a working with it in some way...like  
software or even google chrome (i think thanks to hangouts)
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ale1361 F pulseaudio
   /dev/snd/controlC1:  ale1361 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=39a50866-e309-4acc-b70f-19f745ab0c9e
  InstallationDate: Installed on 2016-10-22 (6 days ago)
  InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 80QQ
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=it
   TERM=xterm
   PATH=(custom, no user)
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic.efi.signed 
root=UUID=86cd71e4-1562-488f-afa6-290f354d4f7a ro
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  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.4.0-45-generic N/A
   linux-backports-modules-4.4.0-45-generic  N/A
   linux-firmware1.157.4
  Tags:  xenial
  Uname: Linux 4.4.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 08/12/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: E0CN61WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Nano 5B6
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 100-15IBD
  dmi.modalias: 
dmi:bvnLENOVO:bvrE0CN61WW:bd08/12/2016:svnLENOVO:pn80QQ:pvrLenovoideapad100-15IBD:rvnLENOVO:rnNano5B6:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoideapad100-15IBD:
  dmi.product.name: 80QQ
  dmi.product.version: Lenovo ideapad 100-15IBD
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1637709/+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 1952818] Re: Fails to suspend

2021-12-25 Thread brad haack
I think this has been fixed by updating the OS to Xubuntu 21.10 (&
associated kernel) & the Bios to 1.3.0.   I also had to keep the sleep
mode in s2idle

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

Title:
  Fails to suspend

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Occasionally my laptop fails to suspend with a lid close.  I always get this 
message in syslog or kernal.log:
  kernel: [ 1947.276485] ACPI: button: The lid device is not compliant to 
SW_LID.
  But it usually continues and suspends successfully.  This time there was 
nothing in syslog, kern.log, or dmesg after the SW_LID message.
  It also never locks the screen either, & this time there was a msg on the 
screen after I opened it up about failing to lock the screen.

  Description:  Ubuntu 21.04
  Release:  21.04

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: linux-image-5.11.0-41-generic 5.11.0-41.45
  ProcVersionSignature: Ubuntu 5.11.0-41.45-generic 5.11.22
  Uname: Linux 5.11.0-41-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  brad   1280 F pulseaudio
  CasperMD5CheckResult: unknown
  Date: Tue Nov 30 18:51:44 2021
  InstallationDate: Installed on 2021-11-20 (10 days ago)
  InstallationMedia: Xubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210819.1)
  MachineType: Dell Inc. Vostro 15 7510
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-41-generic 
root=UUID=a07e9fdf-df33-4257-913f-9fe9f42e08a9 ro quiet splash 
mem_sleep_default=deep vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-41-generic N/A
   linux-backports-modules-5.11.0-41-generic  N/A
   linux-firmware 1.197.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to hirsute on 2021-11-29 (1 days ago)
  dmi.bios.date: 10/14/2021
  dmi.bios.release: 1.2
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.1
  dmi.board.name: 0J0MWF
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.1:bd10/14/2021:br1.2:svnDellInc.:pnVostro157510:pvr:sku0A82:rvnDellInc.:rn0J0MWF:rvrA01:cvnDellInc.:ct10:cvr:
  dmi.product.family: Vostro
  dmi.product.name: Vostro 15 7510
  dmi.product.sku: 0A82
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1952818/+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 1906476] Re: PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, &zp->z_sa_hdl)) failed

2021-12-25 Thread mog
It would be real nice if the ubuntu livecd iso for usb booting could
also get the fixed kernel.

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

Title:
  PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 ==
  sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED,
  &zp->z_sa_hdl)) failed

Status in Native ZFS for Linux:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux-raspi package in Ubuntu:
  Confirmed
Status in ubuntu-release-upgrader package in Ubuntu:
  Confirmed
Status in zfs-linux package in Ubuntu:
  Fix Released
Status in linux source package in Impish:
  Fix Released
Status in linux-raspi source package in Impish:
  Fix Released
Status in ubuntu-release-upgrader source package in Impish:
  Confirmed
Status in zfs-linux source package in Impish:
  Fix Released

Bug description:
  Since today while running Ubuntu 21.04 Hirsute I started getting a ZFS
  panic in the kernel log which was also hanging Disk I/O for all
  Chrome/Electron Apps.

  I have narrowed down a few important notes:
  - It does not happen with module version 0.8.4-1ubuntu11 built and included 
with 5.8.0-29-generic

  - It was happening when using zfs-dkms 0.8.4-1ubuntu16 built with DKMS
  on the same kernel and also on 5.8.18-acso (a custom kernel).

  - For whatever reason multiple Chrome/Electron apps were affected,
  specifically Discord, Chrome and Mattermost. In all cases they seem
  (but I was unable to strace the processes so it was a bit hard ot
  confirm 100% but by deduction from /proc/PID/fd and the hanging ls)
  they seem hung trying to open files in their 'Cache' directory, e.g.
  ~/.cache/google-chrome/Default/Cache and ~/.config/Mattermost/Cache ..
  while the issue was going on I could not list that directory either
  "ls" would just hang.

  - Once I removed zfs-dkms only to revert to the kernel built-in
  version it immediately worked without changing anything, removing
  files, etc.

  - It happened over multiple reboots and kernels every time, all my
  Chrome apps weren't working but for whatever reason nothing else
  seemed affected.

  - It would log a series of spl_panic dumps into kern.log that look like this:
  Dec  2 12:36:42 optane kernel: [   72.857033] VERIFY(0 == 
sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, &zp->z_sa_hdl)) 
failed
  Dec  2 12:36:42 optane kernel: [   72.857036] PANIC at 
zfs_znode.c:335:zfs_znode_sa_init()

  I could only find one other google reference to this issue, with 2 other 
users reporting the same error but on 20.04 here:
  https://github.com/openzfs/zfs/issues/10971

  - I was not experiencing the issue on 0.8.4-1ubuntu14 and fairly sure
  it was working on 0.8.4-1ubuntu15 but broken after upgrade to
  0.8.4-1ubuntu16. I will reinstall those zfs-dkms versions to verify
  that.

  There were a few originating call stacks but the first one I hit was

  Call Trace:
   dump_stack+0x74/0x95
   spl_dumpstack+0x29/0x2b [spl]
   spl_panic+0xd4/0xfc [spl]
   ? sa_cache_constructor+0x27/0x50 [zfs]
   ? _cond_resched+0x19/0x40
   ? mutex_lock+0x12/0x40
   ? dmu_buf_set_user_ie+0x54/0x80 [zfs]
   zfs_znode_sa_init+0xe0/0xf0 [zfs]
   zfs_znode_alloc+0x101/0x700 [zfs]
   ? arc_buf_fill+0x270/0xd30 [zfs]
   ? __cv_init+0x42/0x60 [spl]
   ? dnode_cons+0x28f/0x2a0 [zfs]
   ? _cond_resched+0x19/0x40
   ? _cond_resched+0x19/0x40
   ? mutex_lock+0x12/0x40
   ? aggsum_add+0x153/0x170 [zfs]
   ? spl_kmem_alloc_impl+0xd8/0x110 [spl]
   ? arc_space_consume+0x54/0xe0 [zfs]
   ? dbuf_read+0x4a0/0xb50 [zfs]
   ? _cond_resched+0x19/0x40
   ? mutex_lock+0x12/0x40
   ? dnode_rele_and_unlock+0x5a/0xc0 [zfs]
   ? _cond_resched+0x19/0x40
   ? mutex_lock+0x12/0x40
   ? dmu_object_info_from_dnode+0x84/0xb0 [zfs]
   zfs_zget+0x1c3/0x270 [zfs]
   ? dmu_buf_rele+0x3a/0x40 [zfs]
   zfs_dirent_lock+0x349/0x680 [zfs]
   zfs_dirlook+0x90/0x2a0 [zfs]
   ? zfs_zaccess+0x10c/0x480 [zfs]
   zfs_lookup+0x202/0x3b0 [zfs]
   zpl_lookup+0xca/0x1e0 [zfs]
   path_openat+0x6a2/0xfe0
   do_filp_open+0x9b/0x110
   ? __check_object_size+0xdb/0x1b0
   ? __alloc_fd+0x46/0x170
   do_sys_openat2+0x217/0x2d0
   ? do_sys_openat2+0x217/0x2d0
   do_sys_open+0x59/0x80
   __x64_sys_openat+0x20/0x30

To manage notifications about this bug go to:
https://bugs.launchpad.net/zfs/+bug/1906476/+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 1955570] Re: package linux-firmware 1.187.23 failed to install/upgrade: unable to open '/lib/firmware/matrox/g200_warp.fw.dpkg-new': Operation not permitted

2021-12-25 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  package linux-firmware 1.187.23 failed to install/upgrade: unable to
  open '/lib/firmware/matrox/g200_warp.fw.dpkg-new': Operation not
  permitted

Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  Occurs everytime when google-chrome v. 96.0.4664.110 starts

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: linux-firmware 1.187.23
  ProcVersionSignature: Ubuntu 5.11.0-43.47~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-43-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  brigitte886 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Tue Dec 21 11:47:24 2021
  Dependencies:
   
  DuplicateSignature:
   package:linux-firmware:1.187.23
   Unpacking linux-firmware (1.187.23) over (1.187.20) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-X3YTyW/17-linux-firmware_1.187.23_all.deb (--unpack):
unable to open '/lib/firmware/matrox/g200_warp.fw.dpkg-new': Operation not 
permitted
  ErrorMessage: unable to open '/lib/firmware/matrox/g200_warp.fw.dpkg-new': 
Operation not permitted
  InstallationDate: Installed on 2021-12-07 (15 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0408:a061 Quanta Computer, Inc. HD User Facing
   Bus 001 Device 002: ID 046d:c542 Logitech, Inc. Wireless Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 1M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M
   |__ Port 4: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
   |__ Port 5: Dev 3, If 0, Class=Video, Driver=uvcvideo, 480M
   |__ Port 5: Dev 3, If 1, Class=Video, Driver=uvcvideo, 480M
  MachineType: Acer Aspire A515-54G
  PackageArchitecture: all
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-43-generic 
root=UUID=2f59b1ec-0da1-465c-9784-ad749337cd68 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.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions: grub-pc 2.04-1ubuntu26.13
  SourcePackage: linux-firmware
  Title: package linux-firmware 1.187.23 failed to install/upgrade: unable to 
open '/lib/firmware/matrox/g200_warp.fw.dpkg-new': Operation not permitted
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/03/2020
  dmi.bios.release: 1.21
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.21
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Doc_WC
  dmi.board.vendor: CML
  dmi.board.version: V1.21
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 1.8
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.21:bd07/03/2020:br1.21:efr1.8:svnAcer:pnAspireA515-54G:pvrV1.21:sku:rvnCML:rnDoc_WC:rvrV1.21:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.family: Aspire 5
  dmi.product.name: Aspire A515-54G
  dmi.product.sku: 
  dmi.product.version: V1.21
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1955570/+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 1002952] Re: [meta-bug] Invalid extra "Digital output S/PDIF" device for USB cards

2021-12-25 Thread Edle8
I have the same issue with the following USB devices:

"Sennheiser SC60 for Lync" (USB headset)
"Jabra SPEAK 410 USB" (conference speakerphone)
"HD Pro Webcam C920" (webcam with microphone)

I confirm that the workaround is still valid for the mentioned devices.

https://alsa-project.org/db/?f=d4596d4503525e4b1c998fd17d386c73adf8a9a9

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

Title:
  [meta-bug] Invalid extra "Digital output S/PDIF" device for USB cards

Status in alsa-lib package in Ubuntu:
  Confirmed

Bug description:
  === Read me first ===

  = Symptom =

  If you have a USB headset, or other USB device that does not have any
  S/PDIF output, but yet sometimes there is an extra device called
  "Digital Output (S/PDIF)" for that device, you're suffering from this
  bug.

  This bug is only for USB devices - if you have an invalid digital
  output for some other type of device, please file a separate bug
  instead.

  = Workaround =

  If you're affected, please try this workaround:

  first check the output of "aplay -l" (lowercase L), or "arecord -l" if
  it's an input device, and grab the first of two name in brackets:

  Example:
  card 3: Headset [Sennheiser USB Headset], device 0: USB Audio [USB Audio]
  here grab the name "Sennheiser USB Headset". Now edit the file 
/usr/share/alsa/cards/USB-Audio.conf (requires root permissions)
  Around line 40, you will find a line saying "Logitech USB Headset" 999
  Add a new line after this line, so that there is now a new line called
  "Sennheiser USB Headset" 999
  (including quotes, and replace "Sennheiser USB Headset" with whatever your 
particular card was named.)

  Save the file and reboot your computer for the changes to take effect.

  = Already known devices =

  These card names are already in 12.04:

  "Blue Snowball"
  "Logitech USB Headset"
  "Logitech Web Camera"

  These card names are on their way into 12.04:

  "Logitech Speaker Lapdesk N700"
  "Logitech Wireless Headset"
  "Plantronics USB Headset"
  "Sennheiser USB headset"

  If you have one of the above four, please help out by testing the
  proposed repository and report back in bug 987163.

  If your name is not listed above, please add a comment to this bug,
  including your alsa-info: https://wiki.ubuntu.com/Audio/AlsaInfo -
  they will be collected for a SRU later on, or at least make it into
  the next release of Ubuntu.

  Thanks!

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