I confirm on kernels 4.15.0.19 and 4.15.0.20.
root@CmsrvLAP2:~# umount /media/Cmsrv*
root@CmsrvLAP2:~# mount -l | grep cifs
root@CmsrvLAP2:~# mount -a
root@CmsrvLAP2:~# dmesg | tail
[5.353312] CIFS VFS: ioctl error in smb2_get_dfs_refer rc=-5
[5.354716] CIFS VFS: ioctl error in smb2_get_df
I haven't had a single undock that worked, but I only tried with the
18.04 live installer, so guess that kernel already may be behind...
My hardware is a Lenovo X1 Carbon 5th generatin and a Lenovo ThinkPad
Thunderbolt 3 Dock
--
You received this bug notification because you are a member of Kern
[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
[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
[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
[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
the commit should be the same as 1645959.
** Tags added: intel-kernel-18.10
** Description changed:
CNL will have eMMC5.1 capable host controller that includes new features:
1) Command queue support – making the data transfers highly efficient by
offloading the software overhead into the co
[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
** Tags added: kernel-fixed-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/1767360
Title:
16.04 LTS boot failure with linux-image-4.4.0-122-generic, linux-
image-4.4.0-121-gen
[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
[Expired for linux-firmware (Ubuntu) because there has been no activity
for 60 days.]
** Changed in: linux-firmware (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
ht
[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
[Expired for bluez (Ubuntu) because there has been no activity for 60
days.]
** Changed in: bluez (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bu
I reproduced this this afternoon with the latest stable kernel (4.16.6.)
See attached subset of the kernel log. I'll try with 4.17 tomorrow.
** Attachment added: "kern2.log"
https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1767452/+attachment/5131193/+files/kern2.log
--
You recei
[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
I found some drivers here:
http://www.asix.com.tw/download.php?sub=driver
--
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/1688081
Title:
USb-Ethernet ASIX A88772 stops working after kerne
[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
[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
[Expired for linux-signed (Ubuntu) because there has been no activity
for 60 days.]
** Changed in: linux-signed (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
https://
[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
[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
[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
Used kernel: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.16/
It boots/works.
Added tag and changed status as requested. 1st time Launchpad user so hope I
did it correctly.
Thanks for the help.
--
You received this bug notification because you are a member of Kernel
Packages, which is subsc
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Changed in: linux (Ubuntu Xenial)
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/b
Status changed to 'Confirmed' because the bug affects multiple users.
** 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/1768121
same issue here
--
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/1768121
Title:
Mainline Kernel since 4.16.4 has postinstall script error
Status in linux package in Ubuntu:
Confirmed
B
The problem seems to be missing firmware for your bluetooth chip. The
kernel is trying to load it and can't find it. Because package 'linux-
firmware' is missing those files.
This is very similar to:
https://bugzilla.kernel.org/show_bug.cgi?id=99481
https://bugzilla.kernel.org/show_bug.cgi?id=1126
As a data point for future googlers, I had what sounds like the
same/similar problem today, my middle-button-click stopped working.
Except I found that it was working but I had to hold it down for a few
hundred ms until it reliably clicked, sometimes quickly clicking in
succession would report som
Looks like the problem may be:
abr 30 13:11:02 miguel-ubuntu kernel: bluetooth hci0: Direct firmware load for
brcm/BCM20702A1-0a5c-21e6.hcd failed with error -2
abr 30 13:11:02 miguel-ubuntu kernel: Bluetooth: hci0: BCM: Patch
brcm/BCM20702A1-0a5c-21e6.hcd not found
abr 30 13:12:15 miguel-ubunt
** Tags added: bionic xenial
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-utopic in Ubuntu.
https://bugs.launchpad.net/bugs/1475639
Title:
Atheros QCA9565 bluetooth hardware not detected
Status in linux package in Ubuntu:
same problem here with 16.4,5,6 16.3 installed fine
--
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/1768121
Title:
Mainline Kernel since 4.16.4 has postinstall script error
Status in lin
Per the previous entry, I have retested for this issue with upstream
kernel 4.16.6-041606-generic. No change in DPMS behavior was observed,
i.e., power save for the monitor does not seem to be enabled.
** Tags added: kernel-bug-exists-upstream
--
You received this bug notification because you a
** Tags added: patch
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
https://bugs.launchpad.net/bugs/1768162
Title:
kernel crashes during boot unless IOMMU is disabled on AMD Cpu
Status in linux-signed package i
** Tags added: intel
** Tags removed: intel
** Tags added: intel-kernel-18.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/1591607
Title:
[Feature]Intel PT: Script Interface for appli
Public bug reported:
Previous
- IOMMU was enabled under Ubuntu 16.04 LTS Kernel 4.4 - No Issues
Current
- After upgrading to 18.04 with kernel 4.15 systems crashes with IOMMU enabled
- Disabling IOMMU within the BIOS allow booting with 4.15 kernel
- Enabling IOMMU and switching to 4.4 bo
** Information type changed from Private Security to Public Security
--
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/1763384
Title:
Null-Pointer Deference in hfs.ko (Linux 4.15.0-15.16)
After a fresh install of Ubuntu 18.04 (about an hour ago) on my Gigabyte
P55W v5, and same problem: right after logging in, everything freezes...
and that's about it. I waited for 15 minutes, and nothing happened.
--
You received this bug notification because you are a member of Kernel
Packages,
I discovered a way to cause this instantly, I attempted to change the
size of the ring buffers from 512 bytes to the hardware maximum of 4096
using: ethtool -G eno1 rx 4096 tx 4096, it instantly hung the interface
with the following in dmesg:
[458611.154752] e1000e :00:19.0 eno1: Detected Hard
move this into 18.10. Upstream is still working on that
** Description changed:
Add a (python/perl) scripting interface for Intel Processor Trace to Linux
perf tools. The interface should enable analysis of Intel PT traces, providing
customizable filtering and selection of events and event st
I think this should be done.
--
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/1704698
Title:
[Feature] Northpeak Enabling
Status in intel:
Incomplete
Status in linux package in Ubuntu:
Public bug reported:
Recently, a couple of fixes went in vmxnet3 driver related to LRO, transmit
reset and rxvlan disabled fix. Below are the commits:
https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=7a4c003d6921e2af215f4790aa43a292bdc78be0
https://git.kernel.org/pub/scm/
Public bug reported:
When I boot a Dell Inspiron 7559 with an external monitor connected to
the hdmi port I get a crash on bootup. I can see the following stack
trace in journalctl:
Apr 30 16:52:19 exposure systemd[1]: Started Show Plymouth Boot Screen.
Apr 30 16:52:19 exposure systemd[1]: Reache
** Tags added: patch
--
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/1766727
Title:
initramfs-tools exception during pm.DoInstall with do-release-upgrade
from 16.04 to 18.04
Status in
Python2 will not be maintained upstream past 2020, so a lack of python3
bindings certainly feels like a non-starter. As for why the kernel team
decided to drop the python build-dep in 13.04, I'm not sure, and it's a
conversation worth having.
--
You received this bug notification because you are
Public bug reported:
Hello,
I don't know who does the packaging for the Mainline
Kernel(http://kernel.ubuntu.com/~kernel-ppa/mainline/), but it has been
erroring out in packaging and also for the packages in x64/32 that have
made it, there are post install script errors within the packaging which
So I tried the latest upstream kernel of 4.16 which at the moment was
4.16.6.Bluetooth still not working at the moment.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Tags removed: apport-collected bionic staging
** Tags added: kernel-bug-exists-upstream
--
You received
** Changed in: kernel-sru-workflow/security-signoff
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1766605
Title:
linux-aws: 4.4.0-1018.18
** 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/1767667
Title:
kernel crash in gnome environment
Status in linux pa
You have been subscribed to a public bug:
Apr 28 10:30:44 tatanka gnome-system-mo[4199]: Allocating size to
gnome-system-monitor 0x16542b0 without calling
gtk_widget_get_preferred_width/height(). How does the code know the size to
allocate?
Apr 28 10:35:49 tatanka kernel: [52343.54] gmc_v9_
--- Comment From dougm...@us.ibm.com 2018-04-30 15:31 EDT---
Both logs show that the dmesg buffer has been overrun, so by the time you get
to xmon and run "dl" you've lost the messages that show what happened before
things went wrong. You will need to be collecting console output from the
--- Comment From bren...@br.ibm.com 2018-04-30 15:20 EDT---
I tried to reproduce this on my machine and I was not able to. I am using
kernel 4.15.0-20-generic and I run:
# ltp-install pwd
/home/breno/ltp-install
# ltp-install sudo ./runltp
Is there any other way to reproduce it?
--
** Changed in: kernel-sru-workflow/security-signoff
Status: In Progress => 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/1766601
Title:
linux: 3.13.0-146.195 -propos
** Changed in: kernel-sru-workflow/security-signoff
Status: In Progress => 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/1766604
Title:
linux: 4.4.0-123.147 -propose
** Also affects: ubuntu-power-systems
Importance: Undecided
Status: New
** Changed in: ubuntu-power-systems
Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)
** Changed in: ubuntu-power-systems
Importance: Undecided => High
** Tags added: triage-g
--
You
Default Comment by Bridge
** Attachment added: "guest libvirt xml"
https://bugs.launchpad.net/bugs/1768115/+attachment/5130966/+files/boslcp3g1.xml
** Changed in: ubuntu
Assignee: (unassigned) => Ubuntu on IBM Power Systems Bug Triage
(ubuntu-power-triage)
** Package changed: ubuntu =>
** Changed in: kernel-sru-workflow/security-signoff
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem in Ubuntu.
https://bugs.launchpad.net/bugs/1766599
Title:
linux-oem: 4.13.0-1025.28
You have been subscribed to a public bug:
Problem Description: Migration Guest running with IO stress
crashed@security_file_permission+0xf4/0x160 after couple of migrations.
Steps to re-create:
Source host - boslcp3
Destination host - boslcp4
1.boslcp3 & boslcp4 installed with latest kernel
ro
** Changed in: kernel-sru-workflow/security-signoff
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-gcp in Ubuntu.
https://bugs.launchpad.net/bugs/1766596
Title:
linux-gcp: 4.13.0-1014.18
** Changed in: kernel-sru-workflow/security-signoff
Status: In Progress => 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/1766592
Title:
linux: 4.13.0-40.45 -proposed
** Also affects: linux (Ubuntu Bionic)
Importance: Critical
Status: Confirmed
** Changed in: linux (Ubuntu Bionic)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https:
** Also affects: s390-tools (Ubuntu Bionic)
Importance: Undecided
Status: Fix Released
** Also affects: initramfs-tools (Ubuntu Bionic)
Importance: Undecided
Status: Invalid
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: Invalid
** Also affects
** Changed in: linux (Ubuntu Bionic)
Status: In Progress => Fix Committed
--
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/1767133
Title:
linux-image-4.15.0-20-generic install after
Forgot to mention that everything is running on top of NVIDIA-390
package for GTX 1060
--
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/1767586
Title:
Boot freezes with Gdm3
Status in lin
I have installed the following files:
linux-headers-4.17.0-041700rc3_4.17.0-041700rc3.201804300800_all.deb
linux-headers-4.17.0-041700rc3-generic_4.17.0-041700rc3.201804300800_amd64.deb
linux-image-unsigned-4.17.0-041700rc3-generic_4.17.0-041700rc3.201804300800_amd64.deb
linux-modules-4.17.0-04170
** Summary changed:
- linux: -proposed tracker
+ linux: 4.15.0-21.22 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/prepare-package
Assignee: Canonical Kernel Team (canonical-kernel-team) => Th
Hello.
I just wanto to confirm: everything seems to be okay after updating
Linux kernel to v4.4.0-123-generic. However, I would like to ask a
question about 'intel-microcode' and 'amd64-microcode' packages. During
system updating process via apt(8), there was an information that "The
following NEW
** Changed in: linux (Ubuntu)
Status: New => Triaged
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Tags added: kernel-da-key
** Also affects: linux (Ubuntu Bionic)
Importance: High
Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage)
St
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Status: New => Triaged
--
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/1767905
Title:
Public bug reported:
We have discovered that an early asic model (A0) of our 16/32GB HBA's doesn't
boot with the lpfc driver in Ubuntu 18.04.
After further review and discussion, this has been deemed a low risk
issue since early A0 HBA's were only ever shipped to OEMs for test
purposes. The
Public bug reported:
Note that the symlinks point to "linux-azure-edge-headers" but the
directory is actually named "linux-azure-headers". This breaks DKMS
modules.
jrp@jrpcudau:/usr/src/linux-headers-4.15.0-1006-azure$ ls -l
total 940
drwxr-xr-x 3 root root 4096 Apr 19 16:06 arch
lrwxrwxrwx 1
Hello Anthony, or anyone else affected,
Accepted linux-firmware into xenial-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/1.157.18 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Amitkumar, or anyone else affected,
Accepted linux-firmware into xenial-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/1.157.18 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. S
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.16 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix t
Accepting this for xenial. Normally we'd block until the fix is in the
devel release, but in this case the required firmware is not present in
that release (so we're not regressing with the upgrade path). But please
SRU the fixes with the firmware itself to bionic if ready.
--
You received this b
Hello Seth, or anyone else affected,
Accepted linux-firmware into xenial-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/1.157.18 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
ht
Hello Amitkumar, or anyone else affected,
Accepted linux-firmware into xenial-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/1.157.18 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. S
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Bionic)
Status: New => Triaged
** Changed in: linux (Ubuntu Bionic)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Kernel
We've seen a similar-sounding issue in the past, but couldn't get it
tracked down to the root cause.
Is it possible to enable some instrumentation in the /etc/network/interfaces and
obtain some data on a failing occurrence?
What we've used in the past is adding something like
pre-up echo 'file b
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.16 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix t
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.16 kernel[
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.16 kernel[
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.16 kernel[
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.16 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix t
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Status: New => Triaged
** Tags added: kernel-da-key
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launc
You have been subscribed to a public bug:
My laptop is a 2 in 1 model so I don't know if it's because Linux kernel
still can't fully support this kind of device or some other reason but I
really want to use Ubuntu as my study system because I am a computer
science student and the moment I had the
You have been subscribed to a public bug:
After a simple upgrade with 16.04.1-Ubuntu to kernel 4.13.0-39.44, the
authentication against 802.1x secured networks does not work anymore.
If I boot via an older kernel (4.13.0-37), networking works like a charm.
Other connections like DHCP, static IP o
Hello dann, or anyone else affected,
Accepted linux-firmware into artful-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/1.169.4 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
htt
Hello Timo, or anyone else affected,
Accepted linux-firmware into artful-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/1.169.4 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
htt
** Tags added: bionic manpage
--
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/1767971
Title:
No such man page: kernel_lockdown.7
Status in linux package in Ubuntu:
New
Bug description
The verification of the Stable Release Update for zfs-linux has
completed successfully and the package has now been released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter
This bug was fixed in the package kexec-tools - 1:2.0.10-1ubuntu2.5
---
kexec-tools (1:2.0.10-1ubuntu2.5) xenial; urgency=medium
* The default crashkernel parameter didn't work on any known arm64
systems, set a reasonable default instead (LP: #1763532).
-- dann frazier Fri,
This bug was fixed in the package zfs-linux - 0.6.5.11-1ubuntu3.4
---
zfs-linux (0.6.5.11-1ubuntu3.4) artful; urgency=medium
* Add ZFS 0.7.0 compat fix for zvol_id (LP: #1763067)
The BLKZNAME ioctl msg size has changed in ZFS 0.7.0 so
add forwards compat handling for this io
This bug was fixed in the package zfs-linux - 0.6.5.6-0ubuntu21
---
zfs-linux (0.6.5.6-0ubuntu21) xenial; urgency=medium
* Add ZFS 0.7.0 compat fix for zvol_id (LP: #1763067)
The BLKZNAME ioctl msg size has changed in ZFS 0.7.0 so
add forwards compat handling for this ioctl
** Changed in: zfs-linux (Ubuntu)
Status: In Progress => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1763067
Title:
zvol_id throws ioctl_get_msg failed:Inappropriat
As far as I understand from my testing with xev, xinput test and evtest
there is no issue with the kernel but instead the problem is somewhere
inside xorg.
** Package changed: linux-signed (Ubuntu) => xorg (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages
--- Comment From gwal...@br.ibm.com 2018-04-30 13:07 EDT---
Submitted
https://lists.ubuntu.com/archives/kernel-team/2018-April/092069.html
https://lists.ubuntu.com/archives/kernel-team/2018-April/092070.html
https://lists.ubuntu.com/archives/kernel-team/2018-April/092071.html
--
You recei
The verification of the Stable Release Update for makedumpfile has
completed successfully and the package has now been released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encoun
I have just tested with the latest mainline kernel,
4.17.0-041700rc3-generic, and it is still not working. In the command
line, I tried to trigger a manual scan using bluetoothctl, but it says
"No default controller available".
Also, if it helps, here is a pastebin containing my journalctl
https:/
This bug was fixed in the package makedumpfile - 1:1.6.1-2ubuntu0.2
---
makedumpfile (1:1.6.1-2ubuntu0.2) artful; urgency=medium
* kdump-tools: Add reasonable default 'crashkernel' parameter and kdump
kernel cmdline for arm64. The files that contain the default kernel
cmdlin
This bug was fixed in the package makedumpfile - 1:1.5.9-5ubuntu0.7
---
makedumpfile (1:1.5.9-5ubuntu0.7) xenial; urgency=medium
* kdump-tools: Add reasonable default kdump kernel cmdline for arm64.
The files that contain the default kernel cmdline are now generated
per-arch
1 - 100 of 178 matches
Mail list logo