[Bug 2083921] [NEW] 24.04.1 upgrader failed
Public bug reported: Same failure as previously reported for LTS 24.04. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.20 Uname: Linux 6.9.3-76060903-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.6 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Tue Oct 8 07:14:28 2024 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to jammy on 2024-10-08 (0 days ago) VarLogDistupgradeTermlog: modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2018-04-27T16:03:36.737635 ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade jammy third-party-packages wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2083921 Title: 24.04.1 upgrader failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2083921/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2040483] Re: AppArmor denies crun sending signals to containers (stop, kill)
The tests are successful with both the crun and runc runtimes. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2040483 Title: AppArmor denies crun sending signals to containers (stop, kill) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/golang-github-containers-common/+bug/2040483/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2040483] Re: AppArmor denies crun sending signals to containers (stop, kill)
As above, the tests specified for the SRU complete successfully with the new packages installed. ** Tags removed: verification-needed verification-needed-noble ** Tags added: verification-done verification-done-noble ** Tags removed: mantic server-todo -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2040483 Title: AppArmor denies crun sending signals to containers (stop, kill) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/golang-github-containers-common/+bug/2040483/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2040483] Re: AppArmor denies crun sending signals to containers (stop, kill)
There's a possible additional issue with runc apparmor in https://bugs.launchpad.net/ubuntu/+source/runc/+bug/2072452 that is affecting k8s in Noble. May be worth testing the fixed package to see if it corrects that as well. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2040483 Title: AppArmor denies crun sending signals to containers (stop, kill) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/golang-github-containers-common/+bug/2040483/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072452] Re: AppArmor denies crun sending signals to containers
Upstream fault report: https://github.com/containerd/containerd/issues/10542 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072452 Title: AppArmor denies crun sending signals to containers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2072452/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2072452] Re: AppArmor denies crun sending signals to containers
unknown error after kill: runc did not terminate successfully: exit status 1: unable to signal init: permission denied ** Also affects: runc (Ubuntu) Importance: Undecided Status: New ** Bug watch added: github.com/containerd/containerd/issues #10542 https://github.com/containerd/containerd/issues/10542 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072452 Title: AppArmor denies crun sending signals to containers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2072452/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2040483] Re: AppArmor denies crun sending signals to containers (stop, kill)
You are all very welcome to use the version in the Brightbox Experimental PPA (https://launchpad.net/~brightbox/+archive/ubuntu/experimental), which has a Noble update with the fix in it. Bear in mind the title of the PPA: "Here be dragons" -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2040483 Title: AppArmor denies crun sending signals to containers (stop, kill) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/golang-github-containers-common/+bug/2040483/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060624] Re: lubuntu/xubuntu reinstall (& install) on dual boot system, grub does appear & offer OS choice
I have Xubuntu 23.04 on one drive and 22.04 on another drive as a backup. I have upgraded to 24.04 twice, once when it became available and some time around the middle of June. The computer would not boot after I upgraded. I also have Windows 11 on another drive. I am looking forward to when I can install 24.04 and have it work OK. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060624 Title: lubuntu/xubuntu reinstall (& install) on dual boot system, grub does appear & offer OS choice To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calamares-settings-ubuntu/+bug/2060624/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 2040483] Re: AppArmor denies crun sending signals to containers (stop, kill)
It may be more useful to generate a synthetic replacement definition from the go file, and then `apparmor_parser -r` the definition if the definition exists. On Fri, 14 Jun 2024 at 21:30, Andreas Hasenack <2040...@bugs.launchpad.net> wrote: > ** Also affects: libpod (Ubuntu Oracular) >Importance: Undecided >Status: Confirmed > > ** Also affects: golang-github-containers-common (Ubuntu Oracular) >Importance: Undecided >Status: Confirmed > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/2040483 > > Title: > AppArmor denies crun sending signals to containers (stop, kill) > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/golang-github-containers-common/+bug/2040483/+subscriptions > > -- Neil Wilson -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2040483 Title: AppArmor denies crun sending signals to containers (stop, kill) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/golang-github-containers-common/+bug/2040483/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063821] Re: Ubuntu 22.04 server installer doesn't boot on Xen server as domU in PVH mode
Thank you for your reply. My main goal was to raise awareness since it wasn't clear to me whether anyone was aware of this issue. As I mentioned previously, it would be great to be able to install in PVH mode since it is "the best" mode currently available as I understand it based on this page: https://wiki.xenproject.org/wiki/Understanding_the_Virtualization_Spectrum I have (subsequently to submitting this report) encountered similar behaviour with a Debian 12 installer, so it is not Ubuntu-specific. Unfortunately I don't have time to dig much deeper into this, and the workaround I mentioned works well. I have / will mention it again on Debian channels as well. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063821 Title: Ubuntu 22.04 server installer doesn't boot on Xen server as domU in PVH mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xen/+bug/2063821/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2040483] Re: AppArmor denies crun sending signals to containers (stop, kill)
PR accepted upstream. I've backported the patch the oracular MP above. What needs to be done now to get this into an SRU for noble? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2040483 Title: AppArmor denies crun sending signals to containers (stop, kill) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/golang-github-containers-common/+bug/2040483/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2040483] Re: AppArmor denies crun sending signals to containers (stop, kill)
PR opened upstream: https://github.com/containers/common/pull/2004 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2040483 Title: AppArmor denies crun sending signals to containers (stop, kill) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/golang-github-containers-common/+bug/2040483/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065685] Re: aa-logprof fails with 'runbindable' error
ubuntu@srv-9vqc0:~$ sudo grep -r "runbindable*/*" /etc/apparmor.d
/etc/apparmor.d/abstractions/passt: mount options=(rw, runbindable) /,
ubuntu@srv-9vqc0:~$ sudo aa-logprof
ERROR: Operation {'runbindable'} cannot have a source. Source =
AARE('/')
HTH
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2065685
Title:
aa-logprof fails with 'runbindable' error
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2065685/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2040483] Re: AppArmor denies crun sending signals to containers (stop, kill)
I've pushed the changes based on your comments to the MP above. I've left the signal set for podman as (int, quit, term, kill). Do you think that signal set should be tighter, or is that a good compromise? If that seems ok with you, I'll happily handle the PR upstream at GitHub. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2040483 Title: AppArmor denies crun sending signals to containers (stop, kill) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/golang-github-containers-common/+bug/2040483/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2040483] Re: AppArmor denies crun sending signals to containers (stop, kill)
The debdiff is in the MP above. Podman does try to kill the container itself, as the error trace above testifies. May 14 11:14:41 srv-omzr6 kernel: audit: type=1400 audit(1715685281.392:118): apparmor="DENIED" operation="signal" class="signal" profile="containers-default-0.57.4" pid=7458 comm="conmon" requested_mask="receive" denied_mask="receive" signal=term peer="podman" It's trying to kill conmon in some scenarios, which means your policy changes so far are deficient in that regard. We can tighten the signal set there to term and kill, which is certainly no worse than the pre-4.0.0 situation. I note the point about the signal set on the runtimes, and that should be removed. The stop signals can be set to anything within the container. I would suggest extending the AARE to cover the binaries as well as the policy name. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2040483 Title: AppArmor denies crun sending signals to containers (stop, kill) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/golang-github-containers-common/+bug/2040483/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2040483] Re: AppArmor denies crun sending signals to containers (stop, kill)
Adding the podman signal line, and building a libpod that overrides the default packages eliminates the errors I was getting. All the tests in this ticket pass with the updated packages. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2040483 Title: AppArmor denies crun sending signals to containers (stop, kill) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/golang-github-containers-common/+bug/2040483/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2040483] Re: AppArmor denies crun sending signals to containers (stop, kill)
I've built a backported 4.9.4 libpod for noble based on an updated golang-github-containers-common including the above patch. It's available from ppa:brightbox/experimental -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2040483 Title: AppArmor denies crun sending signals to containers (stop, kill) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/golang-github-containers-common/+bug/2040483/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2040483] Re: AppArmor denies crun sending signals to containers (stop, kill)
The debdiff I've put together for oracular updates the patch to be a bit
more general and cover all the signals I've seen so far in testing. (As
well as dropping the other patch that has been incorporated upstream).
# Allow certain signals from OCI runtimes (podman, runc and crun)
signal (receive) set=(int, quit, kill, term)
peer={/usr/bin/,/usr/sbin/,}runc,
signal (receive) set=(int, quit, kill, term)
peer={/usr/bin/,/usr/sbin/,}crun,
signal (receive) set=(int, quit, kill, term)
peer={/usr/bin/,/usr/sbin/,}podman,
Upstream have said they have no apparmor experience, so I suspect they
will take a PR. See https://github.com/containers/common/issues/1898
** Bug watch added: github.com/containers/common/issues #1898
https://github.com/containers/common/issues/1898
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2040483
Title:
AppArmor denies crun sending signals to containers (stop, kill)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/golang-github-containers-common/+bug/2040483/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2040483] Re: AppArmor denies crun sending signals to containers (stop, kill)
The patch above doesn't work as it stands. We are still getting signal filters in the audit log May 14 11:13:06 srv-omzr6 kernel: audit: type=1400 audit(1715685186.296:112): apparmor="DENIED" operation="signal" class="signal" profile="containers-default-0.57.4" pid=8031 comm="3" requested_mask="receive" denied_mask="receive" signal=term peer="crun" May 14 11:13:06 srv-omzr6 kernel: audit: type=1400 audit(1715685186.318:113): apparmor="DENIED" operation="signal" class="signal" profile="containers-default-0.57.4" pid=8033 comm="3" requested_mask="receive" denied_mask="receive" signal=term peer="crun" May 14 11:13:16 srv-omzr6 kernel: audit: type=1400 audit(1715685196.340:114): apparmor="DENIED" operation="signal" class="signal" profile="containers-default-0.57.4" pid=8035 comm="3" requested_mask="receive" denied_mask="receive" signal=kill peer="crun" May 14 11:13:21 srv-omzr6 kernel: audit: type=1400 audit(1715685201.413:115): apparmor="DENIED" operation="signal" class="signal" profile="containers-default-0.57.4" pid=7664 comm="conmon" requested_mask="receive" denied_mask="receive" signal=term peer="podman" May 14 11:14:31 srv-omzr6 kernel: audit: type=1400 audit(1715685271.577:116): apparmor="DENIED" operation="signal" class="signal" profile="containers-default-0.57.4" pid=8049 comm="3" requested_mask="receive" denied_mask="receive" signal=term peer="crun" May 14 11:14:36 srv-omzr6 kernel: audit: type=1400 audit(1715685276.326:117): apparmor="DENIED" operation="signal" class="signal" profile="containers-default-0.57.4" pid=8052 comm="3" requested_mask="receive" denied_mask="receive" signal=kill peer="crun" May 14 11:14:41 srv-omzr6 kernel: audit: type=1400 audit(1715685281.392:118): apparmor="DENIED" operation="signal" class="signal" profile="containers-default-0.57.4" pid=7458 comm="conmon" requested_mask="receive" denied_mask="receive" signal=term peer="podman" May 14 11:14:41 srv-omzr6 kernel: audit: type=1400 audit(1715685281.604:119): apparmor="DENIED" operation="signal" class="signal" profile="containers-default-0.57.4" pid=8055 comm="3" requested_mask="receive" denied_mask="receive" signal=kill peer="crun" -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2040483 Title: AppArmor denies crun sending signals to containers (stop, kill) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/golang-github-containers-common/+bug/2040483/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065685] [NEW] aa-logprof fails with 'runbindable' error
Public bug reported:
On the latest LTS, aa-logprof does nothing other than fail with the
error
ERROR: Operation {'runbindable'} cannot have a source. Source =
AARE('/')
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: apparmor-utils 4.0.0-beta3-0ubuntu3
ProcVersionSignature: User Name 6.8.0-31.31-generic 6.8.1
Uname: Linux 6.8.0-31-generic x86_64
ApparmorStatusOutput:
Error: command ['/usr/sbin/apparmor_status'] failed with exit code 4: You do
not have enough privilege to read the profile set.
apparmor module is loaded.
ApportVersion: 2.28.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: unknown
CloudArchitecture: x86_64
CloudBuildName: server
CloudID: brightbox
CloudName: brightbox
CloudPlatform: ec2
CloudRegion: gb1s-
CloudSerial: 20240423
CloudSubPlatform: metadata (http://169.254.169.254)
Date: Tue May 14 12:29:17 2024
PackageArchitecture: all
ProcKernelCmdline: BOOT_IMAGE=/vmlinuz-6.8.0-31-generic
root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0
SourcePackage: apparmor
Syslog:
2024-05-13T10:19:58.724594+00:00 srv-9vqc0 dbus-daemon[838]: [system] AppArmor
D-Bus mediation is enabled
2024-05-13T10:22:32.966857+00:00 srv-9vqc0 dbus-daemon[666]: [system] AppArmor
D-Bus mediation is enabled
2024-05-13T10:25:00.210572+00:00 srv-9vqc0 dbus-daemon[1044]: [session
uid=1000 pid=1044] AppArmor D-Bus mediation is enabled
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: apparmor (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug cloud-image noble
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2065685
Title:
aa-logprof fails with 'runbindable' error
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2065685/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2040483] Re: AppArmor denies crun sending signals to containers (stop, kill)
To move this on a bit more rapidly as it is a blocking issue for me. It's the same version in Oracular at present. I've pushed the changes as an MP against ubuntu/devel. What needs to happen next? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2040483 Title: AppArmor denies crun sending signals to containers (stop, kill) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/golang-github-containers-common/+bug/2040483/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2040483] Re: AppArmor denies crun sending signals to containers (stop, kill)
** Merge proposal linked: https://code.launchpad.net/~neil-aldur/ubuntu/+source/golang-github-containers-common/+git/golang-github-containers-common/+merge/465970 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2040483 Title: AppArmor denies crun sending signals to containers (stop, kill) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/golang-github-containers-common/+bug/2040483/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063821] [NEW] Ubuntu 22.04 server installer doesn't boot on Xen server as domU in PVH mode
Public bug reported: The Xen server I am working on has Debian 12 as dom0. As mentioned in the summary I am trying to install Ubuntu 22.04 server as a domU in PVH mode. I tested using ubuntu-22.04.4-live-server-amd64.iso. This is the domU configuration I used. It attempts to use PVHGRUB: name = "ubuntu-2204" memory = 1024 maxmem = 1024 vcpus = 1 vif = [ 'bridge=xenbr0' ] disk = [ '/root/ubuntu-22.04.4-live-server-amd64.iso,raw,xvdg,r,cdrom', '/dev/myvg/ubuntu-2204-root,raw,xvda,rw', '/dev/myvg/ubuntu-2204-swap,raw,xvdb,rw' ] type = "pvh" kernel = "/usr/lib/grub-xen/grub-i386-xen_pvh.bin" I can see the grub menu, and I edit the first entry (Try or install Ubuntu) by appending "console=hvc0 nosplash" to the end of the kernel commandline. I can then see console output scrolling past, until this point: Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: Running /scripts/nfs-top ... done. Begin: Running /scripts/nfs-premount ... done. Begin: Running /scripts/casper-premount ... done. done. Unable to find a medium containing a live file system Attempt interactive netboot from a URL? yes no (default yes): no BusyBox v1.30.1 (Ubuntu 1:1.30.1-7ubuntu3) built-in shell (ash) Enter 'help' for a list of built-in commands. (initramfs) Unable to find a medium containing a live file system I then destroyed the domU and tried the following domU config in PV mode instead. The kernel and ramdisk were extracted from the ISO: name = "ubuntu-2204" memory = 1024 maxmem = 1024 vcpus = 1 vif = [ 'bridge=xenbr0' ] disk = [ '/root/ubuntu-22.04.4-live-server-amd64.iso,raw,xvdg,r,cdrom', '/dev/myvg/ubuntu-2204-root,raw,xvda,rw', '/dev/myvg/ubuntu-2204-swap,raw,xvdb,rw' ] type = "pv" kernel = "/root/ubuntu-2204-vmlinuz" ramdisk = "/root/ubuntu-2204-initrd" extra = "console=hvc0 nosplash" The above config allows me to install the OS successfully over the serial console using the standard server installer. After installation is complete, I can boot the newly installed VM with PVHGRUB in PVH mode using this config: name = "ubuntu-2204" memory = 1024 maxmem = 1024 vcpus = 1 vif = [ 'bridge=xenbr0' ] disk = [ '/dev/myvg/ubuntu-2204-root,raw,xvda,rw', '/dev/myvg/ubuntu-2204-swap,raw,xvdb,rw' ] type = "pvh" kernel = "/usr/lib/grub-xen/grub-i386-xen_pvh.bin" I expected to be able to install the Ubuntu 22.04 domU in PVH mode with PVHGRUB. Instead I had to install the Ubuntu 22.04 domU in PV mode as described above. It was only after successful installation in PV mode, that I could boot the installed domU in PVH mode. ** Affects: xen (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/2063821 Title: Ubuntu 22.04 server installer doesn't boot on Xen server as domU in PVH mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xen/+bug/2063821/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061364] Re: Remote login missing user list
NEW Remote Login - Ubuntu 24.04 LTS Noble Numbat (development branch) - Log in to blank desktop with almost no functionality Remote logged on using Remmina RDP to the 24.04 Desktop Remote Logon and: Mouse works, kind of. I can click on and open the calendar. Open and toggle Accessibility settings. Open the System Tray (pictured) and: Power Off/Log off, disconnect the network, toggle Dark Style (no effect), adjust Volume, and Power Mode has zero effect. Note that Remote Desktop Control for the logged in desktop works on port 3390, as it has in previous releases of Ubuntu on port 3389. If there's any logs or reports I can muster from this machine to help the devs with this issue, please point me to info on how I can retrieve them to post here, which I'll gladly attempt. ** Attachment added: "Screenshot from 2024-04-14 19-28-35.png" https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/2061364/+attachment/5765741/+files/Screenshot%20from%202024-04-14%2019-28-35.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061364 Title: Remote login missing user list To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/2061364/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960945] [NEW] package chromium-browser 97.0.4692.71-0ubuntu0.18.04.1 failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 1
Public bug reported: Failed on upgrade from Ubuntu 18.xx to latest version for Jetson nano. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: chromium-browser 97.0.4692.71-0ubuntu0.18.04.1 Uname: Linux 4.9.253-tegra aarch64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: arm64 CasperMD5CheckResult: skip Date: Tue Feb 15 17:14:31 2022 Desktop-Session: 'None' 'None' 'None' Env: 'None' 'None' ErrorMessage: new chromium-browser package pre-installation script subprocess returned error exit status 1 InstalledPlugins: Load-Avg-1min: 1.52 Load-Processes-Running-Percent: 0.4% Lspci-vt: -[:00]---02.0-[01]00.0 Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller ProcKernelCmdLine: tegraid=21.1.2.0.0 ddr_die=4096M@2048M section=512M memtype=0 vpr_resize usb_port_owner_info=0 lane_owner_info=0 emc_max_dvfs=0 touch_id=0@63 video=tegrafb no_console_suspend=1 console=ttyS0,115200n8 debug_uartport=lsport,4 earlyprintk=uart8250-32bit,0x70006000 maxcpus=4 usbcore.old_scheme_first=1 lp0_vec=0x1000@0xff78 core_edp_mv=1125 core_edp_ma=4000 gpt tegra_fbmem=0x14@0x92ca9000 is_hdmi_initialised=1 earlycon=uart8250,mmio32,0x70006000 root=/dev/mmcblk0p1 rw rootwait rootfstype=ext4 console=ttyS0,115200n8 console=tty0 fbcon=map:0 net.ifnames=0 quiet root=/dev/mmcblk0p1 rw rootwait rootfstype=ext4 console=ttyS0,115200n8 console=tty0 fbcon=map:0 net.ifnames=0 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 SourcePackage: chromium-browser Title: package chromium-browser 97.0.4692.71-0ubuntu0.18.04.1 failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2022-02-15 (0 days ago) acpidump: modified.conffile..etc.default.chromium-browser: [deleted] ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package arm64 focal 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/1960945 Title: package chromium-browser 97.0.4692.71-0ubuntu0.18.04.1 failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1960945/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1958308] Re: New upstream release - please update
On Mon, 31 Jan 2022, 07:05 Neil Mayhew, <1958...@bugs.launchpad.net> wrote: > FYI, Debian will likely update again to 8.12.42 which is a better release > to work with long-term. > 8.12.42 is now in Debian testing. Will Ubuntu sync again automatically? > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958308 Title: New upstream release - please update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libphonenumber/+bug/1958308/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958308] Re: New upstream release - please update
> Debian update to the current version which got synced to Ubuntu That's good to hear. FYI, Debian will likely update again to 8.12.42 which is a better release to work with long-term. (It has a git tag, and the artefact versions don't have "-SNAPSHOT" in them). I assume this will sync automatically and still arrive well before the jammy freeze. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958308 Title: New upstream release - please update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libphonenumber/+bug/1958308/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958308] Re: New upstream release - please update
Thank you for the suggestion. I linked to the upstream bug report that describes the issue, but I can see that it's helpful to have a brief summary in both downstream issues. Previously, the C/C++ version of libphonenumber was accepting and parsing phone numbers that have malformed UTF-8 sequences in them, by converting the offending bytes to spaces. It now rejects the input instead of returning a phone number, which the Java version has always done. Accepting malformed UTF-8 is a potential security issue. libphonenumber was also accepting well-formed input containing invalid code points like U+0096 (a C1 control character) which can be the result of a bad conversion from Windows 1252 legacy encoding where N DASH (U+2013) is represented by \x96. If the legacy text is treated as iso-8859-1 instead of windows-1252, \x96 will be converted to U+0096 instead of U+2013. This type of input is now rejected as well. Let me know if this explanation could be improved. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958308 Title: New upstream release - please update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libphonenumber/+bug/1958308/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938591] Re: update 18.04 to readline8
Sure, updating the 7.0 version to include the .pc file for readline is a fine approach to fixing this problem, but I dont think I would consider this a low priority issue. There are 37 non-ubuntu service accounts watching this bug, so it seems to have significant impact. Add to that the fact that, without this update, any package being developed that use readline won't be able to compile with automake on the 18.04 ubuntu release. It should be an easy and very safe (to use the SRU term) to fix this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938591 Title: update 18.04 to readline8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/readline/+bug/1938591/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958308] [NEW] New upstream release - please update
Public bug reported: The upstream project is now at 8.12.41. There are a number of bug fixes in this release, including one for handling invalid UTF-8 sequences correctly in the C version of the library. See: * https://issuetracker.google.com/issues/206677455 * https://github.com/google/libphonenumber/pull/2698 * https://github.com/google/libphonenumber/releases/tag/v8.12.41 I would very much like to see this version make it into Jammy. I've reported this as Debian bug #1003972 (https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=1003972). I don't know how likely it is that this will get into Bookworm before the Jammy feature freeze on Feb 23. ** Affects: libphonenumber (Ubuntu) Importance: Undecided Status: New ** Description changed: The upstream project is now at 8.12.41. There are a number of bug fixes in this release, including one for handling invalid UTF-8 sequences - correctly. + correctly in the C version of the library. See: * https://issuetracker.google.com/issues/206677455 * https://github.com/google/libphonenumber/pull/2698 * https://github.com/google/libphonenumber/releases/tag/v8.12.41 I would very much like to see this version make it into Jammy. I've reported this as Debian bug #1003972 (https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=1003972). I don't know how likely it is that this will get into Bookworm before the Jammy feature freeze on Feb 23. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958308 Title: New upstream release - please update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libphonenumber/+bug/1958308/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938591] Re: update 18.04 to readline8
sooo...Is anyone going to bother looking into this? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938591 Title: update 18.04 to readline8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/readline/+bug/1938591/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956002] [NEW] install on a clean system. toshiba satellite c55-a
Public bug reported: I was installing UBUNTU 21.04 I was playing AisleRiot and Sudoku while the system installed. An error message popped up referring to shim that I closed. Then the Bug Report process started. I'll restart and see what happens. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.19 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.461 Date: Wed Dec 29 13:57:17 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) RebootRequiredPkgs: linux-image-5.11.0-16-generic linux-base SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute ubiquity-21.04.19 ubuntu ** Attachment added: "syslog" https://bugs.launchpad.net/bugs/1956002/+attachment/5550307/+files/syslog -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956002 Title: install on a clean system. toshiba satellite c55-a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1956002/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947757] Re: NVMe Write Zeroes command has incorrect values for PI modes
** Package changed: ubuntu => linux-hwe-5.4 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947757 Title: NVMe Write Zeroes command has incorrect values for PI modes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.4/+bug/1947757/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947757] [NEW] NVMe Write Zeroes command has incorrect values for PI modes
Public bug reported: The attached screenshot of a PCIe trace snippet is from Ubuntu 20.04.3 LTS, k5.4.0-73-generic, with an NVMe controller formatted to 4K+8 DIX PI2 It shows - A Single-sector Write Zeroes command with SLBA=0x02E18439, ILBRT=0x0 (valid for PI2), PRCHK=0x0 (no checks), PRACT=0 *, DEAC=0 **. Command succeeds. - A Single-sector Read command with SLBA=0x02E18439, EILBRT=0x02E18439, PRCHK=0x5. Command rejected with ‘End to End Ref tag Check Error’. Using ILBRT/EILBRT=SLBA and PRCHK=0x5 is standard for PI2 Reads and Writes in Ubuntu (so making it no different to PI1); but if Ubuntu wants to use these values to successfully read data following a Write Zeroes command, the Write Zeroes command should either: a) set the PRACT bit, causing the controller to generate PI data in accordance with the PI mode*; or b) set the DEAC bit, causing the controller to generate standard Deallocated PI data** (all FFs) thus disabling all checks on the next Read via the AppTag/RefTag=0x rule. Relevant NVMe 1.4 text: * “If the Protection Information Action bit (PRACT) is cleared to ‘0’, then the protection information for this command shall be all zeroes. If the Protection Information Action bit (PRACT) is set to ‘1’, then the protection information shall be based on the End-to-end Data Protection Type Settings (DPS) field in the Identify Namespace data structure and the CDW14.ILBRT, CDW15. LBATM, and CDW15. LBAT fields in the Write Zeroes command. “ ** “If the Deallocate bit is cleared to ‘0’ in a Write Zeroes command… [the controller] shall return the protection information in that logical block based on CDW12.PRINFO in that Write Zeroes command. If the Deallocate bit (CDW12.DEAC) is set to ‘1’ in a Write Zeroes command… [the controller] shall return the protection information in that logical block as specified in section 6.7.1.1 [DSM]” ** Affects: ubuntu Importance: Undecided Status: New ** Tags: nvme ** Attachment added: "Screenshot of LeCroy PCIe trace" https://bugs.launchpad.net/bugs/1947757/+attachment/5534326/+files/4k8DixPI2_Wr0s-Rd.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947757 Title: NVMe Write Zeroes command has incorrect values for PI modes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1947757/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 695825] Quick Favor?
Hey, I just signed the petition "Julius Jones is innocent. Don't let him be executed by the state of Oklahoma." and wanted to see if you could help by adding your name. Our goal is to reach 7,500,000 signatures and we need more support. You can read more and sign the petition here: https://chng.it/n2kqmpfxgD Thanks! Neil -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/695825 Title: Qemu is running without kvm acceleration in maverick To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/695825/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1757202] Re: xubuntu / bionic / nvidia-driver-390 can only be used by one user at a time
Just to mention, I am having this bothersome issue also. My Ubuntu 18.04 is completely up to date. Does anyone know of a DM that works better? Cheers... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1757202 Title: xubuntu / bionic / nvidia-driver-390 can only be used by one user at a time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1757202/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938591] [NEW] update 18.04 to readline8
Public bug reported: libreadline up until version 8 didn't include a pkg-config file, and so any other package that relied on being able to find the readline libraries using the autoconf PKG_CHECK_MODULES macro failed in build. This has since been corrected, but I've received several reports of people trying to build dropwatch (https://github.com/nhorman/dropwatch) on 18.04 LTS, which needs readline, and as such fails. libreadline8 has been available in 20.04 for some time, and it would be nice to have it available in the older LTS releases ** Affects: readline (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/1938591 Title: update 18.04 to readline8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/readline/+bug/1938591/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1491963] Re: preseeding for partman/installation_medium_mounted fails because 'seen' is forced to false
I can demonstrate that https://cdimage.ubuntu.com/ubuntu-legacy- server/releases/focal/release/ubuntu-20.04.1-legacy-server-amd64.iso is affected. The installer prompts with > Your installation medium is on /dev/sdb. You will not be able to create, > delete, or resize partitions on this disk, but you may be able to install > to existing partitions there. If I preseed d-i partman/filter_mounted boolean false then the prompt is silenced. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1491963 Title: preseeding for partman/installation_medium_mounted fails because 'seen' is forced to false To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/partman-base/+bug/1491963/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921798] Re: I think it couldn't estimate what was needed for the upgrade and said it couldn't proceed
I have finally proceeded with a partial upgrade. It seems to have worked. I have not investigated all packages and PPAs yet. However I am much relieved. Thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921798 Title: I think it couldn't estimate what was needed for the upgrade and said it couldn't proceed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1921798/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921798] Re: I think it couldn't estimate what was needed for the upgrade and said it couldn't proceed
I did that Ubuntu-release -upgrader -p. It asked me to install all available updates. So I typed sudo apt-get updates. It did 5 lines: Hit:1 http//mirror.intergrid.com.au/Ubuntu focal InRelease Hit:2 http//mirror.intergrid.com.auUbuntu focal-updates InRelease Hit:3 http//mirror.intergrid.com.auUbuntu focal-backports InRelease Hit:4 http//mirror.intergrid.com.auUbuntu focal-security InRelease Reading package lists... Done I then went to software updates and got the same stuff about partial upgrade or continue. So I gave up again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921798 Title: I think it couldn't estimate what was needed for the upgrade and said it couldn't proceed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1921798/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921798] Re: I think it couldn't estimate what was needed for the upgrade and said it couldn't proceed
Thanks Brian and also Chris Guiver for related Bug 192173 I tried that and afterwards I ran the software updater. It still gives me the message about partial updates with a choice of either clicking on partial upgrade or continue. From what I have read, others have had problems with both these options so I am not game to select either. What should I do? Regards Neil -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921798 Title: I think it couldn't estimate what was needed for the upgrade and said it couldn't proceed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1921798/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921798] Re: I think it couldn't estimate what was needed for the upgrade and said it couldn't proceed
Same as before. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921798 Title: I think it couldn't estimate what was needed for the upgrade and said it couldn't proceed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1921798/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921798] Re: I think it couldn't estimate what was needed for the upgrade and said it couldn't proceed
2nd time this has occurred. ** Attachment added: "See screenshot of error message" https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1921798/+attachment/5482220/+files/Screenshot%20from%202021-03-30%2010-02-23.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921798 Title: I think it couldn't estimate what was needed for the upgrade and said it couldn't proceed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1921798/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921798] [NEW] I think it couldn't estimate what was needed for the upgrade and said it couldn't proceed
Public bug reported: I have made several attempt to upgrade. I think the error massage is different each time. This is the second one where I have submitted a report as recommended. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.42 ProcVersionSignature: Ubuntu 4.15.0-139.143-generic 4.15.18 Uname: Linux 4.15.0-139-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_4_15_0_139_143_generic_75 ApportVersion: 2.20.9-0ubuntu7.23 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Tue Mar 30 09:41:48 2021 InstallationDate: Installed on 2017-04-11 (1448 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to bionic on 2021-03-29 (0 days ago) VarLogDistupgradeTermlog: ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic dist-upgrade third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921798 Title: I think it couldn't estimate what was needed for the upgrade and said it couldn't proceed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1921798/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921673] [NEW] An unresolvable problem occurred while calculating the upgrade. This was likely caused by: * Unofficial software packages not provided by Ubuntu Please use the tool 'ppa-purge' fro
Public bug reported: I just thought it would upgrade from 18.04.5 LTS to 20 automatically but I get an error message and don't know what to do . What is PPA, PPA- Purge package and launchpad PPA? How do I know what is official and what is unoffical Ubuntu software? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.42 ProcVersionSignature: Ubuntu 4.15.0-139.143-generic 4.15.18 Uname: Linux 4.15.0-139-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.23 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Mon Mar 29 15:13:23 2021 InstallationDate: Installed on 2017-04-11 (1447 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to bionic on 2021-03-29 (0 days ago) VarLogDistupgradeTermlog: ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic dist-upgrade third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921673 Title: An unresolvable problem occurred while calculating the upgrade. This was likely caused by: * Unofficial software packages not provided by Ubuntu Please use the tool 'ppa-purge' from the ppa-purge package to remove software from a Launchpad PPA and try the upgrade again. If none of this applies, then please report this bug using the command 'ubuntu-bug ubuntu-release-upgrader-core' in a terminal. If you want to investigate this yourself the log files in '/var/log/dist-upgrade' will contain details about the upgrade. Specifically, look at 'main.log' and 'apt.log'. Comment: I don't know what this means. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1921673/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 778627] Re: bash completion now quotes shell variable references rather than expanding them
It's now 2021 - I'm on Ubuntu 20.04.2 LTS and I'm still being annoyed by this bug! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/778627 Title: bash completion now quotes shell variable references rather than expanding them To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/778627/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917185] Re: Nextcloud settings window does not get decorated with window control buttons
Exploring further, this issue happens with the default theme (which is Yaru-MATE-Light, I think) but not with Ambient-MATE, where the "Close" button displays correctly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917185 Title: Nextcloud settings window does not get decorated with window control buttons To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mate-window-applets/+bug/1917185/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917185] [NEW] Nextcloud settings window does not get decorated with window control buttons
Public bug reported: Ubuntu Mate 21.04 daily build fresh install today. Selected "Redmond" layout. Installed nextcloud-desktop and connected to my server. Clicked on the nextcloud icon in the panel and selected "settings". What should happen: - Nextcloud settings app should appear with close/minimise/restore buttons What actually happens: - Nextcloud settings app appears without these buttons. Has to be closed via the task list on the dock. mate-window-applets-common 20.04.0-1 nextcloud-desktop 3.1.1-1 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: mate-window-applets-common 20.04.0-1 ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 Uname: Linux 5.10.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu59 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: MATE Date: Sat Feb 27 23:46:33 2021 InstallationDate: Installed on 2021-02-27 (0 days ago) InstallationMedia: Ubuntu-MATE 21.04 "Hirsute Hippo" - Alpha amd64 (20210227) PackageArchitecture: all SourcePackage: mate-window-applets UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: mate-window-applets (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute ** Attachment added: "Screenshot at 2021-02-27 23-59-09.png" https://bugs.launchpad.net/bugs/1917185/+attachment/5469911/+files/Screenshot%20at%202021-02-27%2023-59-09.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917185 Title: Nextcloud settings window does not get decorated with window control buttons To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mate-window-applets/+bug/1917185/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1913567] Re: Sync puppet 5.5.22-1 (universe) from Debian unstable (main)
Wonderful. Thank you. > On 7 Feb 2021, at 18:05, Dmitry Shachnev <1913...@bugs.launchpad.net> wrote: > > And finally it migrated. > > ** Changed in: puppet (Ubuntu) > Status: Fix Committed => Fix Released > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1913567 > > Title: > Sync puppet 5.5.22-1 (universe) from Debian unstable (main) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1913567/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1913567 Title: Sync puppet 5.5.22-1 (universe) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1913567/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1913567] Re: Sync puppet 5.5.22-1 (universe) from Debian unstable (main)
I have prepared a 1ubuntu1 version with what I think is the missing diff. https://launchpad.net/~brightbox/+archive/ubuntu/experimental?field.series_filter=hirsute which has been built from the following branch https://code.launchpad.net/~neil- aldur/ubuntu/+source/puppet/+git/puppet/+ref/ubuntu/devel -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1913567 Title: Sync puppet 5.5.22-1 (universe) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1913567/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1913557] Re: Please merge 5.5.22-1 into hirsute
** Changed in: puppet (Ubuntu) Status: Fix Released => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1913557 Title: Please merge 5.5.22-1 into hirsute To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1913557/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1913567] Re: Sync puppet 5.5.22-1 (universe) from Debian unstable (main)
Similarly the Debian package passes a local Autopkgtest Following 4.3 here: https://packaging.ubuntu.com/html/auto-pkg-test.html #executing-the-test $ sudo autopkgtest puppet -U --apt-pocket=proposed=src:puppet -- qemu autopkgtest-hirsute-amd64.img Gives autopkgtest [10:55:15]: test command4: ---] autopkgtest [10:55:16]: test command4: - - - - - - - - - - results - - - - - - - - - - command4 PASS autopkgtest [10:55:17]: summary command1 PASS command2 PASS command3 PASS command4 PASS qemu-system-x86_64: terminating on signal 15 from pid 17892 (/usr/bin/python3) Is this is the correct test command to be using locally? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1913567 Title: Sync puppet 5.5.22-1 (universe) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1913567/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1913567] Re: Sync puppet 5.5.22-1 (universe) from Debian unstable (main)
Are there know differences between the Debian CI and the Ubuntu CI? Because it passes autopkgtest over there. https://ci.debian.net/data/autopkgtest/testing/amd64/p/puppet/10026148/log.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1913567 Title: Sync puppet 5.5.22-1 (universe) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1913567/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1913567] Re: Sync puppet 5.5.22-1 (universe) from Debian unstable (main)
Backport to Focal available at https://launchpad.net/~brightbox/+archive/ubuntu/experimental -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1913567 Title: Sync puppet 5.5.22-1 (universe) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1913567/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1913567] [NEW] Sync puppet 5.5.22-1 (universe) from Debian unstable (main)
Public bug reported: Please sync puppet 5.5.22-1 (universe) from Debian unstable (main) Explanation of the Ubuntu delta and why it can be dropped: * d/t/control: fix second dep8 test by telling it to not use a proxy for the "puppet" hostname, and allow stderr because of a ruby deprecation warning * d/t/control: fix second dep8 test by telling it to not use a proxy for the "puppet" hostname, and allow stderr because of a ruby deprecation warning * d/p/fix-ruby27-warning.patch: Add patch to fix a warning when executed with Ruby 2.7. It fixes an autopkgtest regression in ruby-puppet-syntax. * d/t/control: Add allow-stderr restriction to puppet master and puppet master passenger tests. * d/t/control: add 'puppet' to $no_proxy variable in puppet-master-passenger test to let tests make requests to puppet master running locally (LP: #1869265). * d/p/fix-ruby27-warning.patch: Add patch to fix a warning when executed with Ruby 2.7. It fixes an autopkgtest regression in ruby-puppet-syntax. * d/t/control: Add allow-stderr restriction to puppet master and puppet master passenger tests. * d/t/control: add 'puppet' to $no_proxy variable in puppet-master-passenger test to let tests make requests to puppet master running locally (LP: #1869265). * Revert: - Revert the Ubuntu delta. No changes left. + DEP8 tests fail in the Ubuntu autopkgtest environment without the delta. * d/t/control: fix incorrect merge in 5.4.0-2ubuntu1: - Wrong test was generating the certificate. - Wrong tests were being run for puppet-master-passenger. * Revert: - Revert the Ubuntu delta. No changes left. + DEP8 tests fail in the Ubuntu autopkgtest environment without the delta. * d/t/control: fix incorrect merge in 5.4.0-2ubuntu1: - Wrong test was generating the certificate. - Wrong tests were being run for puppet-master-passenger. * Revert: - Revert the Ubuntu delta. No changes left. + DEP8 tests fail in the Ubuntu autopkgtest environment without the delta. * d/t/control: fix incorrect merge in 5.4.0-2ubuntu1: - Wrong test was generating the certificate. - Wrong tests were being run for puppet-master-passenger. * Revert: - Revert the Ubuntu delta. No changes left. + DEP8 tests fail in the Ubuntu autopkgtest environment without the delta. * d/t/control: fix incorrect merge in 5.4.0-2ubuntu1: - Wrong test was generating the certificate. - Wrong tests were being run for puppet-master-passenger. * Revert: - Revert the Ubuntu delta. No changes left. + DEP8 tests fail in the Ubuntu autopkgtest environment without the delta. * d/t/control: fix incorrect merge in 5.4.0-2ubuntu1: - Wrong test was generating the certificate. - Wrong tests were being run for puppet-master-passenger. * Revert: - Revert the Ubuntu delta. No changes left. + DEP8 tests fail in the Ubuntu autopkgtest environment without the delta. * d/t/control: fix incorrect merge in 5.4.0-2ubuntu1: - Wrong test was generating the certificate. - Wrong tests were being run for puppet-master-passenger. * Fix duplicate oids, cherrypick upstream patch for OpenSSL 1.1 compat. * debian/patches/ruby2.3.6_compat.patch: SSL behavior changed in ruby 2.3.6. * Merge with Debian unstable (LP: #1702578). Remaining changes: - d/t/control: disable sysv-init tests as it does not exist on Ubuntu. - d/t/spec/puppet-master-passenger/zz_puppet3_compat_spec.rb: specify to curl that 'puppet' should not be proxied. - d/t/control: generate a certificate for puppet master if it does not already exist, as it is needed by the tests. * Drop: - d/p/0005-use-systemd-as-the-default-service-provider.path: also make systemd the default provider on Ubuntu. [ Fixed in Debian 4.10.4-1 ] * Merge with Debian unstable (LP: #1702578). Remaining changes: - d/t/control: disable sysv-init tests as it does not exist on Ubuntu. - d/t/spec/puppet-master-passenger/zz_puppet3_compat_spec.rb: specify to curl that 'puppet' should not be proxied. - d/t/control: generate a certificate for puppet master if it does not already exist, as it is needed by the tests. * Drop: - d/p/0005-use-systemd-as-the-default-service-provider.path: also make systemd the default provider on Ubuntu. [ Fixed in Debian 4.10.4-1 ] * Merge with Debian unstable. Remaining changes: - d/p/0005-use-systemd-as-the-default-service-provider.path: also make systemd the default provider on Ubuntu. - d/t/control: disable sysv-init tests as it does not exist on Ubuntu. - d/t/spec/puppet-master-passenger/zz_puppet3_compat_spec.rb: specify to curl that 'puppet' should not be proxied. - d/t/control: generate a certificate for puppet master if it does not already exist, as it is needed by the tests.
[Bug 1913557] Re: Please merge 5.5.22-1 into hirsute
** Changed in: puppet (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/1913557 Title: Please merge 5.5.22-1 into hirsute To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1913557/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1913557] [NEW] Please merge 5.5.22-1 into hirsute
Public bug reported: tracking bug ** Affects: puppet (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/1913557 Title: Please merge 5.5.22-1 into hirsute To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1913557/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1913466] Re: puppet gem provider fails in Focal
ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: puppet 5.5.10-4ubuntu3 ProcVersionSignature: User Name 5.4.0-62.70-generic 5.4.78 Uname: Linux 5.4.0-62-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Jan 27 17:11:14 2021 PackageArchitecture: all SourcePackage: puppet UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1913466 Title: puppet gem provider fails in Focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1913466/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1913467] [NEW] puppet throws numerous ruby warnings on Focal
*** This bug is a duplicate of bug 1875848 *** https://bugs.launchpad.net/bugs/1875848 Public bug reported: The puppet 5.5 version available in Focal throws a lot of ruby warnings, which interferes with the puppet installation traces. remote: /usr/lib/ruby/vendor_ruby/puppet/util.rb:461: warning: URI.escape is obsolete remote: /usr/lib/ruby/vendor_ruby/puppet/file_system/uniquefile.rb:126: warning: $SAFE will become a normal global variable in Ruby 3.0 remote: /usr/lib/ruby/vendor_ruby/puppet/util.rb:315: warning: deprecated Object#=~ is called on Puppet::Transaction::Report; it always returns nil emote: /usr/lib/ruby/vendor_ruby/puppet/type/cron.rb:160: warning: deprecated Object#=~ is called on Integer; it always returns nil ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: puppet 5.5.10-4ubuntu3 ProcVersionSignature: User Name 5.4.0-62.70-generic 5.4.78 Uname: Linux 5.4.0-62-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Jan 27 17:11:14 2021 PackageArchitecture: all SourcePackage: puppet UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: puppet (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal uec-images ** This bug has been marked a duplicate of bug 1875848 Ruby warnings on puppet run on Focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1913467 Title: puppet throws numerous ruby warnings on Focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1913467/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1913466] [NEW] puppet gem provider fails in Focal
Public bug reported: remote: ^[[1;31mError: Execution of '/usr/bin/gem install --no-rdoc --no-ri uricp' returned 1: ERROR: While executing gem ... (OptionParser::InvalidOption) remote: invalid option: --no-rdoc remote: Did you mean? no-force^[[0m remote: ^[[1;31mError: /Stage[main]/Mys_service/Package[uricp]/ensure: change from 'absent' to 'present' failed: Execution of '/usr/bin/gem install --no-rdoc --no-ri uricp' returned 1: ERROR: While executing gem ... (OptionParser::InvalidOption) remote: invalid option: --no-rdoc remote: Did you mean? no-force^[[0m The puppet 5.5 version available in the Focal archives tries to use '--no-rdoc' on a gem install, which is not supported by the Ruby 2.7 gem program installed by Focal. ** Affects: puppet (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/1913466 Title: puppet gem provider fails in Focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1913466/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1797390] Re: Update to 8.9.15
Debian just updated to 8.12.16 and its bug was closed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1797390 Title: Update to 8.9.15 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libphonenumber/+bug/1797390/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877687] Re: grub installation failed! I'm new in ubuntu and I was trying to install ubuntu alongside of my windows 10. :\
I'm lost but the install hasn't worked -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877687 Title: grub installation failed! I'm new in ubuntu and I was trying to install ubuntu alongside of my windows 10. :\ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1877687/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1910945] Re: can't upgrade from 19.10
Thanks Chris. I checked further on support sites. One suggested redirecting sources (sources.list) from Eoan to "...old-releases.ubuntu...", which I did and allowed me to upgrade to 20.04 (albeit the desktop still says 19.10). I'll see what happens when I try next upgrade. If it's too messy, I'll just do a fresh install. Thanks again for your prompt response. kind regardsNeil On Monday, 11 January 2021, 3:10:48 pm AEDT, Chris Guiver <1910...@bugs.launchpad.net> wrote: This comment is not bug related (but off-topic support). For help in ensuring you packages are fully upgraded; refer to https://help.ubuntu.com/community/EOLUpgrades I don't have access to an eoan/19.10 system, and online package databases are gone (having been EOL too now long), so I can't look up to see if packages are 3rd party or Ubuntu repositories, so I'll just suggest you 'upgrade via re-install'. You can install using "Manual Partitioning", select your existing partition(s) and as long as you don't format, the installer will - note your packages, - erase system directories (user configs for Lubuntu are stored in $HOME or user directory), - install system, - attempt to add-back additional packages you had install (if available in Ubuntu repositories for the new release) - then ask to reboot. Even if you get a warning that some packages could not be restored (this can occur for numerous reasons, eg. a dropped package as it relied on python2, Qt4 or like deprecated toolkit for example), the warning is rarely of concern. If you have any support questions, I'll also provide the Lubuntu links page https://lubuntu.me/links/ (you may find me there too) -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1910945 Title: can't upgrade from 19.10 Status in ubuntu-release-upgrader package in Ubuntu: Incomplete Bug description: similar to #934371 but even less detail. Was running "sudo do-release-upgrade" result "Calculating the changes Calculating the changes Could not calculate the upgrade An unresolvable problem occurred while calculating the upgrade. If none of this applies, then please report this bug using the command 'ubuntu-bug ubuntu-release-upgrader-core' in a terminal. If you want to investigate this yourself the log files in '/var/log/dist-upgrade' will contain details about the upgrade. Specifically, look at 'main.log' and 'apt.log'. Restoring original system state Aborting Reading package lists... Done Building dependency tree Reading state information... Done" ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: ubuntu-release-upgrader-core 1:19.10.15.4 [origin: unknown] ProcVersionSignature: Ubuntu 5.3.0-64.58-generic 5.3.18 Uname: Linux 5.3.0-64-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.9 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: LXQt Date: Mon Jan 11 14:14:40 2021 InstallationDate: Installed on 2020-02-15 (331 days ago) InstallationMedia: Lubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017.1) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to eoan on 2021-01-11 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1910945/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1910945 Title: can't upgrade from 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1910945/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1910945] [NEW] can't upgrade from 19.10
Public bug reported: similar to #934371 but even less detail. Was running "sudo do-release-upgrade" result "Calculating the changes Calculating the changes Could not calculate the upgrade An unresolvable problem occurred while calculating the upgrade. If none of this applies, then please report this bug using the command 'ubuntu-bug ubuntu-release-upgrader-core' in a terminal. If you want to investigate this yourself the log files in '/var/log/dist-upgrade' will contain details about the upgrade. Specifically, look at 'main.log' and 'apt.log'. Restoring original system state Aborting Reading package lists... Done Building dependency tree Reading state information... Done" ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: ubuntu-release-upgrader-core 1:19.10.15.4 [origin: unknown] ProcVersionSignature: Ubuntu 5.3.0-64.58-generic 5.3.18 Uname: Linux 5.3.0-64-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.9 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: LXQt Date: Mon Jan 11 14:14:40 2021 InstallationDate: Installed on 2020-02-15 (331 days ago) InstallationMedia: Lubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017.1) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to eoan on 2021-01-11 (0 days ago) ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: amd64 apport-bug dist-upgrade eoan third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1910945 Title: can't upgrade from 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1910945/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895342] Re: Acer Aspire E15 keyboard and trackpad non functional after update to vmlinuz-5.4.0-47-generic
Problem seems to have resolved itself at 5.4.0-58 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895342 Title: Acer Aspire E15 keyboard and trackpad non functional after update to vmlinuz-5.4.0-47-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895342/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908060] [NEW] Touchpad does not work when resuming from standby
Public bug reported: I have a Lenovo t440. The touchpad works fine from boot. However when resuming from standby, occasionally the touchpad will stop responding to any input. The keyboard still works fine. It has only happened since upgrading to 20.04. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-xorg-input-libinput 0.29.0-1 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Dec 14 12:01:47 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu InstallationDate: Installed on 2019-04-18 (605 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: LENOVO 20B60061UK ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic root=UUID=532ed0d4-eb00-46ad-aaba-e988531e342c ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-input-libinput UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/03/2017 dmi.bios.vendor: LENOVO dmi.bios.version: GJET92WW (2.42 ) dmi.board.asset.tag: Not Available dmi.board.name: 20B60061UK dmi.board.vendor: LENOVO dmi.board.version: 0B98401 PRO dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGJET92WW(2.42):bd03/03/2017:svnLENOVO:pn20B60061UK:pvrThinkPadT440:rvnLENOVO:rn20B60061UK:rvr0B98401PRO:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T440 dmi.product.name: 20B60061UK dmi.product.sku: LENOVO_MT_20B6_BU_Think_FM_ThinkPad T440 dmi.product.version: ThinkPad T440 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xserver-xorg-input-libinput (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908060 Title: Touchpad does not work when resuming from standby To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-libinput/+bug/1908060/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895422] Re: Sound card not detected on Dell Latitude 9510 (Realtek ALC711)
Has anyone put together a step-by-step tutorial (written or video), to give a little detailed direction to these steps? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895422 Title: Sound card not detected on Dell Latitude 9510 (Realtek ALC711) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1895422/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1837326] Re: platform eisa.0: EISA: Cannot allocate resource for mainboard
Same: uname -a Linux … 5.4.0-54-generic #60-Ubuntu SMP Fri Nov 6 10:37:59 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1837326 Title: platform eisa.0: EISA: Cannot allocate resource for mainboard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1837326/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874194] Re: Ubuntu 20.04 HDMI connected, no boot
*** This bug is a duplicate of bug 1872159 *** https://bugs.launchpad.net/bugs/1872159 Same bug affects me, I'm running 20.04 on an Asus Zenbook and can confirm that removing "quiet splash" DOES NOT resolve the boot issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874194 Title: Ubuntu 20.04 HDMI connected, no boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874194/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901600] [NEW] installer crashes when installing in virtualbox
Public bug reported: Installing Ubuntu in Virtualbox crashes 1/2 way through the install. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: ubiquity 20.10.13 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.455 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 26 15:48:35 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) ProcEnviron: LANGUAGE=en_CA.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.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 groovy ubiquity-20.10.13 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901600 Title: installer crashes when installing in virtualbox To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1901600/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898152] Re: upgrade fails to calculate if gnuradio-dev is installed
Having not had any success with removing gnuradio, I tried removing other things, including the PPAs I had removed before (I was aiming to make one change at a tie to pin down the issue). It turns out that I had a non-Ubunutu standard versions of sane and some associated libraries. When I forced the version to be the one in bionic-update I was able to update successfully. Thanks for the assistance. As always when one find the solution one wonders why one did not do that first :-( -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898152 Title: upgrade fails to calculate if gnuradio-dev is installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1898152/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899157] [NEW] package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1
*** This bug is a duplicate of bug 1897747 *** https://bugs.launchpad.net/bugs/1897747 Public bug reported: Upgrading 18.04 to 20.04 failed ProblemType: Package DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6.3 ProcVersionSignature: hostname 4.15.0-111.112-generic 4.15.18 Uname: Linux 4.15.0-111-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_4_15_0_111_112_generic_71 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Oct 9 11:42:12 2020 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2015-12-11 (1763 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: initramfs-tools Title: package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2020-10-09 (0 days ago) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899157 Title: package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1899157/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898152] Re: upgrade fails to calculate if gnuradio-dev is installed
Thanks for the suggestion. I did a complete removal of gnuradio-dev using synaptic package manager, and then tried doing an upgrade. Unfortunately I got the same result. I then did a complete removal of gnuradio, and all installed libgnuradio packages (they were 3.7.11-10, if that is any use). I then tried a tried doing an upgrade. Unfortunately I got the same result. I then did sudo apt-get autoremove from the command line. The following packages were removed: The following packages will be REMOVED: libcodec2-0.7 libcomedi0 liblog4cpp5v5 libqt5designer5 libqt5help5 libqwt-qt5-6 librtlsdr0 libuhd003.010.003 libvolk1-bin libvolk1-dev libvolk1.3 python-backports.functools-lru-cache python-certifi python-cheetah python-cycler python-dateutil python-decorator python-gobject python-matplotlib python-networkx python-olefile python-opengl python-pil python-pyparsing python-pyqt5 python-requests python-scipy python-sip python-subprocess32 python-tz python-urllib3 python-yaml python-zmq rtl-sdr uhd-host I then tried a tried doing an upgrade. Unfortunately I got the same result. So, it looks like gnuradio-dev is not the only culprit. Any further suggestions welcome! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898152 Title: upgrade fails to calculate if gnuradio-dev is installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1898152/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898152] Re: upgrade fails
Looks like a duplicate of Bug #1875523 and Bug #1875599. Problem seems to be with python-is-python2 / python-minimal: 2020-10-03 08:28:12,888 INFO installing python-is-python2 because python-minimal was installed 2020-10-03 08:28:12,889 DEBUG Installing 'python-is-python2' (python-minimal was installed on the system) 2020-10-03 08:28:42,073 ERROR Dist-upgrade failed: 'E:Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.' -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898152 Title: upgrade fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1898152/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898152] [NEW] upgrade fails
Public bug reported: Fails complaining about possible issue with PPAs. When these are removed fails with no complaints about PPAs or anything else. Just asks for bug to be reported. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.38 ProcVersionSignature: Ubuntu 4.15.0-118.119-generic 4.15.18 Uname: Linux 4.15.0-118-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Fri Oct 2 17:14:41 2020 InstallationDate: Installed on 2016-09-07 (1485 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to bionic on 2020-10-02 (0 days ago) VarLogDistupgradeTermlog: ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic dist-upgrade third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898152 Title: upgrade fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1898152/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895342] [NEW] Acer Aspire E15 keyboard and trackpad non functional after update to vmlinuz-5.4.0-47-generic
Public bug reported: Have an Acer Aspire E15 running Kubuntu 20.04 Expect: Trackpad and keyboard to work after boot to WM login. What Happens: Trackpad/keyboard unresponsive after WM starts. Recently ( within last month) an update has caused the trackpad and keyboard to stop being detected after the WM starts and autologin is complete. Ive reinstalled which puts me at vmlinuz-5.4.0-26-generic, and the trackpad/keyboard worked normally. After updating to vmlinuz-5.4.0-47-generic and rebooting problem reoccurs. Booting to console: keyboard works normally. Booting via Ubuntu advanced options to 5.4.0-26: Keyboard/trackpad works normally. Some Fn buttons work after login, but only ones monitored by firmware (E.g. screen brightness works, volume control doesn't) neil@neil-Aspire-E5-511:~$ lsb_release -rd Description:Ubuntu 20.04.1 LTS Release:20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-26-generic 5.4.0-26.30 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: neil943 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Fri Sep 11 19:20:04 2020 InstallationDate: Installed on 2020-09-10 (1 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Acer Aspire E5-511 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-26-generic root=UUID=7c62eb69-2b7c-4aea-a384-1460d6533ecd ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-26-generic N/A linux-backports-modules-5.4.0-26-generic N/A linux-firmware1.187.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/09/2015 dmi.bios.vendor: Acer dmi.bios.version: V1.10 dmi.board.name: Aspire E5-511 dmi.board.vendor: Acer dmi.board.version: V1.10 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAcer:bvrV1.10:bd09/09/2015:svnAcer:pnAspireE5-511:pvrV1.10:rvnAcer:rnAspireE5-511:rvrV1.10:cvnAcer:ct10:cvrChassisVersion: dmi.product.family: Bay Trail-M System dmi.product.name: Aspire E5-511 dmi.product.sku: Aspire E5-511_0905_V1.10 dmi.product.version: V1.10 dmi.sys.vendor: Acer ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895342 Title: Acer Aspire E15 keyboard and trackpad non functional after update to vmlinuz-5.4.0-47-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895342/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892422] Re: Pci passthrough interface not showing up in Ubuntu 20.04 but does show in 18.04
Details from working guest 18.04 $ lsmod Module Size Used by isofs 45056 0 nls_iso8859_1 16384 1 kvm_intel 217088 0 kvm 614400 1 kvm_intel irqbypass 16384 1 kvm crct10dif_pclmul 16384 0 crc32_pclmul 16384 0 ghash_clmulni_intel16384 0 input_leds 16384 0 joydev 24576 0 serio_raw 16384 0 sch_fq_codel 20480 6 ib_iser49152 0 rdma_cm61440 1 ib_iser iw_cm 45056 1 rdma_cm ib_cm 53248 1 rdma_cm ib_core 221184 4 rdma_cm,iw_cm,ib_iser,ib_cm iscsi_tcp 20480 0 libiscsi_tcp 20480 1 iscsi_tcp libiscsi 53248 3 libiscsi_tcp,iscsi_tcp,ib_iser scsi_transport_iscsi98304 3 iscsi_tcp,ib_iser,libiscsi ip_tables 28672 0 x_tables 40960 1 ip_tables autofs440960 2 btrfs1150976 0 zstd_compress 163840 1 btrfs raid10 53248 0 raid456 147456 0 async_raid6_recov 20480 1 raid456 async_memcpy 16384 2 raid456,async_raid6_recov async_pq 16384 2 raid456,async_raid6_recov async_xor 16384 3 async_pq,raid456,async_raid6_recov async_tx 16384 5 async_pq,async_memcpy,async_xor,raid456,async_raid6_recov xor24576 2 async_xor,btrfs raid6_pq 114688 4 async_pq,btrfs,raid456,async_raid6_recov libcrc32c 16384 1 raid456 raid1 40960 0 raid0 20480 0 multipath 16384 0 linear 16384 0 hid_generic16384 0 usbhid 49152 0 hid 118784 2 usbhid,hid_generic virtio_net 49152 0 aesni_intel 188416 0 aes_x86_64 20480 1 aesni_intel crypto_simd16384 1 aesni_intel cryptd 24576 3 crypto_simd,ghash_clmulni_intel,aesni_intel glue_helper16384 1 aesni_intel virtio_blk 20480 3 psmouse 151552 0 floppy 77824 0 i40evf 98304 0 $ lspci -v 00:00.0 Host bridge: Intel Corporation 440FX - 82441FX PMC [Natoma] (rev 02) Subsystem: Red Hat, Inc. Qemu virtual machine Flags: fast devsel 00:01.0 ISA bridge: Intel Corporation 82371SB PIIX3 ISA [Natoma/Triton II] Subsystem: Red Hat, Inc. Qemu virtual machine Flags: medium devsel 00:01.1 IDE interface: Intel Corporation 82371SB PIIX3 IDE [Natoma/Triton II] (prog-if 80 [ISA Compatibility mode-only controller, supports bus mastering]) Subsystem: Red Hat, Inc. Qemu virtual machine Flags: bus master, medium devsel, latency 0 [virtual] Memory at 01f0 (32-bit, non-prefetchable) [size=8] [virtual] Memory at 03f0 (type 3, non-prefetchable) [virtual] Memory at 0170 (32-bit, non-prefetchable) [size=8] [virtual] Memory at 0370 (type 3, non-prefetchable) I/O ports at c0e0 [size=16] Kernel driver in use: ata_piix 00:01.3 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ACPI (rev 03) Subsystem: Red Hat, Inc. Qemu virtual machine Flags: medium devsel, IRQ 9 00:02.0 VGA compatible controller: Cirrus Logic GD 5446 (prog-if 00 [VGA controller]) Subsystem: Red Hat, Inc. QEMU Virtual Machine Flags: fast devsel Memory at fc00 (32-bit, prefetchable) [size=32M] Memory at feb9 (32-bit, non-prefetchable) [size=4K] Expansion ROM at 000c [disabled] [size=128K] Kernel modules: cirrusfb 00:03.0 Ethernet controller: Red Hat, Inc. Virtio network device Subsystem: Red Hat, Inc. Virtio network device Physical Slot: 3 Flags: bus master, fast devsel, latency 0, IRQ 11 I/O ports at c040 [size=32] Memory at feb91000 (32-bit, non-prefetchable) [size=4K] Memory at fe01 (64-bit, prefetchable) [size=16K] Expansion ROM at feb0 [disabled] [size=512K] Capabilities: [98] MSI-X: Enable+ Count=3 Masked- Capabilities: [84] Vendor Specific Information: VirtIO: Capabilities: [70] Vendor Specific Information: VirtIO: Notify Capabilities: [60] Vendor Specific Information: VirtIO: DeviceCfg Capabilities: [50] Vendor Specific Information: VirtIO: ISR Capabilities: [40] Vendor Specific Information: VirtIO: CommonCfg Kernel driver in use: virtio-pci 00:04.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 (rev 03) (prog-if 00 [UHCI]) Subsystem: Red Hat, Inc. QEMU Virtual Machine Flags: bus master, fast devsel, latency 0, IRQ 11 I/O ports at c060 [size=32] Kernel driver in use: uhci_hcd 00:04.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 (re
[Bug 1892422] Re: Pci passthrough interface not showing up in Ubuntu 20.04 but does show in 18.04
Hi Christian As you pointed out this does appear to be an issue with the reduced kernel kvm image. I ran the same setup using a standard image and the interface showed up. However after running your suggested updates from comment A on the kvm kernal image, the interface still did not show up. If I bring up the guest using a generic image (not the kvm specific kernal) the interface appears for SRIOV VF Linux emsk8sm1 5.4.0-47-generic #51-Ubuntu SMP Fri Sep 4 19:50:52 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux $ ip add 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: ens3: mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether 52:54:00:8a:9c:ea brd ff:ff:ff:ff:ff:ff inet 192.168.50.243/22 brd 192.168.51.255 scope global ens3 valid_lft forever preferred_lft forever inet6 fe80::5054:ff:fe8a:9cea/64 scope link valid_lft forever preferred_lft forever 3: ens6: mtu 1500 qdisc mq state UP group default qlen 1000 link/ether e2:7e:67:02:77:11 brd ff:ff:ff:ff:ff:ff inet 10.72.2.21/22 brd 10.72.3.255 scope global ens6 valid_lft forever preferred_lft forever inet6 fe80::e07e:67ff:fe02:7711/64 scope link valid_lft forever preferred_lft forever This is the output from Linux 5.4.0-1020-kvm before any updates to linux-image $ ip add 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: ens3: mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 52:54:00:8a:9c:ea brd ff:ff:ff:ff:ff:ff inet 192.168.50.243/22 brd 192.168.51.255 scope global ens3 valid_lft forever preferred_lft forever inet6 fe80::5054:ff:fe8a:9cea/64 scope link valid_lft forever preferred_lft forever 3: tunl0@NONE: mtu 1480 qdisc noop state DOWN group default qlen 1000 link/ipip 0.0.0.0 brd 0.0.0.0 4: sit0@NONE: mtu 1480 qdisc noop state DOWN group default qlen 1000 link/sit 0.0.0.0 brd 0.0.0.0 $ lsmod Module Size Used by loop 28672 6 nls_utf8 12288 0 nls_iso8859_1 12288 1 nls_cp437 16384 1 vfat 16384 1 fat57344 1 vfat dm_multipath 20480 0 dm_mod 86016 2 dm_multipath kvm_intel 176128 0 pata_acpi 12288 0 ip_tables 20480 0 x_tables 24576 1 ip_tables $ lspci -v 00:00.0 Host bridge: Intel Corporation 440FX - 82441FX PMC [Natoma] (rev 02) Subsystem: Red Hat, Inc. Qemu virtual machine Flags: fast devsel 00:01.0 ISA bridge: Intel Corporation 82371SB PIIX3 ISA [Natoma/Triton II] Subsystem: Red Hat, Inc. Qemu virtual machine Flags: medium devsel 00:01.1 IDE interface: Intel Corporation 82371SB PIIX3 IDE [Natoma/Triton II] (prog-if 80 [ISA Compatibility mode-only controller, supports bus mastering]) Subsystem: Red Hat, Inc. Qemu virtual machine Flags: bus master, medium devsel, latency 0 Memory at 01f0 (32-bit, non-prefetchable) [virtual] [size=8] Memory at 03f0 (type 3, non-prefetchable) [virtual] Memory at 0170 (32-bit, non-prefetchable) [virtual] [size=8] Memory at 0370 (type 3, non-prefetchable) [virtual] I/O ports at c0e0 [virtual] [size=16] Kernel driver in use: ata_piix Kernel modules: pata_acpi 00:01.3 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ACPI (rev 03) Subsystem: Red Hat, Inc. Qemu virtual machine Flags: medium devsel, IRQ 9 00:02.0 VGA compatible controller: Cirrus Logic GD 5446 (prog-if 00 [VGA controller]) Subsystem: Red Hat, Inc. QEMU Virtual Machine Flags: fast devsel Memory at fc00 (32-bit, prefetchable) [size=32M] Memory at feb9 (32-bit, non-prefetchable) [size=4K] Expansion ROM at 000c [disabled] [size=128K] 00:03.0 Ethernet controller: Red Hat, Inc. Virtio network device Subsystem: Red Hat, Inc. Virtio network device Physical Slot: 3 Flags: bus master, fast devsel, latency 0, IRQ 11 I/O ports at c040 [size=32] Memory at feb91000 (32-bit, non-prefetchable) [size=4K] Memory at fe01 (64-bit, prefetchable) [size=16K] Expansion ROM at feb0 [disabled] [size=512K] Capabilities: Kernel driver in use: virtio-pci 00:04.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 (rev 03) (prog-if 00 [UHCI])
[Bug 1882774] Re: issues with secondary VMX execution controls
Thanks to everyone who contributed to this fix. I confirm that it works for me in testing with Ussuri and Ubuntu Bionic on vmx-enabled GCP VMs; with fixed qemu packages coming from cloud-archive:ussuri. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882774 Title: issues with secondary VMX execution controls To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1882774/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892422] [NEW] Pci passthrough interface not showing up in Ubuntu 20.04 but does show in 18.04
Public bug reported: After setting up pci pass through for a virtual function it did not show up as an interface in Ubuntu 20.04, it did however show up as a PCI device. After reverting back to 18.04 with exactly the same configuration the interface showed up as expected. Bellow is the configuration and output for both 18.04 and 20.04. virt-install --import --connect qemu:///system --name emsk8sm1 --ram 8192 --disk pool/emsk8sm1/emsk8sm1.img,format=img,bus=virtio --disk cidata.img,device=cdrom,format=img --vcpus 4 --cpu host --os-type linux --os-variant ubuntu18.04 --network bridge=br0,model=virtio,virtualport_type=openvswitch,mac=52:54:00:8a:9c:ea --hostdev 3b:02.5 --console pty,target_type=serial --graphics type=vnc,listen=0.0.0.0 --noautoconsole --autostart -v Configuration of 18.04 where the passthrough works Version Linux emsk8sm1 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:41:39 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux virsh dumpxml emsk8sm1 lspci | grep Ethernet 00:03.0 Ethernet controller: Red Hat, Inc. Virtio network device 00:06.0 Ethernet controller: Intel Corporation Ethernet Virtual Function 700 Series (rev 02) <--- Pass through interface ip link show [interface shows inside of vm ens6] 1: lo: mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: ens3: mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000 link/ether 52:54:00:8a:9c:ea brd ff:ff:ff:ff:ff:ff 3: ens6: mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 1000 link/ether ea:99:ea:36:3e:63 brd ff:ff:ff:ff:ff:ff Configuration of 20.04 where the VF shows as a PCI device but does not show as an interface Version Linux emsk8sm1 5.4.0-1020-kvm #20-Ubuntu SMP Fri Jul 10 05:03:04 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux virsh dumpxml emsk8sm1 lspci | grep Ethernet 00:03.0 Ethernet controller: Red Hat, Inc. Virtio network device 00:06.0 Ethernet controller: Intel Corporation Ethernet Virtual Function 700 Series (rev 02) <--- Pass through interface ip link show [ens 6 does not show as an interface} 1: lo: mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: ens3: mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000 link/ether 52:54:00:8a:9c:ea brd ff:ff:ff:ff:ff:ff 3: tunl0@NONE: mtu 1480 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/ipip 0.0.0.0 brd 0.0.0.0 4: sit0@NONE: mtu 1480 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/sit 0.0.0.0 brd 0.0.0.0 ** Affects: linux-meta (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/1892422 Title: Pci passthrough interface not showing up in Ubuntu 20.04 but does show in 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1892422/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1889314] [NEW] feature request: bionic autoinstall
Public bug reported: Would you please make autoinstall work in bionic? Thanks in advance. ** Affects: subiquity (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/1889314 Title: feature request: bionic autoinstall To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/1889314/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879710] Re: pam_pkcs11 unable to process CRL's
This is fixed with the following patch: https://github.com/OpenSC/pam_pkcs11/pull/45 It looks like OpenSSL 1.1.0 handling for CRL's hadn't been implemented in cert_vfy.c -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879710 Title: pam_pkcs11 unable to process CRL's To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/opensc/+bug/1879710/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879710] Re: pam_pkcs11 unable to process CRL's
Hi, see attachment pam_pkcs11.conf - it's pretty much the generic 0.4 package demo file with some small changes. Below I've pasted the ls/cat outputs for other files in the pam_pkcs11 folder /etc/pam_pkcs11$ cat subject_mapping /DC=com/DC=removedforsecurity/DC=xxx/OU=xxxx/CN=Neil xxx -> neil /CN=Neilxxxx -> neil /etc/pam_pkcs11/crls$ ls -l total 8 -rw-r--r-- 1 root root 934 May 20 14:12 crl1.crl -rw-r--r-- 1 root root 652 May 14 19:12 crlrevlist.crl lrwxrwxrwx 1 root root 8 May 20 14:14 d283dc31.r0 -> crl1.crl lrwxrwxrwx 1 root root 14 May 20 14:14 d283dc31.r1 -> crlrevlist.crl /etc/pam_pkcs11/cacerts$ ls -l total 4 lrwxrwxrwx 1 root root 16 May 19 13:47 d283dc31.0 -> nmwcacertb64.cer -rw-r--r-- 1 root root 1261 May 19 13:46 nmwcacertb64.cer ** Attachment added: "pam_pkcs11.conf" https://bugs.launchpad.net/ubuntu/+source/opensc/+bug/1879710/+attachment/5395682/+files/pam_pkcs11.conf -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879710 Title: pam_pkcs11 unable to process CRL's To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/opensc/+bug/1879710/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1765946] Re: Solaar tray icon not visible
Confirming no icon in sys tray on upgrade from Mint 19.3 to 20. Blank space where icon should be and the solaar menu when that space is left clicked. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1765946 Title: Solaar tray icon not visible To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/solaar/+bug/1765946/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851552] Re: since ubuntu 18 bionic release and latest, the ubuntu18 cloud image is unable to boot up on openstack instance
I don't believe this is to do with networking-calico, so will mark as Invalid for networking-calico. ** Changed in: networking-calico Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851552 Title: since ubuntu 18 bionic release and latest, the ubuntu18 cloud image is unable to boot up on openstack instance To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1851552/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856485] Re: ERROR neutron.manager [-] Plugin 'calico' not found.
Python 3 support was added in Calico v3.15 https://docs.projectcalico.org/release-notes/#v3150 The master networking-calico code now supports Python 3, and no longer Python 2. There is a 'release-v3.15-python2' branch that still supports Python 2, but we are hoping that maintenance of that branch can now be short-lived. ** Changed in: networking-calico 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/1856485 Title: ERROR neutron.manager [-] Plugin 'calico' not found. To manage notifications about this bug go to: https://bugs.launchpad.net/networking-calico/+bug/1856485/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882867] [NEW] package lightdm 1.30.0-0ubuntu3.1 failed to install/upgrade: installed lightdm package pre-removal script subprocess returned error exit status 10
Public bug reported: I also had a login loop. nothing unusual with my install - just upgrading packages. Nothing custom. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: lightdm 1.30.0-0ubuntu3.1 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 AptOrdering: slick-greeter:amd64: Remove lightdm:amd64: Remove NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Jun 4 23:43:52 2020 ErrorMessage: installed lightdm package pre-removal script subprocess returned error exit status 10 InstallationDate: Installed on 2020-05-18 (22 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.3 SourcePackage: lightdm Title: package lightdm 1.30.0-0ubuntu3.1 failed to install/upgrade: installed lightdm package pre-removal script subprocess returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882867 Title: package lightdm 1.30.0-0ubuntu3.1 failed to install/upgrade: installed lightdm package pre-removal script subprocess returned error exit status 10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1882867/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882774] Re: issues with secondary VMX execution controls
Christian, would it be easy for you to build this for Bionic as well? I run tests with GCP instances as the OpenStack hypervisors, and have hit this bug, so am keen to test your fix. (http://lists.openstack.org/pipermail/openstack- discuss/2020-June/015343.html) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882774 Title: issues with secondary VMX execution controls To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1882774/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872452] Re: [amdgpu] Boot into black screen without power supply (Kubuntu on AMD)
I've managed to get the system to boot when not plugged into mains by adding 'iommu=soft' to the linux line in grub. Not sure at what cost but at least I don't lose my display info like when nomodeset is used. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872452 Title: [amdgpu] Boot into black screen without power supply (Kubuntu on AMD) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kwin/+bug/1872452/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872452] Re: [amdgpu] Boot into black screen without power supply (Kubuntu on AMD)
Just to provide a source, I got it from here (where it seems other people have the same issue): https://askubuntu.com/questions/1206472/ubuntu-18-04-and-20-04-stuck-on- gnome-startup-on-battery-only -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872452 Title: [amdgpu] Boot into black screen without power supply (Kubuntu on AMD) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kwin/+bug/1872452/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879710] Re: pam_pkcs11 unable to process CRL's
Wrong package initially selected ** Package changed: coolkey (Ubuntu) => opensc (Ubuntu) ** Information type changed from Private Security to Public Security -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879710 Title: pam_pkcs11 unable to process CRL's To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/opensc/+bug/1879710/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872452] Re: [amdgpu] Boot into black screen without power supply (Kubuntu on AMD / Thinkpad T495)
This affects me too - Ubuntu MATE 20.04, Lenovo T495 (so AMD graphics/amdgpu). Boots fine with power supply connected, but running from battery, laptop POSTs ok, displays grub, displays boot msgs but then screen goes blank. Happy to provide logs if you let me know what you need, I can SSH into the laptop to retrieve whatever is required. Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872452 Title: [amdgpu] Boot into black screen without power supply (Kubuntu on AMD / Thinkpad T495) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kwin/+bug/1872452/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866657] Re: Long window titles cause graphical corruption in title bar
** Also affects: mate-desktop via https://github.com/mate-desktop/marco/issues/595 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/1866657 Title: Long window titles cause graphical corruption in title bar To manage notifications about this bug go to: https://bugs.launchpad.net/mate-desktop/+bug/1866657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866974] Re: The Diffie-Hellman prime sent by the server is not acceptable
*** This bug is a duplicate of bug 1872778 *** https://bugs.launchpad.net/bugs/1872778 Want to add my thanks as well Simon, I'm still getting a warning abut a wildcard cert, but it's at least functional now! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866974 Title: The Diffie-Hellman prime sent by the server is not acceptable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1866974/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873794] Re: Unattended upgrades fixes missing from security repo
If the fix is not in the security pocket, how does it get sorted if the updates pocket is turned off? I understood *-updates are only supposed to be recommended. As I mentioned if you build an image with a tool like 'mkosi' which utilises debootstrap and then cleans the cache, the partial directory is missing in the resulting image. Under the Debian file system layout /var is supposed to be volatile. You can't rely on anything being there. -- 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/1873794 Title: Unattended upgrades fixes missing from security repo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1873794/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871926] [NEW] marco crashed with SIGSEGV in cairo_region_num_rectangles()
Public bug reported: The "System Problem Detected" dialog appeared after I closed a game. I did not notice any problem. I note the error message is the same as in https://bugs.launchpad.net/ubuntu/+source/marco/+bug/1863392 but I'm using the "fix-released" package. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: marco 1.24.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu24 Architecture: amd64 CurrentDesktop: MATE Date: Thu Apr 9 22:03:26 2020 ExecutablePath: /usr/bin/marco InstallationDate: Installed on 2019-10-11 (181 days ago) InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20190926.2) ProcCmdline: marco ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f9b1c0ee9d4 : mov 0x4(%rdi),%eax PC (0x7f9b1c0ee9d4) ok source "0x4(%rdi)" (0x0025) not located in a known VMA region (needed readable region)! destination "%eax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: marco StacktraceTop: cairo_region_num_rectangles () at /lib/x86_64-linux-gnu/libcairo.so.2 () at /lib/x86_64-linux-gnu/libmarco-private.so.2 () at /lib/x86_64-linux-gnu/libmarco-private.so.2 () at /lib/x86_64-linux-gnu/libmarco-private.so.2 () at /lib/x86_64-linux-gnu/libmarco-private.so.2 Title: marco crashed with SIGSEGV in cairo_region_num_rectangles() UpgradeStatus: Upgraded to focal on 2020-02-07 (62 days ago) UserGroups: adm audio cdrom dip lpadmin lxd plugdev sambashare sudo separator: ** Affects: marco (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash focal need-amd64-retrace ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871926 Title: marco crashed with SIGSEGV in cairo_region_num_rectangles() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/marco/+bug/1871926/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871716] [NEW] marco crashed with SIGSEGV in meta_frame_calc_borders()
Public bug reported: I was confronted with the System Error dialog when closing a game. I hadn't noticed anything wrong. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: marco 1.24.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 CrashCounter: 1 CurrentDesktop: MATE Date: Wed Apr 8 21:37:04 2020 ExecutablePath: /usr/bin/marco InstallationDate: Installed on 2020-03-20 (19 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Alpha amd64 (20200320) ProcCmdline: marco ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f7cdaf52364 : mov (%rdi),%rax PC (0x7f7cdaf52364) ok source "(%rdi)" (0x004b9b68) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: marco StacktraceTop: meta_frame_calc_borders () from /lib/x86_64-linux-gnu/libmarco-private.so.2 ?? () from /lib/x86_64-linux-gnu/libmarco-private.so.2 ?? () from /lib/x86_64-linux-gnu/libmarco-private.so.2 ?? () from /lib/x86_64-linux-gnu/libmarco-private.so.2 ?? () from /lib/x86_64-linux-gnu/libmarco-private.so.2 Title: marco crashed with SIGSEGV in meta_frame_calc_borders() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm lpadmin lxd plugdev sambashare sudo separator: ** Affects: marco (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash focal need-amd64-retrace ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871716 Title: marco crashed with SIGSEGV in meta_frame_calc_borders() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/marco/+bug/1871716/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866974] Re: The Diffie-Hellman prime sent by the server is not acceptable
I've recently begun using `evolution-ews` from the Ubuntu 19.10 repository and it's been working brilliantly. I've now attempted to do the same on a fresh Ubuntu 20.04 beta install and can no longer use the plugin to fetch my emails, as I get a TLS/SSL error. I'm using it on an NHS email account with the server URL as `https://mail.nhs.net/ews/exchange.asmx` but when I add my email account I get an error message ``` SSL/TLS certificate for "mail.nhs.net" is not trusted. Do you wish to accept it? ``` The certificate is for *.nhs.net so should be valid, I also get a reported error "Error perfroming TLS handshake. The Diffie-Hellman prime sent by the server is not acceptable (not long enough) If I try to `Accept Permanently` the pop up box continues to reappear. ``` *.nhs.net Identity: *.nhs.net Verified by: GlobalSign RSA OV SSL CA 2018 Expires: 14/03/21 ``` ## On Ubuntu 19.10 (Working) ``` neil@thinkpad:~$ apt search evolution Sorting... Done Full Text Search... Done evolution/eoan,now 3.34.1-2 amd64 [installed] groupware suite with mail client and organizer neil@thinkpad:~$ apt search evolution-ews Sorting... Done Full Text Search... Done evolution-ews/eoan,now 3.34.1-1 amd64 [installed] Exchange Web Services integration for Evolution ``` ## On Ubuntu 20.04 (Error) ``` neil@thinkpad:~$ apt search evolution Sorting... Done Full Text Search... Done evolution/focal,now 3.36.1-1 amd64 [installed] groupware suite with mail client and organizer neil@thinkpad:~$ apt search evolution-ews Sorting... Done Full Text Search... Done evolution-ews/focal,now 3.36.1-1 amd64 [installed] Exchange Web Services integration for Evolution ``` -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866974 Title: The Diffie-Hellman prime sent by the server is not acceptable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1866974/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870381] [NEW] marco crashed with signal 5
Public bug reported: I was confronted by the "System problem detected" dialog on logging in. I didn't notice anything abnormal. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: marco 1.24.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CrashCounter: 1 CurrentDesktop: MATE Date: Thu Apr 2 16:37:23 2020 ExecutablePath: /usr/bin/marco InstallationDate: Installed on 2019-10-11 (173 days ago) InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20190926.2) ProcCmdline: marco --replace --composite ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash Signal: 5 SourcePackage: marco StacktraceTop: () at /lib/x86_64-linux-gnu/libX11.so.6 () at /lib/x86_64-linux-gnu/libX11.so.6 _XReply () at /lib/x86_64-linux-gnu/libX11.so.6 XSync () at /lib/x86_64-linux-gnu/libX11.so.6 () at /lib/x86_64-linux-gnu/libgdk-3.so.0 Title: marco crashed with signal 5 UpgradeStatus: Upgraded to focal on 2020-02-07 (55 days ago) UserGroups: adm audio cdrom dip lpadmin lxd plugdev sambashare sudo separator: ** Affects: marco (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash focal need-amd64-retrace ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870381 Title: marco crashed with signal 5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/marco/+bug/1870381/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869475] Re: Window shrinks and menu disappears when other app is opened/closed to the dock
Here's a little video clip. I've logged out of telegram for privacy reasons (and it doesn't minimise to the dock when logged out) but you can see the effect just by opening the app. ** Attachment added: "shrinking_terminal.mp4" https://bugs.launchpad.net/ubuntu/+source/marco/+bug/1869475/+attachment/5342552/+files/shrinking_terminal.mp4 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869475 Title: Window shrinks and menu disappears when other app is opened/closed to the dock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/marco/+bug/1869475/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
