yes, I filled one. the link is somewhere upwards
--
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/1275116
Title:
lowlatency-flavour crashes and locks up alot
Status in “linux” package in
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/1283965
Title:
Graphics problem: laptop
** Changed in: kernel-development-workflow
Status: In Progress = Fix Released
** Changed in: kernel-development-workflow/promote-to-release
Status: New = Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
** Tags removed: block-proposed 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/1283074
Title:
linux: 3.13.0-12.32 -proposed tracker
Status in Kernel Development Workflow:
In
Dima Ryazanov, please boot into Trusty via
http://cdimage.ubuntu.com/daily-live/current/ , and execute the following via a
terminal:
apport-collect 1244501
** Changed in: linux (Ubuntu)
Status: Confirmed = Incomplete
--
You received this bug notification because you are a member of
** Tags added: 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/1283074
Title:
linux: 3.13.0-12.32 -proposed tracker
Status in Kernel Development Workflow:
In Progress
Status in
I also have a Samsung NP-A530U3C-A01UK laptop that exhibits the same
behaviour. Since applying the fix from juanmanul all is now well.
Many thanks juanmanual for identifying the cause for this long running
issue and for working diligently to find the fix.
--
You received this bug notification
Shubham Verma, thank you for reporting this and helping make Ubuntu better.
+ Could you please provide exact detail on how you installed the MBuntu OSX
theme and marlin file manager (URLs, PPA, etc.)?
+ If you uninstall the MBuntu OSX theme, and use a file manager that comes by
default with
** Tags added: regression-update
** Tags added: latest-bios-4bcn24ww
** Summary changed:
- Lenovo Ideapad S205 Brightness keys do not work anymore
+ [IdeaPad S205 Notebook] Brightness keys do not work anymore
--
You received this bug notification because you are a member of Kernel
Packages,
** Summary changed:
- linux-ti-omap4: version to be filled -proposed tracker
+ linux-ti-omap4: 3.2.0-1444.63 -proposed tracker
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-ti-omap4 in Ubuntu.
Public bug reported:
I have a HP Notebook 14 and the Alps touchpad on it is not detected. The
Touchpad tab in the Mouse preferences is absent.
WIndows 8 reports it as Alps Touch Pad 8.201.1711.126.
ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: linux-image-3.11.0-17-generic 3.11.0-17.31
I realized I might have been a bit terse in the description. The
touchpad is detected as a PS/2 mouse and works that way. There's no
tapping or 3-rd button emulation or anything like that though.
--
You received this bug notification because you are a member of Kernel
Packages, which is
Andrew, thank you for reporting this and helping make Ubuntu better. Could you
please test the latest upstream kernel available (not the daily folder)
following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow
additional upstream developers to examine the issue. Once you've tested
** Summary changed:
- suspend/resume failure
+ [Intel DP35DP] suspend/resume failure
** Tags added: bios-outdated-0572
--
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/1283777
Title:
For informational purpose: Still present in 3.14.0-031400rc4-generic
--
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/1280467
Title:
ACPI Warning: 0x1828-0x182f
Togo28, thank you for reporting this and helping make Ubuntu better. As per
https://downloadcenter.intel.com/SearchResult.aspx?lang=engProductFamily=Desktop+BoardsProductLine=Intel%C2%AE+3+Series+Chipset+BoardsProductProduct=Intel%C2%AE+Desktop+Board+DP35DP
an update to your BIOS is available
Still present in kernel 3.14.0-031400rc4-generic
--
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/1279699
Title:
AER: Corrected error received: id=00e4 / PCIe Bus Error:
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/1284044
Title:
Alps touchpad not detected
git://kernel.ubuntu.com/ppisati/ubuntu-precise.git ti-omap4
** Changed in: kernel-sru-workflow/upload-to-ppa
Status: New = Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-ti-omap4 in Ubuntu.
** Description changed:
This bug is for tracking the version to be filled upload package. This
bug will contain status and testing results related to that upload.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
git://kernel.ubuntu.com/ppisati/ubuntu-quantal.git ti-omap4
** Summary changed:
- linux-ti-omap4: version to be filled -proposed tracker
+ linux-ti-omap4: 3.5.0-239.55 -proposed tracker
** Changed in: kernel-sru-workflow/upload-to-ppa
Status: New = Confirmed
--
You received this bug
Public bug reported:
just after reboot
ProblemType: KernelOops
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-12-generic 3.13.0-12.32
ProcVersionSignature: Ubuntu 3.13.0-12.32-generic 3.13.4
Uname: Linux 3.13.0-12-generic i686
NonfreeKernelModules: nvidia
Annotation: Your system might
This bug was fixed in the package linux - 3.13.0-12.32
---
linux (3.13.0-12.32) trusty; urgency=low
[ Andy Whitcroft ]
* Release Tracking Bug
- LP: #1283074
* Revert SAUCE: Drivers: hv: vmbus: Specify the target CPU that should
receive notification
* [Packaging]
This bug was fixed in the package linux - 3.13.0-12.32
---
linux (3.13.0-12.32) trusty; urgency=low
[ Andy Whitcroft ]
* Release Tracking Bug
- LP: #1283074
* Revert SAUCE: Drivers: hv: vmbus: Specify the target CPU that should
receive notification
* [Packaging]
Terry Relph-Knight, thank you for reporting this bug and helping make
Ubuntu better. Could you please provide the full computer model as noted
on the sticker (ex. XPS M1530)?
** Changed in: linux (Ubuntu)
Importance: Undecided = Medium
** Changed in: linux (Ubuntu)
Status: Confirmed =
This bug was fixed in the package linux - 3.13.0-12.32
---
linux (3.13.0-12.32) trusty; urgency=low
[ Andy Whitcroft ]
* Release Tracking Bug
- LP: #1283074
* Revert SAUCE: Drivers: hv: vmbus: Specify the target CPU that should
receive notification
* [Packaging]
This bug was fixed in the package linux - 3.13.0-12.32
---
linux (3.13.0-12.32) trusty; urgency=low
[ Andy Whitcroft ]
* Release Tracking Bug
- LP: #1283074
* Revert SAUCE: Drivers: hv: vmbus: Specify the target CPU that should
receive notification
* [Packaging]
This bug was fixed in the package linux - 3.13.0-12.32
---
linux (3.13.0-12.32) trusty; urgency=low
[ Andy Whitcroft ]
* Release Tracking Bug
- LP: #1283074
* Revert SAUCE: Drivers: hv: vmbus: Specify the target CPU that should
receive notification
* [Packaging]
Public bug reported:
just after reboot
ProblemType: KernelOops
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-12-generic 3.13.0-12.32
ProcVersionSignature: Ubuntu 3.13.0-12.32-generic 3.13.4
Uname: Linux 3.13.0-12-generic i686
NonfreeKernelModules: nvidia
Annotation: Your system might
Public bug reported:
just after reboot
ProblemType: KernelOops
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-12-generic 3.13.0-12.32
ProcVersionSignature: Ubuntu 3.13.0-12.32-generic 3.13.4
Uname: Linux 3.13.0-12-generic i686
NonfreeKernelModules: nvidia
Annotation: Your system might
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/1284068
Title:
BUG: soft lockup - CPU#0 stuck
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/1284069
Title:
BUG: soft lockup - CPU#1 stuck
** Tags removed: need-duplicate-check
--
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/1284070
Title:
BUG: soft lockup - CPU#1 stuck for 23s! [kswapd0:31]
Status in “linux” package in
** Tags removed: need-duplicate-check
--
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/1284069
Title:
BUG: soft lockup - CPU#1 stuck for 22s! [kswapd0:31]
Status in “linux” package in
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/1284070
Title:
BUG: soft lockup - CPU#1 stuck
** Tags removed: need-duplicate-check
--
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/1284068
Title:
BUG: soft lockup - CPU#0 stuck for 22s! [kswapd0:31]
Status in “linux” package in
** Changed in: kernel-development-workflow/promote-to-release
Status: New = Fix Released
** Changed in: kernel-development-workflow
Status: In Progress = Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
Devs,
Any chance this bug might get a little attention? It makes my pc practically
un-usable.
Everytime I run efibootmgr with the -c option to create a boot
entry, it erases all existing ones. Only the last entry added from
efibootmgr persists - even the device select entries like Boot from USB,
** Description changed:
This bug is for tracking the version to be filled upload package. This
bug will contain status and testing results related to that upload.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
Public bug reported:
Booting and installing from a live usb for trusty does work. However, on
restart the machine will not boot. It hangs at:
https://www.dropbox.com/s/behviox991o01o1/2014-02-23%2016.15.15.jpg
Per apw in #ubuntu-kernel a test to add nr_cpus=1 does work to boot the
machine.
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/1284085
Title:
unable to boot after install
From recent experience working on
https://bugzilla.kernel.org/show_bug.cgi?id=70881, it appears that the
kernels default is to:
- On module load, default to global region
- When associating to an AP, reset the local region to match the APs
It seems like unless you are going to run in AP mode, or
Public bug reported:
Only very recent versions of wireless-regdb have support for VHT (80mhz
channels); in addition, all current kernels have a bug that will cause
your card to fail to associate with a VHT ap when your local regdb
didn't allow VHT:
I have requested an update to an even newer version of regdb, both in
the Debian request that references this, and in #1284093. This is needed
to support VHT, but would also fix this issue.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
** Description changed:
This CVE was fixed under 5d81de8e8667da7135d3a32a964087c0faf5483f but
there is a second fix which will make this much safer going forward
against other bugs:
- http://article.gmane.org/gmane.linux.kernel.cifs/9402
+
The laptop I have the problem on is a Dell XPS M1210 Model PP11S
--
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/1283741
Title:
BUG: unable to handle kernel NULL pointer dereference at
Hey
I've updated my first version a bit, so here is v2.
Changed some values to match the hammerhead file Georg sent to the mailing list
yesterday.
I can't really reproduce the distortion in sound, except when you plug in
headphones (the first thing played is distorted).
There is also a bug,
** Tags removed: needs-upstream-testing
** Tags added: kernel-fixed-upstream kernel-fixed-upstream-3.4.0-030400-generic
--
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/1283953
Title:
Quick'n dirty fix to get both USB3 and Bluetooth running every time - do
automatic xhci_xcd unload / load cycle until no error messages in syslog
is detected:
Needs:
1. custom compiled kernel with xhci_xcd as module, not builtin.
2. Upstream kernel with device ids for 168c:0036 or recompiled
Christopher, thank you for your quick reply. I've done testing the bug
with mainlne 32-bit kernel 3.4.0-030400-generic. The brightness control
works so-so there: exactly like it was with the previous out-of-the-box
kernel update 3.2.0-58. I. e. the brightness control works and the
dialog pops up
This is a NEW and BETTER patch created by Kieran Clancy on the kernel
bugzilla to do the same that my workaround did, but in a more proper
way, and from the kernel:
https://bugzilla.kernel.org/show_bug.cgi?id=44161#c149
I also tested it this weekend, and it works (I forced the issue to
Many thanks juanmanuel for identifying the cause for this long running
issue and for working diligently to find the fix.
You're welcome, it fills me with joy reading all this good feedback!!
--
Juan Manuel Cabo
http://zenstep.com.ar/samsung-linux
--
You received this bug notification because
You have been subscribed to a public bug:
I have an interesting issue with Ubuntu. I have a laptop that has one
jack for line in/microphone and line out/headphones.
This the reason why I bought a spliter like in the attached image.
Splits one 4 pines jack into two jacks: micrphone and line out
Public bug reported:
Possible duplicate.
ProblemType: KernelOops
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-12-generic 3.13.0-12.32
ProcVersionSignature: Ubuntu 3.13.0-12.32-generic 3.13.4
Uname: Linux 3.13.0-12-generic i686
Annotation: Your system might become unstable now and
** Tags removed: need-duplicate-check
--
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/1284154
Title:
BUG: soft lockup - CPU#0 stuck for 22s! [kswapd0:31]
Status in “linux” package in
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/1284154
Title:
BUG: soft lockup - CPU#0 stuck
This would better serve as a question because reporter directly asks for
a solution.
** Package changed: ubuntu = linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: New = Invalid
** Changed in: linux (Ubuntu)
Status: Invalid = New
** Changed in: linux (Ubuntu)
Status:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: kerneloops (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to kerneloops in Ubuntu.
This bug is awaiting verification that the 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-
precise' to 'verification-done-precise'.
If verification is not done by 5 working days
This bug is awaiting verification that the 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-
lucid' to 'verification-done-lucid'.
If verification is not done by 5 working days from
This bug is awaiting verification that the 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-
lucid' to 'verification-done-lucid'.
If verification is not done by 5 working days from
This bug is awaiting verification that the 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-
lucid' to 'verification-done-lucid'.
If verification is not done by 5 working days from
This bug is awaiting verification that the 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-
lucid' to 'verification-done-lucid'.
If verification is not done by 5 working days from
This bug is awaiting verification that the 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-
lucid' to 'verification-done-lucid'.
If verification is not done by 5 working days from
This bug is awaiting verification that the 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-
lucid' to 'verification-done-lucid'.
If verification is not done by 5 working days from
This bug is awaiting verification that the 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-
lucid' to 'verification-done-lucid'.
If verification is not done by 5 working days from
This bug is awaiting verification that the 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-
lucid' to 'verification-done-lucid'.
If verification is not done by 5 working days from
This bug is awaiting verification that the 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-
lucid' to 'verification-done-lucid'.
If verification is not done by 5 working days from
This bug is awaiting verification that the 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-
lucid' to 'verification-done-lucid'.
If verification is not done by 5 working days from
This bug is awaiting verification that the 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-
lucid' to 'verification-done-lucid'.
If verification is not done by 5 working days from
This bug is awaiting verification that the 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-
lucid' to 'verification-done-lucid'.
If verification is not done by 5 working days from
This bug is awaiting verification that the 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-
lucid' to 'verification-done-lucid'.
If verification is not done by 5 working days from
This bug is awaiting verification that the 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-
lucid' to 'verification-done-lucid'.
If verification is not done by 5 working days from
This bug is awaiting verification that the 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-
lucid' to 'verification-done-lucid'.
If verification is not done by 5 working days from
This bug is awaiting verification that the 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-
lucid' to 'verification-done-lucid'.
If verification is not done by 5 working days from
This bug is awaiting verification that the 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-
lucid' to 'verification-done-lucid'.
If verification is not done by 5 working days from
This bug is awaiting verification that the 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-
lucid' to 'verification-done-lucid'.
If verification is not done by 5 working days from
This bug is awaiting verification that the 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-
lucid' to 'verification-done-lucid'.
If verification is not done by 5 working days from
This bug is awaiting verification that the 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-
lucid' to 'verification-done-lucid'.
If verification is not done by 5 working days from
This bug is awaiting verification that the 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-
lucid' to 'verification-done-lucid'.
If verification is not done by 5 working days from
This bug is awaiting verification that the 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-
lucid' to 'verification-done-lucid'.
If verification is not done by 5 working days from
This bug is awaiting verification that the 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-
lucid' to 'verification-done-lucid'.
If verification is not done by 5 working days from
Bisect finished. The first bad commit is
786235eeba0e1e85e5cbbb9f97d1087ad03dfa21. It seem more likely as this
commit concerne kthread (and the first error is scsi4: error handler
thread failed to spawn, error = -12).
I also attach my bisect log if needed.
** Attachment added: bisect.log
This bug is awaiting verification that the 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-
lucid' to 'verification-done-lucid'.
If verification is not done by 5 working days from
This bug is awaiting verification that the 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-
quantal' to 'verification-done-quantal'.
If verification is not done by 5 working days
This bug is awaiting verification that the 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-
lucid' to 'verification-done-lucid'.
If verification is not done by 5 working days from
This bug is awaiting verification that the 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-
saucy' to 'verification-done-saucy'.
If verification is not done by 5 working days from
This bug is awaiting verification that the 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-
precise' to 'verification-done-precise'.
If verification is not done by 5 working days
This bug is awaiting verification that the 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-
lucid' to 'verification-done-lucid'.
If verification is not done by 5 working days from
This bug is awaiting verification that the 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-
lucid' to 'verification-done-lucid'.
If verification is not done by 5 working days from
This bug is awaiting verification that the 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-
lucid' to 'verification-done-lucid'.
If verification is not done by 5 working days from
This bug is awaiting verification that the 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-
lucid' to 'verification-done-lucid'.
If verification is not done by 5 working days from
This bug is awaiting verification that the 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-
lucid' to 'verification-done-lucid'.
If verification is not done by 5 working days from
This bug is awaiting verification that the 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-
lucid' to 'verification-done-lucid'.
If verification is not done by 5 working days from
This bug is awaiting verification that the 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-
saucy' to 'verification-done-saucy'.
If verification is not done by 5 working days from
This bug is awaiting verification that the 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-
precise' to 'verification-done-precise'.
If verification is not done by 5 working days
This bug is awaiting verification that the 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-
quantal' to 'verification-done-quantal'.
If verification is not done by 5 working days
This bug is awaiting verification that the 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-
lucid' to 'verification-done-lucid'.
If verification is not done by 5 working days from
This bug is awaiting verification that the 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-
quantal' to 'verification-done-quantal'.
If verification is not done by 5 working days
This bug is awaiting verification that the 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-
saucy' to 'verification-done-saucy'.
If verification is not done by 5 working days from
1 - 100 of 287 matches
Mail list logo
