My bluetooth mouse is connected now, but I had to follow a special
process...
WHAT WORKS:
I had to turn OFF my wireless, make sure bluetooth was ON, and then
connect/pair the mouse.
After the bluetooth mouse connected successfully, I was able to turn wi-fi ON
again.
Now, my mouse
Thanks Remon! Got me up and running!
--
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/1685442
Title:
Errors: flip_done timed out during boot-up; slow boot
Status in linux package in
Same problem for me with XPS 15 (9550). 4.13.0-25 has no problems,
upgraded to 4.13.0-31 and hard-freezes in a minute or so. Currently
trying to upgrade to 4.13.0-32 to test.
Since it is a hard freeze, is there any file I can check for a log after
booting into the previous (4.13.0-25) kernel?
--
Hi Joseph. It's possible, but not ideal in my situation. I'm running
Ubuntu 16.04 server VMs in KVM (via OpenStack) on a CentOS hypervisor,
and I'm unable to easily reproduce the issue as it can occur on any of
the 50+ VMs I have running. I'd prefer not to change the kernel on every
VM if I can
I am running artful 17.10.1 with linux-firmware version 1.169.2.
I am assuming that version 1.169.2 also has the fix??
In any case, it does not work.
Also, the work-around (Comment #17) no longer works for me.
$ uname -r
4.13.0-32-generic
$ lsb_release --all
No LSB modules are
Dear Dino99,
I'm not sure what this means. My system tells me it is running Ubuntu
17.10 (See attached screenshot.)
I checked for any updates and none was recommended.
Do I need to do something else?
Regards ... Geoff Kyle.
Original Message
On January 27, 2018 9:45 PM,
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1745734/+attachment/5044251/+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/1745734
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1745734/+attachment/5044261/+files/RfKill.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: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1745734/+attachment/5044252/+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: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1745734/+attachment/5044260/+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: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1745734/+attachment/5044259/+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: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1745734/+attachment/5044256/+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/1745734
I was unable to collect any logs while running on the suspect kernel as
th system was effectively unusable from desktop or console. I've
collected the logs from the current state running with the reverted
kernel.
--
You received this bug notification because you are a member of Kernel
Packages,
apport information
** Attachment added: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1745734/+attachment/5044254/+files/JournalErrors.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: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1745734/+attachment/5044257/+files/ProcCpuinfo.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/1745734/+attachment/5044255/+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/1745734
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1745734/+attachment/5044258/+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: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1745734/+attachment/5044263/+files/WifiSyslog.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: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1745734/+attachment/5044262/+files/UdevDb.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/1745734/+attachment/5044253/+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
** Tags added: apport-collected
** Description changed:
Today I applied the latest series of updates to 16.04. After rebooting about
80% of the graphics display is corrupted, leaving a strip down the right side
which is still legible. This was evident on the desktop and
With kernel 4.13.0-31 and 4.13.0-32, resume from hibernate freeze every time.
After applying 'no_console_suspend' in grub, some more infos are printed to
console:
PM: quiesce of devices complete after x msec
PM: late quiesce of devices complete after x msec
PM: noirq quiesce of devices
Touchpad still does not work (with "i2c_hid i2c-SYNA3602:00:
i2c_hid_get_input: incomplete report" err in dmesg) as with latest
v4.15-rc9 as with previous 4.15.0-rc7, 4.15.0-rc6, 4.14.0, 4.13.0-17
builds on YEPO 737A.
--
You received this bug notification because you are a member of Kernel
ad #28:
you need to use the canonical-kernel-team/unstable PPA!
--
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/1742675
Title:
after upgrade to linux-image-extra-4.13.0-26-generic
ad #27:
for a very recent kernel, you could try 4.14.0-17 from the canonical-
kernel-team PPA: for me (Dell e6500) it runs reliably.
However, you need the boot option acpi=off.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
Well of course right after I file this, it hangs. So this may not be
the kernel after 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/1745768
Title:
system hangs within 10 minutes
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/1745768
Title:
system hangs within 10
Public bug reported:
I cannot run for very long under normal operational load using linux-
image-4.13.0-32-generic without a complete system freeze (mouse no
longer moves, keyboard no longer responsive). I have worked around this
by booting back into linux-image-4.13.0-31-generic which is
Still failing under kernel 4.13.0-32 x86_64 with `nopti` parameter
added.
I'm running 17.10 Wayland on a Dell XPS 9560.
--
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/1743094
Title:
I'm not seeing this spammed in dmesg. Only maybe once per boot, but I'm
seeing the following on my 9360 running Ubuntu 17.10:
[ 4649.396767] pcieport :00:1c.4: AER: Corrected error received: id=00e4
[ 4649.396784] pcieport :00:1c.4: PCIe Bus Error: severity=Corrected,
type=Data Link
I'm seeing something slightly different. MokListRT vs dbx list. Is it
the same issue?
[1.066401] Couldn't get size: 0x800e
[1.066403] MODSIGN: Couldn't get UEFI MokListRT
[1.066728] zswap: loaded using pool lzo/zbud
--
You received this bug notification because you are
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/1745758
Title:
package
Public bug reported:
I just did:
sudo apt update
sudo apt upgrade -y
sudo apt dist-upgrade -y
and this bug/error popped up.
Note: I have had this happen on a 2nd Ubuntu 17.10 system as well.
ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: linux-headers-4.13.0-32-generic 4.13.0-32.35
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1745734
and then change the status of the bug to 'Confirmed'.
If, due to the
Public bug reported:
When upgrading to 1.169.3 and after reboot, the wifi stopped working.
`lshw -C network` shows the wifi card while `rfkill list` shows only the
bluetooth adapter.
Reverting back to 1.169.2 make the wifi card work again.
Note that I am using an upgraded Ubuntu 17.10 with the
If you think that the kernel is at fault then the bug should be filed against
"linux".
Reassigning...
** 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
You have been subscribed to a public bug:
Today I applied the latest series of updates to 16.04. After rebooting about
80% of the graphics display is corrupted, leaving a strip down the right side
which is still legible. This was evident on the desktop and also the virtual
consoles.
That version is now dead
http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Kernel
Packages,
That version is now dead
http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Kernel
Packages,
That version is now dead
http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Kernel
Packages,
That version is now dead
http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Kernel
Packages,
That version is now dead
http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Kernel
Packages,
That version is now dead
http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Kernel
Packages,
That version is now dead
http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Kernel
Packages,
That version is now dead
http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Kernel
Packages,
That version is now dead
http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Kernel
Packages,
That version is now dead
http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Kernel
Packages,
That version is now dead
http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Kernel
Packages,
That version is now dead
http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Kernel
Packages,
That version is now dead
http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Kernel
Packages,
That version is now dead
http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Kernel
Packages,
That version is now dead
http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Kernel
Packages,
That version is now dead
http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Kernel
Packages,
That version is now dead
http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Kernel
Packages,
That version is now dead
http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Kernel
Packages,
That version is now dead
http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Kernel
Packages,
I am also affected - all version of 4.13 released so far do not boot. I
also have reverted to 4.10.0.42. Xubuntu 16.04.3 installed on Dell
e6430 laptop Intel/nVidia Graphics no dual-boot. I would echo the
sentiments of an earlier poster - how can this continue through 3+
releases with no
That version is now dead
http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Kernel
Packages,
That version is now dead
http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Kernel
Packages,
That version is now dead
http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml
** Changed in: dkms (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which
That version is now dead
http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Kernel
Packages,
That version is now dead
http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Kernel
Packages,
Keep in mind that the 4.14.x PPA kernels also have PTI enabled, still
hibernation works fine with them.
--
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/1743094
Title:
[regression]
Adding nopti to kernel command line doesn't solve the issue for me.
Tested with the Kernel 4.13.0-32 on Lenovo Thinkpad T470.
--
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/1743094
Title:
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/1745740
Title:
[Xenial] Update to kernel
Public bug reported:
[Description]
After updating from 4.4.0-111 to the latest 4.4.0-112, the system with
enabled BIOS SecureBoot mode will fail to boot because of "Operating
System Loading signature not found in SecureBoot database" prompted by
BIOS (See the attachment picture)
[Steps to
I can confirm that this is not fixed in kernel v4.15-rc1.
I can see the device:
---
$ cat /sys/bus/thunderbolt/devices/0-1/device_name
Thunderbolt to FireWire Adapter
---
.. but it doesn't show up in lspci, and it doesn't look like drivers can
bind to it (I'm trying with libffado). Cold- or
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/1745727
Title:
Wifi stops working on Del XPS
Unfortunately, "nopti" (GRUB_CMDLINE_LINUX_DEFAULT="nopti loglevel=7
no_console_suspend") does not at all make a difference for me.
Tested hibernate-resume cycles with 4.13.0-25, 4.13.0-26, 4.13.0-31 and
4.13.0-32.
--
You received this bug notification because you are a member of Kernel
Public bug reported:
I am running a a Dell XPS 9360 laptop and the wifi started to sometime "hang"
this week after an update (not sure which one).
Running Ubuntu 17.10 (upgraded from Gnome Ubuntu recently)
$lsb_release -rd
Description:Ubuntu 17.10
Release:17.10
I observed that five~
** Tags added: kernel-bug-exists-upstream
** Attachment added: "System info"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1744546/+attachment/5043911/+files/Infos%20of%20the%20Computer.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is
kernel-bug-exists-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/1744546
Title:
systemd boot and kernel
With the last kernel (4.15 rc9) I no longer have the message of Error
"The bug is tpm_crb MSFT0101:00: [firmware bug] acpi region does not
cover..."
But Ihave the same bug "watchdog: BUG: soft lockup - CPU#0 stuck for
23s..."
--
You received this bug notification because you are a member of
73 matches
Mail list logo
