>From linus' tree, posted there last week.
** Patch added: "elantech_v7.patch"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1166442/+attachment/3742049/+files/elantech_v7.patch
** Also affects: linux (Ubuntu Precise)
Importance: Undecided
Status: New
** Also affects: linux
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to b43-fwcutter in Ubuntu.
https://bugs.launchpad.net/bugs/1196988
Title:
package firmware-b43-installer 1:017-2 failed to install/upgrade:
ErrorMessag
** 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/1197492
Title:
package linux-image-3.8.0-25-generic (not installed) failed to
install/upgrade: subp
*** This bug is a duplicate of bug 1197309 ***
https://bugs.launchpad.net/bugs/1197309
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #1197309, so is being marked as such.
** 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/1198405
Title:
package linux-headers-3.8.0-26 3.8.0-26.38 failed to install/upgrade:
Neue Datei »/v
** 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/1197309
Title:
package linux-image-3.8.0-19-generic 3.8.0-19.29 failed to
install/upgrade: subproce
** 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/1196520
Title:
package linux-image-3.8.0-19-generic 3.8.0-19.29 failed to
install/upgrade: package
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to b43-fwcutter in Ubuntu.
https://bugs.launchpad.net/bugs/1197829
Title:
firmware-b43-installer 1:015-14 failed to install/upgrade
Status in “b43-fwcut
** 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/1200192
Title:
package linux-image-extra-3.8.0-26-generic (not installed) failed to
install/upgrade
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bcmwl in Ubuntu.
https://bugs.launchpad.net/bugs/1201220
Title:
bcmwl-kernel-source 6.20.155.1+bdcom-0ubuntu0.0.1: bcmwl kernel module
failed to bui
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to b43-fwcutter in Ubuntu.
https://bugs.launchpad.net/bugs/1201194
Title:
package firmware-b43-installer 1:015-9 failed to install/upgrade:
underproces
** 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/1198619
Title:
package linux-image-3.5.0-36-generic (not installed) failed to
install/upgrade: subp
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bcmwl in Ubuntu.
https://bugs.launchpad.net/bugs/1197586
Title:
bcmwl-kernel-source 6.20.155.1+bdcom-0ubuntu6 Error! Bad return status
for module bu
** 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/1202723
Title:
package linux-image-3.2.0-50-generic 3.2.0-50.76 failed to
install/upgrade: subproce
v3.11-rc1 tested, no change.
my BIOS is already ver. 214. On v3.11-rc1, key events are detected (KDE
popup) but the brightness does not change.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bu
Public bug reported:
Since the last update of Linux header, at each startup on my 64 bytes
machine with Precise 12.04, I've a message saying my display is not
recognized. The startup is bloked until I accept to continue in low
resolution.
Yesterday, I've updated my other pc, a 32 bytes also, with
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/1202905
Title:
Display configuration lost wit
Thanks Paolo booting with the image you linked and
http://people.canonical.com/~ppisati/linux-image-
extra-3.10.0-3-generic_3.10.0-3.13~lp1195687_amd64.deb all went fine as
expected... Awesome! ;-)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscri
Public bug reported:
Crash after resume
ProblemType: KernelOops
DistroRelease: Ubuntu 13.10
Package: linux-image-3.10.0-3-generic 3.10.0-3.12
ProcVersionSignature: Ubuntu 3.10.0-3.12-generic 3.10.1
Uname: Linux 3.10.0-3-generic i686
NonfreeKernelModules: wl
Annotation: This occured during a prev
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/1202883
Title:
[Acer Aspire 5734Z] late resum
@Ranier,
Thanks for your persistence in resolving these bugs.
I read through the history of in bug #1039143, and I agree with you that
one aspect of this problem is unique to USB3 ports. I forwarded the
discussion regarding this bug on the linux kernel mailing list to one of
the xhci_hcd authors.
Picture of the boot faillure on 3.11-rc1 without acpi=off.
** Attachment added: "3.11-rc1_boot_stuck.jpg"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1197451/+attachment/3741726/+files/3.11-rc1_boot_stuck.jpg
--
You received this bug notification because you are a member of Kernel
P
Tried to run apport-collect from within a chroot (after booting off of
the liveUSB again) and it segfaulted.
** 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 Ubu
3.11-rc1 is not better (installed on a dailly 13.10 chrooted) :(
With acpi=off, I still get thesame error as reported by Ma Jun in #7
Without acpi=off, the boot get stuck at "smpboot: Booting Node0, Processors
#1" (No error message but it is stuck).
--
You received this bug notification beca
This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:
apport-collect 1202862
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a commen
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/1202863
Title:
[Hewlett-Packard Compaq Presar
Just to clarify that I don't have this laptop - I only helped triaging
this bug. Thanks.
--
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/1191334
Title:
045e:0745 A wrong hardware detectio
Public bug reported:
I don't know
ProblemType: KernelOops
DistroRelease: Ubuntu 13.04
Package: linux-image-3.8.0-7-generic 3.8.0-7.14
ProcVersionSignature: Ubuntu 3.8.0-7.14-generic 3.8.0
Uname: Linux 3.8.0-7-generic i686
Annotation: This occured during a previous suspend and prevented it from
r
Public bug reported:
A fresh install of the nightly build of Saucy on my Eee PC 1215B
successfully starts up grub, but grub hangs on a blank console screen
with "GRUB" in the top left corner, with a flashing cursor after.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
Hi!
I finally came around to updating the kernel. Tested with the 12.04 LTS
version / 3.2 kernel. Unfortunately mij RAID system won't boot on this
3.2 kernel. Had to fall back to the original 2.6 kernel. Problem.
however, still remains. Any activity on this bug?
Regards, Menno
--
You received t
** Tags added: kernel-bug-exists-upstream
** 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/1201092
Title:
Cannot load
The issue is that I'm so far not able to boot from 13.10 after the installation
(the image on the usb key boots most of the time with acpi=0).
I'm stuck with the same error as reported by Ma Jun in #7
I'm going to try chroot to install 3.11-rc1 from the usbkey.
If you have a simpler way to get a
Max, Phillip already explained that we can't help you here with your
problem. This bug specifically regards a flaw in how the kernel was
writing NVRAM variables for UEFI boot loaders. It is unrelated to GRUB.
You will need to file a new bug for the problem you're having.
--
You received this bug
Tested with latest upstream kernel: the problem is still there.
# uname -a
Linux yasna 3.11.0-031100rc1-generic #201307141935 SMP Sun Jul 14 23:36:57 UTC
2013 x86_64 x86_64 x86_64 GNU/Linux
#
# kvm-ok
INFO: /dev/kvm does not exist
HINT: sudo modprobe kvm_amd
INFO: Your CPU supports KVM extensi
** Changed in: debian
Status: New => Fix Committed
--
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/1102343
Title:
Missing MBIM (Mobile Broadband Interface Model) support
Status in
This still doesn't work for me. After installing grub starts after a
restart, but freezes on a blank console screen with "GRUB" in the upper
left corner, with a flashing cursor after it.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linu
** 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/1124333
Title:
[. .] suspend/resume failure
Status in “linux” pack
There have been a number of kernel updates since the one you reported this
bug against. Please test again with the newer kernel and indicate in the
bug if you are still not able to suspend/resume.
You can update to the latest kernel by simply running the following commands in
a terminal window:
** Description changed:
SRU Justification:
Impact:
Users of the 3.5/3.8 kernel will have poor network throughput when using
OpenStack Neutron depending on their setup.
Fix:
These patches are all in Ubuntu-3.9.0-7.15 / v3.9-rc1:
2681128f0ced8aa4e66f221197e183cc16d244fe
8093315a
I have a completely up-to-date Raring (Kernel 3.8.0-27-generic) and the
problem still persists.
--
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/1162737
Title:
[LENOVO 7417CTO] Wakes up fr
There have been a number of kernel updates since the one you reported this
bug against. Please test again with the newer kernel and indicate in the
bug if you are still not able to suspend/resume.
You can update to the latest kernel by simply running the following commands in
a terminal window:
There have been a number of kernel updates since the one you reported this
bug against. Please test again with the newer kernel and indicate in the
bug if you are still not able to suspend/resume.
You can update to the latest kernel by simply running the following commands in
a terminal window:
There have been a number of kernel updates since the one you reported this
bug against. Please test again with the newer kernel and indicate in the
bug if you are still not able to suspend/resume.
You can update to the latest kernel by simply running the following commands in
a terminal window:
However, given that TLP made it worse, could it be that some power
management setting is doing something funky with the system cache as
indicated with the hdparm -T result?
What I don't know and can't find to how to see what state the cache or
memory are in.
--
You received this bug notification
There have been a number of kernel updates since the one you reported this
bug against. Please test again with the newer kernel and indicate in the
bug if you are still not able to suspend/resume.
You can update to the latest kernel by simply running the following commands in
a terminal window:
There have been a number of kernel updates since the one you reported this
bug against. Please test again with the newer kernel and indicate in the
bug if you are still not able to suspend/resume.
You can update to the latest kernel by simply running the following commands in
a terminal window:
It seems the TLP was not the main cause after all. I've purged TLP from
the system, rebooted multiple times, and the issue still appears, just
not as quickly.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.la
** No longer affects: tlp (Ubuntu)
** Summary changed:
- TLP causing lag under desktop environments
+ 13.04, lag under desktop environments
--
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
I didn't suspend the computer, i shut the lid and it was meant to do
nothing
On Fri, Jul 19, 2013 at 4:46 AM, Joseph Salisbury
wrote:
> Did you battery die while the system was suspended? Also, do you get
> this every time you resume from suspend.
>
> --
> You received this bug notification beca
OK - checked as you asked. I'm currently running kernel
3.10.0-3-generic, and the behavior is exactly as before - "sudo pm-
suspend" puts the machine into suspend state, but attempting to resume
(enter, mouse,...) causes a reboot. The pm-suspend.log file ends at
"performing suspend"; there are no e
There have been a number of kernel updates since the one you reported this
bug against. Please test again with the newer kernel and indicate in the
bug if you are still not able to suspend/resume.
You can update to the latest kernel by simply running the following commands in
a terminal window:
There have been a number of kernel updates since the one you reported this
bug against. Please test again with the newer kernel and indicate in the
bug if you are still not able to suspend/resume.
You can update to the latest kernel by simply running the following commands in
a terminal window:
There have been a number of kernel updates since the one you reported this
bug against. Please test again with the newer kernel and indicate in the
bug if you are still not able to suspend/resume.
You can update to the latest kernel by simply running the following commands in
a terminal window:
There have been a number of kernel updates since the one you reported this
bug against. Please test again with the newer kernel and indicate in the
bug if you are still not able to suspend/resume.
You can update to the latest kernel by simply running the following commands in
a terminal window:
There have been a number of kernel updates since the one you reported this
bug against. Please test again with the newer kernel and indicate in the
bug if you are still not able to suspend/resume.
You can update to the latest kernel by simply running the following commands in
a terminal window:
There have been a number of kernel updates since the one you reported this
bug against. Please test again with the newer kernel and indicate in the
bug if you are still not able to suspend/resume.
You can update to the latest kernel by simply running the following commands in
a terminal window:
There have been a number of kernel updates since the one you reported this
bug against. Please test again with the newer kernel and indicate in the
bug if you are still not able to suspend/resume.
You can update to the latest kernel by simply running the following commands in
a terminal window:
I built the next test kernel, up to the following commit:
608ff1a210ab0e8b969399039bf8e18693605910
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1144322
Can you test that kernel and report back if it has the bug or not. I
will build the next test kernel based on y
There have been a number of kernel updates since the one you reported this
bug against. Please test again with the newer kernel and indicate in the
bug if this issue still exists or not.
You can update to the latest development kernel by simply running the following
commands in
a terminal window:
There have been a number of kernel updates since the one you reported this
bug against. Please test again with the newer kernel and indicate in the
bug if this issue still exists or not.
You can update to the latest development kernel by simply running the following
commands in
a terminal window:
There have been a number of kernel updates since the one you reported this
bug against. Please test again with the newer kernel and indicate in the
bug if this issue still exists or not.
You can update to the latest development kernel by simply running the following
commands in
a terminal window:
There have been a number of kernel updates since the one you reported this
bug against. Please test again with the newer kernel and indicate in the
bug if this issue still exists or not.
You can update to the latest development kernel by simply running the following
commands in
a terminal window:
There have been a number of kernel updates since the one you reported this
bug against. Please test again with the newer kernel and indicate in the
bug if this issue still exists or not.
You can update to the latest development kernel by simply running the following
commands in
a terminal window:
There have been a number of kernel updates since the one you reported this
bug against. Please test again with the newer kernel and indicate in the
bug if this issue still exists or not.
You can update to the latest development kernel by simply running the following
commands in
a terminal window:
Did you battery die while the system was suspended? Also, do you get
this every time you resume from suspend.
--
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/1198755
Title:
[Dell Inc. Vo
There have been a number of kernel updates since the one you reported this
bug against. Please test again with the newer kernel and indicate in the
bug if this issue still exists or not.
You can update to the latest development kernel by simply running the following
commands in
a terminal window:
There have been a number of kernel updates since the one you reported this
bug against. Please test again with the newer kernel and indicate in the
bug if this issue still exists or not.
You can update to the latest development kernel by simply running the following
commands in
a terminal window:
There have been a number of kernel updates since the one you reported this
bug against. Please test again with the newer kernel and indicate in the
bug if this issue still exists or not.
You can update to the latest development kernel by simply running the following
commands in
a terminal window:
There have been a number of kernel updates since the one you reported this
bug against. Please test again with the newer kernel and indicate in the
bug if this issue still exists or not.
You can update to the latest development kernel by simply running the following
commands in
a terminal window:
There have been a number of kernel updates since the one you reported this
bug against. Please test again with the newer kernel and indicate in the
bug if this issue still exists or not.
You can update to the latest development kernel by simply running the following
commands in
a terminal window:
There have been a number of kernel updates since the one you reported this
bug against. Please test again with the newer kernel and indicate in the
bug if this issue still exists or not.
You can update to the latest development kernel by simply running the following
commands in
a terminal window:
** Changed in: debian
Status: New => 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/1183777
Title:
Possible missing firmware /lib/firmware/radeon in mainlin
This issue appears to be an upstream bug, since you tested the latest
upstream kernel. Would it be possible for you to open an upstream bug
report[0]? That will allow the upstream Developers to examine the issue,
and may provide a quicker resolution to the bug.
Please follow the instructions on th
The 3.11-rc1 kernel is now available. Can you test this kernel and post back
if it exhibits this bug?
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.11-rc1-saucy/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https:
** Changed in: linux (Ubuntu Saucy)
Status: In Progress => Fix Committed
--
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/1200243
Title:
Network lock up Windows Azure/Hyper-V
Statu
I am not sure what or how it happened but after a reboot I had to go to
recovery mode after REISUB and now my graphics driver is VESA: Intel®
Sandybridge/Ivybridge Graphics and apport says Xorg crashed per bug [Bug
1202763] [NEW] Xorg crashed with SIGABRT in raise() I don't know if
these 2 issues a
@Jonathan, Can you confirm if you are still seeing this bug or not?
** 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/109
There have been a number of kernel updates since the one you reported this
bug against. Please test again with the newer kernel and indicate in the
bug if this issue still exists or not.
You can update to the latest development kernel by simply running the following
commands in
a terminal window:
There have been a number of kernel updates since the one you reported this
bug against. Please test again with the newer kernel and indicate in the
bug if this issue still exists or not.
You can update to the latest development kernel by simply running the following
commands in
a terminal window:
There have been a number of kernel updates since the one you reported this
bug against. Please test again with the newer kernel and indicate in the
bug if this issue still exists or not.
You can update to the latest development kernel by simply running the following
commands in
a terminal window:
** Changed in: linux (Ubuntu)
Importance: Undecided => Low
** 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/1202723
T
Exactly :-)
Sent from mobile נשלח מנייד
On Jul 18, 2013 3:41 PM, "oliver" wrote:
> Chris, I think Shahar's idea is to submit the patch and hopefully gets
> merged so that regular users don't have to remove anything to get
> everything working.
>
> But yeah, why not, submit a patch and see what h
There have been a number of kernel updates since the one you reported this
bug against. Please test again with the newer kernel and indicate in the
bug if this issue still exists or not.
You can update to the latest development kernel by simply running the following
commands in
a terminal window:
There have been a number of kernel updates since the one you reported this
bug against. Please test again with the newer kernel and indicate in the
bug if this issue still exists or not.
You can update to the latest development kernel by simply running the following
commands in
a terminal window:
There have been a number of kernel updates since the one you reported this
bug against. Please test again with the newer kernel and indicate in the
bug if this issue still exists or not.
You can update to the latest development kernel by simply running the following
commands in
a terminal window:
There have been a number of kernel updates since the one you reported this
bug against. Please test again with the newer kernel and indicate in the
bug if this issue still exists or not.
You can update to the latest development kernel by simply running the following
commands in
a terminal window:
I built a test kernel with the patch. It can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1200570/
Can you test that kernel and post back if it has this bug or not. Note,
you will need to install both the linux-image and linux-image-extra .deb
packages.
Thanks in advance!
--
You
Confirmed the latest test kernel fixes the problem.
--
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/1200243
Title:
Network lock up Windows Azure/Hyper-V
Status in “linux” package in Ubun
There have been a number of kernel updates since the one you reported this
bug against. Please test again with the newer kernel and indicate in the
bug if this issue still exists or not.
You can update to the latest development kernel by simply running the following
commands in
a terminal window:
There have been a number of kernel updates since the one you reported this
bug against. Please test again with the newer kernel and indicate in the
bug if this issue still exists or not.
You can update to the latest development kernel by simply running the following
commands in
a terminal window:
I have this on Raring.
$ uname -a
Linux 3.8.0-27-generic #40-Ubuntu SMP Tue Jul 9 00:19:35 UTC
2013 i686 athlon i686 GNU/Linux
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
I'll build a Saucy test kernel with that patch and post a link to it
shortly.
** Changed in: linux (Ubuntu Saucy)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
** Changed in: linux (Ubuntu Saucy)
Status: Triaged => In Progress
--
You received this bug notification because
There have been a number of kernel updates since the one you reported this
bug against. Please test again with the newer kernel and indicate in the
bug if this issue still exists or not.
You can update to the latest development kernel by simply running the following
commands in
a terminal window:
There have been a number of kernel updates since the one you reported this
bug against. Please test again with the newer kernel and indicate in the
bug if this issue still exists or not.
You can update to the latest development kernel by simply running the following
commands in
a terminal window:
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v3.11 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix t
Thanks Brad, could have changed the status much earlier though.. Sorry
for that!
** 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.launchp
** Also affects: linux (Ubuntu Saucy)
Importance: High
Status: Confirmed
** Changed in: linux (Ubuntu Saucy)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launc
Public bug reported:
idk
ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: linux-image-3.2.0-50-generic 3.2.0-50.76
ProcVersionSignature: Ubuntu 2.6.32-47.109-generic 2.6.32.60+drm33.26
Uname: Linux 2.6.32-47-generic x86_64
NonfreeKernelModules: wl nvidia
ApportVersion: 2.0.1-0ubuntu17.4
The v3.11-rc1 kernel is now available. Can you test that kernel to see if the
fix made it into mainline yet:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.11-rc1-saucy/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
There have been a number of kernel updates since the one you reported this
bug against. Please test again with the newer kernel and indicate in the
bug if this issue still exists or not.
You can update to the latest development kernel by simply running the following
commands in
a terminal window:
1 - 100 of 200 matches
Mail list logo
