All autopkgtests for the newly accepted linux-meta-azure (5.15.0.1038.34) for
jammy have finished running.
The following regressions have been reported in tests triggered by the package:
digimend-dkms/10-4 (amd64, arm64)
systemd/249.11-0ubuntu3.9 (amd64)
Please visit the excuses page listed
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
[Expired for linux-firmware (Ubuntu) because there has been no activity
for 60 days.]
** Changed in: linux-firmware (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Tags removed: verification-needed-focal verification-needed-jammy
verification-needed-kinetic
** Tags added: verification-done-focal verification-done-jammy
verification-done-kinetic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Yes... problem still exists with 5.19.0-41. Known fix is in 5.19.0-42,
which has been landed in non-LTS. Sharing sentiment about landing it in
22.04.x as that's the *current long term support version*. Crucial when.
--
You received this bug notification because you are a member of Kernel
It still doesn't work on 5.19.0-40-generic. If i revert back to
5.19.0-32 the sound works but the nvidia graphics driver stops working.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-5.19 in Ubuntu.
All autopkgtests for the newly accepted linux-meta-aws (5.15.0.1036.35) for
jammy have finished running.
The following regressions have been reported in tests triggered by the package:
dm-writeboost/2.2.13-1ubuntu2 (amd64, arm64)
dpdk-kmods/0~20220111+git-1ubuntu1~22.04.1 (amd64, arm64)
** Tags removed: verification-needed-jammy
** Tags added: verification-done-jammy
--
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/2008971
Title:
Do not sort the task scan result from
** Description changed:
Computers with Intel Atom CPU (maybe other Intel CPUs as well) will not
boot with Kernel 6.2.0-20 OR any other Kernel in 6.2 series or Kernel
6.3.0.
- This includes the latest stable Kernel 6.2.12 in Ubuntu repositories.
- This also includes the latest Ubuntu
All autopkgtests for the newly accepted linux-restricted-modules-azure
(5.15.0-1038.45) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:
nvidia-graphics-drivers-390/390.157-0ubuntu0.22.04.1 (i386)
Please visit the excuses page
All autopkgtests for the newly accepted linux-restricted-modules-azure
(5.15.0-1038.45) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:
nvidia-graphics-drivers-390/390.157-0ubuntu0.22.04.1 (i386)
Please visit the excuses page
All autopkgtests for the newly accepted linux-restricted-modules-aws
(5.15.0-1036.40) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:
nvidia-graphics-drivers-390/390.157-0ubuntu0.22.04.1 (i386)
Please visit the excuses page
All autopkgtests for the newly accepted linux-restricted-modules-aws
(5.15.0-1036.40) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:
nvidia-graphics-drivers-390/390.157-0ubuntu0.22.04.1 (i386)
Please visit the excuses page
All autopkgtests for the newly accepted linux-restricted-modules-azure
(5.19.0-1026.29) for kinetic have finished running.
The following regressions have been reported in tests triggered by the package:
nvidia-graphics-drivers-390/390.157-0ubuntu0.22.10.1 (i386)
Please visit the excuses page
All autopkgtests for the newly accepted linux-restricted-modules-azure
(5.19.0-1026.29) for kinetic have finished running.
The following regressions have been reported in tests triggered by the package:
nvidia-graphics-drivers-390/390.157-0ubuntu0.22.10.1 (i386)
Please visit the excuses page
I am attaching a new version of the script that doesn't mount /proc
unnecessarily. I just realized I left that in there.
** Attachment added: "overlayfsscript_example"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016398/+attachment/5668666/+files/overlayfsscript_example
--
You
All autopkgtests for the newly accepted linux-restricted-modules-aws
(5.19.0-1025.26) for kinetic have finished running.
The following regressions have been reported in tests triggered by the package:
nvidia-graphics-drivers-390/390.157-0ubuntu0.22.10.1 (i386)
Please visit the excuses page
All autopkgtests for the newly accepted linux-restricted-modules-aws
(5.19.0-1025.26) for kinetic have finished running.
The following regressions have been reported in tests triggered by the package:
nvidia-graphics-drivers-390/390.157-0ubuntu0.22.10.1 (i386)
Please visit the excuses page
All autopkgtests for the newly accepted linux-meta-aws (5.19.0.1025.22) for
kinetic have finished running.
The following regressions have been reported in tests triggered by the package:
lttng-modules/2.13.8-1~ubuntu22.10.0 (amd64, arm64)
Please visit the excuses page listed below and
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly
All autopkgtests for the newly accepted linux-restricted-modules-aws
(5.4.0-1102.110) for focal have finished running.
The following regressions have been reported in tests triggered by the package:
nvidia-graphics-drivers-390/390.157-0ubuntu0.20.04.1 (i386)
Please visit the excuses page
All autopkgtests for the newly accepted linux-restricted-modules-aws
(5.4.0-1102.110) for focal have finished running.
The following regressions have been reported in tests triggered by the package:
nvidia-graphics-drivers-390/390.157-0ubuntu0.20.04.1 (i386)
Please visit the excuses page
All autopkgtests for the newly accepted linux-restricted-modules-azure
(5.4.0-1108.114) for focal have finished running.
The following regressions have been reported in tests triggered by the package:
nvidia-graphics-drivers-390/390.157-0ubuntu0.20.04.1 (i386)
Please visit the excuses page
All autopkgtests for the newly accepted linux-restricted-modules-azure
(5.4.0-1108.114) for focal have finished running.
The following regressions have been reported in tests triggered by the package:
nvidia-graphics-drivers-390/390.157-0ubuntu0.20.04.1 (i386)
Please visit the excuses page
This bug is awaiting verification that the linux-aws/5.15.0-1036.40
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy' to 'verification-done-jammy'. If the
problem still exists,
This bug is awaiting verification that the linux-azure/5.15.0-1038.45
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy' to 'verification-done-jammy'. If the
problem still exists,
This bug is awaiting verification that the linux-azure/5.15.0-1038.45
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy' to 'verification-done-jammy'. If the
problem still exists,
This bug is awaiting verification that the linux-aws/5.15.0-1036.40
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy' to 'verification-done-jammy'. If the
problem still exists,
This bug is awaiting verification that the linux-aws/5.15.0-1036.40
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy' to 'verification-done-jammy'. If the
problem still exists,
This bug is awaiting verification that the linux-azure/5.15.0-1038.45
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy' to 'verification-done-jammy'. If the
problem still exists,
This bug is awaiting verification that the linux-azure/5.15.0-1038.45
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy' to 'verification-done-jammy'. If the
problem still exists,
This bug is awaiting verification that the linux-aws/5.15.0-1036.40
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy' to 'verification-done-jammy'. If the
problem still exists,
This bug is awaiting verification that the linux-azure/5.15.0-1038.45
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy' to 'verification-done-jammy'. If the
problem still exists,
This bug is awaiting verification that the linux-azure/5.15.0-1038.45
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy' to 'verification-done-jammy'. If the
problem still exists,
This bug is awaiting verification that the linux-aws/5.15.0-1036.40
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy' to 'verification-done-jammy'. If the
problem still exists,
This bug is awaiting verification that the linux-azure/5.15.0-1038.45
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy' to 'verification-done-jammy'. If the
problem still exists,
This bug is awaiting verification that the linux-aws/5.15.0-1036.40
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy' to 'verification-done-jammy'. If the
problem still exists,
This bug is awaiting verification that the linux-aws/5.15.0-1036.40
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy' to 'verification-done-jammy'. If the
problem still exists,
This bug is awaiting verification that the linux-azure/5.15.0-1038.45
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy' to 'verification-done-jammy'. If the
problem still exists,
This bug is awaiting verification that the linux-aws/5.15.0-1036.40
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy' to 'verification-done-jammy'. If the
problem still exists,
This bug is awaiting verification that the linux-azure/5.15.0-1038.45
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy' to 'verification-done-jammy'. If the
problem still exists,
This bug is awaiting verification that the linux-azure/5.15.0-1038.45
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy' to 'verification-done-jammy'. If the
problem still exists,
** Description changed:
Installing with additional drivers or adding nvidia-driver-390 renders
the system unusable.
On restart there are few lines of the usual kernal information then a
brief orange flash follwed by black. System is unusable.
- Is the GTX 675MX supported? If not,
Maybe some more info?
dpkg: error processing package linux-headers-6.2.0-20-generic (--configure):
installed linux-headers-6.2.0-20-generic package post-installation script
subprocess returned error exit status 1
dpkg: dependency problems prevent configuration of linux-headers-generic:
What fixed it for me - I had set apparmor=0 on my kernel boot args.
-Edit /etc/default/grub
-remove apparmor=0
-update-grub
-> Possible issue with apparmor changes introduced in 6.2.0-19
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
On this very topic, I try update my blogs almost like I’m speaking to
somebody or talking to that reader directly as I consider it helps
engage people a lot more than writing content formally especially when
my own blog is based around the goings ons, daily thoughts and research
about this
This bug is awaiting verification that the linux-azure/5.19.0-1026.29
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-kinetic' to 'verification-done-kinetic'. If the
problem still
This bug is awaiting verification that the linux-azure/5.19.0-1026.29
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-kinetic' to 'verification-done-kinetic'. If the
problem still
This bug is awaiting verification that the linux-aws/5.19.0-1025.26
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-kinetic' to 'verification-done-kinetic'. If the
problem still
This bug is awaiting verification that the linux-aws/5.19.0-1025.26
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-kinetic' to 'verification-done-kinetic'. If the
problem still
This bug is awaiting verification that the linux-azure/5.19.0-1026.29
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-kinetic' to 'verification-done-kinetic'. If the
problem still
This bug is awaiting verification that the linux-azure/5.19.0-1026.29
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-kinetic' to 'verification-done-kinetic'. If the
problem still
This bug is awaiting verification that the linux-aws/5.19.0-1025.26
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-kinetic' to 'verification-done-kinetic'. If the
problem still
This bug is awaiting verification that the linux-azure/5.19.0-1026.29
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-kinetic' to 'verification-done-kinetic'. If the
problem still
This bug is awaiting verification that the linux-aws/5.19.0-1025.26
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-kinetic' to 'verification-done-kinetic'. If the
problem still
This bug is awaiting verification that the linux-azure/5.19.0-1026.29
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-kinetic' to 'verification-done-kinetic'. If the
problem still
This bug is awaiting verification that the linux-azure/5.19.0-1026.29
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-kinetic' to 'verification-done-kinetic'. If the
problem still
This bug is awaiting verification that the linux-aws/5.19.0-1025.26
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-kinetic' to 'verification-done-kinetic'. If the
problem still
This bug is awaiting verification that the linux-aws/5.19.0-1025.26
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-kinetic' to 'verification-done-kinetic'. If the
problem still
This bug is awaiting verification that the linux-azure/5.19.0-1026.29
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-kinetic' to 'verification-done-kinetic'. If the
problem still
This bug is awaiting verification that the linux-azure/5.19.0-1026.29
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-kinetic' to 'verification-done-kinetic'. If the
problem still
This bug is awaiting verification that the linux-aws/5.19.0-1025.26
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-kinetic' to 'verification-done-kinetic'. If the
problem still
This bug is awaiting verification that the linux-aws/5.19.0-1025.26
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-kinetic' to 'verification-done-kinetic'. If the
problem still
This bug is awaiting verification that the linux-azure/5.19.0-1026.29
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-kinetic' to 'verification-done-kinetic'. If the
problem still
This bug is awaiting verification that the linux-aws/5.19.0-1025.26
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-kinetic' to 'verification-done-kinetic'. If the
problem still
This bug is awaiting verification that the linux-azure/5.19.0-1026.29
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-kinetic' to 'verification-done-kinetic'. If the
problem still
This bug is awaiting verification that the linux-azure/5.19.0-1026.29
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-kinetic' to 'verification-done-kinetic'. If the
problem still
This bug is awaiting verification that the linux-azure/5.19.0-1026.29
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-kinetic' to 'verification-done-kinetic'. If the
problem still
This bug is awaiting verification that the linux-azure/5.19.0-1026.29
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-kinetic' to 'verification-done-kinetic'. If the
problem still
Hello, I have exactly the same problem, with a Huawei MateBook X Pro 2022. In
my case the solutions:
#2 The ctrl+alt+F2 trick didn't work with me. My keyboard seems to be not
working after suspend.
#4 doesn't work for me because I don't have the option "Sleep State" in my BIOS
#6 the command
There was an update today (Linux Mint) 5.15.0-71-generic, is still having the
"shift exponent 64 is too large for 64-bit type 'long long unsigned int'
", followed by a crash.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
** Changed in: linux (Ubuntu Focal)
Assignee: (unassigned) => Luke Nowakowski-Krijger (lukenow)
** Changed in: linux (Ubuntu Focal)
Status: New => In Progress
** Summary changed:
- Focal update: upstream stable
apport information
** Attachment added: "acpidump.txt"
https://bugs.launchpad.net/bugs/2017599/+attachment/5668661/+files/acpidump.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/2017599/+attachment/5668660/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/2017599/+attachment/5668659/+files/UdevDb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/2017599/+attachment/5668657/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/2017599/+attachment/5668658/+files/RfKill.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/2017599/+attachment/5668654/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/2017599/+attachment/5668656/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/2017599/+attachment/5668655/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/2017599/+attachment/5668653/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/2017599/+attachment/5668652/+files/Lsusb-v.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/2017599/+attachment/5668650/+files/Lsusb.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/2017599
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/2017599/+attachment/5668649/+files/Lspci-vt.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/2017599/+attachment/5668651/+files/Lsusb-t.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/2017599/+attachment/5668646/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/2017599/+attachment/5668648/+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/2017599
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/2017599/+attachment/5668647/+files/IwConfig.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Bug apparent only when ethernet cable attached. Changed status from
invalid to confirmed.
** Changed in: linux (Ubuntu)
Status: Invalid => Confirmed
** Tags added: apport-collected
** Description changed:
Since installation via upgrade of Kubuntu from 22.10 to 23.04, laptop
touchpad
apport information
** Attachment added: "AlsaInfo.txt"
https://bugs.launchpad.net/bugs/2017599/+attachment/5668645/+files/AlsaInfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Public bug reported:
After upgrading from 22.10 to 23.04, I'm getting the following message:
ERROR couldn't connect to zsys daemon: connection error: desc = "transport:
Error while dialing dial unix /run/zsysd.sock: connect: connection refused"
Setting up initramfs-tools (0.142ubuntu2) ...
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either
Problem still exists for me after updating to
Linux dell-xps-8700 5.19.0-41-generic #42~22.04.1-Ubuntu SMP
PREEMPT_DYNAMIC Tue Apr 18 17:40:00 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
(Ubuntu 22.04.2 LTS)
--
You received this bug notification because you are a member of Kernel
Packages, which is
Resolved itself, no action taken, can't explain. Is it appropriate to
mark this bug as "invalid"? Done so 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/2017599
Title:
Touchpad
Non-bug. Resolved after a few reboots. No action taken.
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
--
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/2017599
Title:
This bug has been reported on the Ubuntu ISO testing tracker.
A list of all reports related to this bug can be found here:
https://iso.qa.ubuntu.com/qatracker/reports/bugs/2017687
** Tags added: iso-testing
--
You received this bug notification because you are a member of Kernel
Packages,
This change was made by a bot.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2017685
Title:
package linux-generic
Public bug reported:
Installing with additional drivers or adding nvidia-driver-390 renders
the system unusable.
On restart there are few lines of the usual kernal information then a
brief orange flash follwed by black. System is unusable.
Is the GTX 675MX supported? If not, this option
Public bug reported:
sem mais
ProblemType: Package
DistroRelease: Ubuntu 23.04
Package: linux-headers-generic 6.2.0.20.20
ProcVersionSignature: Ubuntu 5.19.0-38.39-generic 5.19.17
Uname: Linux 5.19.0-38-generic x86_64
ApportVersion: 2.26.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USER
1 - 100 of 140 matches
Mail list logo
