[Bug 1845719] Re: eoan/linux-raspi2: 5.3.0-1006.7 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => Fix Committed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1846204 packages: main: linux-raspi2 meta: linux-meta-raspi2 - phase: Ready for Promote to Proposed - phase-changed: Thursday, 03. October 2019 15:07 UTC + phase: Promote to Proposed + phase-changed: Saturday, 05. October 2019 06:45 UTC reason: - promote-to-proposed: Stalled -- ready for review + 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/1845719 Title: eoan/linux-raspi2: 5.3.0-1006.7 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1845719/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846271] Re: Full video freeze kernel 4.15.0-65
Set "Storage=persistent" in journald.conf [1]. [1] https://www.freedesktop.org/software/systemd/man/journald.conf.html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846271 Title: Full video freeze kernel 4.15.0-65 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1846271/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823076] Re: System wakes up immediately after suspend if Bluetooth is still enabled
"Same result" here means it doesn't wake up anymore? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1823076 Title: System wakes up immediately after suspend if Bluetooth is still enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1823076/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846248] Re: precise/linux-lts-trusty: 3.13.0-174.225~12.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: 1846250 packages: main: linux-lts-trusty meta: linux-meta-lts-trusty signed: linux-signed-lts-trusty phase: Ready for Promote to Proposed phase-changed: Friday, 04. October 2019 17:41 UTC reason: - promote-to-proposed: Pending -- ready for review + promote-to-proposed: Stalled -- 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/1846248 Title: precise/linux-lts-trusty: 3.13.0-174.225~12.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1846248/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846858] [NEW] Media keys stopped working
Public bug reported: Media keys (volume keys or CTRL+Alt+T) stopped working on october 4th. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 5 07:49:58 2019 DisplayManager: gdm3 InstallationDate: Installed on 2014-07-15 (1907 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520) RelatedPackageVersions: mutter-common 3.34.0-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2018-03-24 (559 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan rls-ee-incoming ** Tags added: rls-ee-incoming -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846858 Title: Media keys stopped working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1846858/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846857] Status changed to Confirmed
This change was made by a bot. ** 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/1846857 Title: After upgrading to kernel 5.0.0-31-generic:amd64, click with one finger and drag with the other doesn't work on the touchpad. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1846857/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846122] Re: trusty/linux-azure: 4.15.0-1061.66~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: 1846123 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Ready for Promote to Proposed phase-changed: Friday, 04. October 2019 17:21 UTC reason: - promote-to-proposed: Pending -- ready for review + promote-to-proposed: Stalled -- 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/1846122 Title: trusty/linux-azure: 4.15.0-1061.66~14.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1846122/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846857] [NEW] After upgrading to kernel 5.0.0-31-generic:amd64, click with one finger and drag with the other doesn't work on the touchpad.
Public bug reported: I just upgraded to linux kernel 5.0.0-31. When I use the trackpad on my Lenovo Yoga 260 to click with one finger, and drag with another, it doesn't move the thing I'm trying to drag. If I use one finger, it works fine, but its hard to drag it far with only one finger, because I can't pick the finger up and move it back to drag some more. I went and booted from 5.0.0-29, and everything is fine again. I'm back to 5.0.0-31 and the problem is back. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-modules-5.0.0-31-generic:amd64 5.0.0-31.33 ProcVersionSignature: Ubuntu 5.0.0-31.33-generic 5.0.21 Uname: Linux 5.0.0-31-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: frohro 2367 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Oct 4 22:14:28 2019 Dependencies: InstallationDate: Installed on 2019-04-19 (169 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2) MachineType: LENOVO 20FES0EX00 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-31-generic root=/dev/mapper/ubuntu--vg-root ro RelatedPackageVersions: linux-restricted-modules-5.0.0-31-generic N/A linux-backports-modules-5.0.0-31-generic N/A linux-firmware1.178.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N1GET91W (1.70 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FES0EX00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1GET91W(1.70):bd06/26/2018:svnLENOVO:pn20FES0EX00:pvrThinkPadYoga260:rvnLENOVO:rn20FES0EX00:rvrSDK0J40700WIN:cvnLENOVO:ct31:cvrNone: dmi.product.family: ThinkPad Yoga 260 dmi.product.name: 20FES0EX00 dmi.product.sku: LENOVO_MT_20FE_BU_Think_FM_ThinkPad Yoga 260 dmi.product.version: ThinkPad Yoga 260 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug disco ** Summary changed: - After upgrading to kerner 5.0.0-31-generic:amd64 click with one finger and drag with the other doesn't work on touchpad. + After upgrading to kernel 5.0.0-31-generic:amd64 click with one finger and drag with the other doesn't work on touchpad. ** Summary changed: - After upgrading to kernel 5.0.0-31-generic:amd64 click with one finger and drag with the other doesn't work on touchpad. + After upgrading to kernel 5.0.0-31-generic:amd64, click with one finger and drag with the other doesn't work on the touchpad. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846857 Title: After upgrading to kernel 5.0.0-31-generic:amd64, click with one finger and drag with the other doesn't work on the touchpad. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1846857/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846842] Re: the upgrade tool from 19.04 to 19.10 failed badly
Thank you again for taking the time to report this bug, plus the time taken to provide extra details in your efforts to help make Ubuntu better. Can I please ask you to provide another detail; specs about your machine using apport-collect. Please execute the following command (on the box the upgrade was performed on) only once, and it will automatically gather debugging information, in a terminal: apport-collect 1846842 When reporting bugs, please try and use apport by using 'ubuntu-bug' and the name of the package affected. This step provides the details that process would have provided. Thanks again for your time in helping make Ubuntu better. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846842 Title: the upgrade tool from 19.04 to 19.10 failed badly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1846842/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1839051] Re: can't install "grub-install/dev/sda"
[Expired for grub-installer (Ubuntu) because there has been no activity for 60 days.] ** Changed in: grub-installer (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1839051 Title: can't install "grub-install/dev/sda" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1839051/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838067] Re: made Ubuntu very slow then crash
[Expired for clamtk (Ubuntu) because there has been no activity for 60 days.] ** Changed in: clamtk (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1838067 Title: made Ubuntu very slow then crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clamtk/+bug/1838067/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838975] Re: Login is slow.
[Expired for update-notifier (Ubuntu) because there has been no activity for 60 days.] ** Changed in: update-notifier (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838975 Title: Login is slow. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/1838975/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838851] Re: Display problems after updating to kernel 5.0.0-23
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838851 Title: Display problems after updating to kernel 5.0.0-23 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838851/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846079] Re: disco/linux-azure: 5.0.0-1023.24 -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: 1846097 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Friday, 04. October 2019 15:58 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff - stakeholder-signoff: Pending -- waiting for signoff + stakeholder-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-azure: bug 1846078 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/1846079 Title: disco/linux-azure: 5.0.0-1023.24 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1846079/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1836752] Re: input/mouse: alps trackpoint-only device doesn't work
** Tags removed: verification-needed-disco ** Tags added: verification-done-disco -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1836752 Title: input/mouse: alps trackpoint-only device doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1836752/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846842] Re: the upgrade tool from 19.04 to 19.10 failed badly
I ran ubuntu-bug update-manager I thought it should have added some data to this ?? has something gone wrong -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846842 Title: the upgrade tool from 19.04 to 19.10 failed badly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1846842/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846842] Re: the upgrade tool from 19.04 to 19.10 failed badly
P.S. sorry if I sounded snappy, looking over what I wrote first some of the words are missing, I guess I was tired when I wrote that. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846842 Title: the upgrade tool from 19.04 to 19.10 failed badly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1846842/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846842] Re: the upgrade tool from 19.04 to 19.10 failed badly
I have determined the the package was the ubuntu-release-upgrader also if you read what I wrote properly you would see that there were no messages: the entirety of gnome-shell was stuffed by the faulty upgrade, all I had was a blank screen. Fortunately I was able to login by ssh from my good machine and fix things on the command line. ok to format the data the way you want it. 1. The specific steps or actions you took that caused you to encounter the problem. I ran update-manager -d on a ubuntu 19.04 box and followed the steps, there were some problems, in short the buttons of the upgrader did not respond to the mouse, I used tab and enter to solve this. 2. The behavior you expected. I expected the upgrader to cleanly upgrade my system. 3. The behavior you actually encountered (in as much detail as possible). The screen locked some way into the upgrade, I found it like this during the night, I attempted to unlock it and after some time I was confronted with a blank screen. So I loggedin from my good machine by ssh, I found that the release upgrader was still running but doing nothing as far as I could tell, I gave it an hour, still nothing so I killed it using "sudo kill -1 pid1 pid2"; where pid1 was the pid of the of the python program doing the upgrade and pid2 was a shell wrapper for it I think, I obtained these pid's from "pgrep --full --list-full upgrade". Then I rebooted the box with sudo shutdown -r +1 , when it came up again I still had a broken box so I sshed in again, ran "sudo apt upgrade" this failed but told me to run "dpkg --configure -a" as there was stuffed messed up with the package system, (I forget it's exact words) so I ran "sudo dpkg --configure -a" it installed many many packages between 4000 and 5000 I think it exited cleanly but things still were not right, I could login graphically again but gnome shell was still at version 3.32.2 not 3.34 and some of the plugins were not working, so I ran "update-manager -d &" again and it gave me a partial upgrader, but that did not work. So I ran "sudo apt-get dist-upgrade" that cleaned up some stuff and deleted one package at least. then I ran update-manager and it pulled down many more packages and fixed the system. After all that I seam to be on a clean copy of 19.10: $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu Eoan Ermine (development branch) Release:19.10 Codename: eoan obviously this needs looking into before 19.10 proper comes out -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846842 Title: the upgrade tool from 19.04 to 19.10 failed badly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1846842/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846249] Re: Num lock works in reverse on Ubuntu 19.10 wayland
When I am logged into Wayland (and therefore experiencing the issue, the output of gsettings list-recursively | grep -e numlock is this when the numlock led is off but the numbers work anyway: org.gnome.desktop.peripherals.keyboard remember-numlock-state true org.gnome.desktop.peripherals.keyboard numlock-state false When the numlock led is on, but the numbers don't work: org.gnome.desktop.peripherals.keyboard remember-numlock-state true org.gnome.desktop.peripherals.keyboard numlock-state true -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846249 Title: Num lock works in reverse on Ubuntu 19.10 wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/x11-utils/+bug/1846249/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845709] Re: Selecting "Copy To..." on an object in "Starred" returns error "The specified location is not supported"
** Changed in: nautilus Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1845709 Title: Selecting "Copy To..." on an object in "Starred" returns error "The specified location is not supported" To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1845709/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846249] Re: Num lock works in reverse on Ubuntu 19.10 wayland
Essentially, it seems like when logging in under Wayland, the system remembers the status of the numlock LED, BUT it always starts the system with the numlock functionality disabled. This is why the LED is out of sync if it's on when logging on, but not if it's off when logging in. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846249 Title: Num lock works in reverse on Ubuntu 19.10 wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/x11-utils/+bug/1846249/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846249] Re: Num lock works in reverse on Ubuntu 19.10 wayland
When I am logged into an X session (and therefore not experiencing the issue), the output of gsettings list-recursively | grep -e numlock is this when the numlock led is off and the numbers don't work: org.gnome.desktop.peripherals.keyboard remember-numlock-state true org.gnome.desktop.peripherals.keyboard numlock-state false When numlock is on and the numbers work: org.gnome.desktop.peripherals.keyboard remember-numlock-state true org.gnome.desktop.peripherals.keyboard numlock-state true -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846249 Title: Num lock works in reverse on Ubuntu 19.10 wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/x11-utils/+bug/1846249/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1836752] Re: input/mouse: alps trackpoint-only device doesn't work
** Changed in: hwe-next 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/1836752 Title: input/mouse: alps trackpoint-only device doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1836752/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846842] Re: the upgrade tool from 19.04 to 19.10 failed badly
** Package changed: ubuntu => ubuntu-release-upgrader (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846842 Title: the upgrade tool from 19.04 to 19.10 failed badly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1846842/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846853] [NEW] Mouse scroll should control VOLUME NOT TIME
Public bug reported: I want the mouse scroll to scroll the volume up and down, not the time forward and back. This is a non-standard behavior that I consider to be a BUG within Totem, and I preferentially use VNC because of this BUG. Fix it so mouse scroll controls volume instead of time please. ** Affects: totem (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/1846853 Title: Mouse scroll should control VOLUME NOT TIME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1846853/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845709] Re: Selecting "Copy To..." on an object in "Starred" returns error "The specified location is not supported"
I just reported it upstream at https://gitlab.gnome.org/GNOME/nautilus/issues/1243 ** Bug watch added: gitlab.gnome.org/GNOME/nautilus/issues #1243 https://gitlab.gnome.org/GNOME/nautilus/issues/1243 ** Also affects: nautilus via https://gitlab.gnome.org/GNOME/nautilus/issues/1243 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1845709 Title: Selecting "Copy To..." on an object in "Starred" returns error "The specified location is not supported" To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1845709/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846842] Re: the upgrade tool from 19.04 to 19.10 failed badly
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. It actually reads like you wanted the chance to complain, where bug reports are not the appropriate place in my opinion. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). I've marked this bug as incomplete, as it contains no actual messages, or details of problems (packages), or specifics. If you believe I'm in error, please feel free to leave a comment as to why, or even better provide the specific details as to problems (apport or details from logs) and you can change status back to "New". ** Changed in: 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/1846842 Title: the upgrade tool from 19.04 to 19.10 failed badly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1846842/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838555] Re: nvme-cli 1.5 in Bionic does not support Micron NVME drives
@slashd , Reading through the patch, it's exactly as @mruffell says it is. It's sequestered into a code path that only exists for micron drives. A code path which previously did not exist. This satisfies the intro, and the first three bullet points of Other_safe_cases. This patch is upstream and AFAICT from git log and comparing of the enablement patch and the file on master of the public project micron-nvme.c has not changed in any consequential way. IMHO. there should be no issue with pushing this in as an SRU into bionic, and does significantly improve the user experience for those with Micron drives. This simultaneously has little to no impact on other users. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838555 Title: nvme-cli 1.5 in Bionic does not support Micron NVME drives To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvme-cli/+bug/1838555/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846535] Re: cloud-init 19.2.36 fails with python exception "Not all expected physical devices present ..." during bionic image deployment from MAAS
I manually tested the new cloud-init using the MAAS CI as we don't have automated tests for bonds or bridges. Xenial, Bionic, and Disco can all commissioning and deploy fine using static IPs, bonds, and bridges. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846535 Title: cloud-init 19.2.36 fails with python exception "Not all expected physical devices present ..." during bionic image deployment from MAAS To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1846535/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1834771] Re: No HDMI-audio after kernel 4.15.-0.50
Could you please have try with the latest mainline kernel: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.3/ If that kernel doesn't work, let us have a try with replacing the current graphic driver amdgpu to the amdgpu-pro. I will update a new comment to explain how to install amdgpu-pro if the kernel v5.3 is confirmed to not work. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1834771 Title: No HDMI-audio after kernel 4.15.-0.50 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1834771/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846641] Re: eoan/linux: 5.3.0-17.18 -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/automated-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 packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed - phase: Promote to Proposed - phase-changed: Friday, 04. October 2019 23:46 UTC + phase: Testing + phase-changed: Saturday, 05. October 2019 01:36 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 trackers: bionic/linux-hwe-edge: bug 1846636 eoan/linux-aws: bug 1846613 eoan/linux-azure: bug 1846616 eoan/linux-gcp: bug 1846623 eoan/linux-kvm: bug 1846628 eoan/linux-oracle: bug 1846630 eoan/linux-raspi2: bug 1846611 eoan/linux-snapdragon: bug 1846634 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/1846641 Title: eoan/linux: 5.3.0-17.18 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1846641/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1692303] Re: Mouse over hints / tooltips show no text
** Changed in: inkscape (Debian) Status: Confirmed => 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/1692303 Title: Mouse over hints / tooltips show no text To manage notifications about this bug go to: https://bugs.launchpad.net/inkscape/+bug/1692303/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1843507] Re: apt-get update to latest libidn2.so.0 causes multiple application failures including apt-update
At what point should I remove the hold on libidn2-0? !!!Please reply!!! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1843507 Title: apt-get update to latest libidn2.so.0 causes multiple application failures including apt-update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libidn2/+bug/1843507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846848] [NEW] Upgrade Mono package from 5.18.0 to 6.4.0
Public bug reported: Ubuntu 19.04 The latest version of Mono in Ubuntu is currently 5.18.0 Please upgrade it to the stable 6.4.0 release Current download link (Ubuntu 18.04 - Should support Ubuntu 19.04) - https://www.mono-project.com/download/stable/#download-lin Thanks :) ** Affects: mono (Ubuntu) Importance: Undecided Status: New ** Tags: upgrade-software-version -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846848 Title: Upgrade Mono package from 5.18.0 to 6.4.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mono/+bug/1846848/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846849] [NEW] Ubuntu MATE Guide doesn't document Magnus
Public bug reported: The Ubuntu MATE Guide referrers for Compiz and its screen magnifier feature, which are no longer included in Ubuntu MATE 19.10. Magnus, the new screen magnifier, should be documented instead. ** Affects: ubuntu-mate-guide (Ubuntu) Importance: Medium Assignee: Martin Wimpress (flexiondotorg) Status: Fix Committed ** Changed in: ubuntu-mate-guide (Ubuntu) Status: New => In Progress ** Changed in: ubuntu-mate-guide (Ubuntu) Importance: Undecided => Medium ** Changed in: ubuntu-mate-guide (Ubuntu) Assignee: (unassigned) => Martin Wimpress (flexiondotorg) ** Changed in: ubuntu-mate-guide (Ubuntu) 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/1846849 Title: Ubuntu MATE Guide doesn't document Magnus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-mate-guide/+bug/1846849/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827253] Re: [apparmor] missing 'mr' on binary for usage on containers
I'm hitting the same problem when using a Bionic host with a Bionic container when using the 5.0 HWE kernel. @paelzer, I'd appreciate if this could be SRU'ed to Bionic, please :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1827253 Title: [apparmor] missing 'mr' on binary for usage on containers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1827253/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846847] [NEW] I was installing Ubuntu 19.04 after formatting the disk(which took 6 hours)
Public bug reported: Disk was formatted by using the "Try Ubuntu option". It was a 1TB disk which was formatted over a period of 6 hours. Once that was done, I was in the process of installing 19.04 when it crashed. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: ubiquity 19.04.9 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CasperVersion: 1.405 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 4 17:26:25 2019 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd quiet splash --- maybe-ubiquity LiveMediaBuild: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: LANGUAGE=en_US.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco ubiquity-19.04.9 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846847 Title: I was installing Ubuntu 19.04 after formatting the disk(which took 6 hours) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1846847/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846014] Re: bionic/linux-gke-5.0: 5.0.0-1020.20~18.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-security Status: New => Confirmed ** 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: 1846015 packages: main: linux-gke-5.0 meta: linux-meta-gke-5.0 signed: linux-signed-gke-5.0 - phase: Holding before Promote to Security - phase-changed: Friday, 04. October 2019 10:21 UTC + phase: Ready for Promote to Security + phase-changed: Saturday, 05. October 2019 00:22 UTC proposed-announcement-sent: true proposed-testing-requested: true + reason: + promote-to-security: Pending -- ready to copy replaces: bug 1845131 trackers: bionic/linux-gke-5.0/gke-kernel: bug 1846013 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/1846014 Title: bionic/linux-gke-5.0: 5.0.0-1020.20~18.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1846014/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846002] Re: bionic/linux-aws-edge: 5.0.0-1018.20~18.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-security Status: New => Confirmed ** 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: 1846003 packages: main: linux-aws-edge meta: linux-meta-aws-edge - phase: Holding before Promote to Security - phase-changed: Friday, 04. October 2019 10:20 UTC + phase: Ready for Promote to Security + phase-changed: Saturday, 05. October 2019 00:21 UTC proposed-announcement-sent: true proposed-testing-requested: true + reason: + promote-to-security: Pending -- ready to copy 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/1846002 Title: bionic/linux-aws-edge: 5.0.0-1018.20~18.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1846002/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846842] Re: the upgrade tool from 19.04 to 19.10 failed badly
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode. To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1846842/+editstatus and add the package name in the text box next to the word Package. [This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.] ** Tags added: bot-comment -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846842 Title: the upgrade tool from 19.04 to 19.10 failed badly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1846842/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845828] Re: Timeout error while renaming a file
Launchpad has imported 10 comments from the remote bug at https://bugzilla.xfce.org/show_bug.cgi?id=11283. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2014-11-06T01:19:35+00:00 Jussi wrote: Way to reproduce the problem: 1. Choose file from your desktop. 2. Open menu with right mouse button. 3. Choose rename. 4. Do not change the name or close the dialog, but wait for 15 seconds. 5. The error message appears and trash can will be disabled until you close the dialog. xfdesktop version 4.11.8 and earlier are affected. For more detail see: https://bugs.launchpad.net/ubuntu/+source/xfdesktop4/+bug/1388946 Reply at: https://bugs.launchpad.net/ubuntu/+source/xfdesktop4/+bug/1845828/comments/0 On 2014-11-09T14:03:29+00:00 Eric Koegel wrote: We're hitting DBUS's reply timeout. We'll have to find a way to perform the call without a timeout to fix this. The code in question is in: http://git.xfce.org/xfce/xfdesktop/tree/src/xfdesktop-file-utils.c#n691 which calls xfdesktop_file_manager_proxy_rename_file_async There's a dbus_g_proxy_call_with_timeout http://dbus.freedesktop.org/doc/dbus-glib/dbus-glib-DBusGProxy.html#dbus-g-proxy-call-with-timeout But the timeout is an int representing milliseconds which only gets up to 32 seconds (unless my math is off). Maybe dbus_g_proxy_call_no_reply? ...If that's not possible then we may have to not use dbus/thunar for renames and write the renaming dialog and operation ourselves to fix this issue. Reply at: https://bugs.launchpad.net/ubuntu/+source/xfdesktop4/+bug/1845828/comments/1 On 2014-11-09T16:15:48+00:00 Jussi wrote: Maybe I haven't understand this, if so, sorry about the noise... It seem the event is called in wrong time, is it possible call the event only after user has given new name for the file? Reply at: https://bugs.launchpad.net/ubuntu/+source/xfdesktop4/+bug/1845828/comments/2 On 2014-11-09T16:55:47+00:00 Eric Koegel wrote: Well right now xfdesktop doesn't have code to display the rename dialog. The good news is it's not hard, it's just a matter of adding it in. Reply at: https://bugs.launchpad.net/ubuntu/+source/xfdesktop4/+bug/1845828/comments/3 On 2015-02-20T23:42:00+00:00 Thaddaeus Tintenfisch wrote: The same applies to the "Create New Folder" and "Create New File" dialog windows. Reply at: https://bugs.launchpad.net/ubuntu/+source/xfdesktop4/+bug/1845828/comments/4 On 2015-03-28T10:31:40+00:00 Thaddaeus Tintenfisch wrote: As of now, we simply ignore this type of error while not breaking any functionality. http://git.xfce.org/xfce/xfdesktop/commit/?id=b0388120725ff485e5ae40fde4017aa8c7efb9cf Reply at: https://bugs.launchpad.net/ubuntu/+source/xfdesktop4/+bug/1845828/comments/5 On 2015-03-31T01:23:37+00:00 Hudd wrote: *** Bug 11780 has been marked as a duplicate of this bug. *** Reply at: https://bugs.launchpad.net/ubuntu/+source/xfdesktop4/+bug/1845828/comments/6 On 2019-10-03T09:35:34+00:00 spike speigel wrote: It appears this is happening again. Can this issue be reopened, or should a new one be created? Xubuntu 19.10 xfdesktop4 4.14.1-1 Reply at: https://bugs.launchpad.net/ubuntu/+source/xfdesktop4/+bug/1845828/comments/14 On 2019-10-04T20:12:18+00:00 Alexxcons-x wrote: Reopened ... I as well can reproduce the bug. Thanks for finding that old bug ! Reply at: https://bugs.launchpad.net/ubuntu/+source/xfdesktop4/+bug/1845828/comments/15 On 2019-10-04T22:15:45+00:00 spike speigel wrote: You're welcome, thank you for verifying :) Reply at: https://bugs.launchpad.net/ubuntu/+source/xfdesktop4/+bug/1845828/comments/16 ** Changed in: xfdesktop Status: Unknown => Confirmed ** Changed in: xfdesktop Importance: Unknown => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1845828 Title: Timeout error while renaming a file To manage notifications about this bug go to: https://bugs.launchpad.net/xfdesktop/+bug/1845828/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/ma
[Bug 1846015] Re: disco/linux-gcp: 5.0.0-1020.20 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-security Status: New => Confirmed ** 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: 1846026 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp - phase: Holding before Promote to Security - phase-changed: Friday, 04. October 2019 10:00 UTC + phase: Ready for Promote to Security + phase-changed: Saturday, 05. October 2019 00:07 UTC proposed-announcement-sent: true proposed-testing-requested: true + reason: + promote-to-security: Pending -- ready to copy trackers: bionic/linux-gcp: bug 1846012 bionic/linux-gke-5.0: bug 1846014 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/1846015 Title: disco/linux-gcp: 5.0.0-1020.20 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1846015/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846003] Re: disco/linux-aws: 5.0.0-1018.20 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-security Status: New => Confirmed ** 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: 1846026 packages: main: linux-aws meta: linux-meta-aws - phase: Holding before Promote to Security - phase-changed: Friday, 04. October 2019 09:59 UTC + phase: Ready for Promote to Security + phase-changed: Saturday, 05. October 2019 00:06 UTC proposed-announcement-sent: true proposed-testing-requested: true + reason: + promote-to-security: Pending -- ready to copy trackers: bionic/linux-aws-edge: bug 1846002 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/1846003 Title: disco/linux-aws: 5.0.0-1018.20 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1846003/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1839593] Re: Missing dependens python-scipy
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gr-gsm (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/1839593 Title: Missing dependens python-scipy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gr-gsm/+bug/1839593/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846009] Re: disco/linux-azure: 5.0.0-1022.23 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-security Status: New => Confirmed ** 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: 1846026 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure - phase: Holding before Promote to Security - phase-changed: Friday, 04. October 2019 09:59 UTC + phase: Ready for Promote to Security + phase-changed: Saturday, 05. October 2019 00:06 UTC proposed-announcement-sent: true proposed-testing-requested: true + reason: + promote-to-security: Pending -- ready to copy trackers: bionic/linux-azure: bug 1846007 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/1846009 Title: disco/linux-azure: 5.0.0-1022.23 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1846009/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846001] Re: disco/linux-raspi2: 5.0.0-1019.19 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-security Status: New => Confirmed ** 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: 1846026 packages: main: linux-raspi2 meta: linux-meta-raspi2 - phase: Holding before Promote to Security - phase-changed: Friday, 04. October 2019 09:58 UTC + phase: Ready for Promote to Security + phase-changed: Saturday, 05. October 2019 00:06 UTC proposed-announcement-sent: true proposed-testing-requested: true + reason: + promote-to-security: Pending -- ready to copy 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/1846001 Title: disco/linux-raspi2: 5.0.0-1019.19 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1846001/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846841] Re: zfsutils-linux is a Depends: not a Recommends:
This bug was fixed in the package ubuntu-mate-meta - 1.255 --- ubuntu-mate-meta (1.255) eoan; urgency=medium * Refreshed dependencies * Moved zfsutils-linux to core-recommends, desktop-recommends (LP: #1846841) -- Martin Wimpress Fri, 04 Oct 2019 23:39:29 +0100 ** Changed in: ubuntu-mate-meta (Ubuntu) Status: Fix Committed => 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/1846841 Title: zfsutils-linux is a Depends: not a Recommends: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-mate-meta/+bug/1846841/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846022] Re: bionic/linux-hwe: 5.0.0-31.33~18.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-security Status: New => Confirmed ** 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: 1846026 packages: main: linux-hwe meta: linux-meta-hwe signed: linux-signed-hwe - phase: Holding before Promote to Security - phase-changed: Friday, 04. October 2019 10:26 UTC + phase: Ready for Promote to Security + phase-changed: Saturday, 05. October 2019 00:08 UTC proposed-announcement-sent: true proposed-testing-requested: true + reason: + promote-to-security: Pending -- ready to copy 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/1846022 Title: bionic/linux-hwe: 5.0.0-31.33~18.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1846022/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846017] Re: disco/linux-kvm: 5.0.0-1019.20 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-security Status: New => Confirmed ** 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: 1846026 packages: main: linux-kvm meta: linux-meta-kvm - phase: Holding before Promote to Security - phase-changed: Friday, 04. October 2019 10:00 UTC + phase: Ready for Promote to Security + phase-changed: Saturday, 05. October 2019 00:07 UTC proposed-announcement-sent: true proposed-testing-requested: true + reason: + promote-to-security: Pending -- ready to copy 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/1846017 Title: disco/linux-kvm: 5.0.0-1019.20 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1846017/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846021] Re: disco/linux-snapdragon: 5.0.0-1023.24 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-security Status: New => Confirmed ** 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: 1846026 packages: main: linux-snapdragon meta: linux-meta-snapdragon - phase: Holding before Promote to Security - phase-changed: Friday, 04. October 2019 10:04 UTC + phase: Ready for Promote to Security + phase-changed: Saturday, 05. October 2019 00:08 UTC proposed-announcement-sent: true proposed-testing-requested: true + reason: + promote-to-security: Pending -- ready to copy 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/1846021 Title: disco/linux-snapdragon: 5.0.0-1023.24 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1846021/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845815] Re: xenial/linux-gcp: 4.15.0-1046.49 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-security Status: New => Confirmed ** 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: 1844403 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp - phase: Holding before Promote to Security - phase-changed: Friday, 04. October 2019 10:17 UTC + phase: Ready for Promote to Security + phase-changed: Saturday, 05. October 2019 00:05 UTC proposed-announcement-sent: true proposed-testing-requested: true + reason: + promote-to-security: Pending -- ready to copy trackers: xenial/linux-gcp/gcp-kernel: bug 1845813 xenial/linux-gcp/gke-kernel: bug 1845814 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/1845815 Title: xenial/linux-gcp: 4.15.0-1046.49 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1845815/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846026] Re: disco/linux: 5.0.0-31.33 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-security Status: New => Confirmed ** 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 bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed - phase: Holding before Promote to Security - phase-changed: Friday, 04. October 2019 09:57 UTC + phase: Ready for Promote to Security + phase-changed: Saturday, 05. October 2019 00:01 UTC proposed-announcement-sent: true proposed-testing-requested: true + reason: + promote-to-security: Pending -- ready to copy trackers: bionic/linux-bluefield: bug 1846024 bionic/linux-hwe: bug 1846022 bionic/linux-oem-osp1: bug 1846023 disco/linux-aws: bug 1846003 disco/linux-azure: bug 1846009 disco/linux-gcp: bug 1846015 disco/linux-kvm: bug 1846017 disco/linux-oracle: bug 1846019 disco/linux-raspi2: bug 1846001 disco/linux-snapdragon: bug 1846021 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/1846026 Title: disco/linux: 5.0.0-31.33 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1846026/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846641] Re: eoan/linux: 5.3.0-17.18 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Fix Committed ** Tags added: block-proposed-eoan ** 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 packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed - phase: Holding before Promote to Proposed - phase-changed: Friday, 04. October 2019 03:21 UTC + phase: Promote to Proposed + phase-changed: Friday, 04. October 2019 23:46 UTC reason: - promote-to-proposed: Stalled -- another kernel is currently pending in Proposed + promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync trackers: bionic/linux-hwe-edge: bug 1846636 eoan/linux-aws: bug 1846613 eoan/linux-azure: bug 1846616 eoan/linux-gcp: bug 1846623 eoan/linux-kvm: bug 1846628 eoan/linux-oracle: bug 1846630 eoan/linux-raspi2: bug 1846611 eoan/linux-snapdragon: bug 1846634 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/1846641 Title: eoan/linux: 5.3.0-17.18 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1846641/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846535] Re: cloud-init 19.2.36 fails with python exception "Not all expected physical devices present ..." during bionic image deployment from MAAS
Oracle SRU verification logs ** Attachment added: "oracle-sru-19.2.36.ubuntu2.txt" https://bugs.launchpad.net/cloud-init/+bug/1846535/+attachment/5294454/+files/oracle-sru-19.2.36.ubuntu2.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846535 Title: cloud-init 19.2.36 fails with python exception "Not all expected physical devices present ..." during bionic image deployment from MAAS To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1846535/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846535] Re: cloud-init 19.2.36 fails with python exception "Not all expected physical devices present ..." during bionic image deployment from MAAS
Attach file ec2-sru-19.2.36.ubuntu2.txt.
** Attachment added: "ec2-sru-19.2.36.ubuntu2.txt"
https://bugs.launchpad.net/bugs/1846535/+attachment/5294457/+files/ec2-sru-19.2.36.ubuntu2.txt
** Description changed:
[Impact]
Any instances launched with bridges or bonds in their network
configuration will fail to bring up networking.
[Test Case]
# Juju bootstrap on maas of a machine sets up a network bridge that triggers
a failure in cloud-init init stage.
# This results in a maas machine deployment failure and the machine gets
released
Procedure:
# Alternate steps on a maas machine with a bridge already created
A1. confirm a bridge interface is configured for the target machine on
interface eno1, name it broam, attach it to a subnet and select auto-assign for
IP
- A2. click deploy -> bionic
+ A2. click deploy -> bionic
A3. Once manual deployment fails go to step 2 below
# Alternative 2 juju bootstrap failure on maas
B1: juju bootrap mymaas --no-gui
- B2: Once bootstrap fails go to step 2
+ B2: Once bootstrap fails go to step 2
2. After deployment failure and machine is powered off click on the
failed/released node in the MAAS UI
3. Click Rescue Mode from the 'Take Action' drop down in the MAAS UI
4. Grab the IP from the interfaces tab
5. ssh ubuntu@ -- cloud-init status --long
# Expect failure message
6. Click Exit Rescue Mode on the node in MAAS UI.
7. ssh to the maas server add the following lines to
/etc/maas/preseeds/curtin_userdata to test official *-proposed packages:
system_upgrade: {enabled: True}
apt:
  sources:
proposed.list:
   source: deb $MIRROR $RELEASE-proposed main universe # upstream
-proposed
8. Repeat step 1 and expect bootstrap success
# expect to see MAASDatasource from bootstrapped machine and no errors
9. juju ssh 0 -- cloud-init status --long
+
+
+ Additional verification checks to avoid regression
+ - DONE oracle
+ - DONE ec2
+ - DONE openstack
+ - DONE gce
+ - TODO azure
[Regression Potential]
The change being SRU'd adds more conditions to an existing conditional.
There is potential to regress the cases that the existing conditional
was introduced to cover, so we will be testing those specifically.
Other than that, there was some minor refactoring of the existing
conditional statement (which did not change the logic it checks), which
could cause issues for Oracle netfailover interfaces. We will also
specifically test on Oracle.
[Original Report]
Symptoms
After deployment of Ubuntu Bionic image on MAAS provider (deploying to a
bare metal server) juju cannot access any deployed machine due to
missing SSH keys and machines are stuck in pending state:
$ juju ssh 0
ERROR retrieving SSH host keys for "0": keys not found
$ juju machines
Machine StateDNSInst id Series AZ Message
0pending 172.20.10.125 block-3 bionic AZ3 Deployed
1pending 172.20.10.124 block-2 bionic AZ2 Deployed
2pending 172.20.10.126 block-1 bionic AZ1 Deployed
3pending 172.20.10.127 object-2 bionic AZ1 Deployed
4pending 172.20.10.128 object-1 bionic AZ2 Deployed
5pending 172.20.10.129 object-3 bionic AZ3 Deployed
It worth mentioning that pods can be successfully deployed with MAAS,
only bare metal deployment fails.
We checked different bionic images: cloud-init 19.2.24 works, and cloud-
init 19.2.36 doesn't.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1846535
Title:
cloud-init 19.2.36 fails with python exception "Not all expected
physical devices present ..." during bionic image deployment from
MAAS
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1846535/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846535] Re: cloud-init 19.2.36 fails with python exception "Not all expected physical devices present ..." during bionic image deployment from MAAS
Attach file nocloud-lxd-sru-19.2.36.ubuntu2.txt. ** Attachment added: "nocloud-lxd-sru-19.2.36.ubuntu2.txt" https://bugs.launchpad.net/bugs/1846535/+attachment/5294458/+files/nocloud-lxd-sru-19.2.36.ubuntu2.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846535 Title: cloud-init 19.2.36 fails with python exception "Not all expected physical devices present ..." during bionic image deployment from MAAS To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1846535/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846535] Re: cloud-init 19.2.36 fails with python exception "Not all expected physical devices present ..." during bionic image deployment from MAAS
Attach file azure-sru-19.2.36.ubuntu2.txt.
** Attachment added: "azure-sru-19.2.36.ubuntu2.txt"
https://bugs.launchpad.net/bugs/1846535/+attachment/5294460/+files/azure-sru-19.2.36.ubuntu2.txt
** Description changed:
[Impact]
Any instances launched with bridges or bonds in their network
configuration will fail to bring up networking.
[Test Case]
# Juju bootstrap on maas of a machine sets up a network bridge that triggers
a failure in cloud-init init stage.
# This results in a maas machine deployment failure and the machine gets
released
Procedure:
# Alternate steps on a maas machine with a bridge already created
A1. confirm a bridge interface is configured for the target machine on
interface eno1, name it broam, attach it to a subnet and select auto-assign for
IP
A2. click deploy -> bionic
A3. Once manual deployment fails go to step 2 below
# Alternative 2 juju bootstrap failure on maas
B1: juju bootrap mymaas --no-gui
B2: Once bootstrap fails go to step 2
2. After deployment failure and machine is powered off click on the
failed/released node in the MAAS UI
3. Click Rescue Mode from the 'Take Action' drop down in the MAAS UI
4. Grab the IP from the interfaces tab
5. ssh ubuntu@ -- cloud-init status --long
# Expect failure message
6. Click Exit Rescue Mode on the node in MAAS UI.
7. ssh to the maas server add the following lines to
/etc/maas/preseeds/curtin_userdata to test official *-proposed packages:
system_upgrade: {enabled: True}
apt:
  sources:
proposed.list:
   source: deb $MIRROR $RELEASE-proposed main universe # upstream
-proposed
8. Repeat step 1 and expect bootstrap success
# expect to see MAASDatasource from bootstrapped machine and no errors
9. juju ssh 0 -- cloud-init status --long
-
Additional verification checks to avoid regression
- - DONE oracle
- - DONE ec2
- - DONE openstack
- - DONE gce
- - TODO azure
+ Â - DONE oracle
+ Â - DONE ec2
+ Â - DONE openstack
+ Â - DONE gce
+ Â - DONE azure
+ - DONE nocloud kvm
+ - DONE nocloud lxd
[Regression Potential]
The change being SRU'd adds more conditions to an existing conditional.
There is potential to regress the cases that the existing conditional
was introduced to cover, so we will be testing those specifically.
Other than that, there was some minor refactoring of the existing
conditional statement (which did not change the logic it checks), which
could cause issues for Oracle netfailover interfaces. We will also
specifically test on Oracle.
[Original Report]
Symptoms
After deployment of Ubuntu Bionic image on MAAS provider (deploying to a
bare metal server) juju cannot access any deployed machine due to
missing SSH keys and machines are stuck in pending state:
$ juju ssh 0
ERROR retrieving SSH host keys for "0": keys not found
$ juju machines
Machine StateDNSInst id Series AZ Message
0pending 172.20.10.125 block-3 bionic AZ3 Deployed
1pending 172.20.10.124 block-2 bionic AZ2 Deployed
2pending 172.20.10.126 block-1 bionic AZ1 Deployed
3pending 172.20.10.127 object-2 bionic AZ1 Deployed
4pending 172.20.10.128 object-1 bionic AZ2 Deployed
5pending 172.20.10.129 object-3 bionic AZ3 Deployed
It worth mentioning that pods can be successfully deployed with MAAS,
only bare metal deployment fails.
We checked different bionic images: cloud-init 19.2.24 works, and cloud-
init 19.2.36 doesn't.
** Tags removed: verification-needed verification-needed-bionic
verification-needed-disco verification-needed-xenial
** Tags added: verification-done verification-done-bionic
verification-done-disco verification-done-xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1846535
Title:
cloud-init 19.2.36 fails with python exception "Not all expected
physical devices present ..." during bionic image deployment from
MAAS
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1846535/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846535] Re: cloud-init 19.2.36 fails with python exception "Not all expected physical devices present ..." during bionic image deployment from MAAS
gce sru verification logs ** Attachment added: "gce-sru-19.2.36.ubuntu2.txt" https://bugs.launchpad.net/cloud-init/+bug/1846535/+attachment/5294455/+files/gce-sru-19.2.36.ubuntu2.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846535 Title: cloud-init 19.2.36 fails with python exception "Not all expected physical devices present ..." during bionic image deployment from MAAS To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1846535/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846535] Re: cloud-init 19.2.36 fails with python exception "Not all expected physical devices present ..." during bionic image deployment from MAAS
Attach file openstack-sru-19.2.36.ubuntu2.txt. ** Attachment added: "openstack-sru-19.2.36.ubuntu2.txt" https://bugs.launchpad.net/bugs/1846535/+attachment/5294456/+files/openstack-sru-19.2.36.ubuntu2.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846535 Title: cloud-init 19.2.36 fails with python exception "Not all expected physical devices present ..." during bionic image deployment from MAAS To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1846535/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846535] Re: cloud-init 19.2.36 fails with python exception "Not all expected physical devices present ..." during bionic image deployment from MAAS
Attach file nocloud-kvm-sru-19.2.36.ubuntu2.txt. ** Attachment added: "nocloud-kvm-sru-19.2.36.ubuntu2.txt" https://bugs.launchpad.net/bugs/1846535/+attachment/5294459/+files/nocloud-kvm-sru-19.2.36.ubuntu2.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846535 Title: cloud-init 19.2.36 fails with python exception "Not all expected physical devices present ..." during bionic image deployment from MAAS To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1846535/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846105] Re: bionic/linux-snapdragon: 4.15.0-1066.73 -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: 1846131 packages: main: linux-snapdragon meta: linux-meta-snapdragon phase: Testing phase-changed: Wednesday, 02. October 2019 23:12 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress - security-signoff: Pending -- waiting for signoff + security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-snapdragon/dragonboard-kernel: bug 1846104 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/1846105 Title: bionic/linux-snapdragon: 4.15.0-1066.73 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1846105/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846108] Re: bionic/linux-aws-fips: 4.15.0-2002.2 -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: 1846110 packages: lrm: linux-restricted-modules-aws-fips main: linux-aws-fips meta: linux-meta-aws-fips signed: linux-signed-aws-fips - phase: Holding before Promote to Proposed - phase-changed: Friday, 04. October 2019 19:37 UTC + phase: Ready for Promote to Proposed + phase-changed: Friday, 04. October 2019 23:17 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/1846108 Title: bionic/linux-aws-fips: 4.15.0-2002.2 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1846108/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846110] Re: bionic/linux-aws: 4.15.0-1052.54 -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: 1846131 packages: lrm: linux-restricted-modules-aws main: linux-aws meta: linux-meta-aws phase: Testing phase-changed: Wednesday, 02. October 2019 23:13 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress - security-signoff: Pending -- waiting for signoff + security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws-fips: bug 1846108 bionic/linux-aws/aws-kernel: bug 1846107 xenial/linux-aws-hwe: bug 1846109 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/1846110 Title: bionic/linux-aws: 4.15.0-1052.54 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1846110/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846115] Re: bionic/linux-kvm: 4.15.0-1048.48 -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: 1846131 packages: main: linux-kvm meta: linux-meta-kvm phase: Testing phase-changed: Wednesday, 02. October 2019 23:14 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress - security-signoff: Pending -- waiting for signoff + security-signoff: Stalled -- 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/1846115 Title: bionic/linux-kvm: 4.15.0-1048.48 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1846115/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1181666] Re: gnome-shell randomly blocks mouse clicks from working in app windows
I get this problem several times a day and it's become very frustrating. Ubuntu 18.04.3 GNOME 3.28.2 Please let me know if any additional information can help triage the bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1181666 Title: gnome-shell randomly blocks mouse clicks from working in app windows To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1181666/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846844] [NEW] Procps: top -b does not display the correct CPU percentages
Public bug reported: Affects: 2:3.3.12-3ubuntu1.2 (bionic) & 2:3.3.10-4ubuntu2.4 (xenial) If I run 'top -b -n 1' the CPU percentages are the same every single time. If I run with more iterations the CPU percentages of subsequent iterations update in real time. If I run top interactively then the CPU percentages correctly update in real time. Here's an example. 1) With n=1 the same CPU percentages are always displayed. while true ; do top -b -n 1 | grep -E "^%Cpu" ; sleep 10; done %Cpu(s): 46.1 us, 4.1 sy, 0.2 ni, 48.1 id, 0.2 wa, 0.0 hi, 1.2 si, 0.0 st %Cpu(s): 46.1 us, 4.1 sy, 0.2 ni, 48.1 id, 0.2 wa, 0.0 hi, 1.2 si, 0.0 st %Cpu(s): 46.1 us, 4.1 sy, 0.2 ni, 48.1 id, 0.2 wa, 0.0 hi, 1.2 si, 0.0 st %Cpu(s): 46.1 us, 4.1 sy, 0.2 ni, 48.1 id, 0.2 wa, 0.0 hi, 1.2 si, 0.0 st %Cpu(s): 46.1 us, 4.1 sy, 0.2 ni, 48.1 id, 0.2 wa, 0.0 hi, 1.2 si, 0.0 st %Cpu(s): 46.1 us, 4.1 sy, 0.2 ni, 48.1 id, 0.2 wa, 0.0 hi, 1.2 si, 0.0 st %Cpu(s): 46.1 us, 4.1 sy, 0.2 ni, 48.1 id, 0.2 wa, 0.0 hi, 1.2 si, 0.0 st %Cpu(s): 46.1 us, 4.1 sy, 0.2 ni, 48.1 id, 0.2 wa, 0.0 hi, 1.2 si, 0.0 st %Cpu(s): 46.1 us, 4.1 sy, 0.2 ni, 48.1 id, 0.2 wa, 0.0 hi, 1.2 si, 0.0 st 2) With n=2 the second iteration shows a changing CPU percentage, but the first is still clearly wrong. while true ; do top -b -n 2 | grep -E "^%Cpu" ; sleep 10; done %Cpu(s): 46.1 us, 4.1 sy, 0.2 ni, 48.1 id, 0.2 wa, 0.0 hi, 1.2 si, 0.0 st %Cpu(s): 27.3 us, 1.7 sy, 0.0 ni, 70.5 id, 0.0 wa, 0.0 hi, 0.4 si, 0.0 st %Cpu(s): 46.1 us, 4.1 sy, 0.2 ni, 48.1 id, 0.2 wa, 0.0 hi, 1.2 si, 0.0 st %Cpu(s): 50.9 us, 5.4 sy, 0.0 ni, 42.2 id, 0.1 wa, 0.0 hi, 1.4 si, 0.0 st %Cpu(s): 46.1 us, 4.1 sy, 0.2 ni, 48.1 id, 0.2 wa, 0.0 hi, 1.2 si, 0.0 st %Cpu(s): 63.3 us, 5.2 sy, 0.0 ni, 29.2 id, 0.1 wa, 0.0 hi, 2.2 si, 0.0 st %Cpu(s): 46.1 us, 4.1 sy, 0.2 ni, 48.1 id, 0.2 wa, 0.0 hi, 1.2 si, 0.0 st %Cpu(s): 43.3 us, 2.9 sy, 0.0 ni, 52.4 id, 0.1 wa, 0.0 hi, 1.2 si, 0.0 st %Cpu(s): 46.1 us, 4.1 sy, 0.2 ni, 48.1 id, 0.2 wa, 0.0 hi, 1.2 si, 0.0 st %Cpu(s): 38.0 us, 3.7 sy, 0.0 ni, 56.8 id, 0.2 wa, 0.0 hi, 1.4 si, 0.0 st %Cpu(s): 46.1 us, 4.1 sy, 0.2 ni, 48.1 id, 0.2 wa, 0.0 hi, 1.2 si, 0.0 st %Cpu(s): 47.9 us, 3.5 sy, 0.0 ni, 47.2 id, 0.1 wa, 0.0 hi, 1.2 si, 0.0 st This affects both Xenial and Bionic. ** Affects: procps (Ubuntu) Importance: Undecided Status: New ** Tags: batch procps top -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846844 Title: Procps: top -b does not display the correct CPU percentages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1846844/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846843] Re: package manpages 3.54-1ubuntu1 failed to install/upgrade: trying to overwrite '/usr/share/man/man1/iconv.1.gz', which is also in package libc-bin 2.19-0ubuntu6.15
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846843 Title: package manpages 3.54-1ubuntu1 failed to install/upgrade: trying to overwrite '/usr/share/man/man1/iconv.1.gz', which is also in package libc-bin 2.19-0ubuntu6.15 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/manpages/+bug/1846843/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846841] Re: zfsutils-linux is a Depends: not a Recommends:
** Changed in: ubuntu-mate-meta (Ubuntu) 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/1846841 Title: zfsutils-linux is a Depends: not a Recommends: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-mate-meta/+bug/1846841/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846843] [NEW] package manpages 3.54-1ubuntu1 failed to install/upgrade: trying to overwrite '/usr/share/man/man1/iconv.1.gz', which is also in package libc-bin 2.19-0ubuntu6.15
Public bug reported: I'm was trying to apply apt-get update command, and it's fault. Than I did apt-get upgrade. This error was during upgrade... ProblemType: Package DistroRelease: Ubuntu 19.04 Package: manpages 3.54-1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-148.174~14.04.1-generic 4.4.177 Uname: Linux 4.4.0-148-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 Date: Fri Oct 4 19:50:04 2019 Dependencies: DuplicateSignature: package:manpages:3.54-1ubuntu1:trying to overwrite '/usr/share/man/man1/iconv.1.gz', which is also in package libc-bin 2.19-0ubuntu6.15 ErrorMessage: trying to overwrite '/usr/share/man/man1/iconv.1.gz', which is also in package libc-bin 2.19-0ubuntu6.15 InstallationDate: Installed on 2018-01-11 (631 days ago) InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1) PackageArchitecture: all RelatedPackageVersions: dpkg 1.17.5ubuntu5.8 apt 1.0.1ubuntu2.23 SourcePackage: manpages Title: package manpages 3.54-1ubuntu1 failed to install/upgrade: trying to overwrite '/usr/share/man/man1/iconv.1.gz', which is also in package libc-bin 2.19-0ubuntu6.15 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: manpages (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package disco package-conflict -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846843 Title: package manpages 3.54-1ubuntu1 failed to install/upgrade: trying to overwrite '/usr/share/man/man1/iconv.1.gz', which is also in package libc-bin 2.19-0ubuntu6.15 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/manpages/+bug/1846843/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846842] [NEW] the upgrade tool from 19.04 to 19.10 failed badly
Public bug reported: I upgraded my old crappy box to 19.10 beta from 19.04, things did not go well the upgrade tool eoan it did not run well I could not get many of the buttons to work by clicking I had to use tab and enter, then the thing that's supposed stop it locking fail while I was asleep; woke up it was locked, and when I tried to unlock it I just got a blank screen. I had to ssh in to it find out what was going on I found it was stuck I gave it an hour to come out of it, it didn't, so I killed the processes with sudo kill -1 pid-of-the-python-program pid-of-the-shell-script then I rebooted it by sudo shutdown, and ssh in again and it was still sick and half done, so I called sudo apt upgrade, which didn't work but gave me the dpkg (sudo dpkg --configure -a) command to use, I ran that and it cleaned it up a lot, and I was able to login to gnome-shell it was still on version 3.32.2 and was a little messed up but worked, I tried the update-manager -d &, that gave me a partial upgrade program which failed, in the end, I fixed it with sudo apt-get dist-upgrade and running the normal update-manager program till every thing was up to date, now it's fine but it took much drama to do it ** Affects: 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/1846842 Title: the upgrade tool from 19.04 to 19.10 failed badly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1846842/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846535] Re: cloud-init 19.2.36 fails with python exception "Not all expected physical devices present ..." during bionic image deployment from MAAS
I have also successfully verified the bionic fix on MAAS. Enabling the *-proposed repo via curtin_userdata pulled the latest cloud-init package fixed the issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846535 Title: cloud-init 19.2.36 fails with python exception "Not all expected physical devices present ..." during bionic image deployment from MAAS To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1846535/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846841] [NEW] zfsutils-linux is a Depends: not a Recommends:
Public bug reported: While adding `zfsutils-linux` to the ubuntu-mate-meta package to address LP: #1843768 it was erroneously added as Depends: when it should be a Recommends: ** Affects: ubuntu-mate-meta (Ubuntu) Importance: Critical Assignee: Martin Wimpress (flexiondotorg) Status: In Progress ** Changed in: ubuntu-mate-meta (Ubuntu) Status: New => In Progress ** Changed in: ubuntu-mate-meta (Ubuntu) Importance: Undecided => Critical ** Changed in: ubuntu-mate-meta (Ubuntu) Assignee: (unassigned) => Martin Wimpress (flexiondotorg) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846841 Title: zfsutils-linux is a Depends: not a Recommends: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-mate-meta/+bug/1846841/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1819207] Re: [FFe] Add Modaliases to open-vm-tools-desktop to allow automatic installation by ubuntu-drivers
Hello Jean-Baptiste, or anyone else affected, Accepted ubuntu-drivers-common into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /ubuntu-drivers-common/1:0.5.2.4 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. ** Changed in: ubuntu-drivers-common (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags removed: verification-done verification-done-bionic ** Tags added: verification-needed 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/1819207 Title: [FFe] Add Modaliases to open-vm-tools-desktop to allow automatic installation by ubuntu-drivers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1819207/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1843796] Re: ubuntu-drivers install --gpgpu should use a DKMS fallback when no linux-modules-nvidia package is available
Hello Alberto, or anyone else affected, Accepted ubuntu-drivers-common into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /ubuntu-drivers-common/1:0.5.2.4 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. ** Changed in: ubuntu-drivers-common (Ubuntu Bionic) Status: Incomplete => Fix Committed ** Tags added: verification-needed 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/1843796 Title: ubuntu-drivers install --gpgpu should use a DKMS fallback when no linux-modules-nvidia package is available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1843796/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846204] Re: eoan/linux: 5.3.0-16.17 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: In Progress => Confirmed ** 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 packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed - phase: Testing - phase-changed: Wednesday, 02. October 2019 01:36 UTC + phase: Ready for Testing + phase-changed: Friday, 04. October 2019 22:25 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress trackers: bionic/linux-hwe-edge: bug 1845727 eoan/linux-aws: bug 1845720 eoan/linux-azure: bug 1845721 eoan/linux-gcp: bug 1845722 eoan/linux-kvm: bug 1845723 eoan/linux-oracle: bug 1845724 eoan/linux-raspi2: bug 1845719 eoan/linux-snapdragon: bug 1845725 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/1846204 Title: eoan/linux: 5.3.0-16.17 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1846204/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846535] Re: cloud-init 19.2.36 fails with python exception "Not all expected physical devices present ..." during bionic image deployment from MAAS
@darmadoo: The cloud-init package is baked into the cloud images that MAAS uses to deploy instances. You have to wait for the next cloud image that will contain this fixed cloud-init, or you can use the workaround in my comment #16 to use a previous image in the meantime. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846535 Title: cloud-init 19.2.36 fails with python exception "Not all expected physical devices present ..." during bionic image deployment from MAAS To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1846535/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845828] Re: Timeout error while renaming a file
** Also affects: xfdesktop via https://bugzilla.xfce.org/show_bug.cgi?id=11283 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1845828 Title: Timeout error while renaming a file To manage notifications about this bug go to: https://bugs.launchpad.net/xfdesktop/+bug/1845828/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846535] Re: cloud-init 19.2.36 fails with python exception "Not all expected physical devices present ..." during bionic image deployment from MAAS
How would I make sure that MAAS pulls the latest package of cloud-init? running 'apt policy cloud-init' shows that I do not have cloud-init installed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846535 Title: cloud-init 19.2.36 fails with python exception "Not all expected physical devices present ..." during bionic image deployment from MAAS To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1846535/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846837] Re: totem-video-thumbnailer in Ubuntu 19.10 is currently broken on aarch64
I added gcc-9 and ffmpeg to related packages because if search "libgomp.so.1: cannot allocate memory in static TLS block" in Google you will find this issue starting to appear in different program this years (such as Anaconda installer, OpenCV, PHP ImageMagick module) so I don't think this issue is isolated to Totem. However, Totem is only program where I can reliable reproduce this issue right now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846837 Title: totem-video-thumbnailer in Ubuntu 19.10 is currently broken on aarch64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ffmpeg/+bug/1846837/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846837] [NEW] totem-video-thumbnailer in Ubuntu 19.10 is currently broken on aarch64
Public bug reported: Hello! I found that totem-video-thumbnailer is broken on aarch64. It fail with following error: (totem-video-thumbnailer:12136): GStreamer-WARNING **: 00:43:52.740: Failed to load plugin '/usr/lib/aarch64-linux- gnu/gstreamer-1.0/libgstlibav.so': /lib/aarch64-linux-gnu/libgomp.so.1: cannot allocate memory in static TLS block (totem-video-thumbnailer:12136): GStreamer-WARNING **: 00:43:52.764: Failed to load plugin '/usr/lib/aarch64-linux- gnu/gstreamer-1.0/libgstlibav.so': /lib/aarch64-linux-gnu/libgomp.so.1: cannot allocate memory in static TLS block (totem-video-thumbnailer:12136): GStreamer-WARNING **: 00:43:52.788: Failed to load plugin '/usr/lib/aarch64-linux- gnu/gstreamer-1.0/libgstlibav.so': /lib/aarch64-linux-gnu/libgomp.so.1: cannot allocate memory in static TLS block I tried to rollback all related packages I could think of (totem, gcc-9, ffmpeg) to previous releases, but for some reason this doesn't help. I remember video thumbnail generation on aarch64 worked fine few weeks ago. ** Affects: ffmpeg (Ubuntu) Importance: Undecided Status: New ** Affects: gcc-9 (Ubuntu) Importance: Undecided Status: New ** Affects: totem (Ubuntu) Importance: Undecided Status: New ** Also affects: gcc-9 (Ubuntu) Importance: Undecided Status: New ** Also affects: ffmpeg (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/1846837 Title: totem-video-thumbnailer in Ubuntu 19.10 is currently broken on aarch64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ffmpeg/+bug/1846837/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1286836] Re: package libpostproc52 6:0.8.10-0ubuntu0.13.10.1 failed to install/upgrade: libpostproc52:amd64 6:0.git20120821-4 (Multi-Arch: no) is not co-installable with libpostproc52 which has m
** Changed in: libav (Ubuntu) Assignee: (unassigned) => pablo (pablostar) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1286836 Title: package libpostproc52 6:0.8.10-0ubuntu0.13.10.1 failed to install/upgrade: libpostproc52:amd64 6:0.git20120821-4 (Multi-Arch: no) is not co-installable with libpostproc52 which has multiple installed instances To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libav/+bug/1286836/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1844654] Re: [SRU] ext-pack: disable auto installation defaulting to yes
thanks Robie for releasing them quickly! I would even had fixed them two days in advance if I were notified about this bug... the delay has been because I don't look to my email daily! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1844654 Title: [SRU] ext-pack: disable auto installation defaulting to yes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox-ext-pack/+bug/1844654/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846131] Re: bionic/linux: 4.15.0-66.75 -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 bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Thursday, 03. October 2019 10:54 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress - security-signoff: Pending -- waiting for signoff + security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws: bug 1846110 bionic/linux-fips: bug 1846119 bionic/linux-gke-4.15: bug 1846114 bionic/linux-ibm-gt: bug 1846116 bionic/linux-kvm: bug 1846115 bionic/linux-oem: bug 1846106 bionic/linux-oracle: bug 1846118 bionic/linux-raspi2: bug 1846103 bionic/linux-snapdragon: bug 1846105 bionic/linux/pc-kernel: bug 1846099 bionic/linux/pc-lowlatency-kernel: bug 1846100 xenial/linux-azure: bug 1846123 xenial/linux-gcp: bug 1846126 xenial/linux-hwe: bug 1846130 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/1846131 Title: bionic/linux: 4.15.0-66.75 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1846131/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1815237] Re: stop shipping "update-pciids" in /usr/sbin
** Changed in: pciutils (Ubuntu) Assignee: Mark Thomas (markthomas) => (unassigned) ** Changed in: pciutils (Ubuntu Disco) Assignee: Mark Thomas (markthomas) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1815237 Title: stop shipping "update-pciids" in /usr/sbin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pciutils/+bug/1815237/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846535] Re: cloud-init 19.2.36 fails with python exception "Not all expected physical devices present ..." during bionic image deployment from MAAS
I successfully verified the bionic fix on MAAS. Here's what I did: 1. deployed a machine with a bridge via maas 2. machine went to deployed mode, couldn't ssh in 3. switched to rescue mode, ssh'd in 4. mounted /, captured cloud-init-output.log with error: http://paste.ubuntu.com/p/Gg53xf9wtZ/ 5. I think enabled proposed via curtin_userdata and repeated, and ssh worked and the error was gone: http://paste.ubuntu.com/p/gXVGmKvWHY/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846535 Title: cloud-init 19.2.36 fails with python exception "Not all expected physical devices present ..." during bionic image deployment from MAAS To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1846535/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1843768] Re: [FFe] Ubiquity with zfs install option
This bug was fixed in the package ubuntu-budgie-meta - 0.53 --- ubuntu-budgie-meta (0.53) eoan; urgency=medium * Refreshed dependencies * Added zfsutils-linux to desktop-recommends (LP: #1843768) -- David Mohammed Fri, 04 Oct 2019 20:45:05 +0100 ** Changed in: ubuntu-budgie-meta (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/1843768 Title: [FFe] Ubiquity with zfs install option To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1843768/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1843355] Re: Remove version "2:2.2.4-1" from eoan proposed
This bug was fixed in the package python-tblib - 1.4.0-2ubuntu1 --- python-tblib (1.4.0-2ubuntu1) eoan; urgency=medium * Reintroduce py2 python-tblib for django 1.11.22 (LP: #1843355) -- Adam Conrad Fri, 04 Oct 2019 12:24:49 -0600 ** Changed in: python-tblib (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/1843355 Title: Remove version "2:2.2.4-1" from eoan proposed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-django/+bug/1843355/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840571] Re: ubuntu 18.04.3 startup purple screen blink and could not start with kernel 5.0.0+
Dear everyone. Today I update ubuntu-18.04.3 to use software-updater, then update kernel-5.0.0-31. I update two PCs. one is i3-7100 PC, I update kenel-5.0.0-31 to three partitions(sda1,sda2,sda3). so three ubuntu-18.04.3 system updated. I reboot PC, Power on/off PC, but purple screen blink not occur. other is amd CPU PC, update kernel-5.0.0-31 to two partitions(sda1,sda2). so two ubuntu-18.04.3 system updated. I reboot PC, Power on/off PC, but purple screen blink not occur too. I will update other PCs, and report result. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1840571 Title: ubuntu 18.04.3 startup purple screen blink and could not start with kernel 5.0.0+ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1840571/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1735363] Re: inkscape: Port to Python 3
I think that, apart from the build process, there is only this bit that
would need to be chnaged. So I'm currently doing this, but I'd love to
be able to specify that at build time (or for inkscape to detect it by
itself, as I suggested above):
--- a/src/extension/implementation/script.cpp
+++ b/src/extension/implementation/script.cpp
@@ -77,7 +77,7 @@
{"python", "python-interpreter", "pythonw" },
#else
{"perl", "perl-interpreter", "perl" },
-{"python", "python-interpreter", "python" },
+{"python", "python-interpreter", "python3" },
#endif
{"ruby", "ruby-interpreter", "ruby" },
{"shell", "shell-interpreter", "sh" },
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1735363
Title:
inkscape: Port to Python 3
To manage notifications about this bug go to:
https://bugs.launchpad.net/inkscape/+bug/1735363/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1837673] Re: Certbot will be unable to create new ACME accounts
> Their py2 counterparts are of course available, but this means we won't be producing python3-certbot packages, just python-certbot (if 0.27.0 works with py2, that is). I personally think this is fine. We just have to make sure the "certbot" package depends on and uses python-certbot rather than python3-certbot in Xenial. 0.27.0 still works with Python 2. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1837673 Title: Certbot will be unable to create new ACME accounts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-certbot/+bug/1837673/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1837673] Re: Certbot will be unable to create new ACME accounts
There are other changes needed in the backport from cosmic. Specifically, python3 support. The xenial certbot packages are py2 currently, and not all py3 dependencies needed by the cosmic package are available in xenial. These two are missing: - python3-parsedatetime - python3-repoze.sphinx.autointerface Their py2 counterparts are of course available, but this means we won't be producing python3-certbot packages, just python-certbot (if 0.27.0 works with py2, that is). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1837673 Title: Certbot will be unable to create new ACME accounts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-certbot/+bug/1837673/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846108] Re: bionic/linux-aws-fips: 4.15.0-2002.2 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1846110 packages: lrm: linux-restricted-modules-aws-fips main: linux-aws-fips meta: linux-meta-aws-fips signed: linux-signed-aws-fips phase: Holding before Promote to Proposed phase-changed: Friday, 04. October 2019 19:37 UTC reason: - promote-to-proposed: Pending -- builds not complete in ppa lrm:depwait,main:queued,meta:depwait,signed:depwait + promote-to-proposed: Ongoing -- builds not complete in ppa lrm:depwait,meta:depwait,signed:depwait variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846108 Title: bionic/linux-aws-fips: 4.15.0-2002.2 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1846108/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846108] Re: bionic/linux-aws-fips: 4.15.0-2002.2 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1846110 packages: lrm: linux-restricted-modules-aws-fips main: linux-aws-fips meta: linux-meta-aws-fips signed: linux-signed-aws-fips phase: Holding before Promote to Proposed phase-changed: Friday, 04. October 2019 19:37 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa lrm:depwait,main:building,meta:depwait,signed:depwait + promote-to-proposed: Pending -- builds not complete in ppa lrm:depwait,main:queued,meta:depwait,signed:depwait variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846108 Title: bionic/linux-aws-fips: 4.15.0-2002.2 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1846108/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845289] Re: Grub EFI amd64 no longer start EFI/Microsoft/Boot/bootmgfw.efi
@brian-murray I have 2.04-1ubuntu9 installed, as well as these extras: ~> sudo apt list --installed '*grub*' Listing... Done grub-common/eoan,now 2.04-1ubuntu9 amd64 [installed] grub-efi-amd64-bin/eoan,now 2.04-1ubuntu9 amd64 [installed,automatic] grub-efi-amd64-signed/eoan,now 1.125+2.04-1ubuntu9 amd64 [installed] grub-gfxpayload-lists/eoan,now 0.7 amd64 [installed] grub-pc-bin/eoan,now 2.04-1ubuntu9 amd64 [installed] grub-pc/eoan,now 2.04-1ubuntu9 amd64 [installed] grub2-common/eoan,now 2.04-1ubuntu9 amd64 [installed] I've included some extra info below, please let me know if you need any further info or want me to test anything. Here is my machine info: ~> inxi -F System:Host: jay-alien-ubu Kernel: 5.3.0-13-generic x86_64 bits: 64 Desktop: KDE Plasma 5.16.5 Distro: Ubuntu 19.10 (Eoan Ermine) Machine: Type: Desktop System: Alienware product: ASM100 v: N/A serial: Mobo: Dell model: 03V3TG v: A00 serial: UEFI: Alienware v: A07 date: 06/12/2018 CPU: Topology: Dual Core model: Intel Core i3-4130T bits: 64 type: MT MCP L2 cache: 3072 KiB Speed: 1097 MHz min/max: 800/2900 MHz Core speeds (MHz): 1: 1097 2: 1097 3: 1098 4: 1098 Graphics: Device-1: NVIDIA GM107M [GeForce GTX 860M] driver: nvidia v: 435.21 Display: x11 server: X.Org 1.20.5 driver: nvidia unloaded: fbdev,modesetting,nouveau,vesa resolution: 1680x1050~60Hz OpenGL: renderer: GeForce GPU/PCIe/SSE2 v: 4.6.0 NVIDIA 435.21 Audio: Device-1: Intel 8 Series/C220 Series High Definition Audio driver: snd_hda_intel Device-2: NVIDIA driver: snd_hda_intel Device-3: Kingston type: USB driver: hid-generic,snd-usb-audio,usbhid Sound Server: ALSA v: k5.3.0-13-generic Network: Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169 IF: enp3s0 state: up speed: 1000 Mbps duplex: full mac: 98:90:96:a3:d9:75 Device-2: Intel Wireless 3160 driver: iwlwifi IF: wlp4s0 state: down mac: 34:de:1a:37:86:24 Drives:Local Storage: total: 931.51 GiB used: 391.01 GiB (42.0%) ID-1: /dev/sda vendor: Samsung model: SSD 860 EVO 1TB size: 931.51 GiB Partition: ID-1: / size: 468.35 GiB used: 390.97 GiB (83.5%) fs: ext4 dev: /dev/sda2 Sensors: System Temperatures: cpu: 44.0 C mobo: N/A gpu: nvidia temp: 36 C Fan Speeds (RPM): N/A Info: Processes: 274 Uptime: 3m Memory: 11.65 GiB used: 1.90 GiB (16.3%) Shell: fish inxi: 3.0.36 Running update-grub gives me: ~> sudo update-grub Sourcing file `/etc/default/grub' Sourcing file `/etc/default/grub.d/init-select.cfg' Generating grub configuration file ... Found linux image: /boot/vmlinuz-5.3.0-13-generic Found initrd image: /boot/initrd.img-5.3.0-13-generic Found linux image: /boot/vmlinuz-5.3.0-12-generic Found initrd image: /boot/initrd.img-5.3.0-12-generic Found Windows Boot Manager on /dev/sda1@/EFI/Microsoft/Boot/bootmgfw.efi Adding boot menu entry for EFI firmware configuration done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1845289 Title: Grub EFI amd64 no longer start EFI/Microsoft/Boot/bootmgfw.efi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1845289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846012] Re: bionic/linux-gcp: 5.0.0-1020.20~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: 1846015 packages: lrm: linux-restricted-modules-gcp main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Promote to Proposed phase-changed: Friday, 04. October 2019 14:06 UTC reason: - promote-to-proposed: Ongoing -- package copied to Proposed signed:depwait + promote-to-proposed: Pending -- package copied to Proposed signed:retry-needed trackers: bionic/linux-gcp-edge: bug 1846011 bionic/linux-gcp/gcp-kernel: bug 1846010 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/1846012 Title: bionic/linux-gcp: 5.0.0-1020.20~18.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1846012/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846106] Re: bionic/linux-oem: 4.15.0-1058.67 -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: 1846131 packages: lrm: linux-restricted-modules-oem main: linux-oem meta: linux-meta-oem signed: linux-signed-oem phase: Promote to Proposed phase-changed: Friday, 04. October 2019 14:40 UTC reason: - promote-to-proposed: Ongoing -- package copied to Proposed signed:depwait + promote-to-proposed: Pending -- package copied to Proposed signed:retry-needed variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846106 Title: bionic/linux-oem: 4.15.0-1058.67 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1846106/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846796] Re: missing tpm event log on lenovo 5th gen X1 carbon with 5.3 kernel
Okay, getting the bios out of Setup Mode by resetting to factory keys fixed this, and now the tpm0 directory is properly populated. Closing as invalid I guess. ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846796 Title: missing tpm event log on lenovo 5th gen X1 carbon with 5.3 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1846796/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1842439] Re: apport-gtk crashed with SIGSEGV in _gtk_settings_get_screen(settings=0x0)
** Tags added: rls-ee-incoming -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1842439 Title: apport-gtk crashed with SIGSEGV in _gtk_settings_get_screen(settings=0x0) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1842439/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1796501] Re: systemd-resolved tries to mitigate DVE-2018-0001 even if DNSSEC=yes
** Tags added: sts-sponsor-ddstreet -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1796501 Title: systemd-resolved tries to mitigate DVE-2018-0001 even if DNSSEC=yes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1796501/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846073] Re: disco/linux-raspi2: 5.0.0-1020.20 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: In Progress => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846073 Title: disco/linux-raspi2: 5.0.0-1020.20 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1846073/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
