This is what I got when I went to the following web site.
http://hplipopensource.com/hplip-web/install_wizard/index.html
You have selected Ubuntu 16.04 using the HP Officejet Pro 8710 All-in-
one Printer.
Ubuntu 16.04 supplies HPLIP 3.15.2 by default, which does not support
your printer.
You mus
I've found the solution to the problem but I can't implement it. I
don't even know if the right persons will even read this. I guess I
just have wait and see if the latest HPLIP will be attached to ubuntu
16.04.
--
You received this bug notification because you are a member of Kernel
Packages,
Ubuntu 16.04 LTS is configured with HPLIP 3.15.2 by default.
Ubuntu 17.04, which is not LTS, is configured with HPLIP 3.17.9 but no
convenient way to upgrade to it and will not be supported after January 2018.
Since Ubuntu 16.04 is going to be supported for the next 5 years, it needs to
have
Christian: looking back and your reply in #478, it would appear that
you're on Mint, not Ubuntu. It is likely the case that Mint is still
shipping the buggy kernel(s).
We can see in #478: "When installing the Kernels provided above, I can
again do changes in BIOS and they stay over reboot. Howev
** Package changed: 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/1743297
Title:
Not work pam-mount in linux-image-4.13.0-26
Status in linux package in Ubuntu:
I'm no longer experiencing this on 4.13.0 series kernels.
--
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/1649727
Title:
No sound card detected with device: Intel Corporation Device 9d71
Public bug reported:
I'm testing the latest 17.10 beta and i'm having issues booting.
It goes through grub, onto the Ubuntu boot screen ... the dots complete
and then nothing the machine just stays on this screen then eventually
the screen turns off.
The only way I can get it to boot is to go in
ith a corrupt drive at the minute as well.
Let me know if there is anything else I can help with.
Thanks
Paul
** Attachment added: "Kern.log file"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1724362/+attachment/4975181/+files/kern.log
--
You received this bug notification
I installed the upstream Kernel you advised and re-commented custom.conf
and booted up with the RC5 Kernel without issue.
Problem fixed ... thank you.
Does that mean i'm now using wayland ?
Thanks !!
--
You received this bug notification because you are a member of Kernel
Packages, which is su
I just tried command
echo $XDG_SESSION_TYPE
and it returned
x11
So I would say no ?
--
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/1724362
Title:
Not booting - 17.10 Beta 2
Stat
I only have Ubuntu on Xorg, or Unity to choose from on the sign in
screen.
System is all updated.
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/1724362
Title:
Not booting - 17.
Re-installed HPLIP 3.15.2.run on my desktop pc and configured my
printer via 123.hp.com. My hp 8710 office jet now works again.
Problem solved!
--
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'm sorry, but I really don't understand. I understand about
kernels...but that page just baffles me completely.
--
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/1673344
Title:
Ub
I do understand that apparently I can't use the mainline kernels because
I'm using the nVidia blob...
--
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/1673344
Title:
Ubuntu 16.04
Sorry...but I really don't know what you're talking about. Who or what
is Artful?
--
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/1673344
Title:
Ubuntu 16.04 doesn't recongnize w
I got my printer working again by downloading and applying HPLIP-3.15.2.run
to my ubuntu 16.04 OS. Thanks
On Thu, Oct 12, 2017 at 9:58 AM, Joseph Salisbury <
joseph.salisb...@canonical.com> wrote:
> Would it be possible for you to test the latest upstream kernel? Refer
> to https://wiki.ubuntu.c
This is still a problem
On Thu, Oct 12, 2017 at 9:58 AM, Joseph Salisbury <
joseph.salisb...@canonical.com> wrote:
> Would it be possible for you to test the latest upstream kernel? Refer
> to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
> v4.14 kernel[0].
>
> If this bug
Yes all changes were saved, the disk problems were on an external drive
not the OS drive.
--
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/1724362
Title:
Not booting - 17.10 Beta 2
Status
Against my wishes I've updated to 17.10 along with the kernel and
drivers that come with it.
And it still fails. Works for a few minutes then goes permanently to a
"Device not ready" until the next reboot.
But now it's even worse because it also trashes every single other wifi
device I have. When
I'm sorry, but this new kernel is much, much MUCH worse than the old one
as now my system is completely unusable.
With 16.04 when the Intel network adapter gave out I could at least switch to
one of my other ones.
But with 18.10 neither the Ralink nor the Realtek work. They are both "active"
and
** Package changed: xorg (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/1731041
Title:
kernel
Status in linux package in Ubuntu:
Confirmed
Bug description:
** Package changed: ubuntu => bluez (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1738404
Title:
Bluetooth sound extreme low quality
Status in bluez package in Ubuntu:
New
FWIW, the Intel-SPI Readme contains:
https://github.com/torvalds/linux/blob/master/Documentation/mtd/intel-
spi.txt
"makes it possible to read and write the SPI serial flash, if certain
protection bits are not set and locked."
"… If it finds any of them set, the whole MTD device is made re
I've emailed Mika Westerberg (author of the module) to ask to share
anything further documentation they've got that would allow a better
understanding of the (intended) operation of the 'intel-spi' module.
--
You received this bug notification because you are a member of Kernel
Packages, which is
Page 5 of:
http://opensecuritytraining.info/IntroBIOS_files/Day2_03_Advanced%20x86%20-%20BIOS%20and%20SMM%20Internals%20-%20SPI%20Flash%20Protection%20Mechanisms.pptx
Talks about "Flash Protection Mechanism";
"Write Protect / Writes blocked / Not Range Specific / SMI# override:
Same as Write P
Have received an excellent reply from Mika Westerberg (thank you!). One
with a suggestion regarding 'GigaDevice' flash chips, and one regarding
certain 'Winbond' flash chips.
Is somebody with access or one of more of these machine(s) able to
provide insight into what flash parts are in their mach
(For clarity the above upload of linux (kernel)=4.13.0-21.24) is a
workaround that just disables compiling in of the module under
suspicion. Because the module is not compiled it, it will not therefore
be loaded either).
--
You received this bug notification because you are a member of Kernel
Pa
[The two theories provided by Mika Westerberg, verbatim]
"""
Instead I have a theory since as far as I know there have been to kinds
of issues.
1. Flash is left locked. This makes the BIOS impossible to save
settings.
This seems to happen only for GigaDevice flashes and for all of thos
Mika Westerberg emailed again with a pointer to the commit from a few
months ago, specifically dealing with a similar issue on Lenovo Yoga
machines:
"""
mfd: lpc_ich: Do not touch SPI-NOR write protection bit on Haswell/Broadwell
At least on Lenovo Thinkpad Yoga, the BIOS seems to monitor the SPI
Could somebody with the hardware also do a test with the following lines
commented out in 'intel-spi.c', commenting out the writel() that
disables SMI interrupt generation, re-compile the kernel and retest:
https://github.com/torvalds/linux/blob/8afda8b26d01ee26a60ef2f0284a7f01a5ed96f8/drivers/mtd
** Description changed:
SRU Justification
Impact: Many users are reporting issues with bios corruption with 17.10.
This seems to stem from enabling the intel-spi-* drivers in the kernel,
which don't appear to be ready for use on end-user machines.
Fix: Disable this driver.
Tes
Register map documentation for the SPI (Serial Peripheral Interface) in
recent Intels begins on page 5626
https://www.intel.com/content/dam/www/public/us/en/documents/datasheets/atom-z8000
-datasheet-vol-2.pdf
HSFSTS (Hardware Sequencer Status) + HSFCTL (Hardware Sequencer Control)
are covered on
** Package changed: 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/1739939
Title:
Update Ubuntu-4.15.0 config to support Intel Atom devices
Status in linux pack
** Package changed: 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/1740116
Title:
Touchpad incorrectly being detected by kernel as PS/2 mouse
Status in linux pa
Unfortunately it looks like it doesn't fix the problem on my Lenovo
S20-30 touch. Tried rebooting with 4.14.9 but bios settings are not
retained.
Are there any other ideas?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
The second kernel from step 8 of the new description has solved the
problem on my Lenovo S20-30 touch. Thanks for fixing.
--
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/1734147
Title:
U
@Paul sabret00the. Please can you file separate new bugs for the
"disassociated with its launcher icon", "my swap disk has issues", and
"I can't launch any Virtual Boxes". These are not related to the CMP
bit in the flash chip, and putting them on this bug
On 11/02/17 11:07, Kai-Heng Feng wrote:
>> On 2 Nov 2017, at 5:40 PM, Paul Menzel <1651...@bugs.launchpad.net> wrote:
>>
>> @kaihengfeng, I am quite surprised and even angry about your comment.
> My apology.
No problem. Maybe I also have to apologize for my response d
I can confirm that the GRUB_GFXPAYLOAD_LINUX=text fix works on my Acer
Aspire One (N214) after upgrading Lubuntu from 17.04 to 17.10.
--
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/1724639
Azure timesync is preventing a number of our production services from
getting accurate timesync; when is the xenial SRU likely to be
available?
--
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
-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: paul 2742 F pulseaudio
Date: Mon Jun 19 21:36:44 2017
Dependencies:
DuplicateSignature:
package:linux-libc-dev:amd64:4.4.0-81.104
Setting up libc6
Affects me too. I also get the iwl_pcie_txq_stuck_timer errors in dmesg
at the point of failure
--
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/1673344
Title:
Ubuntu 16.04 doesn'
Public bug reported:
Between kernel versions 4.4.0-53 and 4.4.0-57 a bug has been
(re?)introduced that is breaking dhcp booting in the initrd environment.
This is stopping instances that use iscsi storage from being able to
connect.
Over serial console it outputs:
IP-Config: no response after 2
** Attachment added: "4.4.0-57 "broken" initrd"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1652348/+attachment/4795793/+files/initrd.img-4.4.0-57-generic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https:
** Attachment added: "Working 4.4.0-53 initrd"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1652348/+attachment/4795794/+files/initrd.img-4.4.0-53-generic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https:/
** Attachment added: "pcap from dhcp server side of inird startup doing dhcp"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1652348/+attachment/4795820/+files/failed.pcap
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
The checksum invalid mentioned in the pcap is interesting, but happens
in both failed and successful, so I'm not sure it's relevant.
--
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/1652348
** Attachment added: "pcap from dhcp server side of 'ipconfig -t "dhcp" -d
"ens2f0" '"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1652348/+attachment/4795819/+files/worked.pcap
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
apport-collect doesn't exist in initrd. I'm unable to supply the
requested information.
** 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.la
I've worked my way back through the kernels. The bug, as it was
(avoided by ip=dhcp in the kernel command line), was in effect in
version 4.4.0-38-generic. It was fixed in 4.4.0-42-generic. This is
the state of play so far with kernels I've tested:
linux-image-4.4.0-38-generic - Affected
linux-
I've also confirmed the bug is present all the way back in
4.4.0-21-generic, and is present in 4.8.0-34-generic from yakkety-
proposed.
--
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/165234
Tried and tested (the current up-to-date kernels at the time of
posting):
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.10-rc1/linux-
headers-4.10.0-041000rc1-generic_4.10.0-041000rc1.201612252031_amd64.deb
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.10-rc1/linux-
image-4.10.0-041000rc1-g
I'll get started on it. This might take a while to do.
A couple of quick observations:
1) we haven't validated that mainline 4.4.0 actually works. I only know
certain Ubuntu versions of the 4.4.0 kernel work. Given how much seems
to be changing between Ubuntu releases of it, that seems a risky
Ahh, I see where the kteam tools stuff is supposed to come from.
It's not clear if I'm supposed to go down that route and use the
mainline-build-one script or not when trying to build the kernel in this
case. If I use the mainline-build-one tool:
$ mainline-build-one afd2ff9b7e1b367172f18ba7f693
Gah.. okay https://wiki.ubuntu.com/KernelTeam/GitKernelBuild
--
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/1652348
Title:
initrd dhcp fails / ignores valid response
Status in linux pac
Rolling that command against master fails too:
ubuntu@Beta:~/linux$ mainline-build-one
afd2ff9b7e1b367172f18ba7f693dfb62bdcb2dc xenial
*** BUILDING: commit:afd2ff9b7e1b367172f18ba7f693dfb62bdcb2dc series:xenial
abinum: ...
full_version<4.4.0>
version<4.4.0>
long
abinum<040400>
fatal: 'xenial' do
Okay.. this is interesting. It seems like the Ubuntu dev version of
4.10 is actually intermittently failing (?!) I guess the next thing to
do here is keep rebooting on this version of the kernel and see how
often the bug occurs vs doesn't occur, so I can get a feel for a
reasonable number of time
I should clarify, I know for certain that 4.4.0-51 is stable and
reliable (and doesn't exhibit the bug). As part of our attempt to
verify everything was correct with the installation we had a system run
from Wednesday before Thanksgiving, all the way through to the following
Monday, during which t
I can give that a shot, following the instructions here:
https://wiki.ubuntu.com/Kernel/KernelBisection#Bisecting_Ubuntu_kernel_versions
--
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/16523
I'll take a fresh look in the morning, but ran into this:
make[1]: Leaving directory
'/home/ubuntu/storage/ubuntu-xenial/debian/build/build-generic/zfs/module'
Debug: module-check-generic
install -d
/home/ubuntu/storage/ubuntu-xenial/debian.master/abi/4.4.0-54.76/amd64
find /home/ubuntu/storage/
Okay... I can't help but think I made a mistake somewhere in the
bisecting process, but it seems to have isolated
fd4b5fa6e3487d15ede746f92601af008b2abbc0 as the bad commit
$ git bisect log
# bad: [6d4f0a79e5a307b6fd3ee3cc5bbb2fcb701b09db] UBUNTU: Ubuntu-4.4.0-57.78
# good: [40a98f0e91bcc062babd0
I see where I messed up.. I'll try the bisect again.
--
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/1652348
Title:
initrd dhcp fails / ignores valid response
Status in linux package in
I bisected again, and again it came back to that mount point change.
This seems so bizarre.
$ git bisect log
# bad: [6d4f0a79e5a307b6fd3ee3cc5bbb2fcb701b09db] UBUNTU: Ubuntu-4.4.0-57.78
# good: [db5f146d309e70067dae57798c9ea679af835aa7] UBUNTU: Ubuntu-4.4.0-53.74
git bisect start 'Ubuntu-4.4.0-57.
This seems to make no sense to me, as a layman anyway.
I checked out the 4.4.0-58.79 tag, reverted that one commit and
confirmed I have a booting 4.4.0-58-generic that'll happily DHCP in the
initrd environment on multiple boots. It really does seem like,
somehow, that commit is the source of the
I tried reverting that specific commit from upstream, but that didn't
resolve the issue. Time for a new round of bisecting the kernel, this
time using mainline.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs
My apologies for any lack of clarity.
I tested against the head of ubuntu-xenial, reverting just that commit
and it fixed it.
I tested against the head of the mainstream kernel and it didn't (last
night I tried 4.9, 4.8, 4.5, 4.4, 4.2 tags of the mainstream kernel and
in every place I find the ge
The more I look at this, the more I'm convinced *most* of the real
problem lies in that ipconfig tool. Yes, various kernel changes seem to
make it alter between working & not working under the circumstances
(which is bizarre), but unless something is specifically interfering
with the inter-process
I've tried every version in the v4 series, and a few in v3. None prior
to (and including) v4.0.0 will boot, none output anything on the screen
to give me a clue why they're not booting.
So far:
v4.0 = won't boot
v4.1 = ipconfig bug
v4.2 = ipconfig bug
v4.3 = ipconfig bug
v4.4 = ipconfig bug
v4.5
** Package changed: 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/1653636
Title:
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-
block(0,
I'm continuing to bisect the mainline linux kernel, and also trying to
see if I can create a straightforward reproducible example.
First focus on bisecting was between 4.5 and 4.6, to figure out what
changed to suddenly have ipconfig working. I've tracked it down to this
using bisect, and validat
I took a step back from doing bisecting and focussed on creating a
replication scenario, which I've done successfully.
ipconfig is struggling to handle things when two interfaces are present
and sending out DHCP requests, even if one interface doesn't get a
response.
Here's what I've done:
Using
** Package changed: ubuntu => bluez (Ubuntu)
** Also affects: gnome-bluetooth (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1694455
T
A number of relevant bug fixes have been committed to the kernel since this
driver was backported. These fixes should probably be backported as well:
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=864db9295b06837d11a260e5dacf99a3fdf6bce2
https://git.kernel.org/cgit/lin
BTW, some Dell Precision 7510 systems (possibly only Xeon systems?) have
a hardware issue where the trackstick or the touchpad or both will
periodically get "stuck" (stop responding briefly) when on A/C power,
when switchable graphics is enabled, when there is significant 2D or 3D
video activity be
When that happens, could you grab the other Alps fixes too?
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1590590/comments/77
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launc
No. If I monitor interrupts, the Alps device actually stops sending
interrupts when the touchpad or trackstick stutters.
--
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/1590590
Title:
To
According to
https://wiki.ubuntu.com/Bugs/FindRightPackage#Hardware_Malfunctions this
bug should have been reported against the Linux kernel.
** Package changed: ubuntu => linux (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to lin
** Package changed: 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/1702253
Title:
hio.ko driver from linux-
image-4.10.0-26-generic_4.10.0-26.30_amd64.deb wi
** 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/1703091
Title:
Kernel panic - not syncing: Fatal exception in inter
** Package changed: xorg (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/1676990
Title:
new kernals wont boot
Status in linux package in Ubuntu:
New
Bug des
** Package changed: 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/1703577
Title:
Java issues with LibreOffice and kernel 4.10.0-26 in Zesty 32bit
Status in lin
** Package changed: ubuntu => bluez (Ubuntu)
** Tags added: zesty
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1693464
Title:
Bluetooth Audio broken for Bose SoundLink Mini
Status in
** Package changed: 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/1694167
Title:
unity does not start when booting with 4.11.3 kernel
Status in linux package i
** Package changed: 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/1699172
Title:
bitwig 1.3.16 don't open with linux 4.8.0-56-generic
Status in linux package i
** Package changed: 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/1704614
Title:
very long kernel boot time with some KVM switch
Status in linux package in Ubu
** Package changed: 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/1705117
Title:
ubuntu 17.04 : Boot failed with luks disk
Status in linux package in Ubuntu:
** Package changed: 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/1656123
Title:
Dualshock 4 (ps4 controller) prevents Ubuntu from booting
Status in linux pack
I'm experiencing this intermittently on a Lenovo ThinkPad T470; I'm
currently running 4.12.0-041200-generic, and it has been patchy
throughout the 4.12.0-rcX series. Anything I can do to gather info?
--
You received this bug notification because you are a member of Kernel
Packages, which is subs
** Package changed: 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/1705921
Title:
Wifi isn't identified for Ampak AP6212
Status in linux package in Ubuntu:
Ne
*** This bug is a duplicate of bug 1659564 ***
https://bugs.launchpad.net/bugs/1659564
** This bug has been marked a duplicate of bug 1659564
linux- image-4.4.0-59-generic. subprocess installed post-installation script
returned error exit status 2
--
You received this bug notification be
*** This bug is a duplicate of bug 1659564 ***
https://bugs.launchpad.net/bugs/1659564
** This bug has been marked a duplicate of bug 1659564
linux- image-4.4.0-59-generic. subprocess installed post-installation script
returned error exit status 2
--
You received this bug notification be
Public bug reported:
We recently noticed that a busy xenial IMAP server with about 22 days
uptime has been logging a lot of OOM messages. The machine has 24G of
memory. Below please find some typical memory info.
I noted that there was about 11G of memory allocated to slab, and since
all of the
** Attachment added: "lspci-vnvn.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1662378/+attachment/4814448/+files/lspci-vnvn.log
--
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
** Package changed: 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/1662589
Title:
Touchpad not working correctly after kernel upgrade
Status in linux package in
** Package changed: 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/1663414
Title:
problem with wireless Network adapter after upgrading to 4.4.0-59
Status in li
I've scheduled install/reboot for Sunday evening UTC, and should be able
to report back a few days after that.
--
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/1662378
Title:
many OOMs on
Zero OOMs after 4 days of uptime (they started after 2 days previously)
so I'd say this is fixed.
--
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/1662378
Title:
many OOMs on busy xenial I
With both 32-bit and 64-bit build of the Lubuntu daily buld (20160326)
I'm seeing this problem using a Toshiba C-50B. Trying to reboot or shut-
down at the end of the ISO test resulted in an indefinite hang and the
use of the on/off button was the method to terminate the session..
** Changed in:
Public bug reported:
Both 32 and 64-bit versions of Lubuntu daily ISO do not poweoff or
reboot when requested so Power button must be used to terminate session.
This may be similar to bug #1552985 but a new bug reported at the
request of Christopher Penalver.
ProblemType: Bug
DistroRelease: Ubun
Unable to update BIOS at this time.
Retested with both 32 and 64-bit ISOs with newer USB drive and both power off
or reboot correctly.
Older USB drive never failed before so had no reason to doubt it. Sorry for any
inconvenience.
Marking bug as "Invalid"
** Changed in: linux (Ubuntu)
Stat
501 - 600 of 1817 matches
Mail list logo
