Hi,
the test plan calls out for two additional steps which I don't see in
your verification:
> run hciconfig, the hci0 shows up.
> run checkbox testcase, it could pass.
> [Checkbox job `com.canonical.certification::bluetooth/detect-output` output]
Could you please clarify if you have performed
Hi,
I can confirm that linux-generic 5.15.0.105 is not available yet in
proposed repository. Latest version is 104.
# apt policy linux-generic
linux-generic:
Installed: 5.15.0.102.99
Candidate: 5.15.0.104.101
Version table:
5.15.0.104.101 500
500
Here's a log file when booting with kernel 6.5.
** Attachment added: "Kernel-6.5-boot.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2061295/+attachment/5765233/+files/Kernel-6.5-boot.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is
Attaching a log file from a failed boot with kernel 6.8 with splash
enabled
** Attachment added: "failedboot.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2061295/+attachment/5765213/+files/failedboot.txt
** Description changed:
I upgraded from 23.10 to 24.04, and with it the
Public bug reported:
I upgraded from 23.10 to 24.04, and with it the new 6.8 kernel. I do not
see the Kubuntu EFI logo, and the system never reaches the sddm login
screen. I could not switch to a tty to login either. If I boot kernel
6.5 it works as expected.
If I remove "quiet splash" from the
*** This bug is a duplicate of bug 2056442 ***
https://bugs.launchpad.net/bugs/2056442
** This bug has been marked a duplicate of bug 2056442
Podman (crun) regression in Ubuntu 22.04: OCI runtime error: chmod
`run/shm`: Operation not supported
--
You received this bug notification
but I also don't want to
leave them unpatched!
Thanks, Andreas
--
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/2060780
Title:
CIFS stopped working/is unstable with kernel update to 5.15.0
Adding a release notes task to put a note under "known issues".
** Also affects: ubuntu-release-notes
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Marking the userspace component (src:nfs-utils) task as invalid, since
it's a bug in the kernel.
** Changed in: nfs-utils (Ubuntu)
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
That would be
https://github.com/torvalds/linux/commit/fce7913b13d0270bcf926f986b7ef329e2e56eec
--
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/2060217
Title:
NFSv4 fails to mount in
> Could I know the kernel version which use for below test?
Search for "testbed running kernel". In the case of that test, it's:
859s autopkgtest [01:53:38]: testbed running kernel: Linux 6.6.0-14-generic
#14-Ubuntu SMP Thu Nov 30 09:46:34 UTC 2023
--
You received this bug notification because
Public bug reported:
Hi,
updated some Ubuntu 22.04 systems to lastest available state this
morning, which caused CIFS mounts (from various fileservers) to stop
working. Kernel was updated to version 5.15.0-102-generic.
I can mount the shares without problems (mount -t cifs), but then, df for
See related question
--
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/2060780
Title:
CIFS stopped working/is unstable with kernel update to 5.15.0-102.112
Status in linux package in
I have GuoqingJiang access to the s390x vm where this bug can be
observed.
--
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/2060217
Title:
NFSv4 fails to mount in noble/s390x
Status in
Perhaps try an older kernel, from when the test last passed?
--
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/2060217
Title:
NFSv4 fails to mount in noble/s390x
Status in Ubuntu on IBM z
** Tags added: update-excuse
--
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/2060217
Title:
NFSv4 fails to mount in noble/s390x
Status in linux package in Ubuntu:
New
Status in
I have a VM where this can be reproduced, if anyone is interested.
--
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/2060217
Title:
NFSv4 fails to mount in noble/s390x
Status in linux
> Does running `mount -vvv ...` provide more information?
Nope, same as single -v:
root@nfs:~# mount /mnt/nfs_home -vvv
mount.nfs: timeout set for Mon Apr 8 15:48:10 2024
mount.nfs: trying text-based options
'vers=4.2,addr=127.0.0.1,clientaddr=127.0.0.1'
mount.nfs: mount(2): Input/output
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
- Just filing the bug now to keep track of it. No troubleshooting done
- yet.
-
https://autopkgtest.ubuntu.com/packages/n/nfs-utils/noble/s390x
Looks like it has been failing for a long
The verification of the Stable Release Update for alsa-ucm-conf 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
Ethan, thanks for the verification.
In the future, please include the exact version of the package that you
tested, and where it came from. I.e., the output of "apt-cache policy
" shows all that information.
There have been a few cases in the past where the verification was
mistakenly done using
Changed status to 'Fix Released' as multiple reports have been made that
this issue no longer occurs on kernel 6.5.0-17-generic.
** Changed in: linux-meta-hwe-6.5 (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages,
Public bug reported:
Would it be possible to update the wireless-regdb on all active ubuntu releases
to the latest upstream (2024-01.23) release? New regulations have been
published. One of those is the 6GHz Wifi in Switzerland.
The current package, 2022.06.06 is quite outdated.
With an update
Thanks @vicamo, but what we want to ensure is much simpler than that
whole release process.
We just want to be sure that the firmware-sof from proposed, and the
updated kernel from proposed (and updates, i.e., currently available
outside proposed) were tested together according to the test plan.
The verification of the Stable Release Update for alsa-ucm-conf 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
** Description changed:
The tuned package has some plugins which rely on the perf python module
[1], and right now they are not working because we do not have the perf
python module available in Ubuntu.
Initially, this was reported in this other bug [2], but it seems the
scope of
We (server team) are working on the src:tuned[0] package, and several of
its profiles make use of the python perf module. That module comes from
the linux kernel AFAIK, and we are just not building it.
In Fedora, it's shipped in the bin:python3-perf package:
[root@f39 ~]# rpm -ql python3-perf
Hello Lee, or anyone else affected,
Accepted mesa into jammy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mesa/23.2.1-1ubuntu3.1~22.04.2 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Please amend the test case to test with both the GA and the (affected)
6.1 OEM kernels.
--
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/2051068
Title:
GUI crashed after installed
Letting you know that the issue persists with kernel 6.5.0-15-generic.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta-hwe-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2048935
Title:
Right speaker broken on Dell XPS 13
This still needs a verification for mantic (I added the missing tag),
and the fix also needs to land in noble.
** Tags added: verification-needed-mantic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
> because of lp:2047492, I can't verify it on mantic.
If this can't be verified in mantic, then please don't flip the mantic
verification tags :)
** Tags removed: verification-done-mantic
** Tags added: verification-needed-mantic
--
You received this bug notification because you are a member
Public bug reported:
After upgrading from the previous HWE kernel 6.2.0-39-generic to the new
HWE kernel 6.5.0-14-generic, the right speaker no longer works. When
booting back into the old HWE kernel, the right speaker functions again.
The left speaker works in both cases.
Hardware info:
Dell
** Tags removed: verification-done-mantic
** Tags added: verification-needed-mantic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2031412
Title:
Support mipi camera on Intel
I just ran this command on my mantic laptop, according to the [test
plan]:
sudo add-apt-repository ppa:oem-solutions-group/intel-ipu6 -y -u
And that PPA does not have mantic packages:
Err:24 https://ppa.launchpadcontent.net/oem-solutions-group/intel-ipu6/ubuntu
mantic Release
This was uploaded, removing sponsors as there is nothing further to
sponsor.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2031412
Title:
Support mipi camera on Intel Meteor
Hello You-Sheng, or anyone else affected,
Accepted ipu6-drivers into mantic-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/ipu6-drivers/0~git202310180730.3f813580-0ubuntu0.23.10.1
in a few hours, and then in the -proposed repository.
Please help us
Could https://github.com/openzfs/zfs/pull/15651 be picked up for this
update still?
--
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/2044657
Title:
Multiple data corruption issues in
The verification of the Stable Release Update for zfs-linux 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
Oh, I missed this bit in https://bugs.launchpad.net/ubuntu/+source/zfs-
linux/+bug/2040181/comments/10 in the other bug:
"It is still worth it to release this sru, before staging the next one
in proposed"
--
You received this bug notification because you are a member of Kernel
Packages, which
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2040181
updating mantic to 2.2.0 final is in mantic-proposed, and this bug here
is in mantic-unapproved.
Should we drop 2.2.0 from mantic-proposed in favor of this one here?
--
You received this bug notification because you are a member
@Artur,
a) you had a previous debdiff for mantic which used version
1.2.9-1ubuntu3.1, which is what we expect for an SRU to mantic, but now
in the mantic unapproved queue I see that you changed the version to
1.2.9-1ubuntu4 again.
The upgrade path between ubuntu releases still works:
Generally, it's your call, unless what you mean is that the current
version in unapproved, without the fix for 2044991, is broken/bad/not-
worth-it. Keep in mind that you would be adding another bug to the sru,
requiring again the full SRU template (impact, test plan, validation),
and all of the
ipu6-drivers in mantic unapproved is addressing more than just this bug:
its changes[1] file lists 2012407 2021740 2026402 2031412.
#2021740 had a question about using a ppa in the test case
#2026402 didn't have a test case, and Timo recently added a comment saying that
this bug was actually
** Description changed:
- NOTE: this SRU depends on intel-usbio-dkms from bug #2041800
-
[SRU Justification]
== ipu6-driver ==
[Impact]
Missing Intel MIPI firmware for Meteor Lake platform.
[Fix]
Based on upstream tag
** Description changed:
+ NOTE: this SRU depends on intel-usbio-dkms from bug #2041800
+
+
[SRU Justification]
== ipu6-driver ==
[Impact]
Missing Intel MIPI firmware for Meteor Lake platform.
[Fix]
Based on upstream tag
Can we change the test case to this:
# enable mantic-proposed, update the kernel, make sure you get 6.5.0-14.14
# reboot into the 6.5.0-14.14 kernel
$ sudo apt install intel-ipu6-dkms intel-vsc-dkms
$ sudo apt install intel-usbio-dkms # from bug 2041800
$ sudo add-apt-repository
ok, so let's see:
> [Test Case]
>
> With all other changes in position, Intel VSC driver modules are to be loaded
> as a soft dependency of some selected camera sensor modules. LJCA modules
> should be loaded automatically on MTL platforms as well.
>
> To actually verify the camera framework:
>
Anscheinend. Mein Fehlerbericht ist mehr als sechs Monate alt, hat
tierisch viel Arbeit gemacht und interessiert kein einziges Exemplar der
Gattung porcus. Es geht ja auch nur um Datenverlust, da gibt es viel
größere Probleme. Geradezu lächerlich.
--
You received this bug notification because
The src:ivsc-driver package produces bin:intel-vsc-dkms
The src:ipu6-drivers package produces bin:intel-ipu6-dkms
We need the test case to use these binary dkms packages from mantic-
proposed (once they get accepted). These are the packages being proposed
for the SRU, so they are the ones that
Hi,
this review is about the ipu6-driver portion of this SRU, which I will
paste below and add inline comments to:
> == ipu6-driver ==
>
> [Impact]
>
> Missing Intel MIPI firmware for Meteor Lake platform.
The changes in ipu6-drivers are not adding a new firmware as far as I
can
Hi,
this review is about the ivsc-driver portion of this SRU, which I will
paste below and add inline comments to:
> == ivsc-driver ==
>
> [Impact]
>
> Missing Intel MIPI firmware for Meteor Lake platform.
The patches added to the ivsc-driver package do not seem to be about a
Also, the "linux" task of this bug, for mantic, is "fix committed". It's
this one I believe:
https://launchpad.net/ubuntu/+source/linux/6.5.0-14.14
So can the tests be made using that kernel? It is claiming to have added
support for MIPI cameras, to some extent:
* Support mipi camera on Intel
No update since Oct 27th, unsubscribing sponsors. Please subscribe again
if there is an update.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to iproute2 in Ubuntu.
Matching subscriptions: iproute2
https://bugs.launchpad.net/bugs/2039280
The verification of the Stable Release Update for mutter 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 a
I still get this error in Ubuntu Lunar, with kernel 6.2.0-35-generic.
Sample:
$ sudo dmesg -T|grep Atomic
[qua nov 1 05:52:03 2023] i915 :00:02.0: [drm] *ERROR* Atomic update
failure on pipe A (start=78023 end=78024) time 305 us, min 1783, max 1799,
scanline start 1753, end 1804
[qua nov
I agree that a merge from debian would be better, since we are quite
behind:
iproute2 | 6.5.0-4 | testing
But we have been at 6.1.0 since at least lunar, so I don't know how long
that would take. I think we can take these patches for noble.
I would ask that you also add this one,
Hi Chengen, or someone else:
could you please clarify that you also performed the test with the 5.15
GA kernel for Jammy, not just 6.2, which is what I assume you did?
I see that @mfo tested with 5.15 in comment #7, but that was before the
package landed in jammy-proposed.
--
You received this
Hello ethan.hsieh, or anyone else affected,
Accepted alsa-ucm-conf into jammy-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/alsa-ucm-
conf/1.2.6.3-1ubuntu1.8 in a few hours, and then in the -proposed
repository.
Please help us by testing this new
Hello ethan.hsieh, or anyone else affected,
Accepted alsa-ucm-conf into lunar-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/alsa-ucm-
conf/1.2.6.3-1ubuntu9.2 in a few hours, and then in the -proposed
repository.
Please help us by testing this new
** Also affects: alsa-ucm-conf (Ubuntu Lunar)
Importance: Undecided
Status: New
** Also affects: alsa-ucm-conf (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: alsa-ucm-conf (Ubuntu Jammy)
Assignee: (unassigned) => ethan.hsieh (ethan.hsieh)
** Changed in:
** Description changed:
Following a recent change from linux-kvm kernel to linux-generic kernel
in the mantic minimized images there is a reproducable bug where a guest
VM does not have an IP address assigned as part of cloud-init
provisioning.
This is easiest to reproduce when
Thanks for your last update.
cifs is indeed provided by the kernel, and mounted via mount.cifs from
cifs-utils. Although similar in nature, this is not samba code. All of
this discussion is pointing at something in the kernel, so I'm switching
the bug task from samba to linux (which is the
PLease keep in mind that the test plan should be executed on the jammy
official kernels.
--
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/2028217
Title:
MTL: Add support for Meteor
Hello koba, or anyone else affected,
Accepted thermald into jammy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/thermald/2.4.9-1ubuntu0.4 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
The verification of the Stable Release Update for dkms 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 a
I suppose it's possible that the particular dkms module that failed to
build is essential for booting the system, so the new approach that
hides this build failure could render the system unbootable without the
user realizing it. A bit less catastrophic, but still very serious,
would be for the
I'm just noticing the discrepancy between the test plan, and the test
execution. If you are confident that a 10min run reproduces the problem,
then please update the test plan accordingly, because it currently says
6h.
--
You received this bug notification because you are a member of Kernel
The test plan calls for a 6h run:
"""
5. monitor cpu temperature for 6 hours if you didn’t hit overheat and shutdown
issue.
"""
Yet the verification says it ran for only 15min?
Is the original test plan wrong, or why is a 15min run ok?
** Tags removed: verification-done-jammy
** Tags added:
kinetic is eol
** Changed in: thermald (Ubuntu Kinetic)
Status: In Progress => Won't Fix
--
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/2012260
Title:
Add support for Alder
Hm, question: I see you are running an oem kernel. Does this thermald
fix only work when running on that specific kernel? Or will it also work
on the normal jammy kernel?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to thermald in Ubuntu.
I'm adding notes do these thermald bugs because it's one upload
addressing 7 bugs, and some have verification done in other bugs, so it
can be hard to track.
This verification is ok.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Hi @koba,
I think you pasted the wrong log in this bug here. You pasted the
verification for INT3400 (bug #1989044)?
** Tags removed: verification-done-jammy
** Tags added: verification-needed-jammy
--
You received this bug notification because you are a member of Kernel
Packages, which is
I'm adding notes do these thermald bugs because it's one upload
addressing 7 bugs, and some have verification done in other bugs, so it
can be hard to track.
This verification is ok.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
We talked OOB, and I think this would be enough for test 1:
- run some workload (the benchmark might be fine) that, with thermald from
jammy (2.4.9-1ubuntu0.2), will throttle the GPU "too soon". I assume there will
be some log message about this throttling. Note the benchmark should exercise
Hi koba, thanks for your update.
I don't know how to interpret it, though, I'm not familiar with that
benchmark you ran. The test plan asks for a game (let's call it
workload) to be used, and to show that the game is not throttled, i.e.,
FPS is not reduced.
We could transpose that to "run
Hello Ionut, or anyone else affected,
Accepted mutter into jammy-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/mutter/42.9-0ubuntu3
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
In the test plan, can you also please confirm it keeps working with the
current and upcoming HWE kernels for jammy?
** Changed in: mutter (Ubuntu Jammy)
Status: In Progress => Fix Committed
** Tags added: verification-needed verification-needed-jammy
--
You received this bug
Before being released into jammy, this will still need a Mantic upload
(devel release), and at least a Lunar upload.
I'm not qualified to do firmware package reviews, as I think these
packages have something special about their release (like a digital
signature), and I don't know how to review
Interesting, so 3.14 did not introduce the problem (I'm assuming you
rebooted). What version did you have before when it was still working?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
Hi Peter, thanks for this report.
Here are a few things for you to please check:
The previous version of this package in jammy-updates was
20220329.git681281e4-0ubuntu3.13[1]. I'm assuming that's the one you had
before. Could you please try to install that one over what you have now,
and see if
Waiting for another debdiff to address the points raised in previous
comments.
--
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/1995606
Title:
Upgrade thermald to 2.5.1 for Jammy
zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.26.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: andreas4727 F pipewire
andreas4730 F wireplumber
/dev/snd/seq: andreas472
zavl icp zcommon znvpair
ApportVersion: 2.26.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: andreas4727 F pipewire
andreas4730 F wireplumber
/dev/snd/seq:andreas4727 F pipewire
The verification of the Stable Release Update for zfs-linux 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
The verification of the Stable Release Update for alsa-ucm-conf 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
Thank you, so we have verification on the oem kernels, and the proposed
kernels, for jammy, kinetic, and lunar.
Did you try alsa-ucm-conf with the currently released kernels for those
ubuntu releases? I wouldn't expect the LED to work, if it requires a
newer kernel, but just to check if nothing
apport information
** Attachment added: "acpidump.txt"
https://bugs.launchpad.net/bugs/2019153/+attachment/5675220/+files/acpidump.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: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/2019153/+attachment/5675219/+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/2019153/+attachment/5675218/+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/2019153/+attachment/5675217/+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: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/2019153/+attachment/5675216/+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/2019153/+attachment/5675215/+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: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/2019153/+attachment/5675214/+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/2019153/+attachment/5675213/+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/2019153/+attachment/5675212/+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-t.txt"
https://bugs.launchpad.net/bugs/2019153/+attachment/5675211/+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: "Lsusb.txt"
https://bugs.launchpad.net/bugs/2019153/+attachment/5675210/+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/2019153
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/2019153/+attachment/5675209/+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: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/2019153/+attachment/5675207/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
1 - 100 of 690 matches
Mail list logo
