[Bug 1849026] Re: trusty/linux-azure: 4.15.0-1062.67~14.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy Whitcroft (apw) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849026 Title: trusty/linux-azure: 4.15.0-1062.67~14.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849026/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849047] Re: xenial/linux-fips: 4.4.0-1024.29 -proposed tracker
** Changed in: kernel-sru-workflow/promote-signing-to-proposed Assignee: (unassigned) => Andy Whitcroft (apw) ** Changed in: kernel-sru-workflow/promote-signing-to-proposed Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849047 Title: xenial/linux-fips: 4.4.0-1024.29 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849047/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849026] Re: trusty/linux-azure: 4.15.0-1062.67~14.04.1 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1849027 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure - phase: Ready for Promote to Proposed - phase-changed: Wednesday, 23. October 2019 11:13 UTC + phase: Promote to Proposed + phase-changed: Wednesday, 23. October 2019 12:51 UTC reason: - promote-to-proposed: Pending -- ready for review + promote-to-proposed: Ongoing -- review in progress variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849026 Title: trusty/linux-azure: 4.15.0-1062.67~14.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849026/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848999] Re: disco/linux-snapdragon: 5.0.0-1025.26 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1849003 packages: main: linux-snapdragon meta: linux-meta-snapdragon - phase: Ready for Promote to Proposed - phase-changed: Wednesday, 23. October 2019 11:41 UTC + phase: Promote to Proposed + phase-changed: Wednesday, 23. October 2019 12:45 UTC reason: - promote-to-proposed: Pending -- ready for review + promote-to-proposed: Ongoing -- review in progress variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848999 Title: disco/linux-snapdragon: 5.0.0-1025.26 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1848999/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848848] Re: Firmware for Radeon RX5700 (navi10) missing / boot failure
Looks like we have a mix ... vega20_ta.bin and navi10_mes.bin do not exist upstream, while raven_kicker_rlc.bin was recently added. I'll have to inquire about whether or not the missing files will be added upstream. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848848 Title: Firmware for Radeon RX5700 (navi10) missing / boot failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1848848/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849478] Re: (experimental) pipewire support not available
** Changed in: chromium-browser (Ubuntu) Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849478 Title: (experimental) pipewire support not available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1849478/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849480] Re: package libpam-fprintd:amd64 0.9.0-0ubuntu1 failed to install/upgrade: installed libpam-fprintd:amd64 package post-installation script subprocess returned error exit status 1
thank you for your bug report, the dmesg log suggests the system had issue due to lack of memory which isn't really a fprintfd issue ** Changed in: fprintd (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849480 Title: package libpam-fprintd:amd64 0.9.0-0ubuntu1 failed to install/upgrade: installed libpam-fprintd:amd64 package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fprintd/+bug/1849480/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849178] Re: upgrading linux-image package to 4.15.0-66.75 breaks Ceph network file system clients
Related to https://lkml.org/lkml/2019/10/3/862 ? (That rervert is _not_ in ubuntu linux 4.15.0-66.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849178 Title: upgrading linux-image package to 4.15.0-66.75 breaks Ceph network file system clients To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849178/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849031] Re: xenial/linux-gcp: 4.15.0-1048.51 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => In Progress ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/verification-testing Status: Confirmed => In Progress ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1849035 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp - phase: Promote to Proposed - phase-changed: Wednesday, 23. October 2019 08:20 UTC + phase: Testing + phase-changed: Wednesday, 23. October 2019 12:41 UTC + proposed-announcement-sent: true + proposed-testing-requested: true reason: - promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync + regression-testing: Ongoing -- testing in progress + security-signoff: Pending -- waiting for signoff + verification-testing: Ongoing -- testing in progress trackers: xenial/linux-gcp/gcp-kernel: bug 1849028 xenial/linux-gcp/gke-kernel: bug 1849029 variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849031 Title: xenial/linux-gcp: 4.15.0-1048.51 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849031/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849371] Re: [snap] Cannot run headless chromium as user www-data
The system-wide /tmp is not accessible by strictly-confined snaps, so /tmp/chromium-home won't work either. In any case this looks like a limitation hard-coded in snapd, which won't create $SNAP_USER_DATA if $HOME is not in /home. So this is not specific to the chromium snap. I'll add a snapd task to the bug. As a workaround (I realize this is less than ideal), could you maybe create a user with a home directory in /home just for this purpose, and have have your server process run chromium as this user? ** Summary changed: - [snap] Cannot run headless chromium as user www-data + [snap] Cannot run chromium as user www-data because home directory is /var/www ** Changed in: chromium-browser (Ubuntu) Status: New => Confirmed ** Also affects: snapd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849371 Title: [snap] Cannot run chromium as user www-data because home directory is /var/www To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1849371/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849484] [NEW] ultra-wide monitor recognized properly when plugged in only intermittently
Public bug reported: I have an LG ultra-wide (2560x1080) monitor. Sometimes when I plug it into my laptop, whose screen was working fine before I plugged it in, both screens go black but nothing else happens. I can still see the mouse cursor and move it between the two monitors (sometimes in the correct location configuration I've configured, sometimes not), but nothing is rendered on the screens. Sometimes when I plug the monitor in, it comes on, but the resolution is wrong. Sometimes it is actually recognized and configured correctly. Frequently I have to unplug the monitor and plug it back in three times or more before it is recognized correctly. I wish it just worked right the first time. :-/ ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Oct 23 08:34:07 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-09-12 (40 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-09-20 (32 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849484 Title: ultra-wide monitor recognized properly when plugged in only intermittently To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1849484/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849374] Re: packages built for python3.8 with disabled tests, for a first binary
** Also affects: astropy (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849374 Title: packages built for python3.8 with disabled tests, for a first binary To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/astropy/+bug/1849374/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849371] Re: [snap] Cannot run chromium as user www-data because home directory is /var/www
Snapd team: this is admittedly a corner case, but users with a home directory outside of /home might want to run snaps (especially CLI tools as e.g. user www-data). Would it be feasible to add support for this in snapd? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849371 Title: [snap] Cannot run chromium as user www-data because home directory is /var/www To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1849371/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848402] Re: No indication that thunderbird is starting
A video demonstrating the problem would be useful, indeed, because I cannot observe it myself. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848402 Title: No indication that thunderbird is starting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1848402/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848999] Re: disco/linux-snapdragon: 5.0.0-1025.26 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz Zemczak (sil2100) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848999 Title: disco/linux-snapdragon: 5.0.0-1025.26 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1848999/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849000] Re: bionic/linux-hwe: 5.0.0-33.35~18.04.1 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1849003 packages: main: linux-hwe meta: linux-meta-hwe signed: linux-signed-hwe phase: Holding before Promote to Proposed phase-changed: Wednesday, 23. October 2019 05:56 UTC reason: - promote-to-proposed: Pending -- builds not complete in ppa main:building,meta:failed + promote-to-proposed: Pending -- builds not complete in ppa meta:failed,signed:retry-needed variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849000 Title: bionic/linux-hwe: 5.0.0-33.35~18.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849000/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849001] Re: bionic/linux-oem-osp1: 5.0.0-1026.29 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1849003 packages: lrm: linux-restricted-modules-oem-osp1 main: linux-oem-osp1 meta: linux-meta-oem-osp1 signed: linux-signed-oem-osp1 phase: Holding before Promote to Proposed phase-changed: Wednesday, 23. October 2019 11:11 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa lrm:depwait,main:building,meta:depwait,signed:depwait + promote-to-proposed: Ongoing -- builds not complete in ppa lrm:depwait,meta:depwait,signed:depwait variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849001 Title: bionic/linux-oem-osp1: 5.0.0-1026.29 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849001/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826125] Re: Dell XPS 13 9380 flickering (Whiskey Lake)
I am back to a working monitor after installing https://people.canonical.com/~khfeng/bfo110511/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1826125 Title: Dell XPS 13 9380 flickering (Whiskey Lake) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1826125/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827929] Re: curtin should support making installed systems BIOS+UEFI hybrid bootable
** Tags added: id-5c93feaf25ac0e77ea3bba88 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1827929 Title: curtin should support making installed systems BIOS+UEFI hybrid bootable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1827929/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1837525] Re: [20.04 FEAT] Set Architecture Level (ALS) to z13
** Tags added: id-5d37a1077ecdd459fd008ecd -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1837525 Title: [20.04 FEAT] Set Architecture Level (ALS) to z13 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1837525/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848173] Re: Ubuntu 16.04.6 - Shared CEX7C cards defined in z/VM guest not established by zcrypt device driver
Thanks for the verification - adjusting the tags accordingly. ** Tags removed: verification-needed-xenial ** Tags added: verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848173 Title: Ubuntu 16.04.6 - Shared CEX7C cards defined in z/VM guest not established by zcrypt device driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1848173/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1841936] Re: Rebuild openssl 1.1.1 to pickup TLSv1.3 (bionic) and unbreak existing builds against 1.1.1 (dh key size)
Code and Builds for Versions D-F ready as well. 4 MPs are up and linked in here the bug (see below description) 1.8.8 and 1.8.19 work the same way. I also picked the change from the 2.0 branch, for Eoan/Focal, but there testing shows errors to load the dh file that the frontend defines like: bind 10.253.194.115:443 ssl crt /etc/ssl/certs/haproxy.pem That now fails to load, the same works in the 1.8 branches and it works (well more likely it wasn't used) prior to the fix. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1841936 Title: Rebuild openssl 1.1.1 to pickup TLSv1.3 (bionic) and unbreak existing builds against 1.1.1 (dh key size) To manage notifications about this bug go to: https://bugs.launchpad.net/haproxy/+bug/1841936/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846762] Re: automatic creation of casper-rw breaks installation from "disk"
** Tags added: id-5daf76eda2a6e5756012409b -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846762 Title: automatic creation of casper-rw breaks installation from "disk" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1846762/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849012] Re: bionic/linux-oem: 4.15.0-1060.69 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1849035 packages: lrm: linux-restricted-modules-oem main: linux-oem meta: linux-meta-oem signed: linux-signed-oem phase: Holding before Promote to Proposed phase-changed: Wednesday, 23. October 2019 10:31 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa lrm:depwait,main:building,meta:depwait,signed:depwait + promote-to-proposed: Ongoing -- builds not complete in ppa lrm:depwait,meta:depwait,signed:depwait variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849012 Title: bionic/linux-oem: 4.15.0-1060.69 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849012/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845571] Re: ubiquity offers installation media as an install target
** Tags added: id-5daf76eda2a6e5756012409b -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1845571 Title: ubiquity offers installation media as an install target To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/partman-auto/+bug/1845571/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1836938] Re: falkon failed to load some pages
Which version of Qt WebEngine do you use? A similar issue was blamed on it: https://bugs.kde.org/show_bug.cgi?id=405852 ** Bug watch added: KDE Bug Tracking System #405852 https://bugs.kde.org/show_bug.cgi?id=405852 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1836938 Title: falkon failed to load some pages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/falkon/+bug/1836938/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848402] Re: No indication that thunderbird is starting
Yes, this happens every time on Unity. In fact, it's been happening for many years. It's only now that I've got round to reporting it. I can take a video on my phone if you like. My keyboard shortcut is configured as: Name: Thunderbird Command: thunderbird Key: Super+T -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848402 Title: No indication that thunderbird is starting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1848402/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1842037] Re: Oops when Kerberos credentials are invalid
Hi Matthew, - Ursprüngliche Mail - > Von: "Bug 1842037" <1842...@bugs.launchpad.net> > An: "burk" > Gesendet: Samstag, 19. Oktober 2019 09:56:12 > Betreff: [Bug 1842037] Re: Oops when Kerberos credentials are invalid > Hi Frank, > > It has been 9 days, or slightly over a week since you applied the respun > test kernel to your systems. It looks very promising. We had no more problems on the test systems. > Are your systems stable now? Yes, they are. > Are they suffering any symptoms of Bug 1842037 or Bug 1828978? No, they're not. > Is the test kernel more stable than regular released Ubuntu kernels? Do > you think the patches you requested fix the problems you were having? I do think so. Please integrated the patches. Thank you very much. Best regards, Frank -- Frank Burkhardt IT Dept., Max Planck Institute for Human Cognitive and Brain Sciences, Leipzig, Germany -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1842037 Title: Oops when Kerberos credentials are invalid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842037/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849483] [NEW] shiftfs: prevent exceeding project quotas
Public bug reported: SRU Justification Impact: Currently shiftfs allows to exceed project quota and reserved space on e.g. ext2. See https://github.com/lxc/lxd/issues/6333 for a report, specifically https://github.com/lxc/lxd/issues/6333#issuecomment-545154838. This is caused by overriding the credentials with the superblock creator's credentials whenever we perform operations such as fallocate() or writes while retaining CAP_SYS_RESOURCE. Fix: Drop CAP_SYS_RESOURCE at superblock creation time from the effective capability set. Regression Potential: Limited to shiftfs. Dropping CAP_SYS_RESOURCE from the effective capability set should be fine and actually give us more security. Test Case: Try to exceed project quotas on a kernel and filesystem that supports them and see that it fails with the mentioned fix applied. Target Kernels: All LTS kernels with shiftfs support. ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Christian Brauner (cbrauner) Status: In Progress ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Christian Brauner (cbrauner) ** Changed in: linux (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849483 Title: shiftfs: prevent exceeding project quotas To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849483/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846016]
(In reply to Thorsten Leemhuis from comment #34)
> ```
> Fixes: f5a47fae6aa3 ("iwlwifi: mvm: fix version check for GEO_TX_POWER_LIMIT
> support")
> ```
> And that patch was recently backported to 5.3:
> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/
> ?h=linux-5.3.y=3a0b7157d6a9833cefd40b5f0fa1cc90285bb4b5
Scratch that, I mixed up the commits, sorry for the noise.
But I still wonder if
https://git.kernel.org/torvalds/c/12e36d98d3e5acf5fc57774e0a15906d55f30cb9
should be backported, as I see warnings mentioned in Bug 205163 here as
well on a system with a 3168
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1846016
Title:
Intel Wireless AC 3168 on Eoan complaints FW error in SYNC CMD
GEO_TX_POWER_LIMIT
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1846016/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846016]
(In reply to Luca Coelho from comment #32)
> Here's the patch that was sent upstream:
> https://lore.kernel.org/linux-wireless/20191009094853.PfIm3J8o7DN_Femup-
> OXkJdtmKE7rftk1ODkm7cx-vk@z/
That
patch/https://git.kernel.org/torvalds/c/12e36d98d3e5acf5fc57774e0a15906d55f30cb9
is not marked for stable afaics. I wonder if it should, as it contains this
line:
```
Fixes: f5a47fae6aa3 ("iwlwifi: mvm: fix version check for GEO_TX_POWER_LIMIT
support")
```
And that patch was recently backported to 5.3:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-5.3.y=3a0b7157d6a9833cefd40b5f0fa1cc90285bb4b5
Thus I suspect that 12e36d98d3e5 should be backported, too. I guess Bug
205163 is an indicator for that, as it talks about Linux 5.3.5.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1846016
Title:
Intel Wireless AC 3168 on Eoan complaints FW error in SYNC CMD
GEO_TX_POWER_LIMIT
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1846016/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826125] Re: Dell XPS 13 9380 flickering (Whiskey Lake)
Updated only launchpad: Just updated my ubuntu to 19.10 with kernel 5.3.0-19-generic and the problem is still here - so not fixed upstream. Will attempt to recompile this kernel using branch from https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1826125/comments/91 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1826125 Title: Dell XPS 13 9380 flickering (Whiskey Lake) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1826125/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848790] Re: USB not working under arm64 on Pi4
@hui.wang - I tested the compiled kernel on my RaspberryPi4 (4GB RAM model). Both KVM and external SSD/USB (in my case Samsung T5, 500GB external SSD) on the USB 3.0 port are working fine: root@cloudstack-mgmt:~# ls /dev/kvm /dev/kvm root@cloudstack-mgmt:~# kvm-ok INFO: /dev/kvm exists KVM acceleration can be used root@cloudstack-mgmt:~# lsusb Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 04e8:61f5 Samsung Electronics Co., Ltd Portable SSD T5 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub # fdisk -l [.. snipped ..] Disk /dev/sda: 465.78 GiB, 500107862016 bytes, 976773168 sectors Disk model: Portable SSD T5 Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 33553920 bytes Disklabel type: dos Disk identifier: 0x Device Boot Start End Sectors Size Id Type /dev/sda12048 976773134 976771087 465.8G c W95 FAT32 (LBA) root@cloudstack-mgmt:~# blkid -o list device fs_type label mount pointUUID --- /dev/mmcblk0p1 vfatsystem-boot /boot/firmware 79A2-EC62 /dev/mmcblk0p2 ext4writable / 2fae1f20-4a20-4c77-a39b-fb6480f64a0b /dev/loop0 squashfs /snap/lxd/12210 /dev/loop1 squashfs /snap/core/7920 /dev/sda1 ext4 (not mounted) 91175b3a-ee2c-47a7-a1e5-f4528e127523 This confirms that the patch and kernel-image build by @hui.wang fixes the external USB storage issue with the 4GB RPi4 model. Thanks @hui.wang. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848790 Title: USB not working under arm64 on Pi4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1848790/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826125] Re: Dell XPS 13 9380 flickering (Whiskey Lake)
Attempting to rebase git://github.com/vsyrjala/linux.git dp_retry_max_vs_optim onto v5.3 upstream seems to be a world of pain. :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1826125 Title: Dell XPS 13 9380 flickering (Whiskey Lake) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1826125/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849480] [NEW] package libpam-fprintd:amd64 0.9.0-0ubuntu1 failed to install/upgrade: installed libpam-fprintd:amd64 package post-installation script subprocess returned error exit status 1
Public bug reported: Caused error on upgrade from 19.04 to 19.10 ProblemType: Package DistroRelease: Ubuntu 19.10 Package: libpam-fprintd:amd64 0.9.0-0ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-32.34-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 NonfreeKernelModules: vboxpci vboxnetadp vboxnetflt vboxdrv ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 Date: Wed Oct 23 12:13:19 2019 ErrorMessage: installed libpam-fprintd:amd64 package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2016-07-04 (1205 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Python3Details: /usr/bin/python3.7, Python 3.7.5rc1, python3-minimal, 3.7.5-1 PythonDetails: /usr/bin/python2.7, Python 2.7.17rc1, python-minimal, 2.7.17-1 RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.4 SourcePackage: fprintd Title: package libpam-fprintd:amd64 0.9.0-0ubuntu1 failed to install/upgrade: installed libpam-fprintd:amd64 package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to eoan on 2019-10-23 (0 days ago) ** Affects: fprintd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package eoan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849480 Title: package libpam-fprintd:amd64 0.9.0-0ubuntu1 failed to install/upgrade: installed libpam-fprintd:amd64 package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fprintd/+bug/1849480/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849480] Re: package libpam-fprintd:amd64 0.9.0-0ubuntu1 failed to install/upgrade: installed libpam-fprintd:amd64 package post-installation script subprocess returned error exit status 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849480 Title: package libpam-fprintd:amd64 0.9.0-0ubuntu1 failed to install/upgrade: installed libpam-fprintd:amd64 package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fprintd/+bug/1849480/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848173] Comment bridged from LTC Bugzilla
--- Comment From fre...@de.ibm.com 2019-10-23 07:52 EDT--- Verified, with uname -a Linux t35lp54 4.4.0-167-generic #196-Ubuntu SMP Mon Oct 21 19:47:50 UTC 2019 s390x s390x s390x GNU/Linux works - I can see the CEX7 cards in toleration mode as CEX5 cards :-) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848173 Title: Ubuntu 16.04.6 - Shared CEX7C cards defined in z/VM guest not established by zcrypt device driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1848173/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849482] [NEW] shiftfs: fix fallocate()
Public bug reported: SRU Justification Impact: Currently shiftfs limits the maximum size for fallocate() needlessly causing calls such as fallocate --length 2GB ./file to fail. This limitation is arbitrary since it's not caused by the underlay but rather by shiftfs itself capping the s_maxbytes. This causes bugs such as the one reported in https://github.com/lxc/lxd/issues/6333. Fix: Currectly set up s_maxbytes when creating the shiftfs superblock. Regression Potential: Limited to shiftfs. Test Case: Try fallocate --length 3GB ./file on top of a filesystem with fallocate support on a fixed kernel and see that the call succeeds and the file is of the expected size. Target Kernels: All LTS kernels with shiftfs support. ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Christian Brauner (cbrauner) Status: In Progress ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Christian Brauner (cbrauner) ** Changed in: linux (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849482 Title: shiftfs: fix fallocate() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849482/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 643557] Re: Search Messages box does not allow to search in message body
Has anyone been able to find out which is the best product among those listed here? https://onlychainsaw.com/best-scroll- saw/">https://onlychainsaw.com/best-scroll-saw/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/643557 Title: Search Messages box does not allow to search in message body To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/643557/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1766945] Re: (EFI on top of legacy install) choosing "replace" or "resize" options in partitioning may lead to an install failure
ubuntu is installing error that is crub error. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1766945 Title: (EFI on top of legacy install) choosing "replace" or "resize" options in partitioning may lead to an install failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/partman-auto/+bug/1766945/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847921] Re: "iwlwifi 0000:04:00.0: Microcode SW error detected. Restarting 0x12000000." at boot
You can install my prebuilt kernel with following command: $ sudo apt install --no-install-recommends linux- headers-5.3.0-17-generic=5.3.0-17.18+lp1846016 linux-modules- extra-5.3.0-17-generic=5.3.0-17.18+lp1846016 To list what packages are available for install, you can use `apt policy`: $ apt policy linux-headers-* linux-headers-5.3.0-17: Installed: 5.3.0-17.18+lp1846016 Candidate: 5.3.0-17.18+lp1846016 Version table: *** 5.3.0-17.18+lp1846016 500 500 http://ppa.launchpad.net/vicamo/ppa-1846016/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status ... To install packages of a specific version, append '=' after the package's name. You'll have to select the right kernel to boot in the grub menu because it's not the latest one installed in your system. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847921 Title: "iwlwifi :04:00.0: Microcode SW error detected. Restarting 0x1200." at boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1847921/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849011] Re: bionic/linux-snapdragon: 4.15.0-1067.74 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/certification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/security-signoff Status: New => In Progress ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/verification-testing Status: Confirmed => In Progress ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1849035 packages: main: linux-snapdragon meta: linux-meta-snapdragon - phase: Promote to Proposed - phase-changed: Wednesday, 23. October 2019 09:11 UTC + phase: Testing + phase-changed: Wednesday, 23. October 2019 11:51 UTC + proposed-announcement-sent: true + proposed-testing-requested: true reason: - promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync + automated-testing: Ongoing -- testing in progress + certification-testing: Ongoing -- testing in progress + security-signoff: Pending -- waiting for signoff + verification-testing: Ongoing -- testing in progress trackers: bionic/linux-snapdragon/dragonboard-kernel: bug 1849010 variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849011 Title: bionic/linux-snapdragon: 4.15.0-1067.74 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849011/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848492] Re: Change Config Option CONFIG_MEMORY_HOTPLUG_DEFAULT_ONLINE for s390x from yes to no
Successfully verified on disco on an LPAR with 32GB Initial and 10GB Reserved. Hence with std. kernel free shows ~31GB and with prop. kernel ~41GB. ** Attachment added: "disco_verification.txt" https://bugs.launchpad.net/ubuntu-z-systems/+bug/1848492/+attachment/5299466/+files/disco_verification.txt ** Tags removed: verification-needed-disco ** Tags added: verification-done-disco -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848492 Title: Change Config Option CONFIG_MEMORY_HOTPLUG_DEFAULT_ONLINE for s390x from yes to no To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1848492/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848999] Re: disco/linux-snapdragon: 5.0.0-1025.26 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Tags added: block-proposed-disco ** Tags added: block-proposed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- + boot-testing-requested: true kernel-stable-master-bug: 1849003 packages: main: linux-snapdragon meta: linux-meta-snapdragon - phase: Holding before Promote to Proposed - phase-changed: Wednesday, 23. October 2019 07:32 UTC + phase: Ready for Promote to Proposed + phase-changed: Wednesday, 23. October 2019 11:41 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa main:building + promote-to-proposed: Pending -- ready for review variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848999 Title: disco/linux-snapdragon: 5.0.0-1025.26 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1848999/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849478] [NEW] (experimental) pipewire support not available
Public bug reported: I'm using the chromium snap (currently 77.0.3865.120, rev 899), it's not possible to enable experimental support for pipewire, as the toggle doesn't show up in chrome://flags. It would be nice to have chromium compiled with pipewire support, to enable screensharing in Hangouts and similar apps. ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849478 Title: (experimental) pipewire support not available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1849478/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849374] Re: packages built for python3.8 with disabled tests, for a first binary
Moved the s390x specific numpy & reverse-deps ftbfs to https://bugs.launchpad.net/ubuntu/+source/bottleneck/+bug/1849477 ** No longer affects: cftime (Ubuntu) ** No longer affects: bottleneck (Ubuntu) ** Tags removed: ftbfs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849374 Title: packages built for python3.8 with disabled tests, for a first binary To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/numpy/+bug/1849374/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848645] Re: bionic/linux-hwe-edge: 5.3.0-19.20~18.04.2 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1848648 packages: main: linux-hwe-edge meta: linux-meta-hwe-edge signed: linux-signed-hwe-edge phase: Promote to Proposed phase-changed: Wednesday, 23. October 2019 09:55 UTC reason: - promote-to-proposed: Ongoing -- review in progress + promote-to-proposed: Pending -- package copies requested to Proposed meta:missing,signed:missing variant: debs ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1848648 packages: main: linux-hwe-edge meta: linux-meta-hwe-edge signed: linux-signed-hwe-edge phase: Promote to Proposed phase-changed: Wednesday, 23. October 2019 09:55 UTC reason: - promote-to-proposed: Pending -- package copies requested to Proposed meta:missing,signed:missing + promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848645 Title: bionic/linux-hwe-edge: 5.3.0-19.20~18.04.2 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1848645/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848983] Re: bionic/linux-aws-5.0: 5.0.0-1020.22~18.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: In Progress => Fix Committed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1848984 packages: lrm: linux-restricted-modules-aws-5.0 main: linux-aws-5.0 meta: linux-meta-aws-5.0 phase: Promote to Proposed phase-changed: Tuesday, 22. October 2019 22:15 UTC reason: - promote-to-proposed: Stalled -- review in progress + promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848983 Title: bionic/linux-aws-5.0: 5.0.0-1020.22~18.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1848983/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849477] [NEW] numpy fails on s390x
Public bug reported: File "/usr/lib/python3/dist-packages/numpy/core/_asarray.py", line 179, in ascontiguousarray return array(a, dtype, copy=False, order='C', ndmin=1) ValueError: ndmin bigger than allowable number of dimensions NPY_MAXDIMS (=32) numpy and many reverse-dependencies are failing with above valueerror on s390x ** Affects: bottleneck (Ubuntu) Importance: Undecided Status: New ** Affects: cftime (Ubuntu) Importance: Undecided Status: New ** Affects: numpy (Ubuntu) Importance: Undecided Status: New ** Affects: pykdtree (Ubuntu) Importance: Undecided Status: New ** Affects: python-feather-format (Ubuntu) Importance: Undecided Status: New ** Tags: ftbfs rls-ff-incoming s390x ** Tags added: rls-ff-incoming ** Tags added: ftbfs ** Also affects: cftime (Ubuntu) Importance: Undecided Status: New ** Also affects: bottleneck (Ubuntu) Importance: Undecided Status: New ** Tags added: s390x ** Also affects: pykdtree (Ubuntu) Importance: Undecided Status: New ** Also affects: python-feather-format (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849477 Title: numpy fails on s390x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bottleneck/+bug/1849477/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847103] Re: gnome-control-center crashed with SIGSEGV in g_type_check_instance_cast() from BG_RECENT_SOURCE() from enumerate_children_finished_cb() from g_task_return_now() from complete_in_idle
** Changed in: gnome-control-center Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847103 Title: gnome-control-center crashed with SIGSEGV in g_type_check_instance_cast() from BG_RECENT_SOURCE() from enumerate_children_finished_cb() from g_task_return_now() from complete_in_idle_cb() To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1847103/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1841936] Re: Rebuild openssl 1.1.1 to pickup TLSv1.3 (bionic) and unbreak existing builds against 1.1.1 (dh key size)
** Description changed: [Impact-Bionic] * openssl 1.1.1 has been backported to Bionic for its longer support upstream period * That would allow the extra feature of TLSv1.3 in some consuming packages what seems "for free". Just with a no change rebuild it would pick that up. [Impact Disco-Focal] - * openssl >=1.1.1 is in Disco-Focal already and thereby it was built -against that already. That made it pick up TLSv1.3, but also a related -bug that broke the ability to control the DHE key, it was always in -"ECDH auto" mode. Therefore the daemon didn't follow the config -anymore. -Upgraders would regress having their DH key behavior changed -unexpectedly. + * openssl >=1.1.1 is in Disco-Focal already and thereby it was built + against that already. That made it pick up TLSv1.3, but also a related + bug that broke the ability to control the DHE key, it was always in + "ECDH auto" mode. Therefore the daemon didn't follow the config + anymore. + Upgraders would regress having their DH key behavior changed + unexpectedly. [Test Case] + A) * run "haproxy -vv" and check the reported TLS versions to include 1.3 + B) + * download https://github.com/drwetter/testssl.sh + * Install haproxy +* ./testssl.sh --pfs :443 +* Check the reported DH key/group (shoudl stay 1024) +* Check if settings work to bump it like +tune.ssl.default-dh-param 2048 + into +/etc/haproxy/haproxy.cfg [Regression Potential-Bionic] * This should be low, the code already runs against the .so of the newer openssl library. This would only make it recognize the newer TLS support. i'd expect more trouble as-is with the somewhat big delta between what it was built against vs what it runs with than afterwards. * [1] and [2] indicate that any config that would have been made for TLSv1.2 [1] would not apply to the v1.3 as it would be configured in [2]. It is good to have no entry for [2] yet as following the defaults of openssl is the safest as that would be updated if new insights/CVEs are known. But this could IMHO be the "regression that I'd expect", one explcitly configured the v1.2 things and once both ends support v1.3 that might be auto-negotiated. One can then set "force-tlsv12" but that is an administrative action [3] * Yet AFAIK this fine grained control [2] for TLSv1.3 only exists in >=1.8.15 [4] and Bionic is on haproxy 1.8.8. So any user of TLSv1.3 in Bionic haproxy would have to stay without that. There are further changes to TLS v1.3 handling enhancements [5] but also fixes [6] which aren't in 1.8.8 in Bionic. So one could say enabling this will enable an inferior TLSv1.3 and one might better not enable it, for an SRU the bar to not break old behavior is intentionally high - I tried to provide as much as possible background, the decision is up to the SRU team. [Regression Potential-Disco-Focal] - * The fixes let the admin regain control of the DH key configuration -which is the fix. But remember that the default config didn't specify -any. Therefore we have two scenarios: -a) an admin had set custom DH parameters which were ignored. He had no - chance to control them and needs the fix. He might have been under - the impression that his keys are safe (there is a CVE against small - ones) and only now is he really safe -> gain high, regression low -b) an admin had not set anything, the default config is meant to use - (compatibility) and the program reported "I'm using 1024, but you - should set it higher". But what really happened was ECDH auto mode - which has longer keys and different settings. Those systems will - be "fixed" by finally following the config, but that means the key - will "now" after the fix be vulnerable. - -> for their POV a formerly secure setup will become vulnerable -I'd expect that any professional setup would use explicit config as it -has seen the warning since day #1 and also any kind of deployment -recipes should use big keys. So the majority of users should be in (a). -c) And OTOH there are people like the reporter who strictly NEED the - key to be small for their devices they have to support. They will - finally be able to use the small keys again which formerly was - impossible. + * The fixes let the admin regain control of the DH key configuration + which is the fix. But remember that the default config didn't specify + any. Therefore we have two scenarios: + a) an admin had set custom DH parameters which were ignored. He had no + chance to control them and needs the fix. He might have been under + the impression that his keys are safe (there is a CVE against small + ones) and only now is he really safe ->
[Bug 1826544] Re: media button to disable touchpad not working
** Changed in: gnome-settings-daemon Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1826544 Title: media button to disable touchpad not working To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1826544/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849047] Re: xenial/linux-fips: 4.4.0-1024.29 -proposed tracker
** Changed in: kernel-sru-workflow/promote-signing-to-proposed Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1849051 packages: main: linux-fips meta: linux-meta-fips signed: linux-signed-fips - phase: Promote to Proposed - phase-changed: Wednesday, 23. October 2019 08:21 UTC + phase: Ready for Promote to Proposed + phase-changed: Wednesday, 23. October 2019 11:26 UTC reason: - promote-to-proposed: Pending -- package copied to Signing signed:retry-needed + promote-signing-to-proposed: Pending -- ready for review variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849047 Title: xenial/linux-fips: 4.4.0-1024.29 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849047/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848645] Re: bionic/linux-hwe-edge: 5.3.0-19.20~18.04.2 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848645 Title: bionic/linux-hwe-edge: 5.3.0-19.20~18.04.2 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1848645/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849476] Re: package virtualbox-ext-pack 6.0.14-1 failed to install/upgrade: installed virtualbox-ext-pack package post-installation script subprocess returned error exit status 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849476 Title: package virtualbox-ext-pack 6.0.14-1 failed to install/upgrade: installed virtualbox-ext-pack package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox-ext-pack/+bug/1849476/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849476] [NEW] package virtualbox-ext-pack 6.0.14-1 failed to install/upgrade: installed virtualbox-ext-pack package post-installation script subprocess returned error exit status 1
Public bug reported: Updated from 19.04 to 19.10. ProblemType: Package DistroRelease: Ubuntu 19.10 Package: virtualbox-ext-pack 6.0.14-1 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 Date: Wed Oct 23 13:12:21 2019 ErrorMessage: installed virtualbox-ext-pack package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2018-01-09 (652 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all Python3Details: /usr/bin/python3.7, Python 3.7.5rc1, python3-minimal, 3.7.5-1 PythonDetails: /usr/bin/python2.7, Python 2.7.17rc1, python-minimal, 2.7.17-1 RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.4 SourcePackage: virtualbox-ext-pack Title: package virtualbox-ext-pack 6.0.14-1 failed to install/upgrade: installed virtualbox-ext-pack package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to eoan on 2019-10-23 (0 days ago) ** Affects: virtualbox-ext-pack (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package eoan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849476 Title: package virtualbox-ext-pack 6.0.14-1 failed to install/upgrade: installed virtualbox-ext-pack package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox-ext-pack/+bug/1849476/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849374] Re: packages built for python3.8 with disabled tests, for a first binary
But this makes bottleneck, cftime fail their testsuites because numpy is busted. ** Also affects: bottleneck (Ubuntu) Importance: Undecided Status: New ** Also affects: cftime (Ubuntu) Importance: Undecided Status: New ** Tags added: ftbfs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849374 Title: packages built for python3.8 with disabled tests, for a first binary To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/numpy/+bug/1849374/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845000] Re: evince assert failure: double free or corruption (!prev)
** Changed in: evince Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1845000 Title: evince assert failure: double free or corruption (!prev) To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/1845000/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1843262] Re: tracker-miner-fs crashed with SIGABRT in raise()
I am also affected after upgrade from bionic to eaon. Same StacktraceTop -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1843262 Title: tracker-miner-fs crashed with SIGABRT in raise() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker-miners/+bug/1843262/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1818547] Re: hid-sensor-hub spamming dmesg in 4.20
HP Spectre x360 on 19.10 with 5.3.0-19-generic has this issue as well. The sensor "id": hid-sensor-hub 001F:8087:0AC2.0004 Tip: Add the line `:msg, contains, "hid-sensor-hub 001F:8087:0AC2.0004" ~` at the top of you /etc/rsyslog.d/50-default.conf to temporarily get rid of this message in your logs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1818547 Title: hid-sensor-hub spamming dmesg in 4.20 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818547/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848790] Re: USB not working under arm64 on Pi4
@Rohit, Got it, thx, and please refer to https://bugs.launchpad.net/ubuntu/+source/linux- raspi2/+bug/1849369/comments/1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848790 Title: USB not working under arm64 on Pi4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1848790/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1844021] Re: Suspend stopped working from 4.4.0-157 onwards
Does this mean this patch will only be collected for Xenial, and the 4.4.0 kernel? I don't want to monkey with the tags, but is there a way to append one for Bionic (I'm assuming that's where Mint gets their 4.15.0 kernels). If not, do I need to open a new bug and cross ref this one? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1844021 Title: Suspend stopped working from 4.4.0-157 onwards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1844021/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849014] Re: bionic/linux-aws-fips: 4.15.0-2003.3 -proposed tracker
** Changed in: kernel-sru-workflow/promote-signing-to-proposed Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-signing-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/verification-testing Status: Confirmed => In Progress ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1849016 packages: lrm: linux-restricted-modules-aws-fips main: linux-aws-fips meta: linux-meta-aws-fips signed: linux-signed-aws-fips - phase: Promote to Proposed - phase-changed: Wednesday, 23. October 2019 10:55 UTC + phase: Testing + phase-changed: Wednesday, 23. October 2019 11:12 UTC + proposed-announcement-sent: true + proposed-testing-requested: true reason: - promote-signing-to-proposed: Ongoing -- review in progress + regression-testing: Ongoing -- testing in progress + verification-testing: Ongoing -- testing in progress variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849014 Title: bionic/linux-aws-fips: 4.15.0-2003.3 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849014/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849001] Re: bionic/linux-oem-osp1: 5.0.0-1026.29 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-lrm Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package-lrm Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package-meta Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-signed Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package-signed Status: Fix Committed => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1849003 packages: lrm: linux-restricted-modules-oem-osp1 main: linux-oem-osp1 meta: linux-meta-oem-osp1 signed: linux-signed-oem-osp1 - phase: Packaging - phase-changed: Wednesday, 23. October 2019 10:30 UTC + phase: Holding before Promote to Proposed + phase-changed: Wednesday, 23. October 2019 11:11 UTC reason: - prepare-package: Pending -- package not yet uploaded - prepare-package-lrm: Pending -- package not yet uploaded - prepare-package-meta: Pending -- package not yet uploaded - prepare-package-signed: Pending -- package not yet uploaded + promote-to-proposed: Ongoing -- builds not complete in ppa lrm:depwait,main:building,meta:depwait,signed:depwait variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849001 Title: bionic/linux-oem-osp1: 5.0.0-1026.29 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849001/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1834558] Re: intel_idle enable in ICL
** Also affects: linux-oem-osp1 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux-oem-osp1 (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Status: New => Invalid ** Changed in: linux (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1834558 Title: intel_idle enable in ICL To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1834558/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849026] Re: trusty/linux-azure: 4.15.0-1062.67~14.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Tags added: block-proposed-trusty ** Tags added: block-proposed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- + boot-testing-requested: true kernel-stable-master-bug: 1849027 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure - phase: Holding before Promote to Proposed - phase-changed: Wednesday, 23. October 2019 07:21 UTC + phase: Ready for Promote to Proposed + phase-changed: Wednesday, 23. October 2019 11:13 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa signed:depwait + promote-to-proposed: Pending -- ready for review variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849026 Title: trusty/linux-azure: 4.15.0-1062.67~14.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849026/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1841936] Re: Rebuild openssl 1.1.1 to pickup TLSv1.3 (bionic) and unbreak existing builds against 1.1.1 (dh key size)
** Merge proposal linked: https://code.launchpad.net/~paelzer/ubuntu/+source/haproxy/+git/haproxy/+merge/374595 ** Merge proposal linked: https://code.launchpad.net/~paelzer/ubuntu/+source/haproxy/+git/haproxy/+merge/374596 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1841936 Title: Rebuild openssl 1.1.1 to pickup TLSv1.3 (bionic) and unbreak existing builds against 1.1.1 (dh key size) To manage notifications about this bug go to: https://bugs.launchpad.net/haproxy/+bug/1841936/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848090] Re: [snap] Unable to install Extensions
Folders under ~/snap/chromium shouldn't be empty. They contain hidden files and folders though, so maybe they appear empty to you because you're not list hidden files. Can you share the output of: ls -la ~/snap/chromium/current/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848090 Title: [snap] Unable to install Extensions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1848090/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849014] Re: bionic/linux-aws-fips: 4.15.0-2003.3 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1849016 packages: lrm: linux-restricted-modules-aws-fips main: linux-aws-fips meta: linux-meta-aws-fips signed: linux-signed-aws-fips - phase: Ready for Promote to Proposed - phase-changed: Wednesday, 23. October 2019 07:46 UTC + phase: Promote to Proposed + phase-changed: Wednesday, 23. October 2019 10:55 UTC reason: - promote-signing-to-proposed: Pending -- ready for review + promote-signing-to-proposed: Ongoing -- review in progress variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849014 Title: bionic/linux-aws-fips: 4.15.0-2003.3 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849014/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849475] [NEW] the updates is crash
Public bug reported: can't update form 18.04 to 19.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.34 ProcVersionSignature: Ubuntu 4.15.0-66.75-generic 4.15.18 Uname: Linux 4.15.0-66-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CrashDB: ubuntu Date: Wed Oct 23 17:54:12 2019 InstallationDate: Installed on 2019-10-02 (20 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to bionic on 2019-10-23 (0 days ago) VarLogDistupgradeAptlog: Log time: 2019-10-23 17:48:46.320258 Log time: 2019-10-23 17:51:33.918998 Log time: 2019-10-23 17:53:53.238759 Log time: 2019-10-23 17:54:20.549536 VarLogDistupgradeTermlog: mtime.conffile..etc.update-manager.release-upgrades: 2019-10-23T17:27:17.697300 ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic dist-upgrade -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849475 Title: the updates is crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1849475/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848790] Re: USB not working under arm64 on Pi4
@hui.wang - I'm not sure on RPi3, but Ubuntu 18.04+KVM certainly works on RPi4. See someone already blogged about this here: https://jamesachambers.com/raspberry-pi-4-ubuntu-server-desktop-18-04-3 -image-unofficial, I tried their image but it had issues due to older libvirt/qemu versions on 18.04. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848790 Title: USB not working under arm64 on Pi4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1848790/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848490] Re: eoan: alsa/sof: Enable SOF_HDA link and codec
** Changed in: linux (Ubuntu Eoan) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848490 Title: eoan: alsa/sof: Enable SOF_HDA link and codec To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848490/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849301] Re: Crashes during installation of Xubuntu 19.10
*** This bug is a duplicate of bug 1848646 *** https://bugs.launchpad.net/bugs/1848646 ** This bug has been marked a duplicate of bug 1848646 Installer crashes during installation around the time a user is created -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849301 Title: Crashes during installation of Xubuntu 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1849301/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1714244] Re: [snap] apparmor denials on /etc/chromium-browser/policies/
@Joachim: there's no separate bug for this yet, but you're right that this needs attention. Would you mind filing one to track this separately? If you can attach examples of custom policies that would be great, too. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1714244 Title: [snap] apparmor denials on /etc/chromium-browser/policies/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1714244/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849014] Re: bionic/linux-aws-fips: 4.15.0-2003.3 -proposed tracker
** Changed in: kernel-sru-workflow/promote-signing-to-proposed Assignee: (unassigned) => Andy Whitcroft (apw) ** Changed in: kernel-sru-workflow/promote-signing-to-proposed Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849014 Title: bionic/linux-aws-fips: 4.15.0-2003.3 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849014/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848475] Re: TB with Gnome - main window size problem
Thanks for the report. I cannot observe the issues you describe. I'm running a fully up-to-date 19.10, with the default GNOME desktop, and I can tile the unmaximized thunderbird window to the leftmost half of the screen by dragging it to the top-left corner, and I can also resize the window so that the width is < half the width of the screen. The latter probably depends on your screen resolution, and on the layout you use in thunderbird. Can you share details on those? And can you test again the first problem and confirm you can reliably reproduce it? ** Changed in: thunderbird (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848475 Title: TB with Gnome - main window size problem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1848475/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848646] Re: Installer crashes during installation around the time a user is created
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubiquity (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848646 Title: Installer crashes during installation around the time a user is created To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1848646/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849031] Re: xenial/linux-gcp: 4.15.0-1048.51 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1849035 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Promote to Proposed phase-changed: Wednesday, 23. October 2019 08:20 UTC reason: - promote-to-proposed: Ongoing -- package copied to Proposed signed:depwait + promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync trackers: xenial/linux-gcp/gcp-kernel: bug 1849028 xenial/linux-gcp/gke-kernel: bug 1849029 variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849031 Title: xenial/linux-gcp: 4.15.0-1048.51 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849031/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1741027] Re: [SRU] Screen sharing panels abort using an non-existent vino gsettings key
I've got same problem at 18.04 with Unity and I confirm that #11 helped. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1741027 Title: [SRU] Screen sharing panels abort using an non-existent vino gsettings key To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1741027/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848402] Re: No indication that thunderbird is starting
I cannot observe the problem you describe. I've tested in a fully up-to- date 19.10 VM, with both the default GNOME desktop, and in the Unity session. In both cases, when starting thunderbird with a keyboard shortcut, the cursor immediately turns into a spinner, and in the case of Unity the icon in the launcher immediately starts glowing (if thunderbird is not a favourite app the icon appears at the bottom of the launcher). Can you confirm you can reliably reproduce the problem? How is your keyboard shortcut configured? ** Changed in: thunderbird (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848402 Title: No indication that thunderbird is starting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1848402/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1841936] Re: Rebuild openssl 1.1.1 to pickup TLSv1.3 (bionic) and unbreak existing builds against 1.1.1 (dh key size)
** Merge proposal linked: https://code.launchpad.net/~paelzer/ubuntu/+source/haproxy/+git/haproxy/+merge/374592 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1841936 Title: Rebuild openssl 1.1.1 to pickup TLSv1.3 (bionic) and unbreak existing builds against 1.1.1 (dh key size) To manage notifications about this bug go to: https://bugs.launchpad.net/haproxy/+bug/1841936/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1844739] Re: Latest Firefox update freezing my system
Can you start firefox in safe mode and report whether the freeze still happens? firefox --safe-mode -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1844739 Title: Latest Firefox update freezing my system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1844739/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849472] [NEW] Bionic raspi3 images should have the same cloud-init datasource setup as eoan
Public bug reported: [Impact] In eoan we switched the datasource configuration from shipping the NoCloud config on the rootfs to actually doing that in the system-boot boot partition. For our images to be consistent throughout various supported series, those changes should be backported to bionic. Also, since we basically use one gadget tree for all the series, we'd want the bionic parts up-to-date in case we introduce breaking changes in the gadget. [Test Case] 1. Image build test. * Start a bionic-proposed classic raspi3 build * Make sure the build succeeds 2. Test if datasource is correct. * Boot up the newly built raspi3 image * Make sure that you can log in with the usual default ubuntu/ubuntu user * Check that the boot partition (as mounted in /boot/firmware) has the user-data file 3. Check if raspi2 did not regress. * Start a bionic-proposed raspi2 build * Make sure the build succeeds * Boot the image * Make sure you can correctly log in with the default ubuntu/ubuntu user [Regression Potential] There is a minimal regression potential related to this upload as we are introducing a small delta from what we have in eoan. In eoan we stopped building raspi2 images completely, but for bionic this 'variant' is still supported, so first regression potential I see is in breaking the default user configuration for those images. Other regression potential might be all related to the 999-cpc-fixes hook, in case some configuration is not skipped for certain architectures. ** Affects: livecd-rootfs (Ubuntu) Importance: Medium Assignee: Łukasz Zemczak (sil2100) Status: Fix Released ** Affects: livecd-rootfs (Ubuntu Bionic) Importance: Undecided Assignee: Łukasz Zemczak (sil2100) Status: In Progress ** Also affects: livecd-rootfs (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: livecd-rootfs (Ubuntu Bionic) Assignee: (unassigned) => Łukasz Zemczak (sil2100) ** Changed in: livecd-rootfs (Ubuntu Bionic) Status: New => In Progress ** Changed in: livecd-rootfs (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849472 Title: Bionic raspi3 images should have the same cloud-init datasource setup as eoan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1849472/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1724895] Re: MTU not applied on private ethernet interfaces
Still broken on 18.04.3 with netplan 0.98-0ubuntu1~18.04.1 and systemd 237-3ubuntu10.31. With dhcp set to false, use-mtu seems to be useless. The only affordable workaround I found is to create an override .link file that only matches by mac address and set the MTU. For example: [Match] MACAddress=aa:bb:cc:dd:ee:ff [Link] MTUBytes=9000 saved as /etc/systemd/network/10-cmonsystemdsetmtuforme.link. Reboot (maybe also "systemctl restart systemd-networkd" works) and mtu should be set. Hoping for a fix in the near future. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1724895 Title: MTU not applied on private ethernet interfaces To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1724895/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849012] Re: bionic/linux-oem: 4.15.0-1060.69 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-lrm Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package-lrm Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package-meta Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-signed Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package-signed Status: Fix Committed => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1849035 packages: lrm: linux-restricted-modules-oem main: linux-oem meta: linux-meta-oem signed: linux-signed-oem - phase: Packaging - phase-changed: Wednesday, 23. October 2019 04:30 UTC + phase: Holding before Promote to Proposed + phase-changed: Wednesday, 23. October 2019 10:31 UTC reason: - prepare-package: Pending -- package not yet uploaded - prepare-package-lrm: Pending -- package not yet uploaded - prepare-package-meta: Pending -- package not yet uploaded - prepare-package-signed: Pending -- package not yet uploaded + promote-to-proposed: Ongoing -- builds not complete in ppa lrm:depwait,main:building,meta:depwait,signed:depwait variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849012 Title: bionic/linux-oem: 4.15.0-1060.69 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849012/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849001] Re: bionic/linux-oem-osp1: 5.0.0-1026.29 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1849003 packages: lrm: linux-restricted-modules-oem-osp1 main: linux-oem-osp1 meta: linux-meta-oem-osp1 signed: linux-signed-oem-osp1 - phase: Ready for Packaging - phase-changed: Tuesday, 22. October 2019 02:12 UTC + phase: Packaging + phase-changed: Wednesday, 23. October 2019 10:30 UTC reason: - prepare-package: Pending -- version not specified + prepare-package: Pending -- package not yet uploaded + prepare-package-lrm: Pending -- package not yet uploaded + prepare-package-meta: Pending -- package not yet uploaded + prepare-package-signed: Pending -- package not yet uploaded variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849001 Title: bionic/linux-oem-osp1: 5.0.0-1026.29 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849001/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849001] Re: bionic/linux-oem-osp1: 5.0.0-1026.29 -proposed tracker
** Summary changed: - bionic/linux-oem-osp1: -proposed tracker + bionic/linux-oem-osp1: 5.0.0-1026.29 -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) => Timo Aaltonen (tjaalton) ** Changed in: kernel-sru-workflow/prepare-package-lrm Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-lrm Assignee: Canonical Kernel Team (canonical-kernel-team) => Timo Aaltonen (tjaalton) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Timo Aaltonen (tjaalton) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Timo Aaltonen (tjaalton) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849001 Title: bionic/linux-oem-osp1: 5.0.0-1026.29 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849001/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849437] Re: [snap] user has no permissions to open downloaded files if download folder is set to /tmp
That's a known problem. Strictly confined snaps are not allowed to read/write to the system-wide /tmp, that would open the door to spying on other applications and more advanced malicious behaviours. Hence /tmp being remapped to /tmp/snap.chromium/tmp. This is discussed in details there: https://forum.snapcraft.io/t /sharing-files-via-tmp/1613. ** Changed in: chromium-browser (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849437 Title: [snap] user has no permissions to open downloaded files if download folder is set to /tmp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1849437/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845595] Re: System got hang after login
The issue reproduces on the Eoan final release version. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1845595 Title: System got hang after login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845595/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826125] Re: Dell XPS 13 9380 flickering (Whiskey Lake)
Just updated my ubuntu to 19.10 with kernel 5.3.0-19-generic and the problem is still here - so not fixed upstream. Will attempt to recompile this kernel using branch from https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1826125/comments/91 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1826125 Title: Dell XPS 13 9380 flickering (Whiskey Lake) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1826125/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848492] Re: Change Config Option CONFIG_MEMORY_HOTPLUG_DEFAULT_ONLINE for s390x from yes to no
Successfully verified on bionic on an LPAR with 32GB Initial and 10GB Reserved. Hence with std. kernel free shows ~31GB and with prop. kernel ~41GB. ** Attachment added: "bionic_verification.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848492/+attachment/5299445/+files/bionic_verification.txt ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848492 Title: Change Config Option CONFIG_MEMORY_HOTPLUG_DEFAULT_ONLINE for s390x from yes to no To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1848492/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1841936] Re: Rebuild openssl 1.1.1 to pickup TLSv1.3 (bionic) and unbreak existing builds against 1.1.1 (dh key size)
** Merge proposal linked: https://code.launchpad.net/~paelzer/ubuntu/+source/haproxy/+git/haproxy/+merge/374589 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1841936 Title: Rebuild openssl 1.1.1 to pickup TLSv1.3 (bionic) and unbreak existing builds against 1.1.1 (dh key size) To manage notifications about this bug go to: https://bugs.launchpad.net/haproxy/+bug/1841936/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848984] Re: disco/linux-aws: 5.0.0-1020.22 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => In Progress ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/verification-testing Status: Confirmed => In Progress ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1849003 packages: main: linux-aws meta: linux-meta-aws - phase: Promote to Proposed - phase-changed: Tuesday, 22. October 2019 20:03 UTC + phase: Testing + phase-changed: Wednesday, 23. October 2019 10:19 UTC + proposed-announcement-sent: true + proposed-testing-requested: true reason: - promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync + automated-testing: Ongoing -- testing in progress + regression-testing: Ongoing -- testing in progress + security-signoff: Pending -- waiting for signoff + verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws-5.0: bug 1848983 variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848984 Title: disco/linux-aws: 5.0.0-1020.22 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1848984/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847710] Re: [ThinkPad X1 Yoga 4th Gen][20QGZ4MTUS, Realtek ALC285, Speaker, Internal] The Volume remains the same value.
The issue reproduces on Eoan final release version. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847710 Title: [ThinkPad X1 Yoga 4th Gen][20QGZ4MTUS, Realtek ALC285, Speaker, Internal] The Volume remains the same value. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1847710/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847708] Re: [ThinkPad X1 Yoga 4th Gen] [HDA-Intel - HDA Intel PCH, recording] Internal mic is useless in Ubuntu 19.10
The issue reproduces on Eeon Final release version. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847708 Title: [ThinkPad X1 Yoga 4th Gen] [HDA-Intel - HDA Intel PCH, recording] Internal mic is useless in Ubuntu 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1847708/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848981] Re: disco/linux-raspi2: 5.0.0-1021.21 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/certification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/security-signoff Status: New => In Progress ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/verification-testing Status: Confirmed => In Progress ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1849003 packages: main: linux-raspi2 meta: linux-meta-raspi2 - phase: Promote to Proposed - phase-changed: Wednesday, 23. October 2019 07:50 UTC + phase: Testing + phase-changed: Wednesday, 23. October 2019 10:16 UTC + proposed-announcement-sent: true + proposed-testing-requested: true reason: - promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync + automated-testing: Ongoing -- testing in progress + certification-testing: Ongoing -- testing in progress + security-signoff: Pending -- waiting for signoff + verification-testing: Ongoing -- testing in progress variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848981 Title: disco/linux-raspi2: 5.0.0-1021.21 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1848981/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849011] Re: bionic/linux-snapdragon: 4.15.0-1067.74 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1849035 packages: main: linux-snapdragon meta: linux-meta-snapdragon phase: Promote to Proposed phase-changed: Wednesday, 23. October 2019 09:11 UTC reason: - promote-to-proposed: Pending -- package copies requested to Proposed main:missing,meta:missing + promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync trackers: bionic/linux-snapdragon/dragonboard-kernel: bug 1849010 variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849011 Title: bionic/linux-snapdragon: 4.15.0-1067.74 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849011/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848997] Re: bionic/linux-oracle-5.0: 5.0.0-1006.10~18.04.1 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1848998 packages: lrm: linux-restricted-modules-oracle-5.0 main: linux-oracle-5.0 meta: linux-meta-oracle-5.0 signed: linux-signed-oracle-5.0 - phase: Ready for Packaging - phase-changed: Tuesday, 22. October 2019 14:52 UTC + phase: Packaging + phase-changed: Wednesday, 23. October 2019 10:20 UTC reason: - prepare-package: Pending -- version not specified + prepare-package: Pending -- package not yet uploaded + prepare-package-lrm: Pending -- package not yet uploaded + prepare-package-meta: Pending -- package not yet uploaded + prepare-package-signed: Pending -- package not yet uploaded variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848997 Title: bionic/linux-oracle-5.0: 5.0.0-1006.10~18.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1848997/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847709] Re: [ThinkPad X1 Yoga 4th Gen] [HDA-Intel - HDA Intel PCH, recording] Mic-mute key and its LED can not work on Ubuntu 19.10
The issue reproduces on Eoan final release version. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847709 Title: [ThinkPad X1 Yoga 4th Gen] [HDA-Intel - HDA Intel PCH, recording] Mic- mute key and its LED can not work on Ubuntu 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1847709/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1841936] Re: Rebuild openssl 1.1.1 to pickup TLSv1.3 (bionic) and unbreak existing builds against 1.1.1 (dh key size)
** Description changed: - [Impact] + [Impact-Bionic] * openssl 1.1.1 has been backported to Bionic for its longer support upstream period * That would allow the extra feature of TLSv1.3 in some consuming packages what seems "for free". Just with a no change rebuild it would pick that up. + [Impact Disco-Focal] + + * openssl >=1.1.1 is in Disco-Focal already and thereby it was built +against that already. That made it pick up TLSv1.3, but also a related +bug that broke the ability to control the DHE key, it was always in +"ECDH auto" mode. Therefore the daemon didn't follow the config +anymore. +Upgraders would regress having their DH key behavior changed +unexpectedly. + [Test Case] * run "haproxy -vv" and check the reported TLS versions to include 1.3 - [Regression Potential] + [Regression Potential-Bionic] * This should be low, the code already runs against the .so of the newer openssl library. This would only make it recognize the newer TLS support. i'd expect more trouble as-is with the somewhat big delta between what it was built against vs what it runs with than afterwards. * [1] and [2] indicate that any config that would have been made for TLSv1.2 [1] would not apply to the v1.3 as it would be configured in [2]. It is good to have no entry for [2] yet as following the defaults of openssl is the safest as that would be updated if new insights/CVEs are known. But this could IMHO be the "regression that I'd expect", one explcitly configured the v1.2 things and once both ends support v1.3 that might be auto-negotiated. One can then set "force-tlsv12" but that is an administrative action [3] * Yet AFAIK this fine grained control [2] for TLSv1.3 only exists in >=1.8.15 [4] and Bionic is on haproxy 1.8.8. So any user of TLSv1.3 in - Bionic haproxy would have to stay without that. There are further -changes to TLS v1.3 handling enhancements [5] but also fixes [6] which -aren't in 1.8.8 in Bionic. + Bionic haproxy would have to stay without that. There are further + changes to TLS v1.3 handling enhancements [5] but also fixes [6] which + aren't in 1.8.8 in Bionic. So one could say enabling this will enable an inferior TLSv1.3 and one - might better not enable it, for an SRU the bar to not break old -behavior is intentionally high - I tried to provide as much as possible -background, the decision is up to the SRU team. + might better not enable it, for an SRU the bar to not break old + behavior is intentionally high - I tried to provide as much as possible + background, the decision is up to the SRU team. + + [Regression Potential-Disco-Focal] + + * The fixes let the admin regain control of the DH key configuration +which is the fix. But remember that the default config didn't specify +any. Therefore we have two scenarios: +a) an admin had set custom DH parameters which were ignored. He had no + chance to control them and needs the fix. He might have been under + the impression that his keys are safe (there is a CVE against small + ones) and only now is he really safe -> gain high, regression low +b) an admin had not set anything, the default config is meant to use + (compatibility) and the program reported "I'm using 1024, but you + should set it higher". But what really happened was ECDH auto mode + which has longer keys and different settings. Those systems will + be "fixed" by finally following the config, but that means the key + will "now" after the fix be vulnerable. + -> for their POV a formerly secure setup will become vulnerable +I'd expect that any professional setup would use explicit config as it +has seen the warning since day #1 and also any kind of deployment +recipes should use big keys. So the majority of users should be in (a). +c) And OTOH there are people like the reporter who strictly NEED the + key to be small for their devices they have to support. They will + finally be able to use the small keys again which formerly was + impossible. + +Summary: (a) good (c) good, (b) good, but a regression in some POV [1]: https://cbonte.github.io/haproxy-dconv/1.8/configuration.html#3.1-ssl-default-bind-ciphers [2]: https://cbonte.github.io/haproxy-dconv/1.8/configuration.html#3.1-ssl-default-bind-ciphersuites [3]: https://www.haproxy.com/documentation/hapee/1-8r2/traffic-management/tls/#define-bind-directives-on-the-frontend [4]: https://github.com/haproxy/haproxy/blob/master/CHANGELOG#L2131 [5]: https://github.com/haproxy/haproxy/commit/526894ff3925d272c13e57926aa6b5d9d8ed5ee3 [6]: https://github.com/haproxy/haproxy/commit/bc34cd1de2ee80de63b5c4d319a501fc0d4ea2f5 [Other Info] * If this is nack'ed we will need an upload that prevents to
