** Tags added: raring
** Description changed:
- I have a Acer Aspire 7740, and noticed after installing that Ubuntu 13.10
(kernel 3.11.0-14) hangs for 10 seconds early in the boot process. It continues
after that.
+ When I received this laptop I installed a new half size mini PCIE wireless
** Description changed:
- The apic_get_tmcct function in arch/x86/kvm/lapic.c in the KVM subsystem
- in the Linux kernel through 3.12.5 allows guest OS users to cause a
- denial of service (divide-by-zero error and host OS crash) via crafted
- modifications of the TMICT value.
+ kvm: division by
** Description changed:
- kvm: cross page vapic_addr access
+ The KVM subsystem in the Linux kernel through 3.12.5 allows local users
+ to gain privileges or cause a denial of service (system crash) via a
+ VAPIC synchronization operation involving a page-end address.
+
+ Break-Fix: -
You have been subscribed to a public bug:
I'm using a freshly installed Ubuntu 13.10.
As soon as I click on a different user I want to switch to in the gearbox menu
I get a black screen and nothing else is happening. I'm still able to SSH to
that box and top does not show any process taking
Adam Niedling, thank you for reporting this bug and helping make Ubuntu
better. This bug was reported a while ago and there hasn't been any
activity in it recently. We were wondering if this is still an issue? If
so, could you please test for this with the latest development release
of Ubuntu? ISO
Christopher Penalver, the bug can be closed. Thanks.
Andy
--
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/1259634
Title:
1969:1091 [Gigabyte Z77X-D3H] Atheros AR8161 Gigabit Ethernet
Andy Esten, this bug report is being closed due to your last comment
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1259634/comments/9
regarding this being fixed with an update. For future reference you can
manage the status of your own bugs by clicking on the current status in
the yellow
dumpa, as per http://download.lenovo.com/express/ddfm.html an update is
available for your BIOS (1.63). If you update to this following
https://help.ubuntu.com/community/BiosUpdate , does it change anything? If it
doesn't, could you please both specify what happened, and just provide the
I cannot use the Alpha1 of Trusty from
https://wiki.ubuntu.com/TrustyTahr/Alpha1/Kubuntu booting the CD gives
only a black screen.
I reinstalled from scratch a 13.10 version formatting the / partition.
The network management plasmoid on status bar shows an unreachable
network; but trying to
The situation is much worse now, as the system does not boot at all. It
hangs at the moment when it recognizes the two disks. Before one of the
disks was ignored but the system could boot.
So, I'm afraid I can not add debug data unless you let me know what is
the information you need and how I
Peter de Kraker, thank you for performing the requested test and the
follow up information. I briefly scanned acer-wmi and didn't see
anything patently obvious code wise as to why this would occur with a
non-OEM provided WiFi chip (although I'm not terribly familiar with it).
Cursorily, the BIOS
** Description changed:
- My computer hangs when booting because of a irq conflict.
- I have a PCI adapter for SATA drives with sata and usb ports with VT6421
chipset.
- When I put only one HD then the system is OK.
- When I boot up with two HD in the sata ports the system behaves badly. Most
Oltion Kola, thank you for your comments. Just to confirm, you attempted
to boot into the live environment of Trusty, and the mainline kernel
v3.13-rc3, and neither allowed you to boot with both disks attached?
--
You received this bug notification because you are a member of Kernel
Packages,
Tested with the latest build. The problem was present in all kernels I
have tested in these 3 years.
--
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/570434
Title:
[Dell Dimension 2400]
Are you being serious? It was reported 1,5 months ago. Last activity was
16 days ago. Do you want me to test the upstream kernel daily or what?
This bug affect the latest stable version of Ubuntu and it is still a
bug.
What makes you think this is a kernel bug anyway? It is not happening if
the
** Changed in: linux-lts-backport-maverick (Ubuntu Lucid)
Status: New = Won't Fix
** Changed in: linux-lts-backport-natty (Ubuntu Lucid)
Status: New = Won't Fix
** Changed in: linux-lts-backport-maverick (Ubuntu Precise)
Status: New = Won't Fix
** Changed in:
@ Brad done the Command and sent ya the info resently not even 3 mins
after i sent this comment hope it helps =)
--
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/1255309
Title:
Kernel
apport information
** Tags added: apport-collected
** Description changed:
On Ubuntu 14.04 LTS kernel 3.12.0-3 does not run Kernel 3.12.0-4 at
bootup when i Tryed to get in the Grub it wont run the Grub eather i
done installed the Lastest Kernel it just wont run it at all... Heres a
** Changed in: linux-lts-backport-maverick (Ubuntu Lucid)
Status: New = Won't Fix
** Changed in: linux-lts-backport-natty (Ubuntu Lucid)
Status: New = Won't Fix
** Changed in: linux-lts-backport-maverick (Ubuntu Precise)
Status: New = Won't Fix
** Changed in:
** Changed in: linux-lts-backport-maverick (Ubuntu Lucid)
Status: New = Won't Fix
** Changed in: linux-lts-backport-natty (Ubuntu Lucid)
Status: New = Won't Fix
** Changed in: linux-lts-backport-maverick (Ubuntu Precise)
Status: New = Won't Fix
** Changed in:
I've updated the BIOS without any changes regarding bluetooth.
The output of sudo dmidecode -s bios-version sudo dmidecode -s
bios-release-date is:
HEET36WW (1.17 )
10/14/2013
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
** Changed in: linux-lts-backport-maverick (Ubuntu Lucid)
Status: New = Won't Fix
** Changed in: linux-lts-backport-natty (Ubuntu Lucid)
Status: New = Won't Fix
** Changed in: linux-lts-backport-maverick (Ubuntu Precise)
Status: New = Won't Fix
** Changed in:
** Changed in: linux-lts-backport-maverick (Ubuntu Lucid)
Status: New = Won't Fix
** Changed in: linux-lts-backport-natty (Ubuntu Lucid)
Status: New = Won't Fix
** Changed in: linux-lts-backport-maverick (Ubuntu Precise)
Status: New = Won't Fix
** Changed in:
** Changed in: linux-lts-backport-maverick (Ubuntu Lucid)
Status: New = Won't Fix
** Changed in: linux-lts-backport-natty (Ubuntu Lucid)
Status: New = Won't Fix
** Changed in: linux-lts-backport-maverick (Ubuntu Precise)
Status: New = Won't Fix
** Changed in:
** Changed in: linux-lts-backport-maverick (Ubuntu Lucid)
Status: New = Won't Fix
** Changed in: linux-lts-backport-natty (Ubuntu Lucid)
Status: New = Won't Fix
** Changed in: linux-lts-backport-maverick (Ubuntu Precise)
Status: New = Won't Fix
** Changed in:
Public bug reported:
I have a Dell Sputnik 3 that I just got and upgraded it to
12.10-13.04-13.10. On boot the kernel crashes with a BUG. I can
prevent the crash by blacklisting the iwlwifi module and I can cause the
BUG by manually loading the module. I will attach a dmesg output from
after the
** Changed in: linux-lts-backport-maverick (Ubuntu Lucid)
Status: New = Won't Fix
** Changed in: linux-lts-backport-natty (Ubuntu Lucid)
Status: New = Won't Fix
** Changed in: linux-lts-backport-maverick (Ubuntu Precise)
Status: New = Won't Fix
** Changed in:
** Changed in: linux-lts-backport-maverick (Ubuntu Lucid)
Status: New = Won't Fix
** Changed in: linux-lts-backport-natty (Ubuntu Lucid)
Status: New = Won't Fix
** Changed in: linux-lts-backport-maverick (Ubuntu Precise)
Status: New = Won't Fix
** Changed in:
This bug is missing log files that will aid in diagnosing the problem.
From a terminal window please run:
apport-collect 1263219
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
emildicule...@gmail.com, thank you for updating your BIOS. Could you
please confirm this issue exists with the latest development release of
Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-
live/current/ . If the issue remains, could you please just make a
comment to this?
** Changed in: linux-lts-backport-maverick (Ubuntu Lucid)
Status: New = Won't Fix
** Changed in: linux-lts-backport-natty (Ubuntu Lucid)
Status: New = Won't Fix
** Changed in: linux-lts-backport-maverick (Ubuntu Precise)
Status: New = Won't Fix
** Changed in:
** Changed in: linux-lts-backport-maverick (Ubuntu Lucid)
Status: New = Won't Fix
** Changed in: linux-lts-backport-natty (Ubuntu Lucid)
Status: New = Won't Fix
** Changed in: linux-lts-backport-maverick (Ubuntu Precise)
Status: New = Won't Fix
** Changed in:
Here is the dmesg output.
This info is a little tricky to collect since I can't bring up my
network (or shutdown my computer normally) after the BUG occurs. I have
to boot into a 13.04 kernel to actually post this info. :) Does the
apport store the output locally somewhere that will survive a
** Changed in: linux-lts-backport-maverick (Ubuntu Lucid)
Status: New = Won't Fix
** Changed in: linux-lts-backport-natty (Ubuntu Lucid)
Status: New = Won't Fix
** Changed in: linux-lts-backport-maverick (Ubuntu Precise)
Status: New = Won't Fix
** Changed in:
** Changed in: linux-lts-backport-maverick (Ubuntu Lucid)
Status: New = Won't Fix
** Changed in: linux-lts-backport-natty (Ubuntu Lucid)
Status: New = Won't Fix
** Changed in: linux-lts-backport-maverick (Ubuntu Precise)
Status: New = Won't Fix
** Changed in:
** Changed in: linux-lts-backport-maverick (Ubuntu Lucid)
Status: New = Won't Fix
** Changed in: linux-lts-backport-natty (Ubuntu Lucid)
Status: New = Won't Fix
** Changed in: linux-lts-backport-maverick (Ubuntu Precise)
Status: New = Won't Fix
** Changed in:
** Changed in: linux-lts-backport-maverick (Ubuntu Lucid)
Status: New = Won't Fix
** Changed in: linux-lts-backport-natty (Ubuntu Lucid)
Status: New = Won't Fix
** Changed in: linux-lts-backport-maverick (Ubuntu Precise)
Status: New = Won't Fix
** Changed in:
** Changed in: linux-lts-backport-maverick (Ubuntu Lucid)
Status: New = Won't Fix
** Changed in: linux-lts-backport-natty (Ubuntu Lucid)
Status: New = Won't Fix
** Changed in: linux-lts-backport-maverick (Ubuntu Precise)
Status: New = Won't Fix
** Changed in:
Hi,
Yep, issue still exists in daily ISO and in
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.13-rc3-trusty/
In both cases, suspend seems to work fine, but then computer doesn't wake up -
have to do hard reboot.
--
You received this bug notification because you are a member of Kernel
** Changed in: linux-lts-backport-maverick (Ubuntu Lucid)
Status: New = Won't Fix
** Changed in: linux-lts-backport-natty (Ubuntu Lucid)
Status: New = Won't Fix
** Changed in: linux-lts-backport-maverick (Ubuntu Precise)
Status: New = Won't Fix
** Changed in:
** Changed in: linux-lts-backport-maverick (Ubuntu Lucid)
Status: New = Won't Fix
** Changed in: linux-lts-backport-natty (Ubuntu Lucid)
Status: New = Won't Fix
** Changed in: linux-lts-backport-maverick (Ubuntu Precise)
Status: New = Won't Fix
** Changed in:
** Changed in: linux-lts-backport-maverick (Ubuntu Lucid)
Status: New = Won't Fix
** Changed in: linux-lts-backport-natty (Ubuntu Lucid)
Status: New = Won't Fix
** Changed in: linux-lts-backport-maverick (Ubuntu Precise)
Status: New = Won't Fix
** Changed in:
** Changed in: linux-lts-backport-maverick (Ubuntu Lucid)
Status: New = Won't Fix
** Changed in: linux-lts-backport-natty (Ubuntu Lucid)
Status: New = Won't Fix
** Changed in: linux-lts-backport-maverick (Ubuntu Precise)
Status: New = Won't Fix
** Changed in:
** Changed in: linux-lts-backport-maverick (Ubuntu Lucid)
Status: New = Won't Fix
** Changed in: linux-lts-backport-natty (Ubuntu Lucid)
Status: New = Won't Fix
** Changed in: linux-lts-backport-maverick (Ubuntu Precise)
Status: New = Won't Fix
** Changed in:
** Tags removed: kernel-bug-exists-upstream-v3.11-rc5 needs-upstream-testing
** Tags added: kernel-bug-exists-upstream-v3.13-rc3
--
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/1175504
** Changed in: linux-lts-backport-maverick (Ubuntu Lucid)
Status: New = Won't Fix
** Changed in: linux-lts-backport-natty (Ubuntu Lucid)
Status: New = Won't Fix
** Changed in: linux-lts-backport-maverick (Ubuntu Precise)
Status: New = Won't Fix
** Changed in:
I still have the issue, update after update since 3.2.0-45 on my Lenovo
L520
--
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/896922
Title:
Lenovo L520 - psmouse.c: touchpad at
found some info on effectings of Kernel 3.12 and 3.13 tag of report
below
https://bugs.launchpad.net/ubuntu/+source/fglrx-installer-
updates/+bug/1259467
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Changed in: linux-lts-backport-maverick (Ubuntu Lucid)
Status: New = Won't Fix
** Changed in: linux-lts-backport-natty (Ubuntu Lucid)
Status: New = Won't Fix
** Changed in: linux-lts-backport-maverick (Ubuntu Precise)
Status: New = Won't Fix
** Changed in:
** Changed in: linux-lts-backport-maverick (Ubuntu Lucid)
Status: New = Won't Fix
** Changed in: linux-lts-backport-natty (Ubuntu Lucid)
Status: New = Won't Fix
** Changed in: linux-lts-backport-maverick (Ubuntu Precise)
Status: New = Won't Fix
** Changed in:
** Changed in: linux-lts-backport-maverick (Ubuntu Lucid)
Status: New = Won't Fix
** Changed in: linux-lts-backport-natty (Ubuntu Lucid)
Status: New = Won't Fix
** Changed in: linux-lts-backport-maverick (Ubuntu Precise)
Status: New = Won't Fix
** Changed in:
** Changed in: linux-lts-backport-maverick (Ubuntu Lucid)
Status: New = Won't Fix
** Changed in: linux-lts-backport-natty (Ubuntu Lucid)
Status: New = Won't Fix
** Changed in: linux-lts-backport-maverick (Ubuntu Precise)
Status: New = Won't Fix
** Changed in:
Unfortunately whilst I get the screen up on boot, the first time the
screen is blanked either by power management, or switching a VT or
standby(closing lid) - I loose the screen and need to do a reboot to
get it back. Not very useful unfortunately.
I have tried a couple of different 3.12 kernels
I too can confirm this problem on two different installations of Ubuntu
13.10.
lsusb -vd 14cd:6116
...
idVendor 0x14cd Super Top
idProduct 0x6116 M6116 SATA Bridge
bcdDevice1.50
...
bmAttributes 0xc0
Self Powered
MaxPower
Tobiasz Jarczyk, the issue you are reporting is an upstream one. Could
you please report this problem through the appropriate channel (would
start with linux-pm) by following the instructions _verbatim_ at
Christopher M. Penalver, I had the same problem, and now it works for me, after
installing fglrx-experimental-12.
My BIOS is the old 2.52. I am currently writing on this machine, it has just
resumed from suspend as expected.
In my opinion, the bug can be closed.
--
You received this bug
klamm2001, so your hardware may be tracked, could you please file a new report
by executing the following in a terminal while booted into a Ubuntu repository
kernel (not a mainline one) via:
ubuntu-bug linux
For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v3.13 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
I'm surprised this is being debated. Look at Google:
https://www.google.com.au/search?q=linux+high+io+desktopoq=linux+high+aqs=chrome.0.69i59j69i57j69i64l2.1936j0j1sourceid=chromeie=UTF-8
You will clearly see that high enough IO will harm desktop responsiveness.
Surely all of these people aren't
** Description changed:
- kvm: BUG_ON() in apic_cluster_id()
+ The recalculate_apic_map function in arch/x86/kvm/lapic.c in the KVM
+ subsystem in the Linux kernel through 3.12.5 allows guest OS users to
+ cause a denial of service (host OS crash) via a crafted ICR write
+ operation in x2apic
** 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/1263219
Title:
kernel panics with BUG
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/1036102
Title:
Card reader not working on
I have absolutely no desire to mess with my BIOS, but that doesn't
change the fact that this bug exists.
** Changed in: linux (Ubuntu)
Status: Expired = New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Julien Olivier, could you please confirm this issue exists with the
latest development release of Ubuntu? ISO images are available from
http://cdimage.ubuntu.com/daily-live/current/ . If the issue remains,
could you please just make a comment to this?
** Changed in: linux (Ubuntu)
Importance:
** Package changed: linux (Ubuntu) = linuxmint
** Changed in: linuxmint
Status: Confirmed = 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/1177427
Title:
multiple scancodes
Tonal, this bug was reported a while ago and there hasn't been any
activity in it recently. We were wondering if this is still an issue? If
so, could you please test for this with the latest development release
of Ubuntu? ISO images are available from http://cdimage.ubuntu.com
/daily-live/current/
Rohan Garg, this bug was reported a while ago and there hasn't been any
activity in it recently. We were wondering if this is still an issue? If
so, could you please test for this with the latest development release
of Ubuntu? ISO images are available from http://cdimage.ubuntu.com
Tested it in the same way on Precise as described in comment 9, same results..
Again - tailing kern.log:
Dec 20 23:50:17 wyvern kernel: [ 108.890147] EXT4-fs (sda5): recovery complete
Dec 20 23:50:17 wyvern kernel: [ 108.892446] EXT4-fs (sda5): mounted
filesystem with ordered data mode. Opts:
The bug still exists in the latest kernel (3.13.0-031300rc3-generic)
** Changed in: linux (Ubuntu)
Status: Expired = Confirmed
** Tags removed: kernel-bug-exists-upstream-v3.11.rc4 kernel-request-3.11.0-7.14
** Tags added: kernel-bug-exists-upstream-v3.13.0-031300rc3-generic
--
You
** Tags removed: kernel-bug-exists-upstream-v3.13.0-031300rc3-generic
needs-upstream-testing
** Tags added: kernel-bug-exists-upstream-v3.13-rc3
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Allan Crooks, thank you for performing the requested test. For
regression testing purposes, would you mind testing a far earlier kernel
series (3.2.x) following
https://wiki.ubuntu.com/Kernel/KernelBisection#Bisecting_Ubuntu_kernel_versions
?
** Tags added: raring
--
You received this bug
Ari Fogel, the issue you are reporting is an upstream one. Could you
please report this problem through the appropriate channel (would check
in with linux-input) by following the instructions _verbatim_ at
I am not using any nvidia hardware and I have this exact same issue. I
believe the bug is within lightdm.
** 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
Rob Tongue, the computer freezing would indicate either an x crash, or kernel
call trace, which are both treated under separate reports based on differing
hardware. Hence, so your hardware may be tracked, could you please file a new
report by executing the following in a terminal while booted
apport information
** Description changed:
fs goes into read-only mode while build lo
$ dmesg
...
[ 2045.473249] virbr0: port 1(vnet0) entered forwarding state
[ 2045.473283] IPv6: ADDRCONF(NETDEV_CHANGE): virbr0: link becomes ready
[10660.961381] perf samples too long (2505
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I dont see these error message with 3.12 kernel, or if I boot with ncq
disabled.
$ echo 1 /sys/block/sda/device/queue_depth
Additionally, fstrim seems to return the same upon reboot
first run
# fstrim -v /
/: 920118112256 bytes were trimmed
second run ( after reboot )
/: 920175951872 bytes
It looks like this bug was fixed upstream. Recent kernels don't have 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/1237204
Title:
Microsoft Natural Keyboard not recognized
Tried that one. Results are completely same.
--
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/1260214
Title:
8086:0166 [ASUS TAICHI 21] External screen doesn't work.
Status in “linux”
I've tested with latest Ubuntu, still not working. To sum up, with 3.11
or 3.12 kernels the bluetooth can be turned on and off and its
visibility can be changed but it doesn't detect any other device nor can
be detected. With 3.13 kernels the device doesn't show in the
application (all menus
Rob, don't listen to him. I got into an argument with him at bug #131094
and now he's here on a personal vendetta. He's just gonna keep asking
for irrelevant information until it gets so difficult to answer that he
can close this bug.
Christopher, I don't recognize your authority, leave this bug
Now Christopher is onto me. He started vandalizing another of my bug
reports. Bug #1247189.
--
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/131094
Title:
Heavy Disk I/O harms desktop
** Package changed: linux (Ubuntu) = plasma-widget-networkmanagement
** Changed in: plasma-widget-networkmanagement
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Hi, Christopher
I've just tested kernel 3.13-rc3, bug still present.
I repeated the same test in other computers I own (intel based), with
mixed results: one with a Gigabyte GA-G31MF-S2 motherboard (intel G31
chipset, socket 775) is affected by this bug. Another one with an ASUS
socket 775
*** This bug is a duplicate of bug 1215098 ***
https://bugs.launchpad.net/bugs/1215098
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Kernel
101 - 190 of 190 matches
Mail list logo
