Good to hear that :D
enjoy it!

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

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

Title:
  If i want my P.C. OK, i must to start with the 5.11.0-40-generic
  Kernel Release . Not another.

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  If i want my P.C. OK, i must to start with the 5.11.0-40-generic
  Kernel Release . Not another !!! (lol)

  When i try to work whith the 5.11.0-43-generic  Kernel Release (or
  41-generic) : My computeur can't make a reboot yet normaly.   My
  question is : is using the 40-generic Kernel Release (and not sup.
  version) present security risk for me* ? (*my sytems's stability and
  security)

  I use an ASUS VivoBook S14

  Many thanks for your answer. With best regards.
  LVH

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.38
  ProcVersionSignature: Ubuntu 5.11.0-40.44~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.23
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May 10 09:22:10 2022
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=<set>
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.23
  Architecture: amd64
  AudioDevicesInUse:
   USER        PID ACCESS COMMAND
   /dev/snd/controlC0:  lio        2675 F.... pulseaudio
   /dev/snd/controlC1:  lio        2675 F.... pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X411QA_A411QA
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=<set>
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-40-generic 
root=UUID=c0faec6a-f9e5-4522-a58a-fcd4c959afd4 ro quiet splash amdgpu_osi=Linux 
amdgpu_backlight=vendor vt.handoff=7
  ProcVersionSignature: Ubuntu 5.11.0-40.44~20.04.2-generic 5.11.22
  RelatedPackageVersions:
   linux-restricted-modules-5.11.0-40-generic N/A
   linux-backports-modules-5.11.0-40-generic  N/A
   linux-firmware                             1.187.30
  Tags:  focal
  Uname: Linux 5.11.0-40-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd nordvpn plugdev sambashare sudo
  _MarkForUpload: True
  acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] 
failed with exit code 126: Error executing command as another user: Request 
dismissed
  dmi.bios.date: 07/03/2019
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X411QA.306
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X411QA
  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.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX411QA.306:bd07/03/2019:br5.12:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX411QA_A411QA:pvr1.0:sku:rvnASUSTeKCOMPUTERINC.:rnX411QA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: VivoBook
  dmi.product.name: VivoBook_ASUSLaptop X411QA_A411QA
  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/1972791/+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

Reply via email to