[Bug 1848402] Re: No indication that thunderbird is starting
Yes, using "Launch email client" fixes the problem for me. -- 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 1844805] Re: virtualbox, virtualbox-dkms, virtualbox-qt fail during upgrade from 19.04 to 19.10
If the system was updated to the tip of disco before being upgraded as above this should not occur as the kernel in disco was fixed to avoid this issue. I was under the impression you had to be updated to the latest -updates packages to do an upgrade, so I am supprised it let you do this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1844805 Title: virtualbox, virtualbox-dkms, virtualbox-qt fail during upgrade from 19.04 to 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1844805/+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: Promote to Proposed phase-changed: Wednesday, 23. October 2019 12:51 UTC reason: - promote-to-proposed: Ongoing -- review in progress + promote-to-proposed: Stalled -- 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 1849512] [NEW] Creating a new user on top of ZFS filesystem does not create a new dataset for his home directory
Public bug reported: When you're using the experimental ZFS on root installation on Ubuntu 19.10 initially you're creating one user. This user has a home directory mounted on different ZFS dataset like in this case: https://paste.ubuntu.com/p/CSsNtt5j6c/ Afterwards when you're adding new users via the gnome-control-center or with adduser, the new users home directories are created on rpool/USERDATA but they don't have separate ZFS datasets. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-control-center 1:3.34.1-1ubuntu2 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 18:12:56 2019 InstallationDate: Installed on 2019-10-23 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan ** Summary changed: - Creating a new user on top of ZFS filesystem does not create a new datase for his home directory + Creating a new user on top of ZFS filesystem does not create a new dataset for his home directory ** Description changed: - When you're using the experimental ZFS on root installation on Ubuntu 19.10 initially you're creating one user. This user have a home directory mounted on different ZFS dataset like in this case: + When you're using the experimental ZFS on root installation on Ubuntu 19.10 initially you're creating one user. This user has a home directory mounted on different ZFS dataset like in this case: https://paste.ubuntu.com/p/CSsNtt5j6c/ Afterwards when you're adding new users via the gnome-control-center or with adduser, the new users home directories are created on rpool/USERDATA but they don't have separate ZFS datasets. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-control-center 1:3.34.1-1ubuntu2 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 18:12:56 2019 InstallationDate: Installed on 2019-10-23 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849512 Title: Creating a new user on top of ZFS filesystem does not create a new dataset for his home directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1849512/+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 can also observe the issue if I create a custom shortcut with command
"thunderbird".
However if I use/redefine the existing shortcut for "Launch email client" (in
the Launchers category), then the issue isn't observable.
The difference lies in the way thunderbird is invoked. For the existing
"Launch email client" shortcut, unity-settings-daemon invokes the
default mailto: URL handler, which calls
g_app_info_get_default_for_uri_scheme("mailto").
I guess the DE (Unity or others) can't easily match a starting process
for thunderbird to an existing desktop file, whereas in the case of the
mailto handler it definitely has all the information needed.
I'd suggest using the existing shortcut and redefining it to suit your
habits.
** Changed in: thunderbird (Ubuntu)
Status: Incomplete => Invalid
--
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 1849015] Re: xenial/linux-aws-hwe: 4.15.0-1053.55~16.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: 1849016 packages: main: linux-aws-hwe meta: linux-meta-aws-hwe phase: Holding before Promote to Proposed phase-changed: Wednesday, 23. October 2019 14:47 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa main:building,meta:building + promote-to-proposed: Ongoing -- builds not complete in ppa main:building 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/1849015 Title: xenial/linux-aws-hwe: 4.15.0-1053.55~16.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849015/+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
and dmesg ** Attachment added: "dmesg-5.3.0.19-18+lp1846016.out" https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1847921/+attachment/5299500/+files/dmesg-5.3.0.19-18+lp1846016.out -- 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 1847921] Re: "iwlwifi 0000:04:00.0: Microcode SW error detected. Restarting 0x12000000." at boot
Hi, I followed your instructions and installed 5.3.0-17.18+lp1846016. I didn't see any errors during boot just blinking cursor in left upper corner of display. However boot took probably same long time as when there were errors and, as I wrote, screen was black with blinking cursor instead of standard Ubuntu booting screen. I am attaching requested files "uname -a" output Linux p50 5.3.0-17-generic #18+lp1846016-Ubuntu SMP Fri Oct 4 14:18:23 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux ** Attachment added: "lspci-5.3.0.19-18+lp1846016.out" https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1847921/+attachment/5299499/+files/lspci-5.3.0.19-18+lp1846016.out -- 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 1607254] Re: pidgin-sipe should depend on package pidgin
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: pidgin-sipe (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/1607254 Title: pidgin-sipe should depend on package pidgin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pidgin-sipe/+bug/1607254/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847979] Re: package xserver-xorg-video-nvidia-430 430.26-0ubuntu0.18.04.2 failed to install/upgrade: trying to overwrite '/usr/share/X11/xorg.conf.d/10-nvidia.conf', which is also in package xse
** Also affects: nvidia-graphics-drivers-435 (Ubuntu) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-430 (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-435 (Ubuntu Bionic) 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/1847979 Title: package xserver-xorg-video-nvidia-430 430.26-0ubuntu0.18.04.2 failed to install/upgrade: trying to overwrite '/usr/share/X11/xorg.conf.d/10-nvidia.conf', which is also in package xserver-xorg-video-nvidia-418 418.74-0ubuntu0~18.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1847979/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849142] Re: Discord and appindicator extension slows down ui
I've only tried in KDE as well. The icon is there but the icon change that is supposes to happen when speaking does not show, but i guess that's on discord to fix. However KDE don't have a slowdown while speaking like gnome does with the indicator extension installed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849142 Title: Discord and appindicator extension slows down ui To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1849142/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849325] Re: 18.04 Server Install - Software RAID setup crashes
Hi Andy, Please do file a bug on the NIC issues; they certainly should work and the modules should be present. Currently the installer does not create a persistent location. A few options here are: 1) cat the file to screen and take photos; you won't be the first to submit a bug report with screenshots 2) Depending on your usb disk layout it's possible to do that; you can sudo bash on tty2 to get root there. If you've just copied the iso directly to the USB stick, then the partition layout doesn't have space. 3) You could modify one of the target disks from the live installer; create a partition on the disk, format it with ext4, mount and then copy the /var/log/installer dir to the partition -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849325 Title: 18.04 Server Install - Software RAID setup crashes To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1849325/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849365] Re: The `update-java-alternatives` script does not update the symbolic link `/usr/lib/jvm/default-java` generated by the `default-jre-headless` package
/usr/lib/jvm/default-java is used for packaging and is not supposed to be handled by alternatives. javaws shouldn't rely on that. ** Also affects: icedtea-web (Ubuntu) Importance: Undecided Status: New ** Changed in: java-common (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/1849365 Title: The `update-java-alternatives` script does not update the symbolic link `/usr/lib/jvm/default-java` generated by the `default-jre- headless` package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/icedtea-web/+bug/1849365/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848918] Re: [snap] "Save As" dialogue: Clicking on Home button opens unexpected folder
*** This bug is a duplicate of bug 1798450 *** https://bugs.launchpad.net/bugs/1798450 ** This bug has been marked a duplicate of bug 1798450 [snap] File dialogs show snap's home directory instead of user's -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848918 Title: [snap] "Save As" dialogue: Clicking on Home button opens unexpected folder To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1848918/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849015] Re: xenial/linux-aws-hwe: 4.15.0-1053.55~16.04.1 -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-meta Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package-meta 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: 1849016 packages: main: linux-aws-hwe meta: linux-meta-aws-hwe - phase: Packaging - phase-changed: Tuesday, 22. October 2019 23:50 UTC + phase: Holding before Promote to Proposed + phase-changed: Wednesday, 23. October 2019 14:47 UTC reason: - prepare-package: Pending -- package not yet uploaded - prepare-package-meta: Pending -- package not yet uploaded + promote-to-proposed: Ongoing -- builds not complete in ppa main:building,meta:building 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/1849015 Title: xenial/linux-aws-hwe: 4.15.0-1053.55~16.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849015/+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
** 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: automated-testing: Stalled -- testing FAILED - promote-to-proposed: Stalled -- packages are in the wrong component + 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 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 1848402] Re: No indication that thunderbird is starting
Also observable using Super+M in Xubuntu which uses that shortcut to launch the default mail reader. -- 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 1848919] Re: [snap] Permission denied on Private encrypted folder
Indeed I can see the rules you mention in /etc/apparmor.d/abstractions/base, which is included by /var/lib/snapd/apparmor/profiles/snap.chromium.chromium. However I can reliably reproduce the issue, and I'm seeing the following denial: AVC apparmor="DENIED" operation="open" profile="snap.chromium.chromium" name="/home/ubuntu/.Private/" pid=11167 comm="pool" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848919 Title: [snap] Permission denied on Private encrypted folder To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1848919/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849018] Re: bionic/linux-gke-4.15: 4.15.0-1047.50 -proposed tracker
** Summary changed: - bionic/linux-gke-4.15: -proposed tracker + bionic/linux-gke-4.15: 4.15.0-1047.50 -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) => Marcelo Cerri (mhcerri) ** 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) => Marcelo Cerri (mhcerri) ** 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) => Marcelo Cerri (mhcerri) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849018 Title: bionic/linux-gke-4.15: 4.15.0-1047.50 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849018/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1818974] Re: Ubuntu 18.04 HWE Kernel 4.18 / 5.0 - Standby wakeup user session crash
** Attachment added: "Xorg.0.log.old" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818974/+attachment/5299497/+files/Xorg.0.log.old -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1818974 Title: Ubuntu 18.04 HWE Kernel 4.18 / 5.0 - Standby wakeup user session crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818974/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1818974] Re: Ubuntu 18.04 HWE Kernel 4.18 / 5.0 - Standby wakeup user session crash
** Attachment added: "Xorg.0.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818974/+attachment/5299498/+files/Xorg.0.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1818974 Title: Ubuntu 18.04 HWE Kernel 4.18 / 5.0 - Standby wakeup user session crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818974/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849018] Re: bionic/linux-gke-4.15: 4.15.0-1047.50 -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: main: linux-gke-4.15 meta: linux-meta-gke-4.15 signed: linux-signed-gke-4.15 - phase: Ready for Packaging - phase-changed: Monday, 21. October 2019 19:23 UTC + phase: Packaging + phase-changed: Wednesday, 23. October 2019 14:27 UTC reason: - prepare-package: Pending -- version not specified + prepare-package: Pending -- package not yet uploaded + prepare-package-meta: Pending -- package not yet uploaded + prepare-package-signed: Pending -- package not yet uploaded trackers: bionic/linux-gke-4.15/gke-kernel: bug 1849017 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/1849018 Title: bionic/linux-gke-4.15: 4.15.0-1047.50 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1849018/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1818974] Re: Ubuntu 18.04 HWE Kernel 4.18 / 5.0 - Standby wakeup user session crash
Kernel 5.0.0-32-generic Put in standby on docking station disconnected wake up user session crashed ** Attachment added: "journalctl--since=today.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818974/+attachment/5299496/+files/journalctl--since%3Dtoday.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1818974 Title: Ubuntu 18.04 HWE Kernel 4.18 / 5.0 - Standby wakeup user session crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818974/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840835] Re: High power consumption using 5.0.0-25-generic
** Description changed: - After updating to 5.0.0-25-generic kernel, battery life is considerably - less and power consumption is about 10 watts more idle, using integrated - graphics. This is a hybrid GPU laptop Intel HD 630/GP107M, and a - possible cause is not powering off the dedicated GPU completely while - using the integrated. + === SRU Justification === + [Impact] + Some Nvidia graphics card has audio function in addition to video + function. When the video function is not bound to any driver, the audio + function can't be runtime suspended, hence preventing the power + resources from being turned off. + + [Fix] + Allow Nvidia audio function to be runtime suspended. + + [Test] + The user reported the fix works. + + [Regression Potential] + Low. It only allows the audio function of discrete Nvidia GPU to be + runtime suspended. Regular audio or audio function with a discrete GPU + already bound to a driver are unaffected. + + === Original Bug Report === + After updating to 5.0.0-25-generic kernel, battery life is considerably less and power consumption is about 10 watts more idle, using integrated graphics. This is a hybrid GPU laptop Intel HD 630/GP107M, and a possible cause is not powering off the dedicated GPU completely while using the integrated. nvidia-driver-430 GP107M [GeForce GTX 1050 Mobile] ** Changed in: linux (Ubuntu) Assignee: Kai-Heng Feng (kaihengfeng) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1840835 Title: High power consumption using 5.0.0-25-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1840835/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848143] Re: linux: soft lockup - CPU stuck in nft_connlimit
** Tags added: kernel-net -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848143 Title: linux: soft lockup - CPU stuck in nft_connlimit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1848143/+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
The following packages ended up in the wrong component in the Proposed pocket: linux-restricted-modules-aws-5.0 5.0.0-1020.22~18.04.1 - is in restricted instead of multiverse linux-modules-nvidia-390-5.0.0-1020-aws 5.0.0-1020.22~18.04.1 - is in restricted instead of multiverse linux-modules-nvidia-390-aws-edge 5.0.0-1020.22~18.04.1 - is in restricted instead of multiverse linux-modules-nvidia-418-5.0.0-1020-aws 5.0.0-1020.22~18.04.1 - is in restricted instead of multiverse linux-modules-nvidia-418-aws-edge 5.0.0-1020.22~18.04.1 - is in restricted instead of multiverse Once this is fixed, set the promote-to-proposed to Fix Released again ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Incomplete -- 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 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: Incomplete => 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/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 1848983] Re: bionic/linux-aws-5.0: 5.0.0-1020.22~18.04.1 -proposed tracker
The following packages ended up in the wrong component in the Proposed pocket: linux-restricted-modules-aws-5.0 5.0.0-1020.22~18.04.1 - is in restricted instead of multiverse linux-modules-nvidia-390-5.0.0-1020-aws 5.0.0-1020.22~18.04.1 - is in restricted instead of multiverse linux-modules-nvidia-390-aws-edge 5.0.0-1020.22~18.04.1 - is in restricted instead of multiverse linux-modules-nvidia-418-5.0.0-1020-aws 5.0.0-1020.22~18.04.1 - is in restricted instead of multiverse linux-modules-nvidia-418-aws-edge 5.0.0-1020.22~18.04.1 - is in restricted instead of multiverse Once this is fixed, set the promote-to-proposed to Fix Released again ** Changed in: kernel-sru-workflow/promote-to-proposed Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Incomplete -- 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 1848919] Re: [snap] Permission denied on Private encrypted folder
Encrypted home is typically setup as ~/.Private, not ~/Private and the
policy already allows:
owner @{HOME}/.Private/** mrixwlk,
owner @{HOMEDIRS}/.ecryptfs/*/.Private/** mrixwlk,
The home interface should already allow ~/Private. What is the denial
you see in the logs?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848919
Title:
[snap] Permission denied on Private encrypted folder
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1848919/+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
Hi Steve, Dmitri, Do you have more details on the grub process. Curtin already runs grub on one or more devices as needed. Are there any specific parameters or settings or will the grub install process detect hybrid configuration? Are there any restrictions on how the partitions are ordered or numbered? ** Changed in: curtin (Ubuntu) Status: Triaged => Incomplete -- 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 1779156] Re: lxc 'delete' fails to destroy ZFS filesystem 'dataset is busy'
Bug status updated accordingly. I set the linux task to Invalid as the kernel was not involved after all. Thanks again Stéphane and Colin! ** Changed in: lxc (Ubuntu) Status: Confirmed => Fix Released ** Changed in: lxc (Ubuntu Cosmic) Status: Confirmed => Fix Released ** Changed in: lxc (Ubuntu Disco) Status: New => Fix Released ** Changed in: lxc (Ubuntu Eoan) Status: Confirmed => Fix Released ** No longer affects: linux (Ubuntu Eoan) ** No longer affects: linux (Ubuntu Disco) ** No longer affects: linux (Ubuntu Cosmic) ** Changed in: linux (Ubuntu) Status: Triaged => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1779156 Title: lxc 'delete' fails to destroy ZFS filesystem 'dataset is busy' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779156/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848771] Re: Reboot after resume from suspend (deep)
Hello, everybody. My notebook (ThinkPad T530) apparently goes into sleep mode according to the log (see below). In reality it hangs up: The screen (backlights) stays on, but shows no content (black image). The device can't be woken up anymore. I have to switch it off (Power Off for 5 sec.). The problem occurred immediately after upgrading Kubuntu from version 19.04 to 19.10. The system was put into operation years ago with version 14.04 and has not been reinstalled since then, but has always been upgraded to the next version by "do-release-upgrade". journalctl -b -1 -e: Okt 23 15:23:13 kubuntumobile NetworkManager[1075]: [1571836993.8059] manager: sleep: sleep requested (sleeping: Okt 23 15:23:13 kubuntumobile NetworkManager[1075]: [1571836993.8090] device (eth0): state change: unavailable -> Okt 23 15:23:14 kubuntumobile org.kde.kpasswdserver[2591]: org.kde.kio.kpasswdserver: User = "" , WindowId = 0 Okt 23 15:23:14 kubuntumobile kernel: e1000e: eth0 NIC Link is Down Okt 23 15:23:14 kubuntumobile charon[2233]: 11[KNL] interface eth0 deactivated Okt 23 15:23:14 kubuntumobile NetworkManager[1075]: [1571836994.0943] device (cdc-wdm2): state change: unavailabl Okt 23 15:23:14 kubuntumobile NetworkManager[1075]: [1571836994.0983] manager: NetworkManager state is now ASLEEP Okt 23 15:23:14 kubuntumobile whoopsie[2172]: [15:23:14] offline Okt 23 15:23:14 kubuntumobile ModemManager[1036]: [/dev/cdc-wdm2] channel destroyed Okt 23 15:23:24 kubuntumobile org.kde.kpasswdserver[2591]: org.kde.kio.kpasswdserver: User = "" , WindowId = 0 Okt 23 15:23:34 kubuntumobile org.kde.kpasswdserver[2591]: org.kde.kio.kpasswdserver: User = "" , WindowId = 0 Okt 23 15:23:38 kubuntumobile mission-control[2912]: disconnect_cb: Disconnect failed: Did not receive a reply. Possible Okt 23 15:23:38 kubuntumobile systemd[1]: Starting TLP suspend/resume... Okt 23 15:23:39 kubuntumobile systemd[1]: Started TLP suspend/resume. Okt 23 15:23:39 kubuntumobile systemd[1]: Reached target Sleep. Okt 23 15:23:39 kubuntumobile systemd[1]: Starting Suspend... Okt 23 15:23:39 kubuntumobile systemd-sleep[21511]: Suspending system... Okt 23 15:23:39 kubuntumobile kernel: PM: suspend entry (deep) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848771 Title: Reboot after resume from suspend (deep) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1848771/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1743592] Re: NGINX fails to start/install/upgrade if IPv6 is completely disabled.
** Description changed:
- There is a known issue where NGINX will not properly run or install when
- IPv6 is fully disabled on a system.
+ [IMPACT]
+
+ With current default vhost listening on IPV6, nginx won't start on fully
+ IPV6 disabled system, expecting to connect to a IPV6 socket on port 80.
+
+ # nginx -t
+ nginx: the configuration file /etc/nginx/nginx.conf syntax is ok
+ ==> nginx: [emerg] socket() [::]:80 failed (97: Address family not supported
by protocol)
+ nginx: configuration file /etc/nginx/nginx.conf test failed
+
+
+ # cat /etc/nginx/sites-enabled/default
+ ..
+ server {
+ listen 80 default_server;
+ listen [::]:80 default_server;
+ ..
+
+
+ [TEST CASE]
+ * Disable ipv6
+ # cat /proc/cmdline
+ ipv6.disable=1
+
+ * Fresh install of nginx:
+ # apt-get install nginx -y
+
+ Output:
+
+ ..
+ Setting up nginx-core (1.14.0-0ubuntu1.6) ...
+ Job for nginx.service failed because the control process exited with error
code.
+ See "systemctl status nginx.service" and "journalctl -xe" for details.
+ invoke-rc.d: initscript nginx, action "start" failed.
+ ● nginx.service - A high performance web server and a reverse proxy server
+Loaded: loaded (/lib/systemd/system/nginx.service; enabled; vendor preset:
enabled)
+Active: failed (Result: exit-code) since Wed 2019-10-23 14:01:26 UTC; 6ms
ago
+ Docs: man:nginx(8)
+ Process: 1005 ExecStartPre=/usr/sbin/nginx -t -q -g daemon on;
master_process on; (code=exited, status=1/FAILURE)
+
+ Oct 23 14:01:26 nginxbionictest1 systemd[1]: Starting A high performance web
server and a reverse proxy server...
+ Oct 23 14:01:26 nginxbionictest1 nginx[1005]: nginx: [emerg] socket() [::]:80
failed (97: Address family not supported by protocol)
+ Oct 23 14:01:26 nginxbionictest1 nginx[1005]: nginx: configuration file
/etc/nginx/nginx.conf test failed
+ Oct 23 14:01:26 nginxbionictest1 systemd[1]: nginx.service: Control process
exited, code=exited status=1
+ Oct 23 14:01:26 nginxbionictest1 systemd[1]: nginx.service: Failed with
result 'exit-code'.
+ Oct 23 14:01:26 nginxbionictest1 systemd[1]: Failed to start A high
performance web server and a reverse proxy server.
+ dpkg: error processing package nginx-core (--configure):
+ installed nginx-core package post-installation script subprocess returned
error exit status 1
+ dpkg: dependency problems prevent configuration of nginx:
+ nginx depends on nginx-core (<< 1.14.0-0ubuntu1.6.1~) | nginx-full (<<
1.14.0-0ubuntu1.6.1~) | nginx-light (<< 1.14.0-0ubuntu1.6.1~) | nginx-extras
(<< 1.14.0-0ubuntu1.6.1~); however:
+ Package nginx-core is not configured yet.
+ Package nginx-full is not installed.
+ Package nginx-light is not installed.
+ Package nginx-extras is not installed.
+ nginx depends on nginx-core (>= 1.14.0-0ubuntu1.6) | nginx-full (>=
1.14.0-0ubuntu1.6) | nginx-light (>= 1.14.0-0ubuntu1.6) | nginx-extras (>=
1.14.0-0ubuntu1.6); however:
+ Package nginx-core is not configured yet.
+ Package nginx-full is not installed.
+ Package nginx-light is not installed.
+ Package nginx-extras is not installed.
+
+ dpkg: error processing package nginx (--configure):
+ dependency problems - leaving unconfigured
+ Processing triggers for systemd (237-3ubuntu10.31) ...
+ No apport report written because the error message indicates its a followup
error from a previous failure.
+
Processing triggers for man-db (2.8.3-2ubuntu0.1)
...
+ Processing triggers for ufw (0.36-0ubuntu0.18.04.1) ...
+ Processing triggers for ureadahead (0.100.0-21) ...
+ Processing triggers for libc-bin (2.27-3ubuntu1) ...
+ Errors were encountered while processing:
+ nginx-core
+ nginx
+ E: Sub-process /usr/bin/dpkg returned an error code (1)
+
+
+ [REGRESSION POTENTIAL]
+
+ LOW.
+
+ Other distributions does that already (Centos and Upstream):
+
+ * nginx.vh.default.conf -> "nginx-1.16.0-1.el8.ngx.src.rpm"
+ server {
+ listen 80;
+ server_name localhost;
+
+ * Upstream nginx:
+ https://github.com/nginx/nginx/blob/master/conf/nginx.conf#L36
+
+ This won't introduce behaviour change for those who upgrade nginx, but
+ it will introduce a behaviour change for those used to have ipv6 listen
+ in the default vhost at fresh package installation.
+
+ But IMHO, the default vhost is a starting point/example, that the admin
+ will anyway have to modify manually or via some automation tool
+ (ansible, chef, puppet, ...)
+
+ So this will only imply that the admin will need to update their recipe
+ to add the ipv6 listen in their vhost config (ONLY if needed).
+
+ I don't see any major blocker here.
+
+ [OTHER INFORMATION]
+
+ * Debian upstream bug:
+ https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942817
+
+ [ORIGINAL DESCRIPTION]
+ There is a known issue where NGINX will not properly run or install when IPv6
is fully disabled on a
[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 -- boot-testing-requested: true kernel-stable-master-bug: 1849035 packages: lrm: linux-restricted-modules-oem main: linux-oem meta: linux-meta-oem signed: linux-signed-oem - phase: Ready for Promote to Proposed - phase-changed: Wednesday, 23. October 2019 13:33 UTC + phase: Promote to Proposed + phase-changed: Wednesday, 23. October 2019 14:10 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/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 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: Incomplete => 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/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 1849435] Re: could not find a distribution template for Ubuntu/focal
package python-apt is not installed. should I install it? thanks orrado@corrado-p7-ff-1021:~$ apt policy python-apt python-apt: Installed: (none) Candidate: 1.9.0ubuntu1 Version table: 1.9.0ubuntu1 500 500 http://it.archive.ubuntu.com/ubuntu focal/universe amd64 Packages corrado@corrado-p7-ff-1021:~$ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849435 Title: could not find a distribution template for Ubuntu/focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1849435/+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/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/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 1741860] Please test proposed package
Hello bugproxy, or anyone else affected, Accepted makedumpfile into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/makedumpfile/1:1.6.5-1ubuntu1~18.04.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1741860 Title: Use the kernel default for crashkernel offset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1741860/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1740106] Re: Gnome terminal not starting, timeout reached (bionic)
I too have the Error constructing proxy for org.gnome.Terminal:/org/gnome/Terminal/Factory0: Error calling StartServiceByName for org.gnome.Terminal: Timeout was reached problem, but it only affects one user. $ cat /etc/default/locale LANG=en_US.UTF-8 LC_ALL=en_US.UTF-8 $ ... which should be the UK/GB version because that's where I live, but for testing I set it as above. I don't have chrome remote desktop and never have had. It works for my test user logins, so it must be something in my environment. It's not a shell startup problem because I see the error message if I run it from an xterm, and the xterm works fine. There must be something else going on. David -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1740106 Title: Gnome terminal not starting, timeout reached (bionic) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1740106/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1681909] Re: kdump is not captured in remote host when kdump over ssh is configured
Hello bugproxy, or anyone else affected, Accepted makedumpfile into disco-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/makedumpfile/1:1.6.5-1ubuntu1.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-disco to verification-done-disco. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-disco. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: makedumpfile (Ubuntu Disco) Status: In Progress => Fix Committed ** Tags removed: verification-done verification-done-disco ** Tags added: verification-needed verification-needed-disco ** Changed in: makedumpfile (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags removed: verification-done-bionic ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1681909 Title: kdump is not captured in remote host when kdump over ssh is configured To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1681909/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1844805] Re: virtualbox, virtualbox-dkms, virtualbox-qt fail during upgrade from 19.04 to 19.10
Wow, Gianfranco. As someone who works on Debian / Ubuntu would it not be preferable for you to make at least a modicum of effort to route an issue like this to the appropriate people rather than merely repeatedly trying to close the bug report? In the short time since 19.10 was officially released this bug has been reported by 11 people. It's a SIGNIFICANT ISSUE. Rather than engaging in a petty pissing match about whose fault the problem is, can you maybe help get it routed to the people who might be able to fix it? And how is it a kernel issue when the problem is that the virtualbox module code shipped in 19.10 that dkms is trying to compile isn't compatible with the old kernel? ** Also affects: ubuntu-release-upgrader (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/1844805 Title: virtualbox, virtualbox-dkms, virtualbox-qt fail during upgrade from 19.04 to 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1844805/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1743592] Re: NGINX fails to start/install/upgrade if IPv6 is completely disabled.
So IMHO there is 2 ways to fix this:
(1) - We remove the ipv6 listen from the vhost (just like
Centos/Upstream does atm)
# nginx.vh.default.conf -> "nginx-1.16.0-1.el8.ngx.src.rpm"
server {
listen 80;
server_name localhost;
So as upstream nginx:
https://github.com/nginx/nginx/blob/master/conf/nginx.conf#L36
This won't introduce behaviour change for those who upgrade nginx, but
it will introduce a behaviour change for those used to have ipv6 listen
in the default vhost at fresh package installation.
But IMHO, the default vhost is a starting point/example, that the admin
will anyway have to modify manually or via some orchestration tool
(ansible, chef, puppet, ...)
So this will only imply that the admin will need to update their recipe
to add the ipv6 listen in the vhost. I don't see any big blocker here.
(2) We implement a ipv6 detection as describe in the debian bug and
provide a noipv6 vhost and/or a ipv6 vhost depending if ipv6 is
[en|dis]abled on the system. But for me, that seems hacky.
I have a preference for scenario #1.
I have proposed both scenarios to debian, let's see what they say. In
the absence of response from their part, I'll have SRU scenario #1 into
Ubuntu.
I'll give debian maintainer team a week or so before.
- Eric
** Changed in: nginx (Ubuntu)
Assignee: Thomas Ward (teward) => Eric Desrochers (slashd)
** Changed in: nginx (Ubuntu)
Status: Triaged => In Progress
** Also affects: nginx (Ubuntu Eoan)
Importance: Undecided
Status: New
** Also affects: nginx (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: nginx (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: nginx (Ubuntu Disco)
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/1743592
Title:
NGINX fails to start/install/upgrade if IPv6 is completely disabled.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1743592/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828597] Re: KDump boot fails with nr_cpus=1
Hello bugproxy, or anyone else affected, Accepted makedumpfile into disco-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/makedumpfile/1:1.6.5-1ubuntu1.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-disco to verification-done-disco. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-disco. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: makedumpfile (Ubuntu Disco) Status: In Progress => Fix Committed ** Tags removed: verification-done verification-done-disco ** Tags added: verification-needed verification-needed-disco ** Changed in: makedumpfile (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags removed: verification-done-bionic ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828597 Title: KDump boot fails with nr_cpus=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1828597/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1779156] Re: lxc 'delete' fails to destroy ZFS filesystem 'dataset is busy'
best. fix. ever. working after a reboot. $ snap list lxd Name Version RevTracking Publisher Notes lxd 3.18 12211 stablecanonical✓ - -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1779156 Title: lxc 'delete' fails to destroy ZFS filesystem 'dataset is busy' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779156/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1681909] Please test proposed package
Hello bugproxy, or anyone else affected, Accepted makedumpfile into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/makedumpfile/1:1.6.5-1ubuntu1~18.04.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1681909 Title: kdump is not captured in remote host when kdump over ssh is configured To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1681909/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828597] Please test proposed package
Hello bugproxy, or anyone else affected, Accepted makedumpfile into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/makedumpfile/1:1.6.5-1ubuntu1~18.04.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828597 Title: KDump boot fails with nr_cpus=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1828597/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848771] Re: Reboot after resume from suspend (deep)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-release-upgrader (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/1848771 Title: Reboot after resume from suspend (deep) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1848771/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1841288] Please test proposed package
Hello Thadeu, or anyone else affected, Accepted makedumpfile into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/makedumpfile/1:1.6.5-1ubuntu1~18.04.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1841288 Title: does not create compressed dump on 5.0 or later kernels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1841288/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1741860] Re: Use the kernel default for crashkernel offset
Hello bugproxy, or anyone else affected, Accepted makedumpfile into disco-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/makedumpfile/1:1.6.5-1ubuntu1.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-disco to verification-done-disco. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-disco. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Tags removed: verification-done verification-done-disco ** Tags added: verification-needed verification-needed-disco ** Changed in: makedumpfile (Ubuntu Bionic) Status: Won't Fix => Fix Committed ** Tags removed: verification-done-bionic ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1741860 Title: Use the kernel default for crashkernel offset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1741860/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1841288] Please test proposed package
Hello Thadeu, or anyone else affected, Accepted makedumpfile into disco-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/makedumpfile/1:1.6.5-1ubuntu1.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-disco to verification-done-disco. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-disco. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: makedumpfile (Ubuntu Bionic) Status: Won't Fix => Fix Committed ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1841288 Title: does not create compressed dump on 5.0 or later kernels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1841288/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828597] Re: KDump boot fails with nr_cpus=1
** 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/1828597 Title: KDump boot fails with nr_cpus=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1828597/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1743592] Re: NGINX fails to start/install/upgrade if IPv6 is completely disabled.
So IMHO there is 2 ways to fix this:
(1) - We remove the ipv6 listen from the vhost (just like
Centos/Upstream does atm)
# nginx.vh.default.conf
server {
listen 80;
server_name localhost;
So as upstream nginx:
https://github.com/nginx/nginx/blob/master/conf/nginx.conf#L36
This won't introduce behaviour change for those who upgrade nginx, but
it will introduce a behaviour change for those used to have ipv6 listen
in the default vhost at fresh package installation.
But IMHO, the default vhost is a starting point/example, that the admin
will anyway have to modify manually or via some orchestration tool
(ansible, chef, puppet, ...)
So this will only imply that the admin will need to update their recipe
to add the ipv6 listen in the vhost. I don't see any big blocker here.
(2) We implement a ipv6 detection as describe in the debian bug and
provide a noipv6 vhost and/or a ipv6 vhost depending if ipv6 is
[en|dis]abled on the system. But for me, that seems hacky.
I have a preference for scenario #1.
I have proposed both scenarios to debian, let's see what they say. In
the absence of response from their part, I'll have SRU scenario #1 into
Ubuntu.
I'll give debian maintainer team a week or so before.
- Eric
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1743592
Title:
NGINX fails to start/install/upgrade if IPv6 is completely disabled.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1743592/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 784725] Re: [needs-packaging] RStudio
This is a really bug report. But Rstudio is not part of the repository yet. I think R RStudio is one of the most used IDEs for R, especially in social sciences. Therefore it would e great if it could become part of the universe repository. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/784725 Title: [needs-packaging] RStudio To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/784725/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1756476] Re: [needs-packaging] Zotero
I liked to raise this issure again. Zotero is the only comprehensive open source citation manager and it should be available directly. Furthermore it is a standalone software, but I am note sure how much of the code is based on Firefox. These is a well supported PPA for Zotero on Github, too. https://github.com/retorquere/zotero-deb -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1756476 Title: [needs-packaging] Zotero To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zotero-standalone-build/+bug/1756476/+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/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 => Fix Released ** 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 => 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: 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 + phase: Testing + phase-changed: Wednesday, 23. October 2019 13:47 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 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 1848471] Re: No infiniband support in netplan renderer
** Also affects: netplan.io (Ubuntu) Importance: Undecided Status: New ** Changed in: cloud-init Importance: Undecided => Wishlist ** Changed in: cloud-init Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848471 Title: No infiniband support in netplan renderer To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1848471/+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
The following packages ended up in the wrong component in the Proposed pocket: linux-restricted-modules-aws-5.0 5.0.0-1020.22~18.04.1 - is in restricted instead of multiverse linux-modules-nvidia-390-5.0.0-1020-aws 5.0.0-1020.22~18.04.1 - is in restricted instead of multiverse linux-modules-nvidia-390-aws-edge 5.0.0-1020.22~18.04.1 - is in restricted instead of multiverse linux-modules-nvidia-418-5.0.0-1020-aws 5.0.0-1020.22~18.04.1 - is in restricted instead of multiverse linux-modules-nvidia-418-aws-edge 5.0.0-1020.22~18.04.1 - is in restricted instead of multiverse Once this is fixed, set the promote-to-proposed to Fix Released again ** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Incomplete ** 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 => Incomplete ** 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: 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: Ongoing -- packages waiting in -proposed for mirror sync + automated-testing: Stalled -- testing FAILED + promote-to-proposed: Stalled -- packages are in the wrong component + regression-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/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 1849495] [NEW] [linux-azure] Add ability to change scsi queue depth
Public bug reported:
Microsoft would like to request the following patch in the 16.04 and
18.04 Azure kernels:
adfbd028e155 ("scsi: storvsc: Add ability to change scsi queue depth")
This patch will add functionality to allow the SCSI queue depth to be
changed by utilizing the "scsi_change_queue_depth" function.
Commit adfbd028e155 was added to mainline in v5.3-rc1
** Affects: linux-azure (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/1849495
Title:
[linux-azure] Add ability to change scsi queue depth
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1849495/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849142] Re: Discord and appindicator extension slows down ui
Thank you for your bug report. Does the same indicator work in other desktop environment (e.g Unity?) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849142 Title: Discord and appindicator extension slows down ui To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1849142/+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 can confirm this using Ubuntu 18.04 but *only* when starting Thunderbird from a keyboard shortcut. I tried using Super+T and Ctrl- Alt-G. For me, the mouse pointer doesn't change to a spinner until Thunderbird has loaded and is checking for new mail. -- 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 1848919] Re: [snap] Permission denied on Private folder
I can reliably reproduce the issue after creating an encrypted Private directory with ecryptfs-setup-private (see https://help.ubuntu.com/community/EncryptedPrivateDirectory#Setup_Your_Encrypted_Private_Directory). The problem stems from the fact that the home interface doesn't allow reading/writing to hidden folders in $HOME, and the ~/Private folder is actually backed by encrypted data in ~/.Private. This is not specific to chromium, other strictly confined snaps using the home interface would be similarly affected. Interestingly, saving a file to the folder still works, despite the error and the fact that the file dialog is unable to show the contents of the folder. ** Changed in: chromium-browser (Ubuntu) Status: New => Confirmed ** Summary changed: - [snap] Permission denied on Private folder + [snap] Permission denied on Private encrypted folder ** Changed in: chromium-browser (Ubuntu) Importance: Undecided => Low ** 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/1848919 Title: [snap] Permission denied on Private encrypted folder To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1848919/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1837522] Re: GCC Miscompilation of vector shift
** Changed in: ubuntu-z-systems Status: Triaged => 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/1837522 Title: GCC Miscompilation of vector shift To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1837522/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1837522] Re: GCC Miscompilation of vector shift
I've updated lots of series tasks and statuses. Probably best viewed on launchpad https://bugs.launchpad.net/ubuntu/+source/gcc-8/+bug/1837522 Summary: gcc-7 & gcc-8 are fixed in Eoan and Focal Disco will go end of life soon, and is marked as Won't Fix, as there is not enough time to complete toolchain SRU prior to its End of Life. Bionic update is in progress, with test rebuild results being analyzed. However, gcc 7.5 was recently announced for November. We are evaluating doing two gcc-7 SRUs with current results, and then later with 7.5. Or we might postpone currently inflight gcc-7 SRU and include this fix with the gcc 7.5 targetting security pocket. ** Also affects: gcc-5 (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: gcc-6 (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: gcc-7 (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: gcc-8 (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: gcc-5 (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: gcc-6 (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: gcc-7 (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: gcc-8 (Ubuntu Bionic) Importance: Undecided Status: New ** No longer affects: gcc-5 (Ubuntu Bionic) ** No longer affects: gcc-5 (Ubuntu Disco) ** No longer affects: gcc-6 (Ubuntu Bionic) ** No longer affects: gcc-6 (Ubuntu Disco) ** Changed in: gcc-7 (Ubuntu) Status: Triaged => Fix Released ** Changed in: gcc-7 (Ubuntu Disco) Status: New => Won't Fix ** Changed in: gcc-7 (Ubuntu Bionic) Status: New => Triaged ** Changed in: gcc-8 (Ubuntu) Status: Triaged => Fix Released ** Changed in: gcc-8 (Ubuntu Disco) Status: New => Won't Fix ** Changed in: gcc-8 (Ubuntu Bionic) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1837522 Title: GCC Miscompilation of vector shift To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1837522/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849342] Re: Disco libvirt FTBS for the next SRU
While the patch is "correct" there is no issue like that "in Disco". It only affects custom build environments. I have built libvirt in Disco in a PPA today and it worked fine (PPA deleted again). Setting Won't Fix on this one. ** Changed in: libvirt (Ubuntu Disco) Status: Confirmed => Won't Fix ** Changed in: libvirt (Ubuntu Disco) Assignee: Christian Ehrhardt (paelzer) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849342 Title: Disco libvirt FTBS for the next SRU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1849342/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849168] Re: [SRU] Missing build dep libsndfile1-dev discovered
** Description changed: [Impact] * Users have reported the inability to use soundfonts with Carla hosted - synthesizer plugins + allowing them to make sound which they weren't before. * Backporting this to the stable release would fix the problem. * The upload simply adds libsndfile1-dev as a build dependency, also includes an upstream patch from the author to fix incompatibilities with lsp-plugins. [Test Case] * Add any soundfont-utilizing synthesizer plugin to Carla, patch audio out to system out, attempt to play notes either using a MIDI keyboard or using the canvas keyboard in Carla. Carla gives the following error: ad_open(): fatal: no decoder backend available * Using the same procedures after the libsndfile1-dev build dependency is added should result in actual notes being produced. [Regression Potential] - * None, simply adds a build dependency and patch to existing package + * Adding libsndfile1-dev as a build dependency allows synthesizer + plugins to actually make sound, which they weren't before, but instead + were causing the aforementioned error. This is primarily to allow said + synthesizer to use sfz sound fonts. I see no regression potential here. + + * Adding the patch from the upstream developer (in debian/patches) + fixes a compatibility issue with lsp-plugins in which the plugins were + not behaving correctly in some cases. This has been tested to work + upstream, and is included in the beta version of Carla 2.1. No + regression here as it fixes an existing bug upstream. + + * Had to fix the debian/rules file to allow the wine bridges to build + against the version of wine included in the archives due to a bug in + said wine package. Mostly a workaround, but allows build to take place. + If there is a regression here, I do not see it in my testing. (built + correctly in ppa:ubuntustudio-dev/autobuild) [Other Information] * Upload includes a patch from upstream developer to fix compatibility issues with lsp-plugins, and debian/rules has been modified to deal with FTBFS bug introduced by wine-development included in eoan. ** Description changed: [Impact] * Users have reported the inability to use soundfonts with Carla hosted allowing them to make sound which they weren't before. * Backporting this to the stable release would fix the problem. * The upload simply adds libsndfile1-dev as a build dependency, also includes an upstream patch from the author to fix incompatibilities with lsp-plugins. [Test Case] * Add any soundfont-utilizing synthesizer plugin to Carla, patch audio out to system out, attempt to play notes either using a MIDI keyboard or using the canvas keyboard in Carla. Carla gives the following error: ad_open(): fatal: no decoder backend available * Using the same procedures after the libsndfile1-dev build dependency is added should result in actual notes being produced. [Regression Potential] * Adding libsndfile1-dev as a build dependency allows synthesizer plugins to actually make sound, which they weren't before, but instead were causing the aforementioned error. This is primarily to allow said synthesizer to use sfz sound fonts. I see no regression potential here. - * Adding the patch from the upstream developer (in debian/patches) + * Adding the patch from the upstream developer (in debian/patches) fixes a compatibility issue with lsp-plugins in which the plugins were not behaving correctly in some cases. This has been tested to work upstream, and is included in the beta version of Carla 2.1. No regression here as it fixes an existing bug upstream. - * Had to fix the debian/rules file to allow the wine bridges to build + * Had to fix the debian/rules file to allow the wine bridges to build against the version of wine included in the archives due to a bug in said wine package. Mostly a workaround, but allows build to take place. If there is a regression here, I do not see it in my testing. (built correctly in ppa:ubuntustudio-dev/autobuild) [Other Information] * Upload includes a patch from upstream developer to fix compatibility issues with lsp-plugins, and debian/rules has been modified to deal with FTBFS bug introduced by wine-development included in eoan. + + * I have PPU rights on this package, so patch is not included in this + bug report as no sponsorship is needed. Just looking for a "green + light". + + * As of this writing, focal is in freeze, but the fix has been uploaded + there as well and is in-queue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849168 Title: [SRU] Missing build dep libsndfile1-dev discovered To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/carla/+bug/1849168/+subscriptions -- ubuntu-bugs mailing list
[Bug 1833114] Re: print page dialog latency when trying to cancel or to save
As noted in comment #2, I used to be able to observe the problem, but I cannot any longer. I upgraded my laptop to 19.10 a while ago while it was still in development, and I couldn't tell for sure when the problem went away. I didn't do a fresh install, nor did I create a new user or cleaned up settings in any way. @Christopher: from your last comment I understand you're still affected. Have you upgraded to 19.10 ? If not, are you planning to do it in a not- too-distant future? If so I'd be interested in knowing whether this resolves the issue for you. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1833114 Title: print page dialog latency when trying to cancel or to save To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1833114/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840377] Re: Virtual Box crash
** Changed in: virtualbox (Ubuntu) Status: Expired => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1840377 Title: Virtual Box crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1840377/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848841] Re: Chromium snap looks tiny in hidpi after gnome shell restart
Thanks for the report Carlos. From your description, it sounds like this is a regression, i.e. restarting gnome-shell with a running instance of chromium packaged as a deb would not rescale to 1x. Is that correct? ** Changed in: chromium-browser (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/1848841 Title: Chromium snap looks tiny in hidpi after gnome shell restart To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1848841/+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
** Tags added: python3.8 -- 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 1848402] Re: No indication that thunderbird is starting
Certainly; please see: https://drive.google.com/file/d/1HnddxhNOpZHsQ2Dxb9dAyvL7Vv0ZQpJG/view?usp=sharing I pressed Super+T just as I said "now". Notice that the mouse pointer near the middle of the screen does not change. -- 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 1849012] Re: bionic/linux-oem: 4.15.0-1060.69 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Tags added: block-proposed-bionic ** 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: 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 + phase: Ready for Promote to Proposed + phase-changed: Wednesday, 23. October 2019 13:33 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa lrm:depwait,meta:depwait,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/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 1849493] [NEW] CONFIG_ANDROID_BINDER_IPC=m is missing in the GCP rolling kernel for bionic
Public bug reported: The rolling GCP kernel for bionic is missing CONFIG_ANDROID_BINDER_IPC=m which is enabled in the standard Ubuntu kernel since 19.04 and available through the HWE kernels in Bionic. As we require CONFIG_ANDROID_BINDER_IPC=m for a not released product in our kernels it would be great if we can import the relevant config changes to the GCP kernel (haven't yet checked our other cloud kernels). All relevant changes from Christian Brauner to enable binder in the Ubuntu kernel are present in the GCP kernel (see https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux- gcp/+git/bionic/log/?h=gcp-edge=grep=brauner). See https://kernel.ubuntu.com/git/ubuntu/ubuntu- bionic.git/commit/debian.master/config/config.common.ubuntu?h=hwe=a758aeb0bb0f52ccbee99f850709c57711753b33 and https://kernel.ubuntu.com/git/ubuntu/ubuntu- bionic.git/commit/debian.master/config/config.common.ubuntu?h=hwe=4b44b695fb5ee2f405d0ad4eda2fc2cad856414c for the relevant config changes in the Ubuntu kernel from Seth. ** Affects: linux (Ubuntu) Importance: High Assignee: Khaled El Mously (kmously) Status: Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849493 Title: CONFIG_ANDROID_BINDER_IPC=m is missing in the GCP rolling kernel for bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849493/+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/promote-to-proposed Status: New => Confirmed ** Tags added: block-proposed-bionic ** 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: 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 + phase: Ready for Promote to Proposed + phase-changed: Wednesday, 23. October 2019 13:32 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa lrm:depwait,meta:depwait,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/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 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: Promote to Proposed phase-changed: Wednesday, 23. October 2019 12:45 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 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 1849493] Re: CONFIG_ANDROID_BINDER_IPC=m is missing in the GCP rolling kernel for bionic
** Changed in: linux (Ubuntu) Importance: Undecided => High ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Khaled El Mously (kmously) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849493 Title: CONFIG_ANDROID_BINDER_IPC=m is missing in the GCP rolling kernel for bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849493/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849477] Re: numpy fails on s390x
** Tags added: python3.8 -- 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 1849399] Re: ibus in 19.10 breaks the delete key, maps to ☭
On 2019-10-23 08:09, Steve Langasek wrote: >> * Which values do the environment variables have? > > $ env | grep -E 'XMOD|_IM' > GTK_IM_MODULE=ibus > QT4_IM_MODULE=ibus > XMODIFIERS=@im=ibus > CLUTTER_IM_MODULE=ibus > QT_IM_MODULE=ibus > $ Looks good. > I don't know where these are being set, because Xsession is hell. They are set by im-config on X-sessions on Debian/Ubuntu. (Without im- config, the most important ones would have been set by GNOME instead.) >> * Can you reproduce it on a fresh 19.10 (or with a newly created >> user)? > > No. Then we know that the issue is caused by something in your $HOME. The question is what and how it ended up there... There is a ~/.cache/ibus/compose folder with a suspicious cache file. Can you please rename that folder, relogin, and check if the issue is still present. >> Assuming that you are on standard Ubuntu, using ibus-setup for >> adding/removing input sources is not the 'right' way > > That's not really a satisfactory position, given that the ibus-setup > command is shipped in the ibus package, which is seeded as part of > the Ubuntu Desktop. If the command should not be used, it should not > be present. Fair point. But on non-GNOME desktops ibus-setup is needed, and made available to the users via an IBus icon. I wouldn't dare to say that you *never* need to use ibus-setup on a GNOME desktop, but GNOME provides an integration where XKB layouts and IBus IMs are presented together in Settings, so normally the users don't need to bother with ibus-setup. >> it's supposed to be done in Settings -> Region & Language (probably >> not significant for this issue, but still...). > > I can't find anything under the settings screens that resembles the > selection of input methods presented by ibus-setup. The "Input Sources" section in Region & Language is what I'm talking about. That interface controls the available input sources and saves the settings as gsettings get org.gnome.desktop.input-sources sources The input sources set via ibus-setup are saved as gsettings get org.freedesktop.ibus.general preload-engines but on GNOME the latter dconf setting is ignored AFAIK. > ibus-setup presents 'Chinese SunPinyin', Settings only presents > 'Chinese'; and removing the Chinese input method from ibus-setup's > config doesn't change what's displayed in Settings (Chinese is still > listed here). For an IBus IM to be presented in Settings or ibus-setup, the package - in your case ibus-sunpinyin - needs to be installed. But when you say that only Chinese is listed in Settings, and assuming that ibus- sunpinyin is still installed on your machine, can it possibly be that if you click the "Chinese" option in Settings, you end up in a sub menu which includes Chinese SunPinyin? ** Changed in: ibus (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/1849399 Title: ibus in 19.10 breaks the delete key, maps to ☭ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1849399/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 172977] Re: File Transfers Cannot be Paused
** Tags added: eoan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/172977 Title: File Transfers Cannot be Paused To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/172977/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 816669] Re: encrypted-home support in new user dialog
** Tags added: eoan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/816669 Title: encrypted-home support in new user dialog To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/816669/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 124440] Re: [enhancement] Ubuntu needs a way to set mouse wheel scrolling speed
** Tags added: eoan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/124440 Title: [enhancement] Ubuntu needs a way to set mouse wheel scrolling speed To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/124440/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849489] Re: Failed to power off from login screen
*** This bug is a duplicate of bug 1847896 *** https://bugs.launchpad.net/bugs/1847896 ** This bug has been marked a duplicate of bug 1847896 Unable to shutdown or restart from log-in screen -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849489 Title: Failed to power off from login screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-session/+bug/1849489/+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: 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: 1849051 packages: main: linux-fips meta: linux-meta-fips signed: linux-signed-fips - phase: Promote to Proposed - phase-changed: Wednesday, 23. October 2019 12:51 UTC + phase: Testing + phase-changed: Wednesday, 23. October 2019 13:13 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/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 1847153] Re: package virtualbox-dkms (not installed) failed to install/upgrade: installed virtualbox-dkms package post-installation script subprocess returned error exit status 10
please purge the old eoan kernel ** Changed in: virtualbox (Ubuntu) Status: Confirmed => Incomplete ** Changed in: virtualbox (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847153 Title: package virtualbox-dkms (not installed) failed to install/upgrade: installed virtualbox-dkms package post-installation script subprocess returned error exit status 10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1847153/+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: 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/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 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: Promote to Proposed phase-changed: Wednesday, 23. October 2019 12:45 UTC reason: - promote-to-proposed: Ongoing -- review in progress + promote-to-proposed: Pending -- package copies requested to Proposed main:missing,meta:missing 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 412738] Re: Can't record a second sound clip
This is finally fixed in 19.10. ** Changed in: gnome-media (Ubuntu) Status: New => Fix Released ** Changed in: gnome-sound-recorder (Ubuntu) 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/412738 Title: Can't record a second sound clip To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-media/+bug/412738/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1051288] Re: LightDM assumes there's only ONE system default layout
** Tags added: eoan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1051288 Title: LightDM assumes there's only ONE system default layout To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1051288/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849488] [NEW] kernel panics due to incorrect backport
Public bug reported: This issue results in kernel panics for anyone who uses CephFS. After some digging we suspect this patch to be cause of the kernel panics: https://kernel.ubuntu.com/git/kernel-ppa/mirror/ubuntu- bionic.git/commit/?id=eb0ba4bdcf12d9c29b9d3318627ad9ff3aff5471 This patch same patch was applied upstream (4.19) and reverted: https://lkml.org/lkml/2019/10/3/862 Quoting: "The backport was incorrect and was causing kernel panics. Revert and re-apply a correct backport from Jeff Layton." Also relevant: https://www.mail-archive.com/ceph-users@lists.ceph.com/msg56549.html Which basically states this patch should not have been applied to 4.15 at all (not intended for pre-5.2) Would be great if you guys could revert the patch. We are stuck on previous kernel versions until this issue is fixed. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849488 Title: kernel panics due to incorrect backport To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849488/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849488] Re: kernel panics due to incorrect backport
Issue is introduced in bionic kernel 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/1849488 Title: kernel panics due to incorrect backport To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849488/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849444] Re: drm core dump on comet lake H [8086:3e9b]
*** This bug is a duplicate of bug 1849278 *** https://bugs.launchpad.net/bugs/1849278 re-setting the duplicate status, this should be a dupe of 1849278 1826691 is about amd/synaptics, while this seems to be about intel/CML PCH ** This bug is no longer a duplicate of bug 1826691 fwupd hangs after 19.04 upgrade from 18.10 ** This bug has been marked a duplicate of bug 1849278 [CML-S] Add-new-CNL-PCH-ID-seen-on-a-CML-platform -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849444 Title: drm core dump on comet lake H [8086:3e9b] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-osp1/+bug/1849444/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849488] Re: kernel panics due to incorrect backport
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849488 Title: kernel panics due to incorrect backport To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849488/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849485] [NEW] Failure to upgrade from 18.04.3 to 19.04
Public bug reported: Ubuntu Studio 18.04.3 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.34 ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-lowlatency 5.0.15 Uname: Linux 5.0.0-23-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CrashDB: ubuntu Date: Wed Oct 23 09:43:27 2019 InstallationDate: Installed on 2018-08-22 (427 days ago) InstallationMedia: Ubuntu-Studio 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to bionic on 2019-10-23 (0 days ago) VarLogDistupgradeAptlog: Log time: 2019-10-23 09:40:37.517938 Log time: 2019-10-23 09:40:54.465033 Log time: 2019-10-23 09:43:14.032941 Log time: 2019-10-23 09:43:35.186346 VarLogDistupgradeTermlog: mtime.conffile..etc.update-manager.release-upgrades: 2019-10-21T13:54:29.624816 ** 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/1849485 Title: Failure to upgrade from 18.04.3 to 19.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1849485/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1783961] Re: CONFIG_KVM is disabled for linux-raspi2 (aarch64)
@hui.wang and the Ubuntu kernel team - kindly consider enabling KVM for arm64 Linux kernel in the raspberrypi preinstalled image in future. Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1783961 Title: CONFIG_KVM is disabled for linux-raspi2 (aarch64) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1783961/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849491] [NEW] Add support for EXTRA_SNAPS in bionic
Public bug reported: [Impact] Currently we are building core18 images using devel (eoan previously, now focal), but we need to switch to actually using bionic instead (as focal will be core20). For this to happen, we need bionic to have the same EXTRA_SNAPS support as we have in eoan as the new custom-image building solution relies on this feature. We actually might need to do the same for xenial to enable the same feature for core16. [Test Case] Run a livefs build of core18 using the bionic-proposed (or xenial- proposed) series and add an EXTRA_SNAPS list of snaps in the metadata override (e.g. "hello-world"). Check the logs to see if the extra snaps have been pulled into the image. [Regression Potential] Basically none. The only regression potential I can think of is by this change being wrongly backported and somehow causing ubuntu-core builds to fail or incorrectly pass additional arguments - but we don't actually rely on that. ** Affects: livecd-rootfs (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: livecd-rootfs (Ubuntu Xenial) Importance: Undecided Assignee: Łukasz Zemczak (sil2100) Status: New ** Affects: livecd-rootfs (Ubuntu Bionic) Importance: Undecided Assignee: Łukasz Zemczak (sil2100) Status: New ** Description changed: [Impact] Currently we are building core18 images using devel (eoan previously, now focal), but we need to switch to actually using bionic instead (as focal will be core20). For this to happen, we need bionic to have the same EXTRA_SNAPS support as we have in eoan as the new custom-image building solution relies on this feature. + We actually might need to do the same for xenial to enable the same + feature for core16. + [Test Case] - Run a livefs build of core18 using the bionic-proposed series and add an - EXTRA_SNAPS list of snaps in the metadata override (e.g. "hello-world"). - Check the logs to see if the extra snaps have been pulled into the - image. + Run a livefs build of core18 using the bionic-proposed (or xenial- + proposed) series and add an EXTRA_SNAPS list of snaps in the metadata + override (e.g. "hello-world"). Check the logs to see if the extra snaps + have been pulled into the image. [Regression Potential] Basically none. The only regression potential I can think of is by this change being wrongly backported and somehow causing ubuntu-core builds to fail or incorrectly pass additional arguments - but we don't actually rely on that. ** Also affects: livecd-rootfs (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: livecd-rootfs (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: livecd-rootfs (Ubuntu) Status: New => Fix Released ** Changed in: livecd-rootfs (Ubuntu Xenial) Assignee: (unassigned) => Łukasz Zemczak (sil2100) ** Changed in: livecd-rootfs (Ubuntu Bionic) Assignee: (unassigned) => Ł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/1849491 Title: Add support for EXTRA_SNAPS in bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1849491/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849489] [NEW] Failed to power off from login screen
Public bug reported: After I log out from my user, at login screen, I click "Power off" button in indicator-session. A dialog appears with 3 buttons. Even I click to "Restart" or "Power off", nothing happens. My PC still be on. The login is still there. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: indicator-session (not installed) 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 CurrentDesktop: ubuntu:GNOME Date: Wed Oct 23 19:56:42 2019 InstallationDate: Installed on 2019-10-18 (5 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: indicator-session UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: indicator-session (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849489 Title: Failed to power off from login screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-session/+bug/1849489/+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
** 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: Ready for Promote to Proposed - phase-changed: Wednesday, 23. October 2019 11:26 UTC + phase: Promote to Proposed + phase-changed: Wednesday, 23. October 2019 12:51 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/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 1848790] Re: USB not working under arm64 on Pi4
** Tags added: id-5db015562d35287792a0a3bc -- 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 1841955] Re: Can't upgrade kernel on raspberry pi3a+
** Tags added: id-5da7195077417327157503f8 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1841955 Title: Can't upgrade kernel on raspberry pi3a+ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1841955/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1783961] Re: CONFIG_KVM is disabled for linux-raspi2 (aarch64)
@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 Further description of how KVM was tested is here along with Apache CloudStack (an IaaS platform): https://github.com/rhtyd/rhtyd.github.io/blob/master/_drafts/2019-10-22-cloudstack-rpi4-kvm.markdown Tested using guest templates Debian 9 and Debian 10, both arm64 - http://dl.rohityadav.cloud/cloudstack-rpi/template/ Tested/issues: - Only scsi seems to be the working disk controller (ide is not supported, virtio may/may not work) - when testing with linux guests. Workaround: use scsi by default. - Plugging in usb devices without an explicit controller added first, fails (on x86_64 systems, controller seems to be already added when usb devices like keyboard/mouse etc are added). Workaround: add a usb controller and then add the usb devices - keyboard, mouse, tablet. I've attached some screenshots of a guest VM running on the RPi4 device using CloudStack. ** Attachment added: "Screenshot from 2019-10-23 18-22-59.png" https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1783961/+attachment/5299489/+files/Screenshot%20from%202019-10-23%2018-22-59.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1783961 Title: CONFIG_KVM is disabled for linux-raspi2 (aarch64) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1783961/+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)
I think I found the issue, retesting ... Yes that was it, my mistake but fixed. Now the Eoan/Focal branches behave as expected as well. -- 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
