Re: [Bug 2072976] Re: back_perl no longer loads (file not found)
Looks like 619afaccab5cedae6ec78bd627aa8399010c54d3 introduced a typo on the second "for opt in" line. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2072976 Title: back_perl no longer loads (file not found) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/2072976/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061728] Re: Apps don't launch from GNOME Software
I was able to resolve this by following the instructions on this page :
https://etbe.coker.com.au/2024/04/24/ubuntu-24-04-bubblewrap/
Basically create the file /etc/apparmor.d/bwrap with the following
contents :
abi ,
include
profile bwrap /usr/bin/bwrap flags=(unconfined) {
userns,
# Site-specific additions and overrides. See local/README for details.
include if exists
}
and execute 'systemctl reload apparmor'
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2061728
Title:
Apps don't launch from GNOME Software
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/2061728/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2070282] [NEW] When clicking the title bar (single click) the window goes to its small state
Public bug reported: Im pretty sure this is related to this extension (Only started happening since the upgrade to Ubuntu 24.04). It does not happen on a window such as Files, But will happen on for example chrome Steps to replicate 1. Open chrome 2. Maximise the window 3. Single click somewhere in the titlebar where there isnt a tab 4. Observe the window getting smaller I have also observed big orage hint boxes appearing (As if its try to do some sort of tiling) No LSB modules are available. Description:Ubuntu 24.04 LTS Release:24.04 ** Affects: gnome-shell-extension-tiling-assistant (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/2070282 Title: When clicking the title bar (single click) the window goes to its small state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-tiling-assistant/+bug/2070282/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069461] Re: AppArmor profiles missing in kernel 5.15 on jammy
Problem was mis-identified. Appropriate source for FIPS has changed leading to the use of an outdated kernel in testing. This issue can be closed without action ** Changed in: livecd-rootfs (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069461 Title: AppArmor profiles missing in kernel 5.15 on jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2069461/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069461] [NEW] AppArmor profiles missing in kernel 5.15 on jammy
Public bug reported: Upcoming Ubuntu Jammy FIPS images will be using the 5.15 kernel. During our pre-publication testing the public cloud team noticed failures in our snap_preseed_optimized test which checks to ensure that snaps are preseeded correctly. This test checks the output of `snap debug seeding` to assert `seed- completion` is present and not empty. `` ❯ snap debug seeding seeded: true preseeded: true image-preseeding: 39.367s seed-completion: 1.335s ``` If `/var/lib/snapd/seed/seed.yaml` exists it also asserts that `preseeded` is present and not empty. With the 5.15 kernel this test is failing which indicates a kernel feature mismatch between the running kernel and the feature set hard-coded in livecd-rootfs for this image. Boot will be slowed by ~200ms until this is resolved in livecd-rootfs. This solution is to add a 5.15 apparmor configuration to the jammy branch of livecd-rootfs [ Impact ] Boot will be slowed by ~200ms until this is resolved in livecd-rootfs [ Test Plan ] * for jammy build any cloud image with preseeded snaps with up to date 5.15 kernel (ec2-pro-fips builds prompted this) * boot * run `snap debug seeding` * assert the test described above passes [ Where problems could occur ] * If these changes do not resolve the preseeding issue, then a feature mismatch will remain as will the ~200ms boot delay. This will require further iteration, but no degradation is expected [ Other Info ] ** Affects: livecd-rootfs (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/2069461 Title: AppArmor profiles missing in kernel 5.15 on jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2069461/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063381] Re: NFS Client can't mount via NFS version 4.0
The proposed pkg fixes my issue! nfs-common/focal-proposed,now 1:1.3.4-2.5ubuntu3.7 amd64 [installed] Installed from proposed repo. Mounted via pam_mount upon ssh login using krb5p; NFSv4 successful mount with vers=4.0 which I could not do before upgrading from focal-updates 1:1.3.4-2.5ubuntu3.6 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063381 Title: NFS Client can't mount via NFS version 4.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/2063381/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059197] Re: mount.nfs: Fix minor version parsing when '-t nfs4' and '-o vers=4.x' are used together
This fixes my issue! https://bugs.launchpad.net/ubuntu/+source/util- linux/+bug/2063381 nfs-common/focal-proposed,now 1:1.3.4-2.5ubuntu3.7 amd64 [installed] Installed from proposed repo. Mounted via pam_mount upon ssh login using krb5p; NFSv4 successful mount with vers=4.0 which I could not do before upgrading from focal-updates 1:1.3.4-2.5ubuntu3.6 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059197 Title: mount.nfs: Fix minor version parsing when '-t nfs4' and '-o vers=4.x' are used together To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/2059197/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063381] Re: NFS Client can't mount via NFS version 4.0
Andreas, Thanks for the information! Much appreciated, I did not find that bug in my searches for NFS related things. Will definitely give this new package a try later today on our test server, thanks again! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063381 Title: NFS Client can't mount via NFS version 4.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/2063381/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063381] Re: NFS Client can't mount via NFS version 4.0
** Description changed: When specifying vers=4.0 or nfsvers=4.0 in NFSv4 mount options, the client ends up using version 4.2 instead. This option seems to be ignored. This happens with pam_mount and manual mount. We have been using pam_mount for years with the option vers=4.0, but now it appears to be broken. Just recently noticed this is happening while troubleshooting root causes of some other issues on our servers. - Test: mounting manually with option: minorversion=0, the client does not mount, no errors are seen with -vvv, no errors in logs either, it just fails silently. - With pam_mount this option fails as well but is logged as mount failed into auth.log + Test: mounting manually with option: minorversion=0, the client does not mount, no errors are seen with -vvv, no errors in logs either, it just fails silently. + With pam_mount this option fails as well but is logged as mount failed into auth.log ex: Apr 24 17:15:22 servername sshd[666278]: (pam_mount.c:522): mount of /mnt/nfs/home/admin_username failed - I see that something similar was fixed in autofs, but this is not autofs - related. https://bugs.launchpad.net/bugs/1818121 + other nfs4 mount options we are using: + sec=krb5p,noatime,nodiratime,async + + + I see that something similar was fixed in autofs, but this is not autofs related, as we do not use it. https://bugs.launchpad.net/bugs/1818121 Found a similar [oracle] issue but cannot read it= https://support.oracle.com/knowledge/Oracle%20Linux%20and%20Virtualization/2528012_1.html --- Description:Ubuntu 20.04.6 LTS Release:20.04 --- util-linux: - Installed: 2.34-0.1ubuntu9.6 - Candidate: 2.34-0.1ubuntu9.6 - Version table: - *** 2.34-0.1ubuntu9.6 500 - 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages - 500 http://us.archive.ubuntu.com/ubuntu focal-security/main amd64 Packages - 100 /var/lib/dpkg/status - 2.34-0.1ubuntu9 500 - 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages - + Installed: 2.34-0.1ubuntu9.6 + Candidate: 2.34-0.1ubuntu9.6 + Version table: + *** 2.34-0.1ubuntu9.6 500 + 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages + 500 http://us.archive.ubuntu.com/ubuntu focal-security/main amd64 Packages + 100 /var/lib/dpkg/status + 2.34-0.1ubuntu9 500 + 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages mount: - Installed: 2.34-0.1ubuntu9.6 - Candidate: 2.34-0.1ubuntu9.6 - Version table: - *** 2.34-0.1ubuntu9.6 500 - 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages - 500 http://us.archive.ubuntu.com/ubuntu focal-security/main amd64 Packages - 100 /var/lib/dpkg/status - 2.34-0.1ubuntu9 500 - 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages - + Installed: 2.34-0.1ubuntu9.6 + Candidate: 2.34-0.1ubuntu9.6 + Version table: + *** 2.34-0.1ubuntu9.6 500 + 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages + 500 http://us.archive.ubuntu.com/ubuntu focal-security/main amd64 Packages + 100 /var/lib/dpkg/status + 2.34-0.1ubuntu9 500 + 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages nfs-common: - Installed: 1:1.3.4-2.5ubuntu3.6 - Candidate: 1:1.3.4-2.5ubuntu3.6 - Version table: - *** 1:1.3.4-2.5ubuntu3.6 500 - 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages - 100 /var/lib/dpkg/status - 1:1.3.4-2.5ubuntu3.3 500 - 500 http://us.archive.ubuntu.com/ubuntu focal-security/main amd64 Packages - 1:1.3.4-2.5ubuntu3 500 - 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages + Installed: 1:1.3.4-2.5ubuntu3.6 + Candidate: 1:1.3.4-2.5ubuntu3.6 + Version table: + *** 1:1.3.4-2.5ubuntu3.6 500 + 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages + 100 /var/lib/dpkg/status + 1:1.3.4-2.5ubuntu3.3 500 + 500 http://us.archive.ubuntu.com/ubuntu focal-security/main amd64 Packages + 1:1.3.4-2.5ubuntu3 500 + 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063381 Title: NFS Client can't mount via NFS version 4.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/2063381/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063381] [NEW] NFS Client can't mount via NFS version 4.0
Public bug reported: When specifying vers=4.0 or nfsvers=4.0 in NFSv4 mount options, the client ends up using version 4.2 instead. This option seems to be ignored. This happens with pam_mount and manual mount. We have been using pam_mount for years with the option vers=4.0, but now it appears to be broken. Just recently noticed this is happening while troubleshooting root causes of some other issues on our servers. Test: mounting manually with option: minorversion=0, the client does not mount, no errors are seen with -vvv, no errors in logs either, it just fails silently. With pam_mount this option fails as well but is logged as mount failed into auth.log ex: Apr 24 17:15:22 servername sshd[666278]: (pam_mount.c:522): mount of /mnt/nfs/home/admin_username failed I see that something similar was fixed in autofs, but this is not autofs related. https://bugs.launchpad.net/bugs/1818121 Found a similar [oracle] issue but cannot read it= https://support.oracle.com/knowledge/Oracle%20Linux%20and%20Virtualization/2528012_1.html --- Description:Ubuntu 20.04.6 LTS Release:20.04 --- util-linux: Installed: 2.34-0.1ubuntu9.6 Candidate: 2.34-0.1ubuntu9.6 Version table: *** 2.34-0.1ubuntu9.6 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu focal-security/main amd64 Packages 100 /var/lib/dpkg/status 2.34-0.1ubuntu9 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages mount: Installed: 2.34-0.1ubuntu9.6 Candidate: 2.34-0.1ubuntu9.6 Version table: *** 2.34-0.1ubuntu9.6 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu focal-security/main amd64 Packages 100 /var/lib/dpkg/status 2.34-0.1ubuntu9 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages nfs-common: Installed: 1:1.3.4-2.5ubuntu3.6 Candidate: 1:1.3.4-2.5ubuntu3.6 Version table: *** 1:1.3.4-2.5ubuntu3.6 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:1.3.4-2.5ubuntu3.3 500 500 http://us.archive.ubuntu.com/ubuntu focal-security/main amd64 Packages 1:1.3.4-2.5ubuntu3 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages ** Affects: util-linux (Ubuntu) Importance: Undecided Status: New ** Tags: mount nfs ** Package changed: autofs (Ubuntu) => util-linux (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063381 Title: NFS Client can't mount via NFS version 4.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/2063381/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059847] Re: Input lag or freezes on Nvidia desktops with X11 after logging "MetaSyncRing: Sync object is not ready -- were events handled properly?"
Thanks - this fix appears to have resolved my lag issues. OS: Ubuntu 22.04.04 LTS $XDG_SESSION_TYPE: x11 nVidia: 535.171.04 Mobo/CPU: MSI MAG B550M BAZOOKA / AMD Ryzen 5 5600X Video card: MSI GeForce GT1030 2GB PCI Express Mostly this was affecting Gnome terminal for me, but just prior to applying this patch (thanks again!!) I used GnuCash and that lagged too. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059847 Title: Input lag or freezes on Nvidia desktops with X11 after logging "MetaSyncRing: Sync object is not ready -- were events handled properly?" To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2059847/+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
I am also seeing this issue on baremetal (Intel NUC), Hyper-V, and LXD VM attempting to connect via RDP from a Windows 11 computer. I was able to capture the following error coming from gnome-shell logs after initiating an RDP connection: JS ERROR: TypeError: this._button is undefined _createSessionMenuButton@resource:///org/gnome/shell/gdm/loginDialog.js:663:13 _init@resource:///org/gnome/shell/gdm/loginDialog.js:589:14 LoginDialog@resource:///org/gnome/shell/gdm/loginDialog.js:487:4 _ensureUnlockDialog@resource:///org/gnome/shell/ui/screenShield.js:472:28 showDialog@resource:///org/gnome/shell/ui/screenShield.js:404:14 _initializeUI/<@resource:///org/gnome/shell/ui/main.js:317:26 _prepareStartupAnimation@resource:///org/gnome/shell/ui/layout.js:764:18 _loadBackground/signalIdhttps://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2061364/+attachment/5765719/+files/Screenshot%202024-04-15%20114510.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 2060578] Re: postfix installed during release upgrade to Noble
We see this in AWS VMs as well on do-release-upgrades with the same prompt/output/etc as describe by Catherine -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060578 Title: postfix installed during release upgrade to Noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2060578/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059350] Re: xfsrestore places all files restored from xfsdump into orphanage directory; root ino differs from mount dir ino
Downloaded the package from noble, which didn't have any unsatisfied dependencies on jammy thankfully. This works fine: root@media:~# xfsdump -J - /photos | xfsrestore - /photos_new xfsdump: using file dump (drive_simple) strategy xfsrestore: using file dump (drive_simple) strategy xfsdump: version 3.1.11 (dump format 3.0) xfsrestore: version 3.1.11 (dump format 3.0)xfsdump: level 0 dump of media:/photos xfsdump: dump date: Wed Mar 27 19:40:51 2024 xfsdump: session id: f85ee60c-3c31-4de5-840d-5b9bae3fd440 xfsdump: session label: "" xfsrestore: searching media for dump xfsdump: ino map phase 1: constructing initial dump list xfsdump: ino map phase 2: skipping (no pruning necessary) xfsdump: ino map phase 3: skipping (only one dump stream) xfsdump: ino map construction complete xfsdump: estimated dump size: 238203138624 bytes xfsdump: creating dump session media file 0 (media 0, file 0) xfsdump: dumping ino map xfsdump: dumping directories xfsrestore: examining media file 0 xfsrestore: dump description: xfsrestore: hostname: media xfsrestore: mount point: /photos xfsrestore: volume: /dev/mapper/vg--array-photos xfsrestore: session time: Wed Mar 27 19:40:51 2024 xfsrestore: level: 0 xfsrestore: session label: "" xfsrestore: media label: "" xfsrestore: file system id: 023a8f91-eb50-4887-8c9e-5e5cb8d2aeb5 xfsrestore: session id: f85ee60c-3c31-4de5-840d-5b9bae3fd440 xfsrestore: media id: 2a268b0a-d3c3-40f0-b811-356e9f7fa837 xfsrestore: searching media for directory dump xfsrestore: reading directories xfsdump: dumping non-directory files xfsrestore: 62746 directories and 221364 entries processed xfsrestore: directory post-processing xfsrestore: restoring non-directory files ...it's humming right along. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059350 Title: xfsrestore places all files restored from xfsdump into orphanage directory; root ino differs from mount dir ino To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfsdump/+bug/2059350/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059350] [NEW] xfsrestore places all files restored from xfsdump into orphanage directory; root ino differs from mount dir ino
Public bug reported: I am attempting to use xfsdump/xfsrestore piped together to rewrite my XFS filesystems for version 5 compatibility. This worked fine for two filesystems so far, 20G and 500G. The latest 300G filesystem I'm trying to rewrite does not work. See below (I interrupted it; it would continue on like that). To my relatively untrained eye, this appears to be this problem: https://access.redhat.com/solutions/6601461 ...but I don't see any bug for that in Ubuntu. It also does not mention xfsdump/xfsrestore version 3.1.9, only 3.1.8 and 3.1.10, so I don't know for sure that this is affected. There's not much information out there in general. Is there a workaround or a fix pending? These filesystems were probably written with Ubuntu 18.04 or earlier (I just recently did a fresh install, replacing Ubuntu 18.04 with Xubuntu 22.04, but I did run as early as 14.04 on this machine at one point, if I recall) -- the 2019 creation dates on the filesystem suggest that that's correct. This is a fully up-to-date freshly installed copy of Xubuntu 22.04.4. root@media:/home/ryanov# xfsdump -J - /photos | xfsrestore - /photos_new xfsdump: using file dump (drive_simple) strategy xfsrestore: using file dump (drive_simple) strategy xfsdump: version 3.1.9 (dump format 3.0) xfsrestore: version 3.1.9 (dump format 3.0) xfsrestore: searching media for dump xfsdump: level 0 dump of media:/photos xfsdump: dump date: Wed Mar 27 19:28:27 2024 xfsdump: session id: 6e04ecba-d6c2-4722-b325-169861233403 xfsdump: session label: "" xfsdump: NOTE: root ino 64 differs from mount dir ino 128, bind mount? xfsdump: ino map phase 1: constructing initial dump list xfsdump: ino map phase 2: skipping (no pruning necessary) xfsdump: ino map phase 3: skipping (only one dump stream) xfsdump: ino map construction complete xfsdump: estimated dump size: 238203138624 bytes xfsdump: creating dump session media file 0 (media 0, file 0) xfsdump: dumping ino map xfsdump: dumping directories xfsrestore: examining media file 0 xfsrestore: dump description: xfsrestore: hostname: media xfsrestore: mount point: /photos xfsrestore: volume: /dev/mapper/vg--array-photos xfsrestore: session time: Wed Mar 27 19:28:27 2024 xfsrestore: level: 0 xfsrestore: session label: "" xfsrestore: media label: "" xfsrestore: file system id: 023a8f91-eb50-4887-8c9e-5e5cb8d2aeb5 xfsrestore: session id: 6e04ecba-d6c2-4722-b325-169861233403 xfsrestore: media id: bcfbb01f-6bfb-4605-8c66-4284dd52612a xfsrestore: searching media for directory dump xfsrestore: reading directories xfsdump: dumping non-directory files xfsrestore: 62746 directories and 221364 entries processed xfsrestore: directory post-processing xfsrestore: restoring non-directory files xfsrestore: NOTE: ino 64 salvaging file, placing in orphanage/128.0/184.JPG xfsrestore: NOTE: ino 69 salvaging file, placing in orphanage/128.0/DIAphoto1.JPG xfsrestore: NOTE: ino 70 salvaging file, placing in orphanage/128.0/DIAphoto2.JPG xfsrestore: NOTE: ino 71 salvaging file, placing in orphanage/128.0/DIAphoto3.JPG xfsrestore: NOTE: ino 72 salvaging file, placing in orphanage/128.0/HelenSullivanID.png xfsrestore: NOTE: ino 73 salvaging file, placing in orphanage/128.0/IMAG0653.jpg xfsrestore: NOTE: ino 74 salvaging file, placing in orphanage/128.0/IMG_2354.JPG xfsrestore: NOTE: ino 75 salvaging file, placing in orphanage/128.0/PRE_2011-08-04-145222.jpg xfsrestore: NOTE: ino 76 salvaging file, placing in orphanage/128.0/Part 1.3 xfsrestore: NOTE: ino 77 salvaging file, placing in orphanage/128.0/Part 1.5 xfsrestore: NOTE: ino 78 salvaging file, placing in orphanage/128.0/Part 1.7 xfsrestore: NOTE: ino 79 salvaging file, placing in orphanage/128.0/Pic.JPG xfsrestore: NOTE: ino 80 salvaging file, placing in orphanage/128.0/RHEAV6789.jpg xfsrestore: NOTE: ino 81 salvaging file, placing in orphanage/128.0/RyanDeanGaryColleen.png xfsrestore: NOTE: ino 82 salvaging file, placing in orphanage/128.0/RyanDrew-PhotoBooth.png xfsrestore: NOTE: ino 83 salvaging file, placing in orphanage/128.0/RyanMomDeanHelenStella.png xfsrestore: NOTE: ino 84 salvaging file, placing in orphanage/128.0/Screenshot from 2015-02-02 11:05:14.png xfsrestore: NOTE: ino 85 salvaging file, placing in orphanage/128.0/Screenshot from 2015-02-04 14:24:07.png xfsrestore: NOTE: ino 86 salvaging file, placing in orphanage/128.0/Screenshot from 2015-05-05 20:31:23.png xfsrestore: NOTE: ino 87 salvaging file, placing in orphanage/128.0/Screenshot from 2015-07-29 12:02:40.png xfsrestore: NOTE: ino 88 salvaging file, placing in orphanage/128.0/alpaca.JPG xfsrestore: NOTE: ino 89 salvaging file, placing in orphanage/128.0/idscan.png xfsrestore: NOTE: ino 90 salvaging file, placing in orphanage/128.0/linkedin.png xfsrestore: NOTE: ino 91 salvaging file, placing in orphanage/128.0/obama inauguration --1.bmp xfsrestore: NOTE: ino 92 salvaging file, placing in orphanage/128.0/photo 2.JPG xfsrestore: NOTE: ino 93 salvaging file, placing in
[Bug 2055793] Re: [regression] Wine program crashes with unhandled page fault on startup
** Summary changed: - Wine program crashes with unhandled page fault on startup + [regression] Wine program crashes with unhandled page fault on startup -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055793 Title: [regression] Wine program crashes with unhandled page fault on startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2055793/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055793] [NEW] Wine program crashes with unhandled page fault on startup
Public bug reported: Today, APT Performed the following update: Start-Date: 2024-03-02 16:23:10 Commandline: aptdaemon role='role-commit-packages' sender=':1.304' Upgrade: tcpdump:amd64 (4.99.1-3ubuntu0.1, 4.99.1-3ubuntu0.2), libglx-mesa0:amd64 (23.0.4-0ubuntu1~22.04.1, 23.2.1-1ubuntu3.1~22.04.2), libglx-mesa0:i386 (23.0.4-0ubuntu1~22.04.1, 23.2.1-1ubuntu3.1~22.04.2), libgbm1:amd64 (23.0.4-0ubuntu1~22.04.1, 23.2.1-1ubuntu3.1~22.04.2), libgbm1:i386 (23.0.4-0ubuntu1~22.04.1, 23.2.1-1ubuntu3.1~22.04.2), firmware-sof-signed:amd64 (2.0-1ubuntu4.4, 2.0-1ubuntu4.5), gigolo:amd64 (0.5.2-1, 0.5.2-1ubuntu0.22.04.1), mesa-va-drivers:amd64 (23.0.4-0ubuntu1~22.04.1, 23.2.1-1ubuntu3.1~22.04.2), libgl1-mesa-dri:amd64 (23.0.4-0ubuntu1~22.04.1, 23.2.1-1ubuntu3.1~22.04.2), libgl1-mesa-dri:i386 (23.0.4-0ubuntu1~22.04.1, 23.2.1-1ubuntu3.1~22.04.2), libosmesa6:amd64 (23.0.4-0ubuntu1~22.04.1, 23.2.1-1ubuntu3.1~22.04.2), libosmesa6:i386 (23.0.4-0ubuntu1~22.04.1, 23.2.1-1ubuntu3.1~22.04.2), mesa-vulkan-drivers:amd64 (23.0.4-0ubuntu1~22.04.1, 23.2.1-1ubuntu3.1~22.04.2), mesa-vulkan-drivers:i386 (23.0.4-0ubuntu1~22.04.1, 23.2.1-1ubuntu3.1~22.04.2), libglapi-mesa:amd64 (23.0.4-0ubuntu1~22.04.1, 23.2.1-1ubuntu3.1~22.04.2), libglapi-mesa:i386 (23.0.4-0ubuntu1~22.04.1, 23.2.1-1ubuntu3.1~22.04.2), libegl-mesa0:amd64 (23.0.4-0ubuntu1~22.04.1, 23.2.1-1ubuntu3.1~22.04.2), mesa-vdpau-drivers:amd64 (23.0.4-0ubuntu1~22.04.1, 23.2.1-1ubuntu3.1~22.04.2) This update causes a problem when running a program via wine (6.0.3~repack-1) which I have run (under wine) for over 10 years. Dialog box error message: A program on your system has crashed, but WineDbg was unable to attach to the process to obtain a backtrace. [ OK ] Terminal error message: wine: Unhandled page fault on read access to at address (thread 0024), starting debugger... Can't attach process 0020: error 5 I reverted by installing the following packages: 8c1d0584ae15da9fa9006798e396280825cbc19b043c9fea34c605d05d10544a libegl-mesa0_23.0.4-0ubuntu1~22.04.1_amd64.deb 33da608ad1dd71ae0e181cc7d29425a3e76d3bc3d595644a4e424ce0065600a1 libgbm1_23.0.4-0ubuntu1~22.04.1_amd64.deb 409bfe746eadf276e85fd82023b87dc4361d6d537d43936b8f8922a2a8f9fdb4 libgbm1_23.0.4-0ubuntu1~22.04.1_i386.deb 8933615dda5ec6c8ddcdf61bf965a6c89fe27bb58257ddbeccf891fabf565bbc libgl1-mesa-dri_23.0.4-0ubuntu1~22.04.1_amd64.deb 7d83885adb22054ff0ba10a10dd014e2a9de22c6d27300aa835b01489c84c51a libgl1-mesa-dri_23.0.4-0ubuntu1~22.04.1_i386.deb c62aafcd439764e398be1684f47b265a9b6e8e84bc455b912ffd844d27f01a01 libglapi-mesa_23.0.4-0ubuntu1~22.04.1_amd64.deb 0485f51e4362795c823936ff955bc46b47677df8d3554ef3cabf850eea25126e libglapi-mesa_23.0.4-0ubuntu1~22.04.1_i386.deb a66c3572cbee38c2ddf7a001528ff2ee8221eade056f45d7607b878b4d976430 libglx-mesa0_23.0.4-0ubuntu1~22.04.1_amd64.deb 88d881ace0ce9b5d219984c9f6c76aabf381cfec3172225be0b3ef94030b35ad libglx-mesa0_23.0.4-0ubuntu1~22.04.1_i386.deb 2d2bb86103d52eb921003506e1ffc474aa29d24f5732ab5e8161aae9370abc7e libosmesa6_23.0.4-0ubuntu1~22.04.1_amd64.deb 48d1ca94af2e82f8074f66f21f29f19d7ea0cec21c9feb664415e92f3418adba libosmesa6_23.0.4-0ubuntu1~22.04.1_i386.deb Which gives the messages: dpkg: warning: downgrading libegl-mesa0:amd64 from 23.2.1-1ubuntu3.1~22.04.2 to 23.0.4-0ubuntu1~22.04.1 dpkg: warning: downgrading libgbm1:amd64 from 23.2.1-1ubuntu3.1~22.04.2 to 23.0.4-0ubuntu1~22.04.1 dpkg: warning: downgrading libgbm1:i386 from 23.2.1-1ubuntu3.1~22.04.2 to 23.0.4-0ubuntu1~22.04.1 dpkg: warning: downgrading libgl1-mesa-dri:amd64 from 23.2.1-1ubuntu3.1~22.04.2 to 23.0.4-0ubuntu1~22.04.1 dpkg: warning: downgrading libgl1-mesa-dri:i386 from 23.2.1-1ubuntu3.1~22.04.2 to 23.0.4-0ubuntu1~22.04.1 dpkg: warning: downgrading libglapi-mesa:amd64 from 23.2.1-1ubuntu3.1~22.04.2 to 23.0.4-0ubuntu1~22.04.1 dpkg: warning: downgrading libglapi-mesa:i386 from 23.2.1-1ubuntu3.1~22.04.2 to 23.0.4-0ubuntu1~22.04.1 dpkg: warning: downgrading libglx-mesa0:amd64 from 23.2.1-1ubuntu3.1~22.04.2 to 23.0.4-0ubuntu1~22.04.1 dpkg: warning: downgrading libglx-mesa0:i386 from 23.2.1-1ubuntu3.1~22.04.2 to 23.0.4-0ubuntu1~22.04.1 dpkg: warning: downgrading libosmesa6:amd64 from 23.2.1-1ubuntu3.1~22.04.2 to 23.0.4-0ubuntu1~22.04.1 dpkg: warning: downgrading libosmesa6:i386 from 23.2.1-1ubuntu3.1~22.04.2 to 23.0.4-0ubuntu1~22.04.1 After reverting, the software starts as normal (and, as expected, there is no error in the terminal). Release: Description: Ubuntu 22.04.4 LTS Release: 22.04 I am not sure exactly which package contains the bug, because these 11 packages upgrade together. The specific version diffs are shown above. One thing I noticed is that this seems to be a fairly large version increase (mesa 23.0.4 --> 23.2.1). If I could get all of the package versions between these two, then
[Bug 1971752] [NEW] Toggling F11 for fullscreen reduces the restored window size
Public bug reported: When I open a Gnome Terminal window at a given size (say 80 columns x 24 rows), press F11 to go full-screen, and then press F11 to restore the window to it's original size, it will be a bit smaller! It will lose both height and width. If I keep toggling with F11, the window will reduce to 3 lines and... I'm not sure exactly how many columns, but it's less than it had. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-terminal 3.44.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu May 5 18:03:50 2022 InstallationDate: Installed on 2022-04-26 (8 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971752 Title: Toggling F11 for fullscreen reduces the restored window size To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1971752/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970076] Re: "User process fault: interruption code 0011 ilc:3" on SSH client/server upon Jammy upgrade
I only have one s390x guest and adding another would be painful due to the slowness of its emulation :) but I have just tried removing all of /etc/ssh and reinstalling openssh-client/openssh-server, same crash. To be clear, this is only happening on my s390x guest. I have a few other non-x86 qemu guests (arm64, ppc64el, riscv64, etc) which have also been upgraded to jammy, none of which have this problem. So I'm willing to bet this is more of a kernel or qemu problem and that openssh is just a symptom. (Though it seems to be a recurring indicative symptom... ISTR openssh segfaults during the bootstrap of riscv64 on qemu; William Grant may be able to chime in.) I've attached my libvirt definition in case it's relevant, but it's pretty standard. ** Attachment added: "s390x-dev.xml" https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1970076/+attachment/5584015/+files/s390x-dev.xml -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970076 Title: "User process fault: interruption code 0011 ilc:3" on SSH client/server upon Jammy upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1970076/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970076] Re: "User process fault: interruption code 0011 ilc:3" on SSH client/server upon Jammy upgrade
** Tags added: apport-crash need-amd64-retrace ** Tags removed: need-amd64-retrace ** Tags added: need-s390x-retrace -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970076 Title: "User process fault: interruption code 0011 ilc:3" on SSH client/server upon Jammy upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1970076/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970076] [NEW] "User process fault: interruption code 0011 ilc:3" on SSH client/server upon Jammy upgrade
Public bug reported: This s390x VM has been upgraded to Jammy, including the host (qemu- system-s390x 1:6.2+dfsg-2ubuntu6). Now any attempt to use ssh, or any incoming sshd attempt immediately results in e.g.: ryan@s390x-dev:~$ ssh g...@github.com [ 433.672800] User process fault: interruption code 0011 ilc:3 in libc.so.6[3ffa6c0+1ca000] [ 433.672946] Failing address: 02aa0b84d000 TEID: 02aa0b84d800 [ 433.672977] Fault in primary space mode while using user ASCE. [ 433.673030] AS:02bc01c7 R3:087cc007 S:0798a000 P:0400 Segmentation fault (core dumped) ** Affects: openssh (Ubuntu) Importance: Undecided Status: New ** Tags: apport-crash jammy need-s390x-retrace qemu s390x ** Attachment added: "_usr_bin_ssh.1000.crash" https://bugs.launchpad.net/bugs/1970076/+attachment/5582994/+files/_usr_bin_ssh.1000.crash -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970076 Title: "User process fault: interruption code 0011 ilc:3" on SSH client/server upon Jammy upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1970076/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968627] [NEW] file saving dialog grows and grows with each additional file dialog
Public bug reported: This might be an issue with xdg-desktop-portal-gnome as well, I am using the Brave Browser and noticed this. I *think* it uses xdg-desktop- portal-gtk for the time being though. This is 22.04 Daily Build from April 9th updated. What happens: If you decide to save an image, the file save dialog pops up, provided by either xdg-desktop-portal-gtk or -gnome, this is fine. However, multiple instances of calling the file save dialog such as saving multiple images from a website will cause the dialog box to grow and grow every time it is called, leading to it stretching off the main screen onto my secondary (which is a portrait 1080x1920 monitor to the right of the main 2560x1440 monitor). This is super annoying because you never know where the window is going to appear, and at what size (well, I guess you do know that it is going to grow each time, but it is VERY inconsistent). I've attached a scaled down webm, in it I am downloading cat pictures from Google Image Search. For the first image, it shows how large it tends to get, and I resize it to a smaller size. Then, with each image that the dialog is brought up for, it grows and grows. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xdg-desktop-portal-gtk 1.14.0-1build1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Apr 11 15:39:25 2022 InstallationDate: Installed on 2022-04-09 (1 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220409) SourcePackage: xdg-desktop-portal-gtk UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: xdg-desktop-portal-gtk (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session ** Attachment added: "screen recording of the file save dialog bug" https://bugs.launchpad.net/bugs/1968627/+attachment/5579502/+files/output.webm -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968627 Title: file saving dialog grows and grows with each additional file dialog To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-gtk/+bug/1968627/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968451] [NEW] GNOME launcher folder icons and labels very small
Public bug reported: Ubuntu 22.04 Daily Build from April 9th The default Utilities folder in GNOME Shell applications launcher (the screen that shows when you hit Super twice) are extremely small/tiny. I haven't seen this with other versions of GNOME shell on other distros with this version of GNOME that I have tested, so it may be a Ubuntu specific issue. I've attached a screenshot of the "Utilities" folder as it existed by default after install, I did however change the icon theme to a few different ones before noticing, but it persisted after switching back to Yaru Icon Theme. I was able to get the normal behavior by dragging all the icons out one by one and recreating the folder, after which it appears normally. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Apr 9 21:11:51 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-04-09 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220409) RelatedPackageVersions: mutter-common 42.0-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session ** Attachment added: "Untitled.png" https://bugs.launchpad.net/bugs/1968451/+attachment/5578879/+files/Untitled.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968451 Title: GNOME launcher folder icons and labels very small To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1968451/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967951] Re: hotplug external monitor logs me out
I have been using Ubuntu 22.04 for several months, initially Ubuntu on wayland was working but at some point Ubuntu on wayland stopped working (It doesn't even show up as an option on the gdm3 login screen). I am mentioning this to preemptively say that: - Ubuntu on wayland is not working - Sway on wayland is working - I don't know why Ubuntu-wayland is not working. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967951 Title: hotplug external monitor logs me out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1967951/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967951] [NEW] hotplug external monitor logs me out
Public bug reported: Summary: When hotplugging an external monitor, I am sent immediately to the login screen. Actions: Boot my laptop either with or without the external plugged in and then log in to my user account. If the monitor is not plugged in, plug it in. Expected result: The monitor is detected and the previous monitor configurations are loaded. Actual result: When the monitor is detected, I am immediately sent to the login screen. On X, with either HDMI or usb c port: I need to log in again. The monitor is detected and functions as expected once I have logged in. On sway with HDMI: I can change to tty2 (where my sway session was started) and the monitor is detected and functions as expected. On sway with usb c: I cannot log in again. It is stuck in a log-in loop. Other info: Description:Ubuntu Jammy Jellyfish (development branch) Release:22.04 xserver-xorg-video-nouveau: Installed: 1:1.0.17-2build1 Candidate: 1:1.0.17-2build1 Version table: *** 1:1.0.17-2build1 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status Sway version 1.5.1 I have uninstalled all the propriety drivers. From the 'About Ubuntu' page, it seems that my Nvidia GPU is not in use. Laptop ASUS TUF A15 FA506IH ** Affects: xserver-xorg-video-nouveau (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/1967951 Title: hotplug external monitor logs me out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1967951/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871781] Re: gdk_drawing_context_get_cairo_context: assertion 'GDK_IS_DRAWING_CONTEXT (context)' failed Segmentation fault
Bug is still present in 20.04.4. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871781 Title: gdk_drawing_context_get_cairo_context: assertion 'GDK_IS_DRAWING_CONTEXT (context)' failed Segmentation fault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pgadmin3/+bug/1871781/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1724732] Re: Wayland login options are missing when a radeon card is installed
I am having a similar issue on Ubuntu 22.04 with Asus Tuf A15 FA605IH -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1724732 Title: Wayland login options are missing when a radeon card is installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1724732/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967034] [NEW] Window switcher only switches between current and previous window only
Public bug reported: Testing out Ubuntu Kylin 22.04 daily builds, I am unable to properly swap between more than two (2) windows. The window switcher switches to the previous window in the stack, but you cannot select any other window, or even go back to the first window without activating window- switch again. lsb_release -rd Description:Ubuntu Jammy Jellyfish (development branch) Release:22.04 ukui-window-switch package: 3.0.1-1 ProblemType: Bug DistroRelease: Ubuntu Kylin 22.04 Package: ukui-window-switch 3.0.1-1 [origin: Ubuntu] ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: UKUI Date: Tue Mar 29 20:29:59 2022 InstallationDate: Installed on 2022-03-30 (0 days ago) InstallationMedia: Ubuntu-Kylin 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) SourcePackage: ukui-window-switch UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ukui-window-switch (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy third-party-packages ** Description changed: - Testing out Ubuntu Kylin 22.04 daily builds, I am unable to swap between - more than two (2) windows. The window switcher switches back and forth - between the two (current and previous) but never lets you select other - windows by continuing to push Alt+Tab, in fact, you can only move to the - other window (no cancellation possible). This may or may not be related - to the fact that I have two screens, but I disabled the other screen and - still notice the behaviour. + Testing out Ubuntu Kylin 22.04 daily builds, I am unable to properly + swap between more than two (2) windows. The window switcher switches to + the previous window in the stack, but you cannot select any other + window, or even go back to the first window without activating window- + switch again. lsb_release -rd Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 - ukui-window-switch package: 3.0.1-1 ProblemType: Bug DistroRelease: Ubuntu Kylin 22.04 Package: ukui-window-switch 3.0.1-1 [origin: Ubuntu] ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: UKUI Date: Tue Mar 29 20:29:59 2022 InstallationDate: Installed on 2022-03-30 (0 days ago) InstallationMedia: Ubuntu-Kylin 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) SourcePackage: ukui-window-switch 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/1967034 Title: Window switcher only switches between current and previous window only To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ukui-window-switch/+bug/1967034/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966553] [NEW] cool-retro-term fails to start due to missing dependency
Public bug reported: On a fresh install of Jammy, the package "cool-retro-term" fails to start due to a missing dependency. This problem is completely mitigated if the package "qml-module-qtquick-controls2" is installed on the system prior to running the program. Release: Description:Ubuntu Jammy Jellyfish (development branch) Release:22.04 Package info: cool-retro-term: Installed: 1.2.0+ds-4 Candidate: 1.2.0+ds-4 Version table: *** 1.2.0+ds-4 500 500 http://us.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages 100 /var/lib/dpkg/status ml-module-qtquick-controls2: Installed: 5.15.2+dfsg-4 Candidate: 5.15.2+dfsg-4 Version table: *** 5.15.2+dfsg-4 500 500 http://us.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages 100 /var/lib/dpkg/status Expected behavior: Cool-retro-term starts when called from the launcher or command line Observed behavior: cool-retro-term fails silently when started from the launcher. When started from the command line, the following error is generated: :~$ cool-retro-term Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use QT_QPA_PLATFORM=wayland to run on Wayland anyway. QQmlApplicationEngine failed to load component qrc:/main.qml:22:1: plugin cannot be loaded for module "QtQuick.Controls": Cannot protect module QtQuick.Controls 2 as it was never registered Cannot load QML interface Behavior after corrective action: When above package is added to the system, the application launches correctly but still publishes warnings to the command line: :~$ cool-retro-term Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use QT_QPA_PLATFORM=wayland to run on Wayland anyway. Both point size and pixel size set. Using pixel size. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: cool-retro-term 1.2.0+ds-4 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Mar 26 12:26:17 2022 InstallationDate: Installed on 2022-03-26 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: cool-retro-term UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: cool-retro-term (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy 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/1966553 Title: cool-retro-term fails to start due to missing dependency To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cool-retro-term/+bug/1966553/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966156] [NEW] mpv stops updating video after resizing
Public bug reported: Ubuntu Jammy Jellyfish 22.04 pre-relase daily build Ratel Performance with Intel i7 3770 CPU and AMD RX 570 GPU mpv 0.34.1 Copyright © 2000-2021 mpv/MPlayer/mplayer2 projects built on UNKNOWN FFmpeg library versions: libavutil 56.70.100 libavcodec 58.134.100 libavformat 58.76.100 libswscale 5.9.100 libavfilter 7.110.100 libswresample 3.9.100 FFmpeg version: 4.4.1-3ubuntu5 Playing a video is fine, but when you resize it may or may not continue to work. It continues to play, complains about a few dropped frames, but in various videos I've tried (mkv from two sources, mp4 from two sources), it will get "stuck" on a certain frame and flash (bright and then dim, back and forth), while the audio continues to play. Seems to be related to audio, since if the movie is muted, the bug doesn't appear to show, but if you turn the audio back up the bug shows up again. Not sure if this is an issue with GNOME, mesa, or mpv itself, but I thought I'd report it in case it can be isolated and fixed. Doesn't appear to affect gnome-mpv or "Celluloid" which uses mpv as the backend. ** Affects: mpv (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/1966156 Title: mpv stops updating video after resizing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mpv/+bug/1966156/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959728] Re: trackpad doesn't work on Lenovo X1 Yoga Titanium after suspend/resume
Same system, same symptoms. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959728 Title: trackpad doesn't work on Lenovo X1 Yoga Titanium after suspend/resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1959728/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962012] [NEW] BERT: Error records from previous boot: Firmware Error Record Type: SOC Firmware Error Record Type2, Revision: 2, Record Identifier: 8f87f311-c998-4d9e-a0c4-6065518c4f6d while trai
Public bug reported: I was training a neural network on CPU using Tensorflow + Keras in Python. The crash happened twice in the same day after installing an update to Ubuntu. 1) Ubuntu 20.04.4 LTS 2) intel-microcode: Installed: 3.20210608.0ubuntu0.20.04.1 Candidate: 3.20210608.0ubuntu0.20.04.1 Version table: *** 3.20210608.0ubuntu0.20.04.1 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 100 /var/lib/dpkg/status 3.20191115.1ubuntu3 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages 3) Not crash. 4) Crash. Excerpt from /var/log/kern.log: BERT: Error records from previous boot: [Hardware Error]: event severity: fatal [Hardware Error]: Error 0, type: fatal [Hardware Error]: section_type: Firmware Error Record Reference [Hardware Error]: Firmware Error Record Type: SOC Firmware Error Record Type2 [Hardware Error]: Revision: 2 [Hardware Error]: Record Identifier: 8f87f311-c998-4d9e-a0c4-6065518c4f6d [Hardware Error]: : 0100c303 0280 04726ce2 002f .lr./... [Hardware Error]: 0010: 000a 0010 80001fff 0001f668 h... [Hardware Error]: 0020: 0001f664 000231c6 deadbeef deafbeef d1.. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: intel-microcode 3.20210608.0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Feb 23 09:32:56 2022 InstallationDate: Installed on 2021-11-23 (91 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: intel-microcode UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: intel-microcode (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/1962012 Title: BERT: Error records from previous boot: Firmware Error Record Type: SOC Firmware Error Record Type2, Revision: 2, Record Identifier: 8f87f311-c998-4d9e-a0c4-6065518c4f6d while training neural network on CPU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1962012/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961454] [NEW] [SRU] Package unusable due to yearly key changes
Public bug reported: [Impact] * ftp.ports.debian.org changes keys every year, and updates debian- ports-archive-keyring 2 years ahead of time. * Packages in bionic and focal do not have 2022's key, making the packages unusable. * SRU falls under "Updates that need to be applied to Ubuntu packages to adjust to changes in the environment, server protocols, web services, and similar" * Package can be synced directly from Debian [Test Plan] sudo debootstrap --arch=riscv64 --force-check-gpg --foreign --keyring=/usr/share/keyrings/debian-ports-archive-keyring.gpg sid /tmp/sid http://ftp.ports.debian.org/debian-ports/ Expected: I: Checking Release signature I: Valid Release signature (key id CBC70A60B9ED6F237A5F5B0BE852514F5DF312F6) I: Retrieving Packages I: Validating Packages I: Resolving dependencies of required packages... I: Resolving dependencies of base packages... [...] Currently: I: Checking Release signature E: Release signed by unknown key (key id E852514F5DF312F6) The specified keyring /usr/share/keyrings/debian-ports-archive-keyring.gpg may be incorrect or out of date. You can find the latest Debian release key at https://ftp-master.debian.org/keys.html [Where problems could occur] * Very old keys are removed from the keyring by subsequent package updates. An existing program might be looking for old keys and start failing, but this scenario is probably unlikely. [Other Info] ** Affects: debian-ports-archive-keyring (Ubuntu) Importance: Undecided Status: New ** Tags: bionic focal ** Tags added: bionic focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961454 Title: [SRU] Package unusable due to yearly key changes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-ports-archive-keyring/+bug/1961454/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960436] Re: Touchpad setting toggles don't work
Restarting computer seems to have settings take affect properly -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960436 Title: Touchpad setting toggles don't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1960436/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960436] [NEW] Touchpad setting toggles don't work
Public bug reported: It seems none of the touchpad toggles change anything. Natural scrolling: Always acts as disabled Tap to click: always acts enabled. Two finger scrolling: always acts enabled. Edge scrolling: always acts enabled. Also toggling two finger scrolling on will toggle edge scrolling off, and vice versa (not sure if intended, also doesn't affect functionality just the toggle visual). Asus ROG STRIX g15 if that helps anything. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.1-1ubuntu3 Uname: Linux 5.17.0-051700rc3-generic x86_64 ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Feb 9 09:54:19 2022 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2022-01-14 (26 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: Upgraded to jammy on 2022-02-09 (0 days ago) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy third-party-packages ** Description changed: It seems none of the touchpad toggles change anything. Natural scrolling: Always acts as disabled Tap to click: always acts enabled. Two finger scrolling: always acts enabled. Edge scrolling: always acts enabled. Also toggling two finger scrolling on will toggle edge scrolling off, and vice versa (not sure if intended, also doesn't affect functionality just the toggle visual). + + Asus ROG STRIX g15 if that helps anything. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.1-1ubuntu3 Uname: Linux 5.17.0-051700rc3-generic x86_64 ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Feb 9 09:54:19 2022 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2022-01-14 (26 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) ProcEnviron: - LANGUAGE=en_CA:en - PATH=(custom, user) - XDG_RUNTIME_DIR= - LANG=en_CA.UTF-8 - SHELL=/bin/bash + LANGUAGE=en_CA:en + PATH=(custom, user) + XDG_RUNTIME_DIR= + LANG=en_CA.UTF-8 + SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: Upgraded to jammy on 2022-02-09 (0 days ago) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960436 Title: Touchpad setting toggles don't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1960436/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1957948] Re: 2.54.2+21.10 introduces a call in vendor_conf.d/snapd.fish to fish function `fish_add_path` which requires fish 3.2 or later (Impish only packages fish 3.1)
as far as I can see `fish_add_path` is still called from data/env/snapd.fish on master (see https://github.com/snapcore/snapd/blob/master/data/env/snapd.fish.in#L3 for reference) and the mentioned bug and corresponding PR/fix only affect the setting of XDG_DATA_DIRS and not the invalid call to this non-existent function on fish <3.2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1957948 Title: 2.54.2+21.10 introduces a call in vendor_conf.d/snapd.fish to fish function `fish_add_path` which requires fish 3.2 or later (Impish only packages fish 3.1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1957948/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956722] [NEW] package ibus-keyman 11.0.103-4 failed to install/upgrade: 已安装 ibus-keyman 软件包 post-installation 脚本 子进程返回错误状态 1
Public bug reported: when i use apt to install ibus, it appears. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: ibus-keyman 11.0.103-4 ProcVersionSignature: Ubuntu 5.4.0-92.103-generic 5.4.157 Uname: Linux 5.4.0-92-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia wl ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: pass Date: Fri Jan 7 16:18:49 2022 ErrorMessage: 已安装 ibus-keyman 软件包 post-installation 脚本 子进程返回错误状态 1 InstallationDate: Installed on 2022-01-05 (2 days ago) InstallationMedia: Ubuntu-Server 20.04.3 LTS "Focal Fossa" - Release amd64 (20210824) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: ibus-keyman Title: package ibus-keyman 11.0.103-4 failed to install/upgrade: 已安装 ibus-keyman 软件包 post-installation 脚本 子进程返回错误状态 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ibus-keyman (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal uec-images -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956722 Title: package ibus-keyman 11.0.103-4 failed to install/upgrade: 已安装 ibus- keyman 软件包 post-installation 脚本 子进程返回错误状态 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus-keyman/+bug/1956722/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955918] [NEW] Triyng to update to 22.04 fails due to missing 'ubuntu-minimal' package.
Public bug reported: "Invalid package information After updating your package information, the essential package 'ubuntu-minimal' could not be located. This may be because you have no official mirrors listed in your software sources, or because of excessive load on the mirror you are using. See /etc/apt/sources.list for the current list of configured software sources. In the case of an overloaded mirror, you may want to try the upgrade again later. " ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: ubuntu-release-upgrader-core 1:21.10.6 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu67 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu Date: Tue Dec 28 11:58:21 2021 InstallationDate: Installed on 2021-01-28 (334 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to impish on 2021-12-28 (0 days ago) VarLogDistupgradeAptlog: Log time: 2021-12-28 11:57:54.958839 Log time: 2021-12-28 11:57:57.884172 Log time: 2021-12-28 11:58:20.773992 Log time: 2021-12-28 11:58:22.493872 ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade impish -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955918 Title: Triyng to update to 22.04 fails due to missing 'ubuntu-minimal' package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1955918/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1652270] Re: Could not boot into RPi3 with kernel 4.4.0-1038-raspi2
** Changed in: linux-raspi2 (Ubuntu) Assignee: Ryan Finnie (fo0bar) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1652270 Title: Could not boot into RPi3 with kernel 4.4.0-1038-raspi2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1652270/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1771740] Re: Expose link offload options
I no longer have the network card in question and don't have a suitable environment to test, sorry. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1771740 Title: Expose link offload options To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1771740/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922414] Re: ssh-agent fails to start (has_option: command not found)
This is still broken on impish when running i3 under X11. Oct 22 15:23:39 operations /usr/libexec/gdm-x-session[5615]: /etc/X11/Xsession.d/30x11-common_xresources: line 16: has_option: command not found Oct 22 15:23:39 operations /usr/libexec/gdm-x-session[5646]: /etc/X11/Xsession.d/75dbus_dbus-launch: line 9: has_option: command not found Oct 22 15:23:39 operations /usr/libexec/gdm-x-session[5658]: /etc/X11/Xsession.d/90x11-common_ssh-agent: line 9: has_option: command not found -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922414 Title: ssh-agent fails to start (has_option: command not found) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1922414/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 881046] Re: Panning in a virtual monitor is not possible after upgrade to Ubuntu 11.10
Well there you go, if you just wait 10 years, you don't ever have to fix anything. Could have fixed it 5-6 years ago, but why bother, right? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/881046 Title: Panning in a virtual monitor is not possible after upgrade to Ubuntu 11.10 To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/881046/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1946883] [NEW] Merge openldap from Debian unstable for 22.04
FYI: 2.5.8 has just been released. I intend to package and upload it to experimental soon (time/spoons permitting). 2.6.0 should be released quite soon (currently in release candidate phase). If possible I would like to target this for the LTS. It includes another library transition (libldap-2.5-0 to libldap2). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946883 Title: Merge openldap from Debian unstable for 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1946883/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Building kernel metapackages
I have built a modified kernel following the BuildYourOwnKernel guide and would like to distribute it in a private apt repo. (I’m using Bionic now, but will move to Focal in the near future.) It works to ask apt to install one of my packages by its hyper-specific name, like, linux-image-unsigned-4.15.0-159-generic, but I’d like to also produce the linux-image-generic and linux-headers-generic metapackages. I can see that these are produced by the linux-meta project but I could not find any documentation on it. If that’s the right way to proceed, how can I use it to produce metapackages that reference the custom packages I built? Or is it easier to create my own metapackages from scratch? Thanks, Ryan -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
[Bug 1941805] [NEW] liblas-bin unable to locate package
Public bug reported: E: Unable to locate package liblas-bin ** Affects: liblas (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/1941805 Title: liblas-bin unable to locate package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/liblas/+bug/1941805/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938953] Re: virtualbox-dkms 6.1.16-dfsg-6~ubuntu1.20.04.2: virtualbox kernel module failed to build
Hey guys, figured I'd drop in. I had this same issue. Wasn't using virtual box at the time. Came back from playing some drums and this error popped up. I should say I've had some wacky errors with Ubuntu, but it started before that, within Windows before I fully dual booted and made ubuntu my primary OS. Weird errors, random restarts, random crashes, random freezes. I believe it is a hardware issue at this point. I'm building a new pc, and will see what happens. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938953 Title: virtualbox-dkms 6.1.16-dfsg-6~ubuntu1.20.04.2: virtualbox kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1938953/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1809685] Re: The evince application often freezes
I can confirm it happens to me also in 21.04. The PDF opens fine for me but the instant I hit print the evince process pegs the CPU and stays there indefinitely. Files are on the local disk. x86_64 architecture. The most recent PDF that did this to me is here: https://www.lcps.org/site/handlers/filedownload.ashx?moduleinstanceid=305856=381294=New%20Health%20form%20MCH-213G-032014.pdf Printing worked fine with 20.04, then I upgraded to 21.04 about a month ago and have not been able to print a PDF ever since. One possibly interesting bit: ryan@khym:/var/log$ sudo dmesg | tail [947533.329921] audit: type=1400 audit(1629163613.332:388): apparmor="DENIED" operation="connect" profile="/usr/bin/evince" name="/run/user/1000/gvfsd/socket-DTLIeIXr" pid=77344 comm="pool-evince" requested_mask="wr" denied_mask="wr" fsuid=1000 ouid=1000 [947538.329943] audit: type=1400 audit(1629163618.332:389): apparmor="DENIED" operation="connect" profile="/usr/bin/evince" name="/run/user/1000/gvfsd/socket-2diq9E0F" pid=77344 comm="pool-evince" requested_mask="wr" denied_mask="wr" fsuid=1000 ouid=1000 [947543.329859] audit: type=1400 audit(1629163623.332:390): apparmor="DENIED" operation="connect" profile="/usr/bin/evince" name="/run/user/1000/gvfsd/socket-n0LaY8dp" pid=77344 comm="pool-evince" requested_mask="wr" denied_mask="wr" fsuid=1000 ouid=1000 [947548.329836] audit: type=1400 audit(1629163628.332:391): apparmor="DENIED" operation="connect" profile="/usr/bin/evince" name="/run/user/1000/gvfsd/socket-GuW4c7UX" pid=77344 comm="pool-evince" requested_mask="wr" denied_mask="wr" fsuid=1000 ouid=1000 [947553.330670] audit: type=1400 audit(1629163633.332:392): apparmor="DENIED" operation="connect" profile="/usr/bin/evince" name="/run/user/1000/gvfsd/socket-lW4MWUNt" pid=77344 comm="pool-evince" requested_mask="wr" denied_mask="wr" fsuid=1000 ouid=1000 [947558.329769] audit: type=1400 audit(1629163638.332:393): apparmor="DENIED" operation="connect" profile="/usr/bin/evince" name="/run/user/1000/gvfsd/socket-jFM9PdLI" pid=77344 comm="pool-evince" requested_mask="wr" denied_mask="wr" fsuid=1000 ouid=1000 [947563.331063] audit: type=1400 audit(1629163643.336:394): apparmor="DENIED" operation="connect" profile="/usr/bin/evince" name="/run/user/1000/gvfsd/socket-jt0kRZuk" pid=77344 comm="pool-evince" requested_mask="wr" denied_mask="wr" fsuid=1000 ouid=1000 [947568.328371] audit: type=1400 audit(1629163648.332:395): apparmor="DENIED" operation="connect" profile="/usr/bin/evince" name="/run/user/1000/gvfsd/socket-9dOXwErT" pid=77344 comm="pool-evince" requested_mask="wr" denied_mask="wr" fsuid=1000 ouid=1000 [947573.326570] audit: type=1400 audit(1629163653.328:396): apparmor="DENIED" operation="connect" profile="/usr/bin/evince" name="/run/user/1000/gvfsd/socket-tz4r2Rco" pid=77344 comm="pool-evince" requested_mask="wr" denied_mask="wr" fsuid=1000 ouid=1000 [947975.225424] audit: type=1400 audit(1629164055.230:397): apparmor="DENIED" operation="exec" profile="/usr/bin/evince" name="/usr/lib/x86_64-linux-gnu/libproxy/0.4.17/pxgsettings" pid=78607 comm="sh" requested_mask="x" denied_mask="x" fsuid=1000 ouid=0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1809685 Title: The evince application often freezes To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/1809685/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940008] Re: systemd lsb-base integration script leaking shell variable changes which can break consumers
I'm not a bash script architect, but I bodged together this workaround and the ipmiutil_wdt service starts correctly with it applied to my system: https://gist.github.com/TheWug/1a7f509e040f10c05039acc06fe29d9e -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940008 Title: systemd lsb-base integration script leaking shell variable changes which can break consumers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1940008/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940008] Re: systemd lsb-base integration script leaking shell variable changes which can break consumers
It also looks like, farther down, systemctl_redirect() leaks $service. Not sure if it's intentional or not, given that it works to protect its other variables, so maybe it could use some attention too. https://gist.github.com/TheWug/e120145f08e994d89e235e077a82ea75#file-40-systemd-L70 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940008 Title: systemd lsb-base integration script leaking shell variable changes which can break consumers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1940008/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940008] [NEW] systemd lsb-base integration script leaking shell variable changes which can break consumers
Public bug reported: I am using systemd version 248.3-1ubuntu3 from the impish repository. It was compiled and built in the following manner: # add impish deb-src repository to apt sources apt build-dep systemd/impish apt source -b systemd/impish Once built, it was installed over the top of systemd 245.4-4ubuntu3. I am running ubuntu 20.04.2. The source tarball of systemd includes a file (./debian/systemd/lib/lsb/init-functions.d/40-systemd) which is intended to be installed into the drop-in script directory provided by the lsb- base package (/lib/lsb/init-functions.d). The problem that I am having is that this file (which is sourced by any script which sources /lib/lsb/init-functions) is setting variables, and in doing so, accidentally overwriting variables which are configured by the calling script. https://gist.github.com/TheWug/e120145f08e994d89e235e077a82ea75#file-40-systemd-L19 I noticed this when investigating why ipmiutil_wdt.service (provided by package ipmiutil) was failing to start. The problem is that the ipmiutil_wdt script, which makes use of init-functions, was statically setting some variables for later use, including one called $prog. $prog is then inadvertently overwritten by 40-systemd when ipmiutil_wdt sources /lib/lsb/init-functions. I think this is systemd's bug because systemd's lsb-base drop-in is not being a "good neighbor" to the scripts with which it shares a controlling shell. Even if ipmiutil were to rewrite its ipmiutil-wdt script, any other such script provided by another package which tries to use a variable called $prog (or $executable, or $argument, or $service, or $state, or any of a handful of others) will find its feet being stepped on by systemd's drop-in. I propose that the drop-in be modified to encapsulate all of this behavior where variables are assigned to within a function or subshell or something, so they can't accidentally contaminate the outside world. Other related package versions: lsb-base: 11.1.0ubuntu2 ipmiutil: 3.1.5-1 ** Affects: systemd (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/1940008 Title: systemd lsb-base integration script leaking shell variable changes which can break consumers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1940008/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 601764] Re: psi does not re-sense network after suspend/hibernate
This is not incomplete; this is a full and accurate bug report that applies to all versions up to and including the current version, as well as the psi-plus fork. This is one of the most annoying "features" of this application. ** Changed in: psi (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/601764 Title: psi does not re-sense network after suspend/hibernate To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/psi/+bug/601764/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1936416] Re: package phpmyadmin 4:4.9.5+dfsg1-2 failed to install/upgrade: installed phpmyadmin package post-installation script subprocess returned error exit status 1
Thanks for the link. This can be closed if needed On Thu, Jul 15, 2021, 11:30 AM William Desportes <1936...@bugs.launchpad.net> wrote: > > If you have a root password for MySQL set before phpmyadmin is installed > the installer craps out, because it is looking for a blank password. The > same goes for the update script. > I'm not a coder, just a person that has been plagued since I discovered > this awesome piece of software. > > This is interesting, but as far as I know we do not control this part. > It is the package https://packages.debian.org/fr/sid/dbconfig-common > But it will be worth investigating if there is something not configured > correctly > > If you want a newer version of phpMyAdmin check out: > https://github.com/phpmyadmin/phpmyadmin/wiki/DebianUbuntu#ubuntu-ppa > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1936416 > > Title: > package phpmyadmin 4:4.9.5+dfsg1-2 failed to install/upgrade: > installed phpmyadmin package post-installation script subprocess > returned error exit status 1 > > Status in phpmyadmin package in Ubuntu: > New > > Bug description: > I think this relates to me having a password and after 25 million > years you all still haven't figured out a way to work around that. > > but if not here is the report, delete if so. > > ProblemType: Package > DistroRelease: Ubuntu 20.04 > Package: phpmyadmin 4:4.9.5+dfsg1-2 > ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119 > Uname: Linux 5.4.0-77-generic x86_64 > NonfreeKernelModules: nvidia_modeset nvidia > ApportVersion: 2.20.11-0ubuntu27.18 > Architecture: amd64 > CasperMD5CheckResult: skip > Date: Thu Jul 8 19:37:41 2021 > ErrorMessage: installed phpmyadmin package post-installation script > subprocess returned error exit status 1 > InstallationDate: Installed on 2016-11-11 (1707 days ago) > InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 > (20160803) > PackageArchitecture: all > 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 > RelatedPackageVersions: >dpkg 1.19.7ubuntu3 >apt 2.0.6 > SourcePackage: phpmyadmin > Title: package phpmyadmin 4:4.9.5+dfsg1-2 failed to install/upgrade: > installed phpmyadmin package post-installation script subprocess returned > error exit status 1 > UpgradeStatus: Upgraded to focal on 2021-07-09 (6 days ago) > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/phpmyadmin/+bug/1936416/+subscriptions > > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1936416 Title: package phpmyadmin 4:4.9.5+dfsg1-2 failed to install/upgrade: installed phpmyadmin package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/phpmyadmin/+bug/1936416/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1936416] Re: package phpmyadmin 4:4.9.5+dfsg1-2 failed to install/upgrade: installed phpmyadmin package post-installation script subprocess returned error exit status 1
If you have a root password for MySQL set before phpmyadmin is installed the installer craps out, because it is looking for a blank password. The same goes for the update script. I'm not a coder, just a person that has been plagued since I discovered this awesome piece of software. On Thu, Jul 15, 2021 at 10:25 AM William Desportes < 1936...@bugs.launchpad.net> wrote: > > I think this relates to me having a password and after 25 million > years you all still haven't figured out a way to work around that. > > Could you explain yourself better on this ? > I am not sure to understand > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1936416 > > Title: > package phpmyadmin 4:4.9.5+dfsg1-2 failed to install/upgrade: > installed phpmyadmin package post-installation script subprocess > returned error exit status 1 > > Status in phpmyadmin package in Ubuntu: > New > > Bug description: > I think this relates to me having a password and after 25 million > years you all still haven't figured out a way to work around that. > > but if not here is the report, delete if so. > > ProblemType: Package > DistroRelease: Ubuntu 20.04 > Package: phpmyadmin 4:4.9.5+dfsg1-2 > ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119 > Uname: Linux 5.4.0-77-generic x86_64 > NonfreeKernelModules: nvidia_modeset nvidia > ApportVersion: 2.20.11-0ubuntu27.18 > Architecture: amd64 > CasperMD5CheckResult: skip > Date: Thu Jul 8 19:37:41 2021 > ErrorMessage: installed phpmyadmin package post-installation script > subprocess returned error exit status 1 > InstallationDate: Installed on 2016-11-11 (1707 days ago) > InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 > (20160803) > PackageArchitecture: all > 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 > RelatedPackageVersions: >dpkg 1.19.7ubuntu3 >apt 2.0.6 > SourcePackage: phpmyadmin > Title: package phpmyadmin 4:4.9.5+dfsg1-2 failed to install/upgrade: > installed phpmyadmin package post-installation script subprocess returned > error exit status 1 > UpgradeStatus: Upgraded to focal on 2021-07-09 (6 days ago) > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/phpmyadmin/+bug/1936416/+subscriptions > > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1936416 Title: package phpmyadmin 4:4.9.5+dfsg1-2 failed to install/upgrade: installed phpmyadmin package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/phpmyadmin/+bug/1936416/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1936416] [NEW] package phpmyadmin 4:4.9.5+dfsg1-2 failed to install/upgrade: installed phpmyadmin package post-installation script subprocess returned error exit status 1
Public bug reported: I think this relates to me having a password and after 25 million years you all still haven't figured out a way to work around that. but if not here is the report, delete if so. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: phpmyadmin 4:4.9.5+dfsg1-2 ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119 Uname: Linux 5.4.0-77-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Jul 8 19:37:41 2021 ErrorMessage: installed phpmyadmin package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2016-11-11 (1707 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803) PackageArchitecture: all 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 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: phpmyadmin Title: package phpmyadmin 4:4.9.5+dfsg1-2 failed to install/upgrade: installed phpmyadmin package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2021-07-09 (6 days ago) ** Affects: phpmyadmin (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/1936416 Title: package phpmyadmin 4:4.9.5+dfsg1-2 failed to install/upgrade: installed phpmyadmin package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/phpmyadmin/+bug/1936416/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1936253] [NEW] Juju 2.9.8 tries to use an empty UID when deleting Kubernetes objects, and cannot remove applications
Public bug reported: I did a little digging on this, and it's definitely the UID on the RBAC role. I'd blame this commit: https://github.com/juju/juju/commit/35e712ef6bf485aaeb8b718e6e6aa10683e381bc#diff-1bb294296419d47846f2432fb32f22cd9f42745a4c0aa8568f140bf499799b9fR85 Juju calls a factory with a name only: https://github.com/juju/juju/blob/develop/caas/kubernetes/provider/application/application.go#L934 Then gets a bare struct where UID is definitely empty, and immediately try to delete it with an empty precondition: https://github.com/juju/juju/blob/dcc82d771253673354f5cd96cc87b528bd81e7b2/caas/kubernetes/provider/resources/clusterrolebinding.go#L31 ** Affects: juju (Ubuntu) Importance: Undecided Status: New ** Package changed: v4l2loopback (Ubuntu) => juju (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1936253 Title: Juju 2.9.8 tries to use an empty UID when deleting Kubernetes objects, and cannot remove applications To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju/+bug/1936253/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934616] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1934616/+attachment/5509443/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934616 Title: qterminal doesn't use correct .bashrc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mate-terminal/+bug/1934616/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934616] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1934616/+attachment/5509442/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934616 Title: qterminal doesn't use correct .bashrc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mate-terminal/+bug/1934616/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934616] Re: qterminal doesn't use correct .bashrc
apport information ** Tags added: apport-collected ** Description changed: Ubuntu 20.04.2 LTS mate-terminal 1.24.0-2ubuntu1 I'm in the process of cleaning up my $HOME. Part of this process was to move all of bash's "junk" into XDG BaseDir compliant locations by specifying in .profile to look at $XDG_CONFIG_HOME/bash/ for the .bashrc file, etc. bash itself is handling the move just fine (e.g. it outputs its history to ~/.local/share/bash/history as commanded). I can go into a TTY and use aliases I specifically put into the new .bashrc (located at ~/.config/bash/.bashrc), etc. The problem is when I try to use said aliases in qterminal, it refuses to recognize this change and use the proper .bashrc. Attached is my ~/.profile for reference. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27.18 + Architecture: amd64 + CasperMD5CheckResult: skip + CurrentDesktop: MATE + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2018-12-05 (944 days ago) + InstallationMedia: Ubuntu-MATE 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) + NonfreeKernelModules: nvidia_modeset nvidia + Package: qterminal + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 5.4.0-77.86-lowlatency 5.4.119 + Tags: focal + Uname: Linux 5.4.0-77-lowlatency x86_64 + UpgradeStatus: Upgraded to focal on 2021-06-18 (17 days ago) + UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1934616/+attachment/5509441/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934616 Title: qterminal doesn't use correct .bashrc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mate-terminal/+bug/1934616/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934616] Re: qterminal doesn't use correct .bashrc
I added mate-terminal as being affected as well, as I just attempted it there, and have the same issue. ** Description changed: Ubuntu 20.04.2 LTS - qterminal 0.14.1-0ubuntu2 (universe, amd64) + mate-terminal 1.24.0-2ubuntu1 I'm in the process of cleaning up my $HOME. Part of this process was to move all of bash's "junk" into XDG BaseDir compliant locations by specifying in .profile to look at $XDG_CONFIG_HOME/bash/ for the .bashrc file, etc. bash itself is handling the move just fine (e.g. it outputs its history to ~/.local/share/bash/history as commanded). I can go into a TTY and use aliases I specifically put into the new .bashrc (located at ~/.config/bash/.bashrc), etc. The problem is when I try to use said aliases in qterminal, it refuses to recognize this change and use the proper .bashrc. I'm sure this is an "upstream" issue, but their GitHub issue tracker essentially tells Ubuntu users to file issues here instead. Attached is my ~/.profile for reference. ** Description changed: Ubuntu 20.04.2 LTS mate-terminal 1.24.0-2ubuntu1 I'm in the process of cleaning up my $HOME. Part of this process was to move all of bash's "junk" into XDG BaseDir compliant locations by specifying in .profile to look at $XDG_CONFIG_HOME/bash/ for the .bashrc file, etc. bash itself is handling the move just fine (e.g. it outputs its history to ~/.local/share/bash/history as commanded). I can go into a TTY and use aliases I specifically put into the new .bashrc (located at ~/.config/bash/.bashrc), etc. The problem is when I try to use said aliases in qterminal, it refuses to recognize this change and use the proper .bashrc. - I'm sure this is an "upstream" issue, but their GitHub issue tracker - essentially tells Ubuntu users to file issues here instead. - Attached is my ~/.profile for reference. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934616 Title: qterminal doesn't use correct .bashrc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mate-terminal/+bug/1934616/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934616] [NEW] qterminal doesn't use correct .bashrc
Public bug reported: Ubuntu 20.04.2 LTS mate-terminal 1.24.0-2ubuntu1 I'm in the process of cleaning up my $HOME. Part of this process was to move all of bash's "junk" into XDG BaseDir compliant locations by specifying in .profile to look at $XDG_CONFIG_HOME/bash/ for the .bashrc file, etc. bash itself is handling the move just fine (e.g. it outputs its history to ~/.local/share/bash/history as commanded). I can go into a TTY and use aliases I specifically put into the new .bashrc (located at ~/.config/bash/.bashrc), etc. The problem is when I try to use said aliases in qterminal, it refuses to recognize this change and use the proper .bashrc. Attached is my ~/.profile for reference. ** Affects: mate-terminal (Ubuntu) Importance: Undecided Status: New ** Affects: qterminal (Ubuntu) Importance: Undecided Status: New ** Attachment added: "profile-copy" https://bugs.launchpad.net/bugs/1934616/+attachment/5509031/+files/profile-copy ** Also affects: mate-terminal (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/1934616 Title: qterminal doesn't use correct .bashrc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mate-terminal/+bug/1934616/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888395] Re: live migration of a vm using the single port binding work flow is broken in train as a result of the introduction of sriov live migration
I've tested this out using the latest stable/train release from opendev. My initial tests are allowing me to live migrate back and forth again. Haven't gotten to every corner case but this looks promising. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888395 Title: live migration of a vm using the single port binding work flow is broken in train as a result of the introduction of sriov live migration To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1888395/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1785493] Re: Netplan on-link does not work for IPv6
Fixed in Ubuntu 20.04! You just need to add a link-scope route for your gateway, as documented: https://netplan.io/examples/#reaching-a -directly-connected-gateway network: ethernets: ens3: dhcp4: true addresses: [ "2602:ff75:7:34fd::/128" ] routes: - to: "2602:ff75:7::1/128" scope: link - to: "::/0" via: "2602:ff75:7::1" on-link: true version: 2 ** Changed in: netplan.io (Ubuntu) Status: Triaged => 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/1785493 Title: Netplan on-link does not work for IPv6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1785493/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929583] [NEW] libpci is not declared as a runtime dependency
Public bug reported: In snapcraft.yaml: https://git.launchpad.net/~chromium-team/chromium- browser/+git/snap-from-source/tree/snapcraft.yaml?h=stable You can see that libpciaccess0 is declared under stage-packages for intel-media-driver. However, this is missing from chromium. This is causing issues in Chrome: https://bugs.chromium.org/p/chromium/issues/detail?id=1068560#c22 ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929583 Title: libpci is not declared as a runtime dependency To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1929583/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1926265] Re: slapd enter in infinite loop on sched_yield syscall
On Wed, May 19, 2021 at 06:46:02PM -, Sergio Durigan Junior wrote: >Ryan, IIUC the patch you're proposing fixes the issue experienced by >Stephane, but we're not entirely sure that it's the same issue being >reported in this bug. Am I right? Yes, exactly. (My debdiff just drops the buggy patch, at the cost of re-introducing the original issue, which IMO has a much smaller impact than the regression, so hopefully an acceptable trade-off.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926265 Title: slapd enter in infinite loop on sched_yield syscall To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1926265/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926265] Re: slapd enter in infinite loop on sched_yield syscall
On Fri, May 14, 2021 at 01:36:12PM -, Stephane Chazelas wrote: >The important backtrace in there is the one from thread 11: > >#0 0x7fb288428474 in read () from /lib/x86_64-linux-gnu/libpthread.so.0 >No symbol table info available. >#1 0x7fb2890c4518 in ?? () from /usr/lib/x86_64-linux-gnu/liblber-2.4.so.2 >No symbol table info available. >#2 0x7fb287895848 in ?? () from /usr/lib/x86_64-linux-gnu/libgnutls.so.30 >No symbol table info available. This is a valid issue, but are we certain it's the same one? The reporter talked about sched_yield and their backtraces included several threads of back_monitor waiting on some kind of lock. >https://bugs.openldap.org/show_bug.cgi?id=8650#c12 explains that it's >https://github.com/openldap/openldap/commit/7b5181da8cdd47a13041f9ee36fa9590a0fa6e48 >that is responsible for the issue. > >https://github.com/openldap/openldap/commit/4c1ab16ade18a253dd81df7e6eced4d920ac6a8e >reverted that commit, but that one did not make it into bionic. Indeed. :( I didn't notice this went unfixed in an LTS, I'm sorry for missing that. >So cherry picking >https://github.com/openldap/openldap/commit/4c1ab16ade18a253dd81df7e6eced4d920ac6a8e >should fix it. In this version it's a Debian patch, so probably just remove the offending patch from d/patches, rather than import the revert? On Fri, May 14, 2021 at 02:18:47PM -, Stephane Chazelas wrote: >Yes, >https://github.com/openldap/openldap/commit/735e1ab14bb055344b4e767a216aa410aa7d1503 >can't be directly applied there. There have been other changes in >between in that section including changes in API, so it would take more >effort to backport that fix. Right. I'm not confident I can backport that correctly, so I'd feel safer just doing the revert. However, sssd should also be tested, to ensure the version in bionic isn't affected by ITS#9210 (https://bugs.openldap.org/show_bug.cgi?id=9210). COMPLETELY UNTESTED debdiff attached. ** Bug watch added: bugs.openldap.org/ #9210 https://bugs.openldap.org/show_bug.cgi?id=9210 ** Attachment added: "openldap_2.4.45+dfsg-1ubuntu1.11.debdiff" https://bugs.launchpad.net/bugs/1926265/+attachment/5497610/+files/openldap_2.4.45+dfsg-1ubuntu1.11.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926265 Title: slapd enter in infinite loop on sched_yield syscall To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1926265/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925061] [NEW] tried installing on Mac Pro 3, 1 w/ amd card and 3.0 bluetooth upgrades
Public bug reported: nothing to note. 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: Sun Apr 18 20:32:26 2021 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_US.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 LC_NUMERIC=C.UTF-8 RebootRequiredPkgs: linux-image-5.8.0-25-generic linux-base SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (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/1925061 Title: tried installing on Mac Pro 3,1 w/ amd card and 3.0 bluetooth upgrades To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1925061/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1857552] Re: [81NX, Realtek ALC285, Speaker, Internal] No sound at all
There is a patch now that is expected to be in kernel version 5.13. If you're willing to build your own kernel, you can find the patch here and do it yourself: https://github.com/thesofproject/linux/issues/2748 ** Bug watch added: github.com/thesofproject/linux/issues #2748 https://github.com/thesofproject/linux/issues/2748 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1857552 Title: [81NX, Realtek ALC285, Speaker, Internal] No sound at all To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1857552/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1857198] Re: alsa ALC285 Missing still, No Sound Lenovo Ideapad S740
There is a patch now that is expected to be in kernel version 5.13. If you're willing to build your own kernel, you can find the patch here and do it yourself: https://github.com/thesofproject/linux/issues/2748 ** Bug watch added: github.com/thesofproject/linux/issues #2748 https://github.com/thesofproject/linux/issues/2748 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1857198 Title: alsa ALC285 Missing still, No Sound Lenovo Ideapad S740 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1857198/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1924219] [NEW] internal compiler error on certain variably sized 3d arrays
Public bug reported:
WSL2:
Ubuntu 20.04.2 LTS (GNU/Linux 5.4.72-microsoft-standard-WSL2 x86_64)
$ lsb_release -rd
Description:Ubuntu 20.04.2 LTS
Release:20.04
$ apt-cache policy gcc-10
gcc-10:
Installed: 10.2.0-5ubuntu1~20.04
Candidate: 10.2.0-5ubuntu1~20.04
Version table:
*** 10.2.0-5ubuntu1~20.04 500
500 http://archive.ubuntu.com/ubuntu focal-updates/universe amd64
Packages
500 http://security.ubuntu.com/ubuntu focal-security/universe amd64
Packages
100 /var/lib/dpkg/status
10-20200411-0ubuntu1 500
500 http://archive.ubuntu.com/ubuntu focal/universe amd64 Packages
$ g++-10 -v
COLLECT_GCC=g++-10
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/10/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none:amdgcn-amdhsa:hsa
OFFLOAD_TARGET_DEFAULT=1
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu
10.2.0-5ubuntu1~20.04' --with-bugurl=file:///usr/share/doc/gcc-10/README.Bugs
--enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++,m2 --prefix=/usr
--with-gcc-major-version-only --program-suffix=-10
--program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id
--libexecdir=/usr/lib --without-included-gettext --enable-threads=posix
--libdir=/usr/lib --enable-nls --enable-clocale=gnu --enable-libstdcxx-debug
--enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new
--enable-gnu-unique-object --disable-vtable-verify --enable-plugin
--enable-default-pie --with-system-zlib --enable-libphobos-checking=release
--with-target-system-zlib=auto --enable-objc-gc=auto --enable-multiarch
--disable-werror --with-arch-32=i686 --with-abi=m64
--with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic
--enable-offload-targets=nvptx-none=/build/gcc-10-WJNXnb/gcc-10-10.2.0/debian/tmp-nvptx/usr,amdgcn-amdhsa=/build/gcc-10-WJNXnb/gcc-10-10.2.0/debian/tmp-gcn/usr,hsa
--without-cuda-driver --enable-checking=release --build=x86_64-linux-gnu
--host=x86_64-linux-gnu --target=x86_64-linux-gnu
Thread model: posix
Supported LTO compression algorithms: zlib zstd
gcc version 10.2.0 (Ubuntu 10.2.0-5ubuntu1~20.04)
$ cat main.cpp
int main() {
int n;
bool arr[3][n][n] {};
if(arr[0][0][0]) {
// don't optimize this out
return 1;
}
}
$ g++-10 main.cpp
during RTL pass: expand
main.cpp: In function ‘int main()’:
main.cpp:3:7: internal compiler error: in make_decl_rtl, at varasm.c:1342
3 | bool arr[3][n][n] {};
| ^~~
Please submit a full bug report,
with preprocessed source if appropriate.
See for instructions.
The type of arr can be any primitive (could possibly include more types,
didn't check). arr must be initialized with brackets. At least one of
the first two dimensions of arr must be a constant, while the last
dimension must be of variable length. I've repeated this behavior with
versions 5.1.0, 6.4.0, 7.3.0, 9.2.0 on online compilers.
** Affects: gcc-10 (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/1924219
Title:
internal compiler error on certain variably sized 3d arrays
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gcc-10/+bug/1924219/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1576559] Re: Refused to switch profile to headset_head_unit: Not connected
@Daniel van Vugt - Thank you for suggesting the change in post #60. It didn't work for me though. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1576559 Title: Refused to switch profile to headset_head_unit: Not connected To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1576559/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1921562] [NEW] Intermittent hangs during ldap_search_ext when TLS enabled
On Sat, Mar 27, 2021 at 01:06:42AM -, Vincent Vanlaer wrote: >https://git.openldap.org/openldap/openldap/-/commit/735e1ab Note that this commit is for OpenLDAP 2.5 and needs adjustment for the 2.4 branch. The commit ids for 2.4 are: https://git.openldap.org/openldap/openldap/-/commit/7cf7aa3141 https://git.openldap.org/openldap/openldap/-/commit/85fc8974f5 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921562 Title: Intermittent hangs during ldap_search_ext when TLS enabled To manage notifications about this bug go to: https://bugs.launchpad.net/openldap/+bug/1921562/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1918427] Re: curtin: install flash-kernel in arm64 UEFI unexpected
* dann frazier <1918...@bugs.launchpad.net> [2021-03-19 12:16]:
> On Fri, Mar 19, 2021 at 10:01 AM Ryan Harper <1918...@bugs.launchpad.net>
> wrote:
> >
> > * dann frazier <1918...@bugs.launchpad.net> [2021-03-18 16:30]:
> > > On Thu, Mar 18, 2021 at 12:25 PM Ryan Harper <1918...@bugs.launchpad.net>
> > > wrote:
> > > >
> > > > * dann frazier <1918...@bugs.launchpad.net> [2021-03-18 12:11]:
> > > > > On Thu, Mar 18, 2021 at 10:25 AM Ryan Harper
> > > > > <1918...@bugs.launchpad.net> wrote:
> > > > > >
> > > > > > * dann frazier <1918...@bugs.launchpad.net> [2021-03-17 20:30]:
> > > > > > > On Tue, Mar 16, 2021 at 10:05 AM Ryan Harper
> > > > > > > <1918...@bugs.launchpad.net> wrote:
> > > > > > > >
> > > > > > > > Hi Dan,
> > > > > > > >
> > > > > > >
> > > > > > > 1) flash-kernel could get installed post-divert. In that case,
> > > > > > > flash-kernel's own postinst will cause it to run and then fail.
> > > > > > > This
> > > > > > > happens today if you start with a cloud image w/o flash-kernel
> > > > > > > pre-baked because Ubuntu's kernel recommends flash-kernel,
> > > > > > > causing it
> > > > > > > to be installed along with the kernel. Official cloud images
> > > > > > > happen to
> > > > > >
> > > > > > Hrm, so if we take a squashfs rootfs (with no flash-kernel present)
> > > > > > chroot into it and install the linux-image-generic package pulling
> > > > > > in
> > > > > > flash-kernel this fails due to postinst of flash-kernel expecting
> > > > > > initramfs to already be generated? This doesn't seem like a curtin
> > > > > > bug.
> > > > >
> > > > > If done so in a chroot that exposes the kernel interfaces (/proc &
> > > > > /sys) that claim to be hardware that requires the initramfs to be
> > > > > post-processed, yes.
> > > >
> > > > Maybe I'm missing something but if I install linux-image-generic
> > > > it populates /boot with vmlinuz-$version (and a few more things)
> > > > and /lib/modules/$version and the kernels postinst will invoke
> > > > update-initramfs. The /boot/initrd.img-$version is *generated* at
> > > > that time during the kernel's postinstall
> > > >
> > > > Now, in the arm case IIUC, the kernel package has a dep on flash-kernel
> > > > being present as it's "needed" to generate the initramfs ... so how can
> > > > flash-kernel's postinst *fail* if it is the tool that's generating said
> > > > initramfs file?
> > >
> > > What flash-kernel does is generate wrapped versions of *exisiting*
> > > vmlinuz and initrd.img files. It doesn't generate those files, rather
> > > post-processes them.
> > > The kernel doesn't depend on flash-kernel, it just recommends it like
> > > it does GRUB on x86.
> >
> > Yes, I get that but it still looks like a packaging bug if dpkg installs
> > flash-kernel first and /boot is not populated with existing initrds; one
> > could easily see this happen in a debootstrap.
>
> Given that a failure to produce a wrapped initrd could cause a system
> to become unbootable, it does seem to me like a hard failure here is
> warranted. But, perhaps we could provide a "s... it's ok, just
> chill" mechanism. Maybe a FLASH_KERNEL_SKIP=1 environment variable?
Agreed but with the condition that the *input* is present. If the
initrd file has not yet been generated then another error from
flash-kernel seems redundant, specifically in the case where if the
kernel package is not yet installed (and maybe this is the reasonble
check the post-inst can do) then it's *always* going to fail.
Does flash-kernel hook into initramfs updates via the
/etc/kernel/{pre,post}inst.d/flash-kernel ? like initramfs-tools does?
I suspect most of what flash-kernel does would be triggered via kernel
postinst hooks.
>
> > Is the "liveness" of the chroot what's tripping up flash-kernel? We
> > currently run inside a chroot which mounts /dev /proc /run and /sys; we
> > could drop those but it also seems reasonable to have flash-kernel not
> > expect existing initrds?
>
> Certainly a non-live chroot can avoid this by leading f-k to believe
> it does not recognize the system. In fact, ISTR bind mounting certain
> files in build chroots to trick f-k into doing nothing.
Interesting. That may be another approach; though that would be a f-k
specific mount for curtin to swallow when installing one package; we
might not know it's getting installed (like as a Recommends with the
linux-image-generic) so that might not be as useful.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1918427
Title:
curtin: install flash-kernel in arm64 UEFI unexpected
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1918427/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1918427] Re: curtin: install flash-kernel in arm64 UEFI unexpected
* dann frazier <1918...@bugs.launchpad.net> [2021-03-18 16:30]: > On Thu, Mar 18, 2021 at 12:25 PM Ryan Harper <1918...@bugs.launchpad.net> > wrote: > > > > * dann frazier <1918...@bugs.launchpad.net> [2021-03-18 12:11]: > > > On Thu, Mar 18, 2021 at 10:25 AM Ryan Harper <1918...@bugs.launchpad.net> > > > wrote: > > > > > > > > * dann frazier <1918...@bugs.launchpad.net> [2021-03-17 20:30]: > > > > > On Tue, Mar 16, 2021 at 10:05 AM Ryan Harper > > > > > <1918...@bugs.launchpad.net> wrote: > > > > > > > > > > > > Hi Dan, > > > > > > > > > > > > > > > > 1) flash-kernel could get installed post-divert. In that case, > > > > > flash-kernel's own postinst will cause it to run and then fail. This > > > > > happens today if you start with a cloud image w/o flash-kernel > > > > > pre-baked because Ubuntu's kernel recommends flash-kernel, causing it > > > > > to be installed along with the kernel. Official cloud images happen to > > > > > > > > Hrm, so if we take a squashfs rootfs (with no flash-kernel present) > > > > chroot into it and install the linux-image-generic package pulling in > > > > flash-kernel this fails due to postinst of flash-kernel expecting > > > > initramfs to already be generated? This doesn't seem like a curtin bug. > > > > > > If done so in a chroot that exposes the kernel interfaces (/proc & > > > /sys) that claim to be hardware that requires the initramfs to be > > > post-processed, yes. > > > > Maybe I'm missing something but if I install linux-image-generic > > it populates /boot with vmlinuz-$version (and a few more things) > > and /lib/modules/$version and the kernels postinst will invoke > > update-initramfs. The /boot/initrd.img-$version is *generated* at > > that time during the kernel's postinstall > > > > Now, in the arm case IIUC, the kernel package has a dep on flash-kernel > > being present as it's "needed" to generate the initramfs ... so how can > > flash-kernel's postinst *fail* if it is the tool that's generating said > > initramfs file? > > What flash-kernel does is generate wrapped versions of *exisiting* > vmlinuz and initrd.img files. It doesn't generate those files, rather > post-processes them. > The kernel doesn't depend on flash-kernel, it just recommends it like > it does GRUB on x86. Yes, I get that but it still looks like a packaging bug if dpkg installs flash-kernel first and /boot is not populated with existing initrds; one could easily see this happen in a debootstrap. Is the "liveness" of the chroot what's tripping up flash-kernel? We currently run inside a chroot which mounts /dev /proc /run and /sys; we could drop those but it also seems reasonable to have flash-kernel not expect existing initrds? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918427 Title: curtin: install flash-kernel in arm64 UEFI unexpected To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1918427/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1918427] Re: curtin: install flash-kernel in arm64 UEFI unexpected
* dann frazier <1918...@bugs.launchpad.net> [2021-03-18 12:11]: > On Thu, Mar 18, 2021 at 10:25 AM Ryan Harper <1918...@bugs.launchpad.net> > wrote: > > > > * dann frazier <1918...@bugs.launchpad.net> [2021-03-17 20:30]: > > > On Tue, Mar 16, 2021 at 10:05 AM Ryan Harper <1918...@bugs.launchpad.net> > > > wrote: > > > > > > > > Hi Dan, > > > > > > > > > > 1) flash-kernel could get installed post-divert. In that case, > > > flash-kernel's own postinst will cause it to run and then fail. This > > > happens today if you start with a cloud image w/o flash-kernel > > > pre-baked because Ubuntu's kernel recommends flash-kernel, causing it > > > to be installed along with the kernel. Official cloud images happen to > > > > Hrm, so if we take a squashfs rootfs (with no flash-kernel present) > > chroot into it and install the linux-image-generic package pulling in > > flash-kernel this fails due to postinst of flash-kernel expecting > > initramfs to already be generated? This doesn't seem like a curtin bug. > > If done so in a chroot that exposes the kernel interfaces (/proc & > /sys) that claim to be hardware that requires the initramfs to be > post-processed, yes. Maybe I'm missing something but if I install linux-image-generic it populates /boot with vmlinuz-$version (and a few more things) and /lib/modules/$version and the kernels postinst will invoke update-initramfs. The /boot/initrd.img-$version is *generated* at that time during the kernel's postinstall Now, in the arm case IIUC, the kernel package has a dep on flash-kernel being present as it's "needed" to generate the initramfs ... so how can flash-kernel's postinst *fail* if it is the tool that's generating said initramfs file? > > In summary curtin will need: > > > > move ephemeral deps.py flash-kernel to arch-packages in > > install-missing-packages with the same logic guarding when to add the > > dep. > > > > It's not clear to me why curtin should work around the packaging bugs > > around flash-kernel and I would suggest that flash-kernel be kept in the > > cloud images until the packging deps/bugs around it are fixed. > > I don't think it should - we should SRU Date's f-k change and the > kernel Recommends change. Are there other packaging issues you've > identified? I don't think possibly something flash-kernel related to the above discussion but that may just be my own misinformation. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918427 Title: curtin: install flash-kernel in arm64 UEFI unexpected To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1918427/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1918427] Re: curtin: install flash-kernel in arm64 UEFI unexpected
* dann frazier <1918...@bugs.launchpad.net> [2021-03-17 20:30]: > On Tue, Mar 16, 2021 at 10:05 AM Ryan Harper <1918...@bugs.launchpad.net> > wrote: > > > > Hi Dan, > > > > Could you summarize the problem with flash-kernel and this system? > > Sure. flash-kernel recognizes Mustang boards and will generate uImage > and uInitrd files for it, which are required for booting with u-boot > firmware. However, these boards can also run in UEFI mode, which > Date's board does. In UEFI mode, flash-kernel still knows it is on a > Mustang and generates uImage/uInitrd files - which won't be used for > anything in that case, they are just wasting space, but does not cause > it to fail. This does cause problems in a curtin install though. > Curtin has logic to divert away tools that get executed during > initramfs hooks, to avoid failures in packaging scripts before an > initramfs is generated. flash-kernel in particular will fail if an > initramfs is not found on this system. Curtin tries to be smart here > and only divert flash-kernel 1) if it is installed and 2) on systems > that are*not* in UEFI mode, and both of these scenarios have escapes: > > 1) flash-kernel could get installed post-divert. In that case, > flash-kernel's own postinst will cause it to run and then fail. This > happens today if you start with a cloud image w/o flash-kernel > pre-baked because Ubuntu's kernel recommends flash-kernel, causing it > to be installed along with the kernel. Official cloud images happen to Hrm, so if we take a squashfs rootfs (with no flash-kernel present) chroot into it and install the linux-image-generic package pulling in flash-kernel this fails due to postinst of flash-kernel expecting initramfs to already be generated? This doesn't seem like a curtin bug. > have flash-kernel pre-baked which avoids this issue. I think curtin > should work whether or not the kernel recommends flash-kernel and > whether or not curtin is pre-baked (in fact, I'd like for us to stop > pre-baking it - the vast majoriy of ARM servers do not need it). > > 2) If flash-kernel is installed, and curtin finds we're in UEFI mode, > it chooses not to divert flash-kernel. flash-kernel will therefore run > and fail on UEFI Mustangs. I don't think that's true. The logic for disabling initramfs tools always runs regardless of UEFI mode and arch. See curtin/commands/curthooks.py:builtin_curthooks() lines 1692- 1699 > > The way I've personally framed this issue is that Ubuntu should not be > trying to install flash-kernel on ARM systems that don't require it, > which is the reason I've added the various tasks here. > - cloud images shouldn't prebake it OK > - the kernel should allow non-flash-kernel bootloaders to satisfy its > recommends OK Thanks. I replied to your later post without seeing this first. This helps a lot. > - curtin shouldn't install flash-kernel on efi-based arm64 servers. > It does this today, but - in what seems like a bug, only in the > ephemeral and not the target. Yeah; I suspect flash-kernel being pre-baked into images hid this for some time. As I mentioned in the other reply, I do think that lines 57-58 in curtin/deps/__init__.py which bring in flash-kerenl to the epheramal can be removed. And it sounds like we'd move that logic instead to the install-missing-packages arch_packages where we ensure s390-tools/zipl are install for s390, there we'd add the same logic to append flash-kernel where needed for the target OS. > > A separate issue is that flash-kernel should know to just exit if it's > running on an EFI system and not bother creating the unused > uImage/uInitrd - Date recently got a patched merged into Debian's f-k > to do that. That would seemingly also avoid the curtin issues here, > but only if we continue to install flash-kernel all the time. OK. In summary curtin will need: move ephemeral deps.py flash-kernel to arch-packages in install-missing-packages with the same logic guarding when to add the dep. It's not clear to me why curtin should work around the packaging bugs around flash-kernel and I would suggest that flash-kernel be kept in the cloud images until the packging deps/bugs around it are fixed. Does that make sense? Ryan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918427 Title: curtin: install flash-kernel in arm64 UEFI unexpected To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1918427/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1918427] Re: curtin: install flash-kernel in arm64 UEFI unexpected
* dann frazier <1918...@bugs.launchpad.net> [2021-03-17 20:40]: > On Wed, Mar 17, 2021 at 4:56 PM Ryan Harper <1918...@bugs.launchpad.net> > wrote: > > > > I still don't understand: > > > > 1) why does which not find flash-kernel if it's present in the ephemeral > > image (meaning it will also be present in the target filesystem > > 2) What is the problem with flash-kernel such that you need to dpkg-divert > > it? > > > > Generally, we do not want to include paths to binaries; we install > > Ubuntu and Centos, and possibly other distros which may not have the > > same path to this tools so I would like to understand what's not working > > to understand why we're hardcoding paths to binaries for dpkg-divert. > > In my POC patch, it is because we need to divert flash-kernel before > it is installed, *just in case* it gets installed as a dependency of Is flash-kernel supposed to be in the cloud-image or not? Is flash-kernel supposed to be in the target OS or not? > some other package (in our case it happened due to a kernel Recommends > relationship). We therefore can't use `which` to look up the path... > unless we continue to always install f-k in the ephemeral for the sole > purpose of looking up its path... but that seems to making assumptions > as well - i.e. that the ephemeral OS has the same paths as the target > OS. flash-kernel runs in the target OS; if it's installed in ephemeral environment thats a by-product of obtaining tools needed but not present in the ephemeral environment. curtin/deps.py runs to ensure the ephemeral environment has the needed tools to create whatever storage configuration curtin supports. In the squashfs images which do not have a kernel already installed curtin will install linux-image-generic to make *additional* kernel modules which may not be in the initrd that maas produces available. I'm not sure why the maas initrd doesn't yet have zfs kernel modules but that's typically the driver of the linux-image-generic install. w.r.t the dep on flash-kernel, if that is only supposed to run in the target image, then I agree we can remove lines 57-58 in curtin/dep/__init.py and not install the package (though it may still get pulled in via the kernel package install). Later durting curthooks stage, curtin will query the *target* os in install-missing-packages for expected packages needed in the target OS. Prior to installing packages in the target OS, curtin does attempt to divert initramfs triggering tools to prevent generating the initramfs more than once (this happens when we install a kernel package in the target OS and either updates or other packages trigger initramfs rebuilds). This is designed around the assumption that the initramfs generation tool is present in the image but not tied to the kernel pacakge. For Ubuntu this is initramfs-tools along with some arch specific tools. flash-kernel is the tool used on arm for non-uefi boot. I see a couple of options but I think I'd like to understand: 1) when is flash-kernel required? Curtin current expects flash-kernel to be needed when arch is arm and when booting non-uefi. Is this still accurate? 2) Is flash-kernel always installed in arm cloud images used by maas? 3) Is flash-kernel installed by packages due to Recommends when it's not needed? If so, are there packaging bugs that need fixing? Ryan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918427 Title: curtin: install flash-kernel in arm64 UEFI unexpected To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1918427/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918427] Re: curtin: install flash-kernel in arm64 UEFI unexpected
I still don't understand: 1) why does which not find flash-kernel if it's present in the ephemeral image (meaning it will also be present in the target filesystem 2) What is the problem with flash-kernel such that you need to dpkg-divert it? Generally, we do not want to include paths to binaries; we install Ubuntu and Centos, and possibly other distros which may not have the same path to this tools so I would like to understand what's not working to understand why we're hardcoding paths to binaries for dpkg-divert. Thanks, Ryan Ryan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918427 Title: curtin: install flash-kernel in arm64 UEFI unexpected To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1918427/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916325] Re: Overly strict NAME_REGEX rejects valid hostnames
Hi, Thank you for filing a bug and helping make Ubuntu better. I believe the regex restriction is happening in the Ubuntu Server Live Installer (subiquity). I've added that package to this bug. Here's the source code in question you're hitting. https://github.com/canonical/subiquity/blob/a76581cd2b973b55e55c6ac05b5bf47168493140/subiquity/ui/views/identity.py#L110 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1916325 Title: Overly strict NAME_REGEX rejects valid hostnames To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1916325/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916325] Re: Overly strict NAME_REGEX rejects valid hostnames
** Also affects: curtin Importance: Undecided Status: New ** Also 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/1916325 Title: Overly strict NAME_REGEX rejects valid hostnames To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1916325/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1918427] Re: curtin: install flash-kernel in arm64 UEFI unexpected
Hi Dan, Could you summarize the problem with flash-kernel and this system? * dann frazier <1918...@bugs.launchpad.net> [2021-03-15 18:25]: > Attached is a patch for curtin that works for me, though it could use > some cleanup. It installs flash-kernel in the same place GRUB gets > installed for EFI-based systems, which seems like the appropriate place. > Before installint it, it diverts /usr/sbin/flash-kernel so that flash- > kernel's postinst doesn't try (and fail) to flash a kernel that isn't > yet installed. There's existing code in enable_update_initramfs() that > will undo this diversion. I suspect we should refactor > disable_update_initramfs() somehow instead of duplicating this code like > I've done here. Looking at the patch, it looks like you could instead modify _update_initramfs_tools() to only return flash-kernel in the case that it's needed rather than for all aarch64. Alternatively, enable/disable_update_initramfs could take a force boolean which would perform the operation whether the tool is present or not (though I don't know if dpkg-divert cares about the presence of the binary-to-be-diverted). > > I've tested this w/ a locally-hacked squash image that has flash-kernel > purged and a PPA kernel that allows grub-efi-arm64 to satisfy the > bootloader Recommends. On an EFI-based system, flash-kernel never gets > installed. On a Moonshot m400, flash-kernel gets installed as expected. > > Once curtin has been updated with a fix like this, and MAAS has been > refreshed to include it, I think we should then be able to remove flash- > kernel from the arm64 cloud images. What's the criteria for determining if a particular arm instance requires flash-kernel or not? Ryan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918427 Title: curtin: install flash-kernel in arm64 UEFI unexpected To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1918427/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906280] Re: [SRU] Add support for disabling mlockall() calls in ovs-vswitchd
Thanks Corey for addressing this so quickly, I'll test it out and report back. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906280 Title: [SRU] Add support for disabling mlockall() calls in ovs-vswitchd To manage notifications about this bug go to: https://bugs.launchpad.net/charm-neutron-gateway/+bug/1906280/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 571481] Re: when slapd upgrade fails, later upgrade attempts overwrite saved backups of pre-upgrade configuration files
Fixed in 2.4.51+dfsg-1 i.e. groovy ** Changed in: openldap (Ubuntu) Assignee: Ryan Tandy (rtandy) => (unassigned) ** Changed in: openldap (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/571481 Title: when slapd upgrade fails, later upgrade attempts overwrite saved backups of pre-upgrade configuration files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/571481/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916509] [NEW] Update PAM and PAM modules
Public bug reported: I want to implement pam_faillock which replaces pam_tally2 but requires pam version >= 1.4.0 The ability to 'reliably' lock accounts after a certain number of failed attempts is a requirement of the NIST 800-171 controls implemented by many U.S. government agencies and contractors. ** Affects: pam (Ubuntu) Importance: Undecided Status: New ** Tags: libpam pam pam-modules -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1916509 Title: Update PAM and PAM modules To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1916509/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914438] Re: compiled without MPRIS
Can confirm this. The package on Focal doesn't have MPRIS working, even when toggled on in the settings. Must have been compiled without libsystemd-dev which should be added to the build-deps, and without the configure option CONFIG_MPRIS=y. Installing the build-deps for cmus along with libsystemd-dev, compiling with ./configure CONFIG_MPRIS=y, running make, sudo make install, results in cmus being installed with MPRIS support. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914438 Title: compiled without MPRIS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cmus/+bug/1914438/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906280] Re: [SRU] Add support for disabling mlockall() calls in ovs-vswitchd
I just got this ERROR on the install hook of ovn-dedicated-chassis 2021-02-12 04:44:00 INFO juju-log Invoking reactive handler: hooks/relations/tls-certificates/requires.py:109:broken:certificates 2021-02-12 04:44:00 INFO juju-log Invoking reactive handler: reactive/ovn_chassis_charm_handlers.py:28:enable_chassis_reactive_code 2021-02-12 04:44:00 DEBUG juju-log tracer: set flag charms.openstack.do-default-charm.installed 2021-02-12 04:44:00 DEBUG juju-log tracer: set flag charms.openstack.do-default-config.changed 2021-02-12 04:44:00 DEBUG juju-log tracer: set flag charms.openstack.do-default-config-rendered 2021-02-12 04:44:00 DEBUG juju-log tracer: set flag charms.openstack.do-default-update-status 2021-02-12 04:44:00 DEBUG juju-log tracer: set flag charms.openstack.do-default-upgrade-charm 2021-02-12 04:44:00 DEBUG juju-log tracer: set flag charms.openstack.do-default-certificates.available 2021-02-12 04:44:00 INFO juju-log Invoking reactive handler: reactive/ovn_chassis_charm_handlers.py:58:disable_openstack 2021-02-12 04:44:00 INFO juju-log Invoking reactive handler: reactive/layer_openstack.py:14:default_install 2021-02-12 04:44:01 DEBUG install Hit:1 http://archive.ubuntu.com/ubuntu focal InRelease 2021-02-12 04:44:02 DEBUG install Hit:2 http://archive.ubuntu.com/ubuntu focal-updates InRelease 2021-02-12 04:44:02 DEBUG install Hit:3 http://archive.ubuntu.com/ubuntu focal-security InRelease 2021-02-12 04:44:02 DEBUG install Hit:4 http://archive.ubuntu.com/ubuntu focal-backports InRelease 2021-02-12 04:44:03 DEBUG install Reading package lists... 2021-02-12 04:44:04 DEBUG juju-log tracer: set flag ovn-dedicated-chassis-installed 2021-02-12 04:44:04 ERROR juju-log Hook error: Traceback (most recent call last): File "/var/lib/juju/agents/unit-ovn-dedicated-chassis-0/.venv/lib/python3.8/site-packages/charms/reactive/__init__.py", line 74, in main bus.dispatch(restricted=restricted_mode) File "/var/lib/juju/agents/unit-ovn-dedicated-chassis-0/.venv/lib/python3.8/site-packages/charms/reactive/bus.py", line 390, in dispatch _invoke(other_handlers) File "/var/lib/juju/agents/unit-ovn-dedicated-chassis-0/.venv/lib/python3.8/site-packages/charms/reactive/bus.py", line 359, in _invoke handler.invoke() File "/var/lib/juju/agents/unit-ovn-dedicated-chassis-0/.venv/lib/python3.8/site-packages/charms/reactive/bus.py", line 181, in invoke self._action(*args) File "/var/lib/juju/agents/unit-ovn-dedicated-chassis-0/charm/reactive/layer_openstack.py", line 27, in default_install instance.install() File "lib/charm/openstack/ovn_dedicated_chassis.py", line 82, in install super().install() File "lib/charms/ovn_charm.py", line 287, in install self.options.mlockall_disabled): AttributeError: 'OVNDedicatedChassisConfigurationAdapter' object has no attribute 'mlockall_disabled' 2021-02-12 04:44:04 DEBUG install Traceback (most recent call last): 2021-02-12 04:44:04 DEBUG install File "/var/lib/juju/agents/unit-ovn-dedicated-chassis-0/charm/hooks/install", line 22, in 2021-02-12 04:44:04 DEBUG install main() 2021-02-12 04:44:04 DEBUG install File "/var/lib/juju/agents/unit-ovn-dedicated-chassis-0/.venv/lib/python3.8/site-packages/charms/reactive/__init__.py", line 74, in main 2021-02-12 04:44:04 DEBUG install bus.dispatch(restricted=restricted_mode) 2021-02-12 04:44:04 DEBUG install File "/var/lib/juju/agents/unit-ovn-dedicated-chassis-0/.venv/lib/python3.8/site-packages/charms/reactive/bus.py", line 390, in dispatch 2021-02-12 04:44:04 DEBUG install _invoke(other_handlers) 2021-02-12 04:44:04 DEBUG install File "/var/lib/juju/agents/unit-ovn-dedicated-chassis-0/.venv/lib/python3.8/site-packages/charms/reactive/bus.py", line 359, in _invoke 2021-02-12 04:44:04 DEBUG install handler.invoke() 2021-02-12 04:44:04 DEBUG install File "/var/lib/juju/agents/unit-ovn-dedicated-chassis-0/.venv/lib/python3.8/site-packages/charms/reactive/bus.py", line 181, in invoke 2021-02-12 04:44:04 DEBUG install self._action(*args) 2021-02-12 04:44:04 DEBUG install File "/var/lib/juju/agents/unit-ovn-dedicated-chassis-0/charm/reactive/layer_openstack.py", line 27, in default_install 2021-02-12 04:44:04 DEBUG install instance.install() 2021-02-12 04:44:04 DEBUG install File "lib/charm/openstack/ovn_dedicated_chassis.py", line 82, in install 2021-02-12 04:44:04 DEBUG install super().install() 2021-02-12 04:44:04 DEBUG install File "lib/charms/ovn_charm.py", line 287, in install 2021-02-12 04:44:04 DEBUG install self.options.mlockall_disabled): 2021-02-12 04:44:04 DEBUG install AttributeError: 'OVNDedicatedChassisConfigurationAdapter' object has no attribute 'mlockall_disabled' -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906280 Title: [SRU] Add support for disabling mlockall() calls in ovs-vswitchd To manage
[Bug 1914655] [NEW] bluetoothd daemon will not start, gives error: bluetoothd[15530]: src/main.c:parse_controller_config() Key file does not have group “Controller”
Public bug reported: I have been trying to get internal microphone, and broken bluetooth working for some time now, and nothing is working. I cannot start the bluetoothd daemon. journalctl -xe gives: Feb 04 23:21:08 G14 bluetoothd[15530]: src/main.c:parse_controller_config() Key file does not have group “Controller” Feb 04 23:21:08 G14 bluetoothd[15530]: src/main.c:main() Unable to get on D-Bus It is for this reason that no other services will start, because the bluetooth daemon doesn't seem to. I am on kernel 5.10.4-051004-generic, Ubuntu 20.10. ** Affects: grub2-signed (Ubuntu) Importance: Undecided Status: New ** Tags: bluetoothd -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914655 Title: bluetoothd daemon will not start, gives error: bluetoothd[15530]: src/main.c:parse_controller_config() Key file does not have group “Controller” To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/1914655/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1868177] Re: /snap/subiquity/1561/usr/bin/subiquity:ValueError:main:wrapper:log_time:block_meta:meta_clear:clear_holders:wipe_superblock:_wipe_superblock:wipe_volume:quick_zero:zero_file_at_o
Huh, Never seen partitions smaller than 1MB... Curtin could truncate the requested size to the greater of 1MB or size of partition. On Tue, Feb 2, 2021 at 4:05 PM dann frazier <1868...@bugs.launchpad.net> wrote: > I worked around the MAAS deployment issue by manually removing all > partitions (parted -- mklabel gpt). > > ** Also affects: curtin (Ubuntu) >Importance: Undecided >Status: New > > -- > You received this bug notification because you are subscribed to > subiquity. > Matching subscriptions: curtin-bugs, subiquity-bugs > https://bugs.launchpad.net/bugs/1868177 > > Title: > > /snap/subiquity/1561/usr/bin/subiquity:ValueError:main:wrapper:log_time:block_meta:meta_clear:clear_holders:wipe_superblock:_wipe_superblock:wipe_volume:quick_zero:zero_file_at_offsets > > To manage notifications about this bug go to: > https://bugs.launchpad.net/subiquity/+bug/1868177/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868177 Title: /snap/subiquity/1561/usr/bin/subiquity:ValueError:main:wrapper:log_time:block_meta:meta_clear:clear_holders:wipe_superblock:_wipe_superblock:wipe_volume:quick_zero:zero_file_at_offsets To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1868177/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912844] Re: Bond with OVS bridging RuntimeError: duplicate mac found!
Thanks for doing most of the digging here @Oddbloke; I suspect as with bond and bridges for ovs, we'll need a special case to check if a vlan entry is also OVS, much like we did for bonds/bridges: https://github.com/canonical/cloud-init/pull/608/files So our is_vlan change will need to see if link device is OVS and if so then say it's a vlan as well (since the DEVTYPE doesn't match) or something to that effect. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912844 Title: Bond with OVS bridging RuntimeError: duplicate mac found! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1912844/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908761] Re: Can't deploy using root XFS partition using 18.04
You might just mark this bug duplicate of the other so we can close both if this fixes things; and if so, I can update our vmtest which exercises this path. Note this is broken all the way back through Xenial. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908761 Title: Can't deploy using root XFS partition using 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1908761/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908761] Re: Can't deploy using root XFS partition using 18.04
@Eric Yeah, I *think* that will work; I believe at the time I manually performed that step and it worked. I'm not sure w.r.t Secure Boot and shim-signed; Maybe @vorlon can confirm if the xfs grub2 module is signed/included in shim-signed? > As follow: > https://salsa.debian.org/grub-team/grub/-/commit/01f1eee93acd4113475b403f80661cf651fbcc00 Ah, that's adding it to the signed bits... that looks promising. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908761 Title: Can't deploy using root XFS partition using 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1908761/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1910140] [NEW] Alignment of password field in 20.04 login screen not in centre
Public bug reported: ubuntu is now launching slowly for me it gives me a black screen at launch that shows the result of a system file check then it jumps to the login screen which seems strange as the alignment of the password field appears now on the left of the screen instead of in the centre as it used to be then ubuntu desktop starts, the screen seems to be shifting or 3 seconds then it adjusts itself to normal what should I reinstall to fix this please ? thanks. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jan 4 19:35:37 2021 DisplayManager: lightdm InstallationDate: Installed on 2021-01-01 (3 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (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/1910140 Title: Alignment of password field in 20.04 login screen not in centre To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1910140/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1715861] Re: r592 & r852 IRQ: DMA errors cause excessive log file entries
Still happens in kernel 5.8. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1715861 Title: r592 & r852 IRQ: DMA errors cause excessive log file entries To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715861/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908140] Re: Bond DHCP fails on Ubuntu Server 20.04 netplan
Thank you for all of your help! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908140 Title: Bond DHCP fails on Ubuntu Server 20.04 netplan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1908140/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908140] Re: Bond DHCP fails on Ubuntu Server 20.04 netplan
The BIOS update does indeed fix the type interface number issue. This ticket can be marked as a duplicate of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1578141 and closed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908140 Title: Bond DHCP fails on Ubuntu Server 20.04 netplan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1908140/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908140] Re: Bond DHCP fails on Ubuntu Server 20.04 netplan
There's a BIOS update available for my board. I'll install this and hopefully I won't need a SW fix. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908140 Title: Bond DHCP fails on Ubuntu Server 20.04 netplan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1908140/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908140] Re: Bond DHCP fails on Ubuntu Server 20.04 netplan
I thought this could be related to https://bugzilla.kernel.org/show_bug.cgi?id=199813. Indeed dmidecode -t 41 shows there are two interfaces for type interface 1 and two for 2. ** Bug watch added: Linux Kernel Bug Tracker #199813 https://bugzilla.kernel.org/show_bug.cgi?id=199813 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908140 Title: Bond DHCP fails on Ubuntu Server 20.04 netplan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1908140/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908140] Re: Bond DHCP fails on Ubuntu Server 20.04 netplan
> your bonded links are down; nothing will happen until they are brought
up.
Yes, I figured as such. I've already tried to bring up eth0, eth1, and
bond0 via ip, ifup, and ifconfig to no success.
> your pasted log appears incomplete since i see no output for eth0 or
eth1; please paste or attach your entire log.
This is the entire log since reboot. If I look at the journal from
previous boots, there are mentions of eth0 and eth1, as well as eno1 and
eno2.
$ networkctl list
IDX LINKTYPE OPERATIONAL SETUP
1 lo loopback carrier unmanaged
2 eno1etheroff unmanaged
3 eno2etheroff unmanaged
4 eth0etheroff pending
5 eth1etheroff pending
6 bond0 bond no-carrier configured
7 docker0 bridge no-carrier unmanaged
After doing ip link set dev {eth0,eth1} up, they change from off to
degraded in networkctl list. Attempting the same on bond0 afterward does
nothing.
$ networkctl status -n 40
* State: no carrier
Address: 172.17.0.1 on docker0
Dec 14 21:29:44 lore systemd[1]: Starting Network Service...
Dec 14 21:29:44 lore systemd-networkd[852]: bond0: netdev ready
Dec 14 21:29:44 lore systemd-networkd[852]: Enumeration completed.
Dec 14 21:29:44 lore systemd[1]: Started Network Service.
Dec 14 21:29:44 lore systemd-networkd[852]: bond0: IPv6 successfully enabled
Dec 14 21:29:44 lore systemd-networkd[852]: bond0: Link UP
Dec 14 21:31:44 lore systemd[1]: systemd-networkd-wait-online.service: Main
process exited, code=exited, status=1/FAILURE
Dec 14 21:31:44 lore systemd[1]: systemd-networkd-wait-online.service: Failed
with result 'exit-code'.
Dec 14 21:31:44 lore systemd[1]: Failed to start Wait for Network to be
Configured.
Dec 14 21:31:50 lore systemd-networkd[852]: rtn1: received neighbor for link
'7' we don't know about, ignoring.
Dec 14 21:31:50 lore systemd-networkd[852]: rtn1: received neighbor for link
'7' we don't know about, ignoring.
Dec 14 21:31:50 lore systemd-networkd[852]: rtn1: received neighbor for link
'7' we don't know about, ignoring.
Dec 14 21:31:50 lore systemd-networkd[852]: rtn1: received neighbor for link
'7' we don't know about, ignoring.
Dec 14 21:31:50 lore systemd-networkd[852]: docker0: Link UP
Dec 15 18:13:43 lore systemd-networkd[856]: eth1: Link IP
Dec 15 18:13:45 lore systemd-networkd[856]: eth0: Ganied carrier
Dec 15 18:13:47 lore systemd-networkd[856]: eth0: Gained IPv6LL
Dec 15 18:13:47 lore systemd-networkd[856]: eth1: Ganied carrier
Dec 15 18:13:48 lore systemd-networkd[856]: eth1: Gained IPv6LL
Dec 15 18:15:13 lore systemd-networkd[856]: bond0: Link DOWN
Dec 15 18:15:41 lore systemd-networkd[856]: eth0: Link DOWN
Dec 15 18:15:41 lore systemd-networkd[856]: eth0: Lost carrier
Dec 15 18:15:45 lore systemd-networkd[856]: eth1: Link DOWN
Dec 15 18:15:45 lore systemd-networkd[856]: eth1: Lost carrer
All of the lines from today (Dec 15) correspond to my attempts to bring
interfaces up as mentioned above, then bringing them back down after it
failed.
> networkctl status bond0 eth0 eth1
* 4: eth0
Link File: n/a
Network File: n/a
Status: off (pending)
HW Address: 0c:c4:7a:c6:c6:a2 (Super Micro Computer, Inc.)
MTU: 1500 (min: 68, max: 9710)
Queue Length (Tx/Rx): 64/64
Auto negotiaition: yes
Speed: n/a
Port: tp
Dec 14 21:29:42 lore systemd-udevd[588]: eth0: Failed to rename network
interface 4 from 'eth0' to 'eno1': File exists
Dec 14 21:29:42 lore systemd-udevd[588]: eth0: Failed to process device,
ignoring: File exists
Dec 15 18:13:45 lore systemd-networkd[856]: eth0: Ganied carrier
Dec 15 18:13:47 lore systemd-networkd[856]: eth0: Gained IPv6LL
Dec 15 18:15:41 lore systemd-networkd[856]: eth0: Link DOWN
Dec 15 18:15:41 lore systemd-networkd[856]: eth0: Lost carrier
* 5: eth1
Link File: n/a
Network File: n/a
Status: off (pending)
HW Address: 0c:c4:7a:c6:c6:a2 (Super Micro Computer, Inc.)
MTU: 1500 (min: 68, max: 9710)
Queue Length (Tx/Rx): 64/64
Auto negotiaition: yes
Speed: n/a
Port: tp
Dec 14 21:29:42 lore systemd-udevd[588]: eth1: Failed to rename network
interface 5 from 'eth1' to 'eno2': File exists
Dec 14 21:29:42 lore systemd-udevd[588]: eth1: Failed to process device,
ignoring: File exists
Dec 15 18:13:43 lore systemd-networkd[856]: eth1: Link IP
Dec 15 18:13:47 lore systemd-networkd[856]: eth1: Ganied carrier
Dec 15 18:13:48 lore systemd-networkd[856]: eth1: Gained IPv6LL
Dec 15 18:15:45 lore systemd-networkd[856]: eth1: Link DOWN
Dec 15 18:15:45 lore systemd-networkd[856]: eth1: Lost carrer
* 6: bond0
Link File: /usr/lib/systemd/network/99-default.link
Network File: /run/systemd/network/10-netplan-bond0.network
Type: bond
State: off (configured)
Driver: bonding
[Bug 1908140] [NEW] Bond DHCP fails on Ubuntu Server 20.04 netplan
Public bug reported: I recently installed Ubuntu Server 20.04 to replace an ESXi server. During the installation, I configured a bonded interface for two ethernet interfaces. I configured the bond on my ZyXel GS1900-8 as a static LAG. During the setup process, the link came up successfully and was leased an IP via DHCP. All subsequent boots have failed to acquire an IP address for the bonded interface. Sometimes, if I allow dhcp4 on the enslaved interfaces, and run sudo dhclient -r && sudo dhclient, the enslaved interfaces will be leased an IP address _and_ the bond will get an IP address. I know this is not proper as dhclient and systemd-networkd do not mix. Also, I would like to configure this as a LACP bond instead. I have enabled LACP on the switch with priority 65535 and "IP/MAC address" load balancing algorithm, switched the LAG from static to LACP, and altered netplan to use the 802.3ad bond mode. Please let me know what, if anything, I'm doing wrong here. I've looked around at as many netplan DHCP bond posts here as I could find to no avail. See below for configuration files and command outputs. I cannot give you the output of `lsb_release -rd` as the package is not installed and there's no connection to install it. $ cat /etc/netplan/00-bond.yaml network: version: 2 renderer: networkd ethernets: eth0: dhcp4: false eth1: dhcp4: false bonds: bond0: dhcp4: true interfaces: - eth0 - eth1 parameters: mode: 802.3ad $ sudo journalctl -b -u systemd-networkd Dec 14 08:06:47 lore systemd[1]: Starting Network Service... Dec 14 08:06:47 lore systemd-networkd[852]: bond0: netdev ready Dec 14 08:06:47 lore systemd-networkd[852]: Enumeration completed. Dec 14 08:06:47 lore systemd[1]: Started Network Service. Dec 14 08:06:47 lore systemd-networkd[852]: bond0: IPv6 successfully enabled Dec 14 08:06:47 lore systemd-networkd[852]: bond0: Link UP Dec 14 08:08:53 lore systemd-networkd[852]: rtn1: received neighbor for link '7' we don't know about, ignoring. Dec 14 08:08:53 lore systemd-networkd[852]: rtn1: received neighbor for link '7' we don't know about, ignoring. Dec 14 08:08:53 lore systemd-networkd[852]: rtn1: received neighbor for link '7' we don't know about, ignoring. Dec 14 08:08:53 lore systemd-networkd[852]: rtn1: received neighbor for link '7' we don't know about, ignoring. Dec 14 08:08:53 lore systemd-networkd[852]: docker0: Link UP $ sudo ip a 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 eno1: mtu 1500 qdisk noop state DOWN group default qlen 1000 link/ether 0c:c4:7a:c6:c3:46 brd ff:ff:ff:ff:ff:ff eno2: mtu 1500 qdisk noop state DOWN group default qlen 1000 link/ether 0c:c4:7a:c6:c3:47 brd ff:ff:ff:ff:ff:ff eth0: mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 0c:c4:7a:c6:c6:a2 brd ff:ff:ff:ff:ff:ff eth1: mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 0c:c4:7a:c6:c6:a3 brd ff:ff:ff:ff:ff:ff bond0: mtu 1500 qdisk noqueue state DOWN group default qlen 1000 link/ether 52:8b:2c:cc:a0:15 brd ff:ff:ff:ff:ff:ff docker0: mtu 1500 qdisc noqueue state DOWN group default link/ether 02:42:26:1c:1b:39 brd ff:ff:ff:ff:ff:ff inet 172.17.0.1/16 brd 172.17.255.255 scope global docker 0 valid_lft forever preferred_lft forever $ cat /run/systemd/network/10-netplan-bond0.netdev [NetDev] Name=bond0 Kind=bond [Bond] Mode=802.3ad $ cat /run/systemd/network/10-netplan-bond0.network [Match] Name=bond0 [Network] DHCP=ipv4 LinkLocalAddressing=ipv6 ConfigureWithoutCarrier=yes [DHCP] RouteMetric=100 UseMTU=true $ cat /run/systemd/network/10-netplan-eth0.network [Match] Name=eth0 [Network] LinkLocalAddressing=no Bond=bond0 $ cat /run/systemd/network/10-netplan-eth1.network [Match] Name=eth1 [Network] LinkLocalAddressing=no Bond=bond0 $ cat /proc/net/bonding/bond0 Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011) Bonding Mode: IEEE 802.3ad Dynamic link aggregation Transmit Hash Policy: layer2 (0) MII Status: down MII Polling Interval (ms): 100 Up Delay (ms): 0 Down Delay (ms): 0 Peer Notification Delay (ms): 0 802.3ad info LACP rate: slow Min links: 0 Aggregator selection policy (ad_select): stable ** Affects: systemd (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/1908140 Title: Bond DHCP fails on Ubuntu Server 20.04 netplan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1908140/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1907107] Re: cloud-init runs too late at first startup after ubuntu autoinstall
* eoli3n <1907...@bugs.launchpad.net> [2020-12-08 13:30]: > If i run autoinstall with that user-data file, autoinstall doesn't run > and subiquity prompt for language setting. > > #cloud-config > runcmd: > - systemctl daemon-reload > - systemctl restart gdm3 > autoinstall: > version: 1 > packages: > - gdm3 > locale: fr_FR.UTF-8 > user-data: > timezone: Europe/Paris > refresh-installer: > update: yes > identity: > hostname: localhost > username: premier > password: $1$l03JsARH$DCxHdrzUH8SRmeDk3/3rU1 > > If I use that user-data file, runcmd seems not to run at the end of > cloud-config after first reboot. > > #cloud-config > autoinstall: > version: 1 > packages: > - gdm3 > locale: fr_FR.UTF-8 > user-data: > timezone: Europe/Paris > refresh-installer: > update: yes > identity: > hostname: localhost > username: premier > password: $1$l03JsARH$DCxHdrzUH8SRmeDk3/3rU1 > runcmd: > - systemctl daemon-reload > - systemctl restart gdm3 > > How should i use runcmd ? I think part of this confusion is that subiquity has it's autoinstall format[1], which looks rather similar to cloud-config, but it's the same and depending on *where* you need things to run (say in the installer environment, or on firstboot) then you need to adjust the config structure. I believe if you want to pass a user-data section in the autoinstall file[2]. It would look like this: #cloud-config autoinstall: version: 1 locale: fr_FR.UTF-8 refresh-installer: update: yes user-data: locale: fr_FR.UTF-8 hostname: localhost users: - name: premier gecos: premier passwd: "$1$l03JsARH$DCxHdrzUH8SRmeDk3/3rU1" shell: /bin/bash groups: "admin,sudo" lock_passwd: False packages: - gdm3 timezone: Europe/Paris runcmd: - systemctl daemon-reload - systemctl restart gdm3 The autoinstaller will merge the 'user-data' section of the autoinstall cloud-config it normally generates and then place this config in the target OS so that in first boot cloud init will do all of the things you need. > > FYI, even if i restart gmd3 manually with Fr locale set and generated, > it is still in english. Then only timezone test is ok, if i > restart manually after cloud-config, clock is well configured. Looking at the config I think if you use the user-data key in autoinstall conf you can be sure that all of the required bits (locale, timezone, packages, etc) do what's needed. 1. https://ubuntu.com/server/docs/install/autoinstall-reference 2. https://github.com/CanonicalLtd/subiquity/blob/main/examples/autoinstall-user-data.yaml Ryan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907107 Title: cloud-init runs too late at first startup after ubuntu autoinstall To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1907107/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1907107] Re: cloud-init runs too late at first startup after ubuntu autoinstall
* eoli3n <1907...@bugs.launchpad.net> [2020-12-08 11:50]: > > I can say that the Ubuntu Server installer isn't typically used to install > > Ubuntu Desktop. > I use it because i can't find any netboot installer which supports > autoinstall and EFI installation. I used legacy netboot (60MB) for my > kickstart install but now i need to autoinstall an EFI system. OK > > > have you looked at just using the Ubuntu Desktop installer with OEM > > mode? > > https://help.ubuntu.com/community/Ubuntu_OEM_Installer_Overview > I just want a way to automate installation from a pxe boot, with an > "answer file", i did with kickstart in a "script" model, i want to do > the same with autoinstall. Sure > > cloud-init is configured to write to the console by default; that's > > why you see output from cloud-init on your tty. > It seems to me a little bit buggy, don't you think ? Well, that's not a bug. It's the default configuration for cloud-init as it runs in places where there's no access to tty or console; just the output that a cloud platform may show you. You may want to remove/override the StandardOutput setting in the cloud-init service units (cloud-init-local, cloud-init, cloud-config, cloud-final). The default is to log to both journal and console. # Output needs to appear in instance console output StandardOutput=journal+console It's something that subiquity could configure differently since in this scenario, the target system would have user-facing console. > I think cloud-config.service should defaulty have a stronger > dependency as Before=getty.target for exemple. Possibly. If you want to test that out, you can add this as a drop-in conf, before for boot the target OS you can: mkdir -p /target/lib/systemd/system/cloud-config.service.d echo -e "[Unit]\nBefore=getty.target > /target/lib/systemd/cloud-config.service.d/10-before-getty.conf > > Why don't the installer configure everything during the install process > ? Generating locales, write /etc/default/locale and set /etc/timezone > are not hard tasks. Even if cloud-init embeed those configuration, you > could tell the installer to setup what in cloud-config as default > config. The design is based on the idea of a template image. The Ubuntu server image is ready to boot and on first boot cloud-init handles the tasks to "instantiate the image". Doesn't the autoinstall input generatea cloud-init config that configures these things? > > If you can't avoid that first startup scripts, you should start as early > as possible in the init process, before any process that could use what > it setup/modify. Does that seem illogical ? It's not. Cloud-init does start up as early as possible (after local fs is mounted). However some tasks require to be run later; for example package install cannot run without networking being configured. At this point, I don't think there is a bug in cloud-init. For your use-case, you may need change some of the defaults that are already cofigured in the image. It's probably worth looking at your working solution to see what, if anything, could be configured by subiquity; or if it makes sense to tweak a default. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907107 Title: cloud-init runs too late at first startup after ubuntu autoinstall To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1907107/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
