[Kernel-packages] [Bug 1878899] Re: Call trace from __video_do_ioctl

** Also affects: v4l2loopback (Ubuntu) Importance: Undecided Status: New ** Changed in: v4l2loopback (Ubuntu) Status: New => Confirmed ** No longer affects: linux (Ubuntu) ** Summary changed: - Call trace from __video_do_ioctl + Call trace from __video_do_ioctl on focal --

[Kernel-packages] [Bug 1793290] Re: Purging the custom kernel does not remove initramfs

A few questions: - Could you please provide the output of the apt-get purge call? - If update-initramfs is called in it, could you please manually call it with the verbose flag (-v) and attach the output? - Does this only happen on the half-configured scenario? I'm moving the status to

[Kernel-packages] [Bug 1791959] Re: [SRU] remove orphaned initrd old-dkms files in /boot

SRU as a merge proposal for both this and bug 1667512 available at Bionic: https://code.launchpad.net/~tdaitx/ubuntu/+source/initramfs-tools/+git/initramfs-tools/+merge/355189 Xenial: https://code.launchpad.net/~tdaitx/ubuntu/+source/initramfs-tools/+git/initramfs-tools/+merge/355190 ** No

[Kernel-packages] [Bug 1791959] Re: [SRU] remove orphaned initrd old-dkms files in /boot

attaching bionic sru patch ** Patch added: "initramfs-tools_0.130ubuntu3.3_debdiff_0.130ubuntu3.4.patch" https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1791959/+attachment/5187983/+files/initramfs-tools_0.130ubuntu3.3_debdiff_0.130ubuntu3.4.patch ** Tags added: bionic -- You received

[Kernel-packages] [Bug 1791959] Re: [SRU] remove orphaned initrd old-dkms files in /boot

attaching cosmic patch ** Patch added: "initramfs-tools_0.131ubuntu10_debdiff_0.131ubuntu11.patch" https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1791959/+attachment/5187984/+files/initramfs-tools_0.131ubuntu10_debdiff_0.131ubuntu11.patch -- You received this bug notification because

[Kernel-packages] [Bug 1791959] Re: [SRU] remove orphaned initrd old-dkms files in /boot

attaching xenial sru patch ** Description changed: [Impact] If a dkms package is installed which has REMAKE_INITRD or the same setting has been manually configured by a user then when a kernel is removed its possible for an ".old-dkms" file to be left in /boot with no associated kernel.

[Kernel-packages] [Bug 1791959] Re: [SRU] remove orphaned initrd old-dkms files in /boot

** Summary changed: - remove /boot/initrd.img-*.old-dkms files left behind + [SRU] remove orphaned initrd old-dkms files in /boot ** Description changed: [Impact] If a dkms package is installed which has REMAKE_INITRD or the same setting has been manually configured by a user then when a

[Kernel-packages] [Bug 1791959] Re: remove /boot/initrd.img-*.old-dkms files left behind

** Changed in: dkms (Ubuntu Xenial) Status: New => Invalid ** Changed in: dkms (Ubuntu Bionic) Status: New => Invalid ** Description changed: [Impact] If a dkms package is installed which has REMAKE_INITRD or the same setting has been manually configured by a user then when a

[Kernel-packages] [Bug 1791959] Re: remove /boot/initrd.img-*.old-dkms files left behind

** Changed in: dkms (Ubuntu) Importance: Undecided => Medium ** Changed in: dkms (Ubuntu) Status: New => Confirmed ** Also affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Changed in: initramfs-tools (Ubuntu) Status: New => Confirmed ** Changed

[Kernel-packages] [Bug 1791959] Re: remove /boot/initrd.img-*.old-dkms files left behind

** Changed in: dkms (Ubuntu) Status: Confirmed => Invalid -- 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/1791959 Title: remove /boot/initrd.img-*.old-dkms files left behind

[Kernel-packages] [Bug 1791959] Re: remove /boot/initrd.img-*.old-dkms files left behind

** Description changed: [Impact] If a dkms package is installed which has REMAKE_INITRD or the same setting has be manually configured by a user then when a kernel is removed its possible for an ".old-dkms" file to be left in /boot with no associated kernel. bug 1515513 dealt with

[Kernel-packages] [Bug 1791959] [NEW] remove /boot/initrd.img-*.old-dkms files left behind

Public bug reported: [Impact] If a dkms package is installed which has REMAKE_INITRD or the same setting has be manually configured by a user then when a kernel is removed its possible for an ".old-dkms" file to be left in /boot with no associated kernel. bug 1515513 dealt with removing

[Kernel-packages] [Bug 1699772] Re: linux-image-4.13.0-12-generic, linux-image-4.10.0-24-generic, linux-image-4.8.0-56-generic, linux-image-4.4.0-81-generic, linux-image-3.13.0-121-generic | Regressio

IcedTea 2.6.14 has backported a fix for the exec guard issue and will be available in Trusty's openjdk-7 version 7u181-2.6.14-0ubuntu0.1. The fix for OpenJDK-8 will be included in the next security update. -- You received this bug notification because you are a member of Kernel Packages, which

[Kernel-packages] [Bug 1699772] Re: linux-image-4.10.0-24-generic, linux-image-4.8.0-56-generic, linux-image-4.4.0-81-generic, linux-image-3.13.0-121-generic Regression: many user-space apps crashing

Regarding OpenJDK 8, it crashes as soon as Xss is set to (or higher than) 1141K in a i386 JVM (32-bit). I used the example code from bug #1700270. Please note that there is no need to even use the java class: the program will segfault while starting the JVM, so do remove lines 30-34 from either

Re: [Kernel-packages] [Bug 1710653] Re: Reboot into linux 4.11.0-13 after update caused 100% cpu on btrfs-cleaner/btrfs-transaction

On Mon, Aug 14, 2017 at 4:06 PM, Joseph Salisbury 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.13 kernel[0]. > > If this bug is fixed in the mainline

[Kernel-packages] [Bug 1710653] Re: Reboot into linux 4.11.0-13 after update caused 100% cpu on btrfs-cleaner/btrfs-transaction

FYI I was using 4.10.0-26 for the past days before the 400+ packages upgrade in artful. I am using snapper to get periodic system snapshots (pre/post apt install|remove and also hourly/daily/weekly). The actual behavior was that a short time after boot the btrfs cleaner/transaction process got

[Kernel-packages] [Bug 1710653] [NEW] Reboot into linux 4.11.0-13 after update caused 100% cpu on btrfs-cleaner/btrfs-transaction

Public bug reported: After doing no updates for a while I did a big update after the archive transitions. On the first boot I got btrfs-cleaner stuck at 100% CPU, sometimes changing place with btrfs-transaction. Atop does not report a high IO usage, only high CPU. The computer gets super slow

[Kernel-packages] [Bug 1619446] Re: mismatching headers between powerpc/ppc64el and other archs

** 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/1619446 Title: mismatching headers between powerpc/ppc64el and other

[Kernel-packages] [Bug 1619446] [NEW] mismatching headers between powerpc/ppc64el and other archs

Public bug reported: the header files from linux-libc-dev are causing repsnapper on -proposed to FTBFS on powerpc/ppc64el I tracked it to 2 include clauses: #include #include causing the following error on powerpc/ppc64el builds: following errors: src/printer/custom_baud.cpp: In function

[Kernel-packages] [Bug 1496223] Re: squid3 FTBFS due to linux-libc-dev and libc6-dev headers mismatch

This patch also fixes LP: #1501566 and LP: #1496924. ** Patch added: "squid3_3.3.8-1ubuntu16.debdiff" https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1496223/+attachment/4489239/+files/squid3_3.3.8-1ubuntu16.debdiff ** Patch removed: "fixes for this bug as well as LP: #1501566 and LP:

[Kernel-packages] [Bug 1496223] Re: squid3 FTBFS due to linux-libc-dev and libc6-dev headers mismatch

libecap3 was been deleted. I have created LP: #1504200 to handle the gcc5 transition. After it gets sponsored it should be ok to apply the squid debdiff. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.

[Kernel-packages] [Bug 1496223] Re: squid3 FTBFS due to linux-libc-dev and libc6-dev headers mismatch

I agree that merging the new one is the best approach and rbasak was already working in it, for this reason I was withholding my patches (at the time they required -D_GLIBCXX_USE_CXX11_ABI=0 since I didn't have a libecap2 compiled for gcc5). I decided to publish my patches for 3.3.8 just in case

[Kernel-packages] [Bug 1496223] Re: squid3 FTBFS due to linux-libc-dev and libc6-dev headers mismatch

** Patch added: "fixes for this bug as well as LP: #1501566 and LP: #1496924" https://bugs.launchpad.net/squid/+bug/1496223/+attachment/4480476/+files/squid3_3.3.8-1ubuntu16.debdiff -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to

[Kernel-packages] [Bug 1496223] Re: squid3 FTBFS due to linux-libc-dev and libc6-dev headers mismatch

The squid3_3.3.8-1ubuntu16.debdiff patch requires gcc5 transition of libecap2. I kept the lib soname and added a Conflicts: as per https://wiki.debian.org/TransitionBestPractices libecap2 and squid3 have been build at

[Kernel-packages] [Bug 1496223] Re: squid3 FTBFS due to linux-libc-dev and libc6-dev headers mismatch

** Project changed: linux => squid -- 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/1496223 Title: squid3 FTBFS due to linux-libc-dev and libc6-dev headers mismatch Status in Squid:

[Kernel-packages] [Bug 1496223] Re: squid3 FTBFS due to linux-libc-dev and libc6-dev headers mismatch

** Bug watch added: Squid Bugzilla #4323 http://bugs.squid-cache.org/show_bug.cgi?id=4323 ** Also affects: linux via http://bugs.squid-cache.org/show_bug.cgi?id=4323 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Kernel

[Kernel-packages] [Bug 1496223] Re: squid3 FTBFS due to linux-libc-dev and libc6-dev headers mismatch

** Also affects: glibc (Ubuntu) Importance: Undecided Status: New ** 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.