[Kernel-packages] [Bug 2016388] Re: Kernel Panic on shutdown / reboot on NUC8I3BEH

2024-04-15 Thread b
Confirmed on 5.15.0-102

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

Title:
  Kernel Panic on shutdown / reboot on NUC8I3BEH

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Kernel 5.4.0-146 panics on power-down (e.g. shutdown -P now)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-146-generic 5.4.0-146.163
  ProcVersionSignature: Ubuntu 5.4.0-144.161-generic 5.4.229
  Uname: Linux 5.4.0-144-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.26
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bbogart1051 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Sat Apr 15 09:07:33 2023
  InstallationDate: Installed on 2019-02-09 (1526 days ago)
  InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Intel(R) Client Systems NUC8i3BEH
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-144-generic 
root=UUID=9c982b36-8142-4719-810a-e06f81cab223 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-144-generic N/A
   linux-backports-modules-5.4.0-144-generic  N/A
   linux-firmware 1.187.38
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2022-06-30 (289 days ago)
  dmi.bios.date: 02/14/2023
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BECFL357.86A.0092.2023.0214.1114
  dmi.board.name: NUC8BEB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: J72693-304
  dmi.chassis.type: 3
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBECFL357.86A.0092.2023.0214.1114:bd02/14/2023:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-303:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-304:cvnIntelCorporation:ct3:cvr2.0:
  dmi.product.family: Intel NUC
  dmi.product.name: NUC8i3BEH
  dmi.product.sku: BOXNUC8i3BEH
  dmi.product.version: J72753-303
  dmi.sys.vendor: Intel(R) Client Systems

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016388/+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 2016388] Re: Kernel Panic on shutdown / reboot on NUC8I3BEH

2024-03-25 Thread b
Confirmed on 5.15.0-100 and 5.15.0-101

** Attachment added: "Photo of panic call trace for 5.15.0-101"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016388/+attachment/5759323/+files/20240325_091737.jpg

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

Title:
  Kernel Panic on shutdown / reboot on NUC8I3BEH

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Kernel 5.4.0-146 panics on power-down (e.g. shutdown -P now)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-146-generic 5.4.0-146.163
  ProcVersionSignature: Ubuntu 5.4.0-144.161-generic 5.4.229
  Uname: Linux 5.4.0-144-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.26
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bbogart1051 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Sat Apr 15 09:07:33 2023
  InstallationDate: Installed on 2019-02-09 (1526 days ago)
  InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Intel(R) Client Systems NUC8i3BEH
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-144-generic 
root=UUID=9c982b36-8142-4719-810a-e06f81cab223 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-144-generic N/A
   linux-backports-modules-5.4.0-144-generic  N/A
   linux-firmware 1.187.38
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2022-06-30 (289 days ago)
  dmi.bios.date: 02/14/2023
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BECFL357.86A.0092.2023.0214.1114
  dmi.board.name: NUC8BEB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: J72693-304
  dmi.chassis.type: 3
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBECFL357.86A.0092.2023.0214.1114:bd02/14/2023:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-303:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-304:cvnIntelCorporation:ct3:cvr2.0:
  dmi.product.family: Intel NUC
  dmi.product.name: NUC8i3BEH
  dmi.product.sku: BOXNUC8i3BEH
  dmi.product.version: J72753-303
  dmi.sys.vendor: Intel(R) Client Systems

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016388/+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 2016388] Re: Kernel Panic on shutdown / reboot on NUC8I3BEH

2024-03-15 Thread b
** Attachment added: "Kernel panic"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016388/+attachment/5756269/+files/20240315_090551.jpg

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

Title:
  Kernel Panic on shutdown / reboot on NUC8I3BEH

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Kernel 5.4.0-146 panics on power-down (e.g. shutdown -P now)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-146-generic 5.4.0-146.163
  ProcVersionSignature: Ubuntu 5.4.0-144.161-generic 5.4.229
  Uname: Linux 5.4.0-144-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.26
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bbogart1051 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Sat Apr 15 09:07:33 2023
  InstallationDate: Installed on 2019-02-09 (1526 days ago)
  InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Intel(R) Client Systems NUC8i3BEH
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-144-generic 
root=UUID=9c982b36-8142-4719-810a-e06f81cab223 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-144-generic N/A
   linux-backports-modules-5.4.0-144-generic  N/A
   linux-firmware 1.187.38
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2022-06-30 (289 days ago)
  dmi.bios.date: 02/14/2023
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BECFL357.86A.0092.2023.0214.1114
  dmi.board.name: NUC8BEB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: J72693-304
  dmi.chassis.type: 3
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBECFL357.86A.0092.2023.0214.1114:bd02/14/2023:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-303:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-304:cvnIntelCorporation:ct3:cvr2.0:
  dmi.product.family: Intel NUC
  dmi.product.name: NUC8i3BEH
  dmi.product.sku: BOXNUC8i3BEH
  dmi.product.version: J72753-303
  dmi.sys.vendor: Intel(R) Client Systems

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016388/+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 2016388] Re: Kernel Panic on shutdown / reboot on NUC8I3BEH

2024-02-19 Thread b
confirmed on 5.15.0-92

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

Title:
  Kernel Panic on shutdown / reboot on NUC8I3BEH

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Kernel 5.4.0-146 panics on power-down (e.g. shutdown -P now)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-146-generic 5.4.0-146.163
  ProcVersionSignature: Ubuntu 5.4.0-144.161-generic 5.4.229
  Uname: Linux 5.4.0-144-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.26
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bbogart1051 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Sat Apr 15 09:07:33 2023
  InstallationDate: Installed on 2019-02-09 (1526 days ago)
  InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Intel(R) Client Systems NUC8i3BEH
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-144-generic 
root=UUID=9c982b36-8142-4719-810a-e06f81cab223 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-144-generic N/A
   linux-backports-modules-5.4.0-144-generic  N/A
   linux-firmware 1.187.38
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2022-06-30 (289 days ago)
  dmi.bios.date: 02/14/2023
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BECFL357.86A.0092.2023.0214.1114
  dmi.board.name: NUC8BEB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: J72693-304
  dmi.chassis.type: 3
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBECFL357.86A.0092.2023.0214.1114:bd02/14/2023:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-303:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-304:cvnIntelCorporation:ct3:cvr2.0:
  dmi.product.family: Intel NUC
  dmi.product.name: NUC8i3BEH
  dmi.product.sku: BOXNUC8i3BEH
  dmi.product.version: J72753-303
  dmi.sys.vendor: Intel(R) Client Systems

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016388/+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 2016388] Re: Kernel Panic on shutdown / reboot on NUC8I3BEH

2024-02-07 Thread b
Issue confirmed on 5.4.0-170.

** Attachment added: "20240207_103433.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016388/+attachment/5745140/+files/20240207_103433.jpg

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

Title:
  Kernel Panic on shutdown / reboot on NUC8I3BEH

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Kernel 5.4.0-146 panics on power-down (e.g. shutdown -P now)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-146-generic 5.4.0-146.163
  ProcVersionSignature: Ubuntu 5.4.0-144.161-generic 5.4.229
  Uname: Linux 5.4.0-144-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.26
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bbogart1051 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Sat Apr 15 09:07:33 2023
  InstallationDate: Installed on 2019-02-09 (1526 days ago)
  InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Intel(R) Client Systems NUC8i3BEH
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-144-generic 
root=UUID=9c982b36-8142-4719-810a-e06f81cab223 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-144-generic N/A
   linux-backports-modules-5.4.0-144-generic  N/A
   linux-firmware 1.187.38
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2022-06-30 (289 days ago)
  dmi.bios.date: 02/14/2023
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BECFL357.86A.0092.2023.0214.1114
  dmi.board.name: NUC8BEB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: J72693-304
  dmi.chassis.type: 3
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBECFL357.86A.0092.2023.0214.1114:bd02/14/2023:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-303:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-304:cvnIntelCorporation:ct3:cvr2.0:
  dmi.product.family: Intel NUC
  dmi.product.name: NUC8i3BEH
  dmi.product.sku: BOXNUC8i3BEH
  dmi.product.version: J72753-303
  dmi.sys.vendor: Intel(R) Client Systems

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016388/+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 2000947] Re: UVC Quanta 0408:4035 camera PROBLEM

2024-01-15 Thread Devika B S
@Giuliano

Thanks a lot for the update. It resolved the camera issues.

BR 
Devika

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

Title:
  UVC  Quanta 0408:4035  camera PROBLEM

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I bought a Acer Nitro 5 AN517-55 with Quanta ACER HD User Facing',
  USB 0408:4035.

  The camera is reported to have problems by many users:  
  https://linux-hardware.org/?id=usb:0408-4035
  The uvc camera Quanta 0408:4035 does not work with ubuntu 22,04. the camera 
is “recongized” but fails installation.

  My console commands report similar info to other users: 
  
https://unix.stackexchange.com/questions/723504/integrated-camera-not-detected-working-on-acer-nitro-5-an515-58

  
  PROPOSED SOLUTION 
  I got in contact with laurent.pinch...@ideasonboard.com   and with 
riba...@chromium.org , and subscribed to https://www.linuxtv.org/lists. And  
me...@vger.kernel.org mailinglist.

  Laurent proposed me a fix and I modified the 5,15 uvc_driver.c
  version, and loaded it on github

  https://github.com/Giuliano69/uvc_driver-for-Quanta-HD-User-
  Facing-0x0408-0x4035-/blob/main/uvc_driver.c

  I offered to test the fix, so I tried to compile the module with the
  new source.

  COMPILING PROBLEMS
  I’m running **Ubuntu 22.04.1 LTS, with kernel 
  giuliano@Astra2A:/usr/src$ cat /proc/version_signature
  Ubuntu 5.15.0-56.62-generic 5.15.64

  BUT  the linux-source that I found installed seems to be different
  tgiuliano@Astra2A:/usr/src$ ls -al linux-so*
  lrwxrwxrwx 1 root root 47 nov 22 16:08 linux-source-5.15.0.tar.bz2 -> 
linux-source-5.15.0/linux-source-5.15.0.tar.bz2

  I expanded  the tar file, configured the IDE and compiled without error  any 
errors… 
  I manually copied the uvcvideo.ko in 
  /lib/modules/5.15.0-56-
  sudo cp…...

  then tryed to intall the new uvcvideo.ko module
  sudo rmmod uvcvideo && sudo modprobe uvcvideo

  BUT… IT FAILS
  giuliano@Astra2A:~$ sudo rmmod uvcvideo && sudo modprobe uvcvideo
  modprobe: ERROR: could not insert 'uvcvideo': Exec format error

  and dmesg shows
  [25961.151982] usbcore: registered new interface driver uvcvideo
  [26323.125534] usbcore: deregistering interface driver uvcvideo
  [26323.189294] uvcvideo: disagrees about version of symbol module_layout


  These are the TWO modinfo from the old and new uvcvideo modules
  https://pastebin.com/tSj8Exm6
  Basically
  OLD module: vermagic: 5.15.0-56-generic SMP mod_unload modversions 
  NEW module: vermagic: 5.15.64 SMP mod_unload modversions


  -kindly ASK

  HOW can FORCE the uvcdriver.c to match mi kernel version ?
  Have I got OTHER ways to make the kernel module I’m compiling, match my 
running system ?

  I would like to test the module so to confirm the patch and let it
  enter the kernel main stream...

  
  BR
  Giuliano

  PS
  btw…. to allow Eclipse to compile the kernel, I had to pass this commands
  scripts/config --disable CONFIG_SYSTEM_REVOCATION_KEYS
  scripts/config --disable SYSTEM_REVOCATION_KEYS
  scripts/config --disable SYSTEM_TRUSTED_KEYS

  hope that this does not affect the module layout & checking
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  giuliano   2142 F pulseaudio
   /dev/snd/pcmC1D0p:   giuliano   2142 F...m pulseaudio
   /dev/snd/controlC0:  giuliano   2142 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-11-03 (66 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: Acer Nitro AN517-55
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-57-generic 
root=UUID=f07e25f9-07e7-4a29-a15e-f481aa0ee0f2 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-57.63-generic 5.15.74
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-57-generic N/A
   linux-backports-modules-5.15.0-57-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.9
  Tags:  jammy
  Uname: Linux 5.15.0-57-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo wireshark
  _MarkForUpload: True
  dmi.bios.date: 04/20/2022
  dmi.bios.release: 1.6
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.06
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Ignis_ADH
  dmi.board.vendor: ADL
  dmi.board.version: V1.06
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  

[Kernel-packages] [Bug 2000947] Re: UVC Quanta 0408:4035 camera PROBLEM

2024-01-12 Thread Devika B S
@giuliano

Hi, recently, I updated to 6.5.0-14-generic, and the bash file you
mentioned in #108 is not working. I have attached the error file if you
would like to take a look.

Thanks in advance.

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

Title:
  UVC  Quanta 0408:4035  camera PROBLEM

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I bought a Acer Nitro 5 AN517-55 with Quanta ACER HD User Facing',
  USB 0408:4035.

  The camera is reported to have problems by many users:  
  https://linux-hardware.org/?id=usb:0408-4035
  The uvc camera Quanta 0408:4035 does not work with ubuntu 22,04. the camera 
is “recongized” but fails installation.

  My console commands report similar info to other users: 
  
https://unix.stackexchange.com/questions/723504/integrated-camera-not-detected-working-on-acer-nitro-5-an515-58

  
  PROPOSED SOLUTION 
  I got in contact with laurent.pinch...@ideasonboard.com   and with 
riba...@chromium.org , and subscribed to https://www.linuxtv.org/lists. And  
me...@vger.kernel.org mailinglist.

  Laurent proposed me a fix and I modified the 5,15 uvc_driver.c
  version, and loaded it on github

  https://github.com/Giuliano69/uvc_driver-for-Quanta-HD-User-
  Facing-0x0408-0x4035-/blob/main/uvc_driver.c

  I offered to test the fix, so I tried to compile the module with the
  new source.

  COMPILING PROBLEMS
  I’m running **Ubuntu 22.04.1 LTS, with kernel 
  giuliano@Astra2A:/usr/src$ cat /proc/version_signature
  Ubuntu 5.15.0-56.62-generic 5.15.64

  BUT  the linux-source that I found installed seems to be different
  tgiuliano@Astra2A:/usr/src$ ls -al linux-so*
  lrwxrwxrwx 1 root root 47 nov 22 16:08 linux-source-5.15.0.tar.bz2 -> 
linux-source-5.15.0/linux-source-5.15.0.tar.bz2

  I expanded  the tar file, configured the IDE and compiled without error  any 
errors… 
  I manually copied the uvcvideo.ko in 
  /lib/modules/5.15.0-56-
  sudo cp…...

  then tryed to intall the new uvcvideo.ko module
  sudo rmmod uvcvideo && sudo modprobe uvcvideo

  BUT… IT FAILS
  giuliano@Astra2A:~$ sudo rmmod uvcvideo && sudo modprobe uvcvideo
  modprobe: ERROR: could not insert 'uvcvideo': Exec format error

  and dmesg shows
  [25961.151982] usbcore: registered new interface driver uvcvideo
  [26323.125534] usbcore: deregistering interface driver uvcvideo
  [26323.189294] uvcvideo: disagrees about version of symbol module_layout


  These are the TWO modinfo from the old and new uvcvideo modules
  https://pastebin.com/tSj8Exm6
  Basically
  OLD module: vermagic: 5.15.0-56-generic SMP mod_unload modversions 
  NEW module: vermagic: 5.15.64 SMP mod_unload modversions


  -kindly ASK

  HOW can FORCE the uvcdriver.c to match mi kernel version ?
  Have I got OTHER ways to make the kernel module I’m compiling, match my 
running system ?

  I would like to test the module so to confirm the patch and let it
  enter the kernel main stream...

  
  BR
  Giuliano

  PS
  btw…. to allow Eclipse to compile the kernel, I had to pass this commands
  scripts/config --disable CONFIG_SYSTEM_REVOCATION_KEYS
  scripts/config --disable SYSTEM_REVOCATION_KEYS
  scripts/config --disable SYSTEM_TRUSTED_KEYS

  hope that this does not affect the module layout & checking
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  giuliano   2142 F pulseaudio
   /dev/snd/pcmC1D0p:   giuliano   2142 F...m pulseaudio
   /dev/snd/controlC0:  giuliano   2142 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-11-03 (66 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: Acer Nitro AN517-55
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-57-generic 
root=UUID=f07e25f9-07e7-4a29-a15e-f481aa0ee0f2 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-57.63-generic 5.15.74
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-57-generic N/A
   linux-backports-modules-5.15.0-57-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.9
  Tags:  jammy
  Uname: Linux 5.15.0-57-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo wireshark
  _MarkForUpload: True
  dmi.bios.date: 04/20/2022
  dmi.bios.release: 1.6
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.06
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Ignis_ADH
  

[Kernel-packages] [Bug 2016388] Re: Kernel Panic on shutdown / reboot on NUC8I3BEH

2024-01-10 Thread b
This issue persists on 5.15.0-91

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

Title:
  Kernel Panic on shutdown / reboot on NUC8I3BEH

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Kernel 5.4.0-146 panics on power-down (e.g. shutdown -P now)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-146-generic 5.4.0-146.163
  ProcVersionSignature: Ubuntu 5.4.0-144.161-generic 5.4.229
  Uname: Linux 5.4.0-144-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.26
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bbogart1051 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Sat Apr 15 09:07:33 2023
  InstallationDate: Installed on 2019-02-09 (1526 days ago)
  InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Intel(R) Client Systems NUC8i3BEH
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-144-generic 
root=UUID=9c982b36-8142-4719-810a-e06f81cab223 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-144-generic N/A
   linux-backports-modules-5.4.0-144-generic  N/A
   linux-firmware 1.187.38
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2022-06-30 (289 days ago)
  dmi.bios.date: 02/14/2023
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BECFL357.86A.0092.2023.0214.1114
  dmi.board.name: NUC8BEB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: J72693-304
  dmi.chassis.type: 3
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBECFL357.86A.0092.2023.0214.1114:bd02/14/2023:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-303:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-304:cvnIntelCorporation:ct3:cvr2.0:
  dmi.product.family: Intel NUC
  dmi.product.name: NUC8i3BEH
  dmi.product.sku: BOXNUC8i3BEH
  dmi.product.version: J72753-303
  dmi.sys.vendor: Intel(R) Client Systems

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016388/+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 2016388] Re: Kernel Panic on shutdown / reboot on NUC8I3BEH

2023-10-16 Thread b
** Attachment added: "Photo of panic call trace for 5.4.0-164"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016388/+attachment/5710071/+files/20231016_084851.jpg

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

Title:
  Kernel Panic on shutdown / reboot on NUC8I3BEH

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Kernel 5.4.0-146 panics on power-down (e.g. shutdown -P now)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-146-generic 5.4.0-146.163
  ProcVersionSignature: Ubuntu 5.4.0-144.161-generic 5.4.229
  Uname: Linux 5.4.0-144-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.26
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bbogart1051 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Sat Apr 15 09:07:33 2023
  InstallationDate: Installed on 2019-02-09 (1526 days ago)
  InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Intel(R) Client Systems NUC8i3BEH
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-144-generic 
root=UUID=9c982b36-8142-4719-810a-e06f81cab223 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-144-generic N/A
   linux-backports-modules-5.4.0-144-generic  N/A
   linux-firmware 1.187.38
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2022-06-30 (289 days ago)
  dmi.bios.date: 02/14/2023
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BECFL357.86A.0092.2023.0214.1114
  dmi.board.name: NUC8BEB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: J72693-304
  dmi.chassis.type: 3
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBECFL357.86A.0092.2023.0214.1114:bd02/14/2023:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-303:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-304:cvnIntelCorporation:ct3:cvr2.0:
  dmi.product.family: Intel NUC
  dmi.product.name: NUC8i3BEH
  dmi.product.sku: BOXNUC8i3BEH
  dmi.product.version: J72753-303
  dmi.sys.vendor: Intel(R) Client Systems

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016388/+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 2016388] Re: Kernel Panic on shutdown / reboot on NUC8I3BEH

2023-10-16 Thread b
I'm not sure how, but I managed to get to a console and see the panic
trace on 5.15.0-84. (see attachment below) It does not match the same
panic that I've been previously getting with other kernels.

I also confirm the issue persists on 5.15.0-86 and 5.4.0-164

** Attachment added: "Panic call trace for 5.15.9-84"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016388/+attachment/5710070/+files/20231013_175852.jpg

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

Title:
  Kernel Panic on shutdown / reboot on NUC8I3BEH

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Kernel 5.4.0-146 panics on power-down (e.g. shutdown -P now)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-146-generic 5.4.0-146.163
  ProcVersionSignature: Ubuntu 5.4.0-144.161-generic 5.4.229
  Uname: Linux 5.4.0-144-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.26
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bbogart1051 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Sat Apr 15 09:07:33 2023
  InstallationDate: Installed on 2019-02-09 (1526 days ago)
  InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Intel(R) Client Systems NUC8i3BEH
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-144-generic 
root=UUID=9c982b36-8142-4719-810a-e06f81cab223 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-144-generic N/A
   linux-backports-modules-5.4.0-144-generic  N/A
   linux-firmware 1.187.38
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2022-06-30 (289 days ago)
  dmi.bios.date: 02/14/2023
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BECFL357.86A.0092.2023.0214.1114
  dmi.board.name: NUC8BEB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: J72693-304
  dmi.chassis.type: 3
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBECFL357.86A.0092.2023.0214.1114:bd02/14/2023:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-303:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-304:cvnIntelCorporation:ct3:cvr2.0:
  dmi.product.family: Intel NUC
  dmi.product.name: NUC8i3BEH
  dmi.product.sku: BOXNUC8i3BEH
  dmi.product.version: J72753-303
  dmi.sys.vendor: Intel(R) Client Systems

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016388/+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 2016388] Re: Kernel Panic on shutdown / reboot on NUC8I3BEH

2023-10-10 Thread b
The issue persists on 5.4.0-163 and 5.15.0-84

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

Title:
  Kernel Panic on shutdown / reboot on NUC8I3BEH

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Kernel 5.4.0-146 panics on power-down (e.g. shutdown -P now)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-146-generic 5.4.0-146.163
  ProcVersionSignature: Ubuntu 5.4.0-144.161-generic 5.4.229
  Uname: Linux 5.4.0-144-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.26
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bbogart1051 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Sat Apr 15 09:07:33 2023
  InstallationDate: Installed on 2019-02-09 (1526 days ago)
  InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Intel(R) Client Systems NUC8i3BEH
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-144-generic 
root=UUID=9c982b36-8142-4719-810a-e06f81cab223 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-144-generic N/A
   linux-backports-modules-5.4.0-144-generic  N/A
   linux-firmware 1.187.38
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2022-06-30 (289 days ago)
  dmi.bios.date: 02/14/2023
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BECFL357.86A.0092.2023.0214.1114
  dmi.board.name: NUC8BEB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: J72693-304
  dmi.chassis.type: 3
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBECFL357.86A.0092.2023.0214.1114:bd02/14/2023:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-303:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-304:cvnIntelCorporation:ct3:cvr2.0:
  dmi.product.family: Intel NUC
  dmi.product.name: NUC8i3BEH
  dmi.product.sku: BOXNUC8i3BEH
  dmi.product.version: J72753-303
  dmi.sys.vendor: Intel(R) Client Systems

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016388/+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 2000947] Re: UVC Quanta 0408:4035 camera PROBLEM

2023-09-29 Thread Devika B S
** Attachment removed: "compile_module.sh"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2000947/+attachment/5705396/+files/compile_module.sh

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

Title:
  UVC  Quanta 0408:4035  camera PROBLEM

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I bought a Acer Nitro 5 AN517-55 with Quanta ACER HD User Facing',
  USB 0408:4035.

  The camera is reported to have problems by many users:  
  https://linux-hardware.org/?id=usb:0408-4035
  The uvc camera Quanta 0408:4035 does not work with ubuntu 22,04. the camera 
is “recongized” but fails installation.

  My console commands report similar info to other users: 
  
https://unix.stackexchange.com/questions/723504/integrated-camera-not-detected-working-on-acer-nitro-5-an515-58

  
  PROPOSED SOLUTION 
  I got in contact with laurent.pinch...@ideasonboard.com   and with 
riba...@chromium.org , and subscribed to https://www.linuxtv.org/lists. And  
me...@vger.kernel.org mailinglist.

  Laurent proposed me a fix and I modified the 5,15 uvc_driver.c
  version, and loaded it on github

  https://github.com/Giuliano69/uvc_driver-for-Quanta-HD-User-
  Facing-0x0408-0x4035-/blob/main/uvc_driver.c

  I offered to test the fix, so I tried to compile the module with the
  new source.

  COMPILING PROBLEMS
  I’m running **Ubuntu 22.04.1 LTS, with kernel 
  giuliano@Astra2A:/usr/src$ cat /proc/version_signature
  Ubuntu 5.15.0-56.62-generic 5.15.64

  BUT  the linux-source that I found installed seems to be different
  tgiuliano@Astra2A:/usr/src$ ls -al linux-so*
  lrwxrwxrwx 1 root root 47 nov 22 16:08 linux-source-5.15.0.tar.bz2 -> 
linux-source-5.15.0/linux-source-5.15.0.tar.bz2

  I expanded  the tar file, configured the IDE and compiled without error  any 
errors… 
  I manually copied the uvcvideo.ko in 
  /lib/modules/5.15.0-56-
  sudo cp…...

  then tryed to intall the new uvcvideo.ko module
  sudo rmmod uvcvideo && sudo modprobe uvcvideo

  BUT… IT FAILS
  giuliano@Astra2A:~$ sudo rmmod uvcvideo && sudo modprobe uvcvideo
  modprobe: ERROR: could not insert 'uvcvideo': Exec format error

  and dmesg shows
  [25961.151982] usbcore: registered new interface driver uvcvideo
  [26323.125534] usbcore: deregistering interface driver uvcvideo
  [26323.189294] uvcvideo: disagrees about version of symbol module_layout


  These are the TWO modinfo from the old and new uvcvideo modules
  https://pastebin.com/tSj8Exm6
  Basically
  OLD module: vermagic: 5.15.0-56-generic SMP mod_unload modversions 
  NEW module: vermagic: 5.15.64 SMP mod_unload modversions


  -kindly ASK

  HOW can FORCE the uvcdriver.c to match mi kernel version ?
  Have I got OTHER ways to make the kernel module I’m compiling, match my 
running system ?

  I would like to test the module so to confirm the patch and let it
  enter the kernel main stream...

  
  BR
  Giuliano

  PS
  btw…. to allow Eclipse to compile the kernel, I had to pass this commands
  scripts/config --disable CONFIG_SYSTEM_REVOCATION_KEYS
  scripts/config --disable SYSTEM_REVOCATION_KEYS
  scripts/config --disable SYSTEM_TRUSTED_KEYS

  hope that this does not affect the module layout & checking
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  giuliano   2142 F pulseaudio
   /dev/snd/pcmC1D0p:   giuliano   2142 F...m pulseaudio
   /dev/snd/controlC0:  giuliano   2142 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-11-03 (66 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: Acer Nitro AN517-55
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-57-generic 
root=UUID=f07e25f9-07e7-4a29-a15e-f481aa0ee0f2 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-57.63-generic 5.15.74
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-57-generic N/A
   linux-backports-modules-5.15.0-57-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.9
  Tags:  jammy
  Uname: Linux 5.15.0-57-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo wireshark
  _MarkForUpload: True
  dmi.bios.date: 04/20/2022
  dmi.bios.release: 1.6
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.06
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Ignis_ADH
  dmi.board.vendor: ADL
  dmi.board.version: 

[Kernel-packages] [Bug 2000947] Re: UVC Quanta 0408:4035 camera PROBLEM

2023-09-29 Thread Devika B S
** Attachment added: "compile_module.sh"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2000947/+attachment/5705396/+files/compile_module.sh

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

Title:
  UVC  Quanta 0408:4035  camera PROBLEM

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I bought a Acer Nitro 5 AN517-55 with Quanta ACER HD User Facing',
  USB 0408:4035.

  The camera is reported to have problems by many users:  
  https://linux-hardware.org/?id=usb:0408-4035
  The uvc camera Quanta 0408:4035 does not work with ubuntu 22,04. the camera 
is “recongized” but fails installation.

  My console commands report similar info to other users: 
  
https://unix.stackexchange.com/questions/723504/integrated-camera-not-detected-working-on-acer-nitro-5-an515-58

  
  PROPOSED SOLUTION 
  I got in contact with laurent.pinch...@ideasonboard.com   and with 
riba...@chromium.org , and subscribed to https://www.linuxtv.org/lists. And  
me...@vger.kernel.org mailinglist.

  Laurent proposed me a fix and I modified the 5,15 uvc_driver.c
  version, and loaded it on github

  https://github.com/Giuliano69/uvc_driver-for-Quanta-HD-User-
  Facing-0x0408-0x4035-/blob/main/uvc_driver.c

  I offered to test the fix, so I tried to compile the module with the
  new source.

  COMPILING PROBLEMS
  I’m running **Ubuntu 22.04.1 LTS, with kernel 
  giuliano@Astra2A:/usr/src$ cat /proc/version_signature
  Ubuntu 5.15.0-56.62-generic 5.15.64

  BUT  the linux-source that I found installed seems to be different
  tgiuliano@Astra2A:/usr/src$ ls -al linux-so*
  lrwxrwxrwx 1 root root 47 nov 22 16:08 linux-source-5.15.0.tar.bz2 -> 
linux-source-5.15.0/linux-source-5.15.0.tar.bz2

  I expanded  the tar file, configured the IDE and compiled without error  any 
errors… 
  I manually copied the uvcvideo.ko in 
  /lib/modules/5.15.0-56-
  sudo cp…...

  then tryed to intall the new uvcvideo.ko module
  sudo rmmod uvcvideo && sudo modprobe uvcvideo

  BUT… IT FAILS
  giuliano@Astra2A:~$ sudo rmmod uvcvideo && sudo modprobe uvcvideo
  modprobe: ERROR: could not insert 'uvcvideo': Exec format error

  and dmesg shows
  [25961.151982] usbcore: registered new interface driver uvcvideo
  [26323.125534] usbcore: deregistering interface driver uvcvideo
  [26323.189294] uvcvideo: disagrees about version of symbol module_layout


  These are the TWO modinfo from the old and new uvcvideo modules
  https://pastebin.com/tSj8Exm6
  Basically
  OLD module: vermagic: 5.15.0-56-generic SMP mod_unload modversions 
  NEW module: vermagic: 5.15.64 SMP mod_unload modversions


  -kindly ASK

  HOW can FORCE the uvcdriver.c to match mi kernel version ?
  Have I got OTHER ways to make the kernel module I’m compiling, match my 
running system ?

  I would like to test the module so to confirm the patch and let it
  enter the kernel main stream...

  
  BR
  Giuliano

  PS
  btw…. to allow Eclipse to compile the kernel, I had to pass this commands
  scripts/config --disable CONFIG_SYSTEM_REVOCATION_KEYS
  scripts/config --disable SYSTEM_REVOCATION_KEYS
  scripts/config --disable SYSTEM_TRUSTED_KEYS

  hope that this does not affect the module layout & checking
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  giuliano   2142 F pulseaudio
   /dev/snd/pcmC1D0p:   giuliano   2142 F...m pulseaudio
   /dev/snd/controlC0:  giuliano   2142 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-11-03 (66 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: Acer Nitro AN517-55
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-57-generic 
root=UUID=f07e25f9-07e7-4a29-a15e-f481aa0ee0f2 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-57.63-generic 5.15.74
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-57-generic N/A
   linux-backports-modules-5.15.0-57-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.9
  Tags:  jammy
  Uname: Linux 5.15.0-57-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo wireshark
  _MarkForUpload: True
  dmi.bios.date: 04/20/2022
  dmi.bios.release: 1.6
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.06
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Ignis_ADH
  dmi.board.vendor: ADL
  dmi.board.version: V1.06

[Kernel-packages] [Bug 2000947] Re: UVC Quanta 0408:4035 camera PROBLEM

2023-09-29 Thread Devika B S
@giuliano

Thank you for sharing the link. I found the solution there. Have a great
day!

** Attachment added: "compile_module.sh"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2000947/+attachment/5705395/+files/compile_module.sh

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

Title:
  UVC  Quanta 0408:4035  camera PROBLEM

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I bought a Acer Nitro 5 AN517-55 with Quanta ACER HD User Facing',
  USB 0408:4035.

  The camera is reported to have problems by many users:  
  https://linux-hardware.org/?id=usb:0408-4035
  The uvc camera Quanta 0408:4035 does not work with ubuntu 22,04. the camera 
is “recongized” but fails installation.

  My console commands report similar info to other users: 
  
https://unix.stackexchange.com/questions/723504/integrated-camera-not-detected-working-on-acer-nitro-5-an515-58

  
  PROPOSED SOLUTION 
  I got in contact with laurent.pinch...@ideasonboard.com   and with 
riba...@chromium.org , and subscribed to https://www.linuxtv.org/lists. And  
me...@vger.kernel.org mailinglist.

  Laurent proposed me a fix and I modified the 5,15 uvc_driver.c
  version, and loaded it on github

  https://github.com/Giuliano69/uvc_driver-for-Quanta-HD-User-
  Facing-0x0408-0x4035-/blob/main/uvc_driver.c

  I offered to test the fix, so I tried to compile the module with the
  new source.

  COMPILING PROBLEMS
  I’m running **Ubuntu 22.04.1 LTS, with kernel 
  giuliano@Astra2A:/usr/src$ cat /proc/version_signature
  Ubuntu 5.15.0-56.62-generic 5.15.64

  BUT  the linux-source that I found installed seems to be different
  tgiuliano@Astra2A:/usr/src$ ls -al linux-so*
  lrwxrwxrwx 1 root root 47 nov 22 16:08 linux-source-5.15.0.tar.bz2 -> 
linux-source-5.15.0/linux-source-5.15.0.tar.bz2

  I expanded  the tar file, configured the IDE and compiled without error  any 
errors… 
  I manually copied the uvcvideo.ko in 
  /lib/modules/5.15.0-56-
  sudo cp…...

  then tryed to intall the new uvcvideo.ko module
  sudo rmmod uvcvideo && sudo modprobe uvcvideo

  BUT… IT FAILS
  giuliano@Astra2A:~$ sudo rmmod uvcvideo && sudo modprobe uvcvideo
  modprobe: ERROR: could not insert 'uvcvideo': Exec format error

  and dmesg shows
  [25961.151982] usbcore: registered new interface driver uvcvideo
  [26323.125534] usbcore: deregistering interface driver uvcvideo
  [26323.189294] uvcvideo: disagrees about version of symbol module_layout


  These are the TWO modinfo from the old and new uvcvideo modules
  https://pastebin.com/tSj8Exm6
  Basically
  OLD module: vermagic: 5.15.0-56-generic SMP mod_unload modversions 
  NEW module: vermagic: 5.15.64 SMP mod_unload modversions


  -kindly ASK

  HOW can FORCE the uvcdriver.c to match mi kernel version ?
  Have I got OTHER ways to make the kernel module I’m compiling, match my 
running system ?

  I would like to test the module so to confirm the patch and let it
  enter the kernel main stream...

  
  BR
  Giuliano

  PS
  btw…. to allow Eclipse to compile the kernel, I had to pass this commands
  scripts/config --disable CONFIG_SYSTEM_REVOCATION_KEYS
  scripts/config --disable SYSTEM_REVOCATION_KEYS
  scripts/config --disable SYSTEM_TRUSTED_KEYS

  hope that this does not affect the module layout & checking
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  giuliano   2142 F pulseaudio
   /dev/snd/pcmC1D0p:   giuliano   2142 F...m pulseaudio
   /dev/snd/controlC0:  giuliano   2142 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-11-03 (66 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: Acer Nitro AN517-55
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-57-generic 
root=UUID=f07e25f9-07e7-4a29-a15e-f481aa0ee0f2 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-57.63-generic 5.15.74
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-57-generic N/A
   linux-backports-modules-5.15.0-57-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.9
  Tags:  jammy
  Uname: Linux 5.15.0-57-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo wireshark
  _MarkForUpload: True
  dmi.bios.date: 04/20/2022
  dmi.bios.release: 1.6
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.06
  dmi.board.asset.tag: Type2 - 

[Kernel-packages] [Bug 2000947] Re: UVC Quanta 0408:4035 camera PROBLEM

2023-09-29 Thread Devika B S
Hi

@giuliano

I followed the steps from #37, and they worked initially. However, after
a recent update, my kernel changed to 6.2.0-33, and now it no longer
functions properly. When I attempted to retrace the steps from #37, I
encountered error #99, even though I had deleted all the files created
during each execution of the commands.

I have an Acer Aspire A515-57G laptop with the camera identified as
'0408:4033 Quanta Computer, Inc. ACER HD User Facing,' running Ubuntu
22.04.3 LTS.

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

Title:
  UVC  Quanta 0408:4035  camera PROBLEM

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I bought a Acer Nitro 5 AN517-55 with Quanta ACER HD User Facing',
  USB 0408:4035.

  The camera is reported to have problems by many users:  
  https://linux-hardware.org/?id=usb:0408-4035
  The uvc camera Quanta 0408:4035 does not work with ubuntu 22,04. the camera 
is “recongized” but fails installation.

  My console commands report similar info to other users: 
  
https://unix.stackexchange.com/questions/723504/integrated-camera-not-detected-working-on-acer-nitro-5-an515-58

  
  PROPOSED SOLUTION 
  I got in contact with laurent.pinch...@ideasonboard.com   and with 
riba...@chromium.org , and subscribed to https://www.linuxtv.org/lists. And  
me...@vger.kernel.org mailinglist.

  Laurent proposed me a fix and I modified the 5,15 uvc_driver.c
  version, and loaded it on github

  https://github.com/Giuliano69/uvc_driver-for-Quanta-HD-User-
  Facing-0x0408-0x4035-/blob/main/uvc_driver.c

  I offered to test the fix, so I tried to compile the module with the
  new source.

  COMPILING PROBLEMS
  I’m running **Ubuntu 22.04.1 LTS, with kernel 
  giuliano@Astra2A:/usr/src$ cat /proc/version_signature
  Ubuntu 5.15.0-56.62-generic 5.15.64

  BUT  the linux-source that I found installed seems to be different
  tgiuliano@Astra2A:/usr/src$ ls -al linux-so*
  lrwxrwxrwx 1 root root 47 nov 22 16:08 linux-source-5.15.0.tar.bz2 -> 
linux-source-5.15.0/linux-source-5.15.0.tar.bz2

  I expanded  the tar file, configured the IDE and compiled without error  any 
errors… 
  I manually copied the uvcvideo.ko in 
  /lib/modules/5.15.0-56-
  sudo cp…...

  then tryed to intall the new uvcvideo.ko module
  sudo rmmod uvcvideo && sudo modprobe uvcvideo

  BUT… IT FAILS
  giuliano@Astra2A:~$ sudo rmmod uvcvideo && sudo modprobe uvcvideo
  modprobe: ERROR: could not insert 'uvcvideo': Exec format error

  and dmesg shows
  [25961.151982] usbcore: registered new interface driver uvcvideo
  [26323.125534] usbcore: deregistering interface driver uvcvideo
  [26323.189294] uvcvideo: disagrees about version of symbol module_layout


  These are the TWO modinfo from the old and new uvcvideo modules
  https://pastebin.com/tSj8Exm6
  Basically
  OLD module: vermagic: 5.15.0-56-generic SMP mod_unload modversions 
  NEW module: vermagic: 5.15.64 SMP mod_unload modversions


  -kindly ASK

  HOW can FORCE the uvcdriver.c to match mi kernel version ?
  Have I got OTHER ways to make the kernel module I’m compiling, match my 
running system ?

  I would like to test the module so to confirm the patch and let it
  enter the kernel main stream...

  
  BR
  Giuliano

  PS
  btw…. to allow Eclipse to compile the kernel, I had to pass this commands
  scripts/config --disable CONFIG_SYSTEM_REVOCATION_KEYS
  scripts/config --disable SYSTEM_REVOCATION_KEYS
  scripts/config --disable SYSTEM_TRUSTED_KEYS

  hope that this does not affect the module layout & checking
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  giuliano   2142 F pulseaudio
   /dev/snd/pcmC1D0p:   giuliano   2142 F...m pulseaudio
   /dev/snd/controlC0:  giuliano   2142 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-11-03 (66 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: Acer Nitro AN517-55
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-57-generic 
root=UUID=f07e25f9-07e7-4a29-a15e-f481aa0ee0f2 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-57.63-generic 5.15.74
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-57-generic N/A
   linux-backports-modules-5.15.0-57-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.9
  Tags:  jammy
  Uname: Linux 5.15.0-57-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh 

[Kernel-packages] [Bug 2026652] Re: Suspend Broken

2023-09-27 Thread Marlen T. B.
I switched back to the NVIDIA drivers.

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

Title:
  Suspend Broken

Status in linux-signed-lowlatency package in Ubuntu:
  New

Bug description:
  When I go to suspend my system via the UI "Suspend" option, the system
  fails to suspend. Instead it looks like its going to suspend, and then
  wakes up but with a locked screen.

  When I use `pm-suspend` from the command line, it suspends the system,
  but does not lock the screen. I have the Settings -> Privacy -> Screen
  Lock -> "Lock Screen on Suspend" setting enabled.

  I am using the Nouveau driver, with Wayland, using GNOME 44.2.
  This bug only started when I switched away from using any of the NVIDIA 
drivers, so its probably partially Nouveau related. Switching back to the 
NVIDIA drivers (I tried them all) isn't an option, because they break:
  1. External monitor connectivity
  2. VMWare Horizon

  Debug info:

  1. `lsb_release -rd`
  Description:  Ubuntu 23.04
  Release:  23.04

  2. `uname -srm`
  Linux 6.2.0-1007-lowlatency x86_64

  Please let me know of any other information needed to debug this.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: linux-image-6.2.0-1007-lowlatency 6.2.0-1007.7
  ProcVersionSignature: Ubuntu 6.2.0-1007.7-lowlatency 6.2.12
  Uname: Linux 6.2.0-1007-lowlatency x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jul  9 10:26:06 2023
  InstallationDate: Installed on 2021-12-18 (567 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  SourcePackage: linux-signed-lowlatency
  UpgradeStatus: Upgraded to lunar on 2023-04-26 (73 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-lowlatency/+bug/2026652/+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 2026652] Re: Suspend Broken

2023-07-24 Thread Marlen T. B.
May or may not be related to this other bug I filed
https://bugs.launchpad.net/ubuntu/+bug/2028410.

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

Title:
  Suspend Broken

Status in linux-signed-lowlatency package in Ubuntu:
  New

Bug description:
  When I go to suspend my system via the UI "Suspend" option, the system
  fails to suspend. Instead it looks like its going to suspend, and then
  wakes up but with a locked screen.

  When I use `pm-suspend` from the command line, it suspends the system,
  but does not lock the screen. I have the Settings -> Privacy -> Screen
  Lock -> "Lock Screen on Suspend" setting enabled.

  I am using the Nouveau driver, with Wayland, using GNOME 44.2.
  This bug only started when I switched away from using any of the NVIDIA 
drivers, so its probably partially Nouveau related. Switching back to the 
NVIDIA drivers (I tried them all) isn't an option, because they break:
  1. External monitor connectivity
  2. VMWare Horizon

  Debug info:

  1. `lsb_release -rd`
  Description:  Ubuntu 23.04
  Release:  23.04

  2. `uname -srm`
  Linux 6.2.0-1007-lowlatency x86_64

  Please let me know of any other information needed to debug this.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: linux-image-6.2.0-1007-lowlatency 6.2.0-1007.7
  ProcVersionSignature: Ubuntu 6.2.0-1007.7-lowlatency 6.2.12
  Uname: Linux 6.2.0-1007-lowlatency x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jul  9 10:26:06 2023
  InstallationDate: Installed on 2021-12-18 (567 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  SourcePackage: linux-signed-lowlatency
  UpgradeStatus: Upgraded to lunar on 2023-04-26 (73 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-lowlatency/+bug/2026652/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


Re: [Kernel-packages] [Bug 2016388] Re: Kernel Panic on shutdown / reboot on NUC8I3BEH

2023-07-21 Thread b
The issue persists using kernel 5.15.0-76, unfortunately, the console 
remains blank, no panic message is printed but the machine stays on 
(power light stays on) and is unresponsive. Holding down the power 
button is the only action possible.

Could not find anything in the log files, looks like the machine totally 
locks up now rather than having a panic.

On 2023-07-13 17:49, Kai-Heng Feng wrote:
> Please install later kernel by issuing `sudo apt install linux-generic-
> hwe-20.04` and reboot.
> 

-- 
B. Bogart, PhD
they/them
www.ekran.org

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

Title:
  Kernel Panic on shutdown / reboot on NUC8I3BEH

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Kernel 5.4.0-146 panics on power-down (e.g. shutdown -P now)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-146-generic 5.4.0-146.163
  ProcVersionSignature: Ubuntu 5.4.0-144.161-generic 5.4.229
  Uname: Linux 5.4.0-144-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.26
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bbogart1051 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Sat Apr 15 09:07:33 2023
  InstallationDate: Installed on 2019-02-09 (1526 days ago)
  InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Intel(R) Client Systems NUC8i3BEH
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-144-generic 
root=UUID=9c982b36-8142-4719-810a-e06f81cab223 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-144-generic N/A
   linux-backports-modules-5.4.0-144-generic  N/A
   linux-firmware 1.187.38
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2022-06-30 (289 days ago)
  dmi.bios.date: 02/14/2023
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BECFL357.86A.0092.2023.0214.1114
  dmi.board.name: NUC8BEB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: J72693-304
  dmi.chassis.type: 3
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBECFL357.86A.0092.2023.0214.1114:bd02/14/2023:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-303:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-304:cvnIntelCorporation:ct3:cvr2.0:
  dmi.product.family: Intel NUC
  dmi.product.name: NUC8i3BEH
  dmi.product.sku: BOXNUC8i3BEH
  dmi.product.version: J72753-303
  dmi.sys.vendor: Intel(R) Client Systems

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016388/+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 2026652] Re: Suspend Broken

2023-07-19 Thread Marlen T. B.
After updating and restarting I can again use the hacky script I was
using before. I wish sleep just worked normally :(

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

Title:
  Suspend Broken

Status in linux-signed-lowlatency package in Ubuntu:
  New

Bug description:
  When I go to suspend my system via the UI "Suspend" option, the system
  fails to suspend. Instead it looks like its going to suspend, and then
  wakes up but with a locked screen.

  When I use `pm-suspend` from the command line, it suspends the system,
  but does not lock the screen. I have the Settings -> Privacy -> Screen
  Lock -> "Lock Screen on Suspend" setting enabled.

  I am using the Nouveau driver, with Wayland, using GNOME 44.2.
  This bug only started when I switched away from using any of the NVIDIA 
drivers, so its probably partially Nouveau related. Switching back to the 
NVIDIA drivers (I tried them all) isn't an option, because they break:
  1. External monitor connectivity
  2. VMWare Horizon

  Debug info:

  1. `lsb_release -rd`
  Description:  Ubuntu 23.04
  Release:  23.04

  2. `uname -srm`
  Linux 6.2.0-1007-lowlatency x86_64

  Please let me know of any other information needed to debug this.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: linux-image-6.2.0-1007-lowlatency 6.2.0-1007.7
  ProcVersionSignature: Ubuntu 6.2.0-1007.7-lowlatency 6.2.12
  Uname: Linux 6.2.0-1007-lowlatency x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jul  9 10:26:06 2023
  InstallationDate: Installed on 2021-12-18 (567 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  SourcePackage: linux-signed-lowlatency
  UpgradeStatus: Upgraded to lunar on 2023-04-26 (73 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-lowlatency/+bug/2026652/+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 2026652] Re: Suspend Broken

2023-07-18 Thread Marlen T. B.
After updating, now `sudo pm-suspend` doesn't work anymore.

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

Title:
  Suspend Broken

Status in linux-signed-lowlatency package in Ubuntu:
  New

Bug description:
  When I go to suspend my system via the UI "Suspend" option, the system
  fails to suspend. Instead it looks like its going to suspend, and then
  wakes up but with a locked screen.

  When I use `pm-suspend` from the command line, it suspends the system,
  but does not lock the screen. I have the Settings -> Privacy -> Screen
  Lock -> "Lock Screen on Suspend" setting enabled.

  I am using the Nouveau driver, with Wayland, using GNOME 44.2.
  This bug only started when I switched away from using any of the NVIDIA 
drivers, so its probably partially Nouveau related. Switching back to the 
NVIDIA drivers (I tried them all) isn't an option, because they break:
  1. External monitor connectivity
  2. VMWare Horizon

  Debug info:

  1. `lsb_release -rd`
  Description:  Ubuntu 23.04
  Release:  23.04

  2. `uname -srm`
  Linux 6.2.0-1007-lowlatency x86_64

  Please let me know of any other information needed to debug this.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: linux-image-6.2.0-1007-lowlatency 6.2.0-1007.7
  ProcVersionSignature: Ubuntu 6.2.0-1007.7-lowlatency 6.2.12
  Uname: Linux 6.2.0-1007-lowlatency x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jul  9 10:26:06 2023
  InstallationDate: Installed on 2021-12-18 (567 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  SourcePackage: linux-signed-lowlatency
  UpgradeStatus: Upgraded to lunar on 2023-04-26 (73 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-lowlatency/+bug/2026652/+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 2026652] Re: Suspend Broken

2023-07-15 Thread Marlen T. B.
Currently running this script to sleep my computer as a workaround.


```bash
#!/usr/bin/env bash

# sleep.sh
cat $(basename "$0")

# See https://askubuntu.com/a/1126678
# The sleep is necessary to make sure the screen locks before suspend
sudo ls >/dev/null && # caches sudo permissions
  dbus-send \
--type=method_call \
--dest=org.gnome.ScreenSaver \
/org/gnome/ScreenSaver org.gnome.ScreenSaver.Lock \
  & sleep 2 && sudo pm-suspend
```

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

Title:
  Suspend Broken

Status in linux-signed-lowlatency package in Ubuntu:
  New

Bug description:
  When I go to suspend my system via the UI "Suspend" option, the system
  fails to suspend. Instead it looks like its going to suspend, and then
  wakes up but with a locked screen.

  When I use `pm-suspend` from the command line, it suspends the system,
  but does not lock the screen. I have the Settings -> Privacy -> Screen
  Lock -> "Lock Screen on Suspend" setting enabled.

  I am using the Nouveau driver, with Wayland, using GNOME 44.2.
  This bug only started when I switched away from using any of the NVIDIA 
drivers, so its probably partially Nouveau related. Switching back to the 
NVIDIA drivers (I tried them all) isn't an option, because they break:
  1. External monitor connectivity
  2. VMWare Horizon

  Debug info:

  1. `lsb_release -rd`
  Description:  Ubuntu 23.04
  Release:  23.04

  2. `uname -srm`
  Linux 6.2.0-1007-lowlatency x86_64

  Please let me know of any other information needed to debug this.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: linux-image-6.2.0-1007-lowlatency 6.2.0-1007.7
  ProcVersionSignature: Ubuntu 6.2.0-1007.7-lowlatency 6.2.12
  Uname: Linux 6.2.0-1007-lowlatency x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jul  9 10:26:06 2023
  InstallationDate: Installed on 2021-12-18 (567 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  SourcePackage: linux-signed-lowlatency
  UpgradeStatus: Upgraded to lunar on 2023-04-26 (73 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-lowlatency/+bug/2026652/+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 2026652] Re: Suspend Broken

2023-07-14 Thread Marlen T. B.
** Description changed:

  When I go to suspend my system via the UI "Suspend" option, the system
  fails to suspend. Instead it looks like its going to suspend, and then
  wakes up but with a locked screen.
  
  When I use `pm-suspend` from the command line, it suspends the system,
  but does not lock the screen. I have the Settings -> Privacy -> Screen
  Lock -> "Lock Screen on Suspend" setting enabled.
  
  I am using the Nouveau driver, with Wayland, using GNOME 44.2.
- This bug only started when I switched away from using any of the NVIDIA 
drivers, so its probably partially Nouveau related. Switching away from NVIDIA 
drivers (I tried them all) isn't an option, because they break:
+ This bug only started when I switched away from using any of the NVIDIA 
drivers, so its probably partially Nouveau related. Switching back to the 
NVIDIA drivers (I tried them all) isn't an option, because they break:
  1. External monitor connectivity
  2. VMWare Horizon
  
  Debug info:
  
  1. `lsb_release -rd`
  Description:  Ubuntu 23.04
  Release:  23.04
  
  2. `uname -srm`
  Linux 6.2.0-1007-lowlatency x86_64
  
  Please let me know of any other information needed to debug this.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: linux-image-6.2.0-1007-lowlatency 6.2.0-1007.7
  ProcVersionSignature: Ubuntu 6.2.0-1007.7-lowlatency 6.2.12
  Uname: Linux 6.2.0-1007-lowlatency x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jul  9 10:26:06 2023
  InstallationDate: Installed on 2021-12-18 (567 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  SourcePackage: linux-signed-lowlatency
  UpgradeStatus: Upgraded to lunar on 2023-04-26 (73 days ago)

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

Title:
  Suspend Broken

Status in linux-signed-lowlatency package in Ubuntu:
  New

Bug description:
  When I go to suspend my system via the UI "Suspend" option, the system
  fails to suspend. Instead it looks like its going to suspend, and then
  wakes up but with a locked screen.

  When I use `pm-suspend` from the command line, it suspends the system,
  but does not lock the screen. I have the Settings -> Privacy -> Screen
  Lock -> "Lock Screen on Suspend" setting enabled.

  I am using the Nouveau driver, with Wayland, using GNOME 44.2.
  This bug only started when I switched away from using any of the NVIDIA 
drivers, so its probably partially Nouveau related. Switching back to the 
NVIDIA drivers (I tried them all) isn't an option, because they break:
  1. External monitor connectivity
  2. VMWare Horizon

  Debug info:

  1. `lsb_release -rd`
  Description:  Ubuntu 23.04
  Release:  23.04

  2. `uname -srm`
  Linux 6.2.0-1007-lowlatency x86_64

  Please let me know of any other information needed to debug this.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: linux-image-6.2.0-1007-lowlatency 6.2.0-1007.7
  ProcVersionSignature: Ubuntu 6.2.0-1007.7-lowlatency 6.2.12
  Uname: Linux 6.2.0-1007-lowlatency x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jul  9 10:26:06 2023
  InstallationDate: Installed on 2021-12-18 (567 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  SourcePackage: linux-signed-lowlatency
  UpgradeStatus: Upgraded to lunar on 2023-04-26 (73 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-lowlatency/+bug/2026652/+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 2026652] Re: Suspend Broken

2023-07-12 Thread Marlen T. B.
I'd love to hear if anyone has any suggestions around this, since its a
hardware risk if I can't sleep my computer, or a security risk if I `pm-
suspend` it and it doesn't lock.

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

Title:
  Suspend Broken

Status in linux-signed-lowlatency package in Ubuntu:
  New

Bug description:
  When I go to suspend my system via the UI "Suspend" option, the system
  fails to suspend. Instead it looks like its going to suspend, and then
  wakes up but with a locked screen.

  When I use `pm-suspend` from the command line, it suspends the system,
  but does not lock the screen. I have the Settings -> Privacy -> Screen
  Lock -> "Lock Screen on Suspend" setting enabled.

  I am using the Nouveau driver, with Wayland, using GNOME 44.2.
  This bug only started when I switched away from using any of the NVIDIA 
drivers, so its probably partially Nouveau related. Switching away from NVIDIA 
drivers (I tried them all) isn't an option, because they break:
  1. External monitor connectivity
  2. VMWare Horizon

  Debug info:

  1. `lsb_release -rd`
  Description:  Ubuntu 23.04
  Release:  23.04

  2. `uname -srm`
  Linux 6.2.0-1007-lowlatency x86_64

  Please let me know of any other information needed to debug this.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: linux-image-6.2.0-1007-lowlatency 6.2.0-1007.7
  ProcVersionSignature: Ubuntu 6.2.0-1007.7-lowlatency 6.2.12
  Uname: Linux 6.2.0-1007-lowlatency x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jul  9 10:26:06 2023
  InstallationDate: Installed on 2021-12-18 (567 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  SourcePackage: linux-signed-lowlatency
  UpgradeStatus: Upgraded to lunar on 2023-04-26 (73 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-lowlatency/+bug/2026652/+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 2016388] Re: Kernel Panic on shutdown / reboot on NUC8I3BEH

2023-07-11 Thread b
The issue persists with 5.4.0-152

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

Title:
  Kernel Panic on shutdown / reboot on NUC8I3BEH

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Kernel 5.4.0-146 panics on power-down (e.g. shutdown -P now)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-146-generic 5.4.0-146.163
  ProcVersionSignature: Ubuntu 5.4.0-144.161-generic 5.4.229
  Uname: Linux 5.4.0-144-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.26
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bbogart1051 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Sat Apr 15 09:07:33 2023
  InstallationDate: Installed on 2019-02-09 (1526 days ago)
  InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Intel(R) Client Systems NUC8i3BEH
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-144-generic 
root=UUID=9c982b36-8142-4719-810a-e06f81cab223 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-144-generic N/A
   linux-backports-modules-5.4.0-144-generic  N/A
   linux-firmware 1.187.38
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2022-06-30 (289 days ago)
  dmi.bios.date: 02/14/2023
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BECFL357.86A.0092.2023.0214.1114
  dmi.board.name: NUC8BEB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: J72693-304
  dmi.chassis.type: 3
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBECFL357.86A.0092.2023.0214.1114:bd02/14/2023:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-303:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-304:cvnIntelCorporation:ct3:cvr2.0:
  dmi.product.family: Intel NUC
  dmi.product.name: NUC8i3BEH
  dmi.product.sku: BOXNUC8i3BEH
  dmi.product.version: J72753-303
  dmi.sys.vendor: Intel(R) Client Systems

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016388/+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 2026652] Re: Suspend Broken

2023-07-09 Thread Marlen T. B.
I updated by BIOS version from BHCN44WW to BHCN45WW, and this did not
fix the problem.

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

Title:
  Suspend Broken

Status in linux-signed-lowlatency package in Ubuntu:
  New

Bug description:
  When I go to suspend my system via the UI "Suspend" option, the system
  fails to suspend. Instead it looks like its going to suspend, and then
  wakes up but with a locked screen.

  When I use `pm-suspend` from the command line, it suspends the system,
  but does not lock the screen. I have the Settings -> Privacy -> Screen
  Lock -> "Lock Screen on Suspend" setting enabled.

  I am using the Nouveau driver, with Wayland, using GNOME 44.2.
  This bug only started when I switched away from using any of the NVIDIA 
drivers, so its probably partially Nouveau related. Switching away from NVIDIA 
drivers (I tried them all) isn't an option, because they break:
  1. External monitor connectivity
  2. VMWare Horizon

  Debug info:

  1. `lsb_release -rd`
  Description:  Ubuntu 23.04
  Release:  23.04

  2. `uname -srm`
  Linux 6.2.0-1007-lowlatency x86_64

  Please let me know of any other information needed to debug this.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: linux-image-6.2.0-1007-lowlatency 6.2.0-1007.7
  ProcVersionSignature: Ubuntu 6.2.0-1007.7-lowlatency 6.2.12
  Uname: Linux 6.2.0-1007-lowlatency x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jul  9 10:26:06 2023
  InstallationDate: Installed on 2021-12-18 (567 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  SourcePackage: linux-signed-lowlatency
  UpgradeStatus: Upgraded to lunar on 2023-04-26 (73 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-lowlatency/+bug/2026652/+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 2026652] [NEW] Suspend Broken

2023-07-09 Thread Marlen T. B.
Public bug reported:

When I go to suspend my system via the UI "Suspend" option, the system
fails to suspend. Instead it looks like its going to suspend, and then
wakes up but with a locked screen.

When I use `pm-suspend` from the command line, it suspends the system,
but does not lock the screen. I have the Settings -> Privacy -> Screen
Lock -> "Lock Screen on Suspend" setting enabled.

I am using the Nouveau driver, with Wayland, using GNOME 44.2.
This bug only started when I switched away from using any of the NVIDIA 
drivers, so its probably partially Nouveau related. Switching away from NVIDIA 
drivers (I tried them all) isn't an option, because they break:
1. External monitor connectivity
2. VMWare Horizon

Debug info:

1. `lsb_release -rd`
Description:Ubuntu 23.04
Release:23.04

2. `uname -srm`
Linux 6.2.0-1007-lowlatency x86_64

Please let me know of any other information needed to debug this.

ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: linux-image-6.2.0-1007-lowlatency 6.2.0-1007.7
ProcVersionSignature: Ubuntu 6.2.0-1007.7-lowlatency 6.2.12
Uname: Linux 6.2.0-1007-lowlatency x86_64
ApportVersion: 2.26.1-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sun Jul  9 10:26:06 2023
InstallationDate: Installed on 2021-12-18 (567 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
SourcePackage: linux-signed-lowlatency
UpgradeStatus: Upgraded to lunar on 2023-04-26 (73 days ago)

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


** Tags: amd64 apport-bug lunar suspend-resume wayland-session

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

Title:
  Suspend Broken

Status in linux-signed-lowlatency package in Ubuntu:
  New

Bug description:
  When I go to suspend my system via the UI "Suspend" option, the system
  fails to suspend. Instead it looks like its going to suspend, and then
  wakes up but with a locked screen.

  When I use `pm-suspend` from the command line, it suspends the system,
  but does not lock the screen. I have the Settings -> Privacy -> Screen
  Lock -> "Lock Screen on Suspend" setting enabled.

  I am using the Nouveau driver, with Wayland, using GNOME 44.2.
  This bug only started when I switched away from using any of the NVIDIA 
drivers, so its probably partially Nouveau related. Switching away from NVIDIA 
drivers (I tried them all) isn't an option, because they break:
  1. External monitor connectivity
  2. VMWare Horizon

  Debug info:

  1. `lsb_release -rd`
  Description:  Ubuntu 23.04
  Release:  23.04

  2. `uname -srm`
  Linux 6.2.0-1007-lowlatency x86_64

  Please let me know of any other information needed to debug this.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: linux-image-6.2.0-1007-lowlatency 6.2.0-1007.7
  ProcVersionSignature: Ubuntu 6.2.0-1007.7-lowlatency 6.2.12
  Uname: Linux 6.2.0-1007-lowlatency x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jul  9 10:26:06 2023
  InstallationDate: Installed on 2021-12-18 (567 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  SourcePackage: linux-signed-lowlatency
  UpgradeStatus: Upgraded to lunar on 2023-04-26 (73 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-lowlatency/+bug/2026652/+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 2016388] Re: Kernel Panic on shutdown / reboot on NUC8I3BEH

2023-05-03 Thread b
The issue persists with 5.4.0-148

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

Title:
  Kernel Panic on shutdown / reboot on NUC8I3BEH

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Kernel 5.4.0-146 panics on power-down (e.g. shutdown -P now)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-146-generic 5.4.0-146.163
  ProcVersionSignature: Ubuntu 5.4.0-144.161-generic 5.4.229
  Uname: Linux 5.4.0-144-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.26
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bbogart1051 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Sat Apr 15 09:07:33 2023
  InstallationDate: Installed on 2019-02-09 (1526 days ago)
  InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Intel(R) Client Systems NUC8i3BEH
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-144-generic 
root=UUID=9c982b36-8142-4719-810a-e06f81cab223 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-144-generic N/A
   linux-backports-modules-5.4.0-144-generic  N/A
   linux-firmware 1.187.38
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2022-06-30 (289 days ago)
  dmi.bios.date: 02/14/2023
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BECFL357.86A.0092.2023.0214.1114
  dmi.board.name: NUC8BEB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: J72693-304
  dmi.chassis.type: 3
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBECFL357.86A.0092.2023.0214.1114:bd02/14/2023:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-303:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-304:cvnIntelCorporation:ct3:cvr2.0:
  dmi.product.family: Intel NUC
  dmi.product.name: NUC8i3BEH
  dmi.product.sku: BOXNUC8i3BEH
  dmi.product.version: J72753-303
  dmi.sys.vendor: Intel(R) Client Systems

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016388/+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 2018122] Re: My Headphone is Jack Not Being Detected After Waking From Sleep on Ubuntu 23.04

2023-05-02 Thread Marlen T. B.
Bug initially filed at https://askubuntu.com/questions/1465601/how-do-i-
fix-my-headphone-jack-not-being-detected-after-waking-from-sleep-on-ubu

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

Title:
  My Headphone is Jack Not Being Detected After Waking From Sleep on
  Ubuntu 23.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  If I sleep/wake my computer, the 3.5 mm headphone jack no-longer
  detects when its gets plugged in.

  Using Ubuntu 23.04 and pipewire:

  $ pipewire --version
  pipewire
  Compiled with libpipewire 0.3.65
  Linked with libpipewire 0.3.65

  I can work around this problem by one of two ways:
  1. After restart, my headphone jack works as expected.
  2. Restarting pipewire, then sleeping/waking my computer again. I've been 
running the following (not sure if I need both):
  ```
  systemctl --user restart pipewire
  systemctl --user restart pipewire-pulse.service
  ```

  Please let me know of any other information I should provide, and/or where I 
should actually post this bug.
  --- 
  ProblemType: Bug
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 23.04
  InstallationDate: Installed on 2021-12-18 (500 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 048d:c100 Integrated Technology Express, Inc. ITE 
Device(8910)
   Bus 001 Device 002: ID 5986:2113 Acer, Inc SunplusIT Integrated Camera
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson 
Peak (JfP)
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81T2
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   LANG=en_CA.UTF-8
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic 
root=UUID=623299a9-c6f0-4bad-91c7-51d940e93e0c ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-20-generic N/A
   linux-backports-modules-6.2.0-20-generic  N/A
   linux-firmware20230323.gitbcdcfbcf-0ubuntu1
  Tags:  lunar
  Uname: Linux 6.2.0-20-generic x86_64
  UpgradeStatus: Upgraded to lunar on 2023-04-26 (6 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 01/20/2022
  dmi.bios.release: 1.44
  dmi.bios.vendor: LENOVO
  dmi.bios.version: BHCN44WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion Y545 PG0
  dmi.ec.firmware.release: 1.44
  dmi.modalias: 
dmi:bvnLENOVO:bvrBHCN44WW:bd01/20/2022:br1.44:efr1.44:svnLENOVO:pn81T2:pvrLegionY545PG0:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegionY545PG0:skuLENOVO_MT_81T2_BU_idea_FM_LegionY545PG0:
  dmi.product.family: Legion Y545 PG0
  dmi.product.name: 81T2
  dmi.product.sku: LENOVO_MT_81T2_BU_idea_FM_Legion Y545 PG0
  dmi.product.version: Legion Y545 PG0
  dmi.sys.vendor: LENOVO

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

2023-05-02 Thread Marlen T. B.
apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/2018122/+attachment/5670466/+files/RfKill.txt

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

Title:
  My Headphone is Jack Not Being Detected After Waking From Sleep on
  Ubuntu 23.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  If I sleep/wake my computer, the 3.5 mm headphone jack no-longer
  detects when its gets plugged in.

  Using Ubuntu 23.04 and pipewire:

  $ pipewire --version
  pipewire
  Compiled with libpipewire 0.3.65
  Linked with libpipewire 0.3.65

  I can work around this problem by one of two ways:
  1. After restart, my headphone jack works as expected.
  2. Restarting pipewire, then sleeping/waking my computer again. I've been 
running the following (not sure if I need both):
  ```
  systemctl --user restart pipewire
  systemctl --user restart pipewire-pulse.service
  ```

  Please let me know of any other information I should provide, and/or where I 
should actually post this bug.
  --- 
  ProblemType: Bug
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 23.04
  InstallationDate: Installed on 2021-12-18 (500 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 048d:c100 Integrated Technology Express, Inc. ITE 
Device(8910)
   Bus 001 Device 002: ID 5986:2113 Acer, Inc SunplusIT Integrated Camera
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson 
Peak (JfP)
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81T2
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   LANG=en_CA.UTF-8
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic 
root=UUID=623299a9-c6f0-4bad-91c7-51d940e93e0c ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-20-generic N/A
   linux-backports-modules-6.2.0-20-generic  N/A
   linux-firmware20230323.gitbcdcfbcf-0ubuntu1
  Tags:  lunar
  Uname: Linux 6.2.0-20-generic x86_64
  UpgradeStatus: Upgraded to lunar on 2023-04-26 (6 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 01/20/2022
  dmi.bios.release: 1.44
  dmi.bios.vendor: LENOVO
  dmi.bios.version: BHCN44WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion Y545 PG0
  dmi.ec.firmware.release: 1.44
  dmi.modalias: 
dmi:bvnLENOVO:bvrBHCN44WW:bd01/20/2022:br1.44:efr1.44:svnLENOVO:pn81T2:pvrLegionY545PG0:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegionY545PG0:skuLENOVO_MT_81T2_BU_idea_FM_LegionY545PG0:
  dmi.product.family: Legion Y545 PG0
  dmi.product.name: 81T2
  dmi.product.sku: LENOVO_MT_81T2_BU_idea_FM_Legion Y545 PG0
  dmi.product.version: Legion Y545 PG0
  dmi.sys.vendor: LENOVO

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

2023-05-02 Thread Marlen T. B.
apport information

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

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

Title:
  My Headphone is Jack Not Being Detected After Waking From Sleep on
  Ubuntu 23.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  If I sleep/wake my computer, the 3.5 mm headphone jack no-longer
  detects when its gets plugged in.

  Using Ubuntu 23.04 and pipewire:

  $ pipewire --version
  pipewire
  Compiled with libpipewire 0.3.65
  Linked with libpipewire 0.3.65

  I can work around this problem by one of two ways:
  1. After restart, my headphone jack works as expected.
  2. Restarting pipewire, then sleeping/waking my computer again. I've been 
running the following (not sure if I need both):
  ```
  systemctl --user restart pipewire
  systemctl --user restart pipewire-pulse.service
  ```

  Please let me know of any other information I should provide, and/or where I 
should actually post this bug.
  --- 
  ProblemType: Bug
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 23.04
  InstallationDate: Installed on 2021-12-18 (500 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 048d:c100 Integrated Technology Express, Inc. ITE 
Device(8910)
   Bus 001 Device 002: ID 5986:2113 Acer, Inc SunplusIT Integrated Camera
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson 
Peak (JfP)
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81T2
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   LANG=en_CA.UTF-8
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic 
root=UUID=623299a9-c6f0-4bad-91c7-51d940e93e0c ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-20-generic N/A
   linux-backports-modules-6.2.0-20-generic  N/A
   linux-firmware20230323.gitbcdcfbcf-0ubuntu1
  Tags:  lunar
  Uname: Linux 6.2.0-20-generic x86_64
  UpgradeStatus: Upgraded to lunar on 2023-04-26 (6 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 01/20/2022
  dmi.bios.release: 1.44
  dmi.bios.vendor: LENOVO
  dmi.bios.version: BHCN44WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion Y545 PG0
  dmi.ec.firmware.release: 1.44
  dmi.modalias: 
dmi:bvnLENOVO:bvrBHCN44WW:bd01/20/2022:br1.44:efr1.44:svnLENOVO:pn81T2:pvrLegionY545PG0:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegionY545PG0:skuLENOVO_MT_81T2_BU_idea_FM_LegionY545PG0:
  dmi.product.family: Legion Y545 PG0
  dmi.product.name: 81T2
  dmi.product.sku: LENOVO_MT_81T2_BU_idea_FM_Legion Y545 PG0
  dmi.product.version: Legion Y545 PG0
  dmi.sys.vendor: LENOVO

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

2023-05-02 Thread Marlen T. B.
apport information

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

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

Title:
  My Headphone is Jack Not Being Detected After Waking From Sleep on
  Ubuntu 23.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  If I sleep/wake my computer, the 3.5 mm headphone jack no-longer
  detects when its gets plugged in.

  Using Ubuntu 23.04 and pipewire:

  $ pipewire --version
  pipewire
  Compiled with libpipewire 0.3.65
  Linked with libpipewire 0.3.65

  I can work around this problem by one of two ways:
  1. After restart, my headphone jack works as expected.
  2. Restarting pipewire, then sleeping/waking my computer again. I've been 
running the following (not sure if I need both):
  ```
  systemctl --user restart pipewire
  systemctl --user restart pipewire-pulse.service
  ```

  Please let me know of any other information I should provide, and/or where I 
should actually post this bug.
  --- 
  ProblemType: Bug
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 23.04
  InstallationDate: Installed on 2021-12-18 (500 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 048d:c100 Integrated Technology Express, Inc. ITE 
Device(8910)
   Bus 001 Device 002: ID 5986:2113 Acer, Inc SunplusIT Integrated Camera
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson 
Peak (JfP)
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81T2
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   LANG=en_CA.UTF-8
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic 
root=UUID=623299a9-c6f0-4bad-91c7-51d940e93e0c ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-20-generic N/A
   linux-backports-modules-6.2.0-20-generic  N/A
   linux-firmware20230323.gitbcdcfbcf-0ubuntu1
  Tags:  lunar
  Uname: Linux 6.2.0-20-generic x86_64
  UpgradeStatus: Upgraded to lunar on 2023-04-26 (6 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 01/20/2022
  dmi.bios.release: 1.44
  dmi.bios.vendor: LENOVO
  dmi.bios.version: BHCN44WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion Y545 PG0
  dmi.ec.firmware.release: 1.44
  dmi.modalias: 
dmi:bvnLENOVO:bvrBHCN44WW:bd01/20/2022:br1.44:efr1.44:svnLENOVO:pn81T2:pvrLegionY545PG0:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegionY545PG0:skuLENOVO_MT_81T2_BU_idea_FM_LegionY545PG0:
  dmi.product.family: Legion Y545 PG0
  dmi.product.name: 81T2
  dmi.product.sku: LENOVO_MT_81T2_BU_idea_FM_Legion Y545 PG0
  dmi.product.version: Legion Y545 PG0
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2018122/+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 2018122] Re: My Headphone is Jack Not Being Detected After Waking From Sleep on Ubuntu 23.04

2023-05-02 Thread Marlen T. B.
Bug seemed to be triggered by putting laptop to sleep with headphones
plugged in, then disconnecting while asleep. After wake/resume
headphones where no longer detected.

I can no longer recreate this bug.

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

Title:
  My Headphone is Jack Not Being Detected After Waking From Sleep on
  Ubuntu 23.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  If I sleep/wake my computer, the 3.5 mm headphone jack no-longer
  detects when its gets plugged in.

  Using Ubuntu 23.04 and pipewire:

  $ pipewire --version
  pipewire
  Compiled with libpipewire 0.3.65
  Linked with libpipewire 0.3.65

  I can work around this problem by one of two ways:
  1. After restart, my headphone jack works as expected.
  2. Restarting pipewire, then sleeping/waking my computer again. I've been 
running the following (not sure if I need both):
  ```
  systemctl --user restart pipewire
  systemctl --user restart pipewire-pulse.service
  ```

  Please let me know of any other information I should provide, and/or where I 
should actually post this bug.
  --- 
  ProblemType: Bug
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 23.04
  InstallationDate: Installed on 2021-12-18 (500 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 048d:c100 Integrated Technology Express, Inc. ITE 
Device(8910)
   Bus 001 Device 002: ID 5986:2113 Acer, Inc SunplusIT Integrated Camera
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson 
Peak (JfP)
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81T2
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   LANG=en_CA.UTF-8
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic 
root=UUID=623299a9-c6f0-4bad-91c7-51d940e93e0c ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-20-generic N/A
   linux-backports-modules-6.2.0-20-generic  N/A
   linux-firmware20230323.gitbcdcfbcf-0ubuntu1
  Tags:  lunar
  Uname: Linux 6.2.0-20-generic x86_64
  UpgradeStatus: Upgraded to lunar on 2023-04-26 (6 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 01/20/2022
  dmi.bios.release: 1.44
  dmi.bios.vendor: LENOVO
  dmi.bios.version: BHCN44WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion Y545 PG0
  dmi.ec.firmware.release: 1.44
  dmi.modalias: 
dmi:bvnLENOVO:bvrBHCN44WW:bd01/20/2022:br1.44:efr1.44:svnLENOVO:pn81T2:pvrLegionY545PG0:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegionY545PG0:skuLENOVO_MT_81T2_BU_idea_FM_LegionY545PG0:
  dmi.product.family: Legion Y545 PG0
  dmi.product.name: 81T2
  dmi.product.sku: LENOVO_MT_81T2_BU_idea_FM_Legion Y545 PG0
  dmi.product.version: Legion Y545 PG0
  dmi.sys.vendor: LENOVO

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

2023-05-02 Thread Marlen T. B.
apport information

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

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

Title:
  My Headphone is Jack Not Being Detected After Waking From Sleep on
  Ubuntu 23.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  If I sleep/wake my computer, the 3.5 mm headphone jack no-longer
  detects when its gets plugged in.

  Using Ubuntu 23.04 and pipewire:

  $ pipewire --version
  pipewire
  Compiled with libpipewire 0.3.65
  Linked with libpipewire 0.3.65

  I can work around this problem by one of two ways:
  1. After restart, my headphone jack works as expected.
  2. Restarting pipewire, then sleeping/waking my computer again. I've been 
running the following (not sure if I need both):
  ```
  systemctl --user restart pipewire
  systemctl --user restart pipewire-pulse.service
  ```

  Please let me know of any other information I should provide, and/or where I 
should actually post this bug.
  --- 
  ProblemType: Bug
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 23.04
  InstallationDate: Installed on 2021-12-18 (500 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 048d:c100 Integrated Technology Express, Inc. ITE 
Device(8910)
   Bus 001 Device 002: ID 5986:2113 Acer, Inc SunplusIT Integrated Camera
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson 
Peak (JfP)
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81T2
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   LANG=en_CA.UTF-8
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic 
root=UUID=623299a9-c6f0-4bad-91c7-51d940e93e0c ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-20-generic N/A
   linux-backports-modules-6.2.0-20-generic  N/A
   linux-firmware20230323.gitbcdcfbcf-0ubuntu1
  Tags:  lunar
  Uname: Linux 6.2.0-20-generic x86_64
  UpgradeStatus: Upgraded to lunar on 2023-04-26 (6 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 01/20/2022
  dmi.bios.release: 1.44
  dmi.bios.vendor: LENOVO
  dmi.bios.version: BHCN44WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion Y545 PG0
  dmi.ec.firmware.release: 1.44
  dmi.modalias: 
dmi:bvnLENOVO:bvrBHCN44WW:bd01/20/2022:br1.44:efr1.44:svnLENOVO:pn81T2:pvrLegionY545PG0:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegionY545PG0:skuLENOVO_MT_81T2_BU_idea_FM_LegionY545PG0:
  dmi.product.family: Legion Y545 PG0
  dmi.product.name: 81T2
  dmi.product.sku: LENOVO_MT_81T2_BU_idea_FM_Legion Y545 PG0
  dmi.product.version: Legion Y545 PG0
  dmi.sys.vendor: LENOVO

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

2023-05-02 Thread Marlen T. B.
apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/2018122/+attachment/5670468/+files/WifiSyslog.txt

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

Title:
  My Headphone is Jack Not Being Detected After Waking From Sleep on
  Ubuntu 23.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  If I sleep/wake my computer, the 3.5 mm headphone jack no-longer
  detects when its gets plugged in.

  Using Ubuntu 23.04 and pipewire:

  $ pipewire --version
  pipewire
  Compiled with libpipewire 0.3.65
  Linked with libpipewire 0.3.65

  I can work around this problem by one of two ways:
  1. After restart, my headphone jack works as expected.
  2. Restarting pipewire, then sleeping/waking my computer again. I've been 
running the following (not sure if I need both):
  ```
  systemctl --user restart pipewire
  systemctl --user restart pipewire-pulse.service
  ```

  Please let me know of any other information I should provide, and/or where I 
should actually post this bug.
  --- 
  ProblemType: Bug
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 23.04
  InstallationDate: Installed on 2021-12-18 (500 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 048d:c100 Integrated Technology Express, Inc. ITE 
Device(8910)
   Bus 001 Device 002: ID 5986:2113 Acer, Inc SunplusIT Integrated Camera
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson 
Peak (JfP)
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81T2
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   LANG=en_CA.UTF-8
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic 
root=UUID=623299a9-c6f0-4bad-91c7-51d940e93e0c ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-20-generic N/A
   linux-backports-modules-6.2.0-20-generic  N/A
   linux-firmware20230323.gitbcdcfbcf-0ubuntu1
  Tags:  lunar
  Uname: Linux 6.2.0-20-generic x86_64
  UpgradeStatus: Upgraded to lunar on 2023-04-26 (6 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 01/20/2022
  dmi.bios.release: 1.44
  dmi.bios.vendor: LENOVO
  dmi.bios.version: BHCN44WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion Y545 PG0
  dmi.ec.firmware.release: 1.44
  dmi.modalias: 
dmi:bvnLENOVO:bvrBHCN44WW:bd01/20/2022:br1.44:efr1.44:svnLENOVO:pn81T2:pvrLegionY545PG0:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegionY545PG0:skuLENOVO_MT_81T2_BU_idea_FM_LegionY545PG0:
  dmi.product.family: Legion Y545 PG0
  dmi.product.name: 81T2
  dmi.product.sku: LENOVO_MT_81T2_BU_idea_FM_Legion Y545 PG0
  dmi.product.version: Legion Y545 PG0
  dmi.sys.vendor: LENOVO

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

2023-05-02 Thread Marlen T. B.
apport information

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

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

Title:
  My Headphone is Jack Not Being Detected After Waking From Sleep on
  Ubuntu 23.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  If I sleep/wake my computer, the 3.5 mm headphone jack no-longer
  detects when its gets plugged in.

  Using Ubuntu 23.04 and pipewire:

  $ pipewire --version
  pipewire
  Compiled with libpipewire 0.3.65
  Linked with libpipewire 0.3.65

  I can work around this problem by one of two ways:
  1. After restart, my headphone jack works as expected.
  2. Restarting pipewire, then sleeping/waking my computer again. I've been 
running the following (not sure if I need both):
  ```
  systemctl --user restart pipewire
  systemctl --user restart pipewire-pulse.service
  ```

  Please let me know of any other information I should provide, and/or where I 
should actually post this bug.
  --- 
  ProblemType: Bug
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 23.04
  InstallationDate: Installed on 2021-12-18 (500 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 048d:c100 Integrated Technology Express, Inc. ITE 
Device(8910)
   Bus 001 Device 002: ID 5986:2113 Acer, Inc SunplusIT Integrated Camera
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson 
Peak (JfP)
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81T2
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   LANG=en_CA.UTF-8
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic 
root=UUID=623299a9-c6f0-4bad-91c7-51d940e93e0c ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-20-generic N/A
   linux-backports-modules-6.2.0-20-generic  N/A
   linux-firmware20230323.gitbcdcfbcf-0ubuntu1
  Tags:  lunar
  Uname: Linux 6.2.0-20-generic x86_64
  UpgradeStatus: Upgraded to lunar on 2023-04-26 (6 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 01/20/2022
  dmi.bios.release: 1.44
  dmi.bios.vendor: LENOVO
  dmi.bios.version: BHCN44WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion Y545 PG0
  dmi.ec.firmware.release: 1.44
  dmi.modalias: 
dmi:bvnLENOVO:bvrBHCN44WW:bd01/20/2022:br1.44:efr1.44:svnLENOVO:pn81T2:pvrLegionY545PG0:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegionY545PG0:skuLENOVO_MT_81T2_BU_idea_FM_LegionY545PG0:
  dmi.product.family: Legion Y545 PG0
  dmi.product.name: 81T2
  dmi.product.sku: LENOVO_MT_81T2_BU_idea_FM_Legion Y545 PG0
  dmi.product.version: Legion Y545 PG0
  dmi.sys.vendor: LENOVO

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

2023-05-02 Thread Marlen T. B.
apport information

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

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

Title:
  My Headphone is Jack Not Being Detected After Waking From Sleep on
  Ubuntu 23.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  If I sleep/wake my computer, the 3.5 mm headphone jack no-longer
  detects when its gets plugged in.

  Using Ubuntu 23.04 and pipewire:

  $ pipewire --version
  pipewire
  Compiled with libpipewire 0.3.65
  Linked with libpipewire 0.3.65

  I can work around this problem by one of two ways:
  1. After restart, my headphone jack works as expected.
  2. Restarting pipewire, then sleeping/waking my computer again. I've been 
running the following (not sure if I need both):
  ```
  systemctl --user restart pipewire
  systemctl --user restart pipewire-pulse.service
  ```

  Please let me know of any other information I should provide, and/or where I 
should actually post this bug.
  --- 
  ProblemType: Bug
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 23.04
  InstallationDate: Installed on 2021-12-18 (500 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 048d:c100 Integrated Technology Express, Inc. ITE 
Device(8910)
   Bus 001 Device 002: ID 5986:2113 Acer, Inc SunplusIT Integrated Camera
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson 
Peak (JfP)
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81T2
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   LANG=en_CA.UTF-8
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic 
root=UUID=623299a9-c6f0-4bad-91c7-51d940e93e0c ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-20-generic N/A
   linux-backports-modules-6.2.0-20-generic  N/A
   linux-firmware20230323.gitbcdcfbcf-0ubuntu1
  Tags:  lunar
  Uname: Linux 6.2.0-20-generic x86_64
  UpgradeStatus: Upgraded to lunar on 2023-04-26 (6 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 01/20/2022
  dmi.bios.release: 1.44
  dmi.bios.vendor: LENOVO
  dmi.bios.version: BHCN44WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion Y545 PG0
  dmi.ec.firmware.release: 1.44
  dmi.modalias: 
dmi:bvnLENOVO:bvrBHCN44WW:bd01/20/2022:br1.44:efr1.44:svnLENOVO:pn81T2:pvrLegionY545PG0:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegionY545PG0:skuLENOVO_MT_81T2_BU_idea_FM_LegionY545PG0:
  dmi.product.family: Legion Y545 PG0
  dmi.product.name: 81T2
  dmi.product.sku: LENOVO_MT_81T2_BU_idea_FM_Legion Y545 PG0
  dmi.product.version: Legion Y545 PG0
  dmi.sys.vendor: LENOVO

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

2023-05-02 Thread Marlen T. B.
apport information

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

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

Title:
  My Headphone is Jack Not Being Detected After Waking From Sleep on
  Ubuntu 23.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  If I sleep/wake my computer, the 3.5 mm headphone jack no-longer
  detects when its gets plugged in.

  Using Ubuntu 23.04 and pipewire:

  $ pipewire --version
  pipewire
  Compiled with libpipewire 0.3.65
  Linked with libpipewire 0.3.65

  I can work around this problem by one of two ways:
  1. After restart, my headphone jack works as expected.
  2. Restarting pipewire, then sleeping/waking my computer again. I've been 
running the following (not sure if I need both):
  ```
  systemctl --user restart pipewire
  systemctl --user restart pipewire-pulse.service
  ```

  Please let me know of any other information I should provide, and/or where I 
should actually post this bug.
  --- 
  ProblemType: Bug
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 23.04
  InstallationDate: Installed on 2021-12-18 (500 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 048d:c100 Integrated Technology Express, Inc. ITE 
Device(8910)
   Bus 001 Device 002: ID 5986:2113 Acer, Inc SunplusIT Integrated Camera
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson 
Peak (JfP)
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81T2
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   LANG=en_CA.UTF-8
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic 
root=UUID=623299a9-c6f0-4bad-91c7-51d940e93e0c ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-20-generic N/A
   linux-backports-modules-6.2.0-20-generic  N/A
   linux-firmware20230323.gitbcdcfbcf-0ubuntu1
  Tags:  lunar
  Uname: Linux 6.2.0-20-generic x86_64
  UpgradeStatus: Upgraded to lunar on 2023-04-26 (6 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 01/20/2022
  dmi.bios.release: 1.44
  dmi.bios.vendor: LENOVO
  dmi.bios.version: BHCN44WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion Y545 PG0
  dmi.ec.firmware.release: 1.44
  dmi.modalias: 
dmi:bvnLENOVO:bvrBHCN44WW:bd01/20/2022:br1.44:efr1.44:svnLENOVO:pn81T2:pvrLegionY545PG0:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegionY545PG0:skuLENOVO_MT_81T2_BU_idea_FM_LegionY545PG0:
  dmi.product.family: Legion Y545 PG0
  dmi.product.name: 81T2
  dmi.product.sku: LENOVO_MT_81T2_BU_idea_FM_Legion Y545 PG0
  dmi.product.version: Legion Y545 PG0
  dmi.sys.vendor: LENOVO

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

2023-05-02 Thread Marlen T. B.
apport information

** Attachment added: "PaInfo.txt"
   https://bugs.launchpad.net/bugs/2018122/+attachment/5670461/+files/PaInfo.txt

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

Title:
  My Headphone is Jack Not Being Detected After Waking From Sleep on
  Ubuntu 23.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  If I sleep/wake my computer, the 3.5 mm headphone jack no-longer
  detects when its gets plugged in.

  Using Ubuntu 23.04 and pipewire:

  $ pipewire --version
  pipewire
  Compiled with libpipewire 0.3.65
  Linked with libpipewire 0.3.65

  I can work around this problem by one of two ways:
  1. After restart, my headphone jack works as expected.
  2. Restarting pipewire, then sleeping/waking my computer again. I've been 
running the following (not sure if I need both):
  ```
  systemctl --user restart pipewire
  systemctl --user restart pipewire-pulse.service
  ```

  Please let me know of any other information I should provide, and/or where I 
should actually post this bug.
  --- 
  ProblemType: Bug
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 23.04
  InstallationDate: Installed on 2021-12-18 (500 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 048d:c100 Integrated Technology Express, Inc. ITE 
Device(8910)
   Bus 001 Device 002: ID 5986:2113 Acer, Inc SunplusIT Integrated Camera
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson 
Peak (JfP)
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81T2
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   LANG=en_CA.UTF-8
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic 
root=UUID=623299a9-c6f0-4bad-91c7-51d940e93e0c ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-20-generic N/A
   linux-backports-modules-6.2.0-20-generic  N/A
   linux-firmware20230323.gitbcdcfbcf-0ubuntu1
  Tags:  lunar
  Uname: Linux 6.2.0-20-generic x86_64
  UpgradeStatus: Upgraded to lunar on 2023-04-26 (6 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 01/20/2022
  dmi.bios.release: 1.44
  dmi.bios.vendor: LENOVO
  dmi.bios.version: BHCN44WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion Y545 PG0
  dmi.ec.firmware.release: 1.44
  dmi.modalias: 
dmi:bvnLENOVO:bvrBHCN44WW:bd01/20/2022:br1.44:efr1.44:svnLENOVO:pn81T2:pvrLegionY545PG0:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegionY545PG0:skuLENOVO_MT_81T2_BU_idea_FM_LegionY545PG0:
  dmi.product.family: Legion Y545 PG0
  dmi.product.name: 81T2
  dmi.product.sku: LENOVO_MT_81T2_BU_idea_FM_Legion Y545 PG0
  dmi.product.version: Legion Y545 PG0
  dmi.sys.vendor: LENOVO

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

2023-05-02 Thread Marlen T. B.
apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/2018122/+attachment/5670456/+files/IwConfig.txt

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

Title:
  My Headphone is Jack Not Being Detected After Waking From Sleep on
  Ubuntu 23.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  If I sleep/wake my computer, the 3.5 mm headphone jack no-longer
  detects when its gets plugged in.

  Using Ubuntu 23.04 and pipewire:

  $ pipewire --version
  pipewire
  Compiled with libpipewire 0.3.65
  Linked with libpipewire 0.3.65

  I can work around this problem by one of two ways:
  1. After restart, my headphone jack works as expected.
  2. Restarting pipewire, then sleeping/waking my computer again. I've been 
running the following (not sure if I need both):
  ```
  systemctl --user restart pipewire
  systemctl --user restart pipewire-pulse.service
  ```

  Please let me know of any other information I should provide, and/or where I 
should actually post this bug.
  --- 
  ProblemType: Bug
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 23.04
  InstallationDate: Installed on 2021-12-18 (500 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 048d:c100 Integrated Technology Express, Inc. ITE 
Device(8910)
   Bus 001 Device 002: ID 5986:2113 Acer, Inc SunplusIT Integrated Camera
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson 
Peak (JfP)
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81T2
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   LANG=en_CA.UTF-8
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic 
root=UUID=623299a9-c6f0-4bad-91c7-51d940e93e0c ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-20-generic N/A
   linux-backports-modules-6.2.0-20-generic  N/A
   linux-firmware20230323.gitbcdcfbcf-0ubuntu1
  Tags:  lunar
  Uname: Linux 6.2.0-20-generic x86_64
  UpgradeStatus: Upgraded to lunar on 2023-04-26 (6 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 01/20/2022
  dmi.bios.release: 1.44
  dmi.bios.vendor: LENOVO
  dmi.bios.version: BHCN44WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion Y545 PG0
  dmi.ec.firmware.release: 1.44
  dmi.modalias: 
dmi:bvnLENOVO:bvrBHCN44WW:bd01/20/2022:br1.44:efr1.44:svnLENOVO:pn81T2:pvrLegionY545PG0:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegionY545PG0:skuLENOVO_MT_81T2_BU_idea_FM_LegionY545PG0:
  dmi.product.family: Legion Y545 PG0
  dmi.product.name: 81T2
  dmi.product.sku: LENOVO_MT_81T2_BU_idea_FM_Legion Y545 PG0
  dmi.product.version: Legion Y545 PG0
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2018122/+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 2018122] Re: My Headphone is Jack Not Being Detected After Waking From Sleep on Ubuntu 23.04

2023-05-02 Thread Marlen T. B.
apport information

** Tags added: apport-collected

** Description changed:

  If I sleep/wake my computer, the 3.5 mm headphone jack no-longer detects
  when its gets plugged in.
  
  Using Ubuntu 23.04 and pipewire:
  
  $ pipewire --version
  pipewire
  Compiled with libpipewire 0.3.65
  Linked with libpipewire 0.3.65
  
  I can work around this problem by one of two ways:
  1. After restart, my headphone jack works as expected.
  2. Restarting pipewire, then sleeping/waking my computer again. I've been 
running the following (not sure if I need both):
  ```
  systemctl --user restart pipewire
  systemctl --user restart pipewire-pulse.service
  ```
  
- Please let me know of any other information I should provide, and/or
- where I should actually post this bug.
+ Please let me know of any other information I should provide, and/or where I 
should actually post this bug.
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.26.1-0ubuntu2
+ Architecture: amd64
+ CRDA: N/A
+ CasperMD5CheckResult: pass
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 23.04
+ InstallationDate: Installed on 2021-12-18 (500 days ago)
+ InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
+ Lsusb:
+  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+  Bus 001 Device 003: ID 048d:c100 Integrated Technology Express, Inc. ITE 
Device(8910)
+  Bus 001 Device 002: ID 5986:2113 Acer, Inc SunplusIT Integrated Camera
+  Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson 
Peak (JfP)
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+ MachineType: LENOVO 81T2
+ NonfreeKernelModules: nvidia_modeset nvidia
+ Package: linux (not installed)
+ ProcEnviron:
+  LANG=en_CA.UTF-8
+  LANGUAGE=en_CA:en
+  PATH=(custom, no user)
+  SHELL=/bin/bash
+  TERM=xterm-256color
+ ProcFB: 0 i915drmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic 
root=UUID=623299a9-c6f0-4bad-91c7-51d940e93e0c ro quiet splash vt.handoff=7
+ ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
+ PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
+ RelatedPackageVersions:
+  linux-restricted-modules-6.2.0-20-generic N/A
+  linux-backports-modules-6.2.0-20-generic  N/A
+  linux-firmware20230323.gitbcdcfbcf-0ubuntu1
+ Tags:  lunar
+ Uname: Linux 6.2.0-20-generic x86_64
+ UpgradeStatus: Upgraded to lunar on 2023-04-26 (6 days ago)
+ UserGroups: N/A
+ _MarkForUpload: True
+ dmi.bios.date: 01/20/2022
+ dmi.bios.release: 1.44
+ dmi.bios.vendor: LENOVO
+ dmi.bios.version: BHCN44WW
+ dmi.board.asset.tag: NO Asset Tag
+ dmi.board.name: LNVNB161216
+ dmi.board.vendor: LENOVO
+ dmi.board.version: SDK0R32862 WIN
+ dmi.chassis.asset.tag: NO Asset Tag
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: LENOVO
+ dmi.chassis.version: Legion Y545 PG0
+ dmi.ec.firmware.release: 1.44
+ dmi.modalias: 
dmi:bvnLENOVO:bvrBHCN44WW:bd01/20/2022:br1.44:efr1.44:svnLENOVO:pn81T2:pvrLegionY545PG0:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegionY545PG0:skuLENOVO_MT_81T2_BU_idea_FM_LegionY545PG0:
+ dmi.product.family: Legion Y545 PG0
+ dmi.product.name: 81T2
+ dmi.product.sku: LENOVO_MT_81T2_BU_idea_FM_Legion Y545 PG0
+ dmi.product.version: Legion Y545 PG0
+ dmi.sys.vendor: LENOVO

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/2018122/+attachment/5670453/+files/AlsaInfo.txt

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

Title:
  My Headphone is Jack Not Being Detected After Waking From Sleep on
  Ubuntu 23.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  If I sleep/wake my computer, the 3.5 mm headphone jack no-longer
  detects when its gets plugged in.

  Using Ubuntu 23.04 and pipewire:

  $ pipewire --version
  pipewire
  Compiled with libpipewire 0.3.65
  Linked with libpipewire 0.3.65

  I can work around this problem by one of two ways:
  1. After restart, my headphone jack works as expected.
  2. Restarting pipewire, then sleeping/waking my computer again. I've been 
running the following (not sure if I need both):
  ```
  systemctl --user restart pipewire
  systemctl --user restart pipewire-pulse.service
  ```

  Please let me know of any other information I should provide, and/or where I 
should actually post this bug.
  --- 
  ProblemType: Bug
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 23.04
  InstallationDate: Installed on 2021-12-18 (500 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 048d:c100 Integrated Technology Express, Inc. ITE 
Device(8910)
   Bus 001 Device 002: ID 5986:2113 

[Kernel-packages] [Bug 2018122] Lspci.txt

2023-05-02 Thread Marlen T. B.
apport information

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

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

Title:
  My Headphone is Jack Not Being Detected After Waking From Sleep on
  Ubuntu 23.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  If I sleep/wake my computer, the 3.5 mm headphone jack no-longer
  detects when its gets plugged in.

  Using Ubuntu 23.04 and pipewire:

  $ pipewire --version
  pipewire
  Compiled with libpipewire 0.3.65
  Linked with libpipewire 0.3.65

  I can work around this problem by one of two ways:
  1. After restart, my headphone jack works as expected.
  2. Restarting pipewire, then sleeping/waking my computer again. I've been 
running the following (not sure if I need both):
  ```
  systemctl --user restart pipewire
  systemctl --user restart pipewire-pulse.service
  ```

  Please let me know of any other information I should provide, and/or where I 
should actually post this bug.
  --- 
  ProblemType: Bug
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 23.04
  InstallationDate: Installed on 2021-12-18 (500 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 048d:c100 Integrated Technology Express, Inc. ITE 
Device(8910)
   Bus 001 Device 002: ID 5986:2113 Acer, Inc SunplusIT Integrated Camera
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson 
Peak (JfP)
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81T2
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   LANG=en_CA.UTF-8
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic 
root=UUID=623299a9-c6f0-4bad-91c7-51d940e93e0c ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-20-generic N/A
   linux-backports-modules-6.2.0-20-generic  N/A
   linux-firmware20230323.gitbcdcfbcf-0ubuntu1
  Tags:  lunar
  Uname: Linux 6.2.0-20-generic x86_64
  UpgradeStatus: Upgraded to lunar on 2023-04-26 (6 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 01/20/2022
  dmi.bios.release: 1.44
  dmi.bios.vendor: LENOVO
  dmi.bios.version: BHCN44WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion Y545 PG0
  dmi.ec.firmware.release: 1.44
  dmi.modalias: 
dmi:bvnLENOVO:bvrBHCN44WW:bd01/20/2022:br1.44:efr1.44:svnLENOVO:pn81T2:pvrLegionY545PG0:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegionY545PG0:skuLENOVO_MT_81T2_BU_idea_FM_LegionY545PG0:
  dmi.product.family: Legion Y545 PG0
  dmi.product.name: 81T2
  dmi.product.sku: LENOVO_MT_81T2_BU_idea_FM_Legion Y545 PG0
  dmi.product.version: Legion Y545 PG0
  dmi.sys.vendor: LENOVO

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

2023-05-02 Thread Marlen T. B.
apport information

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

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

Title:
  My Headphone is Jack Not Being Detected After Waking From Sleep on
  Ubuntu 23.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  If I sleep/wake my computer, the 3.5 mm headphone jack no-longer
  detects when its gets plugged in.

  Using Ubuntu 23.04 and pipewire:

  $ pipewire --version
  pipewire
  Compiled with libpipewire 0.3.65
  Linked with libpipewire 0.3.65

  I can work around this problem by one of two ways:
  1. After restart, my headphone jack works as expected.
  2. Restarting pipewire, then sleeping/waking my computer again. I've been 
running the following (not sure if I need both):
  ```
  systemctl --user restart pipewire
  systemctl --user restart pipewire-pulse.service
  ```

  Please let me know of any other information I should provide, and/or where I 
should actually post this bug.
  --- 
  ProblemType: Bug
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 23.04
  InstallationDate: Installed on 2021-12-18 (500 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 048d:c100 Integrated Technology Express, Inc. ITE 
Device(8910)
   Bus 001 Device 002: ID 5986:2113 Acer, Inc SunplusIT Integrated Camera
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson 
Peak (JfP)
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81T2
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   LANG=en_CA.UTF-8
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic 
root=UUID=623299a9-c6f0-4bad-91c7-51d940e93e0c ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-20-generic N/A
   linux-backports-modules-6.2.0-20-generic  N/A
   linux-firmware20230323.gitbcdcfbcf-0ubuntu1
  Tags:  lunar
  Uname: Linux 6.2.0-20-generic x86_64
  UpgradeStatus: Upgraded to lunar on 2023-04-26 (6 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 01/20/2022
  dmi.bios.release: 1.44
  dmi.bios.vendor: LENOVO
  dmi.bios.version: BHCN44WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion Y545 PG0
  dmi.ec.firmware.release: 1.44
  dmi.modalias: 
dmi:bvnLENOVO:bvrBHCN44WW:bd01/20/2022:br1.44:efr1.44:svnLENOVO:pn81T2:pvrLegionY545PG0:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegionY545PG0:skuLENOVO_MT_81T2_BU_idea_FM_LegionY545PG0:
  dmi.product.family: Legion Y545 PG0
  dmi.product.name: 81T2
  dmi.product.sku: LENOVO_MT_81T2_BU_idea_FM_Legion Y545 PG0
  dmi.product.version: Legion Y545 PG0
  dmi.sys.vendor: LENOVO

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

2023-05-02 Thread Marlen T. B.
apport information

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

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

Title:
  My Headphone is Jack Not Being Detected After Waking From Sleep on
  Ubuntu 23.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  If I sleep/wake my computer, the 3.5 mm headphone jack no-longer
  detects when its gets plugged in.

  Using Ubuntu 23.04 and pipewire:

  $ pipewire --version
  pipewire
  Compiled with libpipewire 0.3.65
  Linked with libpipewire 0.3.65

  I can work around this problem by one of two ways:
  1. After restart, my headphone jack works as expected.
  2. Restarting pipewire, then sleeping/waking my computer again. I've been 
running the following (not sure if I need both):
  ```
  systemctl --user restart pipewire
  systemctl --user restart pipewire-pulse.service
  ```

  Please let me know of any other information I should provide, and/or where I 
should actually post this bug.
  --- 
  ProblemType: Bug
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 23.04
  InstallationDate: Installed on 2021-12-18 (500 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 048d:c100 Integrated Technology Express, Inc. ITE 
Device(8910)
   Bus 001 Device 002: ID 5986:2113 Acer, Inc SunplusIT Integrated Camera
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson 
Peak (JfP)
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81T2
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   LANG=en_CA.UTF-8
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic 
root=UUID=623299a9-c6f0-4bad-91c7-51d940e93e0c ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-20-generic N/A
   linux-backports-modules-6.2.0-20-generic  N/A
   linux-firmware20230323.gitbcdcfbcf-0ubuntu1
  Tags:  lunar
  Uname: Linux 6.2.0-20-generic x86_64
  UpgradeStatus: Upgraded to lunar on 2023-04-26 (6 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 01/20/2022
  dmi.bios.release: 1.44
  dmi.bios.vendor: LENOVO
  dmi.bios.version: BHCN44WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion Y545 PG0
  dmi.ec.firmware.release: 1.44
  dmi.modalias: 
dmi:bvnLENOVO:bvrBHCN44WW:bd01/20/2022:br1.44:efr1.44:svnLENOVO:pn81T2:pvrLegionY545PG0:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegionY545PG0:skuLENOVO_MT_81T2_BU_idea_FM_LegionY545PG0:
  dmi.product.family: Legion Y545 PG0
  dmi.product.name: 81T2
  dmi.product.sku: LENOVO_MT_81T2_BU_idea_FM_Legion Y545 PG0
  dmi.product.version: Legion Y545 PG0
  dmi.sys.vendor: LENOVO

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

2023-05-02 Thread Marlen T. B.
apport information

** Attachment added: "AudioDevicesInUse.txt"
   
https://bugs.launchpad.net/bugs/2018122/+attachment/5670454/+files/AudioDevicesInUse.txt

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

Title:
  My Headphone is Jack Not Being Detected After Waking From Sleep on
  Ubuntu 23.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  If I sleep/wake my computer, the 3.5 mm headphone jack no-longer
  detects when its gets plugged in.

  Using Ubuntu 23.04 and pipewire:

  $ pipewire --version
  pipewire
  Compiled with libpipewire 0.3.65
  Linked with libpipewire 0.3.65

  I can work around this problem by one of two ways:
  1. After restart, my headphone jack works as expected.
  2. Restarting pipewire, then sleeping/waking my computer again. I've been 
running the following (not sure if I need both):
  ```
  systemctl --user restart pipewire
  systemctl --user restart pipewire-pulse.service
  ```

  Please let me know of any other information I should provide, and/or where I 
should actually post this bug.
  --- 
  ProblemType: Bug
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 23.04
  InstallationDate: Installed on 2021-12-18 (500 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 048d:c100 Integrated Technology Express, Inc. ITE 
Device(8910)
   Bus 001 Device 002: ID 5986:2113 Acer, Inc SunplusIT Integrated Camera
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson 
Peak (JfP)
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81T2
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   LANG=en_CA.UTF-8
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic 
root=UUID=623299a9-c6f0-4bad-91c7-51d940e93e0c ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-20-generic N/A
   linux-backports-modules-6.2.0-20-generic  N/A
   linux-firmware20230323.gitbcdcfbcf-0ubuntu1
  Tags:  lunar
  Uname: Linux 6.2.0-20-generic x86_64
  UpgradeStatus: Upgraded to lunar on 2023-04-26 (6 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 01/20/2022
  dmi.bios.release: 1.44
  dmi.bios.vendor: LENOVO
  dmi.bios.version: BHCN44WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion Y545 PG0
  dmi.ec.firmware.release: 1.44
  dmi.modalias: 
dmi:bvnLENOVO:bvrBHCN44WW:bd01/20/2022:br1.44:efr1.44:svnLENOVO:pn81T2:pvrLegionY545PG0:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegionY545PG0:skuLENOVO_MT_81T2_BU_idea_FM_LegionY545PG0:
  dmi.product.family: Legion Y545 PG0
  dmi.product.name: 81T2
  dmi.product.sku: LENOVO_MT_81T2_BU_idea_FM_Legion Y545 PG0
  dmi.product.version: Legion Y545 PG0
  dmi.sys.vendor: LENOVO

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

2023-05-02 Thread Marlen T. B.
apport information

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

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

Title:
  My Headphone is Jack Not Being Detected After Waking From Sleep on
  Ubuntu 23.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  If I sleep/wake my computer, the 3.5 mm headphone jack no-longer
  detects when its gets plugged in.

  Using Ubuntu 23.04 and pipewire:

  $ pipewire --version
  pipewire
  Compiled with libpipewire 0.3.65
  Linked with libpipewire 0.3.65

  I can work around this problem by one of two ways:
  1. After restart, my headphone jack works as expected.
  2. Restarting pipewire, then sleeping/waking my computer again. I've been 
running the following (not sure if I need both):
  ```
  systemctl --user restart pipewire
  systemctl --user restart pipewire-pulse.service
  ```

  Please let me know of any other information I should provide, and/or where I 
should actually post this bug.
  --- 
  ProblemType: Bug
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 23.04
  InstallationDate: Installed on 2021-12-18 (500 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 048d:c100 Integrated Technology Express, Inc. ITE 
Device(8910)
   Bus 001 Device 002: ID 5986:2113 Acer, Inc SunplusIT Integrated Camera
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson 
Peak (JfP)
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81T2
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   LANG=en_CA.UTF-8
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic 
root=UUID=623299a9-c6f0-4bad-91c7-51d940e93e0c ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-20-generic N/A
   linux-backports-modules-6.2.0-20-generic  N/A
   linux-firmware20230323.gitbcdcfbcf-0ubuntu1
  Tags:  lunar
  Uname: Linux 6.2.0-20-generic x86_64
  UpgradeStatus: Upgraded to lunar on 2023-04-26 (6 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 01/20/2022
  dmi.bios.release: 1.44
  dmi.bios.vendor: LENOVO
  dmi.bios.version: BHCN44WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion Y545 PG0
  dmi.ec.firmware.release: 1.44
  dmi.modalias: 
dmi:bvnLENOVO:bvrBHCN44WW:bd01/20/2022:br1.44:efr1.44:svnLENOVO:pn81T2:pvrLegionY545PG0:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegionY545PG0:skuLENOVO_MT_81T2_BU_idea_FM_LegionY545PG0:
  dmi.product.family: Legion Y545 PG0
  dmi.product.name: 81T2
  dmi.product.sku: LENOVO_MT_81T2_BU_idea_FM_Legion Y545 PG0
  dmi.product.version: Legion Y545 PG0
  dmi.sys.vendor: LENOVO

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

2023-05-02 Thread Marlen T. B.
apport information

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

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

Title:
  My Headphone is Jack Not Being Detected After Waking From Sleep on
  Ubuntu 23.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  If I sleep/wake my computer, the 3.5 mm headphone jack no-longer
  detects when its gets plugged in.

  Using Ubuntu 23.04 and pipewire:

  $ pipewire --version
  pipewire
  Compiled with libpipewire 0.3.65
  Linked with libpipewire 0.3.65

  I can work around this problem by one of two ways:
  1. After restart, my headphone jack works as expected.
  2. Restarting pipewire, then sleeping/waking my computer again. I've been 
running the following (not sure if I need both):
  ```
  systemctl --user restart pipewire
  systemctl --user restart pipewire-pulse.service
  ```

  Please let me know of any other information I should provide, and/or where I 
should actually post this bug.
  --- 
  ProblemType: Bug
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 23.04
  InstallationDate: Installed on 2021-12-18 (500 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 048d:c100 Integrated Technology Express, Inc. ITE 
Device(8910)
   Bus 001 Device 002: ID 5986:2113 Acer, Inc SunplusIT Integrated Camera
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson 
Peak (JfP)
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81T2
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   LANG=en_CA.UTF-8
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic 
root=UUID=623299a9-c6f0-4bad-91c7-51d940e93e0c ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-20-generic N/A
   linux-backports-modules-6.2.0-20-generic  N/A
   linux-firmware20230323.gitbcdcfbcf-0ubuntu1
  Tags:  lunar
  Uname: Linux 6.2.0-20-generic x86_64
  UpgradeStatus: Upgraded to lunar on 2023-04-26 (6 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 01/20/2022
  dmi.bios.release: 1.44
  dmi.bios.vendor: LENOVO
  dmi.bios.version: BHCN44WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion Y545 PG0
  dmi.ec.firmware.release: 1.44
  dmi.modalias: 
dmi:bvnLENOVO:bvrBHCN44WW:bd01/20/2022:br1.44:efr1.44:svnLENOVO:pn81T2:pvrLegionY545PG0:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegionY545PG0:skuLENOVO_MT_81T2_BU_idea_FM_LegionY545PG0:
  dmi.product.family: Legion Y545 PG0
  dmi.product.name: 81T2
  dmi.product.sku: LENOVO_MT_81T2_BU_idea_FM_Legion Y545 PG0
  dmi.product.version: Legion Y545 PG0
  dmi.sys.vendor: LENOVO

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

2023-05-02 Thread Marlen T. B.
** Attachment added: "acpidump.txt"
   
https://bugs.launchpad.net/bugs/2018122/+attachment/5670452/+files/acpidump.txt

** Description changed:

  If I sleep/wake my computer, the 3.5 mm headphone jack no-longer detects
  when its gets plugged in.
  
  Using Ubuntu 23.04 and pipewire:
  
  $ pipewire --version
  pipewire
  Compiled with libpipewire 0.3.65
  Linked with libpipewire 0.3.65
  
  I can work around this problem by one of two ways:
  1. After restart, my headphone jack works as expected.
  2. Restarting pipewire, then sleeping/waking my computer again. I've been 
running the following (not sure if I need both):
  ```
  systemctl --user restart pipewire
  systemctl --user restart pipewire-pulse.service
  ```
  
- Please let me know of any other information I should provide, and/or where I 
should actually post this bug.
- --- 
- ProblemType: Bug
- ApportVersion: 2.26.1-0ubuntu2
- Architecture: amd64
- AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  marlen72779 F wireplumber
-  /dev/snd/controlC1:  marlen72779 F wireplumber
-  /dev/snd/seq:marlen72768 F pipewire
- CRDA: N/A
- CasperMD5CheckResult: pass
- CurrentDesktop: ubuntu:GNOME
- DistroRelease: Ubuntu 23.04
- InstallationDate: Installed on 2021-12-18 (500 days ago)
- InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
- Lsusb:
-  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
-  Bus 001 Device 003: ID 048d:c100 Integrated Technology Express, Inc. ITE 
Device(8910)
-  Bus 001 Device 002: ID 5986:2113 Acer, Inc SunplusIT Integrated Camera
-  Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson 
Peak (JfP)
-  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
- MachineType: LENOVO 81T2
- NonfreeKernelModules: nvidia_modeset nvidia
- Package: linux (not installed)
- ProcEnviron:
-  LANG=en_CA.UTF-8
-  LANGUAGE=en_CA:en
-  PATH=(custom, no user)
-  SHELL=/bin/bash
-  TERM=xterm-256color
- ProcFB: 0 i915drmfb
- ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic 
root=UUID=623299a9-c6f0-4bad-91c7-51d940e93e0c ro quiet splash vt.handoff=7
- ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
- PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
- RelatedPackageVersions:
-  linux-restricted-modules-6.2.0-20-generic N/A
-  linux-backports-modules-6.2.0-20-generic  N/A
-  linux-firmware20230323.gitbcdcfbcf-0ubuntu1
- Tags:  lunar
- Uname: Linux 6.2.0-20-generic x86_64
- UpgradeStatus: Upgraded to lunar on 2023-04-26 (6 days ago)
- UserGroups: N/A
- _MarkForUpload: True
- dmi.bios.date: 01/20/2022
- dmi.bios.release: 1.44
- dmi.bios.vendor: LENOVO
- dmi.bios.version: BHCN44WW
- dmi.board.asset.tag: NO Asset Tag
- dmi.board.name: LNVNB161216
- dmi.board.vendor: LENOVO
- dmi.board.version: SDK0R32862 WIN
- dmi.chassis.asset.tag: NO Asset Tag
- dmi.chassis.type: 10
- dmi.chassis.vendor: LENOVO
- dmi.chassis.version: Legion Y545 PG0
- dmi.ec.firmware.release: 1.44
- dmi.modalias: 
dmi:bvnLENOVO:bvrBHCN44WW:bd01/20/2022:br1.44:efr1.44:svnLENOVO:pn81T2:pvrLegionY545PG0:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegionY545PG0:skuLENOVO_MT_81T2_BU_idea_FM_LegionY545PG0:
- dmi.product.family: Legion Y545 PG0
- dmi.product.name: 81T2
- dmi.product.sku: LENOVO_MT_81T2_BU_idea_FM_Legion Y545 PG0
- dmi.product.version: Legion Y545 PG0
- dmi.sys.vendor: LENOVO
+ Please let me know of any other information I should provide, and/or
+ where I should actually post this bug.

** Attachment removed: "acpidump.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2018122/+attachment/5670452/+files/acpidump.txt

** Attachment removed: "WifiSyslog.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2018122/+attachment/5670451/+files/WifiSyslog.txt

** Attachment removed: "UdevDb.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2018122/+attachment/5670450/+files/UdevDb.txt

** Attachment removed: "RfKill.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2018122/+attachment/5670449/+files/RfKill.txt

** Attachment removed: "ProcModules.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2018122/+attachment/5670448/+files/ProcModules.txt

** Attachment removed: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2018122/+attachment/5670447/+files/ProcInterrupts.txt

** Attachment removed: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2018122/+attachment/5670446/+files/ProcCpuinfoMinimal.txt

** Attachment removed: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2018122/+attachment/5670445/+files/ProcCpuinfo.txt

** Attachment removed: "AlsaInfo.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2018122/+attachment/5670437/+files/AlsaInfo.txt

** Attachment removed: 

[Kernel-packages] [Bug 2018122] WifiSyslog.txt

2023-05-02 Thread Marlen T. B.
** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/2018122/+attachment/5670451/+files/WifiSyslog.txt

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

Title:
  My Headphone is Jack Not Being Detected After Waking From Sleep on
  Ubuntu 23.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  If I sleep/wake my computer, the 3.5 mm headphone jack no-longer
  detects when its gets plugged in.

  Using Ubuntu 23.04 and pipewire:

  $ pipewire --version
  pipewire
  Compiled with libpipewire 0.3.65
  Linked with libpipewire 0.3.65

  I can work around this problem by one of two ways:
  1. After restart, my headphone jack works as expected.
  2. Restarting pipewire, then sleeping/waking my computer again. I've been 
running the following (not sure if I need both):
  ```
  systemctl --user restart pipewire
  systemctl --user restart pipewire-pulse.service
  ```

  Please let me know of any other information I should provide, and/or where I 
should actually post this bug.
  --- 
  ProblemType: Bug
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 23.04
  InstallationDate: Installed on 2021-12-18 (500 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 048d:c100 Integrated Technology Express, Inc. ITE 
Device(8910)
   Bus 001 Device 002: ID 5986:2113 Acer, Inc SunplusIT Integrated Camera
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson 
Peak (JfP)
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81T2
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   LANG=en_CA.UTF-8
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic 
root=UUID=623299a9-c6f0-4bad-91c7-51d940e93e0c ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-20-generic N/A
   linux-backports-modules-6.2.0-20-generic  N/A
   linux-firmware20230323.gitbcdcfbcf-0ubuntu1
  Tags:  lunar
  Uname: Linux 6.2.0-20-generic x86_64
  UpgradeStatus: Upgraded to lunar on 2023-04-26 (6 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 01/20/2022
  dmi.bios.release: 1.44
  dmi.bios.vendor: LENOVO
  dmi.bios.version: BHCN44WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion Y545 PG0
  dmi.ec.firmware.release: 1.44
  dmi.modalias: 
dmi:bvnLENOVO:bvrBHCN44WW:bd01/20/2022:br1.44:efr1.44:svnLENOVO:pn81T2:pvrLegionY545PG0:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegionY545PG0:skuLENOVO_MT_81T2_BU_idea_FM_LegionY545PG0:
  dmi.product.family: Legion Y545 PG0
  dmi.product.name: 81T2
  dmi.product.sku: LENOVO_MT_81T2_BU_idea_FM_Legion Y545 PG0
  dmi.product.version: Legion Y545 PG0
  dmi.sys.vendor: LENOVO

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

2023-05-02 Thread Marlen T. B.
** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/2018122/+attachment/5670450/+files/UdevDb.txt

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

Title:
  My Headphone is Jack Not Being Detected After Waking From Sleep on
  Ubuntu 23.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  If I sleep/wake my computer, the 3.5 mm headphone jack no-longer
  detects when its gets plugged in.

  Using Ubuntu 23.04 and pipewire:

  $ pipewire --version
  pipewire
  Compiled with libpipewire 0.3.65
  Linked with libpipewire 0.3.65

  I can work around this problem by one of two ways:
  1. After restart, my headphone jack works as expected.
  2. Restarting pipewire, then sleeping/waking my computer again. I've been 
running the following (not sure if I need both):
  ```
  systemctl --user restart pipewire
  systemctl --user restart pipewire-pulse.service
  ```

  Please let me know of any other information I should provide, and/or where I 
should actually post this bug.
  --- 
  ProblemType: Bug
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 23.04
  InstallationDate: Installed on 2021-12-18 (500 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 048d:c100 Integrated Technology Express, Inc. ITE 
Device(8910)
   Bus 001 Device 002: ID 5986:2113 Acer, Inc SunplusIT Integrated Camera
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson 
Peak (JfP)
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81T2
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   LANG=en_CA.UTF-8
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic 
root=UUID=623299a9-c6f0-4bad-91c7-51d940e93e0c ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-20-generic N/A
   linux-backports-modules-6.2.0-20-generic  N/A
   linux-firmware20230323.gitbcdcfbcf-0ubuntu1
  Tags:  lunar
  Uname: Linux 6.2.0-20-generic x86_64
  UpgradeStatus: Upgraded to lunar on 2023-04-26 (6 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 01/20/2022
  dmi.bios.release: 1.44
  dmi.bios.vendor: LENOVO
  dmi.bios.version: BHCN44WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion Y545 PG0
  dmi.ec.firmware.release: 1.44
  dmi.modalias: 
dmi:bvnLENOVO:bvrBHCN44WW:bd01/20/2022:br1.44:efr1.44:svnLENOVO:pn81T2:pvrLegionY545PG0:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegionY545PG0:skuLENOVO_MT_81T2_BU_idea_FM_LegionY545PG0:
  dmi.product.family: Legion Y545 PG0
  dmi.product.name: 81T2
  dmi.product.sku: LENOVO_MT_81T2_BU_idea_FM_Legion Y545 PG0
  dmi.product.version: Legion Y545 PG0
  dmi.sys.vendor: LENOVO

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

2023-05-02 Thread Marlen T. B.
** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/2018122/+attachment/5670449/+files/RfKill.txt

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

Title:
  My Headphone is Jack Not Being Detected After Waking From Sleep on
  Ubuntu 23.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  If I sleep/wake my computer, the 3.5 mm headphone jack no-longer
  detects when its gets plugged in.

  Using Ubuntu 23.04 and pipewire:

  $ pipewire --version
  pipewire
  Compiled with libpipewire 0.3.65
  Linked with libpipewire 0.3.65

  I can work around this problem by one of two ways:
  1. After restart, my headphone jack works as expected.
  2. Restarting pipewire, then sleeping/waking my computer again. I've been 
running the following (not sure if I need both):
  ```
  systemctl --user restart pipewire
  systemctl --user restart pipewire-pulse.service
  ```

  Please let me know of any other information I should provide, and/or where I 
should actually post this bug.
  --- 
  ProblemType: Bug
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 23.04
  InstallationDate: Installed on 2021-12-18 (500 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 048d:c100 Integrated Technology Express, Inc. ITE 
Device(8910)
   Bus 001 Device 002: ID 5986:2113 Acer, Inc SunplusIT Integrated Camera
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson 
Peak (JfP)
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81T2
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   LANG=en_CA.UTF-8
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic 
root=UUID=623299a9-c6f0-4bad-91c7-51d940e93e0c ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-20-generic N/A
   linux-backports-modules-6.2.0-20-generic  N/A
   linux-firmware20230323.gitbcdcfbcf-0ubuntu1
  Tags:  lunar
  Uname: Linux 6.2.0-20-generic x86_64
  UpgradeStatus: Upgraded to lunar on 2023-04-26 (6 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 01/20/2022
  dmi.bios.release: 1.44
  dmi.bios.vendor: LENOVO
  dmi.bios.version: BHCN44WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion Y545 PG0
  dmi.ec.firmware.release: 1.44
  dmi.modalias: 
dmi:bvnLENOVO:bvrBHCN44WW:bd01/20/2022:br1.44:efr1.44:svnLENOVO:pn81T2:pvrLegionY545PG0:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegionY545PG0:skuLENOVO_MT_81T2_BU_idea_FM_LegionY545PG0:
  dmi.product.family: Legion Y545 PG0
  dmi.product.name: 81T2
  dmi.product.sku: LENOVO_MT_81T2_BU_idea_FM_Legion Y545 PG0
  dmi.product.version: Legion Y545 PG0
  dmi.sys.vendor: LENOVO

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

2023-05-02 Thread Marlen T. B.
** Attachment added: "Lspci-vt.txt"
   
https://bugs.launchpad.net/bugs/2018122/+attachment/5670441/+files/Lspci-vt.txt

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

Title:
  My Headphone is Jack Not Being Detected After Waking From Sleep on
  Ubuntu 23.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  If I sleep/wake my computer, the 3.5 mm headphone jack no-longer
  detects when its gets plugged in.

  Using Ubuntu 23.04 and pipewire:

  $ pipewire --version
  pipewire
  Compiled with libpipewire 0.3.65
  Linked with libpipewire 0.3.65

  I can work around this problem by one of two ways:
  1. After restart, my headphone jack works as expected.
  2. Restarting pipewire, then sleeping/waking my computer again. I've been 
running the following (not sure if I need both):
  ```
  systemctl --user restart pipewire
  systemctl --user restart pipewire-pulse.service
  ```

  Please let me know of any other information I should provide, and/or where I 
should actually post this bug.
  --- 
  ProblemType: Bug
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 23.04
  InstallationDate: Installed on 2021-12-18 (500 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 048d:c100 Integrated Technology Express, Inc. ITE 
Device(8910)
   Bus 001 Device 002: ID 5986:2113 Acer, Inc SunplusIT Integrated Camera
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson 
Peak (JfP)
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81T2
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   LANG=en_CA.UTF-8
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic 
root=UUID=623299a9-c6f0-4bad-91c7-51d940e93e0c ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-20-generic N/A
   linux-backports-modules-6.2.0-20-generic  N/A
   linux-firmware20230323.gitbcdcfbcf-0ubuntu1
  Tags:  lunar
  Uname: Linux 6.2.0-20-generic x86_64
  UpgradeStatus: Upgraded to lunar on 2023-04-26 (6 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 01/20/2022
  dmi.bios.release: 1.44
  dmi.bios.vendor: LENOVO
  dmi.bios.version: BHCN44WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion Y545 PG0
  dmi.ec.firmware.release: 1.44
  dmi.modalias: 
dmi:bvnLENOVO:bvrBHCN44WW:bd01/20/2022:br1.44:efr1.44:svnLENOVO:pn81T2:pvrLegionY545PG0:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegionY545PG0:skuLENOVO_MT_81T2_BU_idea_FM_LegionY545PG0:
  dmi.product.family: Legion Y545 PG0
  dmi.product.name: 81T2
  dmi.product.sku: LENOVO_MT_81T2_BU_idea_FM_Legion Y545 PG0
  dmi.product.version: Legion Y545 PG0
  dmi.sys.vendor: LENOVO

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

2023-05-02 Thread Marlen T. B.
** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/2018122/+attachment/5670447/+files/ProcInterrupts.txt

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

Title:
  My Headphone is Jack Not Being Detected After Waking From Sleep on
  Ubuntu 23.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  If I sleep/wake my computer, the 3.5 mm headphone jack no-longer
  detects when its gets plugged in.

  Using Ubuntu 23.04 and pipewire:

  $ pipewire --version
  pipewire
  Compiled with libpipewire 0.3.65
  Linked with libpipewire 0.3.65

  I can work around this problem by one of two ways:
  1. After restart, my headphone jack works as expected.
  2. Restarting pipewire, then sleeping/waking my computer again. I've been 
running the following (not sure if I need both):
  ```
  systemctl --user restart pipewire
  systemctl --user restart pipewire-pulse.service
  ```

  Please let me know of any other information I should provide, and/or where I 
should actually post this bug.
  --- 
  ProblemType: Bug
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 23.04
  InstallationDate: Installed on 2021-12-18 (500 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 048d:c100 Integrated Technology Express, Inc. ITE 
Device(8910)
   Bus 001 Device 002: ID 5986:2113 Acer, Inc SunplusIT Integrated Camera
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson 
Peak (JfP)
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81T2
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   LANG=en_CA.UTF-8
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic 
root=UUID=623299a9-c6f0-4bad-91c7-51d940e93e0c ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-20-generic N/A
   linux-backports-modules-6.2.0-20-generic  N/A
   linux-firmware20230323.gitbcdcfbcf-0ubuntu1
  Tags:  lunar
  Uname: Linux 6.2.0-20-generic x86_64
  UpgradeStatus: Upgraded to lunar on 2023-04-26 (6 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 01/20/2022
  dmi.bios.release: 1.44
  dmi.bios.vendor: LENOVO
  dmi.bios.version: BHCN44WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion Y545 PG0
  dmi.ec.firmware.release: 1.44
  dmi.modalias: 
dmi:bvnLENOVO:bvrBHCN44WW:bd01/20/2022:br1.44:efr1.44:svnLENOVO:pn81T2:pvrLegionY545PG0:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegionY545PG0:skuLENOVO_MT_81T2_BU_idea_FM_LegionY545PG0:
  dmi.product.family: Legion Y545 PG0
  dmi.product.name: 81T2
  dmi.product.sku: LENOVO_MT_81T2_BU_idea_FM_Legion Y545 PG0
  dmi.product.version: Legion Y545 PG0
  dmi.sys.vendor: LENOVO

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

2023-05-02 Thread Marlen T. B.
** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/2018122/+attachment/5670448/+files/ProcModules.txt

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

Title:
  My Headphone is Jack Not Being Detected After Waking From Sleep on
  Ubuntu 23.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  If I sleep/wake my computer, the 3.5 mm headphone jack no-longer
  detects when its gets plugged in.

  Using Ubuntu 23.04 and pipewire:

  $ pipewire --version
  pipewire
  Compiled with libpipewire 0.3.65
  Linked with libpipewire 0.3.65

  I can work around this problem by one of two ways:
  1. After restart, my headphone jack works as expected.
  2. Restarting pipewire, then sleeping/waking my computer again. I've been 
running the following (not sure if I need both):
  ```
  systemctl --user restart pipewire
  systemctl --user restart pipewire-pulse.service
  ```

  Please let me know of any other information I should provide, and/or where I 
should actually post this bug.
  --- 
  ProblemType: Bug
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 23.04
  InstallationDate: Installed on 2021-12-18 (500 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 048d:c100 Integrated Technology Express, Inc. ITE 
Device(8910)
   Bus 001 Device 002: ID 5986:2113 Acer, Inc SunplusIT Integrated Camera
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson 
Peak (JfP)
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81T2
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   LANG=en_CA.UTF-8
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic 
root=UUID=623299a9-c6f0-4bad-91c7-51d940e93e0c ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-20-generic N/A
   linux-backports-modules-6.2.0-20-generic  N/A
   linux-firmware20230323.gitbcdcfbcf-0ubuntu1
  Tags:  lunar
  Uname: Linux 6.2.0-20-generic x86_64
  UpgradeStatus: Upgraded to lunar on 2023-04-26 (6 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 01/20/2022
  dmi.bios.release: 1.44
  dmi.bios.vendor: LENOVO
  dmi.bios.version: BHCN44WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion Y545 PG0
  dmi.ec.firmware.release: 1.44
  dmi.modalias: 
dmi:bvnLENOVO:bvrBHCN44WW:bd01/20/2022:br1.44:efr1.44:svnLENOVO:pn81T2:pvrLegionY545PG0:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegionY545PG0:skuLENOVO_MT_81T2_BU_idea_FM_LegionY545PG0:
  dmi.product.family: Legion Y545 PG0
  dmi.product.name: 81T2
  dmi.product.sku: LENOVO_MT_81T2_BU_idea_FM_Legion Y545 PG0
  dmi.product.version: Legion Y545 PG0
  dmi.sys.vendor: LENOVO

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

2023-05-02 Thread Marlen T. B.
** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/2018122/+attachment/5670446/+files/ProcCpuinfoMinimal.txt

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

Title:
  My Headphone is Jack Not Being Detected After Waking From Sleep on
  Ubuntu 23.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  If I sleep/wake my computer, the 3.5 mm headphone jack no-longer
  detects when its gets plugged in.

  Using Ubuntu 23.04 and pipewire:

  $ pipewire --version
  pipewire
  Compiled with libpipewire 0.3.65
  Linked with libpipewire 0.3.65

  I can work around this problem by one of two ways:
  1. After restart, my headphone jack works as expected.
  2. Restarting pipewire, then sleeping/waking my computer again. I've been 
running the following (not sure if I need both):
  ```
  systemctl --user restart pipewire
  systemctl --user restart pipewire-pulse.service
  ```

  Please let me know of any other information I should provide, and/or where I 
should actually post this bug.
  --- 
  ProblemType: Bug
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 23.04
  InstallationDate: Installed on 2021-12-18 (500 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 048d:c100 Integrated Technology Express, Inc. ITE 
Device(8910)
   Bus 001 Device 002: ID 5986:2113 Acer, Inc SunplusIT Integrated Camera
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson 
Peak (JfP)
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81T2
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   LANG=en_CA.UTF-8
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic 
root=UUID=623299a9-c6f0-4bad-91c7-51d940e93e0c ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-20-generic N/A
   linux-backports-modules-6.2.0-20-generic  N/A
   linux-firmware20230323.gitbcdcfbcf-0ubuntu1
  Tags:  lunar
  Uname: Linux 6.2.0-20-generic x86_64
  UpgradeStatus: Upgraded to lunar on 2023-04-26 (6 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 01/20/2022
  dmi.bios.release: 1.44
  dmi.bios.vendor: LENOVO
  dmi.bios.version: BHCN44WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion Y545 PG0
  dmi.ec.firmware.release: 1.44
  dmi.modalias: 
dmi:bvnLENOVO:bvrBHCN44WW:bd01/20/2022:br1.44:efr1.44:svnLENOVO:pn81T2:pvrLegionY545PG0:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegionY545PG0:skuLENOVO_MT_81T2_BU_idea_FM_LegionY545PG0:
  dmi.product.family: Legion Y545 PG0
  dmi.product.name: 81T2
  dmi.product.sku: LENOVO_MT_81T2_BU_idea_FM_Legion Y545 PG0
  dmi.product.version: Legion Y545 PG0
  dmi.sys.vendor: LENOVO

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

2023-05-02 Thread Marlen T. B.
** Attachment added: "Lsusb-t.txt"
   
https://bugs.launchpad.net/bugs/2018122/+attachment/5670442/+files/Lsusb-t.txt

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

Title:
  My Headphone is Jack Not Being Detected After Waking From Sleep on
  Ubuntu 23.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  If I sleep/wake my computer, the 3.5 mm headphone jack no-longer
  detects when its gets plugged in.

  Using Ubuntu 23.04 and pipewire:

  $ pipewire --version
  pipewire
  Compiled with libpipewire 0.3.65
  Linked with libpipewire 0.3.65

  I can work around this problem by one of two ways:
  1. After restart, my headphone jack works as expected.
  2. Restarting pipewire, then sleeping/waking my computer again. I've been 
running the following (not sure if I need both):
  ```
  systemctl --user restart pipewire
  systemctl --user restart pipewire-pulse.service
  ```

  Please let me know of any other information I should provide, and/or where I 
should actually post this bug.
  --- 
  ProblemType: Bug
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 23.04
  InstallationDate: Installed on 2021-12-18 (500 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 048d:c100 Integrated Technology Express, Inc. ITE 
Device(8910)
   Bus 001 Device 002: ID 5986:2113 Acer, Inc SunplusIT Integrated Camera
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson 
Peak (JfP)
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81T2
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   LANG=en_CA.UTF-8
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic 
root=UUID=623299a9-c6f0-4bad-91c7-51d940e93e0c ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-20-generic N/A
   linux-backports-modules-6.2.0-20-generic  N/A
   linux-firmware20230323.gitbcdcfbcf-0ubuntu1
  Tags:  lunar
  Uname: Linux 6.2.0-20-generic x86_64
  UpgradeStatus: Upgraded to lunar on 2023-04-26 (6 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 01/20/2022
  dmi.bios.release: 1.44
  dmi.bios.vendor: LENOVO
  dmi.bios.version: BHCN44WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion Y545 PG0
  dmi.ec.firmware.release: 1.44
  dmi.modalias: 
dmi:bvnLENOVO:bvrBHCN44WW:bd01/20/2022:br1.44:efr1.44:svnLENOVO:pn81T2:pvrLegionY545PG0:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegionY545PG0:skuLENOVO_MT_81T2_BU_idea_FM_LegionY545PG0:
  dmi.product.family: Legion Y545 PG0
  dmi.product.name: 81T2
  dmi.product.sku: LENOVO_MT_81T2_BU_idea_FM_Legion Y545 PG0
  dmi.product.version: Legion Y545 PG0
  dmi.sys.vendor: LENOVO

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

2023-05-02 Thread Marlen T. B.
** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/2018122/+attachment/5670440/+files/Lspci.txt

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

Title:
  My Headphone is Jack Not Being Detected After Waking From Sleep on
  Ubuntu 23.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  If I sleep/wake my computer, the 3.5 mm headphone jack no-longer
  detects when its gets plugged in.

  Using Ubuntu 23.04 and pipewire:

  $ pipewire --version
  pipewire
  Compiled with libpipewire 0.3.65
  Linked with libpipewire 0.3.65

  I can work around this problem by one of two ways:
  1. After restart, my headphone jack works as expected.
  2. Restarting pipewire, then sleeping/waking my computer again. I've been 
running the following (not sure if I need both):
  ```
  systemctl --user restart pipewire
  systemctl --user restart pipewire-pulse.service
  ```

  Please let me know of any other information I should provide, and/or where I 
should actually post this bug.
  --- 
  ProblemType: Bug
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 23.04
  InstallationDate: Installed on 2021-12-18 (500 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 048d:c100 Integrated Technology Express, Inc. ITE 
Device(8910)
   Bus 001 Device 002: ID 5986:2113 Acer, Inc SunplusIT Integrated Camera
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson 
Peak (JfP)
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81T2
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   LANG=en_CA.UTF-8
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic 
root=UUID=623299a9-c6f0-4bad-91c7-51d940e93e0c ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-20-generic N/A
   linux-backports-modules-6.2.0-20-generic  N/A
   linux-firmware20230323.gitbcdcfbcf-0ubuntu1
  Tags:  lunar
  Uname: Linux 6.2.0-20-generic x86_64
  UpgradeStatus: Upgraded to lunar on 2023-04-26 (6 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 01/20/2022
  dmi.bios.release: 1.44
  dmi.bios.vendor: LENOVO
  dmi.bios.version: BHCN44WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion Y545 PG0
  dmi.ec.firmware.release: 1.44
  dmi.modalias: 
dmi:bvnLENOVO:bvrBHCN44WW:bd01/20/2022:br1.44:efr1.44:svnLENOVO:pn81T2:pvrLegionY545PG0:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegionY545PG0:skuLENOVO_MT_81T2_BU_idea_FM_LegionY545PG0:
  dmi.product.family: Legion Y545 PG0
  dmi.product.name: 81T2
  dmi.product.sku: LENOVO_MT_81T2_BU_idea_FM_Legion Y545 PG0
  dmi.product.version: Legion Y545 PG0
  dmi.sys.vendor: LENOVO

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

2023-05-02 Thread Marlen T. B.
** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/2018122/+attachment/5670445/+files/ProcCpuinfo.txt

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

Title:
  My Headphone is Jack Not Being Detected After Waking From Sleep on
  Ubuntu 23.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  If I sleep/wake my computer, the 3.5 mm headphone jack no-longer
  detects when its gets plugged in.

  Using Ubuntu 23.04 and pipewire:

  $ pipewire --version
  pipewire
  Compiled with libpipewire 0.3.65
  Linked with libpipewire 0.3.65

  I can work around this problem by one of two ways:
  1. After restart, my headphone jack works as expected.
  2. Restarting pipewire, then sleeping/waking my computer again. I've been 
running the following (not sure if I need both):
  ```
  systemctl --user restart pipewire
  systemctl --user restart pipewire-pulse.service
  ```

  Please let me know of any other information I should provide, and/or where I 
should actually post this bug.
  --- 
  ProblemType: Bug
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 23.04
  InstallationDate: Installed on 2021-12-18 (500 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 048d:c100 Integrated Technology Express, Inc. ITE 
Device(8910)
   Bus 001 Device 002: ID 5986:2113 Acer, Inc SunplusIT Integrated Camera
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson 
Peak (JfP)
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81T2
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   LANG=en_CA.UTF-8
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic 
root=UUID=623299a9-c6f0-4bad-91c7-51d940e93e0c ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-20-generic N/A
   linux-backports-modules-6.2.0-20-generic  N/A
   linux-firmware20230323.gitbcdcfbcf-0ubuntu1
  Tags:  lunar
  Uname: Linux 6.2.0-20-generic x86_64
  UpgradeStatus: Upgraded to lunar on 2023-04-26 (6 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 01/20/2022
  dmi.bios.release: 1.44
  dmi.bios.vendor: LENOVO
  dmi.bios.version: BHCN44WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion Y545 PG0
  dmi.ec.firmware.release: 1.44
  dmi.modalias: 
dmi:bvnLENOVO:bvrBHCN44WW:bd01/20/2022:br1.44:efr1.44:svnLENOVO:pn81T2:pvrLegionY545PG0:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegionY545PG0:skuLENOVO_MT_81T2_BU_idea_FM_LegionY545PG0:
  dmi.product.family: Legion Y545 PG0
  dmi.product.name: 81T2
  dmi.product.sku: LENOVO_MT_81T2_BU_idea_FM_Legion Y545 PG0
  dmi.product.version: Legion Y545 PG0
  dmi.sys.vendor: LENOVO

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

2023-05-02 Thread Marlen T. B.
** Attachment added: "PaInfo.txt"
   https://bugs.launchpad.net/bugs/2018122/+attachment/5670444/+files/PaInfo.txt

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

Title:
  My Headphone is Jack Not Being Detected After Waking From Sleep on
  Ubuntu 23.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  If I sleep/wake my computer, the 3.5 mm headphone jack no-longer
  detects when its gets plugged in.

  Using Ubuntu 23.04 and pipewire:

  $ pipewire --version
  pipewire
  Compiled with libpipewire 0.3.65
  Linked with libpipewire 0.3.65

  I can work around this problem by one of two ways:
  1. After restart, my headphone jack works as expected.
  2. Restarting pipewire, then sleeping/waking my computer again. I've been 
running the following (not sure if I need both):
  ```
  systemctl --user restart pipewire
  systemctl --user restart pipewire-pulse.service
  ```

  Please let me know of any other information I should provide, and/or where I 
should actually post this bug.
  --- 
  ProblemType: Bug
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 23.04
  InstallationDate: Installed on 2021-12-18 (500 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 048d:c100 Integrated Technology Express, Inc. ITE 
Device(8910)
   Bus 001 Device 002: ID 5986:2113 Acer, Inc SunplusIT Integrated Camera
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson 
Peak (JfP)
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81T2
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   LANG=en_CA.UTF-8
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic 
root=UUID=623299a9-c6f0-4bad-91c7-51d940e93e0c ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-20-generic N/A
   linux-backports-modules-6.2.0-20-generic  N/A
   linux-firmware20230323.gitbcdcfbcf-0ubuntu1
  Tags:  lunar
  Uname: Linux 6.2.0-20-generic x86_64
  UpgradeStatus: Upgraded to lunar on 2023-04-26 (6 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 01/20/2022
  dmi.bios.release: 1.44
  dmi.bios.vendor: LENOVO
  dmi.bios.version: BHCN44WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion Y545 PG0
  dmi.ec.firmware.release: 1.44
  dmi.modalias: 
dmi:bvnLENOVO:bvrBHCN44WW:bd01/20/2022:br1.44:efr1.44:svnLENOVO:pn81T2:pvrLegionY545PG0:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegionY545PG0:skuLENOVO_MT_81T2_BU_idea_FM_LegionY545PG0:
  dmi.product.family: Legion Y545 PG0
  dmi.product.name: 81T2
  dmi.product.sku: LENOVO_MT_81T2_BU_idea_FM_Legion Y545 PG0
  dmi.product.version: Legion Y545 PG0
  dmi.sys.vendor: LENOVO

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

2023-05-02 Thread Marlen T. B.
** Attachment added: "Lsusb-v.txt"
   
https://bugs.launchpad.net/bugs/2018122/+attachment/5670443/+files/Lsusb-v.txt

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

Title:
  My Headphone is Jack Not Being Detected After Waking From Sleep on
  Ubuntu 23.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  If I sleep/wake my computer, the 3.5 mm headphone jack no-longer
  detects when its gets plugged in.

  Using Ubuntu 23.04 and pipewire:

  $ pipewire --version
  pipewire
  Compiled with libpipewire 0.3.65
  Linked with libpipewire 0.3.65

  I can work around this problem by one of two ways:
  1. After restart, my headphone jack works as expected.
  2. Restarting pipewire, then sleeping/waking my computer again. I've been 
running the following (not sure if I need both):
  ```
  systemctl --user restart pipewire
  systemctl --user restart pipewire-pulse.service
  ```

  Please let me know of any other information I should provide, and/or where I 
should actually post this bug.
  --- 
  ProblemType: Bug
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 23.04
  InstallationDate: Installed on 2021-12-18 (500 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 048d:c100 Integrated Technology Express, Inc. ITE 
Device(8910)
   Bus 001 Device 002: ID 5986:2113 Acer, Inc SunplusIT Integrated Camera
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson 
Peak (JfP)
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81T2
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   LANG=en_CA.UTF-8
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic 
root=UUID=623299a9-c6f0-4bad-91c7-51d940e93e0c ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-20-generic N/A
   linux-backports-modules-6.2.0-20-generic  N/A
   linux-firmware20230323.gitbcdcfbcf-0ubuntu1
  Tags:  lunar
  Uname: Linux 6.2.0-20-generic x86_64
  UpgradeStatus: Upgraded to lunar on 2023-04-26 (6 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 01/20/2022
  dmi.bios.release: 1.44
  dmi.bios.vendor: LENOVO
  dmi.bios.version: BHCN44WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion Y545 PG0
  dmi.ec.firmware.release: 1.44
  dmi.modalias: 
dmi:bvnLENOVO:bvrBHCN44WW:bd01/20/2022:br1.44:efr1.44:svnLENOVO:pn81T2:pvrLegionY545PG0:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegionY545PG0:skuLENOVO_MT_81T2_BU_idea_FM_LegionY545PG0:
  dmi.product.family: Legion Y545 PG0
  dmi.product.name: 81T2
  dmi.product.sku: LENOVO_MT_81T2_BU_idea_FM_Legion Y545 PG0
  dmi.product.version: Legion Y545 PG0
  dmi.sys.vendor: LENOVO

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

2023-05-02 Thread Marlen T. B.
** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/2018122/+attachment/5670439/+files/IwConfig.txt

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

Title:
  My Headphone is Jack Not Being Detected After Waking From Sleep on
  Ubuntu 23.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  If I sleep/wake my computer, the 3.5 mm headphone jack no-longer
  detects when its gets plugged in.

  Using Ubuntu 23.04 and pipewire:

  $ pipewire --version
  pipewire
  Compiled with libpipewire 0.3.65
  Linked with libpipewire 0.3.65

  I can work around this problem by one of two ways:
  1. After restart, my headphone jack works as expected.
  2. Restarting pipewire, then sleeping/waking my computer again. I've been 
running the following (not sure if I need both):
  ```
  systemctl --user restart pipewire
  systemctl --user restart pipewire-pulse.service
  ```

  Please let me know of any other information I should provide, and/or where I 
should actually post this bug.
  --- 
  ProblemType: Bug
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 23.04
  InstallationDate: Installed on 2021-12-18 (500 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 048d:c100 Integrated Technology Express, Inc. ITE 
Device(8910)
   Bus 001 Device 002: ID 5986:2113 Acer, Inc SunplusIT Integrated Camera
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson 
Peak (JfP)
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81T2
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   LANG=en_CA.UTF-8
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic 
root=UUID=623299a9-c6f0-4bad-91c7-51d940e93e0c ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-20-generic N/A
   linux-backports-modules-6.2.0-20-generic  N/A
   linux-firmware20230323.gitbcdcfbcf-0ubuntu1
  Tags:  lunar
  Uname: Linux 6.2.0-20-generic x86_64
  UpgradeStatus: Upgraded to lunar on 2023-04-26 (6 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 01/20/2022
  dmi.bios.release: 1.44
  dmi.bios.vendor: LENOVO
  dmi.bios.version: BHCN44WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion Y545 PG0
  dmi.ec.firmware.release: 1.44
  dmi.modalias: 
dmi:bvnLENOVO:bvrBHCN44WW:bd01/20/2022:br1.44:efr1.44:svnLENOVO:pn81T2:pvrLegionY545PG0:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegionY545PG0:skuLENOVO_MT_81T2_BU_idea_FM_LegionY545PG0:
  dmi.product.family: Legion Y545 PG0
  dmi.product.name: 81T2
  dmi.product.sku: LENOVO_MT_81T2_BU_idea_FM_Legion Y545 PG0
  dmi.product.version: Legion Y545 PG0
  dmi.sys.vendor: LENOVO

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

2023-05-02 Thread Marlen T. B.
** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/2018122/+attachment/5670438/+files/CurrentDmesg.txt

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

Title:
  My Headphone is Jack Not Being Detected After Waking From Sleep on
  Ubuntu 23.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  If I sleep/wake my computer, the 3.5 mm headphone jack no-longer
  detects when its gets plugged in.

  Using Ubuntu 23.04 and pipewire:

  $ pipewire --version
  pipewire
  Compiled with libpipewire 0.3.65
  Linked with libpipewire 0.3.65

  I can work around this problem by one of two ways:
  1. After restart, my headphone jack works as expected.
  2. Restarting pipewire, then sleeping/waking my computer again. I've been 
running the following (not sure if I need both):
  ```
  systemctl --user restart pipewire
  systemctl --user restart pipewire-pulse.service
  ```

  Please let me know of any other information I should provide, and/or where I 
should actually post this bug.
  --- 
  ProblemType: Bug
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 23.04
  InstallationDate: Installed on 2021-12-18 (500 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 048d:c100 Integrated Technology Express, Inc. ITE 
Device(8910)
   Bus 001 Device 002: ID 5986:2113 Acer, Inc SunplusIT Integrated Camera
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson 
Peak (JfP)
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81T2
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   LANG=en_CA.UTF-8
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic 
root=UUID=623299a9-c6f0-4bad-91c7-51d940e93e0c ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-20-generic N/A
   linux-backports-modules-6.2.0-20-generic  N/A
   linux-firmware20230323.gitbcdcfbcf-0ubuntu1
  Tags:  lunar
  Uname: Linux 6.2.0-20-generic x86_64
  UpgradeStatus: Upgraded to lunar on 2023-04-26 (6 days ago)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 01/20/2022
  dmi.bios.release: 1.44
  dmi.bios.vendor: LENOVO
  dmi.bios.version: BHCN44WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion Y545 PG0
  dmi.ec.firmware.release: 1.44
  dmi.modalias: 
dmi:bvnLENOVO:bvrBHCN44WW:bd01/20/2022:br1.44:efr1.44:svnLENOVO:pn81T2:pvrLegionY545PG0:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegionY545PG0:skuLENOVO_MT_81T2_BU_idea_FM_LegionY545PG0:
  dmi.product.family: Legion Y545 PG0
  dmi.product.name: 81T2
  dmi.product.sku: LENOVO_MT_81T2_BU_idea_FM_Legion Y545 PG0
  dmi.product.version: Legion Y545 PG0
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2018122/+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 2018122] Re: My Headphone is Jack Not Being Detected After Waking From Sleep on Ubuntu 23.04

2023-05-02 Thread Marlen T. B.
** Tags added: apport-collected

** Description changed:

  If I sleep/wake my computer, the 3.5 mm headphone jack no-longer detects
  when its gets plugged in.
  
  Using Ubuntu 23.04 and pipewire:
  
  $ pipewire --version
  pipewire
  Compiled with libpipewire 0.3.65
  Linked with libpipewire 0.3.65
  
  I can work around this problem by one of two ways:
  1. After restart, my headphone jack works as expected.
  2. Restarting pipewire, then sleeping/waking my computer again. I've been 
running the following (not sure if I need both):
  ```
  systemctl --user restart pipewire
  systemctl --user restart pipewire-pulse.service
  ```
  
- Please let me know of any other information I should provide, and/or
- where I should actually post this bug.
+ Please let me know of any other information I should provide, and/or where I 
should actually post this bug.
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.26.1-0ubuntu2
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  marlen72779 F wireplumber
+  /dev/snd/controlC1:  marlen72779 F wireplumber
+  /dev/snd/seq:marlen72768 F pipewire
+ CRDA: N/A
+ CasperMD5CheckResult: pass
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 23.04
+ InstallationDate: Installed on 2021-12-18 (500 days ago)
+ InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
+ Lsusb:
+  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+  Bus 001 Device 003: ID 048d:c100 Integrated Technology Express, Inc. ITE 
Device(8910)
+  Bus 001 Device 002: ID 5986:2113 Acer, Inc SunplusIT Integrated Camera
+  Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson 
Peak (JfP)
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+ MachineType: LENOVO 81T2
+ NonfreeKernelModules: nvidia_modeset nvidia
+ Package: linux (not installed)
+ ProcEnviron:
+  LANG=en_CA.UTF-8
+  LANGUAGE=en_CA:en
+  PATH=(custom, no user)
+  SHELL=/bin/bash
+  TERM=xterm-256color
+ ProcFB: 0 i915drmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-20-generic 
root=UUID=623299a9-c6f0-4bad-91c7-51d940e93e0c ro quiet splash vt.handoff=7
+ ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
+ PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
+ RelatedPackageVersions:
+  linux-restricted-modules-6.2.0-20-generic N/A
+  linux-backports-modules-6.2.0-20-generic  N/A
+  linux-firmware20230323.gitbcdcfbcf-0ubuntu1
+ Tags:  lunar
+ Uname: Linux 6.2.0-20-generic x86_64
+ UpgradeStatus: Upgraded to lunar on 2023-04-26 (6 days ago)
+ UserGroups: N/A
+ _MarkForUpload: True
+ dmi.bios.date: 01/20/2022
+ dmi.bios.release: 1.44
+ dmi.bios.vendor: LENOVO
+ dmi.bios.version: BHCN44WW
+ dmi.board.asset.tag: NO Asset Tag
+ dmi.board.name: LNVNB161216
+ dmi.board.vendor: LENOVO
+ dmi.board.version: SDK0R32862 WIN
+ dmi.chassis.asset.tag: NO Asset Tag
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: LENOVO
+ dmi.chassis.version: Legion Y545 PG0
+ dmi.ec.firmware.release: 1.44
+ dmi.modalias: 
dmi:bvnLENOVO:bvrBHCN44WW:bd01/20/2022:br1.44:efr1.44:svnLENOVO:pn81T2:pvrLegionY545PG0:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegionY545PG0:skuLENOVO_MT_81T2_BU_idea_FM_LegionY545PG0:
+ dmi.product.family: Legion Y545 PG0
+ dmi.product.name: 81T2
+ dmi.product.sku: LENOVO_MT_81T2_BU_idea_FM_Legion Y545 PG0
+ dmi.product.version: Legion Y545 PG0
+ dmi.sys.vendor: LENOVO

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/2018122/+attachment/5670437/+files/AlsaInfo.txt

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

Title:
  My Headphone is Jack Not Being Detected After Waking From Sleep on
  Ubuntu 23.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  If I sleep/wake my computer, the 3.5 mm headphone jack no-longer
  detects when its gets plugged in.

  Using Ubuntu 23.04 and pipewire:

  $ pipewire --version
  pipewire
  Compiled with libpipewire 0.3.65
  Linked with libpipewire 0.3.65

  I can work around this problem by one of two ways:
  1. After restart, my headphone jack works as expected.
  2. Restarting pipewire, then sleeping/waking my computer again. I've been 
running the following (not sure if I need both):
  ```
  systemctl --user restart pipewire
  systemctl --user restart pipewire-pulse.service
  ```

  Please let me know of any other information I should provide, and/or where I 
should actually post this bug.
  --- 
  ProblemType: Bug
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 23.04
  InstallationDate: Installed on 2021-12-18 (500 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 

[Kernel-packages] [Bug 2016388] Re: Kernel Panic on shutdown / reboot on NUC8I3BEH

2023-04-23 Thread b
I was advised to use a different method of flashing the bios ("BIOS
recovery" by holding down the power on button with USB including BIOS
inserted) on the Intel forum (https://community.intel.com/t5/Intel-
NUCs/Linux-kernel-panics-on-reboot-and-shutdown-on-NUC8I3BEH-
using/m-p/1477101/emcs_t/S2h8ZW1haWx8dG9waWNfc3Vic2NyaXB0aW9ufExHSTlaMk5RS0FYSlZRfDE0NzcxMDF8U1VCU0NSSVBUSU9OU3xoSw#M99529)

The issue persists with BIOS 0092 and 5.4.0-147.

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

Title:
  Kernel Panic on shutdown / reboot on NUC8I3BEH

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Kernel 5.4.0-146 panics on power-down (e.g. shutdown -P now)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-146-generic 5.4.0-146.163
  ProcVersionSignature: Ubuntu 5.4.0-144.161-generic 5.4.229
  Uname: Linux 5.4.0-144-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.26
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bbogart1051 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Sat Apr 15 09:07:33 2023
  InstallationDate: Installed on 2019-02-09 (1526 days ago)
  InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Intel(R) Client Systems NUC8i3BEH
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-144-generic 
root=UUID=9c982b36-8142-4719-810a-e06f81cab223 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-144-generic N/A
   linux-backports-modules-5.4.0-144-generic  N/A
   linux-firmware 1.187.38
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2022-06-30 (289 days ago)
  dmi.bios.date: 02/14/2023
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BECFL357.86A.0092.2023.0214.1114
  dmi.board.name: NUC8BEB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: J72693-304
  dmi.chassis.type: 3
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBECFL357.86A.0092.2023.0214.1114:bd02/14/2023:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-303:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-304:cvnIntelCorporation:ct3:cvr2.0:
  dmi.product.family: Intel NUC
  dmi.product.name: NUC8i3BEH
  dmi.product.sku: BOXNUC8i3BEH
  dmi.product.version: J72753-303
  dmi.sys.vendor: Intel(R) Client Systems

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016388/+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 2016388] Re: Kernel Panic on shutdown / reboot on NUC8I3BEH

2023-04-20 Thread b
Issue persists using BIOS 0088 and 0089.

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

Title:
  Kernel Panic on shutdown / reboot on NUC8I3BEH

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Kernel 5.4.0-146 panics on power-down (e.g. shutdown -P now)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-146-generic 5.4.0-146.163
  ProcVersionSignature: Ubuntu 5.4.0-144.161-generic 5.4.229
  Uname: Linux 5.4.0-144-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.26
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bbogart1051 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Sat Apr 15 09:07:33 2023
  InstallationDate: Installed on 2019-02-09 (1526 days ago)
  InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Intel(R) Client Systems NUC8i3BEH
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-144-generic 
root=UUID=9c982b36-8142-4719-810a-e06f81cab223 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-144-generic N/A
   linux-backports-modules-5.4.0-144-generic  N/A
   linux-firmware 1.187.38
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2022-06-30 (289 days ago)
  dmi.bios.date: 02/14/2023
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BECFL357.86A.0092.2023.0214.1114
  dmi.board.name: NUC8BEB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: J72693-304
  dmi.chassis.type: 3
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBECFL357.86A.0092.2023.0214.1114:bd02/14/2023:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-303:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-304:cvnIntelCorporation:ct3:cvr2.0:
  dmi.product.family: Intel NUC
  dmi.product.name: NUC8i3BEH
  dmi.product.sku: BOXNUC8i3BEH
  dmi.product.version: J72753-303
  dmi.sys.vendor: Intel(R) Client Systems

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016388/+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 2016388] Re: Kernel Panic on shutdown / reboot on NUC8I3BEH

2023-04-20 Thread b
Problem persists using BIOS 0089, trying 0088 next...

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

Title:
  Kernel Panic on shutdown / reboot on NUC8I3BEH

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Kernel 5.4.0-146 panics on power-down (e.g. shutdown -P now)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-146-generic 5.4.0-146.163
  ProcVersionSignature: Ubuntu 5.4.0-144.161-generic 5.4.229
  Uname: Linux 5.4.0-144-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.26
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bbogart1051 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Sat Apr 15 09:07:33 2023
  InstallationDate: Installed on 2019-02-09 (1526 days ago)
  InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Intel(R) Client Systems NUC8i3BEH
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-144-generic 
root=UUID=9c982b36-8142-4719-810a-e06f81cab223 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-144-generic N/A
   linux-backports-modules-5.4.0-144-generic  N/A
   linux-firmware 1.187.38
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2022-06-30 (289 days ago)
  dmi.bios.date: 02/14/2023
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BECFL357.86A.0092.2023.0214.1114
  dmi.board.name: NUC8BEB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: J72693-304
  dmi.chassis.type: 3
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBECFL357.86A.0092.2023.0214.1114:bd02/14/2023:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-303:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-304:cvnIntelCorporation:ct3:cvr2.0:
  dmi.product.family: Intel NUC
  dmi.product.name: NUC8i3BEH
  dmi.product.sku: BOXNUC8i3BEH
  dmi.product.version: J72753-303
  dmi.sys.vendor: Intel(R) Client Systems

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016388/+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 2016388] Re: Kernel Panic on shutdown / reboot on NUC8I3BEH

2023-04-20 Thread b
Confirmed on 5.4.0-147

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

Title:
  Kernel Panic on shutdown / reboot on NUC8I3BEH

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Kernel 5.4.0-146 panics on power-down (e.g. shutdown -P now)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-146-generic 5.4.0-146.163
  ProcVersionSignature: Ubuntu 5.4.0-144.161-generic 5.4.229
  Uname: Linux 5.4.0-144-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.26
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bbogart1051 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Sat Apr 15 09:07:33 2023
  InstallationDate: Installed on 2019-02-09 (1526 days ago)
  InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Intel(R) Client Systems NUC8i3BEH
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-144-generic 
root=UUID=9c982b36-8142-4719-810a-e06f81cab223 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-144-generic N/A
   linux-backports-modules-5.4.0-144-generic  N/A
   linux-firmware 1.187.38
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2022-06-30 (289 days ago)
  dmi.bios.date: 02/14/2023
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BECFL357.86A.0092.2023.0214.1114
  dmi.board.name: NUC8BEB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: J72693-304
  dmi.chassis.type: 3
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBECFL357.86A.0092.2023.0214.1114:bd02/14/2023:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-303:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-304:cvnIntelCorporation:ct3:cvr2.0:
  dmi.product.family: Intel NUC
  dmi.product.name: NUC8i3BEH
  dmi.product.sku: BOXNUC8i3BEH
  dmi.product.version: J72753-303
  dmi.sys.vendor: Intel(R) Client Systems

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016388/+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 2016388] Re: Kernel Panic on shutdown / reboot on NUC8I3BEH

2023-04-20 Thread b
** Summary changed:

- Kernel Panic on powerdown on NUC8I3BEH1
+ Kernel Panic on shutdown / reboot on NUC8I3BEH

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

Title:
  Kernel Panic on shutdown / reboot on NUC8I3BEH

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Kernel 5.4.0-146 panics on power-down (e.g. shutdown -P now)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-146-generic 5.4.0-146.163
  ProcVersionSignature: Ubuntu 5.4.0-144.161-generic 5.4.229
  Uname: Linux 5.4.0-144-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.26
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bbogart1051 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Sat Apr 15 09:07:33 2023
  InstallationDate: Installed on 2019-02-09 (1526 days ago)
  InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Intel(R) Client Systems NUC8i3BEH
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-144-generic 
root=UUID=9c982b36-8142-4719-810a-e06f81cab223 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-144-generic N/A
   linux-backports-modules-5.4.0-144-generic  N/A
   linux-firmware 1.187.38
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2022-06-30 (289 days ago)
  dmi.bios.date: 02/14/2023
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BECFL357.86A.0092.2023.0214.1114
  dmi.board.name: NUC8BEB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: J72693-304
  dmi.chassis.type: 3
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBECFL357.86A.0092.2023.0214.1114:bd02/14/2023:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-303:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-304:cvnIntelCorporation:ct3:cvr2.0:
  dmi.product.family: Intel NUC
  dmi.product.name: NUC8i3BEH
  dmi.product.sku: BOXNUC8i3BEH
  dmi.product.version: J72753-303
  dmi.sys.vendor: Intel(R) Client Systems

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016388/+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 2016388] Re: Kernel Panic on powerdown on NUC8I3BEH1

2023-04-17 Thread b
I was unable to go back to an older version of the BIOS; both BE0088 and
BE0089 resulted in the following error:

"Incompatible BIOS version, Update Aborted!"

This happened both using the built in UEFI BIOS update option and
running IFLASH2 in FreeDOS booting in legacy mode.

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

Title:
  Kernel Panic on powerdown on NUC8I3BEH1

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Kernel 5.4.0-146 panics on power-down (e.g. shutdown -P now)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-146-generic 5.4.0-146.163
  ProcVersionSignature: Ubuntu 5.4.0-144.161-generic 5.4.229
  Uname: Linux 5.4.0-144-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.26
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bbogart1051 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Sat Apr 15 09:07:33 2023
  InstallationDate: Installed on 2019-02-09 (1526 days ago)
  InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Intel(R) Client Systems NUC8i3BEH
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-144-generic 
root=UUID=9c982b36-8142-4719-810a-e06f81cab223 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-144-generic N/A
   linux-backports-modules-5.4.0-144-generic  N/A
   linux-firmware 1.187.38
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2022-06-30 (289 days ago)
  dmi.bios.date: 02/14/2023
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BECFL357.86A.0092.2023.0214.1114
  dmi.board.name: NUC8BEB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: J72693-304
  dmi.chassis.type: 3
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBECFL357.86A.0092.2023.0214.1114:bd02/14/2023:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-303:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-304:cvnIntelCorporation:ct3:cvr2.0:
  dmi.product.family: Intel NUC
  dmi.product.name: NUC8i3BEH
  dmi.product.sku: BOXNUC8i3BEH
  dmi.product.version: J72753-303
  dmi.sys.vendor: Intel(R) Client Systems

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016388/+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 2016388] Re: Kernel Panic on powerdown on NUC8I3BEH1

2023-04-15 Thread b
Same thing with BIOS 0090 and kernel 5.4.0-135

** Attachment added: "Photo of panic trace"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016388/+attachment/5664317/+files/BIOS0090_5.4.0-135_20230415_103355.jpg

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

Title:
  Kernel Panic on powerdown on NUC8I3BEH1

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Kernel 5.4.0-146 panics on power-down (e.g. shutdown -P now)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-146-generic 5.4.0-146.163
  ProcVersionSignature: Ubuntu 5.4.0-144.161-generic 5.4.229
  Uname: Linux 5.4.0-144-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.26
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bbogart1051 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Sat Apr 15 09:07:33 2023
  InstallationDate: Installed on 2019-02-09 (1526 days ago)
  InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Intel(R) Client Systems NUC8i3BEH
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-144-generic 
root=UUID=9c982b36-8142-4719-810a-e06f81cab223 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-144-generic N/A
   linux-backports-modules-5.4.0-144-generic  N/A
   linux-firmware 1.187.38
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2022-06-30 (289 days ago)
  dmi.bios.date: 02/14/2023
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BECFL357.86A.0092.2023.0214.1114
  dmi.board.name: NUC8BEB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: J72693-304
  dmi.chassis.type: 3
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBECFL357.86A.0092.2023.0214.1114:bd02/14/2023:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-303:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-304:cvnIntelCorporation:ct3:cvr2.0:
  dmi.product.family: Intel NUC
  dmi.product.name: NUC8i3BEH
  dmi.product.sku: BOXNUC8i3BEH
  dmi.product.version: J72753-303
  dmi.sys.vendor: Intel(R) Client Systems

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016388/+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 2016388] Re: Kernel Panic on powerdown on NUC8I3BEH1

2023-04-15 Thread b
Confirmed on 121.

Another thing I realized is that I also updated the BIOS when I upgraded
the RAM. Updated to BE0092. I have no idea what the previous BIOS
version I was using (whatever shipped with the machine initially), but
this one sill seems the most up to date version.

I'll try downgrading BIOS to BE0090.



** Attachment added: "5.4.0-121_20230415_100513.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016388/+attachment/5664316/+files/5.4.0-121_20230415_100513.jpg

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

Title:
  Kernel Panic on powerdown on NUC8I3BEH1

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Kernel 5.4.0-146 panics on power-down (e.g. shutdown -P now)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-146-generic 5.4.0-146.163
  ProcVersionSignature: Ubuntu 5.4.0-144.161-generic 5.4.229
  Uname: Linux 5.4.0-144-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.26
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bbogart1051 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Sat Apr 15 09:07:33 2023
  InstallationDate: Installed on 2019-02-09 (1526 days ago)
  InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Intel(R) Client Systems NUC8i3BEH
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-144-generic 
root=UUID=9c982b36-8142-4719-810a-e06f81cab223 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-144-generic N/A
   linux-backports-modules-5.4.0-144-generic  N/A
   linux-firmware 1.187.38
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2022-06-30 (289 days ago)
  dmi.bios.date: 02/14/2023
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BECFL357.86A.0092.2023.0214.1114
  dmi.board.name: NUC8BEB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: J72693-304
  dmi.chassis.type: 3
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBECFL357.86A.0092.2023.0214.1114:bd02/14/2023:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-303:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-304:cvnIntelCorporation:ct3:cvr2.0:
  dmi.product.family: Intel NUC
  dmi.product.name: NUC8i3BEH
  dmi.product.sku: BOXNUC8i3BEH
  dmi.product.version: J72753-303
  dmi.sys.vendor: Intel(R) Client Systems

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016388/+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 2016388] Re: Kernel Panic on powerdown on NUC8I3BEH1

2023-04-15 Thread b
Same thing with 131. So I have no idea what's going on. I upgraded the
RAM in this machine around March 14th, which is why I know that was the
last time I rebooted and I believe I would have noticed a panic.

I also confirm it seems all reboots result in the same panic (e.g. "sudo
reboot" and also using the XFCE gui to shutdown or reboot).

Looking at my dpkg output, it looks like I've installed a lot of kernels
and presumably they all would have required a reboot, I only noticed
this kernel panic on shutdown yesterday.

rc  linux-image-5.4.0-121-generic  5.4.0-121.137 amd64Signed ke>
rc  linux-image-5.4.0-122-generic  5.4.0-122.138 amd64Signed ke>
rc  linux-image-5.4.0-124-generic  5.4.0-124.140 amd64Signed ke>
rc  linux-image-5.4.0-126-generic  5.4.0-126.142 amd64Signed ke>
ii  linux-image-5.4.0-131-generic  5.4.0-131.147 amd64Signed ke>
rc  linux-image-5.4.0-135-generic  5.4.0-135.152 amd64Signed ke>
ii  linux-image-5.4.0-144-generic  5.4.0-144.161 amd64Signed ke>
ii  linux-image-5.4.0-146-generic  5.4.0-146.163 amd64Signed ke>

I'll try 121 as a final attempt.

** Attachment added: "Photo of panic trace"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016388/+attachment/5664278/+files/5.4.0-131_20230415_094504.jpg

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

Title:
  Kernel Panic on powerdown on NUC8I3BEH1

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Kernel 5.4.0-146 panics on power-down (e.g. shutdown -P now)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-146-generic 5.4.0-146.163
  ProcVersionSignature: Ubuntu 5.4.0-144.161-generic 5.4.229
  Uname: Linux 5.4.0-144-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.26
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bbogart1051 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Sat Apr 15 09:07:33 2023
  InstallationDate: Installed on 2019-02-09 (1526 days ago)
  InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Intel(R) Client Systems NUC8i3BEH
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-144-generic 
root=UUID=9c982b36-8142-4719-810a-e06f81cab223 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-144-generic N/A
   linux-backports-modules-5.4.0-144-generic  N/A
   linux-firmware 1.187.38
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2022-06-30 (289 days ago)
  dmi.bios.date: 02/14/2023
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BECFL357.86A.0092.2023.0214.1114
  dmi.board.name: NUC8BEB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: J72693-304
  dmi.chassis.type: 3
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBECFL357.86A.0092.2023.0214.1114:bd02/14/2023:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-303:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-304:cvnIntelCorporation:ct3:cvr2.0:
  dmi.product.family: Intel NUC
  dmi.product.name: NUC8i3BEH
  dmi.product.sku: BOXNUC8i3BEH
  dmi.product.version: J72753-303
  dmi.sys.vendor: Intel(R) Client Systems

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016388/+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 2016388] Re: Kernel Panic on powerdown on NUC8I3BEH1

2023-04-15 Thread b
hmm. The issue persists going back to 5.4.0-135 also...

Trying 5.4.0-131 next, but if that it's still happening the issue may be
else ware?

I don't reboot or shutdown this machine very often, the last time I can
confirm I shut down without a panic was around March 14th.

** Attachment added: "5.4.0-135_20230415_093229.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016388/+attachment/5664276/+files/5.4.0-135_20230415_093229.jpg

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

Title:
  Kernel Panic on powerdown on NUC8I3BEH1

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Kernel 5.4.0-146 panics on power-down (e.g. shutdown -P now)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-146-generic 5.4.0-146.163
  ProcVersionSignature: Ubuntu 5.4.0-144.161-generic 5.4.229
  Uname: Linux 5.4.0-144-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.26
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bbogart1051 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Sat Apr 15 09:07:33 2023
  InstallationDate: Installed on 2019-02-09 (1526 days ago)
  InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Intel(R) Client Systems NUC8i3BEH
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-144-generic 
root=UUID=9c982b36-8142-4719-810a-e06f81cab223 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-144-generic N/A
   linux-backports-modules-5.4.0-144-generic  N/A
   linux-firmware 1.187.38
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2022-06-30 (289 days ago)
  dmi.bios.date: 02/14/2023
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BECFL357.86A.0092.2023.0214.1114
  dmi.board.name: NUC8BEB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: J72693-304
  dmi.chassis.type: 3
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBECFL357.86A.0092.2023.0214.1114:bd02/14/2023:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-303:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-304:cvnIntelCorporation:ct3:cvr2.0:
  dmi.product.family: Intel NUC
  dmi.product.name: NUC8i3BEH
  dmi.product.sku: BOXNUC8i3BEH
  dmi.product.version: J72753-303
  dmi.sys.vendor: Intel(R) Client Systems

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016388/+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 2016388] Re: Kernel Panic on powerdown on NUC8I3BEH1

2023-04-15 Thread b
Photo of console showing panic trace using 5.4.0-144

** Attachment added: "Photo of panic trace"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016388/+attachment/5664275/+files/5.4.0-144_20230415_091831.jpg

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

Title:
  Kernel Panic on powerdown on NUC8I3BEH1

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Kernel 5.4.0-146 panics on power-down (e.g. shutdown -P now)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-146-generic 5.4.0-146.163
  ProcVersionSignature: Ubuntu 5.4.0-144.161-generic 5.4.229
  Uname: Linux 5.4.0-144-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.26
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bbogart1051 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Sat Apr 15 09:07:33 2023
  InstallationDate: Installed on 2019-02-09 (1526 days ago)
  InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Intel(R) Client Systems NUC8i3BEH
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-144-generic 
root=UUID=9c982b36-8142-4719-810a-e06f81cab223 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-144-generic N/A
   linux-backports-modules-5.4.0-144-generic  N/A
   linux-firmware 1.187.38
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2022-06-30 (289 days ago)
  dmi.bios.date: 02/14/2023
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BECFL357.86A.0092.2023.0214.1114
  dmi.board.name: NUC8BEB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: J72693-304
  dmi.chassis.type: 3
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBECFL357.86A.0092.2023.0214.1114:bd02/14/2023:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-303:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-304:cvnIntelCorporation:ct3:cvr2.0:
  dmi.product.family: Intel NUC
  dmi.product.name: NUC8i3BEH
  dmi.product.sku: BOXNUC8i3BEH
  dmi.product.version: J72753-303
  dmi.sys.vendor: Intel(R) Client Systems

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016388/+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 2016388] Re: Kernel Panic on powerdown on NUC8I3BEH1

2023-04-15 Thread b
This issue seems to persist falling back to kernel 5.4.0-144

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

Title:
  Kernel Panic on powerdown on NUC8I3BEH1

Status in linux package in Ubuntu:
  New

Bug description:
  Kernel 5.4.0-146 panics on power-down (e.g. shutdown -P now)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-146-generic 5.4.0-146.163
  ProcVersionSignature: Ubuntu 5.4.0-144.161-generic 5.4.229
  Uname: Linux 5.4.0-144-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.26
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bbogart1051 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Sat Apr 15 09:07:33 2023
  InstallationDate: Installed on 2019-02-09 (1526 days ago)
  InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Intel(R) Client Systems NUC8i3BEH
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-144-generic 
root=UUID=9c982b36-8142-4719-810a-e06f81cab223 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-144-generic N/A
   linux-backports-modules-5.4.0-144-generic  N/A
   linux-firmware 1.187.38
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2022-06-30 (289 days ago)
  dmi.bios.date: 02/14/2023
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BECFL357.86A.0092.2023.0214.1114
  dmi.board.name: NUC8BEB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: J72693-304
  dmi.chassis.type: 3
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBECFL357.86A.0092.2023.0214.1114:bd02/14/2023:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-303:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-304:cvnIntelCorporation:ct3:cvr2.0:
  dmi.product.family: Intel NUC
  dmi.product.name: NUC8i3BEH
  dmi.product.sku: BOXNUC8i3BEH
  dmi.product.version: J72753-303
  dmi.sys.vendor: Intel(R) Client Systems

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016388/+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 2016388] [NEW] Kernel Panic on powerdown on NUC8I3BEH1

2023-04-15 Thread b
Public bug reported:

Kernel 5.4.0-146 panics on power-down (e.g. shutdown -P now)

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-146-generic 5.4.0-146.163
ProcVersionSignature: Ubuntu 5.4.0-144.161-generic 5.4.229
Uname: Linux 5.4.0-144-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.26
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  bbogart1051 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: XFCE
Date: Sat Apr 15 09:07:33 2023
InstallationDate: Installed on 2019-02-09 (1526 days ago)
InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
MachineType: Intel(R) Client Systems NUC8i3BEH
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-144-generic 
root=UUID=9c982b36-8142-4719-810a-e06f81cab223 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.4.0-144-generic N/A
 linux-backports-modules-5.4.0-144-generic  N/A
 linux-firmware 1.187.38
SourcePackage: linux
UpgradeStatus: Upgraded to focal on 2022-06-30 (289 days ago)
dmi.bios.date: 02/14/2023
dmi.bios.vendor: Intel Corp.
dmi.bios.version: BECFL357.86A.0092.2023.0214.1114
dmi.board.name: NUC8BEB
dmi.board.vendor: Intel Corporation
dmi.board.version: J72693-304
dmi.chassis.type: 3
dmi.chassis.vendor: Intel Corporation
dmi.chassis.version: 2.0
dmi.modalias: 
dmi:bvnIntelCorp.:bvrBECFL357.86A.0092.2023.0214.1114:bd02/14/2023:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-303:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-304:cvnIntelCorporation:ct3:cvr2.0:
dmi.product.family: Intel NUC
dmi.product.name: NUC8i3BEH
dmi.product.sku: BOXNUC8i3BEH
dmi.product.version: J72753-303
dmi.sys.vendor: Intel(R) Client Systems

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


** Tags: amd64 apport-bug focal third-party-packages

** Attachment added: "Photo of panic trace"
   
https://bugs.launchpad.net/bugs/2016388/+attachment/5664254/+files/20230414_161829.jpg

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

Title:
  Kernel Panic on powerdown on NUC8I3BEH1

Status in linux package in Ubuntu:
  New

Bug description:
  Kernel 5.4.0-146 panics on power-down (e.g. shutdown -P now)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-146-generic 5.4.0-146.163
  ProcVersionSignature: Ubuntu 5.4.0-144.161-generic 5.4.229
  Uname: Linux 5.4.0-144-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.26
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bbogart1051 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Sat Apr 15 09:07:33 2023
  InstallationDate: Installed on 2019-02-09 (1526 days ago)
  InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Intel(R) Client Systems NUC8i3BEH
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-144-generic 
root=UUID=9c982b36-8142-4719-810a-e06f81cab223 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-144-generic N/A
   linux-backports-modules-5.4.0-144-generic  N/A
   linux-firmware 1.187.38
  SourcePackage: linux
  UpgradeStatus: Upgraded to focal on 2022-06-30 (289 days ago)
  dmi.bios.date: 02/14/2023
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BECFL357.86A.0092.2023.0214.1114
  dmi.board.name: NUC8BEB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: J72693-304
  dmi.chassis.type: 3
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBECFL357.86A.0092.2023.0214.1114:bd02/14/2023:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-303:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-304:cvnIntelCorporation:ct3:cvr2.0:
  dmi.product.family: Intel NUC
  dmi.product.name: NUC8i3BEH
  dmi.product.sku: BOXNUC8i3BEH
  dmi.product.version: J72753-303
  dmi.sys.vendor: Intel(R) Client Systems

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016388/+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 2012520] Re: USB3 to ethernet adapter stops working (ax88179)

2023-03-25 Thread B Tasker
I encountered the same issue with an Anker USB-C hub+ethernet using the
same chipset:

root@ratchett:~# ethtool -i enxa0cec86958e9
driver: ax88179_178a
version: 5.19.0-35-generic
firmware-version: 
expansion-rom-version: 
bus-info: 2-1.4:1.0
supports-statistics: no
supports-test: no
supports-eeprom-access: yes
supports-register-dump: no
supports-priv-flags: no

Hunting around led me to an upstream kernel bug report:
https://bugzilla.kernel.org/show_bug.cgi?id=212731

One of the comments in there notes that there's an out-of-band fix at
https://github.com/nothingstopsme/AX88179_178A_Linux_Driver

Using that does seem to have resolved the issue for me - I've chucked
some fairly heavy workloads across the network without issue, whereas
before starting a simple video call would kill the adapter.

Installation steps are:

git clone https://github.com/nothingstopsme/AX88179_178A_Linux_Driver.git
cd AX88179_178A_Linux_Driver/source
make
sudo make install
sudo reboot




** Bug watch added: Linux Kernel Bug Tracker #212731
   https://bugzilla.kernel.org/show_bug.cgi?id=212731

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

Title:
  USB3 to ethernet adapter stops working (ax88179)

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

Bug description:
  On a machine with the ax88179 USB3 ethernet adapter, the adapter works
  poorly.

  As long as there is a moderate usage of the ethernet connection
  everything seems to work fine.

  As soon as the usage pattern changes and a continuous throughput is
  required (typical case teleconferencing via teams, skype, etc) the
  adapter stops working and the following line gets repeated many many
  times in the system logs:

  ax88179_178a 4-1.4:2.0 eth1: Failed to write reg index 0x0001: -32

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.19.0-35-generic 5.19.0-35.36~22.04.1
  ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-35-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Wed Mar 22 15:35:38 2023
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2020-02-16 (1130 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: linux-signed-hwe-5.19
  UpgradeStatus: Upgraded to jammy on 2022-06-03 (292 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2012520/+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 1986623] Re: cryptsetup fails to decrypt root partion during boot

2023-02-18 Thread Patrick B
Searching the web I found and wonder if it is related:
https://unix.stackexchange.com/questions/708445/etc-crypttab-not-updating-in-initramfs

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

Title:
  cryptsetup fails to decrypt root partion during boot

Status in cryptsetup package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  During boot, cryptsetup fails to decrypt the root partition in a,
  seemingly, non-deterministic fashion. I know that the password is
  correct and that the keymap is not a fault either, because I have
  specifically chosen the very weak password "123456" for testing
  purposes. A hardware defect seems also rather unlikely as this
  behavior does not affect other Linux distributions or FreeBSD. Earlier
  Ubuntu versions do not seem to be affected either, as this bug appears
  to have been introduced during a kernel update in 20.04 and persists
  throughout 20.04-22.04. Unfortunately I cannot pinpoint the exact
  kernel update that introduced this bug. I have appended the output of
  cryptsetup when manually called from the initramfs shell. Here the
  second attempt succeeded in decrypting the root partition, however, it
  usually takes a lot more attempts to do so.

  As for some additional information, I can decrypt the same luks
  partition from a live USB without any problems whatsoever.

  echo 123456 | cryptsetup open --type luks --debug /dev/nvme0n1p3 
nvme0n1p3_crypt
  # cryptsetup 2.4.3 processing "cryptsetup open --type luks --debug 
/dev/nvme0n1p3 nvme0n1p3_crypt"
  # Running command open.
  # Locking memory.
  # Installing SIGINT/SIGTERM handler.
  # Unblocking interruption on signal.
  # Allocating context for crypt device /dev/nvme0n1p3.
  # Trying to open and read device /dev/nvme0n1p3 with direct-io.
  # Initialising device-mapper backend library.
  # Trying to load any crypt type from device /dev/nvme0n1p3.
  # Crypto backend (OpenSSL 3.0.2 15 Mar 2022 [default]) initialized in 
cryptsetup library version 2.4.3.
  # Detected kernel Linux 5.15.0-46-generic x86_64.
  # Loading LUKS2 header (repair disabled).
  # Acquiring read lock for device /dev/nvme0n1p3.
  # Opening lock resource file /run/cryptsetup/L_259:3
  # Verifying lock handle for /dev/nvme0n1p3.
  # Device /dev/nvme0n1p3 READ lock taken.
  # Trying to read primary LUKS2 header at offset 0x0.
  # Opening locked device /dev/nvme0n1p3
  # Verifying locked device handle (bdev)
  # LUKS2 header version 2 of size 16384 bytes, checksum sha256.
  # Checksum:99172356e66a2fec247b1e5c758af8bc1338a3fb8bd973aab5e1512a93b2dbdc 
(on-disk)
  # Checksum:99172356e66a2fec247b1e5c758af8bc1338a3fb8bd973aab5e1512a93b2dbdc 
(in-memory)
  # Trying to read secondary LUKS2 header at offset 0x4000.
  # Reusing open ro fd on device /dev/nvme0n1p3
  # LUKS2 header version 2 of size 16384 bytes, checksum sha256.
  # Checksum:655a50aef64b6fd4e10b8863df72d7fc62a7020f74684cb3419d4e22adb6fd9c 
(on-disk)
  # Checksum:655a50aef64b6fd4e10b8863df72d7fc62a7020f74684cb3419d4e22adb6fd9c 
(in-memory)
  # Device size 497776852992, offset 16777216.
  # Device /dev/nvme0n1p3 READ lock released.
  # PBKDF argon2id, time_ms 2000 (iterations 0), max_memory_kb 1048576, 
parallel_threads 4.
  # Activating volume nvme0n1p3_crypt using token (any type) -1.
  # dm version   [ opencount flush ]   [16384] (*1)
  # dm versions   [ opencount flush ]   [16384] (*1)
  # Detected dm-ioctl version 4.45.0.
  # Detected dm-crypt version 1.23.0.
  # Device-mapper backend running with UDEV support enabled.
  # dm status nvme0n1p3_crypt  [ opencount noflush ]   [16384] (*1)
  No usable token is available.
  # STDIN descriptor passphrase entry requested.
  # Activating volume nvme0n1p3_crypt [keyslot -1] using passphrase.
  # dm versions   [ opencount flush ]   [16384] (*1)
  # dm status nvme0n1p3_crypt  [ opencount noflush ]   [16384] (*1)
  # Keyslot 0 priority 1 != 2 (required), skipped.
  # Keyslot 1 priority 1 != 2 (required), skipped.
  # Trying to open LUKS2 keyslot 0.
  # Running keyslot key derivation.
  # Reading keyslot area [0x8000].
  # Acquiring read lock for device /dev/nvme0n1p3.
  # Opening lock resource file /run/cryptsetup/L_259:3
  # Verifying lock handle for /dev/nvme0n1p3.
  # Device /dev/nvme0n1p3 READ lock taken.
  # Reusing open ro fd on device /dev/nvme0n1p3
  # Device /dev/nvme0n1p3 READ lock released.
  # Verifying key from keyslot 0, digest 0.
  # Digest 0 (pbkdf2) verify failed with -1.
  # Trying to open LUKS2 keyslot 1.
  # Running keyslot key derivation.
  # Reading keyslot area [0x47000].
  # Acquiring read lock for device /dev/nvme0n1p3.
  # Opening lock resource file /run/cryptsetup/L_259:3
  # Verifying lock handle for /dev/nvme0n1p3.
  # Device /dev/nvme0n1p3 READ lock taken.
  # Reusing open ro fd on device /dev/nvme0n1p3
  # Device /dev/nvme0n1p3 READ lock released.
  # 

[Kernel-packages] [Bug 1986623] Re: cryptsetup fails to decrypt root partion during boot

2023-02-11 Thread Patrick B
The original poster uses an AMD system. My affected system also uses an
AMD (part of /proc/cpunifo attached). What are other affected systems
using?

** Attachment added: "part of cat /proc/cpunifo"
   
https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1986623/+attachment/5646314/+files/cpuinfo_snip.txt

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

Title:
  cryptsetup fails to decrypt root partion during boot

Status in cryptsetup package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  During boot, cryptsetup fails to decrypt the root partition in a,
  seemingly, non-deterministic fashion. I know that the password is
  correct and that the keymap is not a fault either, because I have
  specifically chosen the very weak password "123456" for testing
  purposes. A hardware defect seems also rather unlikely as this
  behavior does not affect other Linux distributions or FreeBSD. Earlier
  Ubuntu versions do not seem to be affected either, as this bug appears
  to have been introduced during a kernel update in 20.04 and persists
  throughout 20.04-22.04. Unfortunately I cannot pinpoint the exact
  kernel update that introduced this bug. I have appended the output of
  cryptsetup when manually called from the initramfs shell. Here the
  second attempt succeeded in decrypting the root partition, however, it
  usually takes a lot more attempts to do so.

  As for some additional information, I can decrypt the same luks
  partition from a live USB without any problems whatsoever.

  echo 123456 | cryptsetup open --type luks --debug /dev/nvme0n1p3 
nvme0n1p3_crypt
  # cryptsetup 2.4.3 processing "cryptsetup open --type luks --debug 
/dev/nvme0n1p3 nvme0n1p3_crypt"
  # Running command open.
  # Locking memory.
  # Installing SIGINT/SIGTERM handler.
  # Unblocking interruption on signal.
  # Allocating context for crypt device /dev/nvme0n1p3.
  # Trying to open and read device /dev/nvme0n1p3 with direct-io.
  # Initialising device-mapper backend library.
  # Trying to load any crypt type from device /dev/nvme0n1p3.
  # Crypto backend (OpenSSL 3.0.2 15 Mar 2022 [default]) initialized in 
cryptsetup library version 2.4.3.
  # Detected kernel Linux 5.15.0-46-generic x86_64.
  # Loading LUKS2 header (repair disabled).
  # Acquiring read lock for device /dev/nvme0n1p3.
  # Opening lock resource file /run/cryptsetup/L_259:3
  # Verifying lock handle for /dev/nvme0n1p3.
  # Device /dev/nvme0n1p3 READ lock taken.
  # Trying to read primary LUKS2 header at offset 0x0.
  # Opening locked device /dev/nvme0n1p3
  # Verifying locked device handle (bdev)
  # LUKS2 header version 2 of size 16384 bytes, checksum sha256.
  # Checksum:99172356e66a2fec247b1e5c758af8bc1338a3fb8bd973aab5e1512a93b2dbdc 
(on-disk)
  # Checksum:99172356e66a2fec247b1e5c758af8bc1338a3fb8bd973aab5e1512a93b2dbdc 
(in-memory)
  # Trying to read secondary LUKS2 header at offset 0x4000.
  # Reusing open ro fd on device /dev/nvme0n1p3
  # LUKS2 header version 2 of size 16384 bytes, checksum sha256.
  # Checksum:655a50aef64b6fd4e10b8863df72d7fc62a7020f74684cb3419d4e22adb6fd9c 
(on-disk)
  # Checksum:655a50aef64b6fd4e10b8863df72d7fc62a7020f74684cb3419d4e22adb6fd9c 
(in-memory)
  # Device size 497776852992, offset 16777216.
  # Device /dev/nvme0n1p3 READ lock released.
  # PBKDF argon2id, time_ms 2000 (iterations 0), max_memory_kb 1048576, 
parallel_threads 4.
  # Activating volume nvme0n1p3_crypt using token (any type) -1.
  # dm version   [ opencount flush ]   [16384] (*1)
  # dm versions   [ opencount flush ]   [16384] (*1)
  # Detected dm-ioctl version 4.45.0.
  # Detected dm-crypt version 1.23.0.
  # Device-mapper backend running with UDEV support enabled.
  # dm status nvme0n1p3_crypt  [ opencount noflush ]   [16384] (*1)
  No usable token is available.
  # STDIN descriptor passphrase entry requested.
  # Activating volume nvme0n1p3_crypt [keyslot -1] using passphrase.
  # dm versions   [ opencount flush ]   [16384] (*1)
  # dm status nvme0n1p3_crypt  [ opencount noflush ]   [16384] (*1)
  # Keyslot 0 priority 1 != 2 (required), skipped.
  # Keyslot 1 priority 1 != 2 (required), skipped.
  # Trying to open LUKS2 keyslot 0.
  # Running keyslot key derivation.
  # Reading keyslot area [0x8000].
  # Acquiring read lock for device /dev/nvme0n1p3.
  # Opening lock resource file /run/cryptsetup/L_259:3
  # Verifying lock handle for /dev/nvme0n1p3.
  # Device /dev/nvme0n1p3 READ lock taken.
  # Reusing open ro fd on device /dev/nvme0n1p3
  # Device /dev/nvme0n1p3 READ lock released.
  # Verifying key from keyslot 0, digest 0.
  # Digest 0 (pbkdf2) verify failed with -1.
  # Trying to open LUKS2 keyslot 1.
  # Running keyslot key derivation.
  # Reading keyslot area [0x47000].
  # Acquiring read lock for device /dev/nvme0n1p3.
  # Opening lock resource file /run/cryptsetup/L_259:3
  # Verifying lock 

[Kernel-packages] [Bug 1986623] Re: cryptsetup fails to decrypt root partion during boot

2023-02-10 Thread Patrick B
Having the same issue with an existing installation of kubuntu. When
installing a fresh kubuntu on the same hardware (only difference on a
brand new nvme drive) I have the issue after first boot even with that
fresh Kubuntu 22.04.1 LTS. See https://askubuntu.com/q/1454265/1671849

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

Title:
  cryptsetup fails to decrypt root partion during boot

Status in cryptsetup package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  During boot, cryptsetup fails to decrypt the root partition in a,
  seemingly, non-deterministic fashion. I know that the password is
  correct and that the keymap is not a fault either, because I have
  specifically chosen the very weak password "123456" for testing
  purposes. A hardware defect seems also rather unlikely as this
  behavior does not affect other Linux distributions or FreeBSD. Earlier
  Ubuntu versions do not seem to be affected either, as this bug appears
  to have been introduced during a kernel update in 20.04 and persists
  throughout 20.04-22.04. Unfortunately I cannot pinpoint the exact
  kernel update that introduced this bug. I have appended the output of
  cryptsetup when manually called from the initramfs shell. Here the
  second attempt succeeded in decrypting the root partition, however, it
  usually takes a lot more attempts to do so.

  As for some additional information, I can decrypt the same luks
  partition from a live USB without any problems whatsoever.

  echo 123456 | cryptsetup open --type luks --debug /dev/nvme0n1p3 
nvme0n1p3_crypt
  # cryptsetup 2.4.3 processing "cryptsetup open --type luks --debug 
/dev/nvme0n1p3 nvme0n1p3_crypt"
  # Running command open.
  # Locking memory.
  # Installing SIGINT/SIGTERM handler.
  # Unblocking interruption on signal.
  # Allocating context for crypt device /dev/nvme0n1p3.
  # Trying to open and read device /dev/nvme0n1p3 with direct-io.
  # Initialising device-mapper backend library.
  # Trying to load any crypt type from device /dev/nvme0n1p3.
  # Crypto backend (OpenSSL 3.0.2 15 Mar 2022 [default]) initialized in 
cryptsetup library version 2.4.3.
  # Detected kernel Linux 5.15.0-46-generic x86_64.
  # Loading LUKS2 header (repair disabled).
  # Acquiring read lock for device /dev/nvme0n1p3.
  # Opening lock resource file /run/cryptsetup/L_259:3
  # Verifying lock handle for /dev/nvme0n1p3.
  # Device /dev/nvme0n1p3 READ lock taken.
  # Trying to read primary LUKS2 header at offset 0x0.
  # Opening locked device /dev/nvme0n1p3
  # Verifying locked device handle (bdev)
  # LUKS2 header version 2 of size 16384 bytes, checksum sha256.
  # Checksum:99172356e66a2fec247b1e5c758af8bc1338a3fb8bd973aab5e1512a93b2dbdc 
(on-disk)
  # Checksum:99172356e66a2fec247b1e5c758af8bc1338a3fb8bd973aab5e1512a93b2dbdc 
(in-memory)
  # Trying to read secondary LUKS2 header at offset 0x4000.
  # Reusing open ro fd on device /dev/nvme0n1p3
  # LUKS2 header version 2 of size 16384 bytes, checksum sha256.
  # Checksum:655a50aef64b6fd4e10b8863df72d7fc62a7020f74684cb3419d4e22adb6fd9c 
(on-disk)
  # Checksum:655a50aef64b6fd4e10b8863df72d7fc62a7020f74684cb3419d4e22adb6fd9c 
(in-memory)
  # Device size 497776852992, offset 16777216.
  # Device /dev/nvme0n1p3 READ lock released.
  # PBKDF argon2id, time_ms 2000 (iterations 0), max_memory_kb 1048576, 
parallel_threads 4.
  # Activating volume nvme0n1p3_crypt using token (any type) -1.
  # dm version   [ opencount flush ]   [16384] (*1)
  # dm versions   [ opencount flush ]   [16384] (*1)
  # Detected dm-ioctl version 4.45.0.
  # Detected dm-crypt version 1.23.0.
  # Device-mapper backend running with UDEV support enabled.
  # dm status nvme0n1p3_crypt  [ opencount noflush ]   [16384] (*1)
  No usable token is available.
  # STDIN descriptor passphrase entry requested.
  # Activating volume nvme0n1p3_crypt [keyslot -1] using passphrase.
  # dm versions   [ opencount flush ]   [16384] (*1)
  # dm status nvme0n1p3_crypt  [ opencount noflush ]   [16384] (*1)
  # Keyslot 0 priority 1 != 2 (required), skipped.
  # Keyslot 1 priority 1 != 2 (required), skipped.
  # Trying to open LUKS2 keyslot 0.
  # Running keyslot key derivation.
  # Reading keyslot area [0x8000].
  # Acquiring read lock for device /dev/nvme0n1p3.
  # Opening lock resource file /run/cryptsetup/L_259:3
  # Verifying lock handle for /dev/nvme0n1p3.
  # Device /dev/nvme0n1p3 READ lock taken.
  # Reusing open ro fd on device /dev/nvme0n1p3
  # Device /dev/nvme0n1p3 READ lock released.
  # Verifying key from keyslot 0, digest 0.
  # Digest 0 (pbkdf2) verify failed with -1.
  # Trying to open LUKS2 keyslot 1.
  # Running keyslot key derivation.
  # Reading keyslot area [0x47000].
  # Acquiring read lock for device /dev/nvme0n1p3.
  # Opening lock resource file /run/cryptsetup/L_259:3
  # Verifying lock handle for /dev/nvme0n1p3.
  # 

[Kernel-packages] [Bug 1938477] Re: [Dell Inspiron 7573] Screen brightness changing randomly with kernel 5.11.0-25

2022-11-19 Thread P B
I put in a Nvidia 3080 card with the 470 driver and the problem has gone
away if that helps anyone.  So possibly a driver issue for me on the
video card.

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

Title:
  [Dell Inspiron 7573] Screen brightness changing randomly with kernel
  5.11.0-25

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello guys!

  The brightness of the screen on my laptop (Dell 7573 with touch ips
  1080 panel) slightly changes randomly when using the laptop builtin
  display. It feels the same as I changed the brightness one step using
  the keyboard keys.

  Here is a video:
  
https://drive.google.com/file/d/1XQLXKLWu2TlOoGP-p8eaUGZR78713ErH/view?usp=sharing

  I suffer with this problem since a long time ago. I think since ubuntu
  19. I tried everything you can imagine, I will make a list of things
  I've tried. I had gave up trying to fix this already but in a
  beautiful sunny day suddenly the bug stopped happening. So I decided
  to report this bug now because this bug does NOT happen with only this
  version of the kernel: Linux 5.11.0-16-generic. So that can probably e
  useful to help discovering the bug reason.

  I am choosing this version on grub every time I reboot so the bug
  doesn't happen. If I boot on 5.11.0-25 the bug is back.

  List of things I've tried:
  - Changing i915 parameters like enable_psr to false and many others.
  - Upgrading BIOS version.
  - Installing windows and applying all the patches on dell's website and 
installing ubuntu again.
  - Disabling "dynamic backlight control" on BIOS.

  Some maybe useful info:
  - I've tried other distros like Fedora and PopOS and the same bug happens.
  - The bug does not happen when using live ubuntu from usb.
  - When you fresh install ubuntu (I've tried with 20.04, 20.10 and 21.04) the 
bug doesn't happen when you have just installed the os but it starts again 
after the first update. The same applies to the other distro's mentioned above.
  - When you disable i915 driver with modeset parameter, it does not happen.
  - The bug does NOT happen only with this kernel version 5.11.0-16-generic, 
BUT it starts happening again if I lock screen and login again. So I am never 
locking my screen and holding this kernel version for now.

  Thanks guys!

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: xorg 1:7.7+22ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jul 29 20:54:14 2021
  DistUpgraded: Fresh install
  DistroCodename: hirsute
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 6.1.18, 5.11.0-16-generic, x86_64: installed
   virtualbox, 6.1.18, 5.11.0-25-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Dell UHD Graphics 620 [1028:07ec]
  InstallationDate: Installed on 2021-07-25 (4 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: Dell Inc. Inspiron 7573
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic 
root=UUID=663d1a67-7acb-428f-a6c8-a9a259a5427c ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/06/2021
  dmi.bios.release: 1.18
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.18.1
  dmi.board.name: 023FRC
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.18.1:bd05/06/2021:br1.18:svnDellInc.:pnInspiron7573:pvr:rvnDellInc.:rn023FRC:rvrA00:cvnDellInc.:ct31:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7573
  dmi.product.sku: 07EC
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.105-3~21.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1938477/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : 

[Kernel-packages] [Bug 1938477] Re: [Dell Inspiron 7573] Screen brightness changing randomly with kernel 5.11.0-25

2022-11-18 Thread P B
Hi there.  I'm having the same problem.  When I'm looking at Firefox the
screen is nice and bright.  When I click on XTerm right next to it, the
whole screen dims noticeable.  I can do a video of it and replicate on
demand if needed.  When I click back on Firefox, the whole screen
brightens back up.  This is a fresh install of 22.04 - jammy.  Ubuntu
22.04.1 LTS

I'm running a normal desktop (not laptop) with a Nvidia 3070ti video
card.  So there is no video sensor to tell if the room is bright or
dark.  I've tried "xrandr --output HDMI-0 --brightness 1" but that
didn't make any difference.

AMD® Ryzen 5 3600 6-core processor × 12

# cat /etc/debian_version 
bookworm/sid

Linux myHost 5.15.0-53-generic #59-Ubuntu SMP Mon Oct 17 18:53:30 UTC
2022 x86_64 x86_64 x86_64 GNU/Linux

GNOME Version 42.5

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

Title:
  [Dell Inspiron 7573] Screen brightness changing randomly with kernel
  5.11.0-25

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello guys!

  The brightness of the screen on my laptop (Dell 7573 with touch ips
  1080 panel) slightly changes randomly when using the laptop builtin
  display. It feels the same as I changed the brightness one step using
  the keyboard keys.

  Here is a video:
  
https://drive.google.com/file/d/1XQLXKLWu2TlOoGP-p8eaUGZR78713ErH/view?usp=sharing

  I suffer with this problem since a long time ago. I think since ubuntu
  19. I tried everything you can imagine, I will make a list of things
  I've tried. I had gave up trying to fix this already but in a
  beautiful sunny day suddenly the bug stopped happening. So I decided
  to report this bug now because this bug does NOT happen with only this
  version of the kernel: Linux 5.11.0-16-generic. So that can probably e
  useful to help discovering the bug reason.

  I am choosing this version on grub every time I reboot so the bug
  doesn't happen. If I boot on 5.11.0-25 the bug is back.

  List of things I've tried:
  - Changing i915 parameters like enable_psr to false and many others.
  - Upgrading BIOS version.
  - Installing windows and applying all the patches on dell's website and 
installing ubuntu again.
  - Disabling "dynamic backlight control" on BIOS.

  Some maybe useful info:
  - I've tried other distros like Fedora and PopOS and the same bug happens.
  - The bug does not happen when using live ubuntu from usb.
  - When you fresh install ubuntu (I've tried with 20.04, 20.10 and 21.04) the 
bug doesn't happen when you have just installed the os but it starts again 
after the first update. The same applies to the other distro's mentioned above.
  - When you disable i915 driver with modeset parameter, it does not happen.
  - The bug does NOT happen only with this kernel version 5.11.0-16-generic, 
BUT it starts happening again if I lock screen and login again. So I am never 
locking my screen and holding this kernel version for now.

  Thanks guys!

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: xorg 1:7.7+22ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jul 29 20:54:14 2021
  DistUpgraded: Fresh install
  DistroCodename: hirsute
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 6.1.18, 5.11.0-16-generic, x86_64: installed
   virtualbox, 6.1.18, 5.11.0-25-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Dell UHD Graphics 620 [1028:07ec]
  InstallationDate: Installed on 2021-07-25 (4 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: Dell Inc. Inspiron 7573
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic 
root=UUID=663d1a67-7acb-428f-a6c8-a9a259a5427c ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/06/2021
  dmi.bios.release: 1.18
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.18.1
  dmi.board.name: 023FRC
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.18.1:bd05/06/2021:br1.18:svnDellInc.:pnInspiron7573:pvr:rvnDellInc.:rn023FRC:rvrA00:cvnDellInc.:ct31:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7573
  dmi.product.sku: 07EC
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.105-3~21.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  

[Kernel-packages] [Bug 1977919] Re: Docker container creation causes kernel oops on linux-aws 5.13.0.1028.31~20.04.22

2022-06-09 Thread Bill B.
So this was painful for us. AWS hosted server running Ubuntu 20.04.4
LTS. Just for others, here are the steps we took thanks to the other
comments here:

We had to force shut down the machine and wait (aws console). Then we
got this script running, and started the machine back up:

while true; do
  ssh -o ConnectTimeout=2 -i <.pem file> ubuntu@ "sudo systemctl disable 
docker.service; sudo systemctl disable containerd.service"
done

---
Now, ssh into machine normally, and this is what we ran in our case:
sudo -i
cd /boot/grub
grep -Ei 'submenu|menuentry ' /boot/grub/grub.cfg | sed -re "s/(.? 
)'([^']+)'.*/\1 \2/"
The result on mine was:
---
menuentry  Ubuntu
submenu  Advanced options for Ubuntu
menuentry  Ubuntu, with Linux 5.13.0-1028-aws # <-- BAD BAD BAD
menuentry  Ubuntu, with Linux 5.13.0-1028-aws (recovery mode)
menuentry  Ubuntu, with Linux 5.13.0-1025-aws # <-- what we want
menuentry  Ubuntu, with Linux 5.13.0-1025-aws (recovery mode)
menuentry  Ubuntu, with Linux 5.4.0-1029-aws
menuentry  Ubuntu, with Linux 5.4.0-1029-aws (recovery mode)
menuentry  Ubuntu 20.04.4 LTS (20.04) (on /dev/nvme0n1p1)
submenu  Advanced options for Ubuntu 20.04.4 LTS (20.04) (on /dev/nvme0n1p1)
menuentry  Ubuntu (on /dev/nvme0n1p1)
menuentry  Ubuntu, with Linux 5.13.0-1028-aws (on /dev/nvme0n1p1)
menuentry  Ubuntu, with Linux 5.13.0-1028-aws (recovery mode) (on 
/dev/nvme0n1p1)
menuentry  Ubuntu, with Linux 5.13.0-1025-aws (on /dev/nvme0n1p1)
menuentry  Ubuntu, with Linux 5.13.0-1025-aws (recovery mode) (on 
/dev/nvme0n1p1)
menuentry  Ubuntu, with Linux 5.4.0-1029-aws (on /dev/nvme0n1p1)
menuentry  Ubuntu, with Linux 5.4.0-1029-aws (recovery mode) (on 
/dev/nvme0n1p1)
---
So we wanted off 1028, and back to 1025. Edited: 
vi /etc/default/grub
changed:
GRUB_DEFAULT="Advanced options for Ubuntu>Ubuntu, with Linux 5.13.0-1025-aws"

NOTE: the first half is the "MENUENTRY" from above, then ">" and then the 
submenu.
Saved

run:
grub-mkconfig -o /boot/grub/grub.cfg
sudo reboot

then, after reboot:

sudo systemctl enable docker.service; sudo systemctl enable containerd.service
sudo reboot

Should be back up! It seems like upgrading to the newest kernel also
helps based on the above, but will try that later.

Hope this helps someone like you all helped us!!

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

Title:
  Docker container creation causes kernel oops on linux-aws
  5.13.0.1028.31~20.04.22

Status in linux-aws-5.13 package in Ubuntu:
  Confirmed
Status in linux-azure-5.13 package in Ubuntu:
  Confirmed
Status in linux-gcp-5.13 package in Ubuntu:
  Confirmed
Status in linux-intel-iotg-5.15 package in Ubuntu:
  Confirmed
Status in linux-oracle-5.13 package in Ubuntu:
  Confirmed
Status in linux-aws-5.13 source package in Focal:
  Fix Committed
Status in linux-azure-5.13 source package in Focal:
  Fix Committed
Status in linux-gcp-5.13 source package in Focal:
  Fix Committed
Status in linux-intel-iotg-5.15 source package in Focal:
  Won't Fix
Status in linux-oracle-5.13 source package in Focal:
  Fix Committed

Bug description:
  Running the attached script on the latest AWS AMI for Ubuntu 20.04, I
  get a kernel panic and hard reset of the node.

  [   12.314552] VFS: Close: file count is 0
  [   12.351090] [ cut here ]
  [   12.351093] kernel BUG at include/linux/fs.h:3104!
  [   12.355272] invalid opcode:  [#1] SMP PTI
  [   12.358963] CPU: 1 PID: 863 Comm: sed Not tainted 5.13.0-1028-aws 
#31~20.04.1-Ubuntu
  [   12.366241] Hardware name: Amazon EC2 m5.large/, BIOS 1.0 10/16/2017
  [   12.371130] RIP: 0010:__fput+0x247/0x250
  [   12.374897] Code: 00 48 85 ff 0f 84 8b fe ff ff f6 c7 40 0f 85 82 fe ff ff 
e8 ab 38 00 00 e9 78 fe ff ff 4c 89 f7 e8 2e 88 02 00 e9 b5 fe ff ff <0f> 0b 0f 
1f 80 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 53 31 db 48
  [   12.389075] RSP: 0018:b50280d9fd88 EFLAGS: 00010246
  [   12.393425] RAX:  RBX: 000a801d RCX: 
9152e0716000
  [   12.398679] RDX: 9152cf075280 RSI: 0001 RDI: 

  [   12.403879] RBP: b50280d9fdb0 R08: 0001 R09: 
9152dfcba2c8
  [   12.409102] R10: b50280d9fd88 R11: 9152d04e9d10 R12: 
9152d04e9d00
  [   12.414333] R13: 9152dfcba2c8 R14: 9152cf0752a0 R15: 
9152dfc2e180
  [   12.419533] FS:  () GS:9153ea90() 
knlGS:
  [   12.426937] CS:  0010 DS:  ES:  CR0: 80050033
  [   12.431506] CR2: 556cf30250a8 CR3: bce10006 CR4: 
007706e0
  [   12.436716] DR0:  DR1:  DR2: 

  [   12.441941] DR3:  DR6: fffe0ff0 DR7: 
0400
  [   12.447170] PKRU: 5554
  [   12.450355] 

[Kernel-packages] [Bug 1973482] [NEW] kernel 4.15.0.177 break everything on Dell XPS 15 9570

2022-05-15 Thread B Este
Public bug reported:

There are many issues including:

- wireless card DISBLED / UNCLAIMED
- no sound output device listed
- strange electrical noise in the speakers when the cpu is under load
- mounting /boot/efi hangs for 1m30
- various services not starting (snap, etc)

Rolling back to 4.15.0.176 fixes all the issues.

Can you let me know which logs I could provide to help?

Thank you

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-177-generic 4.15.0-177.186
ProcVersionSignature: Ubuntu 4.15.0-177.186-generic 4.15.18
Uname: Linux 4.15.0-177-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.27
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
CurrentDesktop: ubuntu:GNOME
Date: Mon May 16 00:39:58 2022
InstallationDate: Installed on 2018-12-15 (1247 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
IwConfig:
 virbr0no wireless extensions.
 
 lono wireless extensions.
 
 virbr0-nic  no wireless extensions.
MachineType: Dell Inc. XPS 15 9570
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-177-generic 
root=UUID=d62d426c-0675-4dca-a5e1-6c8b79ed8056 ro acpi_rev_override=1 
nouveau.modeset=0 pcie_aspm=force drm.vblankoffdelay=1 scsi_mod.use_blk_mq=1 
nouveau.runpm=0 mem_sleep_default=deep noibrs noibpb nopti nospectre_v2 
nospectre_v1 l1tf=off nospec_store_bypass_disable no_stf_barrier mds=off 
mitigations=off clocksource=hpet
RelatedPackageVersions:
 linux-restricted-modules-4.15.0-177-generic N/A
 linux-backports-modules-4.15.0-177-generic  N/A
 linux-firmware  1.173.20
RfKill:
 
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/07/2021
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.20.0
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.20.0:bd06/07/2021:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 15 9570
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug bionic

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

Title:
  kernel 4.15.0.177 break everything on Dell XPS 15 9570

Status in linux package in Ubuntu:
  New

Bug description:
  There are many issues including:

  - wireless card DISBLED / UNCLAIMED
  - no sound output device listed
  - strange electrical noise in the speakers when the cpu is under load
  - mounting /boot/efi hangs for 1m30
  - various services not starting (snap, etc)

  Rolling back to 4.15.0.176 fixes all the issues.

  Can you let me know which logs I could provide to help?

  Thank you

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-177-generic 4.15.0-177.186
  ProcVersionSignature: Ubuntu 4.15.0-177.186-generic 4.15.18
  Uname: Linux 4.15.0-177-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.27
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 16 00:39:58 2022
  InstallationDate: Installed on 2018-12-15 (1247 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  IwConfig:
   virbr0no wireless extensions.
   
   lono wireless extensions.
   
   virbr0-nic  no wireless extensions.
  MachineType: Dell Inc. XPS 15 9570
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-177-generic 
root=UUID=d62d426c-0675-4dca-a5e1-6c8b79ed8056 ro acpi_rev_override=1 
nouveau.modeset=0 pcie_aspm=force drm.vblankoffdelay=1 scsi_mod.use_blk_mq=1 
nouveau.runpm=0 mem_sleep_default=deep noibrs noibpb nopti nospectre_v2 
nospectre_v1 l1tf=off nospec_store_bypass_disable no_stf_barrier mds=off 
mitigations=off clocksource=hpet
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-177-generic N/A
   linux-backports-modules-4.15.0-177-generic  N/A
   linux-firmware  1.173.20
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/07/2021
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.20.0
  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.20.0:bd06/07/2021:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9570
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1969986] [NEW] AMDGPU driver confused by two AMD GPUs

2022-04-22 Thread J-B Vosteen
Public bug reported:

When I start a game (Surviving Mars) via Steam the framerates are
abysmal, somewhere between 10 to 20 fps. On 17.4.22 it still hit 60 fps.

When my screen is attached to the 6600 XT card and the game is running,
the following can be seen:

jan-bart@barts-tuxbox:/sys$ cat  
./devices/pci:00/:00:01.1/:10:00.0/:11:00.0/:12:00.0/pp_dpm_sclk
0: 500Mhz 
1: 700Mhz *
2: 2900Mhz 
jan-bart@barts-tuxbox:/sys$ cat 
./devices/pci:00/:00:08.1/:30:00.0/pp_dpm_sclk
0: 200Mhz 
1: 700Mhz 
2: 2000Mhz *
jan-bart@barts-tuxbox:/sys$ lspci | grep VGA
12:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Navi 
23 [Radeon RX 6600/6600 XT/6600M] (rev c1)
30:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Cezanne (rev c8)

For some reason the clock of the unused graphics device is increased.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-5.15.0-25-generic 5.15.0-25.25
ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
Uname: Linux 5.15.0-25-generic x86_64
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC2:  jan-bart   1677 F pulseaudio
 /dev/snd/controlC0:  jan-bart   1677 F pulseaudio
 /dev/snd/controlC1:  jan-bart   1677 F pulseaudio
CasperMD5CheckResult: pass
CurrentDesktop: GNOME
Date: Fri Apr 22 20:53:17 2022
InstallationDate: Installed on 2022-03-20 (32 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220319)
MachineType: Micro-Star International Co., Ltd. MS-7C92
ProcFB:
 0 amdgpudrmfb
 1 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic 
root=UUID=cc17c347-c0ab-47b6-9c92-86a6b2826ddc ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.15.0-25-generic N/A
 linux-backports-modules-5.15.0-25-generic  N/A
 linux-firmware 20220329.git681281e4-0ubuntu1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/21/2021
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: 1.80
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: MPG B550I GAMING EDGE MAX WIFI (MS-7C92)
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: 1.0
dmi.chassis.asset.tag: To be filled by O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvr1.80:bd12/21/2021:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C92:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMPGB550IGAMINGEDGEMAXWIFI(MS-7C92):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: MS-7C92
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: 1.0
dmi.sys.vendor: Micro-Star International Co., Ltd.

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


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

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

Title:
  AMDGPU driver confused by two AMD GPUs

Status in linux package in Ubuntu:
  New

Bug description:
  When I start a game (Surviving Mars) via Steam the framerates are
  abysmal, somewhere between 10 to 20 fps. On 17.4.22 it still hit 60
  fps.

  When my screen is attached to the 6600 XT card and the game is
  running, the following can be seen:

  jan-bart@barts-tuxbox:/sys$ cat  
./devices/pci:00/:00:01.1/:10:00.0/:11:00.0/:12:00.0/pp_dpm_sclk
  0: 500Mhz 
  1: 700Mhz *
  2: 2900Mhz 
  jan-bart@barts-tuxbox:/sys$ cat 
./devices/pci:00/:00:08.1/:30:00.0/pp_dpm_sclk
  0: 200Mhz 
  1: 700Mhz 
  2: 2000Mhz *
  jan-bart@barts-tuxbox:/sys$ lspci | grep VGA
  12:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Navi 23 [Radeon RX 6600/6600 XT/6600M] (rev c1)
  30:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Cezanne (rev c8)

  For some reason the clock of the unused graphics device is increased.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-25-generic 5.15.0-25.25
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  jan-bart   1677 F pulseaudio
   /dev/snd/controlC0:  jan-bart   1677 F pulseaudio
   /dev/snd/controlC1:  jan-bart   1677 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: GNOME
  Date: Fri Apr 22 20:53:17 2022
  InstallationDate: Installed on 2022-03-20 (32 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220319)
  

[Kernel-packages] [Bug 1849084] Re: Freeze on system-resume caused by kwin and amdgpu driver

2022-03-22 Thread P. B.
After 23 months without this Standby/Resume bug, it has now reappeared - See 
#30 above
System; Lenovo V155-15API (V155 Series)
Processor; AMD Ryzen 5 3500U
Graphics adapter; AMD Radeon RX Vega 8
Memory; 12288 MB (Windows partition)

Dual booting Windows 10 & Ubuntu 20.04.4 LTS (Ubuntu being main OS on separate 
partition)
Bug present under both Ubuntu & Windows
In Windows I once again ran the AMD Driver Auto-detect tool & let it install 
the drivers it detected as needed or needing updating. This fixed the problem 
in April 2020 but it has had no effect in 2022.

In the Windows partition Lenovo want to install a BIOS upgrade, but I'm
concerned about possible effect on the dual boot.

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

Title:
  Freeze on system-resume caused by kwin and amdgpu driver

Status in kwin package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in plasma-desktop package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Confirmed

Bug description:
  This is a well investigated bug by me.

  Problem: a black screen freeze occurs by suspend-resume process
  Ubuntu version: Kubuntu 19.10 default plasma, or the backported 5.17
  Kernel version: default 5.3.10 or the mainline 5.4.0rc3
  xserver-xorg-video-amdgpu: 19.* or the newest from git, the 18.0.1-1 works 
well

  This freeze can be reproduced only if opengl 2.0 or 3.1 compositor is
  enabled in Plasma settings. Xrender is OK however I don't like screen
  tearing.

  On Ubuntu 19.10 Gnome desktop (X based) this doesn't occur even if the
  Gnome's compositor is enabled. (I don't know what is the default one
  there but I haven't disabled it)

  I think this is a Kwin / amdgpu driver related bug because of the
  differentiation. These can be fixed even in Kwin/opengl compositor not
  just in the amdgpu driver or in kernel.

  One possible solution: disable opengl compositor by suspend and re-
  enable it after login. Use fe.: Xrender before login / before the
  system restored from suspend.

  For Ubuntu's maintainers: Couldn't be this problem solved by a
  downstream solution? Maybe a proper script could be enough by resume
  and by suspend. There are a lot of bugs like this reported in
  freedesktop bugreport and the developers haven't got enough time for
  fix them fast enough.


  Syslog:

  Oct 21 10:57:26 pc kernel: [ 9475.308852] Code: 85 78 ff ff ff e9 9f f8 ff ff 
8b b0 98 04 00 00 48 c7 c7 ef 5f a5 c0 e8 49 2d 9d ff 44 0f b6 45 a3 49 8b 4d 
08 e9 bf fa ff ff <0f> 0b e9 ca fb ff ff 0f 0b e8 7d 36 84 c1 66 66 2e 0f 1f 84 
00 00
  Oct 21 10:57:26 pc kernel: [ 9475.308853] RSP: 0018:b7b54274b7b0 EFLAGS: 
00010002
  Oct 21 10:57:26 pc kernel: [ 9475.308855] RAX: 0202 RBX: 
0202 RCX: 046a
  Oct 21 10:57:26 pc kernel: [ 9475.308856] RDX: 0001 RSI: 
0202 RDI: 0002
  Oct 21 10:57:26 pc kernel: [ 9475.308857] RBP: b7b54274b870 R08: 
 R09: 94da76b2d170
  Oct 21 10:57:26 pc kernel: [ 9475.308858] R10: b7b54274b708 R11: 
b7b54274b70c R12: 94da76b2d000
  Oct 21 10:57:26 pc kernel: [ 9475.308859] R13: 94d970f2c300 R14: 
94da758d25d0 R15: 94da270d1400
  Oct 21 10:57:26 pc kernel: [ 9475.308861] FS:  7f2a1b9bea80() 
GS:94da87c4() knlGS:
  Oct 21 10:57:26 pc kernel: [ 9475.308863] CS:  0010 DS:  ES:  CR0: 
80050033
  Oct 21 10:57:26 pc kernel: [ 9475.308864] CR2: 7fb083e9b4a5 CR3: 
00012c11 CR4: 003406e0
  Oct 21 10:57:26 pc kernel: [ 9475.308865] Call Trace:
  Oct 21 10:57:26 pc kernel: [ 9475.308977]  
amdgpu_dm_atomic_commit_tail+0x96f/0x1030 [amdgpu]
  Oct 21 10:57:26 pc kernel: [ 9475.308991]  commit_tail+0x50/0xc0 
[drm_kms_helper]
  Oct 21 10:57:26 pc kernel: [ 9475.309000]  ? commit_tail+0x50/0xc0 
[drm_kms_helper]
  Oct 21 10:57:26 pc kernel: [ 9475.309009]  
drm_atomic_helper_commit+0x118/0x120 [drm_kms_helper]
  Oct 21 10:57:26 pc kernel: [ 9475.309115]  amdgpu_dm_atomic_commit+0x95/0xa0 
[amdgpu]
  Oct 21 10:57:26 pc kernel: [ 9475.309135]  drm_atomic_commit+0x4a/0x50 [drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309144]  
drm_atomic_helper_set_config+0x89/0xa0 [drm_kms_helper]
  Oct 21 10:57:26 pc kernel: [ 9475.309159]  drm_mode_setcrtc+0x1cd/0x7a0 [drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309234]  ? amdgpu_cs_wait_ioctl+0xd6/0x150 
[amdgpu]
  Oct 21 10:57:26 pc kernel: [ 9475.309249]  ? drm_mode_getcrtc+0x190/0x190 
[drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309262]  drm_ioctl_kernel+0xae/0xf0 [drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309276]  drm_ioctl+0x234/0x3d0 [drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309290]  ? drm_mode_getcrtc+0x190/0x190 
[drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309370]  amdgpu_drm_ioctl+0x4e/0x80 [amdgpu]
  Oct 21 10:57:26 pc kernel: [ 

[Kernel-packages] [Bug 1911055] Re: [modeset][nvidia] suspend/resume broken in nvidia-460 : Display engine push buffer channel allocation failed

2022-02-14 Thread Shawn B
I recently was able to work around this issue using the nvidia 510 drivers and 
following this suggestion: 
https://forums.developer.nvidia.com/t/fixed-suspend-resume-issues-with-the-driver-version-470/187150/3

Thus far no issues with resuming. Not sure if it helps with 460 but
thought I'd share.

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

Title:
  [modeset][nvidia] suspend/resume broken in nvidia-460 : Display engine
  push buffer channel allocation failed

Status in nvidia-graphics-drivers-460 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Confirmed

Bug description:
  After a recent update to nvidia-460, suspend then resume results in a
  black screen, then a hang for around 120 seconds, and then the text:

  nvidia-modeset: ERROR: GPU:0: Display engine push buffer channel allocation 
failed: 0x65 (Call timed out [NV_ERR_TIMEOUT])
  nvidia-modeset: ERROR: GPU:0: Failed to allocate display engine core DMA push 
buffer
  nvidia-modeset: ERROR: GPU:0: Display engine push buffer channel allocation 
failed: 0x65 (Call timed out [NV_ERR_TIMEOUT])
  nvidia-modeset: ERROR: GPU:0: Failed to allocate display engine core DMA push 
buffer

  dmesg shows:

  [  188.352670] ACPI: Waking up from system sleep state S3
  ...
  [  309.142164] nvidia-modeset: ERROR: GPU:0: Display engine push buffer 
channel allocation failed: 0x65 (Call timed out [NV_ERR_TIMEOUT])
  [  309.142319] nvidia-modeset: ERROR: GPU:0: Failed to allocate display 
engine core DMA push buffer
  [  313.142165] nvidia-modeset: ERROR: GPU:0: Display engine push buffer 
channel allocation failed: 0x65 (Call timed out [NV_ERR_TIMEOUT])
  [  313.142348] nvidia-modeset: ERROR: GPU:0: Failed to allocate display 
engine core DMA push buffer
  [  313.151885] acpi LNXPOWER:08: Turning OFF
  [  313.151898] acpi LNXPOWER:04: Turning OFF
  [  313.152351] acpi LNXPOWER:03: Turning OFF
  [  313.153064] acpi LNXPOWER:02: Turning OFF
  ...
  [  325.010192] nvidia-modeset: WARNING: GPU:0: Unable to read EDID for 
display device DELL 2209WA (HDMI-0)
  [  325.010577] BUG: kernel NULL pointer dereference, address: 0050
  [  325.010579] #PF: supervisor read access in kernel mode
  [  325.010580] #PF: error_code(0x) - not-present page
  [  325.010580] PGD 0 P4D 0
  [  325.010582] Oops:  [#1] SMP PTI
  [  325.010583] CPU: 9 PID: 2247 Comm: Xorg Tainted: P   O  
5.4.0-60-generic #67-Ubuntu
  [  325.010584] Hardware name: Razer Blade/DANA_MB, BIOS 01.01 08/31/2018
  [  325.010595] RIP: 0010:_nv000112kms+0xd/0x30 [nvidia_modeset]
  [  325.010596] Code: 16 00 74 06 83 7e 0c 02 77 03 31 c0 c3 c7 46 0c 01 00 00 
00 b8 01 00 00 00 c3 0f 1f 00 0f b7 46 04 0f b7 56 08 39 d0 0f 47 c2 <3b> 47 18 
77 06 83 7e 10 02 77 08 31 c0 c3 0f 1f 44 00 00 c7 46 10
  [  325.010597] RSP: 0018:b89542e5b8a8 EFLAGS: 00010246
  [  325.010598] RAX: 0280 RBX: 0038 RCX: 
03ff
  [  325.010598] RDX: 0280 RSI: b89542e5bba0 RDI: 
0038
  [  325.010599] RBP: b89542e5b9c8 R08:  R09: 
c379e440
  [  325.010600] R10:  R11:  R12: 
b89542e5b948
  [  325.010600] R13: b89542e5b948 R14: b89542e5b930 R15: 
c3a50e60
  [  325.010601] FS:  7feb4c09ea80() GS:8e46ada4() 
knlGS:
  [  325.010602] CS:  0010 DS:  ES:  CR0: 80050033
  [  325.010602] CR2: 0050 CR3: 0004772e2006 CR4: 
003606e0
  [  325.010603] Call Trace:
  [  325.010610]  ? _nv002768kms+0x96/0xd0 [nvidia_modeset]
  [  325.010616]  ? _nv002328kms+0xb5/0x110 [nvidia_modeset]
  [  325.010624]  ? _nv000742kms+0x168/0x370 [nvidia_modeset]
  [  325.010823]  ? _nv036002rm+0x62/0x70 [nvidia]
  [  325.010910]  ? os_get_current_tick+0x2c/0x50 [nvidia]
  [  325.010921]  ? _nv002771kms+0x433/0x600 [nvidia_modeset]
  [  325.010928]  ? _nv002771kms+0x3fc/0x600 [nvidia_modeset]
  [  325.010930]  ? __schedule+0x2eb/0x740
  [  325.010935]  ? _nv000742kms+0x40/0x40 [nvidia_modeset]
  [  325.010939]  ? nvkms_alloc+0x6a/0xa0 [nvidia_modeset]
  [  325.010944]  ? _nv000742kms+0x40/0x40 [nvidia_modeset]
  [  325.010948]  ? _nv000744kms+0x2a/0x40 [nvidia_modeset]
  [  325.010952]  ? nvKmsIoctl+0x96/0x1d0 [nvidia_modeset]
  [  325.010957]  ? nvkms_ioctl_common+0x42/0x80 [nvidia_modeset]
  [  325.010961]  ? nvkms_ioctl+0xc4/0x100 [nvidia_modeset]
  [  325.011016]  ? nvidia_frontend_unlocked_ioctl+0x3b/0x50 [nvidia]
  [  325.011017]  ? do_vfs_ioctl+0x407/0x670
  [  325.011019]  ? do_user_addr_fault+0x216/0x450
  [  325.011020]  ? ksys_ioctl+0x67/0x90
  [  325.011021]  ? __x64_sys_ioctl+0x1a/0x20
  [  325.011023]  ? do_syscall_64+0x57/0x190
  [  325.011024]  ? entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [  325.011025] Modules linked in: rfcomm ccm aufs 

[Kernel-packages] [Bug 1958591] Re: [amdgpu] Random noise 'static' display after internal display turned off/on

2022-01-28 Thread Simon B
Hi, 
I have been experiencing the same problem for several days. I have to press 
escape when I launch my laptop, to display its screen correctly. Otherwise, as 
mentioned before, I get a multicolored snow. If my screen goes to sleep, it 
also happens. 
I use a Tuxedo computer Pulse, with a Ryzen 7 4800h. Under Kubuntu.

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

Title:
  [amdgpu] Random noise 'static' display after internal display turned
  off/on

Status in linux-hwe-5.13 package in Ubuntu:
  Confirmed

Bug description:
  Laptop internal display shows random looking 'static' after it's
  turned off and then on again.   e.g. on suspend/resume, or when
  plugging/unplugging an external monitor.

  This appeared to come after a `dist-upgrade` took the kernel from
  5.11.0-44 to 5.13.0-25 (hwe).

  Others are seeing this with both NVidia and AMD graphics hardware:
  - 
https://www.reddit.com/r/Ubuntu/comments/s8c83w/laptop_shows_static_screen_after_going_into_lock/
  - 
https://www.reddit.com/r/Ubuntu/comments/s8fit0/please_help_static_noise_display_on_ubuntu_2004/

  I use i3 under gnome-flashback, but tried using default Ubuntu/Gnome
  both X and Wayland, and gnome-flashback/metacity.  All showed the same
  problem.

  Also tried an `apt install --reinstall xserver-xorg-video-radeon
  libdrm-radeon1` for luck - no joy.

  Running a 20.04.3 live stick the problem does *not* occur.

  System: Thinkpad X13 Gen1
  Processor: AMD Ryzen 7 PRO 4750U
  System Firmware: 1.35

  $ lsb_release -rd
  Description:Ubuntu 20.04.3 LTS
  Release:20.04

  Happy to assist with investigations.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: i3-GNOME-Flashback:GNOME-Flashback:GNOME
  Date: Thu Jan 20 19:37:09 2022
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev d1) (prog-if 
00 [VGA controller])
 Subsystem: Lenovo Renoir [17aa:5082]
  InstallationDate: Installed on 2021-06-24 (210 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: LENOVO 20UF0014US
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-27-generic 
root=UUID=5db0269f-fa23-487e-ace8-ba99bca814a8 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/20/2021
  dmi.bios.release: 1.36
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1CET67W(1.36 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20UF0014US
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.36
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1CET67W(1.36):bd10/20/2021:br1.36:efr1.36:svnLENOVO:pn20UF0014US:pvrThinkPadX13Gen1:rvnLENOVO:rn20UF0014US:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20UF_BU_Think_FM_ThinkPadX13Gen1:
  dmi.product.family: ThinkPad X13 Gen 1
  dmi.product.name: 20UF0014US
  dmi.product.sku: LENOVO_MT_20UF_BU_Think_FM_ThinkPad X13 Gen 1
  dmi.product.version: ThinkPad X13 Gen 1
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.105-3~20.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.5
  version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.5
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1958591/+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 1948502] Re: TP-Link UB500 Bluetooth USB adapter not working properly

2022-01-14 Thread Muthukannan B
Could you please let us know when this fix will be available for Ubuntu
Ubuntu 20.04.3 LTS?

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

Title:
  TP-Link UB500 Bluetooth USB adapter not working properly

Status in linux package in Ubuntu:
  Confirmed
Status in linux package in Arch Linux:
  Fix Released

Bug description:
  I have just bought a Tp-link bluetooth 5.0 usb adapter (UB500). According to 
this website https://usb-ids.gowdy.us/read/UD/2357/0604 the chip is Realtek 
RTL8761B. 
  It works just fine on Windows 10, but I'm having problems on Ubuntu. 

  I'm running Ubuntu 21.10 with the 5.14.14-051414-generic kernel

  The adapter seems to be correctly installed and properly working,
  however scanning does not pick up any bluetooth device. I've tried two
  headsets (that I know are properly working) and my phone, with no
  success. When performing a scan on my phone, the computer doesn't show
  up, even if I've set it to visible.

  (I'm sorry if the information is not complete, but ubuntu-bug is not
  working for me)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948502/+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 1956396] Re: kernel 5.13.0-23 extremely slow boot on AMD proc/graphics

2022-01-05 Thread max b
Computer became unusable.
Takes forever to start. Fails to shutdown. In the console (Ctrl+alt+f2) reports 
kernel panic.
Ryzen 3500U.

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

Title:
   kernel 5.13.0-23 extremely slow boot on AMD proc/graphics

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  5.13.0-23 HWE kernel on Linux Mint 20.2 Xfce (Ubuntu 20.04.3)
  Had been using the 5.13 HWE kernel for months with no problems.
  Today the kernel and linux-firmware updated.
  5.13.0-23 kernel now takes about 2 minutes to boot to the login screen.
  Normal boot time is 8 seconds.
  During that time the pc is frozen with only a _ underline cursor that doesn't 
flash.
  Can't change terminals with Ctrl+Alt+F1, etc.
  Problem does not occur when booting 5.11.0-44 or 5.4.0-92 so I'm pretty sure 
the problem is in the kernel and not linux-firmware.

  System information (while using 5.11 kernel)
  CPU:   Topology: Quad Core model: AMD Ryzen 5 3400G with Radeon Vega 
Graphics bits: 64 type: MT MCP
     arch: Zen+ rev: 1 L2 cache: 2048 KiB
     flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 
svm bogomips: 59089
     Speed: 1259 MHz min/max: 1400/3700 MHz boost: enabled Core speeds 
(MHz): 1: 1258 2: 1258
     3: 1258 4: 1258 5: 1257 6: 1260 7: 1267 8: 1330

  Graphics:  Device-1: AMD Picasso vendor: Hewlett-Packard driver: amdgpu v: 
kernel bus ID: 0c:00.0
     chip ID: 1002:15d8
     Display: x11 server: X.Org 1.20.13 driver: amdgpu resolution: 
1920x1080~60Hz
     OpenGL:
     renderer: AMD Radeon Vega 11 Graphics (RAVEN DRM 3.40.0 
5.11.0-44-generic LLVM 12.0.0)
     v: 4.6 Mesa 21.0.3 direct render: Yes

  Forums threads about it:
  https://ubuntuforums.org/showthread.php?t=2470574
  https://forums.linuxmint.com/viewtopic.php?f=46=364729

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956396/+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 1857385] Re: xHCI host controller not responding, assume dead via USB-C docking station

2021-11-13 Thread Walex B
This is happening to me on a ThinkPad E495 with AMD chipset and no
docking station, with Ubuntu LTS 20, kernel 5.11.0-40-generic (latest
HWE), for example on inserting an USB mouse:

Nov 11 19:00:52 cyme upowerd[2469]: treating change event as add on 
/sys/devices/pci:00/:00:08.1/:05:00.3/usb1/1-4
Nov 11 19:00:52 cyme kernel: usb usb1-port4: disabled by hub (EMI?), 
re-enabling...
Nov 11 19:00:52 cyme kernel: usb 1-4: USB disconnect, device number 18
Nov 11 19:00:52 cyme kernel: usb 1-4: new low-speed USB device number 19 using 
xhci_hcd
Nov 11 19:01:03 cyme kernel: xhci_hcd :05:00.3: xHCI host not responding to 
stop endpoint command.
Nov 11 19:01:03 cyme kernel: [43B blob data]
Nov 11 19:01:03 cyme kernel: xhci_hcd :05:00.3: xHCI host controller not 
responding, assume dead
Nov 11 19:01:03 cyme kernel: xhci_hcd :05:00.3: HC died; cleaning up
Nov 11 19:01:03 cyme kernel: usb usb1-port4: couldn't allocate usb_device


The workaround described in comment #22 above, to unbind and then bind the 
devices, works for me too. Weird. It did not seem to happen with earlier recent 
kernel version, but not sure when i started to happen.

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

Title:
  xHCI host controller not responding, assume dead via USB-C docking
  station

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello,
  I'm using a Lenovo T495s with the Lenovo AJ40 - Ultra Docking Station USB-C 
(https://support.lenovo.com/us/en/solutions/pd500173O) and, when I undock the 
laptop from the docking station, the USB Hub disconnects all the local laptop 
USB ports and they are unusable.
  If I try to re-attach the laptop to the docking station nothing change, the 
ports (docking and laptop) are still disconnected, the hdmi/lan/power is 
working good. Sometimes it happens also when the laptop is docked and I'm 
working.

  The issue seems similar of the bug 1766076:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766076

  but here no thunderbolt, it's a ryzen cpu.
  As written in the bug 1766076, the only way to have the USB in working 
condition is unbinding/binding the xhci or using the unit/systemd workaround 
described on post 83 
(https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766076/comments/83) with 
some modification, sometimes is still not working at all.

  The issue is present on Ubuntu 19.10 (see below the logs), on Ubuntu
  18.04 (with kernel 4.x or 5.0 mainline by ubuntu, 5.2 and 5.4 debs
  installed from kernel.org) and on Fedora 31 too. In Windows everything
  is working fine.

  The bios and firmware of the docking station are updated to the last
  one (1 month ago).

  The dmesg when I undock the laptop:

  [  305.299725] usb 2-1: USB disconnect, device number 2
  [  305.310888] [drm] DM_MST: stopping TM on aconnector: 8e933bad [id: 
77]
  [  305.311186] [drm] DM_MST: Disabling connector: 0c5e8d66 [id: 81] 
[master: 8e933bad]
  [  305.311957] [drm] DM_MST: Disabling connector: b7fb3125 [id: 86] 
[master: 8e933bad]
  [  305.312136] [drm] DM_MST: Disabling connector: e642e447 [id: 91] 
[master: 8e933bad]
  [  305.362012] r8169 :03:00.0 enp3s0f0: Link is Down
  [  305.464627] usb 3-4: USB disconnect, device number 2
  [  305.464642] usb 3-4.2: USB disconnect, device number 3
  [  305.472691] usb 2-4: USB disconnect, device number 4
  [  305.472704] usb 2-4.2: USB disconnect, device number 5
  [  305.472712] usb 2-4.2.4: USB disconnect, device number 7
  [  306.725746] usb 2-4.2.4: 2:1: usb_set_interface failed (-19)
  [  306.725892] usb 2-4.2.4: 2:1: usb_set_interface failed (-19)
  ...hundreds of line - the same
  [  310.520323] usb 2-4.2.4: 2:1: usb_set_interface failed (-19)
  [  310.520504] xhci_hcd :05:00.3: xHCI host not responding to stop 
endpoint command.
  [  310.520622] usb 2-4.2.4: 2:1: usb_set_interface failed (-19)
  hundreds of line - the same
  [  310.529388] usb 2-4.2.4: 2:1: usb_set_interface failed (-19)
  [  310.529626] usb 2-4.2.4: 2:1: usb_set_interface failed (-19)
  [  310.530634] usb 2-4.2.4: 2:1: usb_set_interface failed (-19)
  [  310.530740] usb 2-4.2.4: 2:1: usb_set_interface failed (-19)
  [  310.530843] usb 2-4.2.4: 2:1: usb_set_interface failed (-19)
  [  310.531095] usb 2-4.2.4: 2:1: usb_set_interface failed (-19)
  [  310.531324] usb 2-4.2.4: 2:1: usb_set_interface failed (-19)
  [  310.532315] xhci_hcd :05:00.3: xHCI host controller not responding, 
assume dead
  [  310.532379] xhci_hcd :05:00.3: HC died; cleaning up
  [  310.532440] xhci_hcd :05:00.3: Timeout while waiting for configure 
endpoint command
  [  310.670248] usb 2-4.3: USB disconnect, device number 6
  [  310.834039] usb 2-4.5: USB disconnect, device number 8
  [  310.835017] usb 2-2: USB disconnect, device number 10

  When I re-attach the latop to 

[Kernel-packages] [Bug 1950842] [NEW] Bluetooth Adapter Not Detected

2021-11-12 Thread Alex B
Public bug reported:

Attempted every Stackoverflow & related solution I could find, at this
point I can only assume this is a bug.

Installed Ubuntu 21.10 on ASUS-TUF-Gaming-F17-FX706HM-TUF706HM. No
Bluetooth devices can connect.

Exact symptoms:

Click on the taskbar. It says Bluetooth Off. When I expand that, it
gives me the option to turn Bluetooth off. That is not a typo.

Go into Settings->Bluetooth. Sliding button on the top says Bluetooth is
on (button is on the right, filled in purple), but the page says
Bluetooth is off.

ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: linux-image-5.13.0-20-generic 5.13.0-20.20
ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
Uname: Linux 5.13.0-20-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu71
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  alex   1632 F pulseaudio
 /dev/snd/pcmC0D0p:   alex   1632 F...m pulseaudio
 /dev/snd/controlC1:  alex   1632 F pulseaudio
CasperMD5CheckResult: pass
Date: Fri Nov 12 20:52:18 2021
InstallationDate: Installed on 2021-11-07 (5 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
MachineType: ASUSTeK COMPUTER INC. ASUS TUF Gaming F17 FX706HM_TUF706HM
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-20-generic 
root=UUID=46136636-f0da-438b-826d-858cd17bf141 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.
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
 linux-restricted-modules-5.13.0-20-generic N/A
 linux-backports-modules-5.13.0-20-generic  N/A
 linux-firmware 1.201.1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/05/2021
dmi.bios.release: 5.19
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: FX706HM.309
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: FX706HM
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.ec.firmware.release: 3.6
dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrFX706HM.309:bd10/05/2021:br5.19:efr3.6:svnASUSTeKCOMPUTERINC.:pnASUSTUFGamingF17FX706HM_TUF706HM:pvr1.0:sku:rvnASUSTeKCOMPUTERINC.:rnFX706HM:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: ASUS TUF Gaming F17
dmi.product.name: ASUS TUF Gaming F17 FX706HM_TUF706HM
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


** Tags: amd64 apport-bug impish

** Attachment added: "attachments.tar.gz"
   
https://bugs.launchpad.net/bugs/1950842/+attachment/5540538/+files/attachments.tar.gz

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

Title:
  Bluetooth Adapter Not Detected

Status in linux package in Ubuntu:
  New

Bug description:
  Attempted every Stackoverflow & related solution I could find, at this
  point I can only assume this is a bug.

  Installed Ubuntu 21.10 on ASUS-TUF-Gaming-F17-FX706HM-TUF706HM. No
  Bluetooth devices can connect.

  Exact symptoms:

  Click on the taskbar. It says Bluetooth Off. When I expand that, it
  gives me the option to turn Bluetooth off. That is not a typo.

  Go into Settings->Bluetooth. Sliding button on the top says Bluetooth
  is on (button is on the right, filled in purple), but the page says
  Bluetooth is off.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: linux-image-5.13.0-20-generic 5.13.0-20.20
  ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
  Uname: Linux 5.13.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alex   1632 F pulseaudio
   /dev/snd/pcmC0D0p:   alex   1632 F...m pulseaudio
   /dev/snd/controlC1:  alex   1632 F pulseaudio
  CasperMD5CheckResult: pass
  Date: Fri Nov 12 20:52:18 2021
  InstallationDate: Installed on 2021-11-07 (5 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: ASUSTeK COMPUTER INC. ASUS TUF Gaming F17 FX706HM_TUF706HM
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-20-generic 
root=UUID=46136636-f0da-438b-826d-858cd17bf141 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit 

[Kernel-packages] [Bug 1358153] Re: Keyboard and touchpad randomly crash after boot

2021-09-03 Thread Abhijith B
this issue is coming again now

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

Title:
  Keyboard and touchpad randomly crash after boot

Status in linux package in Ubuntu:
  Triaged

Bug description:
  After the OS boots, the keyboard and the touchpad crash and I cannot
  even type my password to log in.

  This bug is a quite old one, and present in multiple distributions, so
  I think it might be a kernel bug, but I am not sure.

  The OS itself doesn't freeze, I can use a mouse instead of the
  touchpad, and if I had an external USB keyboard, it would work also.

  One more thing: when this problem occurs, I cannot simply reboot or
  turn off the machine by selecting the appropriate option from the
  system menu, because this way the system hangs with a black screen. I
  can turn off only by pressing the power-off button.

  I am using Ubuntu 14.04 with this kernel: Ubuntu 3.13.0-32.57-generic 
3.13.11.4
  --- 
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2014-08-29 (5 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  Package: linux (not installed)
  Tags:  trusty
  Uname: Linux 3.17.0-031700rc3-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  --- 
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  dani   2181 F pulseaudio
   /dev/snd/controlC0:  dani   2181 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=a9f6f696-577f-4995-8f13-ffd629ddff13
  InstallationDate: Installed on 2014-08-29 (6 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: ASUSTeK Computer Inc. 1225B
  NonfreeKernelModules: wl
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-35-generic 
root=UUID=a4260107-7842-4e50-b922-9f8387c0e9f1 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-35-generic N/A
   linux-backports-modules-3.13.0-35-generic  N/A
   linux-firmware 1.127.5
  StagingDrivers: keucr
  Tags:  trusty staging
  Uname: Linux 3.13.0-35-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 06/05/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 209
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: 1225B
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 209
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr209:bd06/05/2012:svnASUSTeKComputerInc.:pn1225B:pvr1.0:rvnASUSTeKComputerInc.:rn1225B:rvr209:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.name: 1225B
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1358153/+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 1543919] Re: Remove EISA support from main kernel image and make it M (modular)

2021-07-19 Thread B. C. Schmerker
I've an emachines®/acer® EL1210-09 (Advance Micro Devices Inc. Athlon
LE-1620 (P/N ADH1620IAA5DH); nVIDIA® nForce® 780a SLI with planar C77 a2
GPU; nVIDIA® GF119 a1 GPU on PCIe 2.0 x16 slot).  The system DMesg
predictably detects no EISA resources on probing platform eisa.0, so
EISA.c and related headers can be compiled as a module with no effect on
my system's kernel initialization.  AFAIK, Intel PCI has replaced EISA
on all x86 and x86_64 systems built after 2000.  The following redact
from /var/log/dmesg.0 on 17 July 2021 illustrates typical info:

[0.00] kernel: Linux version 5.8.0-59-generic (buildd@lcy01-amd64-022) 
(gcc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0, GNU ld (GNU Binutils for Ubuntu) 
2.34) #66~20.04.1-Ubuntu SMP Thu Jun 17 11:14:10 UTC 2021 (Ubuntu 
5.8.0-59.66~20.04.1-generic 5.8.18)
[0.00] kernel: Command line: BOOT_IMAGE=/vmlinuz-5.8.0-59-generic 
root=UUID=c4248af1-a4cf-49a2-ba18-4de2c65c815c ro acpi_force_32bit_fadt_addr 
acpi_rev_override check_enable_amd_mmconf pcie_bus_tune=off pcie_aspm=off 
pci_ports=native intremap=off agp=off nohugeiomap parport=0 hashdist=0
...
[0.212298] kernel: EISA bus registered
...
[1.006643] kernel: platform eisa.0: Probing EISA bus 0
[1.006715] kernel: platform eisa.0: EISA: Cannot allocate resource for 
mainboard
[1.006779] kernel: platform eisa.0: Cannot allocate resource for EISA slot 1
[1.006855] kernel: platform eisa.0: Cannot allocate resource for EISA slot 8
[1.006917] kernel: platform eisa.0: EISA: Detected 0 cards

I concur on the feasibility of offloading EISA from Kernel core and
building a Module EISA.ko.

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

Title:
  Remove EISA support from main kernel image and make it M (modular)

Status in linux package in Ubuntu:
  Triaged

Bug description:
  (This is a sort of RfC. )

  I have a PC that still has the good old PCI ports, but I am 100% sure that 
the active use of EISA dates back yet more 10 years.
  In other words, boards that _only_ support EISA date back 25 years now, while 
those that provide *one* EISA slot date back roughly 15 years (one of the 
Elitegroup K7 series comes to mind, from about 2001/02).

  So the EISA support *should* be provided, as we should even support ancient 
hardware (Linux principle :))
  However, why the EISA support is *compiled in* is beyond me.

  For instance, it creates lots of totally unnecessary noise in dmesg:

  [0.08] EISA bus registered
  [1.598316] platform eisa.0: Probing EISA bus 0
  [1.598345] platform eisa.0: Cannot allocate resource for EISA slot 1  
(repeated 10 times, i=i+1)
  [1.598368] platform eisa.0: EISA: Detected 0 cards

  For a 1997 mainboard, this would make perfect sense.
  But it is very probable that said mainboard would require linux-image-extra 
nonetheless to support some days-of-yore chipset.

  So why not leave it as a *module*, while removing its support from
  main kernel image once and for all?

  Your turn.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1543919/+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 1911055] Re: [modeset][nvidia] suspend/resume broken in nvidia-460 : Display engine push buffer channel allocation failed

2021-06-30 Thread Shawn B
I was also having a suspend/resume with 460.56+. Rolling back to 460.39
fixed it.

Older packages can be found at https://launchpad.net/ubuntu/+source
/nvidia-graphics-drivers-460/+publishinghistory

List of packages I have installed:
libnvidia-cfg1-460:amd64
libnvidia-common-460
libnvidia-compute-460:amd64
libnvidia-compute-460:i386
libnvidia-decode-460:amd64
libnvidia-decode-460:i386
libnvidia-encode-460:amd64
libnvidia-encode-460:i386
libnvidia-extra-460:amd64
libnvidia-extra-460:i386
libnvidia-fbc1-460:amd64
libnvidia-fbc1-460:i386
libnvidia-gl-460:amd64
libnvidia-gl-460:i386
libnvidia-ifr1-460:amd64
libnvidia-ifr1-460:i386
nvidia-compute-utils-460
nvidia-dkms-460
nvidia-driver-460
nvidia-kernel-common-460
nvidia-kernel-source-460
nvidia-prime
nvidia-prime-applet
nvidia-settings
nvidia-utils-460
xserver-xorg-video-nvidia-460

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

Title:
  [modeset][nvidia] suspend/resume broken in nvidia-460 : Display engine
  push buffer channel allocation failed

Status in nvidia-graphics-drivers-460 package in Ubuntu:
  Confirmed

Bug description:
  After a recent update to nvidia-460, suspend then resume results in a
  black screen, then a hang for around 120 seconds, and then the text:

  nvidia-modeset: ERROR: GPU:0: Display engine push buffer channel allocation 
failed: 0x65 (Call timed out [NV_ERR_TIMEOUT])
  nvidia-modeset: ERROR: GPU:0: Failed to allocate display engine core DMA push 
buffer
  nvidia-modeset: ERROR: GPU:0: Display engine push buffer channel allocation 
failed: 0x65 (Call timed out [NV_ERR_TIMEOUT])
  nvidia-modeset: ERROR: GPU:0: Failed to allocate display engine core DMA push 
buffer

  dmesg shows:

  [  188.352670] ACPI: Waking up from system sleep state S3
  ...
  [  309.142164] nvidia-modeset: ERROR: GPU:0: Display engine push buffer 
channel allocation failed: 0x65 (Call timed out [NV_ERR_TIMEOUT])
  [  309.142319] nvidia-modeset: ERROR: GPU:0: Failed to allocate display 
engine core DMA push buffer
  [  313.142165] nvidia-modeset: ERROR: GPU:0: Display engine push buffer 
channel allocation failed: 0x65 (Call timed out [NV_ERR_TIMEOUT])
  [  313.142348] nvidia-modeset: ERROR: GPU:0: Failed to allocate display 
engine core DMA push buffer
  [  313.151885] acpi LNXPOWER:08: Turning OFF
  [  313.151898] acpi LNXPOWER:04: Turning OFF
  [  313.152351] acpi LNXPOWER:03: Turning OFF
  [  313.153064] acpi LNXPOWER:02: Turning OFF
  ...
  [  325.010192] nvidia-modeset: WARNING: GPU:0: Unable to read EDID for 
display device DELL 2209WA (HDMI-0)
  [  325.010577] BUG: kernel NULL pointer dereference, address: 0050
  [  325.010579] #PF: supervisor read access in kernel mode
  [  325.010580] #PF: error_code(0x) - not-present page
  [  325.010580] PGD 0 P4D 0
  [  325.010582] Oops:  [#1] SMP PTI
  [  325.010583] CPU: 9 PID: 2247 Comm: Xorg Tainted: P   O  
5.4.0-60-generic #67-Ubuntu
  [  325.010584] Hardware name: Razer Blade/DANA_MB, BIOS 01.01 08/31/2018
  [  325.010595] RIP: 0010:_nv000112kms+0xd/0x30 [nvidia_modeset]
  [  325.010596] Code: 16 00 74 06 83 7e 0c 02 77 03 31 c0 c3 c7 46 0c 01 00 00 
00 b8 01 00 00 00 c3 0f 1f 00 0f b7 46 04 0f b7 56 08 39 d0 0f 47 c2 <3b> 47 18 
77 06 83 7e 10 02 77 08 31 c0 c3 0f 1f 44 00 00 c7 46 10
  [  325.010597] RSP: 0018:b89542e5b8a8 EFLAGS: 00010246
  [  325.010598] RAX: 0280 RBX: 0038 RCX: 
03ff
  [  325.010598] RDX: 0280 RSI: b89542e5bba0 RDI: 
0038
  [  325.010599] RBP: b89542e5b9c8 R08:  R09: 
c379e440
  [  325.010600] R10:  R11:  R12: 
b89542e5b948
  [  325.010600] R13: b89542e5b948 R14: b89542e5b930 R15: 
c3a50e60
  [  325.010601] FS:  7feb4c09ea80() GS:8e46ada4() 
knlGS:
  [  325.010602] CS:  0010 DS:  ES:  CR0: 80050033
  [  325.010602] CR2: 0050 CR3: 0004772e2006 CR4: 
003606e0
  [  325.010603] Call Trace:
  [  325.010610]  ? _nv002768kms+0x96/0xd0 [nvidia_modeset]
  [  325.010616]  ? _nv002328kms+0xb5/0x110 [nvidia_modeset]
  [  325.010624]  ? _nv000742kms+0x168/0x370 [nvidia_modeset]
  [  325.010823]  ? _nv036002rm+0x62/0x70 [nvidia]
  [  325.010910]  ? os_get_current_tick+0x2c/0x50 [nvidia]
  [  325.010921]  ? _nv002771kms+0x433/0x600 [nvidia_modeset]
  [  325.010928]  ? _nv002771kms+0x3fc/0x600 [nvidia_modeset]
  [  325.010930]  ? __schedule+0x2eb/0x740
  [  325.010935]  ? _nv000742kms+0x40/0x40 [nvidia_modeset]
  [  325.010939]  ? nvkms_alloc+0x6a/0xa0 [nvidia_modeset]
  [  325.010944]  ? _nv000742kms+0x40/0x40 [nvidia_modeset]
  [  325.010948]  ? _nv000744kms+0x2a/0x40 [nvidia_modeset]
  [  325.010952]  ? nvKmsIoctl+0x96/0x1d0 [nvidia_modeset]
  [  325.010957]  ? nvkms_ioctl_common+0x42/0x80 [nvidia_modeset]
  

[Kernel-packages] [Bug 1911392] Re: Touchpad no longer detected

2021-01-24 Thread Christian B
I downgraded to an even older kernel version (linux-image-4.15.0-20-generic, 
last changelog entry in April 2018).
The problem still persists -- issue can be closed. Definitely a hardware defect.

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

Title:
  Touchpad no longer detected

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The touchpad on my Lenovo Ideapad 720S-13IKB stopped working
  yesterday. It was always working fine before that. It no longer shows
  up in my device list. See attached file.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-130-generic 4.15.0-130.134
  ProcVersionSignature: Ubuntu 4.15.0-130.134-generic 4.15.18
  Uname: Linux 4.15.0-130-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  cb 1884 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan 13 08:13:59 2021
  InstallationDate: Installed on 2018-06-16 (941 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: LENOVO 81A8
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-130-generic 
root=UUID=364c39f2-ff11-4b3f-afb9-27fc63aa44c4 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-130-generic N/A
   linux-backports-modules-4.15.0-130-generic  N/A
   linux-firmware  1.173.19
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/23/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 5SCN38WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 720S-13IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr5SCN38WW:bd02/23/2018:svnLENOVO:pn81A8:pvrLenovoideapad720S-13IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad720S-13IKB:
  dmi.product.family: ideapad 720S-13IKB
  dmi.product.name: 81A8
  dmi.product.version: Lenovo ideapad 720S-13IKB
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1911392/+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 1911392] Re: Touchpad no longer detected

2021-01-15 Thread Christian B
Problem also occurs with older kernel 4.15.0-128.
Just tested with an Ubuntu 20 live CD. Same problem.

I therefore assume it's a hardware problem that is unrelated to Ubuntu.

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

Title:
  Touchpad no longer detected

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The touchpad on my Lenovo Ideapad 720S-13IKB stopped working
  yesterday. It was always working fine before that. It no longer shows
  up in my device list. See attached file.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-130-generic 4.15.0-130.134
  ProcVersionSignature: Ubuntu 4.15.0-130.134-generic 4.15.18
  Uname: Linux 4.15.0-130-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  cb 1884 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan 13 08:13:59 2021
  InstallationDate: Installed on 2018-06-16 (941 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: LENOVO 81A8
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-130-generic 
root=UUID=364c39f2-ff11-4b3f-afb9-27fc63aa44c4 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-130-generic N/A
   linux-backports-modules-4.15.0-130-generic  N/A
   linux-firmware  1.173.19
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/23/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 5SCN38WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 720S-13IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr5SCN38WW:bd02/23/2018:svnLENOVO:pn81A8:pvrLenovoideapad720S-13IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad720S-13IKB:
  dmi.product.family: ideapad 720S-13IKB
  dmi.product.name: 81A8
  dmi.product.version: Lenovo ideapad 720S-13IKB
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1911392/+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 1911392] [NEW] Touchpad no longer detected

2021-01-12 Thread Christian B
Public bug reported:

The touchpad on my Lenovo Ideapad 720S-13IKB stopped working yesterday.
It was always working fine before that. It no longer shows up in my
device list. See attached file.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-130-generic 4.15.0-130.134
ProcVersionSignature: Ubuntu 4.15.0-130.134-generic 4.15.18
Uname: Linux 4.15.0-130-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.21
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  cb 1884 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Wed Jan 13 08:13:59 2021
InstallationDate: Installed on 2018-06-16 (941 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
MachineType: LENOVO 81A8
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-130-generic 
root=UUID=364c39f2-ff11-4b3f-afb9-27fc63aa44c4 ro quiet splash vt.handoff=1
RelatedPackageVersions:
 linux-restricted-modules-4.15.0-130-generic N/A
 linux-backports-modules-4.15.0-130-generic  N/A
 linux-firmware  1.173.19
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/23/2018
dmi.bios.vendor: LENOVO
dmi.bios.version: 5SCN38WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo ideapad 720S-13IKB
dmi.modalias: 
dmi:bvnLENOVO:bvr5SCN38WW:bd02/23/2018:svnLENOVO:pn81A8:pvrLenovoideapad720S-13IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad720S-13IKB:
dmi.product.family: ideapad 720S-13IKB
dmi.product.name: 81A8
dmi.product.version: Lenovo ideapad 720S-13IKB
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug bionic

** Attachment added: "output of cat /proc/bus/input/devices"
   https://bugs.launchpad.net/bugs/1911392/+attachment/5452533/+files/devices

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

Title:
  Touchpad no longer detected

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The touchpad on my Lenovo Ideapad 720S-13IKB stopped working
  yesterday. It was always working fine before that. It no longer shows
  up in my device list. See attached file.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-130-generic 4.15.0-130.134
  ProcVersionSignature: Ubuntu 4.15.0-130.134-generic 4.15.18
  Uname: Linux 4.15.0-130-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  cb 1884 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan 13 08:13:59 2021
  InstallationDate: Installed on 2018-06-16 (941 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: LENOVO 81A8
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-130-generic 
root=UUID=364c39f2-ff11-4b3f-afb9-27fc63aa44c4 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-130-generic N/A
   linux-backports-modules-4.15.0-130-generic  N/A
   linux-firmware  1.173.19
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/23/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 5SCN38WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 720S-13IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr5SCN38WW:bd02/23/2018:svnLENOVO:pn81A8:pvrLenovoideapad720S-13IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad720S-13IKB:
  dmi.product.family: ideapad 720S-13IKB
  dmi.product.name: 81A8
  dmi.product.version: Lenovo ideapad 720S-13IKB
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1911392/+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 1911240] [NEW] package bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu4 failed to install/upgrade: installed bcmwl-kernel-source package post-installation script subprocess retur

2021-01-12 Thread Ken B
Public bug reported:

dpkg: error processing package bcmwl-kernel-source (--configure):
 installed bcmwl-kernel-source package post-installation script subprocess 
returned error exit status 10

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu4
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.4
Architecture: amd64
CasperMD5CheckResult: skip
Date: Tue Jan 12 13:53:08 2021
ErrorMessage: installed bcmwl-kernel-source package post-installation script 
subprocess returned error exit status 10
InstallationDate: Installed on 2021-01-12 (0 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.2ubuntu0.1
SourcePackage: bcmwl
Title: package bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu4 failed to 
install/upgrade: installed bcmwl-kernel-source package post-installation script 
subprocess returned error exit status 10
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package focal third-party-packages

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

Title:
  package bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu4 failed to
  install/upgrade: installed bcmwl-kernel-source package post-
  installation script subprocess returned error exit status 10

Status in bcmwl package in Ubuntu:
  New

Bug description:
  dpkg: error processing package bcmwl-kernel-source (--configure):
   installed bcmwl-kernel-source package post-installation script subprocess 
returned error exit status 10

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu4
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Tue Jan 12 13:53:08 2021
  ErrorMessage: installed bcmwl-kernel-source package post-installation script 
subprocess returned error exit status 10
  InstallationDate: Installed on 2021-01-12 (0 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: bcmwl
  Title: package bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu4 failed to 
install/upgrade: installed bcmwl-kernel-source package post-installation script 
subprocess returned error exit status 10
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1911240/+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 1894230] Re: Device queue depth should be 31 not 32

2020-09-18 Thread Bobby B
Please close this bug.  I was wrong about the queue depth being the
source of this issue.  Currently I've tried including pci=nomsi at the
kernel command line, and I seem to be the avoiding SATA errors.

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

Title:
  Device queue depth should be 31 not 32

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Setting drive device/queue_depth to 31 from 32 resolved an issue
  whereby I had numerous zpool and ATA errors but only under high load
  (zpool scrub) or when trimming the drives.  Was able to reduce
  incidence by setting to libata.force=noncqtrim, and resolve with
  libata.force=noncq, but with an obvious performance impact.

  Upstream kernel seems to be aware of this issue, so I'm assuming this
  is a downstream or udev configuration issue, see:
  
https://ata.wiki.kernel.org/index.php/Libata_FAQ#Enabling.2C_disabling_and_checking_NCQ

  Scrub repaired all errors, but, because repairs were made, it seems
  like it's not just a communications issue, and that there is the
  potential for DATA LOSS on non-redundant and/or non-ZFS
  configurations.

  Sample syslog error:

  [   33.688898] ata1.00: exception Emask 0x50 SAct 0x1003000 SErr 0x4c0900 
action 0x6 frozen
  [   33.688908] ata1.00: irq_stat 0x0800, interface fatal error
  [   33.688913] ata1: SError: { UnrecovData HostInt CommWake 10B8B Handshk }
  [   33.688917] ata1.00: failed command: WRITE FPDMA QUEUED
  [   33.688923] ata1.00: cmd 61/00:60:df:28:3d/01:00:2a:00:00/40 tag 12 ncq 
dma 131072 out
  [   33.688929] ata1.00: status: { DRDY }
  [   33.688931] ata1.00: failed command: WRITE FPDMA QUEUED
  [   33.688937] ata1.00: cmd 61/08:68:18:a9:d2/00:00:04:00:00/40 tag 13 ncq 
dma 4096 out
  [   33.688942] ata1.00: status: { DRDY }
  [   33.688945] ata1.00: failed command: WRITE FPDMA QUEUED
  [   33.688951] ata1.00: cmd 61/00:c0:df:27:3d/01:00:2a:00:00/40 tag 24 ncq 
dma 131072 out
  [   33.688956] ata1.00: status: { DRDY }
  [   33.688963] ata1: hard resetting link

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894230/+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 1894230] Re: Device queue depth should be 31 not 32

2020-09-04 Thread Bobby B
Uncomfortable dumping logs I can't view.

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

Title:
  Device queue depth should be 31 not 32

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Setting drive device/queue_depth to 31 from 32 resolved an issue
  whereby I had numerous zpool and ATA errors but only under high load
  (zpool scrub) or when trimming the drives.  Was able to reduce
  incidence by setting to libata.force=noncqtrim, and resolve with
  libata.force=noncq, but with an obvious performance impact.

  Upstream kernel seems to be aware of this issue, so I'm assuming this
  is a downstream or udev configuration issue, see:
  
https://ata.wiki.kernel.org/index.php/Libata_FAQ#Enabling.2C_disabling_and_checking_NCQ

  Scrub repaired all errors, but, because repairs were made, it seems
  like it's not just a communications issue, and that there is the
  potential for DATA LOSS on non-redundant and/or non-ZFS
  configurations.

  Sample syslog error:

  [   33.688898] ata1.00: exception Emask 0x50 SAct 0x1003000 SErr 0x4c0900 
action 0x6 frozen
  [   33.688908] ata1.00: irq_stat 0x0800, interface fatal error
  [   33.688913] ata1: SError: { UnrecovData HostInt CommWake 10B8B Handshk }
  [   33.688917] ata1.00: failed command: WRITE FPDMA QUEUED
  [   33.688923] ata1.00: cmd 61/00:60:df:28:3d/01:00:2a:00:00/40 tag 12 ncq 
dma 131072 out
  [   33.688929] ata1.00: status: { DRDY }
  [   33.688931] ata1.00: failed command: WRITE FPDMA QUEUED
  [   33.688937] ata1.00: cmd 61/08:68:18:a9:d2/00:00:04:00:00/40 tag 13 ncq 
dma 4096 out
  [   33.688942] ata1.00: status: { DRDY }
  [   33.688945] ata1.00: failed command: WRITE FPDMA QUEUED
  [   33.688951] ata1.00: cmd 61/00:c0:df:27:3d/01:00:2a:00:00/40 tag 24 ncq 
dma 131072 out
  [   33.688956] ata1.00: status: { DRDY }
  [   33.688963] ata1: hard resetting link

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


  1   2   3   4   5   >