apport information
** Attachment added: "NetDevice.lo.txt"
https://bugs.launchpad.net/bugs/1774443/+attachment/5155233/+files/NetDevice.lo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "NetDevice.enp0s20u3.txt"
https://bugs.launchpad.net/bugs/1774443/+attachment/5155232/+files/NetDevice.enp0s20u3.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1774443/+attachment/5155240/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "PciNetwork.txt"
https://bugs.launchpad.net/bugs/1774443/+attachment/5155236/+files/PciNetwork.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1774443/+attachment/5155239/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1774443/+attachment/5155238/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1774443/+attachment/5155237/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "NetworkManager.conf.txt"
https://bugs.launchpad.net/bugs/1774443/+attachment/5155235/+files/NetworkManager.conf.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "NetDevice.wlp8s0.txt"
https://bugs.launchpad.net/bugs/1774443/+attachment/5155234/+files/NetDevice.wlp8s0.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1774443/+attachment/5155230/+files/Lsusb.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/1774443
apport information
** Attachment added: "IpAddr.txt"
https://bugs.launchpad.net/bugs/1774443/+attachment/5155227/+files/IpAddr.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1774443/+attachment/5155226/+files/Dependencies.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "NetDevice.eno1.txt"
https://bugs.launchpad.net/bugs/1774443/+attachment/5155231/+files/NetDevice.eno1.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1774443/+attachment/5155228/+files/IwConfig.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1774443/+attachment/5155229/+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/1774443
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1774443/+attachment/5155225/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1774443/+attachment/5155224/+files/CRDA.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/1774443
apport information
** Tags added: apport-collected
** Description changed:
Laptop is an HP Pavilion dm4-3170se. Dual booting Windows 7 and ubuntu.
In Windows, system boots with wireless disabled and then pressing the
wireless enable button twice enables WiFi.
In ubuntu, system boots
I can confirm that hibernate works on 4.13.0-21 but is broken in
4.13.0-25 and 4.13.0-31.
I have reviewed syslog and kern.log but don't see any entries regarding
the failed resume attempt.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
** Tags added: verification-done
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to ubuntu-fan in Ubuntu.
https://bugs.launchpad.net/bugs/1737640
Title:
/usr/sbin/fanctl: arithmetic expression: expecting primary |
unconfigured
** Changed in: juju
Status: Triaged => Invalid
** Tags removed: verification-needed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to ubuntu-fan in Ubuntu.
https://bugs.launchpad.net/bugs/1737640
Title:
/usr/sbin/fanctl:
I confirm this issue, LibreOffice Base crushed any time when i try to do
anything in Base. are there any pathches ?
Processor: Intel Pentium T4400 @ 2.20GHz (2 Cores)
Software:
OS: Ubuntu 17.04, Kernel: 4.10.0-26-generic (i686), Desktop: Xfce 4.12, Display
Driver: modesetting 1.19.3, OpenGL:
Please ignore my posts. I now realize it's not the same error. My
apologies. Monitor, please delete my responses. 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/1706128
Title:
Though the above is not exactly for 4.4.0-87, 4.4.0-87 is the culprit.
This was a step after the initial issue occurred. If you need additional
logs, please let me know.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
In trying to troubleshoot this on a production server I noticed the issue is
actually with linux-image-extra-4.4.0-87-generic. In the apt-auto-remove post
install script, the linux-image-extra-4.4.0-87-generic creates a segfault.
$ sudo apt-get install linux-image-extra-4.4.0-81-generic
PS: Here's the log file...
Jul 12 23:38:48 LEE-03 kernel: ata14.00: exception Emask 0x0 SAct 0x0 SErr 0x0
action 0x6
Jul 12 23:38:48 LEE-03 kernel: ata14.00: irq_stat 0x4001
Jul 12 23:38:48 LEE-03 kernel: ata14.00: cmd
a0/01:00:00:00:01/00:00:00:00:00/a0 tag 1 dma 16640 in
I have also got this bug, but from Ubuntu 16.04.02 LTS (32-bit), (with
MATE desktop add-on)
It would be good if this got some attention, thanks.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to libatasmart in Ubuntu.
I am unable to run apport-collect running 4.12-rc3, because I cannot
actually boot my computer (an immediate kernel panic occurs, as
evidenced by adding the output from earlyprintk=efi), so I'm marking
this bug as confirmed. Please also see relevant discussion about this
issue on the Linux Kernel
It appears a kernel panic is happening immediately while attempting to boot
4.12-rc3, it doesn't happen on 4.12-rc2.
Adding earlyprintk=efi to the grub command line options, I get the following
message (which explains why the bootloader stops at 'loading initial
ramdisk...'):
This was
Public bug reported:
I have an HP Spectre x360 Convertible laptop with an Intel 5500U SoC. In
short, I am completely unable to boot kernel 4.12-rc3, even though I
could boot from 4.12-rc2 perfectly fine. The loading screen does not
appear at all, instead GRUB remains stuck on "Loading initial
This was fixed in 4.12-rc2!
** Changed in: linux (Ubuntu)
Status: Confirmed => 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/1692143
Title:
fs changes in kernel
Seems this was resolved in 4.12-rc2, mounting ntfs-3g volumes is fine,
doesn't generate a kernel warning! It was fixed in fs/fuse/inode.c at
https://github.com/torvalds/linux/commit/69c8ebf83213e6165b13d94ec599b861467ee2dc
with
diff --git a/fs/fuse/inode.c b/fs/fuse/inode.c
index
Okay, so the warning is clearly being generated by the WARN_ON function in
fs/super.c.
I realize I could disable the warning, but that sounds like a bad idea. One
question though,
why would we be verifying if sb->s_bdi is equal to the address of some "struct
backing_dev_info
** Attachment added: "dmesg.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1692143/+attachment/4879845/+files/dmesg.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Attachment added: "lspci-vvnn.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1692143/+attachment/4879846/+files/lspci-vvnn.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Public bug reported:
Mounting any ntfs partition or ntfs-formatted external drive in kernel
4.12 results in a critical kernel warning. Possible data corruption
could happen, as the drive must be forcibly unmounted. The kernel
warning appears in the syslog literally every single time, this is a
** Attachment added: "uname-a.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1692143/+attachment/4879847/+files/uname-a.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Attachment added: "version.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1692143/+attachment/4879867/+files/version.log
** Also affects: ntfs-3g (Ubuntu)
Importance: Undecided
Status: New
** Also affects: fuse (Ubuntu)
Importance: Undecided
Status: New
--
** No longer affects: 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/1677175
Title:
network-manager 1.2.6 won't connect to vpn and displays false
connected message
apport information
** Tags added: apport-collected xenial
** Description changed:
I have been having a rather serious and incredibly annoying problem on the
updated version of network-manager v1.2.6 on Ubuntu 16.04.2 LTS. Trying to
manually connect to my VPN provider using openvpn through
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1677175/+attachment/4850129/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1677175/+attachment/4850128/+files/JournalErrors.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Public bug reported:
I have been having a rather serious and incredibly annoying problem on the
updated version of network-manager v1.2.6 on Ubuntu 16.04.2 LTS. Trying to
manually connect to my VPN provider using openvpn through the network manager
fails literally any time except bootup. Every
I tried to do an apport and it seg-faulted in the middle of it. However
a few days of researching and looking at the chipset datasheet specific
to my model and I found something useful.
The dmesg report complains about vendor request 0x07 which is a multiple
byte read in the specs, while the
Reporting in from 16.04LTS, this bug still exists and Bug #1388416
appears to be describing the same bug and is marked Confirmed. I just
signed up to post this so I'm still unfamiliar with the platform to find
a way to link to it here.
I have the same issue, though it appeared to change behaviors
I can confirm this works on xenial after installing squashfuse.
root@clean-lark:~# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 16.04.1 LTS
Release:16.04
Codename: xenial
root@clean-lark:~# uname -a
Linux clean-lark 4.4.0-63-generic
Yes, this problem most definitely occurs with the Yakkety proposed
kernel, I tried using the most recent build of 16.10 that comes with
4.8, and the graphical problems persist.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
All kernels after 4.7.4 have this exact same issue with Broadwell
integrated graphics, including the official 4.8 release and the previous
rc builds.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Since my last comment, I have been trying the modesetting driver
periodically and it seems that a fairly recent update has fixed the
screen wrapping I was seeing on my Lemur. My operating system is still
Xubuntu 16.04. I have been using the modesetting driver since last night
and I have seen no
** Description changed:
I would like to report a severe graphics regression, involving frequent
rainbow-glitching and flickering on a x64 computer with Intel Broadwell
5500U processor w/ integrated graphics. This issue was not present on
kernel v4.7.4, which I will continue to use. Due to
I was unable to use apport-collect but I believe the information I have
provided is sufficient. I am running Ubuntu 16.04.1 LTS with kernel
v4.7.5-generic on a x64 HP Spectre x360 with Broadwell GT2 5500
integrated graphics.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
Public bug reported:
I would like to report a severe graphics regression, involving frequent
rainbow-glitching and flickering on a x64 computer with Intel Broadwell
5500U processor w/ integrated graphics. This issue was not present on
kernel v4.7.4, which I will continue to use. Due to
I have a lemu5 installed with Xubuntu 16.04. I have seen the same kind
of screen wrapping when I try to use the modesetting driver in place of
xserver-xorg-video-intel (as suggested by its description). It manifests
itself somewhat randomly during normal use. I noticed it is particularly
bad when
Public bug reported:
When the clocksource is set to "refined-jiffies" it ticks twice as fast.
This is not an issue when it is changed to "tsc".
The problem existed in earlier kernels too.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-76-generic 3.13.0-76.120
And I just remembered that I have some logs from the newer failure that
might help. I will post short excerpts here as otherwise there is
nothing to distinguish them from the logs of the older failure.
>From kern.log:
Nov 29 11:36:53 hydra kernel: [ 35.815890] bbswitch: version 0.7
Nov 29
More information: I found that 352.63 also claimed to support my nvidia
graphics card. I installed it. It made me reconfigure my xorg.conf.
Putting "Intel" as the default driver allowed me to see the login screen. But
whenever I entered the correct password, X would crash and send me back to the
Just in case anyone's still listening. The most recent update, which
included an nvidia driver update (340.96-0ubuntu0.14.04.1), pushed back
the version of the latest kernel that worked. 3.13.0-58 no longer works.
57 gives bad resolution, I am testing 55, 32 still works. So it seems
like whatever
And here I am realizing I should have said more. Both versions performed
identically, but I wrote a lot more about the 3.13 because I could
compare the effects of installing it from the upstream source with the
effects of installing it from the package manager. Whereas the most I
could say about
Sorry, my comment wasn't clear. I tested both 3.13.whatever and linux-
image-4.3.0-040300rc7-generic_4.3.0-040300rc7.201510260712_i386. Both
gave the same results.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I know I took a long time again. My primary observation is that this bug
does not appear when the nvidia driver is not installed.
I tested the upstream kernel version that matches the most recent
repository kernel update(as well as the most recent upstream kernel
version) before installing the
Okay so I updated my BIOS. Summary: I detect no change.
On my first restart I tried using the latest kernel I have installed
(3.13.0-63), and got the black screen. I noticed that the backlight
stays off when I get the blank screen. Unfortunately I cannot say
whether or not this is new. I feel
Sorry for the delay. I am still working up the nerve to update my BIOS.
In the meantime, I thought it might be useful if I mentioned that the
most recent set of updates I got broke this for kernel version 3.13.0-59
as well, I luckily still had -58 which is working. If you want me to
tell you
Sorry I took so long. Trying to test the upstream kernel took some
figuring out and I had to go on a trip. I could not get the upstream
kernel to install the nvidia driver (or the kernel headers), without the
nvidia driver (presumably using the Intel integrated graphics) it did
give me a graphical
** Tags added: kernel-unable-to-test-upstream
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1482711
Title:
X displays nothing instead of login screen
Status in linux package in
This is really becoming a problem. The latest logitech bluetooth devices
simply do not work with the version of bluez used in Ubuntu! Every
supported release needs to be upgraded to the latest version in order to
ensure a satisfactory end-user experience.
--
You received this bug notification
Public bug reported:
The kernel version in the auto-generated information is wrong, because
when using the kernel with the problem, I can't do anything, including
send bug reports. This happened with the newest kernel update to
3.13.0-61. I am using -59, which still works, to send the report.
Well for some reason it submitted it in the middle of typing. The end of
that last sentence was that it I normally use the integrated Intel
graphics card for my desktop, and anything not specially high
performance.
--
You received this bug notification because you are a member of Kernel
For those users wanting a solution:
Uninstall usbip package if you've installed it.
On trusty, install linux-tools-generic-lts-utopic. I can't seem to find
a package that will create a binary, but you can run the binary manually
from /usr/lib/linux-tools/. As of this writing it's /usr/lib/linux-
Public bug reported:
After unlocking phone and establishing trust, the iPhone 5S will not
pair with Linux. I get the repeated unhandled lockdown error -20.
I have tried the solution presented here:
http://ubuntuforums.org/showthread.php?t=2228772
ProblemType: Bug
DistroRelease: Ubuntu 14.04
I have an MSI H97M-G43 motherboard, H97 chipset but ALC892. Running
Kubuntu 14.04
Installing the 3.15.0-031500rc2-generic kernel did not work, even though
the patch was apparently incorporated.
The suggestion about: echo options snd-hda-intel vid=8086 pid=8ca0
snoop=0 sudo
Chistopher Penalver, I have downloaded and performed minor testing with
the amd64 image of the Trusty daily-live build (downloaded at 21:47
CEST, so presumably yesterday's build).
The live image was able to restart the Wired Interface connection
without fail 5 out of 5 attempts I made. Not
this problem
entirely.
Thank you for your help, and if there is anything I can do to help with
the process, I would be more than happy to participate.
-Nicholas Anderson
ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: alsa-base 1.0.25+dfsg-0ubuntu4
ProcVersionSignature
the audio is idle. However,
disabling the audio device power-save feature remedies this problem
entirely.
Thank you for your help, and if there is anything I can do to help
with the process, I would be more than happy to participate.
-Nicholas Anderson
ProblemType: Bug
DistroRelease
the audio is idle. However,
disabling the audio device power-save feature remedies this problem
entirely.
Thank you for your help, and if there is anything I can do to help
with the process, I would be more than happy to participate.
-Nicholas Anderson
ProblemType: Bug
DistroRelease: Ubuntu
the audio is idle. However,
disabling the audio device power-save feature remedies this problem
entirely.
Thank you for your help, and if there is anything I can do to help
with the process, I would be more than happy to participate.
-Nicholas Anderson
ProblemType: Bug
when the audio is idle. However,
disabling the audio device power-save feature remedies this problem
entirely.
Thank you for your help, and if there is anything I can do to help
with the process, I would be more than happy to participate.
-Nicholas Anderson
ProblemType: Bug
sound when the audio is idle. However,
disabling the audio device power-save feature remedies this problem
entirely.
Thank you for your help, and if there is anything I can do to help
with the process, I would be more than happy to participate.
-Nicholas Anderson
ProblemType: Bug
sound when the audio is idle. However,
disabling the audio device power-save feature remedies this problem
entirely.
Thank you for your help, and if there is anything I can do to help
with the process, I would be more than happy to participate.
-Nicholas Anderson
ProblemType: Bug
buzzing sound when the audio is idle. However,
disabling the audio device power-save feature remedies this problem
entirely.
Thank you for your help, and if there is anything I can do to help
with the process, I would be more than happy to participate.
-Nicholas Anderson
ProblemType: Bug
the audio is idle. However,
disabling the audio device power-save feature remedies this problem
entirely.
Thank you for your help, and if there is anything I can do to help
with the process, I would be more than happy to participate.
-Nicholas Anderson
ProblemType: Bug
DistroRelease
to participate.
-Nicholas Anderson
ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: alsa-base 1.0.25+dfsg-0ubuntu4
ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7
Uname: Linux 3.11.0-14-generic x86_64
ApportVersion: 2.12.5-0ubuntu2.1
Architecture: amd64
when the audio is idle. However,
disabling the audio device power-save feature remedies this problem
entirely.
Thank you for your help, and if there is anything I can do to help
with the process, I would be more than happy to participate.
-Nicholas Anderson
ProblemType: Bug
the audio is idle. However,
disabling the audio device power-save feature remedies this problem
entirely.
Thank you for your help, and if there is anything I can do to help
with the process, I would be more than happy to participate.
-Nicholas Anderson
ProblemType: Bug
DistroRelease
sound when the audio is idle. However,
disabling the audio device power-save feature remedies this problem
entirely.
Thank you for your help, and if there is anything I can do to help
with the process, I would be more than happy to participate.
-Nicholas Anderson
ProblemType: Bug
the audio is idle. However,
disabling the audio device power-save feature remedies this problem
entirely.
Thank you for your help, and if there is anything I can do to help
with the process, I would be more than happy to participate.
-Nicholas Anderson
ProblemType: Bug
DistroRelease
the audio is idle. However,
disabling the audio device power-save feature remedies this problem
entirely.
Thank you for your help, and if there is anything I can do to help
with the process, I would be more than happy to participate.
-Nicholas Anderson
ProblemType: Bug
DistroRelease
sound when the audio is idle. However,
disabling the audio device power-save feature remedies this problem
entirely.
Thank you for your help, and if there is anything I can do to help
with the process, I would be more than happy to participate.
-Nicholas Anderson
ProblemType: Bug
,
disabling the audio device power-save feature remedies this problem
entirely.
Thank you for your help, and if there is anything I can do to help
with the process, I would be more than happy to participate.
-Nicholas Anderson
ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package
Given that:
1) The config file : /etc/default/tmpfs is no longer installed and
therefore doesn't contain a comment that says Adjust the default size
of /dev/shm by uncommenting the line below (or whatever it said
exactly)
2) /dev/shm is now mounted as /run/shm who's size is controlled by some
If you look at http://packages.ubuntu.com/lucid/bcmwl-kernel-source,
you'll notice that this package is for 802.11 wireless cards that have
Broadcom's architecture. The important thing to note about this package
is that it only supports certain broadcom cards, but any card that
internally says it
** Package changed: ubuntu = linux-firmware (Ubuntu)
--
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/1234488
Title:
Unreliable wifi with N mode enabled
Status in
whiskey-icarus@whiskeyicarus-Inspiron-6000:~$ sudo apt-get -f install
Reading package lists... Done
Building dependency tree
Reading state information... Done
Correcting dependencies... Done
The following packages were automatically installed and are no longer
required:
libcelt0-0 libopenspc0
Public bug reported:
Errors were encountered while processing:
/var/cache/apt/archives/linux-image-3.5.0-37-generic_3.5.0-37.58_i386.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
ProblemType: Package
DistroRelease: Ubuntu 12.10
Package: linux-image-3.5.0-37-generic (not installed)
For me at least it turned out to be a hardware problem. After getting
the fan replaced I'm not experiencing this problem at all.
--
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/751689
101 - 194 of 194 matches
Mail list logo
