I just upgraded to 4.4.0-91 from the main repository, and it boots
again!
All my virtual machines are running too.
Looks like this is fixed in something which was changed between -89 and
-91.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
I can't provide the Apport logs; it asks me to log in to Launchpad using
Lynx, then fails with "Bad bot!"
Is there an alternative way to do this? The machine is a headless
server.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because
This looks a lot like what I'm seeing on #1709511
I'm running qemu+kvm virtual machines.
--
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/1709564
Title:
Kernel bug after upgrade to 4.4.0-
I'd like to provide a better backtrace if it's needed, but I'm not sure
how to do this.
Attaching lspci -vnvn
** Attachment added: "lspci-vnvn.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1709511/+attachment/4929105/+files/lspci-vnvn.log
--
You received this bug notification be
Public bug reported:
After applying the 4.4.0-89 kernel update, I get a panic on boot.
4.4.0-87 boots normally.
I expected that 4.4.0-89 would boot normally (as 4.4.0-87) instead of crashing.
Systemd displays an announcement: "Starting udev Wait for Complete Device
Initialization...", then I
** Attachment added: "version.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1709511/+attachment/4929106/+files/version.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/bugs/170
I've just released version 1.4.2 which fixes the two QL-570 bugs raised
by Ladislav Laska.
Bug #1607917 open to (hopefully) get the upstream packages updated.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to hwdata in Ubuntu.
https://bugs.
I've managed to source a slightly-used QL-570 for a more reasonable
price, along with (apparently) five rolls of labels. That should be
arriving "soon-ish".
I'll have a look at the driver when I get a spare moment. As I've said
on the upstream ticket, the negative-print bug looks like the thing
lo
Upstream version bumped to 1.4.1.
Be advised that there's an open ticket on QL-570 support:
https://bitbucket.org/philpem/printer-driver-ptouch/issues/2
/negativeprint-and-cutmedia-jobend-doesnt
Main issue is that media cutting apparently doesn't work 100% as
described on QL printers. Unless/unti
9 matches
Mail list logo