This should be Fix Released for the development release, right?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to intel-gpu-tools in Ubuntu.
https://bugs.launchpad.net/bugs/2061324
Title:
Error when re-building package from source
Hello Hector, or anyone else affected,
Accepted intel-gpu-tools into jammy-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/intel-gpu-
tools/1.26-2ubuntu0.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new
Hello Leonardo, or anyone else affected,
Accepted intel-gpu-tools into jammy-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/intel-gpu-
tools/1.26-2ubuntu0.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new
Hello Leonardo, or anyone else affected,
Accepted intel-gpu-tools into mantic-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/intel-gpu-
tools/1.27.1-1ubuntu0.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new
Looking at the firmware-sof SRU, it looks like both this package and the
kernel need updating to complete the hardware enablement. So have these
been tested from -proposed together? It looks like verification was done
separately for the kernel and for the userspace package, and that makes
no sense
The removal of pptpd seems like something that should be release noted
to me, to give enquiring users somewhere to refer to.
** Also affects: ubuntu-release-notes
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which
Thank you for the clarification! I'll remove the regression-update tag
then, since this is the intended behaviour of the security update, so it
shouldn't count towards regression statistics.
** Tags removed: regression-update
--
You received this bug notification because you are a member of
Looks like this is a reported regression in the security pocket.
** Information type changed from Public to Public Security
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/2045931
Title:
Reopening because a PIN of is not reported to work (and even if it
did, that would still be a regression in a stable release).
** Changed in: bluez (Ubuntu)
Status: Incomplete => Confirmed
** Changed in: bluez (Ubuntu)
Importance: Undecided => Critical
--
You received this bug
Hello You-Sheng, or anyone else affected,
Accepted linux-firmware into mantic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/20230919.git3672ccab-0ubuntu2.2 in a few hours, and then in the
-proposed repository.
Please help us by
The verification-done* tags are used by the SRU process only, to track
verification of a package in the official Ubuntu proposed pocket once
completed according to a Test Plan agreed by the SRU team. Please do not
use this tag unless this process has been followed. Since
Oh, wait. You are just fixing the race condition?
Please the SRU documentation then. Right now I read "We should drop it
in favour of using simpledrm with fbdev emulation layer" which is very
misleading as to what you're actually proposing to do.
--
You received this bug notification because
> it will expose the race condition to GDM
What race condition, please? If this is the justification for the
proposed SRU, then I'd expect to see that explained, but I don't see any
explanation.
--
You received this bug notification because you are a member of Kernel
Packages, which is
Oh, this?
> When this stack is enabled, it changes boot timing such that some
drivers may take a longer time to boot and GDM may hang in a black
screen.
In that case, why can you not revert the kernel config change in the HWE
backport to Jammy?
--
You received this bug notification because you
> This is an improvement to the current situation of aborting release
upgrade half way through.
Is it? If the user ends up with a broken DKMS package on release
upgrade, then at least they'll know about it. But if we silently ignore
the failure, the release upgrade will finish pretending that it
@afredfactice it sounds like your issue is not related to this bug. If
you think it is related, please could you explain why? Otherwise, please
see https://ubuntu.com/community/support for community support options.
--
You received this bug notification because you are a member of Kernel
The verification of the Stable Release Update for kexec-tools has
completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you
I noted that Lunar wasn't updated when I accepted this, but didn't want
to block progress Jammy while I enquired. However, another SRU team
member has confirmed that it is a requirement for hardware enablements
for the latest stable release of Ubuntu to be enabled as well -
otherwise users will be
Hello You-Sheng, or anyone else affected,
Accepted linux-firmware into jammy-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/20220329.git681281e4-0ubuntu3.16 in a few hours, and then in
the -proposed repository.
Please help us by
Hello Chris, or anyone else affected,
Accepted linux-firmware into jammy-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/20220329.git681281e4-0ubuntu3.16 in a few hours, and then in
the -proposed repository.
Please help us by testing
Hello Chris, or anyone else affected,
Accepted linux-firmware into lunar-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/20230323.gitbcdcfbcf-0ubuntu1.4 in a few hours, and then in the
-proposed repository.
Please help us by testing
Hello You-Sheng, or anyone else affected,
Accepted linux-firmware into jammy-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/20220329.git681281e4-0ubuntu3.16 in a few hours, and then in
the -proposed repository.
Please help us by
Hello You-Sheng, or anyone else affected,
Accepted linux-firmware into lunar-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/20230323.gitbcdcfbcf-0ubuntu1.4 in a few hours, and then in the
-proposed repository.
Please help us by
Hello Mario, or anyone else affected,
Accepted linux-firmware into jammy-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/20220329.git681281e4-0ubuntu3.16 in a few hours, and then in
the -proposed repository.
Please help us by testing
Hello Mario, or anyone else affected,
Accepted linux-firmware into lunar-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/20230323.gitbcdcfbcf-0ubuntu1.4 in a few hours, and then in the
-proposed repository.
Please help us by testing
Hello Timo, or anyone else affected,
Accepted linux-firmware into jammy-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/20220329.git681281e4-0ubuntu3.16 in a few hours, and then in
the -proposed repository.
Please help us by testing
Hello You-Sheng, or anyone else affected,
Accepted linux-firmware into jammy-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/20220329.git681281e4-0ubuntu3.16 in a few hours, and then in
the -proposed repository.
Please help us by
Hello You-Sheng, or anyone else affected,
Accepted linux-firmware into lunar-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/20230323.gitbcdcfbcf-0ubuntu1.4 in a few hours, and then in the
-proposed repository.
Please help us by
Hello Ioanna, or anyone else affected,
Accepted kexec-tools into focal-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/kexec-
tools/1:2.0.18-1ubuntu1.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package.
Hello Chris, or anyone else affected,
Accepted firmware-sof into jammy-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/firmware-
sof/2.0-1ubuntu4.2 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Roxana, or anyone else affected,
Accepted dkms into jammy-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/dkms/2.8.7-2ubuntu2.2
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
An upload of thermald to focal-proposed has been rejected from the
upload queue for the following reason: "Question in
https://bugs.launchpad.net/oem-priority/+bug/2009676/comments/14
outstanding for over a month".
--
You received this bug notification because you are a member of Kernel
Which package builds of linux-firmware did you test please? All three?
Just one?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1968604
Title:
rtl8761b usb bluetooth doesn't
Sorry, I'm just not clear on what has been tested.
Please could you detail precisely what version of what package has been
tested against what version of what kernel?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.1 in
Also is there any testing being done to ensure that other use cases of
alsa-ucm-conf haven't regressed?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.1 in Ubuntu.
https://bugs.launchpad.net/bugs/2015972
Title:
Dell:
I see this is verified against the proposed kernel for Jammy. But Lunar
and Kinetic look like they have been tested only against locally patched
kernels, rather than the Ubuntu archive. I would expect SRU
verifications for hardware enablements to be tested exclusively against
the Ubuntu archive
(and please re-upload when ready - the SRU team won't notice to respond
otherwise)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1964992
Title:
ZFS ignores ARC sizes below
As there's been no response, I'm cleaning this up from the queue. This
can still be fixed in Focal, but see the comments above on what needs to
be resolved first.
** Changed in: zfs-linux (Ubuntu Focal)
Status: Incomplete => Triaged
--
You received this bug notification because you are a
Thank you for the re-upload.
I think this remains blocked on answers to my questions in
https://lists.ubuntu.com/archives/ubuntu-
release/2022-October/005495.html ?
** Changed in: thermald (Ubuntu Jammy)
Status: In Progress => Incomplete
--
You received this bug notification because you
This SRU remains blocked on https://lists.ubuntu.com/archives/ubuntu-
release/2022-October/005495.html.
For a straight backport to Jammy, if that is the conclusion, then the
upload also needs an SRU meta-bug really to document the justification
and regression risk mitigation for the backport.
**
The correct logic shouldn't be hard to write, unless I'm missing
something? So can we just do it right, and as soon as is necessary? If
it's obviously correct, I don't think we need to wait for upstream
acceptance, but equally it shouldn't take them long to review it either.
Because the parameters
The verification of the Stable Release Update for dmidecode has
completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you
> For focal we can only test the current kernel (hwe-5.15 has not yet
picked up the lastest jammy changes because of the upcoming point
release)
It seems odd to release an SRU without the ability to test what it is
fixing. If it turns out not to fix it, we'd have to be doing an SRU
again for no
** Bug watch added: Debian Bug tracker #996104
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996104
** Also affects: dkms (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996104
Importance: Unknown
Status: Unknown
--
You received this bug notification because
ged in: dkms (Ubuntu)
Status: Confirmed => In Progress
** Changed in: dkms (Ubuntu)
Assignee: (unassigned) => Robie Basak (racb)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
https://bugs.launchpad.net/bugs/1963835
** Tags added: regression-update
--
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/1966432
Title:
audio crackling on usb sound card
Status in linux package in Ubuntu:
Confirmed
Bug
Hello Hui, or anyone else affected,
Accepted alsa-ucm-conf into focal-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/alsa-ucm-
conf/1.2.2-1ubuntu0.12 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package.
It looks like verification is still needed against linux-firmware
1.187.27 in focal-proposed?
** Tags removed: verification-done-focal
** Tags added: verification-needede-focal
** Tags removed: verification-needede-focal
** Tags added: verification-needed-focal
--
You received this bug
Can you confirm the package version that was used with proposed enabled
please? We've had serious regressions in the past because the version
released accidentally did not match the version tested, so I want to
make sure that the version I release is the version you tested.
Note that this is
Hi Jeremy,
It's not your fault. This is something your sponsor is supposed to have
checked.
@Alberto
Please could you properly review this, make sure it meets SRU policy,
try to anticipate and answer any questions the SRU team might have in
advance, and then work with Jeremy to resubmit to the
An upload of nvidia-settings to impish-proposed has been rejected from
the upload queue for the following reason: "See
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-
common/+bug/1957094/comments/12".
--
You received this bug notification because you are a member of Kernel
Packages,
An upload of nvidia-settings to focal-proposed has been rejected from
the upload queue for the following reason: "See
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-
common/+bug/1957094/comments/12".
--
You received this bug notification because you are a member of Kernel
Packages,
An upload of ubuntu-drivers-common to impish-proposed has been rejected
from the upload queue for the following reason: "See
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-
common/+bug/1957094/comments/12".
--
You received this bug notification because you are a member of Kernel
An upload of ubuntu-drivers-common to focal-proposed has been rejected
from the upload queue for the following reason: "See
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-
common/+bug/1957094/comments/12".
--
You received this bug notification because you are a member of Kernel
Missing SRU information: no regression analysis (ie. "Where things go
wrong" formerly "Regression Potential").
Please follow https://wiki.ubuntu.com/StableReleaseUpdates#Procedure
properly.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
The verification of the Stable Release Update for alsa-lib has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter
SRU +1 for the current upload in Focal unapproved also, but this is
currently blocked on the 20.04.3 freeze.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to thermald in Ubuntu.
https://bugs.launchpad.net/bugs/1940629
Title:
Support
Unsubscribing sponsors.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to thermald in Ubuntu.
https://bugs.launchpad.net/bugs/1940629
Title:
Support Jasper Lake
Status in OEM Priority Project:
New
Status in thermald package in Ubuntu:
Hello Andy, or anyone else affected,
Accepted thermald into hirsute-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/thermald/2.4.3-1ubuntu2 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Jatin, or anyone else affected,
Accepted gnome-settings-daemon into hirsute-proposed. The package will
build now and be available at
https://launchpad.net/ubuntu/+source/gnome-settings-
daemon/3.38.1-3ubuntu3.1 in a few hours, and then in the -proposed
repository.
Please help us by testing
Hello Jatin, or anyone else affected,
Accepted gnome-settings-daemon into focal-proposed. The package will
build now and be available at
https://launchpad.net/ubuntu/+source/gnome-settings-
daemon/3.36.1-0ubuntu1.1 in a few hours, and then in the -proposed
repository.
Please help us by testing
Hello Andy, or anyone else affected,
Accepted bluez into hirsute-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/bluez/5.56-0ubuntu4.2
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Andy, or anyone else affected,
Accepted bluez into focal-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/bluez/5.53-0ubuntu3.3
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
> Declaring "Fix Committed" when a fix exists in an upstream tributary
before anything has reached proposed is a procedure requested by seb128
and we now follow on the desktop team.
I'm not sure what you mean by "upstream tributary", but if the fix
exists in the main Ubuntu packaging branch used
See bug 1926062 for previous SRU review.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1933221
Title:
Blutooth on/off does not work properly from gnome-control-center
Status in OEM
The fix for this seems missing in Impish. What does "Fix Committed" mean
here? What are your plans to fix this in Impish?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1926062
Title:
Also, the current upload references bug 1933221 which is a dupe. I'm not
sure how SRU tooling will handle this. Unless you can confirm that it
will work, please could you reference the master bug in your upload
instead?
--
You received this bug notification because you are a member of Kernel
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
I'll leave any security assessment and security-based prioritisation for
the security team.
>From a non-security perspective, I think this is of low priority since
it only affects an unusual end-user
Since this bug is a packaging issue being fixed in this SRU, it needs
SRU information documented please, and should be verified as part of the
SRU being landed.
Please also triage other similar-looking package conflicts such as bug
1691729 and bug 1927240. I assume these are covered already so am
Hello fossfreedom, or anyone else affected,
Accepted linux-firmware-raspi2 into groovy-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/linux-firmware-raspi2/4-0ubuntu0~20.10.1 in a few hours, and then in
the -proposed repository.
Please help us by
Hello fossfreedom, or anyone else affected,
Accepted linux-firmware-raspi2 into focal-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/linux-firmware-raspi2/4-0ubuntu0~20.04.1 in a few hours, and then in
the -proposed repository.
Please help us by
Hello Kleber, or anyone else affected,
Accepted openafs into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/openafs/1.6.15-1ubuntu1.1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Kai-Chuan, or anyone else affected,
Accepted alsa-ucm-conf into groovy-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/alsa-ucm-
conf/1.2.2-1ubuntu5.2 in a few hours, and then in the -proposed
repository.
Please help us by testing this new
Hello Kai-Chuan, or anyone else affected,
Accepted alsa-ucm-conf into focal-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/alsa-ucm-
conf/1.2.2-1ubuntu0.6 in a few hours, and then in the -proposed
repository.
Please help us by testing this new
The Hirsute fix is in hirsute-proposed.
** Changed in: dkms (Ubuntu Hirsute)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
https://bugs.launchpad.net/bugs/1915051
Title:
Hello Marcelo, or anyone else affected,
Accepted dkms into groovy-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/dkms/2.8.3-4ubuntu0.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Marcelo, or anyone else affected,
Accepted dkms into focal-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/dkms/2.8.1-5ubuntu2 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Rafael, or anyone else affected,
Accepted iproute2 into bionic-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/iproute2/4.15.0-2ubuntu1.3 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Merge proposal linked:
https://code.launchpad.net/~rafaeldtinoco/ubuntu/+source/iproute2/+git/iproute2/+merge/396921
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to iproute2 in Ubuntu.
Matching subscriptions: iproute2
Hello Andreas, or anyone else affected,
Accepted virt-manager into focal-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/virt-
manager/1:2.2.1-3ubuntu2.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new
Hello Markus, or anyone else affected,
Accepted qemu into focal-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/qemu/1:4.2-3ubuntu6.7
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
As you explained I acknowledge that we are changing behaviour in Focal
here, but I agree with you that this is the least worst option.
** Description changed:
[Impact]
- * The defaults of virt-manager for disk allocation always worked fine
-when qcow2 had nothing but sparse support. So
** Tags added: focal regression-release
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1847105
Title:
very slow disk creation, snapshotting
Status in virt-manager:
Fix Released
Hello You-Sheng, or anyone else affected,
Accepted apport into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/apport/2.20.9-0ubuntu7.17 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello James, or anyone else affected,
Accepted zfs-linux into focal-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/zfs-
linux/0.8.3-1ubuntu12.3 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package. See
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Am I right in understanding that this is a host kernel oops? My
understanding of PCIe passthrough is that if you're passing through your
sound card to a VM then the host kernel's sound driver should never
crash,
This is blocked on someone writing a test case as requested by Łukasz in
comment 10.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to thermald in Ubuntu.
https://bugs.launchpad.net/bugs/1874933
Title:
Performance workaround for Dell
Here's the change that was made: https://git.launchpad.net/~ubuntu-
kernel/ubuntu/+source/linux/+git/zesty/commit/?id=a87ae50beda8c46c543b39e19070549cf355eb65
It's just the default of the consoleblank= kernel parameter. You can
override it by specifying that parameter to the kernel at boot time
> I understand that the original reporter said that he got it working
with setterm, but as by convention these bug reports often require
verification from others in order to get any attention, it seems only
reasonable that after many have said that the DPMS power saving is what
is not working,
I was still running your good test kernel:
(actual kernel package appeared autoremoved) 4.15.0-66-generic
#75~lp1845810 noise level low
Upgrading to bionic-updates:
4.15.0-70.79 4.15.0-70-generic #79-Ubuntu noise level high (as expected,
bug not yet fixed)
Upgrading to bionic-proposed:
@kaihengfeng Thank you for your help in resolving this!
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Your build works very well. The noise floor is even lower than before
the regression, and my audio quality is now the best I've heard it.
Thank you!
For clarity:
Medium noise: linux-image-4.15.0-58-generic 4.15.0-58.64
High noise (initial regression): linux-image-4.15.0-60-generic 4.15.0-60.67
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1845810/+attachment/5292818/+files/WifiSyslog.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages,
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1845810/+attachment/5292817/+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/1845810/+attachment/5292814/+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: "PulseList.txt"
https://bugs.launchpad.net/bugs/1845810/+attachment/5292815/+files/PulseList.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/1845810/+attachment/5292816/+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: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1845810/+attachment/5292808/+files/IwConfig.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/1845810/+attachment/5292811/+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: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1845810/+attachment/5292810/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
1 - 100 of 239 matches
Mail list logo
