Thanks for responding me.
I appreciate it.
I have reinstalled the ubuntu 14.10 LTS with GNOME.
It is working fine now.
On Fri, Dec 19, 2014 at 8:50 PM, Jamie Strandboge
wrote:
> ** Information type changed from Private Security to Public
>
> --
> You received this bug notification because you ar
It seems it works with Kubuntu 14.04 and Kernel 3.16 (Utopic) on a TP
X200.
--
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/451282
Title:
display is fully dimmed after resume from suspend
Aline Freitas, this bug report is being closed due to your last comment
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1401748/comments/7
regarding this being fixed with a BIOS update. For future reference you
can manage the status of your own bugs by clicking on the current status
in the yel
[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.
https://bugs.launchpad.net/bu
As HP only releases their BIOS firmware update for my model in 64bits
Windows-only exe, and after many attempts to do it without installing
windows (WinPE live, for example) has failed I ended formatting
everything, installing windows 8, updating the BIOS and then restoring
Ubuntu.
My system is wo
I have the same problem in 14.04 and do not know how to rsolve it.
--
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/204133
Title:
wubi install unusable - Buffer I/O error on device loop0
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/1404428
Title:
System does not resume after s
Public bug reported:
In linux-image-3.13.0-41 and -43, my system goes to sleep when the lid
is closed, but does not resume when the lid is opened. It's probably
hardware specific (MacBook Pro running Trusty/14.04), but I saw that my
hardware data was sent with this report.
I noticed the problem
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/1404407
Title:
Kernel panic while cpying file
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/1404409
Title:
[regression] Intel 10Gb NIC Cr
Same on my Ubuntu 14.10 system right after upgrade to kernel version
3.16.0-28. The earlier version (3.16.0-25) boots just fine. Will be
reverting back to the early version for now.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
Public bug reported:
I have a new MSI CX61 2PC 2198XFR that I installed today with Ubuntu
14.04 LTS that works fine with my old computer.
Some info for the new one :
Linux JPD-CX61-2PC 3.13.0-43-generic #72-Ubuntu SMP Mon Dec 8 19:35:06 UTC 2014
x86_64 x86_64 x86_64 GNU/Linux
When I plugged an
Public bug reported:
I posted this to net...@vger.kernel.org as well:
http://www.spinics.net/lists/netdev/msg309110.html
I think the next step is to try to bisect this down to a specific commit. I'm
starting to look at the instructions here:
https://wiki.ubuntu.com/Kernel/KernelBisection
-
** Description changed:
Since the upgrade from Ubuntu 14.04 to 14.10 the Synaptic touchpad is
not detected entirely. The secondary key (right mouse button) does not
work with kernel 3.16.0-23-generic. Falling back under Ubuntu 14.10 to
the kernel 3.13.0-37-generic the Synaptic touchpad is
Brad: I'm testing the proposed kernel fix for trusty right now, but as
Donald mentioned, 5 days might not be enough to test it since the kernel
panic occurs randomly after a period of time.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to l
@JFL
In default setting left click is tap in any place of the touchpad.
This can be disabled in System Settings.
In this casy you will need to press a hardware button in lower left.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
Great fix. Thanks.
A question though. To left click, you have to just "touch" the area on
the lower left. I don't like that behaviour. How do I make it so you
have to physically "click" to register a mouse click? Which config
needs to be changed, or is that a lower-level driver issue?
Thanks
Public bug reported:
This is pretty rough:
root@tamriel:~# apport-collect 1404374
*** Collecting problem information
The collected information can be sent to the developers to improve the
application. This might take a few minutes.
.dpkg-query: no packages found matching linux
...
*** Send pro
Issue was resolved by moving the USB keyboard connector from the front
USB port to a USB port on the rear of the computer. Boot menu works as
advertised, must have to do with timing and priority of the USB ports.
--
You received this bug notification because you are a member of Kernel
Packages,
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1404374/+attachment/4284394/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bug
Note that the apport information included is from the 40.69 kernel boot,
of course.
** 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.launchp
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1404374/+attachment/4284389/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1404374/+attachment/4284391/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1404374/+attachment/4284392/+files/UdevDb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1404374
apport information
** Attachment added: "UdevLog.txt"
https://bugs.launchpad.net/bugs/1404374/+attachment/4284393/+files/UdevLog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1404
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1404374/+attachment/4284388/+files/Lspci.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1404374
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1404374/+attachment/4284390/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad
apport information
** Tags added: apport-collected
** Description changed:
I'm on OFTC and Freenode as Snow-Man if folks want to chat further or if
there's anything I can run with 'crash' to provide additional
information.
This is a KVM guest running under a physical box which is runn
This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:
apport-collect 1404374
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
Public bug reported:
I'm on OFTC and Freenode as Snow-Man if folks want to chat further or if
there's anything I can run with 'crash' to provide additional
information.
This is a KVM guest running under a physical box which is running the
same kernel (43.72)
I've downgraded the KVM guest to Linu
** Tags removed: verification-needed-utopic
** Tags added: verification-done-utopic
--
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/1335478
Title:
A new instance of IBM Domino 'bindsock'
I have also tested kernel 3.13.0-44 on Trusty-Proposed and it solves the
bug. I have modified the tag verification-needed-trusty to verification-
done-trusty.
** Tags removed: verification-needed-trusty
** Tags added: verification-done-trusty
--
You received this bug notification because you are
I pulled today's commits from
git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git which
build as kernel 3.18.0 showing still the same issue.
Additionaly I took the opportunity to upgrade my ACER B115's BIOS from V1.22 to
V1.26. Luckily I had to reset my personal settings back and wit
I've tested the kernel (3.13.0-44) from Trusty-Proposed and it solves
the bug. I cannot figure out where the tag "verification-needed-
utopic" resides and therefore I can't change the tag to "verification-
done"
--
You received this bug notification because you are a member of Kernel
Packages,
** 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/1393317
Title:
Intel 7265 [8086:095b] Wireless disconne
Did not disect to the bottom - released version 3.16.0-28 corrects the
problem, so I assume that someone beat me to it.
Fixed and verified over the last few days by switching back and forth
between -25 and -28. Wifi keeps dropping in -25, and stays stable
overnight in -28.
** Changed in: linux (U
Here is an output from the console of a system experiencing this issue.
This bug occurs after executing "sudo poweroff" and "sudo shutdown -h now" This
issue was found on trusty-updates and trusty-
proposed. It wasn't seen in the released version.
$ uname -a
Linux am5 3.13.0-37-generic #64-Ubunt
reggar, the next step is to fully reverse commit bisect from kernel 3.16
to 3.18.1 in order to identify the last bad commit, followed immediately
by the first good one. Once this commit has been identified, then it may
be reviewed as a candidate for backporting into your release. Could you
please d
raggar, the next step is to fully reverse commit bisect from kernel 3.16
to 3.18.1 in order to identify the last bad commit, followed immediately
by the first good one. Once this commit has been identified, then it may
be reviewed as a candidate for backporting into your release. Could you
please d
Erlenmayr, the general issue of resuming from suspend while a closed
laptop is in a jostling bag is one that wouldn't be unique to Ubuntu, as
it affects all hardware and operating systems. I've dealt with folks who
have caused hardware failure to a brand new computer due to this. What
I've done mys
Thanks, Andy- I've provided all this info in PMR 41425,227,000.
--
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/1335478
Title:
A new instance of IBM Domino 'bindsock' cannot bind to ports
Patches sent to the lxc-devel mailing list to follow up on stgraber's
idea.
So between this and Eric's patch to prevent anyone but root from doing
umount -f, this should become non-urgent.
But it still seems wrong.
--
You received this bug notification because you are a member of Kernel
Package
** Description changed:
- Same behavior when using pm-suspend. This bug may be CRITICAL, because
- it is hard to notice whether the laptop waking up, especially because
- that does not always happen immediately. Getting to sleep takes up to 30
- seconds. Hardware damage may be a result of waking u
holger_p., would this be reproducible in the latest mainline kernel
available 3.18.1?
** Tags removed: kernel-bug-exists-upstream-3.18-rc1
** Tags removed: performing-bisect
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu
I can confirm that the issue looks fixed using 3.13.0-44.73~precise1
from precise-proposed.
I made more than ten reboots with the new kernel installed on VMs and
all were successful. Then I switched back to the previous
3.13.0-43.72~precise1 and VMs boot failed at the first trial. Again back
to pr
Federico Sassi, the next step is to fully reverse commit bisect from
kernel 3.18-rc7 to 3.18.1 in order to identify the last bad commit,
followed immediately by the first good one. Once this commit has been
identified, then it may be reviewed as a candidate for backporting into
your release. Could
So, I don't have a problem testing this on trusty-proposed but the 5 day
thing might be an issue. The kernel panic happened randomly after some
period of time, it wasn't something I could trigger on demand. All I can
do is run a server and wait some period of time and see if it kernel
panics or not
The attached test.c should tickle this bug, sendmsg should return ret=4
errno=0 when the fix is applied, ret=-1 errno=22 when it is not.
** Attachment added: "test.c"
https://bugs.launchpad.net/ubuntu/+source/linux-lts-trusty/+bug/1335478/+attachment/4284352/+files/test.c
--
You received thi
This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:
apport-collect 1404335
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 bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:
apport-collect 1404050
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
** Package changed: ubuntu-release-upgrader (Ubuntu) => linux (Ubuntu)
--
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/1404050
Title:
After loading Ubuntu along side windows, my keyboard
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-
trusty' to 'verification-done-trusty'.
If verification is not done by 5 working days from t
You have been subscribed to a public bug:
Prior to loading Ubuntu 14.10, my system boot menu comes up and I can
make changes using my keyboard. (F10,F11, up, down etc). After loading
Ubuntu, my keyboard does not respond on either boot menu. (Launch
Ubuntu, Launch Window) As a result, I can't ch
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-
utopic' to 'verification-done-utopic'.
If verification is not done by 5 working days from t
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-
trusty' to 'verification-done-trusty'.
If verification is not done by 5 working days from t
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-
utopic' to 'verification-done-utopic'.
If verification is not done by 5 working days from t
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-
utopic' to 'verification-done-utopic'.
If verification is not done by 5 working days from t
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 tod
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-
trusty' to 'verification-done-trusty'.
If verification is not done by 5 working days from t
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-
trusty' to 'verification-done-trusty'.
If verification is not done by 5 working days from t
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-
trusty' to 'verification-done-trusty'.
If verification is not done by 5 working days from t
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-
trusty' to 'verification-done-trusty'.
If verification is not done by 5 working days from t
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 from
I could not pair the Z8000 mouse to 12.04 LTS. Importatnt to mention,
the desktop sometimes freezes during the pairing.
The bluez version is: 4.98-2ubuntu7.2.
The laptop is an HP Envy TouchSmart 15.
I was able to connect other Bluetoth mouses to the op. system except the
reported HP Z8000 mouse.
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-
utopic' to 'verification-done-utopic'.
If verification is not done by 5 working days from t
I am testing it for two weeks already. It definitely solves the problem.
** Tags removed: verification-needed-utopic
** Tags added: verification-done-utopic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.lau
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-
utopic' to 'verification-done-utopic'.
If verification is not done by 5 working days from t
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-
utopic' to 'verification-done-utopic'.
If verification is not done by 5 working days from t
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-
trusty' to 'verification-done-trusty'.
If verification is not done by 5 working days from t
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-
utopic' to 'verification-done-utopic'.
If verification is not done by 5 working days from t
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-
utopic' to 'verification-done-utopic'.
If verification is not done by 5 working days from t
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-
utopic' to 'verification-done-utopic'.
If verification is not done by 5 working days from t
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-
trusty' to 'verification-done-trusty'.
If verification is not done by 5 working days from t
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-
trusty' to 'verification-done-trusty'.
If verification is not done by 5 working days from t
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 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-
trusty' to 'verification-done-trusty'.
If verification is not done by 5 working days from t
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-
utopic' to 'verification-done-utopic'.
If verification is not done by 5 working days from t
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-
utopic' to 'verification-done-utopic'.
If verification is not done by 5 working days from t
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-
utopic' to 'verification-done-utopic'.
If verification is not done by 5 working days from t
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-
trusty' to 'verification-done-trusty'.
If verification is not done by 5 working days from t
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-
utopic' to 'verification-done-utopic'.
If verification is not done by 5 working days from t
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-
trusty' to 'verification-done-trusty'.
If verification is not done by 5 working days from t
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-
trusty' to 'verification-done-trusty'.
If verification is not done by 5 working days from t
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-
utopic' to 'verification-done-utopic'.
If verification is not done by 5 working days from t
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-
utopic' to 'verification-done-utopic'.
If verification is not done by 5 working days from t
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-
utopic' to 'verification-done-utopic'.
If verification is not done by 5 working days from t
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-
trusty' to 'verification-done-trusty'.
If verification is not done by 5 working days from t
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-
trusty' to 'verification-done-trusty'.
If verification is not done by 5 working days from t
Public bug reported:
[Impact]
Fixes an issue where after the system halts the cpu starts to experience soft
lockups.
[Test Case]
The most reliable means of reproducing this issue is to 'sudo poweroff' the
system from the console.
[Regression Potential]
These patches are upstream patches that h
Hello Christopher,
Thanks for your help! I tested the most recent kernel:
3.18.1-031801-generic
In this kernel the touchpad keeps working after a suspend. Do you need
me to test this on a lower kernel as well?
I changed this to confirmed and added the tags.
** Tags added: kernel-fixed-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/1401935
Title:
[Acer Aspire V3-371] Touchpad stops working after suspe
** Tags added: unable-to-bisect
--
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/1385937
Title:
[Acer Travelmate B115-M] Synaptic touchpad not correctly detected in
kernel 3.16 after upg
I will try to open a service request based on this information. Is there
anything more specific information about which of the fields is passing
on the junk?
Perhaps this could actually get fixed!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscri
Now I have edited /proc/acpi/wakeup for four weeks and it did not happen
again a single time. It really is the XHC1 (USB3) interface waking up
the computer.
My still unanswered question again: Why is this b* enabled by
default in the first place? A decade before this bug I already
considered i
@penalvch, as stated by @erlenmayr, the bug is the same in 14.04.01.
--
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/1391476
Title:
[MacBookPro11,1] Laptop wakes up while lid closed
Stat
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1404242/+attachment/4284248/+files/WifiSyslog.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages,
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1404242/+attachment/4284239/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net
apport information
** Attachment added: "UdevLog.txt"
https://bugs.launchpad.net/bugs/1404242/+attachment/4284247/+files/UdevLog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1404
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1404242/+attachment/4284242/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1404242/+attachment/4284244/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad
1 - 100 of 175 matches
Mail list logo
