trusty + linux-virtual-lts-xenial looks good also.
ubuntu@sm-y1:~$ uname -r
4.4.0-38-generic
ubuntu@sm-y1:~$ dpkg -S /boot/vmlinuz-$(uname -r)
linux-image-4.4.0-38-generic: /boot/vmlinuz-4.4.0-38-generic
ubuntu@sm-y1:~$ grep overlay /proc/mounts
overlayroot / overlayfs rw,relatime,lowerdir=/media
OK, i recreated with simple:
uvt-kvm create sm-y1 release=yakkety
uvt-kvm ssh --insecure sm-y1
% echo "root:passw0rd" | sudo chpasswd
% sudo apt-get update && sudo apt-get dist-upgrade && sudo reboot
...
then at the virsh console i see the fail, log in and:
root@sm-y1:~# mount /dev/disk/by-
** No longer affects: cloud-init
--
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/1618572
Title:
apt-key add fails in overlayfs
Status in linux package in Ubuntu:
Confirmed
Status in li
I tried to pair today using bluetoothctl but all I got back was
Failed to pair: org.bluez.Error.AuthenticationRejected
and the same "failed" message on the radio display.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
h
** Branch linked: lp:~ssweeny/bluez/snappy-interface
--
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/1560094
Title:
Starting bluez service is denied
Status in bluez package in Ubuntu:
Still didn't work for me.
** Attachment added: "syslog part containing pairing attempt"
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1552410/+attachment/4640867/+files/syslog-snippet
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribe
** Attachment added: "ubuntu-system-settings log"
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1552410/+attachment/4640868/+files/application-legacy-ubuntu-system-settings-.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bl
Here's the syslog snippet from when I tried pairing using bluetoothctl
** Attachment added: "syslog part containing pairing attempt using bluetoothctl"
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1552410/+attachment/4641441/+files/syslog-snippet-bluetoothctl
--
You received this bug
** Attachment added: "hcidump of a pairing attempt"
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1552410/+attachment/4643207/+files/hcidump-hr.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.la
Attaching a script that shows the failure without downloading an image.
** Attachment added: "script to show failure"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1628336/+attachment/4749866/+files/show-fail.sh
--
You received this bug notification because you are a member of Kernel
Public bug reported:
This fails on 4.8.0-17-generic and passes on
$ sudo apt-get update
$ sudo apt-get install -qy cloud-image-utils
$ wget
http://cloud-images.ubuntu.com/xenial/current/xenial-server-cloudimg-amd64-disk1.img
$ cp xenial-server-cloudimg-amd64-disk1.img disk.img
$ sudo mount-image
** Description changed:
- This fails on 4.8.0-17-generic and passes on
+ This fails on 4.8.0-17-generic and passes on 4.4.0-9136-generic
$ sudo apt-get update
$ sudo apt-get install -qy cloud-image-utils
$ wget
http://cloud-images.ubuntu.com/xenial/current/xenial-server-cloudimg-amd64-di
I have this problem as well. Was already running 16.10 Development branch
successfully, I think that when 16.10 was released that the next sudo apt
update / upgrade changed something. I started getting errors that updates
needed to be applied, but some lock file was read-only; then whole screen
I am not running the low latency kernel, just generic kernel. I was
successfully using both AMD CPU (proprietary driver) AND the NVIDIA proprietary
driver.
I tried tweaking the UEFI settings, but made things worse. So I switched the
settings back.
--
You received this bug notification because
Public bug reported:
I booted a yakkety system on azure, and saw
$ systemctl status hv-fcopy-daemon.service --no-pager --full
● hv-fcopy-daemon.service - Hyper-V File Copy Protocol Daemon
Loaded: loaded (/lib/systemd/system/hv-fcopy-daemon.service; enabled; vendor
preset: enabled)
Active
Public bug reported:
I launched 2 different yakkety systems on azure instance types:
Basic_A0
Standard_D1_v2
More information what those things are at :
https://azure.microsoft.com/en-us/pricing/details/virtual-machines/linux/
systemd-analize says:
## Basic A0
smoser@sm-y-d1v2-1:~$ systemd
** Description changed:
I launched 2 different yakkety systems on azure instance types:
Basic_A0
Standard_D1_v2
More information what those things are at :
https://azure.microsoft.com/en-us/pricing/details/virtual-machines/linux/
systemd-analize says:
- ## Standard D1 v2
-
I just launched 1 instance of xenial and of trusty with the same user-
data, both of these were 'Standard_D1_v2' type. They do not seem to
have such bad performance. trusty does not have systemd-analyze, but
i've included 'dmesg | grep sda1.*mounted' for each, which shows quite a
difference to the
Public bug reported:
We have a "virtual maas" setup where we have a maas node on a linux
bridge (created by libvirt) and some other number of nodes on that same
bridge.
the maas node then controls the other nodes turning them on and off and
generally working maas-like magic.
In this scenario on
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
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/1618572
Title:
cloud-init failing to configure sources and addi
This seems to be a kernel regression that happened either in 4.4 or 4.2.
I'll get more information on recreate soon. to get this off my system,
here are my very sloppy notes http://paste.ubuntu.com/23117619/
essentially, you boot a cloud image with overlayroot enabled then 'apt-key add
- https
x86_64
NonfreeKernelModules: wl
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: scott 1702 F pulseaudio
/dev/snd/pcmC0D0p: scott 1702 F...m pulseaudio
/dev/snd/controlC0: scott 1702 F pulseaudio
If we're not close to a solution... I'm tempted to suggest creating
daily saucy images with 'ethtool -K eth0 sg off' running on ifup, via
some injected network config script.
it could look like this.
$ cat /etc/network/if-up.d/bug-1200243
#!/bin/sh
[ "$IFACE" = "eth0" ] || exit 0
kver=$(uname -r
I've just verified on saucy daily images that this seems to be work-aroundable
by launching with user-data containing a boothook that will run ethtool -K eth0
gso off.
example cloud-config:
#cloud-config
apt_update: true
apt_upgrade: true
packages: [ pastebinit ]
output: {all: '| tee -a /var/log
Public bug reported:
on azure saucy images
(b39f27a8b8c64d52b05eac6a62ebad85__Ubuntu_DAILY_BUILD-saucy-
13_10-amd64-server-20130718-en-us-30GB in 'US East' location). I get a
300 second timeout before / is mounted RW.
See attached dmesg for full dmesg. snippet here.
[6.974849] scsi3 : stor
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1202700/+attachment/3741337/+files/ProcCpuinfo.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/b
apport information
** Tags added: apport-collected saucy uec-images
** Description changed:
on azure saucy images
(b39f27a8b8c64d52b05eac6a62ebad85__Ubuntu_DAILY_BUILD-saucy-
13_10-amd64-server-20130718-en-us-30GB in 'US East' location). I get a
300 second timeout before / is mounted RW.
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1202700/+attachment/3741336/+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/1202700
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1202700/+attachment/3741339/+files/ProcModules.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/b
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1202700/+attachment/3741338/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad
apport information
** Attachment added: "UdevLog.txt"
https://bugs.launchpad.net/bugs/1202700/+attachment/3741341/+files/UdevLog.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/1202
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1202700/+attachment/3741340/+files/UdevDb.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/1202700
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1202700/+attachment/3741342/+files/WifiSyslog.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/bug
$ echo "deb http://archive.ubuntu.com/ubuntu $(lsb_release -sc)-proposed main"
| sudo tee /etc/apt/sources.list.d/proposed.list
$ sudo apt-get update
$ sudo apt-get install linux-virtual
$ apt-cache policy linux-virtual
linux-virtual:
Installed: 4.2.0.19.21
Candidate: 4.2.0.19.21
Version tab
This is happening on my Lenovo T510 which uses Nvidia so I don't think
the video driver has anything to do with it. This bug (for me) is also
the worst kind in that it's intermittent. Tonight, the system locked up
when I forgot about this problem and it hosed a partition that was in
the middle of b
Public bug reported:
standard periodic update was being processed - had a few programs open
at the time usually this does not impact the update process
ProblemType: Package
DistroRelease: Ubuntu 15.10
Package: linux-image-4.2.0-19-generic (not installed)
ProcVersionSignature: Ubuntu 4.2.0-18.22-g
s/out.diff
** Changed in: cloud-init
Importance: Undecided => High
** Changed in: cloud-init
Status: New => Confirmed
** Changed in: cloud-init
Assignee: (unassigned) => Scott Moser (smoser)
** Also affects: cloud-init (Ubuntu)
Importance: Undecided
Status: New
Public bug reported:
We've made some progress on bug 1499869 , such that on Friday I actually had
successful installs.
An attempt at an install today shows a kernel stack trace early in the boot,
then the initramfs not finding any network devices and thus failing to mount
the iscsi root.
The t
** 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/1502946
Title:
kernel crash on m400 arm64 server cartridge
Status in
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1502946/+attachment/4485082/+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/1502946
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1502946/+attachment/4485083/+files/ProcCpuinfo.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/b
apport information
** Tags added: apport-collected trusty uec-images
** Description changed:
We've made some progress on bug 1499869 , such that on Friday I actually had
successful installs.
An attempt at an install today shows a kernel stack trace early in the boot,
then the initramfs not
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1502946/+attachment/4485084/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1502946/+attachment/4485086/+files/UdevDb.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/1502946
apport information
** Attachment added: "UdevLog.txt"
https://bugs.launchpad.net/bugs/1502946/+attachment/4485087/+files/UdevLog.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/1502
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1502946/+attachment/4485085/+files/ProcModules.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/b
apport information
** Attachment added: "BootDmesg.txt"
https://bugs.launchpad.net/bugs/1502946/+attachment/4485081/+files/BootDmesg.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/
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1502946/+attachment/4485088/+files/WifiSyslog.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/bug
marked as confirmed.
I collected info running trusty kernel as current wily wont boot.
--
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/1502946
Title:
kernel crash on m400 arm64 server car
** Changed in: linux (Ubuntu)
Importance: Undecided => Critical
--
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/1502946
Title:
kernel crash on m400 arm64 server cartridge
Status in li
what provides (or should create) /etc/kernel.conf ?
--
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/1536810
Title:
kernel install failed /bin/cp: cannot stat
‘/boot/initrd.img-4.3.0-7-g
** Attachment added: "script reproducing problem"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1536810/+attachment/4556461/+files/reproduce.sh
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launch
I've checked, and the file exists. the content is
# Kernel Image management overrides
# See kernel-img.conf(5) for details
do_symlinks = yes
do_bootloader = no
link_in_boot = yes
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubu
For reference, show-kernel-img-conf.
this downloads cloud images and extracts the questioned file.
Note, there is a change in this file from wily to xenial, but the change is in
place for all arch, and i'm only seeing these build failures in arm64 and armhf.
== wily armhf [wily-server-cloudimg-a
Note, there are 2 changes fom wily to xenial in the content of that file:
a.) for arches other than amd64, we gain the 'link_in_boot = yes'
b.) there is a case change for the 'do_symlinks' setting from wily ('Yes') to
xenial ('yes')
--
You received this bug notification because you are a membe
It seems to be 'a' that causes the failure.
If i remove 'link_in_boot' then it works.
I've committed a change to maas-iamges to work around this at least temporarily
http://bazaar.launchpad.net/~maas-images-maintainers/maas-images/maas-ephemerals/revision/268
--
You received this bug notifica
It'd be nice to track down why images have this change from wily in
them, especially since it is not helpful.
--
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/1536810
Title:
kernel install
"the kernel at least created the configuration".
I don't know where the file came from, but that is the file that is in
official ubuntu cloud images, built by livefs.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https:
We really need to understand what is creating this file because
apparently in live build, its not the installation of a kernel.
--
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/1536810
Title
** Description changed:
Hi, this failure for kernel package installation occured inside a maas image
(lp:maas-images) build process.
The failure log ends like this:
Unpacking linux-generic (4.3.0.7.8) ...
Processing triggers for man-db (2.7.5-1) ...
Setting up linux-image-4.3.0-7-gen
Public bug reported:
Commit 633d6f17cd91ad5bf2370265946f716e42d388c6 (aka
38d30afb12140c0e3a446fe779dc9cd29548f313 in vivid) in Xen domU causes
high resource requirements in the underlying target dom0 (migrating a
64-bit domU involves a 1GB malloc in dom0, as well as a lot of
unnecessary work).
I
** 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/1542941
Title:
Regression: problems migrating recent wily/vivid Xen VM
That's the patch which *introduces* the regression.
The missing one is 98dd166ea3a3c3b57919e20d9b0d1237fcd0349d.
--
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/1542941
Title:
Regression
Apologies for the confusion; I had the right commit ID but pasted the
wrong description. Now fixed, I think!
** Description changed:
Commit 633d6f17cd91ad5bf2370265946f716e42d388c6 (aka
38d30afb12140c0e3a446fe779dc9cd29548f313 in vivid) in Xen domU causes
high resource requirements in the
Public bug reported:
hibernate / resume - appears to fail at pulse audio?
not sure - using suspend works fine
ProblemType: KernelOops
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-15-generic 4.4.0-15.31
ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
Uname: Linux 4.4.0-15-gen
heres the diagnosis of the failure here:
a.) the powerVM system was successfully booting and installing xenial,
but was failing to bring up networking on the installed system.
b.) curtin had written (as designed) /etc/udev/rules.d/70-persistent-net.rules
containing a line like:
SUBSYSTEM=="net
I looked in the /boot directory of the installed beta2 version and I
noticed that the file size of
initrd.img-4.4.0-15-powerpc-smp was 37077095 bytes.
I am wondering if there is a maximum file that yaboot can handle for the
ramdisk.
--
You received this bug notification because you are a member
** Changed in: qemu
Status: New => Invalid
--
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/1563887
Title:
qemu-system-ppc64 freezes on starting image on ppc64le
Status in QEMU:
ok. so after playing some, this all comes down to needing 'usb=off' on
the qemu command line.
works:
qemu-system-ppc64 -enable-kvm -machine usb=off -device
virtio-net-pci,netdev=net00 -netdev type=user,id=net00 -drive
if=virtio,file=xenial-server-cloudimg-ppc64el-disk1.img,format=qcow2 -drive
i
Note, that Michael Roth's comments are probably valid. I suspect that
if leftyfb ever saw this working on powerVM host, then it was through
the kvm_pr module. In my experience, that works generally pretty well
(buit my testing has only ever been done powerNV host).
--
You received this bug noti
ok, so it is /lib/modules-load.d/open-iscsi.conf that has 'ib_iser' in
it.
ib_iser per modinfo "iSER (iSCSI Extensions for RDMA) Datamover".
per depmod on full linux-image-extra system:
kernel/drivers/infiniband/ulp/iser/ib_iser.ko:
kernel/drivers/infiniband/core/rdma_cm.ko
kernel/drivers/infi
So, some conversation with infinity at
http://irclogs.ubuntu.com/2016/04/07/%23ubuntu-devel.html .
All of ib_iser's deps are already in linux-generic
(http://paste.ubuntu.com/15670921/)
So we might as well move that module also.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
**
** Description changed:
Calling iscsi ibft a 'virtual' thing is a bit questionable.
That said, I was looking at ibft using qemu and ipxe. The cloud images
do not have the iscsi_ibft module included, so you can't read the
information out of /sys/firmware/ibft until you have it.
Giv
Public bug reported:
Calling iscsi ibft a 'virtual' thing is a bit questionable.
That said, I was looking at ibft using qemu and ipxe. The cloud images
do not have the iscsi_ibft module included, so you can't read the
information out of /sys/firmware/ibft until you have it.
Given a iscsi target
I've dropped the maas-images task as that is being addressed under bug
1508565
** No longer affects: maas-images
--
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/1425699
Title:
kernel pan
** 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/1411294
Title:
kernel panic during MAAS fastpath install of Vivid images
Status in maas-images:
Fix
Public bug reported:
Hi, this failure for kernel package installation occured inside a maas image
(lp:maas-images) build process.
The failure log ends like this:
Unpacking linux-generic (4.3.0.7.8) ...
Processing triggers for man-db (2.7.5-1) ...
Setting up linux-image-4.3.0-7-generic (4.3.0-7.1
For full disclosure, this is in a "cross" build environment (qemu-static).
this works for other versions of ubuntu and has worked for xenial in the past.
the error messages seem to indicate 'update-initramfs' was deferred, but
the the postinst tried to copy it into place even though it wasnt there
** 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/1536810
Title:
kernel install failed /bin/cp: cannot stat
‘/boot/ini
** Summary changed:
- numad does not work on apple alluminum keyboard
+ numpad does not work on apple alluminum keyboard
--
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/285159
Title:
num
*** This bug is a duplicate of bug 1265436 ***
https://bugs.launchpad.net/bugs/1265436
The verification of the Stable Release Update for linux-firmware has
completed successfully and the package has now been released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
u
The verification of the Stable Release Update for mikutter 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 a
Public bug reported:
Suspend no longer works on my laptop running Trusty. It will just blank
the screen for a few seconds then come back up to the unlock prompt.
ProblemType: KernelOops
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-8-generic 3.13.0-8.28
ProcVersionSignature: Ubuntu 3.13
I have now installed the latest daily image of Ubuntu 14.04 as the main
install to help with testing before the final release.
The mouse cursor is still jumpy as described above. If another bug
report or further information would be useful at anytime feel free to
let me know.
--
You received th
/vmlinuz-3.13.0-8-generic]
ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2
Uname: Linux 3.13.0-8-generic x86_64
ApportVersion: 2.13.2-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: scott 1915 F pulseaudio
/dev/snd/controlC0
Hi Christopher, this was also a problem in Ubuntu 13.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/1272624
Title:
[Dell Latitude E7440] 14.04 Touchpad not as smooth as Win7
Status
Christopher, I have not personally tested on a release prior to Saucy
but according to comment #15 in bug 1258837 the touchpad bug (if it is
the same) didn't seem to exhibit itself in earlier kernel versions used
in 12.04
--
You received this bug notification because you are a member of Kernel
Pa
Christopher M. Penalver, in the live USB of 12.04.0 the two-finger
scrolling can not be activated under Settings-->Mouse. The problem was
not reproducable but I put that down to the OS not recognising the
second finger.
Edward-douse, I tried the newest version of ElementaryOS and the results
were
Sorry it took so long, but I reproduced the bug with the upstream
kernel.
** Tags added: kernel-bug-exists-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/1280304
Title:
[System
Christopher M. Penalver, I have just installed and rebooted to test the
following (below) and found that the bug still exists.
linux-image-3.14.0-031400rc4-generic_3.14.0-031400rc4.201402232235_amd64.deb
linux-headers-3.14.0-031400rc4-generic_3.14.0-031400rc4.201402232235_amd64.deb
** Tags added:
gnature: Ubuntu 3.13.0-8.28-generic 3.13.2
Uname: Linux 3.13.0-8-generic x86_64
ApportVersion: 2.13.2-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: scott 1915 F pulseaudio
/dev/snd/controlC0: scott 1915 F pulsea
I tried what Wren tried, but this did not fix the problem for me. I
replaced the entire QCA6147 directory, not just hw3.0. Still no luck.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.ne
Public bug reported:
[Impact]
Most attempts to use IPv6 on the ThunderX NIC will fail.
[Test Case]
Attempt an IPv6 TCP connection:
$ wget -6 'http://www.kernel.org/'
The connection will time out.
[Regression Risk]
The fix is upstream, and is limited to the ThunderX nicvf driver.
[Workaround]
This bug is not to track a problem, it's to change a default kernel
option to a more secure setting already in use by other distributions,
such as upstream Debian.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bu
Public bug reported:
bcmwl-kernel-source worked correctly on the original 16.04 LTS kernel,
but no longer works on the hwe kernel (4.10.0-33). I am using the b43
open source driver temporarily in order to file this report.
Description:Ubuntu 16.04.3 LTS
Release:16.04
bcmwl-kernel-so
Laptop info:
description: Notebook
product: 0769AK8 (Lenovo)
vendor: LENOVO
version: 3000 N200
serial: redacted
width: 64 bits
capabilities: smbios-2.4 dmi-2.4 vsyscall32
configuration: boot=oem-specific chassis=notebook family=Lenovo sku=Lenovo
uuid=redacted
*-core
Sorry, my previous comment was for another initramfs-tools related bug.
Please disregard #18.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
https://bugs.launchpad.net/bugs/1515513
Title:
/boot/initrd.img-*.old-dkms fil
The commit for this in upstream Debian (0.123 version of initramfs-
tools) is here: https://anonscm.debian.org/cgit/kernel/initramfs-
tools.git/commit/?id=ac6d31fc2c707b72ff8af9944c9b4f8af303a6a3 - I would
be happy to make a patch for this commit to xenial (zesty and later has
0.125+, so should alr
Mistaken identification of affected package. After reinstalling
16.04(.0) I have verified that bcmwl-kernel-source is not involved.
Marking this bug invalid.
** Changed in: bcmwl (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Pack
** Also affects: nss-pam-ldapd (Ubuntu)
Importance: Undecided
Status: New
** Also affects: openssh (Ubuntu)
Importance: Undecided
Status: New
** Also affects: openvpn (Ubuntu)
Importance: Undecided
Status: New
** Also affects: postfix (Ubuntu)
Importance: Undecid
301 - 400 of 811 matches
Mail list logo
