to make my case once more:
- Debian is more modular, what is the reason we don't follow what upstream does
here?
- the size of the package leads to problems as evidenced in bug 1951422 and bug
1951423
- it should be possible to carve out the larger bits into a separate package
without making
It appears that this change might have introduced a regression.
Please have a look at bug 1960499 and bug 1960621.
+--[ https://askubuntu.com/questions/1392037/ ]
|
| From Ubuntu package list for nvidia-driver-*, any
| nvidia driver in the major versions on the left will
| be effectively
The linux-firmware package in jammy grew considerably and is now almost
1GB in size.
--
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/1958518
Title:
split some large, lesser-used
Juerg, thank you for picking this up and my apologies for the late
response.
You are of course right that there is no scientific answer or approach
to this question. I'd simply look at the biggest directories with ncdu
and make a decision if I thought that hardware was common when going
down the
** Changed in: linux-firmware (Ubuntu)
Status: Incomplete => Invalid
--
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/1515497
Title:
package linux-firmware 1.149 failed to
** Changed in: linux-firmware (Ubuntu)
Status: Fix Committed => Fix Released
--
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/1735271
Title:
Update firmware for netronome
This was fixed in vivid
linux-firmware (1.139) vivid; urgency=medium
* Rebase against
git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git
8ac569dd3ca3ca685bd47ee86c1eeb6050864db3
linux-firmware: Update AMD microcode patch firmware files
linux-firmware: Add
*** This bug is a duplicate of bug 1358025 ***
https://bugs.launchpad.net/bugs/1358025
** This bug has been marked a duplicate of bug 1358025
package linux-firmware 1.79.1 failed to install/upgrade: trying to overwrite
'/lib/firmware/ar3k/ramps_0x3101_40.dfu', which is also in package
I believe this has been addressed in the meantime, please confirm.
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux-
firmware/tree/debian?h=jammy
** Changed in: linux-firmware (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member
My apologies for the less-than-ideal experience. This isn't something
that Ubuntu can fix, but I believe it would be up to one of the OEM
groups to add breaks/replaces/conflict-information to the oem-wireless-
skyray-rtl8723be-1265442-dkms package
Reassigning (wild guess)
** Package changed:
*** This bug is a duplicate of bug 1358025 ***
https://bugs.launchpad.net/bugs/1358025
** This bug has been marked a duplicate of bug 1358025
package linux-firmware 1.79.1 failed to install/upgrade: trying to overwrite
'/lib/firmware/ar3k/ramps_0x3101_40.dfu', which is also in package
*** This bug is a duplicate of bug 1358025 ***
https://bugs.launchpad.net/bugs/1358025
** Package changed: linux-firmware (Ubuntu) => dell
** Changed in: dell
Status: Invalid => New
** This bug has been marked a duplicate of bug 1358025
package linux-firmware 1.79.1 failed to
*** This bug is a duplicate of bug 1358025 ***
https://bugs.launchpad.net/bugs/1358025
** This bug has been marked a duplicate of bug 1358025
package linux-firmware 1.79.1 failed to install/upgrade: trying to overwrite
'/lib/firmware/ar3k/ramps_0x3101_40.dfu', which is also in package
reassign to the dell project, they need to specify a Replaces-
relationship for their bt-dw1705-firmware package with the official
linux-firmware package from Ubuntu.
** Package changed: linux-firmware (Ubuntu) => dell
--
You received this bug notification because you are a member of Kernel
bt-dw1705-firmware is a third-party package and apparently it conflicts
with the official Ubuntu packages
It is not a good idea to install random software off the internet. In
case you insist to do, you are on your own.
Marking ticket as invalid.
** Changed in: linux-firmware (Ubuntu)
bt-dw1705-firmware is a third-party package and apparently it conflicts
with the official Ubuntu packages
It is not a good idea to install random software off the internet. In
case you insist to do, you are on your own.
Marking ticket as invalid.
** Changed in: linux-firmware (Ubuntu)
Public bug reported:
The linux-image-generic package depends on linux-firmware which is over
half a gigabyte in size installed. I will assume that quite many people
do not have netronome hardware which weighs in at almost 150MB of that.
I kindly suggest to put such large firmware for less common
upstream is closed WFM
time to close here, too?
--
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/1488758
Title:
GPU crash on NUC with i915
Status in linux package in Ubuntu:
Triaged
I'm sorry, but I dont' understand this bug report. Maybe you can
explain what you did, what you expected to happen and what happened
instead.
FWIW, turbostat exists just fine in focal.
$ dpkg -S /usr/bin/turbostat
linux-tools-common: /usr/bin/turbostat
--
You received this bug notification
Here is my status.
The hidd binary seems to be gone. The bluetooth-wizard binary worked
fine for me in bionic just now.
--
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/1059185
Title:
lucid is EOL
closing as obsolete
** Changed in: linux (Ubuntu)
Status: Confirmed => 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/884549
Title:
old linux-backports-*
Trusty is no longer supported.
Closing as obsolete
** Changed in: linux (Ubuntu)
Status: Triaged => Opinion
--
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/1529917
Title:
This hardware has long since bitten the dust over here.
Closing
** 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/513921
closing as obsolete
** 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/641027
Title:
Screen flickers after 2.6.32-24.42
Is this still an issue?
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
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/1320851
Title:
WARNING: CPU: 0 PID: 74 at
How about bionic and later?
--
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/1331149
Title:
Bluetooth: hci0 failed to open Intel firmware file
Status in linux package in Ubuntu:
old bug marked as fixed upstream
** 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/568655
Title:
[Sony Corporation
closing as no-response, obsolete
** 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/594129
Title:
8086:27a2 X crashs on
Public bug reported:
I have an X220 connected to a dock and via HDMI to an external monitor
running bionic. I noticed that anytime that I came back to the machine
from a screensaver both displays would flicker hard in certain areas of
the screen. The "fix" is to click the affected areas and then
still an issue?
** Changed in: linux (Ubuntu)
Status: Triaged => Incomplete
--
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/1023174
Title:
"ip -6 addr flush" flushes much more
closing as obsolete
** 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/698120
Title:
[gm45] Dual head corruption on
Can this be closed or is this still an issue?
** Changed in: linux (Ubuntu)
Status: Triaged => Incomplete
--
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/1396291
Title:
Maximum
4.15 is in bionic.
Setting to fixed, assuming this was just forgotten.
** Changed in: linux (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Nothing you say in your rant rules out an upstream bug. But maybe you
are not so interested in getting this analysed and fixed?
Anyhow, most likely time has moved on. Are you still affected by this
problem?
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
You received
Anybody who can still reproduce this particular problem?
** Changed in: linux (Ubuntu Xenial)
Status: Confirmed => Incomplete
--
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/1643566
I experience this, too, in bionic.
Possibly related to bug 1730458.
--
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/1674763
Title:
Warnings then GPF originating from nouveau under zesty
ping Michael and Urschl
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
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/1747273
Title:
Can not control brightness on
** Changed in: linux-firmware (Ubuntu)
Status: Incomplete => Invalid
--
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/1658352
Title:
package initramfs-tools 0.103ubuntu4.7
FWIW, this affects for example the latest www.system-rescue-cd.org as
well dated 2nd of April. It boots by default into an amd64 kernel but
the btrfs tools are i386. Very much looks like an upstream issue to me
and possibly more relevant than one might be tempted to think initially.
--
You
Asif, did Steve's instructions help you to resolve the issue?
** Changed in: linux-firmware (Ubuntu)
Status: New => Incomplete
** Changed in: linux-firmware (Ubuntu)
Assignee: (unassigned) => Rolf Leggewie (r0lf)
--
You received this bug notification because you are a
found this on the console when removing a kernel package:
dpkg: warning: while removing linux-image-4.4.0-81-generic, directory
'/lib/modules/4.4.0-81-generic' not empty so not removed
$ find /lib/modules/4.4.0-81-generic/
/lib/modules/4.4.0-81-generic/
/lib/modules/4.4.0-81-generic/modules.dep
@Daniel, have you even bothered to actually read this ticket? Comment
#11, for example?
Who gives a hoot about Quantal EOL in this case? Since you are paid you
ought to do a lot better.
** Changed in: bluez (Ubuntu)
Status: Incomplete => Confirmed
** Changed in: gnome-bluetooth
** Tags added: kernel-bug-exists-upstream
--
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/1678645
Title:
"btrfs send" returns "Inappropriate ioctl for device"
Status in linux package in
** 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/1678645
Title:
"btrfs send" returns "Inappropriate ioctl for device"
There's nothing missing, all necessary information is there.
** Changed in: linux (Ubuntu)
Status: Incomplete => New
--
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/1678645
Title:
** 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/1211976
Title:
[ 11.063330] WARNING: CPU: 2 PID: 1455 at
setting to fix released as per the latest comments
** 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/557224
Title:
** 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/1088053
Title:
Kernel needs to provide FIFREEZE/FITHAW ioctl so that
** No longer affects: linux (Ubuntu Trusty)
** No longer affects: linux (Ubuntu)
** No longer affects: linux (Ubuntu Vivid)
** No longer affects: linux (Ubuntu Wily)
** No longer affects: linux (Ubuntu Xenial)
** No longer affects: linux (Ubuntu Yakkety)
--
You received this bug
The fix is in trusty and later, so setting status to 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/1063791
Title:
ubuntu kernels < 3.7 do not include DISCARD/TRIM (FITRIM
Thanks, guys, for your work. The only release still affected by this
bug is precise which will be EOL by the end of this month. It's time to
move on. Closing as obsolete.
** Changed in: linux (Ubuntu)
Status: Triaged => Invalid
** Changed in: linux (Ubuntu)
Status: Invalid =>
found another similar bug 1678645
--
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/1619918
Title:
lsattr 32bit does not work on 64bit kernel (Inappropriate ioctl error)
Status in linux:
Public bug reported:
It seems I discovered another "Inappropriate ioctl for device" bug when
running an amd64 kernel on an i386 system (the first one was bug
1619918). My system is trusty, but I assume later versions and even
upstream are affected.
Steps to reproduce:
- run an amd64 kernel via
Can this ticket be closed?
--
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/1305335
Title:
Cutting or copying files on btrfs to ecryptfs results in data loss
Status in eCryptfs:
@Po-Hsu So, I did the work, yet you didn't act on it in time. Great!
Just confirms the impression of the Ubuntu kernel team I've had for a
while.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I'm happy to report that with kernel linux-
image-3.13.0-114-generic:amd64 and e2fsprogs:i386 on trusty the original
issue with lsattr is fixed and there are no regressions with "btrfs fi
show" or "btrfs sub snapshot".
For verification of the other kernels, is it sufficient for me to
install
Po-Hsu Lin, I understand the kernel team is busy, but frankly, I don't
understand why I should be doing all the work when it wasn't me
introducing the regression. There are clear steps provided in how to
verify the problem and the fix. I don't think it should be beyond those
who get paid for
Thank you for releasing the test kernels. I will likely need a bit more
time for testing than the allotted five days as the internet in this
part of the world is inadequate. Please confirm the extension.
--
You received this bug notification because you are a member of Kernel
Packages, which
I'm happy to report that with the latest kernel from
http://kernel.ubuntu.com/~jsalisbury/lp1619918/ the original issue with
lsattr is fixed and there are no regressions with "btrfs fi show" or
"btrfs sub snapshot".
--
You received this bug notification because you are a member of Kernel
still not fixed.
$ sudo find /lib/modules/4.4.0-53-generic/
/lib/modules/4.4.0-53-generic/
/lib/modules/4.4.0-53-generic/build
$ file /lib/modules/4.4.0-53-generic/build /lib/modules/4.4.0-53-generic/
/lib/modules/4.4.0-53-generic/build: symbolic link to
On 08.02.2017 04:29, Joseph Salisbury wrote:
> There should be a fix coming from upstream shortly:
> https://lkml.org/lkml/2017/2/6/969
Great! Thanks.
** No longer affects: linux (Ubuntu Vivid)
--
You received this bug notification because you are a member of Kernel
Packages, which is
How many more times will I have to do silly tests with predictable
results before this regression is finally fixed, Joseph? Just asking.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
On 07.01.2017 01:38, Luke-Jr wrote:
> On Friday, January 06, 2017 5:22:34 PM Joseph Salisbury wrote:
>> btrfs: bugfix: handle FS_IOC32_{GETFLAGS,SETFLAGS,GETVERSION} in
>> btrfs_ioctl
>>
>> However, this commit introduced a new regression. With this commit
>> applied, "btrfs fi show" no
Thank you for providing the kernel. Here are the (as expected results)
results:
- lsattr bug is back
- "btrfs fi show" works
- snapshotting works
$ uname -a
Linux 1001P 4.4.0-53-generic #74~lp1619918Commit4c63c2454eReverted SMP Tue Dec
13 18:27:31 UT x86_64 x86_64 x86_64 GNU/Linux
--
You
** Bug watch added: Linux Kernel Bug Tracker #190221
http://bugzilla.kernel.org/show_bug.cgi?id=190221
** Also affects: kernel via
http://bugzilla.kernel.org/show_bug.cgi?id=190221
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member
adding to comment #36: mainline kernel 4.9.0-040900rc7-generic
#201611271731 does
- not have the problem with lsattr
- not have the problem with "btrfs fi show"
- INDEED have the problem with snapshotting
--
You received this bug notification because you are a member of Kernel
Packages, which
The original bug is just an annoyance in my opinion and a cornercase as
well. From what I can tell it makes it impossible to get extended
attributes for any file, but only if you have a mixed i386/amd64
environment, run the amd64 kernel while having i386 e2fsprogs. The
impact of that should be
IOW, I think backing out the patch and reintroducing the original
problem is better than keeping the regression the fix introduced to
stick around.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
mainline amd64 kernel 4.9.0-040900rc7-generic #201611271731 does not
have the problem with lsattr "btrfs fi show". It DOES have the problem
with creating a btrfs snapshot.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Changed in: libmtp (Ubuntu)
Status: Confirmed => Fix Released
** 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.
You know, it's getting to be somewhat annoying. I have very limited
bandwidth here. Why don't you back out the patch already until a proper
solution is found? I will happily continue to test but as you can see
it does take me some time. The test case is pretty clear, why can you
not be
Ubuntu has not shipped a btrfs package for a long time, moving to kernel
bugs for triage.
This bug is pretty old. Did anyone affected by this experience it with
xenial or later?
** Package changed: btrfs (Ubuntu) => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: New => Incomplete
I've downloaded the kernel from
http://kernel.ubuntu.com/~jsalisbury/lp1619918/xenial/ and
https://launchpad.net/~canonical-kernel-security-
team/+archive/ubuntu/ppa/+build/11038082 now. Both kernels have the
same problem/regression (verified with "sudo btrfs fi show /")
--
You received this
I apologize for the delayed response, I was travelling.
Yes, the error message is the same as for the original report. Then it
was triggered by a call to lsattr, now by calling btrfs to create a
snapshot. The released kernels do not have the originally reported
problem with lsattr but regressed
Thank you for providing the test kernel. Unfortunately, it does not fix
the regression. I installed the trusty kernel. I did not install the
linux-tools-* packages as it would have uninstalled the trusty version
of linux-tools-generic. I have the i386 version of that package
installed but I
The "I don't give a sh.."-attitude displayed here towards a regression
is shocking. Why do I even bother to test?
The regression is apparently much more severe to obot. I can no longer
take a snapshot of my btrfs filesystem.
$ sudo btrfs sub snapshot -r /mnt/LTS/@home/
Brad, how can you set this to verified and release when that introduces
a pretty severe regression? OMG!!
** Tags added: regression-update
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Yes, regression from -96 to -97 verified on trusty.
** Tags removed: verification-done-trusty
** Tags added: regression-proposed verification-needed-trusty
** Tags removed: verification-needed-trusty
** Tags added: verification-done-trusty
** Changed in: linux (Ubuntu Trusty)
Status: Fix
I think there might be a regression with this kernel. "sudo btrfs fi
show" no longer works and only puts out "Btrfs v3.12"
--
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/1619918
Title:
Thanks. This works well in trusty.
** Tags removed: verification-needed-trusty
** Tags added: verification-done-trusty
--
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/1619918
Title:
Alistair, can you confirm the fix as reported by John in #43?
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Rolf Leggewie (r0lf)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.
Still present on trusty and it seems to be a problem with tp-smapi-dkms.
$ find /lib/modules/3.13.0-65-generic/
/lib/modules/3.13.0-65-generic/
/lib/modules/3.13.0-65-generic/updates
/lib/modules/3.13.0-65-generic/updates/dkms
/lib/modules/3.13.0-65-generic/updates/dkms/thinkpad_ec.ko
@All, please let us know what your current status with regards to this
ticket. Are you still affected?
--
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/1059185
Title:
bluetooth-wizard
Konrad, that's premature. This problem was reported for example against
trusty which until very recently was the latest LTS. Please stop
closing tickets just because they are old. You can always ask if people
are still affected by this problem and then close the ticket if there is
no response.
** Changed in: linux-lts-backport-maverick (Ubuntu Utopic)
Status: New => Won't Fix
** Changed in: linux-lts-backport-natty (Ubuntu Utopic)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
** Changed in: linux-lts-backport-maverick (Ubuntu Utopic)
Status: New => Won't Fix
** Changed in: linux-lts-backport-natty (Ubuntu Utopic)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
** Changed in: linux-lts-backport-maverick (Ubuntu Utopic)
Status: New => Won't Fix
** Changed in: linux-lts-backport-natty (Ubuntu Utopic)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
** Changed in: linux-lts-backport-maverick (Ubuntu Utopic)
Status: New => Won't Fix
** Changed in: linux-lts-backport-natty (Ubuntu Utopic)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
** Changed in: linux-lts-backport-maverick (Ubuntu Utopic)
Status: New => Won't Fix
** Changed in: linux-lts-backport-natty (Ubuntu Utopic)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
** Changed in: linux-lts-backport-maverick (Ubuntu Utopic)
Status: New => Won't Fix
** Changed in: linux-lts-backport-natty (Ubuntu Utopic)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
** Changed in: linux-lts-backport-maverick (Ubuntu Utopic)
Status: New => Won't Fix
** Changed in: linux-lts-backport-natty (Ubuntu Utopic)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
** Changed in: linux-lts-backport-maverick (Ubuntu Utopic)
Status: New => Won't Fix
** Changed in: linux-lts-backport-natty (Ubuntu Utopic)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
** Changed in: linux-lts-backport-maverick (Ubuntu Utopic)
Status: New => Won't Fix
** Changed in: linux-lts-backport-natty (Ubuntu Utopic)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
** Changed in: linux-lts-backport-maverick (Ubuntu Utopic)
Status: New => Won't Fix
** Changed in: linux-lts-backport-natty (Ubuntu Utopic)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
** Changed in: linux-lts-backport-maverick (Ubuntu Utopic)
Status: New => Won't Fix
** Changed in: linux-lts-backport-natty (Ubuntu Utopic)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
** Changed in: linux-lts-backport-maverick (Ubuntu Utopic)
Status: New => Won't Fix
** Changed in: linux-lts-backport-natty (Ubuntu Utopic)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
** Changed in: linux-lts-backport-maverick (Ubuntu Utopic)
Status: New => Won't Fix
** Changed in: linux-lts-backport-natty (Ubuntu Utopic)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
** Changed in: linux-lts-backport-maverick (Ubuntu Utopic)
Status: New => Won't Fix
** Changed in: linux-lts-backport-natty (Ubuntu Utopic)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
** Changed in: linux-lts-backport-maverick (Ubuntu Utopic)
Status: New => Won't Fix
** Changed in: linux-lts-backport-natty (Ubuntu Utopic)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
** Changed in: linux-hammerhead (Ubuntu Utopic)
Status: New => Won't Fix
** Changed in: linux-raspi2 (Ubuntu Utopic)
Status: New => Won't Fix
** Changed in: linux-meta (Ubuntu Utopic)
Status: New => Won't Fix
--
You received this bug notification because you are a member
1 - 100 of 1016 matches
Mail list logo
