[Bug 2066406] [NEW] package grub-pc 2.04-1ubuntu26.17 failed to install/upgrade: installed grub-pc package post-installation script subprocess returned error exit status 1
Public bug reported: fresh install ubuntu 20.04 then ran apt-get update apt-get upgrade ProblemType: Package DistroRelease: Ubuntu 20.04 Package: grub-pc 2.04-1ubuntu26.17 ProcVersionSignature: Ubuntu 5.15.0-67.74~20.04.1-generic 5.15.85 Uname: Linux 5.15.0-67-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed May 22 12:16:15 2024 ErrorMessage: installed grub-pc package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2024-05-22 (0 days ago) InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316) ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-67-generic root=UUID=bfbf1d81-45fd-4e5c-a2ef-f5af1a4a1ddc ro quiet splash Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.10 SourcePackage: grub2 Title: package grub-pc 2.04-1ubuntu26.17 failed to install/upgrade: installed grub-pc package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub2 (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/2066406 Title: package grub-pc 2.04-1ubuntu26.17 failed to install/upgrade: installed grub-pc package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/2066406/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2066066] Re: cloud-init startup failure with Python 3.9.5, Ubuntu Focal
** Also affects: cloud-init (Ubuntu Focal) 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/2066066 Title: cloud-init startup failure with Python 3.9.5, Ubuntu Focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2066066/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065546] Re: postfix configuration must be set on 24.04 before apt package manager can be used
There's no postfix bug described here. ** Changed in: postfix (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065546 Title: postfix configuration must be set on 24.04 before apt package manager can be used To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/emacs/+bug/2065546/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065434] [NEW] [USB-Audio - ALC1220-VB-DT, playback] fails after a while
Public bug reported: Audio will work fine for a period of time, then randomly, you will hear static, and then every sound effect is a static pop. The auto complete "miss" sound in terminal is awful for example. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 6.5.0-28.29~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri May 10 13:08:18 2024 InstallationDate: Installed on 2020-04-28 (1473 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_Card: HD Webcam C910 - USB Device 0x46d:0x821 Symptom_PulseAudioLog: Symptom_Type: Sound works for a while, then breaks Title: [USB-Audio - ALC1220-VB-DT, playback] fails after a while UpgradeStatus: Upgraded to jammy on 2023-04-27 (378 days ago) dmi.bios.date: 03/04/2022 dmi.bios.release: 16.3 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1603 dmi.board.asset.tag: Default string dmi.board.name: PRIME TRX40-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1603:bd03/04/2022:br16.3:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMETRX40-PRO:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS ** Affects: alsa-driver (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/2065434 Title: [USB-Audio - ALC1220-VB-DT, playback] fails after a while To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2065434/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064877] Re: Resume from Standby vmnet1/8 connected instead of Wired LAN
Same issue for me. Was using a script for Proton VPN loaded into the LAN connection. Deleted the custom connection and rebooted. VMnet1 and 8 stopped trying to connect, and as a bonus now my KDE weather widget is working again. Will use the GUI ProtonVPN application to make changes to VPN. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064877 Title: Resume from Standby vmnet1/8 connected instead of Wired LAN To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/2064877/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973098] Re: [i915] Intermittent freezing and LSPCON init failed kernel messages
Hoping to see the issue go away with the new Ubuntu 24.04 on a HP HP ProDesk 400 G3 DM/82A5 and it uses Intel HD Graphics 630. But nope still happens. I needed to pull the power for a bit before screen would come back properly. Is there additional information needed to troubleshoot the issue? 024-04-25T19:09:21.155484-05:00 ProDesk400 kernel: i915 :00:02.0: [drm] *ERROR* LSPCON mode hasn't settled 2024-04-25T19:09:21.429475-05:00 ProDesk400 kernel: i915 :00:02.0: [drm] *ERROR* LSPCON mode change timed out 2024-04-25T19:09:21.429481-05:00 ProDesk400 kernel: i915 :00:02.0: [drm] *ERROR* LSPCON mode change failed 2024-04-25T19:09:21.429482-05:00 ProDesk400 kernel: i915 :00:02.0: [drm] *ERROR* LSPCON resume failed 2024-04-25T19:09:21.438472-05:00 ProDesk400 kernel: i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful 2024-04-25T19:09:21.456511-05:00 ProDesk400 kernel: i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful 2024-04-25T19:09:23.289474-05:00 ProDesk400 kernel: i915 :00:02.0: [drm] *ERROR* LSPCON mode hasn't settled 2024-04-25T19:09:23.572475-05:00 ProDesk400 kernel: i915 :00:02.0: [drm] *ERROR* LSPCON mode change timed out 2024-04-25T19:09:23.572480-05:00 ProDesk400 kernel: i915 :00:02.0: [drm] *ERROR* LSPCON mode change failed 2024-04-25T19:09:23.572482-05:00 ProDesk400 kernel: i915 :00:02.0: [drm] *ERROR* LSPCON resume failed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973098 Title: [i915] Intermittent freezing and LSPCON init failed kernel messages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973098/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063491] [NEW] Cannot restore files using duply version included with Noble
Public bug reported: The version of duply (v2.4.1) included with Noble Numbat is not able to restore files. I get this error when attempting a fetch (restore) operation: --- Start running command FETCH at 2024-04-26 05:45:23.076 --- CommandLineError: Option '--file-to-restore was changed in 2.0.0. --file-to-restore to --path-to-restore --do-not-restore-ownership to --no-restore-ownership Enter 'duplicity --help' for help screen. 2024-04-26 05:45:24.020 Task 'FETCH' failed with exit code '23'. --- Finished state FAILED 'code 23' at 2024-04-26 05:45:24.020 - Runtime 00:00:00.944 --- It appears that the version 2.4.1 is incompatible with the included version of duplicity (2.1.4). If I use version 2.5.2 of duply (the latest available on the website), I can restore files successfully. ** Affects: duply (Ubuntu) Importance: Undecided Status: New ** Tags: duplicity duply -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063491 Title: Cannot restore files using duply version included with Noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/duply/+bug/2063491/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061529] [NEW] NameError: name 'yubikey' is not defined
Public bug reported: Running ykman-gui on 22.04 currently shows the following. ykman works fine. NameError: name 'yubikey' is not defined ) qml: qrc:/qml/YubiKey.qml:208: TypeError: Cannot read property 'success' of undefined "PyOtherSide error: Traceback (most recent call last):\n\n File \"\", line 1, in \n\nNameError: name 'yubikey' is not defined\n" qml: Function not found: 'yubikey.controller.refresh' (Traceback (most recent call last): File "", line 1, in NameError: name 'yubikey' is not defined ) qml: qrc:/qml/YubiKey.qml:208: TypeError: Cannot read property 'success' of undefined "PyOtherSide error: Traceback (most recent call last):\n\n File \"\", line 1, in \n\nNameError: name 'yubikey' is not defined\n" qml: Function not found: 'yubikey.controller.refresh' (Traceback (most recent call last): File "", line 1, in NameError: name 'yubikey' is not defined ) qml: qrc:/qml/YubiKey.qml:208: TypeError: Cannot read property 'success' of undefined ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: yubikey-manager-qt 1.2.5-1build2 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 Uname: Linux 6.8.0-11-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Apr 15 09:56:39 2024 InstallationDate: Installed on 2024-01-19 (87 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: yubikey-manager-qt UpgradeStatus: Upgraded to noble on 2024-03-06 (40 days ago) ** Affects: yubikey-manager-qt (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061529 Title: NameError: name 'yubikey' is not defined To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yubikey-manager-qt/+bug/2061529/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: Fwd: [Bug 2060275] [NEW] pmproxy crash at startup in libpcp_web.so.1
Hi Martin,
On Tue, Apr 9, 2024 at 6:09 PM Martin Pitt wrote:
>
> Nathan Scott [2024-04-09 17:30 +1000]:
> > > It's not really unknown, it's "just" a file conflict:
> >
> > Yeah - the unknown bit for me is "why tho" - I cannot see conflicting
> > files in those packages that would have any debug symbols (there's
> > some common directories... but no binaries shared AFAICS).
> >
> > > | dpkg: error processing archive
> > > build/deb/pcp-pmda-infiniband-dbgsym_6.2.1-0.20240409.f312285_amd64.deb
> > > (--install):
> > > | trying to overwrite
> > > '/usr/lib/debug/.build-id/57/02df011cfaf166b948e1fefde236eaf3a6ee65.debug',
> > > which is also in package pcp-dbgsym 6.2.1-0.20240409.f312285
> > > |
> > > | dpkg: error processing archive
> > > build/deb/pcp-testsuite-dbgsym_6.2.1-0.20240409.f312285_amd64.deb
> > > (--install):
> > > | trying to overwrite
> > > '/usr/lib/debug/.build-id/17/6edc7e590f766a2ea87b5decaeb994d7c48d24.debug',
> > > which is also in package pcp-dbgsym 6.2.1-0.20240409.f312285
> > >
> > > I.e. these are shipped in two different packages.
> >
> > "these"?
>
> These two files, i.e.
> /usr/lib/debug/.build-id/57/02df011cfaf166b948e1fefde236eaf3a6ee65.debug
> exists
> both in pcp-pmda-infiniband-dbgsym and pcp-dbgsym. Presumably they shouldn't
> be
> in the latter.
Yep, understood - but again, I'm not understanding why. AFAICS, there
are no files with the same names or contents between those packages.
> > OK ... so that's pointing towards v3 archives a little bit, good.
> >
> > > > The limited stack we have suggests we're in pmproxy log discovery
> > > > code, in an inotify/libuv event, which does have v3-specific code.
> > > >
> > > > For those who can reproduce this, it'd be worth experimenting and
> > > > setting the following field back to 2 ... (requires pmlogger restart).
> > > >
> > > > $ grep PCP_ARCHIVE_VERSION /etc/pcp.conf
> > > > PCP_ARCHIVE_VERSION=3
>
> I created https://github.com/cockpit-project/cockpit/pull/20275 with an x120
> test amplification, and intererestinly there the overwhelming majority of test
> runs actually crashes there. So with that I have a fairly high confidence in
> the significance of test results when trying a change.
>
> I tested with
>
> sed -i 's/PCP_ARCHIVE_VERSION=3/PCP_ARCHIVE_VERSION=2/' /etc/pcp.conf
>
> This runs on image preparation, i.e. clean /var/log and no daemons running.
> The
> VM is freshly booted for each test, so no running pmlogger. There is no
> observed change, it still crashes the same way and with the same frequency
> ("almost every time").
OK, so it's not related to the recent v3 archive changes then.
I have a fairly recent Debian VM locally - I tried reproducing the problem
there but had no luck, it always starts fine and runs fine. Tried running it
under valgrind too just in case, but again nothing.
We also don't see this issue on Fedora, CentOS or RHEL and SuSE are
also not reporting this. Since (I think) all Debian versions are fine (can we
confirm?) it might be a Ubuntu-specific issue. Are there patches or some
global compiler option(s) unique to Ubuntu versions where this is failing?
Otherwise, I'm fresh out of ideas.
I can't really justify time chasing this any further - I think we'll need some
assistance from Ubuntu folk to help us gain additional insights.
cheers.
--
Nathan
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060275
Title:
pmproxy crash at startup in libpcp_web.so.1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pcp/+bug/2060275/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971469] Re: FTBFS against openssl 3
** Changed in: cyrus-imapd (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971469 Title: FTBFS against openssl 3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cyrus-imapd/+bug/1971469/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060717] [NEW] colcon-core argument parsing is broken by recent changes to Python 3.11+
Public bug reported: Recent changes to Python which have been backported to Python 3.11 and 3.12 break colcon argument parsing due to a dependency on private API in argparse. A fix has been released in colcon-core 0.16.1 which should be backported to any platforms which will receive the updated Python releases. The python3-colcon-core package currently in Ubuntu Noble is suffering from this issue now. https://github.com/colcon/colcon-core/pull/635 ** Affects: ros2-colcon-core (Ubuntu) Importance: Undecided Status: Confirmed ** Patch added: "0001-Fix-argument-parsing-in-newer-Python.patch" https://bugs.launchpad.net/bugs/2060717/+attachment/5762890/+files/0001-Fix-argument-parsing-in-newer-Python.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060717 Title: colcon-core argument parsing is broken by recent changes to Python 3.11+ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ros2-colcon-core/+bug/2060717/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874662] Re: Corrupted installation medium
I just downloaded the ISO, and used that ISO to start a Virtualbox guest installation and got this error. No flash drives or physical mediums. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874662 Title: Corrupted installation medium To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1874662/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058578] Re: Add support for several cs35l41 amplifier devices (laptop audio support)
I don't know how that got lost... "git clone" should be: git clone https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058578 Title: Add support for several cs35l41 amplifier devices (laptop audio support) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.5/+bug/2058578/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058578] [NEW] Add support for several cs35l41 amplifier devices (laptop audio support)
Public bug reported: Support for the cs35l41_hda_property table has been already been backported to hwe-6.5-next: commit eec052d5cff271d7bf6854f28c62c4a6650c379b (HEAD -> hwe-6.5-next, tag: Ubuntu-hwe-6.5-6.5.0-27.28_22.04.1, origin/hwe-6.5-next) Support for several devices has been merged to torvalds/linux v6.8 tag: commit e8f897f4afef0031fe618a8e94127a0934896aba (HEAD, tag: v6.8) It would be great if the following commits for sound/pci/hda/cs35l41_hda_property.c could be cherry-picked for release in the near future (listed newest to oldest): b603d95692e47dc6f5f733e93c3841dc0c01e624 706c1fa1ab09f11a131fc4d699ce4c0224b1cb2d be220d2e5544ff094142d263db5cf94d034b5e39 c16dfab33f99fc3ff43d48253bc2784ccb84c1de 8c14dbf36424eb751d70c15f9a671549390057b2 7d65d70161ef75a3991480c91668ac11acedf211 ba7053b4b4a4ddcf530fa2b897e697004715d086 d110858a6925827609d11db8513d76750483ec06 ee694e7db47e1af00ffb29f569904a9ed576868f 916d051730ae48aef8b588fd096fefca4bc0590a ed7326a24a1a9af65fafefd86b505e7c3b968f6d 2b35b66d82dc4641ba60f7f3c36c0040eedb74e2 b257187bcff4bccc9e7a8f1b8a1a5526ff815af1 b592ed2e1d78a475f781802e441c499ab446975b 8c4c216db8fb84be9c4ca60d72b2066cf28f 2e6f979037d5ae35c0ed38e2b63e9876eb7bc65f I am running on KDE neon 6.0 release 22.04 Linux Scott-Laptop 6.5.0-26-generic #26~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Tue Mar 12 10:22:43 UTC 2 x86_64 x86_64 x86_64 GNU/Linux This works fine for me: #!/bin/bash git clone cd jammy git remote add upstream https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git git fetch upstream git checkout hwe-6.5-next commits="2e6f979037d5ae35c0ed38e2b63e9876eb7bc65f 8c4c216db8fb84be9c4ca60d72b2066cf28f b592ed2e1d78a475f781802e441c499ab446975b b257187bcff4bccc9e7a8f1b8a1a5526ff815af1 2b35b66d82dc4641ba60f7f3c36c0040eedb74e2 ed7326a24a1a9af65fafefd86b505e7c3b968f6d 916d051730ae48aef8b588fd096fefca4bc0590a ee694e7db47e1af00ffb29f569904a9ed576868f d110858a6925827609d11db8513d76750483ec06 ba7053b4b4a4ddcf530fa2b897e697004715d086 7d65d70161ef75a3991480c91668ac11acedf211 8c14dbf36424eb751d70c15f9a671549390057b2 c16dfab33f99fc3ff43d48253bc2784ccb84c1de be220d2e5544ff094142d263db5cf94d034b5e39 706c1fa1ab09f11a131fc4d699ce4c0224b1cb2d b603d95692e47dc6f5f733e93c3841dc0c01e624" for c in $commits; do echo $c git cherry-pick $c done cp /boot/config-$(uname -r) .config make -j16 ** Affects: linux-hwe-6.5 (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/2058578 Title: Add support for several cs35l41 amplifier devices (laptop audio support) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.5/+bug/2058578/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056556] [NEW] apt-add-repository incorrectly forces lowercase
Public bug reported: I have a local APT repository with a non-lowercase suite identifier. apt-add-repository always forces it into lowercase, which causes apt to emit warnings when it notices the mismatch: $ sudo apt-add-repository "deb http://example.com/deb FooBar Baz" Repository: 'deb http://example.com/ foobar Baz' Description: Archive for codename: foobar components: Baz More info: http://example.com/ Adding repository. Press [ENTER] to continue or Ctrl-c to cancel. (...) $ sudo apt update (...) W: Conflicting distribution: http://example.com/deb foobar InRelease (expected foobar but got FooBar) ** Affects: software-properties (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/2056556 Title: apt-add-repository incorrectly forces lowercase To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2056556/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973098] Re: [i915] Intermittent freezing and LSPCON init failed kernel messages
See same issue using Ubuntu 23.10 on a HP HP ProDesk 400 G3 DM/82A5 and it uses Intel HD Graphics 630. Occasionally I will get a black screen with no ability to activate which then requires a reboot. Sometimes I will need to power off and unplug hdmi cable. i915 :00:02.0: [drm] *ERROR* LSPCON mode hasn't settled 2024-02-27T13:33:30.125032-06:00 HPProDesk400 kernel: [ 3323.472414] i915 :00:02.0: [drm] *ERROR* LSPCON mode change timed out 2024-02-27T13:33:30.125049-06:00 HPProDesk400 kernel: [ 3323.472417] i915 :00:02.0: [drm] *ERROR* LSPCON mode change failed 2024-02-27T13:33:30.125049-06:00 HPProDesk400 kernel: [ 3323.472418] i915 :00:02.0: [drm] *ERROR* LSPCON resume failed 2024-02-27T13:33:30.133026-06:00 HPProDesk400 kernel: [ 3323.481193] i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful 2024-02-27T13:33:30.149026-06:00 HPProDesk400 kernel: [ 3323.498313] i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973098 Title: [i915] Intermittent freezing and LSPCON init failed kernel messages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973098/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976581] Re: Ubiquity installer failing with "Failed to mount the target: /target"
*** This bug is a duplicate of bug 1976585 *** https://bugs.launchpad.net/bugs/1976585 ** This bug has been marked a duplicate of bug 1976585 Ubiquity Installer Crash (Consistently Repeatable) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1976581 Title: Ubiquity installer failing with "Failed to mount the target: /target" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1976581/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976585] [NEW] Ubiquity Installer Crash (Consistently Repeatable)
Public bug reported: Ubiquity installer fails with the following steps, booting off a 22.04 LTS USB. Steps to reproduce: - Select: *Try or Install Ubuntu [wait for bootup] - Select: Try Ubuntu (with English) [wait for boot] - Run "Install Ubuntu 22.04 LTS" icon in the top left corner of the screen [Shows Install / Welcome screen] - Select English, click on Continue - Select English (US) / English (US) for keyboard layout, click on Continue - Select Normal Installation, Install thrid-party software, Configute secure boot, entered password, click on Continue - Select Erase disk and install Ubuntu, Advanced features..., Erase disk and use ZFS, Encrypt the new Ubuntu installation, click OK, click Install Now - Enter a security key, click Install Now - View "Write the changes to disks?" (single drive computer, partitions: vfat, swap, bpool, rpool), click Continue - View "Where are you?", select Los Angeles, click Continue - Installer crashed. Looking at /var/log/syslog, I see the following consistently with every try: Jun 2 04:16:53 ubuntu ubiquity[6225]: switched to page usersetup Jun 2 04:16:53 ubuntu ubiquity: Traceback (most recent call last): Jun 2 04:16:53 ubuntu ubiquity: File "/usr/share/ubiquity/install.py", line 769, in Jun 2 04:16:53 ubuntu ubiquity: install = Install() Jun 2 04:16:53 ubuntu ubiquity: File "/usr/share/ubiquity/install.py", line 69, in __init__ Jun 2 04:16:53 ubuntu ubiquity: assert os.path.ismount(self.target), \ Jun 2 04:16:53 ubuntu ubiquity: AssertionError: Failed to mount the target: /target ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubiquity 22.04.15 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.470 Date: Wed Jun 1 21:17:24 2022 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ubiquity-22.04.15 ubuntu ** Attachment added: "/var/log/syslog" https://bugs.launchpad.net/bugs/1976585/+attachment/5594430/+files/syslog -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1976585 Title: Ubiquity Installer Crash (Consistently Repeatable) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1976585/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976581] Re: Ubiquity installer failing with "Failed to mount the target: /target"
/var/log/syslog ** Attachment added: "syslog" https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1976581/+attachment/5594427/+files/syslog -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1976581 Title: Ubiquity installer failing with "Failed to mount the target: /target" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1976581/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976581] [NEW] Ubiquity installer failing with "Failed to mount the target: /target"
Public bug reported: I'm trying to install Ubuntu with third party apps so that I can use secure boot. I also am choosing to use zfs with encryption. If fails when I press next on the timezone step. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubiquity 22.04.15 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.470 Date: Wed Jun 1 20:51:25 2022 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ubiquity-22.04.15 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1976581 Title: Ubiquity installer failing with "Failed to mount the target: /target" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1976581/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970921] Re: Drag and drop does not work
I am observing the same issue on 22.04. I cannot drag and drop from nautilus into chrome or slack. If I switch to an xorg session I can drag and drop. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970921 Title: Drag and drop does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1970921/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1974214] Re: Segfaults on verify callout, in _gnutls_trust_list_get_issuer
We've been running Sergio's exim 4.95-4ubuntu3~ppa2 for 27 hours so far with no segfaults (previously it was segfaulting every few minutes) -- looks like the bug is fixed with those patches; thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1974214 Title: Segfaults on verify callout, in _gnutls_trust_list_get_issuer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/exim4/+bug/1974214/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1974214] Re: Segfaults on verify callout, in _gnutls_trust_list_get_issuer
Hi Sergio, unfortunately your patched package does not fix the problem -- we still see segfaults. From the upstream discussion, I think we may need this commit as well: https://git.exim.org/exim.git/commitdiff/8c74b00980bc7e3e479e8dfcd7c0008b2ac3f543 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1974214 Title: Segfaults on verify callout, in _gnutls_trust_list_get_issuer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/exim4/+bug/1974214/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1745754] Re: upgrading from an End of Life release is not easy peasy
Wouldn't it just be an extensive list of if/then conditional statements that covered all the official and point releases? Once done the first time it would only be updated each time a new release was released or an old one was archived to make sure it pointed to the correct path for the upgrade for whatever version you were running. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1745754 Title: upgrading from an End of Life release is not easy peasy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1745754/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1745754] Re: upgrading from an End of Life release is not easy peasy
It seems to be a very simple issue. do upgrade already tells you what
version you have and if there is an upgrade path on new releases. Why
can't it do that for every release going back into antiquity. There are
probably only 40ish official releases that would need to be covered.
When a release is archived you only need to update the sources for that
release to point the updater to the archives as opposed to the latest
supported releases. I'm a advanced user not a programmer but if I can
address it on the command line with this line of code to make it work on
a case by case basis
sudo sed -i -re
's/([a-z]{2}\.)?archive.ubuntu.com|security.ubuntu.com/old-releases.ubuntu.com/g'
/etc/apt/sources.list
and then
sudo apt-get update && sudo apt-get dist-upgrade
how hard would it be to create this in the normal upgrade process for
each of the old releases.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1745754
Title:
upgrading from an End of Life release is not easy peasy
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1745754/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1974598] [NEW] upgrade from 20.04 to 22.04 failed
Public bug reported: do-release-upgrade seems to have failed on grub-efi, wondering if it choked on my config; attached logs as per error message. System was left in bootable, runnable state, but a zpool was blown away. -- system pools and one pool on NVMe were ok: sribe@sribe000:~$ sudo zpool status pool: bpool state: ONLINE scan: scrub repaired 0B in 0 days 00:00:01 with 0 errors on Sun May 8 00:24:02 2022 config: NAME STATE READ WRITE CKSUM bpool ONLINE 0 0 0 mirror-0 ONLINE 0 0 0 ata-SuperMicro_SSD_SMC0515D90120D212004-part2 ONLINE 0 0 0 ata-SuperMicro_SSD_SMC0515D94819DQL3014-part2 ONLINE 0 0 0 errors: No known data errors pool: pg_pool state: ONLINE scan: scrub repaired 0B in 0 days 00:00:15 with 0 errors on Sun May 8 00:24:16 2022 config: NAME STATE READ WRITE CKSUM pg_pool ONLINE 0 0 0 mirror-0 ONLINE 0 0 0 nvme-INTEL_SSDPELKX010T8_PHLJ0081015R1P0I-part1 ONLINE 0 0 0 nvme-INTEL_SSDPELKX010T8_PHLJ008100M71P0I-part1 ONLINE 0 0 0 errors: No known data errors pool: rpool state: ONLINE scan: scrub repaired 0B in 0 days 00:00:11 with 0 errors on Sun May 8 00:24:13 2022 config: NAME STATE READ WRITE CKSUM rpool ONLINE 0 0 0 mirror-0 ONLINE 0 0 0 ata-SuperMicro_SSD_SMC0515D90120D212004-part3 ONLINE 0 0 0 ata-SuperMicro_SSD_SMC0515D94819DQL3014-part3 ONLINE 0 0 0 errors: No known data errors -- but an archive pool on HDD is fubar: sribe@sribe000:~$ sudo zpool import pool: zp_repo id: 11719108999789418570 state: FAULTED status: The pool metadata is corrupted. action: The pool cannot be imported due to damaged devices or data. The pool may be active on another system, but can be imported using the '-f' flag. see: http://zfsonlinux.org/msg/ZFS-8000-72 config: zp_repo FAULTED corrupted data logs mirror-1 ONLINE nvme-INTEL_SSDPELKX010T8_PHLJ0081015R1P0I-part2 ONLINE nvme-INTEL_SSDPELKX010T8_PHLJ008100M71P0I-part2 ONLINE -- the pool is not active on another system and import with -f fails Fortunately, reverting to a snapshot of the system before the failed upgrade brought the zpool back. I have a pretty customized ZFS setup, including tweaks to /usr/share/initramfs-tools/scripts/zfs--so it might be the case that I will never be able to use the automatic upgrade. ** Affects: ubuntu Importance: Undecided Status: New ** Attachment added: "contents of /var/log/dist-upgrade" https://bugs.launchpad.net/bugs/1974598/+attachment/5591648/+files/logs.tar.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1974598 Title: upgrade from 20.04 to 22.04 failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1974598/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1974214] Re: Segfaults on verify callout, in _gnutls_trust_list_get_issuer
@tobhe Thanks for looking into this. However that upstream bug was apparently fixed in GnuTLS 3.7.4; I just tried libgnutls30 3.7.4-2ubuntu1 from kinetic and I still see these crashes in exim4. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1974214 Title: Segfaults on verify callout, in _gnutls_trust_list_get_issuer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/exim4/+bug/1974214/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1974214] Re: Segfaults on verify callout, in _gnutls_trust_list_get_issuer
** Summary changed: - Segfaults on sender verify callout, in _gnutls_trust_list_get_issuer + Segfaults on verify callout, in _gnutls_trust_list_get_issuer ** Description changed: We are experiencing segfaults in exim since upgrading from impish (4.94.2-7ubuntu2 with libgnutls30 3.7.1-5ubuntu1) to jammy (4.95-4ubuntu2 with libgnutls30 3.7.3-4ubuntu1), in - _gnutls_trust_list_get_issuer, seemingly in the sender verify callout - during message submission. + _gnutls_trust_list_get_issuer, seemingly in the sender/recipient verify + callout during message submission. Typically the initial attempt to submit a message crashes an exim child thread, but the same message is accepted when the sender retries. gdb backtrace: Thread 2.1 "exim4" received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7fe2f844d080 (LWP 29278)] 0x7fe2f8f3eb2b in _gnutls_trust_list_get_issuer (flags=, issuer=, cert=, list=) at x509/../../../lib/x509/verify-high.c:1026 1026x509/../../../lib/x509/verify-high.c: No such file or directory. (gdb) bt #0 0x7fe2f8f3eb2b in _gnutls_trust_list_get_issuer (flags=, issuer=, cert=, - list=) at x509/../../../lib/x509/verify-high.c:1026 + list=) at x509/../../../lib/x509/verify-high.c:1026 #1 gnutls_x509_trust_list_get_issuer (list=list@entry=0x55ef6bd9c260, cert=0x55ef6bd9be20, issuer=issuer@entry=0x7ffc82dba510, - flags=flags@entry=16) at x509/../../../lib/x509/verify-high.c:1129 + flags=flags@entry=16) at x509/../../../lib/x509/verify-high.c:1129 #2 0x7fe2f8f3f679 in gnutls_x509_trust_list_verify_crt2 (list=0x55ef6bd9c260, cert_list=0x7ffc82dba5c0, - cert_list_size=, data=, elements=, flags=33554432, voutput=0x7ffc82dba888, func=0x0) - at x509/../../../lib/x509/verify-high.c:1522 + cert_list_size=, data=, elements=, flags=33554432, voutput=0x7ffc82dba888, func=0x0) + at x509/../../../lib/x509/verify-high.c:1522 #3 0x7fe2f8ed7516 in _gnutls_x509_cert_verify_peers (status=0x7ffc82dba888, elements=0, data=0x0, session=0x55ef6c0c1150) - at ../../lib/cert-session.c:597 + at ../../lib/cert-session.c:597 #4 gnutls_certificate_verify_peers (session=0x55ef6c0c1150, data=data@entry=0x0, elements=elements@entry=0, - status=status@entry=0x7ffc82dba888) at ../../lib/cert-session.c:776 + status=status@entry=0x7ffc82dba888) at ../../lib/cert-session.c:776 #5 0x7fe2f8ed8000 in gnutls_certificate_verify_peers2 (session=, status=status@entry=0x7ffc82dba888) - at ../../lib/cert-session.c:653 + at ../../lib/cert-session.c:653 #6 0x55ef6b7698ef in verify_certificate (state=, errstr=0x7ffc82dbaa20) - at /build/exim4-sMcKLv/exim4-4.95/b-exim4-daemon-light/build-Linux-x86_64/tls-gnu.c:2519 + at /build/exim4-sMcKLv/exim4-4.95/b-exim4-daemon-light/build-Linux-x86_64/tls-gnu.c:2519 #7 0x55ef6b7a5d7b in tls_client_start.constprop.0 (cctx=cctx@entry=0x55ef6be0e688, conn_args=conn_args@entry=0x55ef6bdfe5f8, - tlsp=0x55ef6b7f59c0 , errstr=errstr@entry=0x7ffc82dbaa20, cookie=) - at /build/exim4-sMcKLv/exim4-4.95/b-exim4-daemon-light/build-Linux-x86_64/tls-gnu.c:3593 + tlsp=0x55ef6b7f59c0 , errstr=errstr@entry=0x7ffc82dbaa20, cookie=) + at /build/exim4-sMcKLv/exim4-4.95/b-exim4-daemon-light/build-Linux-x86_64/tls-gnu.c:3593 #8 0x55ef6b78b0ef in smtp_setup_conn (sx=0x55ef6bdfe5e8, suppress_tls=) at transports/smtp.c:2673 #9 0x55ef6b776350 in do_callout (pm_mailfrom=, se_mailfrom=, options=, - callout_connect=, callout_overall=, callout=, tf=0x7ffc82dbbc10, - host_list=, addr=0x7ffc82dbbdd0) - at /build/exim4-sMcKLv/exim4-4.95/b-exim4-daemon-light/build-Linux-x86_64/verify.c:677 + callout_connect=, callout_overall=, callout=, tf=0x7ffc82dbbc10, + host_list=, addr=0x7ffc82dbbdd0) + at /build/exim4-sMcKLv/exim4-4.95/b-exim4-daemon-light/build-Linux-x86_64/verify.c:677 #10 verify_address (vaddr=, fp=, options=, callout=, - callout_overall=, callout_connect=, se_mailfrom=, pm_mailfrom=, - routed=) at /build/exim4-sMcKLv/exim4-4.95/b-exim4-daemon-light/build-Linux-x86_64/verify.c:1947 + callout_overall=, callout_connect=, se_mailfrom=, pm_mailfrom=, + routed=) at /build/exim4-sMcKLv/exim4-4.95/b-exim4-daemon-light/build-Linux-x86_64/verify.c:1947 #11 0x55ef6b6f1660 in acl_verify (where=where@entry=0, addr=addr@entry=0x7ffc82dbc5e0, - arg=0x55ef6babc2b8 "recipient/defer_ok/callout=30s,defer_ok,use_postmaster", user_msgptr=user_msgptr@entry=0x7ffc82dbca50, - log_msgptr=log_msgptr@entry=0x7ffc82dbca58, basic_errno=basic_errno@entry=0x7ffc82dbc38c) - at /build/exim4-sMcKLv/exim4-4.95/b-exim4-daemon-light/build-Linux-x86_64/acl.c:2168 + arg=0x55ef6babc2b8 "recipient/defer_ok/callout=30s,defer_ok,use_postmaster", user_msgptr=user_msgptr@entry=0x7ffc82dbca50, + log_msgptr=log_msgptr@entry=0x7ffc82dbca58, basic_errno=basic_errno@entry=0x7ffc82dbc38c) +
[Bug 1974214] Re: Segfaults on sender verify callout, in _gnutls_trust_list_get_issuer
A similar/identical issue appears to have been discussed briefly on the Exim list: https://lists.exim.org/lurker/message/20211008.224037.c1fee944.gl.html They suggest that it may be a GnuTLS bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1974214 Title: Segfaults on sender verify callout, in _gnutls_trust_list_get_issuer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/exim4/+bug/1974214/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1974214] [NEW] Segfaults on sender verify callout, in _gnutls_trust_list_get_issuer
Public bug reported: We are experiencing segfaults in exim since upgrading from impish (4.94.2-7ubuntu2 with libgnutls30 3.7.1-5ubuntu1) to jammy (4.95-4ubuntu2 with libgnutls30 3.7.3-4ubuntu1), in _gnutls_trust_list_get_issuer, seemingly in the sender verify callout during message submission. Typically the initial attempt to submit a message crashes an exim child thread, but the same message is accepted when the sender retries. gdb backtrace: Thread 2.1 "exim4" received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7fe2f844d080 (LWP 29278)] 0x7fe2f8f3eb2b in _gnutls_trust_list_get_issuer (flags=, issuer=, cert=, list=) at x509/../../../lib/x509/verify-high.c:1026 1026x509/../../../lib/x509/verify-high.c: No such file or directory. (gdb) bt #0 0x7fe2f8f3eb2b in _gnutls_trust_list_get_issuer (flags=, issuer=, cert=, list=) at x509/../../../lib/x509/verify-high.c:1026 #1 gnutls_x509_trust_list_get_issuer (list=list@entry=0x55ef6bd9c260, cert=0x55ef6bd9be20, issuer=issuer@entry=0x7ffc82dba510, flags=flags@entry=16) at x509/../../../lib/x509/verify-high.c:1129 #2 0x7fe2f8f3f679 in gnutls_x509_trust_list_verify_crt2 (list=0x55ef6bd9c260, cert_list=0x7ffc82dba5c0, cert_list_size=, data=, elements=, flags=33554432, voutput=0x7ffc82dba888, func=0x0) at x509/../../../lib/x509/verify-high.c:1522 #3 0x7fe2f8ed7516 in _gnutls_x509_cert_verify_peers (status=0x7ffc82dba888, elements=0, data=0x0, session=0x55ef6c0c1150) at ../../lib/cert-session.c:597 #4 gnutls_certificate_verify_peers (session=0x55ef6c0c1150, data=data@entry=0x0, elements=elements@entry=0, status=status@entry=0x7ffc82dba888) at ../../lib/cert-session.c:776 #5 0x7fe2f8ed8000 in gnutls_certificate_verify_peers2 (session=, status=status@entry=0x7ffc82dba888) at ../../lib/cert-session.c:653 #6 0x55ef6b7698ef in verify_certificate (state=, errstr=0x7ffc82dbaa20) at /build/exim4-sMcKLv/exim4-4.95/b-exim4-daemon-light/build-Linux-x86_64/tls-gnu.c:2519 #7 0x55ef6b7a5d7b in tls_client_start.constprop.0 (cctx=cctx@entry=0x55ef6be0e688, conn_args=conn_args@entry=0x55ef6bdfe5f8, tlsp=0x55ef6b7f59c0 , errstr=errstr@entry=0x7ffc82dbaa20, cookie=) at /build/exim4-sMcKLv/exim4-4.95/b-exim4-daemon-light/build-Linux-x86_64/tls-gnu.c:3593 #8 0x55ef6b78b0ef in smtp_setup_conn (sx=0x55ef6bdfe5e8, suppress_tls=) at transports/smtp.c:2673 #9 0x55ef6b776350 in do_callout (pm_mailfrom=, se_mailfrom=, options=, callout_connect=, callout_overall=, callout=, tf=0x7ffc82dbbc10, host_list=, addr=0x7ffc82dbbdd0) at /build/exim4-sMcKLv/exim4-4.95/b-exim4-daemon-light/build-Linux-x86_64/verify.c:677 #10 verify_address (vaddr=, fp=, options=, callout=, callout_overall=, callout_connect=, se_mailfrom=, pm_mailfrom=, routed=) at /build/exim4-sMcKLv/exim4-4.95/b-exim4-daemon-light/build-Linux-x86_64/verify.c:1947 #11 0x55ef6b6f1660 in acl_verify (where=where@entry=0, addr=addr@entry=0x7ffc82dbc5e0, arg=0x55ef6babc2b8 "recipient/defer_ok/callout=30s,defer_ok,use_postmaster", user_msgptr=user_msgptr@entry=0x7ffc82dbca50, log_msgptr=log_msgptr@entry=0x7ffc82dbca58, basic_errno=basic_errno@entry=0x7ffc82dbc38c) at /build/exim4-sMcKLv/exim4-4.95/b-exim4-daemon-light/build-Linux-x86_64/acl.c:2168 #12 0x55ef6b6f479e in acl_check_condition (level=, basic_errno=0x7ffc82dbc38c, log_msgptr=, user_msgptr=, epp=, addr=, where=, cb=0x55ef6babc298, verb=) at /build/exim4-sMcKLv/exim4-4.95/b-exim4-daemon-light/build-Linux-x86_64/acl.c:3838 #13 acl_check_internal (where=where@entry=0, addr=addr@entry=0x7ffc82dbc5e0, s=s@entry=0x55ef6bab9990 "acl_check_rcpt", user_msgptr=user_msgptr@entry=0x7ffc82dbca50, log_msgptr=log_msgptr@entry=0x7ffc82dbca58) at /build/exim4-sMcKLv/exim4-4.95/b-exim4-daemon-light/build-Linux-x86_64/acl.c:4225 #14 0x55ef6b6f7b9e in acl_check (where=0, recipient=, s=0x55ef6bab9990 "acl_check_rcpt", user_msgptr=0x7ffc82dbca50, log_msgptr=0x7ffc82dbca58) at /build/exim4-sMcKLv/exim4-4.95/b-exim4-daemon-light/build-Linux-x86_64/acl.c:4539 #15 0x55ef6b75c2fd in smtp_setup_msg () at /build/exim4-sMcKLv/exim4-4.95/b-exim4-daemon-light/build-Linux-x86_64/smtp_in.c:5283 #16 0x55ef6b6e5cda in handle_smtp_call (accepted=0x7ffc82dbceb0, accept_socket=, listen_socket_count=, listen_sockets=) at /build/exim4-sMcKLv/exim4-4.95/b-exim4-daemon-light/build-Linux-x86_64/daemon.c:551 #17 daemon_go () at /build/exim4-sMcKLv/exim4-4.95/b-exim4-daemon-light/build-Linux-x86_64/daemon.c:2594 #18 main (argc=, cargv=) at /build/exim4-sMcKLv/exim4-4.95/b-exim4-daemon-light/build-Linux-x86_64/exim.c:4947 ** Affects: exim4 (Ubuntu) Importance: Undecided Status: New ** Affects: gnutls28 (Ubuntu) Importance: Undecided Status: New ** Also affects: gnutls28 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you
[Bug 1973436] [NEW] Ubuntu 20.04 to 22.04 upgrade does not work
Public bug reported: An unresolvable problem occurred while calculating the upgrade. This was caused by: * Upgrading to a pre-release version of Ubuntu This is most likely a transient problem, please try again later. If none of this applies, then please report this bug using the command 'ubuntu-bug ubuntu-release-upgrader-core' in a terminal. If you want to investigate this yourself the log files in '/var/log/dist-upgrade' will contain details about the upgrade. Specifically, look at 'main.log' and 'apt.log'. Restoring original system state Aborting Reading package lists... Done Building dependency tree Reading state information... Done This system was installed 2 years ago 20.04 fresh. The upgrade to 22.04 is rejected. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.38 ProcVersionSignature: Ubuntu 5.4.0-110.124-generic 5.4.181 Uname: Linux 5.4.0-110-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sat May 14 18:55:57 2022 PackageArchitecture: all SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to focal on 2022-05-14 (0 days ago) ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973436 Title: Ubuntu 20.04 to 22.04 upgrade does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1973436/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970898] Re: unable to use nfs client to mount nfs in Ubuntu 22.04
I was also unable to use NFS mounts since upgrading my client to 22.04. My server is a QNAP running version 5.0.0.1986. Enabling NFSv4 on the server did not solve the issue. Adding vers=3 as a mount option on the client lets NFS mounts work again for me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970898 Title: unable to use nfs client to mount nfs in Ubuntu 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1970898/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968782] [NEW] CHROOT_SESSION_PURGE is set to false without union-type, so 90apt-sources does not render
Public bug reported: I'm not sure if this is incorrect behavior in schroot or incorrect assumption in sbuild-launchpad-chroot. I have a system where I was not able to use union, so the focal-amd64 config that was built by sbuild-launchpad-chroot looks like below. When attempting to build from it (sbuild --dist=focal --arch=amd64 --arch- all package.dsc), CHROOT_SESSION_PURGE is set to false. That causes me to take the 'exit 0' path in https://git.launchpad.net/~motu/ubuntu/+source/sbuild-launchpad- chroot/tree/etc/schroot/setup.d/90apt-sources#n39 . The end result is the 'apt.default.mirror' setting is not honored. If you set 'union-type=overlay', then you'll get CHROOT_SESSION_PURGE set to true and it will work as desired. % cat /etc/schroot/chroot.d/focal-amd64 [focal-amd64] type=directory directory=/var/lib/schroot/chroot/focal-amd64 description=Ubuntu focal/amd64 sbuild root-groups=root,sbuild profile=sbuild launchpad.dist=ubuntu launchpad.series=focal launchpad.arch=amd64 launchpad.url=http://launchpadlibrarian.net/475801990/livecd.ubuntu-base.rootfs.tar.gz apt.enable=true aliases=focal-security-amd64,focal-security+main-amd64,focal-security+restricted-amd64,focal-security+universe-amd64,focal-security+multiverse-amd64,focal-updates-amd64,focal-updates+main-amd64,focal-updates+restricted-amd64,focal-updates+universe-amd64,focal-updates+multiverse-amd64,focal-proposed-amd64,focal-proposed+main-amd64,focal-proposed+restricted-amd64,focal-proposed+universe-amd64,focal-proposed+multiverse-amd64,focal-backports-amd64,focal-backports+main-amd64,focal-backports+restricted-amd64,focal-backports+universe-amd64,focal-backports+multiverse-amd64 apt.default.mirror=MY_MIRROR ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: sbuild-launchpad-chroot 0.17ubuntu0.20.10.1~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-28.31~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-28-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Apr 12 15:53:54 2022 InstallationDate: Installed on 2020-01-15 (817 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: sbuild-launchpad-chroot UpgradeStatus: Upgraded to focal on 2020-04-17 (725 days ago) modified.conffile..etc.schroot.setup.d.90apt-sources: [modified] mtime.conffile..etc.schroot.setup.d.90apt-sources: 2022-04-12T15:23:14.405987 ** Affects: sbuild-launchpad-chroot (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/1968782 Title: CHROOT_SESSION_PURGE is set to false without union-type, so 90apt- sources does not render To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sbuild-launchpad-chroot/+bug/1968782/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967812] Re: ubuntu 22.04 beta crash regarding gnome-shell and several others also...
** Package changed: ubuntu => gnome-shell (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967812 Title: ubuntu 22.04 beta crash regarding gnome-shell and several others also... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1967812/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967812] [NEW] ubuntu 22.04 beta crash regarding gnome-shell and several others also...
Public bug reported: Hello to all, Under the Ubuntu 22.04 final Beta on live usb mode after startup I noticed a crash regarding gnome-shell and also I noticed several others on my end also meaning several other crashes and the several other crashes I don't know what they are unless I boot to it again via usb flash drive as well... So Thanks in advance and Have a great day also.. ** Affects: ubuntu Importance: Undecided Status: New ** Tags: live-usb -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967812 Title: ubuntu 22.04 beta crash regarding gnome-shell and several others also... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1967812/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 552145] Re: Memtest86+ locks on starting, no error message given
This bug report is a decade old and the reported system has long since failed and been recycled. The nearest similar system I can access is a Core 2 Duo T8100, which is able to both start and exit the latest Memtest (in Jammy) using regular onscreen command keys. I suspect this means that the problem is solved for the original system as well. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/552145 Title: Memtest86+ locks on starting, no error message given To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/memtest86+/+bug/552145/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967078] VarLogDistupgradeMainlog.txt
apport information ** Attachment added: "VarLogDistupgradeMainlog.txt" https://bugs.launchpad.net/bugs/1967078/+attachment/5574702/+files/VarLogDistupgradeMainlog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967078 Title: Firefox snap install fails due to disabled networking in upgrade process To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967078/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967078] VarLogDistupgradeLspcitxt.txt
apport information ** Attachment added: "VarLogDistupgradeLspcitxt.txt" https://bugs.launchpad.net/bugs/1967078/+attachment/5574701/+files/VarLogDistupgradeLspcitxt.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967078 Title: Firefox snap install fails due to disabled networking in upgrade process To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967078/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967078] VarLogDistupgradeApttermlog.txt
apport information ** Attachment added: "VarLogDistupgradeApttermlog.txt" https://bugs.launchpad.net/bugs/1967078/+attachment/5574700/+files/VarLogDistupgradeApttermlog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967078 Title: Firefox snap install fails due to disabled networking in upgrade process To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967078/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967078] VarLogDistupgradeAptlog.txt
apport information ** Attachment added: "VarLogDistupgradeAptlog.txt" https://bugs.launchpad.net/bugs/1967078/+attachment/5574699/+files/VarLogDistupgradeAptlog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967078 Title: Firefox snap install fails due to disabled networking in upgrade process To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967078/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967078] VarLogDistupgradeAptclonesystemstate.tar.gz
apport information ** Attachment added: "VarLogDistupgradeAptclonesystemstate.tar.gz" https://bugs.launchpad.net/bugs/1967078/+attachment/5574698/+files/VarLogDistupgradeAptclonesystemstate.tar.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967078 Title: Firefox snap install fails due to disabled networking in upgrade process To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967078/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967078] VarLogDistupgradeAptHistorylog.txt
apport information ** Attachment added: "VarLogDistupgradeAptHistorylog.txt" https://bugs.launchpad.net/bugs/1967078/+attachment/5574697/+files/VarLogDistupgradeAptHistorylog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967078 Title: Firefox snap install fails due to disabled networking in upgrade process To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967078/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967078] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1967078/+attachment/5574696/+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/1967078 Title: Firefox snap install fails due to disabled networking in upgrade process To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967078/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967078] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1967078/+attachment/5574694/+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/1967078 Title: Firefox snap install fails due to disabled networking in upgrade process To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967078/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967078] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1967078/+attachment/5574695/+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/1967078 Title: Firefox snap install fails due to disabled networking in upgrade process To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967078/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967078] Re: Firefox snap install fails due to disabled networking in upgrade process
apport information ** Tags added: apport-collected dist-upgrade ** Description changed: Upgrading from Kubuntu 20.04.4 LTS to Jammy fails to install Firefox snap due to disabled networking. Prior to the snap installation attempt, networking is disabled as part of the regular do-release- upgrade process. Although networking is enabled again, and a link is restored, later in the process, name resolution typically fails until the system is rebooted following completion of the upgrade. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-23-generic 5.15.0-23.23 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 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: scott 959 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Mar 30 04:28:02 2022 HotplugNewDevices: HotplugNewMounts: InstallationDate: Installed on 2022-03-30 (0 days ago) InstallationMedia: Kubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) MachineType: LENOVO 6465CTO PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=dd8941af-5c34-46a0-ab6f-18cd32e613b0 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220314.gitcd01f857-0ubuntu2 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux Symptom: storage UdevMonitorLog: monitor will print the received events for: UDEV - the event which udev sends out after rule processing UdisksMonitorLog: Monitoring the udisks daemon. Press Ctrl+C to exit. 04:28:26.684: The udisks-daemon is running (name-owner :1.10). UpgradeStatus: Upgraded to jammy on 2022-03-30 (0 days ago) dmi.bios.date: 04/25/2008 dmi.bios.release: 2.23 dmi.bios.vendor: LENOVO dmi.bios.version: 7LETB7WW (2.17 ) dmi.board.name: 6465CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.8 dmi.modalias: dmi:bvnLENOVO:bvr7LETB7WW(2.17):bd04/25/2008:br2.23:efr1.8:svnLENOVO:pn6465CTO:pvrThinkPadT61:rvnLENOVO:rn6465CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:sku: dmi.product.family: ThinkPad T61 dmi.product.name: 6465CTO dmi.product.version: ThinkPad T61 dmi.sys.vendor: LENOVO + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu79 + Architecture: amd64 + CasperMD5CheckResult: unknown + CrashDB: ubuntu + CurrentDesktop: KDE + DistroRelease: Ubuntu 22.04 + InstallationDate: Installed on 2022-03-30 (0 days ago) + InstallationMedia: Kubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) + Package: ubuntu-release-upgrader-core 1:22.04.7 + PackageArchitecture: all + ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 + Tags: jammy dist-upgrade + Uname: Linux 5.15.0-23-generic x86_64 + UpgradeStatus: Upgraded to jammy on 2022-03-30 (0 days ago) + UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo + VarLogDistupgradeXorgFixuplog: + INFO:root:/usr/bin/do-release-upgrade running + INFO:root:No xorg.conf, exiting + _MarkForUpload: True ** Attachment added: "CurrentDmesg.txt.txt" https://bugs.launchpad.net/bugs/1967078/+attachment/5574693/+files/CurrentDmesg.txt.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967078 Title: Firefox snap install fails due to disabled networking in upgrade process To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967078/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967078] [NEW] Firefox snap install fails due to disabled networking in upgrade process
Public bug reported: Upgrading from Kubuntu 20.04.4 LTS to Jammy fails to install Firefox snap due to disabled networking. Prior to the snap installation attempt, networking is disabled as part of the regular do-release- upgrade process. Although networking is enabled again, and a link is restored, later in the process, name resolution typically fails until the system is rebooted following completion of the upgrade. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-23-generic 5.15.0-23.23 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 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: scott 959 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Mar 30 04:28:02 2022 HotplugNewDevices: HotplugNewMounts: InstallationDate: Installed on 2022-03-30 (0 days ago) InstallationMedia: Kubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) MachineType: LENOVO 6465CTO PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=dd8941af-5c34-46a0-ab6f-18cd32e613b0 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220314.gitcd01f857-0ubuntu2 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux Symptom: storage UdevMonitorLog: monitor will print the received events for: UDEV - the event which udev sends out after rule processing UdisksMonitorLog: Monitoring the udisks daemon. Press Ctrl+C to exit. 04:28:26.684: The udisks-daemon is running (name-owner :1.10). UpgradeStatus: Upgraded to jammy on 2022-03-30 (0 days ago) dmi.bios.date: 04/25/2008 dmi.bios.release: 2.23 dmi.bios.vendor: LENOVO dmi.bios.version: 7LETB7WW (2.17 ) dmi.board.name: 6465CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.8 dmi.modalias: dmi:bvnLENOVO:bvr7LETB7WW(2.17):bd04/25/2008:br2.23:efr1.8:svnLENOVO:pn6465CTO:pvrThinkPadT61:rvnLENOVO:rn6465CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:sku: dmi.product.family: ThinkPad T61 dmi.product.name: 6465CTO dmi.product.version: ThinkPad T61 dmi.sys.vendor: LENOVO ** Affects: linux (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/1967078 Title: Firefox snap install fails due to disabled networking in upgrade process To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967078/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863498] Re: raise ValueError('malformed node or string: ' + repr(node)) ValueError: malformed node or string: b"['$HOME']\n"
** Changed in: python-caja (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/1863498
Title:
raise ValueError('malformed node or string: ' + repr(node))
ValueError: malformed node or string: b"['$HOME']\n"
To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup-caja/+bug/1863498/+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 1859506] Re: swtpm fails in focal with apparor
** Summary changed: - swtmp fails in focal with apparor + swtpm fails in focal with apparor -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1859506 Title: swtpm fails in focal with apparor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1859506/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947311] Re: Unexpected partition growth on first boot on impish for raspberry pi
@Noah, cloud-init isn't doing anything wrong. Its working as designed. 'growroot', which is provided by cloud-initramfs-tools (upstream [1], package [2]) also didn't do anything wrong. It's sole purpose in the initramfs is to do what it is doing. I'm not sure what code creates the image you've pointed to. That is the code that included growroot into the image. Thats what Juerg was saying. It should not be necessary with any kernel newer than 3.8 (~10 years ago). If growroot was *not* present, then the user-data you have provided would tell cloud-init not to grow the partition. -- [1] https://code.launchpad.net/cloud-initramfs-tools [2] https://launchpad.net/ubuntu/+source/cloud-initramfs-tools -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947311 Title: Unexpected partition growth on first boot on impish for raspberry pi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1947311/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947311] Re: Unexpected partition growth on first boot on impish for raspberry pi
> I thought cloud-initramfs-growroot was solely used with old kernels that > can't resize mounted > filesystems but I could be wrong. Wondering though why we install that > package all of a sudden. that is another option, to remove cloud-initramfs-growroot from the image/initrd. The problem with that is that you're then relying on cloud-init to grow the rootfs, and if you disable cloud-init you don't get the grow. I'm not exactly sure what the purpose of these images is. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947311 Title: Unexpected partition growth on first boot on impish for raspberry pi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1947311/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947311] Re: Unexpected partition growth on first boot on impish for raspberry pi
@Noah,
The image you pointed at there has the package 'cloud-initramfs-growroot'
in its initramfs. cloud-initramfs-growroot is going to run growpart on the
root filesystem during the initramfs unless one of the following files
exists on the root filesystem:
/var/lib/cloud/instance/root-grown
/etc/growroot-disabled
/etc/growroot-grown
So the easiest to do is to create one of those files. You have mentioned
above that MacOS does not have ext4 filesystem support. So you can't easily
do it natively.
Here are some other options:
1. use libguestfs/guestfish or some other mechanism to boot a linux in which
you could create one of those files.
2. Improve growpart to read a kernel command line option to disable
itself.
3. Improve growpart to further look for a "disable" file on a vfat
filesystem labelled 'system-boot' (lets just say 'growroot-disabled'), and
then use MacOS support of vfat to create the file there.
4. Further partition the image before booting. Growpart can only grow the
root filesystem until the next partition boundary.
Further exploring option '4', here is some information about the image:
a.) there are 2 partitions,
* 1 : 256M partition with VFAT filesystem labelled 'system-boot'.
* 2 : ~3.9GB partition with ext4 filesystem labelled 'writable'
b.) there is 16676864 bytes of unpartitioned space after partition 2.
c.) These are just rants:
* The second partition starts on a MiB boundary, but does not end on one.
So when you create another partition on that disk you're likely
* The partition table type really should be GPT, not dos. 10 years ago
GPT would have been the right decision and it still is today.
* I wonder why 16676864 bytes (32572 sectors) of unused space. that is an
strange number.
So something you probably can do is to add a partition of minimal size
directly after the last partition. You could use fdisk to do this
interactively or sfdisk like below:
If I were trying to do this right, I'd end my mini-partition on a MiB
boundary so that the fourth partition would start on a MiB boundary.
MiB boundary just make sense for alignment (or even 4MiB boundary, for
LVM extent alignment. Maybe it isn't completely necessary, but why not?).
But for simplicitly sake, lets just add a partition right at the end of the
previous one.
Info is attached and at https://paste.ubuntu.com/p/SmQKM2qCXX/ .
Below is the fdisk session inline here (launchpad doesn't format things
like that well, so I put it in attachemnt and pastebin also).
The end result is we have a partition (number 4) that starts right where
the second partition ends, so that:
a.) you can use partition 3 as you wanted before.
b.) growpart can't grow anything.
-
$ fdisk jammy-preinstalled-server-arm64+raspi.img
Welcome to fdisk (util-linux 2.34).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.
Command (m for help): p
Disk jammy-preinstalled-server-arm64+raspi.img: 4.18 GiB, 4483710976 bytes,
8757248 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x755644c9
Device Boot Start End Sectors Size Id
Type
jammy-preinstalled-server-arm64+raspi.img1 * 2048 526335 524288 256M c
W95
jammy-preinstalled-server-arm64+raspi.img2 526336 8722627 8196292 3.9G 83
Linu
Command (m for help): n
Partition type
p primary (2 primary, 0 extended, 2 free)
e extended (container for logical partitions)
Select (default p): p
Partition number (3,4, default 3): 4
First sector (8722628-8757247, default 8724480): 8722628
Last sector, +/-sectors or +/-size{K,M,G,T,P} (8722628-8757247, default
8757247): +2047
Created a new partition 4 of type 'Linux' and of size 1 MiB.
Command (m for help): w
The partition table has been altered.
Syncing disks.
** Attachment added: "info.txt : disk layout info and partitioning"
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1947311/+attachment/5561442/+files/info.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1947311
Title:
Unexpected partition growth on first boot on impish for raspberry pi
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1947311/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1959639] [NEW] Running autopkgtest in lxc crashes host's ntp
On Monday, January 31, 2022 9:51:59 PM EST Bryce Harrington wrote: > Comparing the build log from 3.6.3 with the autopkgtest log for 3.6.4, > these lines jump out at me: > > ### 3.6.3 ### > > install -m644 debian/postfix.insserv.conf > debian/postfix/etc/insserv.conf.d/postfix txt2man -t postfix-collate -r > postfix-3.6.3 -d -s 1 auxiliary/collate/README > > debian/postfix/usr/share/man/man1/postfix-collate.1 expand: 1: No such file > or directory > install man/man1/*.1 debian/postfix/usr/share/man/man1 > > ### 3.6.4 ### > > install -m644 debian/postfix.insserv.conf > debian/postfix/etc/insserv.conf.d/postfix txt2man -t postfix-collate -r > postfix-3.6.4 -d 'Mon Jan 31 09:42:30 PM UTC 2022' -s 1 > auxiliary/collate/README > > debian/postfix/usr/share/man/man1/postfix-collate.1 install man/man1/*.1 > debian/postfix/usr/share/man/man1 This was due to a quoting error in debian/rules in 3.6.3. What's being expanded there is: '$(shell date -s @$(SOURCE_DATE_EPOCH))' Nothing to do with NTP. Scott K -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959639 Title: Running autopkgtest in lxc crashes host's ntp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1959639/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959324] Re: sbuild-launchpad-chroot does not notice tar extract failures
** Also affects: sbuild-launchpad-chroot (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: sbuild-launchpad-chroot (Ubuntu Focal) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959324 Title: sbuild-launchpad-chroot does not notice tar extract failures To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sbuild-launchpad-chroot/+bug/1959324/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959324] [NEW] sbuild-launchpad-chroot does not notice tar extract failures
Public bug reported: Nothing is checking exit code of tar when the downloaded tarball is extracted. Tar could fail for many reasons including permission or filesystem full. If tar failed, sbuild-launchpad-chroot would just continue on. The user would likely fail in a less obvious way later on. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: sbuild-launchpad-chroot 0.17ubuntu0.20.10.1~20.04.1 ProcVersionSignature: Ubuntu 5.11.0-46.51~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-46-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jan 27 12:22:26 2022 InstallationDate: Installed on 2020-01-15 (742 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: sbuild-launchpad-chroot UpgradeStatus: Upgraded to focal on 2020-04-17 (650 days ago) ** Affects: sbuild-launchpad-chroot (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: sbuild-launchpad-chroot (Ubuntu Focal) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug focal ** Changed in: sbuild-launchpad-chroot (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959324 Title: sbuild-launchpad-chroot does not notice tar extract failures To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sbuild-launchpad-chroot/+bug/1959324/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1957884] Re: postfix warns about differing chroot files after package upgrades
In theory, yes. In practice, it would be very complicated and it's not something that's likely to get done in the near-term. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1957884 Title: postfix warns about differing chroot files after package upgrades To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1957884/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1957884] Re: postfix warns about differing chroot files after package upgrades
Does restarting (not reloading) or stopping/starting postfix get things back in sync? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1957884 Title: postfix warns about differing chroot files after package upgrades To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1957884/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1519331] Re: Postfix cannot resolve DNS if network was unavailable when it was started, such as on a laptop
It's postfix@$INSTANCE. If you don't have multi-instance setup, the default instance is "-", so you would look for postfix@-, not postfix@. This is discussed in README.Debian. You should probably file a new bug for this problem if you don't get it figured out. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1519331 Title: Postfix cannot resolve DNS if network was unavailable when it was started, such as on a laptop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1519331/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1956505] Re: Merge 3.6.3-5 from debian
On Wednesday, January 5, 2022 11:13:49 AM EST you wrote: > Also check if we can get rid of the delta and make postfix a sync again. No. The glibc change isn't incorporated. It would be nice if someone from a distro (like Ubuntu) that has applied the patch would talk to upstream about it and get them to incorporate it. I don't plan to add it as a patch unless Debian actually needs it, which we don't so far. Scott K -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956505 Title: Merge 3.6.3-5 from debian To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1956505/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1948881] Re: XSane plugin not available in GIMP File menu
In case it helps, I noticed that in Ubuntu 21.04, my ~/.config/GIMP/2.10/pluginrc contained (menu-path "/File/Create/Acquire/XSane/Device dialog...") within the (proc-def "xsane" ...) s-expression. No menu-path appears in my Ubuntu 21.10 ~/.config/GIMP/2.10/pluginrc. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1948881 Title: XSane plugin not available in GIMP File menu To manage notifications about this bug go to: https://bugs.launchpad.net/gimp/+bug/1948881/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1954573] Re: error on verifying inbound mail
Thanks. I'll reassign this to Ubuntu's dkimpy package. They should consider doing a stable release update to fix this. ** Project changed: dkimpy-milter => dkimpy (Ubuntu) ** Changed in: dkimpy (Ubuntu) Importance: Undecided => High ** Changed in: dkimpy (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1954573 Title: error on verifying inbound mail To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkimpy/+bug/1954573/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915238] Re: warning: /var/spool/postfix/etc/ssl/certs/ca-certificates.crt and /etc/ssl/certs/ca-certificates.crt differ
Not a ca-certificates issue. ** Changed in: ca-certificates (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915238 Title: warning: /var/spool/postfix/etc/ssl/certs/ca-certificates.crt and /etc/ssl/certs/ca-certificates.crt differ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1915238/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915238] Re: warning: /var/spool/postfix/etc/ssl/certs/ca-certificates.crt and /etc/ssl/certs/ca-certificates.crt differ
This is an unneeded leftover and the file in the chroot (/var/spool/postfix) can be deleted. When using smtp*_tls_CAfile, the smtp or smtpd daemon copies from /etc/ssl/certs before entering the chroot (CApath is different), so it doesn't need to be there. We stopped copying the file into the chroot in 3.4.7-1, but didn't clean up the old one. I've committed a change to the Debian postfix git repository, which will be in the next Debian upload, to do this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915238 Title: warning: /var/spool/postfix/etc/ssl/certs/ca-certificates.crt and /etc/ssl/certs/ca-certificates.crt differ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1915238/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915238] Re: warning: /var/spool/postfix/etc/ssl/certs/ca-certificates.crt and /etc/ssl/certs/ca-certificates.crt differ
So I looked into this a bit more and based on http://www.postfix.org/postconf.5.html#smtp_tls_CAfile is doesn't appear to me that the ca-certificates.crt file needs to be in the chroot at all. What happens if you just delete the chroot copy? Looking in the git history, I can see we used to install this file into the chroot, but I'm not sure we needed to. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915238 Title: warning: /var/spool/postfix/etc/ssl/certs/ca-certificates.crt and /etc/ssl/certs/ca-certificates.crt differ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1915238/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955611] Re: Unable to boot Live USB on Mac
Thanks for your reply Chris, The software used to create the media was rufus 3.17, following this tutorial: https://ubuntu.com/tutorials/create-a-usb-stick-on-windows The media boots without error from within a virtual machine via plopboot and plopkexec, but not on bare metal of the same hardware, and successfully boots on a Lenovo Thinkcentre M700. I'm not sure why the media is failing to boot only on bare metal for the Macbook. If there are any other validation steps I can take I would be glad to do so. The issue has been posted on ask ubuntu and the suggestions so far have been to validate the media: https://askubuntu.com/questions/1383225/how- to-boot-from-a-live-usb-stick-on-a-mac I look forward to hearing from you. Kind regards, Scott. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955611 Title: Unable to boot Live USB on Mac To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1955611/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955581] [NEW] Consider merge/synch from Debian
Public bug reported: Debian now has jack-mixer 17. This might be a good time to see if a sync is possible or at least do a merge so it's clear what's different between the packages. ** Affects: jack-mixer (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/1955581 Title: Consider merge/synch from Debian To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jack-mixer/+bug/1955581/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1939353] Re: FTBFS 3.5.6-1build1 with gcc-11
Incorporation of this patch in postfix upstream is currently being discussed on the postfix-users mailing list. The specific question asked by Wietse is: Has this been adopted, or do people on 3.5.* still have to tinker with their /etc/resolv.conf files? If anyone from Ubuntu could comment on that, it would be great. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1939353 Title: FTBFS 3.5.6-1build1 with gcc-11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1939353/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847275] Re: stunnel4: "INTERNAL ERROR: Bad magic at ssl.c, line 117" - DoS vulnerability
I'm not convinced that CVE-2021-20230 is the same bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847275 Title: stunnel4: "INTERNAL ERROR: Bad magic at ssl.c, line 117" - DoS vulnerability To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/stunnel4/+bug/1847275/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952001] [NEW] cloud-init 21.3-1-g6803368d-0ubuntu1~18.04.4 recreated SSH host keys on Azure VMs
Public bug reported: On multiple Azure VMs running Ubuntu 18.04.6 LTS, when cloud-init 21.3-1-g6803368d-0ubuntu1~18.04.4 was installed, it re-created the SSH host keys. This caused an obvious security scare that our machines had been hacked. ** Affects: cloud-init (Ubuntu) Importance: Undecided Status: New ** Attachment added: "cloud-init.log from one of the machines" https://bugs.launchpad.net/bugs/1952001/+attachment/5542881/+files/cloud-init.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952001 Title: cloud-init 21.3-1-g6803368d-0ubuntu1~18.04.4 recreated SSH host keys on Azure VMs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1952001/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915238] Re: warning: /var/spool/postfix/etc/ssl/certs/ca-certificates.crt and /etc/ssl/certs/ca-certificates.crt differ
I'm open to putting a fix in Debian. I haven't come up with a solution that I'm happy with and don't currently have a lot of time to work on this. I think Paride Legovini's "wall-of-text" post is on the right track, but I would really prefer to avoid asking a question about this. Anything in configure-instance.sh needs to be init system agnostic. I don't mind a systemd specific solution since that's our default init, but not in configure-instance.sh (no idea if there is one, but that's a boundary condition to a proper fix in my view). If someone comes up with a patch, I can test it and will be glad to land it in Debian if suitable and functional. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915238 Title: warning: /var/spool/postfix/etc/ssl/certs/ca-certificates.crt and /etc/ssl/certs/ca-certificates.crt differ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1915238/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950943] [NEW] Installation Error
Public bug reported: Performing installation, error occured after coping files ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: ubiquity 21.10.10 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.465 CurrentDesktop: ubuntu:GNOME Date: Sun Nov 14 21:28:45 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) ProcEnviron: LANGUAGE=en_US.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish ubiquity-21.10.10 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950943 Title: Installation Error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1950943/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1478006] Re: Include test suite in package
This has been done finally in 3.0.2-2. :-) ** Changed in: xlsxwriter (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/1478006 Title: Include test suite in package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xlsxwriter/+bug/1478006/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947532] [NEW] missing .torrent on startup - ktorrent quits with Malformed URL
Public bug reported: Error message on startup: "Malformed URL /tmp/mozilla_supaplex0/linuxmint.torrent" then exits after I hit OK. https://github.com/supaplextor/cloudy-chance-tcpip- checks/blob/master/Screenshot%20from%202021-10-17%2017-14-41.png The torrent file is not there. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ktorrent 5.1.2-1build1 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Oct 17 17:24:06 2021 InstallationDate: Installed on 2021-09-29 (18 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ktorrent UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ktorrent (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/1947532 Title: missing .torrent on startup - ktorrent quits with Malformed URL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ktorrent/+bug/1947532/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848534] Re: [Microsoft Hyper-V guest] System shows graphic artifacts for a moment, then text cursor for about minute and then starts
This is still a bug in Ubuntu 21.04 and 21.10. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848534 Title: [Microsoft Hyper-V guest] System shows graphic artifacts for a moment, then text cursor for about minute and then starts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1848534/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1923616] Re: Please remove rax-nova-agent and xe-guest-utils source and binaries from Hirsute
xe-guest-utilities is the Xen equivalent to open-vm-tools which is still in Ubuntu to support VMware. Though xe-guest-utilities may have been added to Ubuntu for one particular cloud, it is needed on all installations of Ubuntu in VMs running on Citrix Hypervisor / XenServer, or on XCP-ng etc.. It would be very helpful for those of us who run Ubuntu on Xen VMs if xe-guest-utilities were reintroduced before 22.04. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1923616 Title: Please remove rax-nova-agent and xe-guest-utils source and binaries from Hirsute To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rax-nova-agent/+bug/1923616/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944381] Re: package wx3.0-i18n (not installed) failed to install/upgrade: trying to overwrite '/usr/share/locale/ca/LC_MESSAGES/wxstd.mo', which is also in package wx3.1-i18n 3.1.3-1.bionic
** Changed in: wxwidgets3.0 (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/1944381 Title: package wx3.0-i18n (not installed) failed to install/upgrade: trying to overwrite '/usr/share/locale/ca/LC_MESSAGES/wxstd.mo', which is also in package wx3.1-i18n 3.1.3-1.bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wxwidgets3.0/+bug/1944381/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944381] Re: package wx3.0-i18n (not installed) failed to install/upgrade: trying to overwrite '/usr/share/locale/ca/LC_MESSAGES/wxstd.mo', which is also in package wx3.1-i18n 3.1.3-1.bionic
This error message is reporting that the wx3.0-i18n and wx3.1-i18n packages both contain the file /usr/share/locale/ca/LC_MESSAGES/wxstd.mo. The wx3.1-i18n package is not part of Ubuntu, so you'll need to report this problem to wherever you obtained that package (perhaps a PPA?). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944381 Title: package wx3.0-i18n (not installed) failed to install/upgrade: trying to overwrite '/usr/share/locale/ca/LC_MESSAGES/wxstd.mo', which is also in package wx3.1-i18n 3.1.3-1.bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wxwidgets3.0/+bug/1944381/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943188] Re: Ensure chrony is configured (Automated)
I copied over this from another host (same results): = # Welcome to the chrony configuration file. See chrony.conf(5) for more # information about usuable directives. # This will use (up to): # - 4 sources from ntp.ubuntu.com which some are ipv6 enabled # - 2 sources from 2.ubuntu.pool.ntp.org which is ipv6 enabled as well # - 1 source from [01].ubuntu.pool.ntp.org each (ipv4 only atm) # This means by default, up to 6 dual-stack and up to 2 additional IPv4-only # sources will be used. # At the same time it retains some protection against one of the entries being # down (compare to just using one of the lines). See (LP: #1754358) for the # discussion. # # About using servers from the NTP Pool Project in general see (LP: #104525). # Approved by Ubuntu Technical Board on 2011-02-08. # See http://www.pool.ntp.org/join.html for more information. #pool ntp.ubuntu.comiburst maxsources 4 pool 0.pool.ntp.org iburst maxsources 4 pool 1.pool.ntp.org iburst maxsources 4 pool 2.pool.ntp.org iburst maxsources 4 pool 3.pool.ntp.org iburst maxsources 4 # This directive specify the location of the file containing ID/key pairs for # NTP authentication. keyfile /etc/chrony/chrony.keys # This directive specify the file into which chronyd will store the rate # information. driftfile /var/lib/chrony/chrony.drift # Uncomment the following line to turn logging on. #log tracking measurements statistics # Log files location. logdir /var/log/chrony # Stop bad estimates upsetting machine clock. maxupdateskew 100.0 # This directive enables kernel synchronisation (every 11 minutes) of the # real-time clock. Note that it can’t be used along with the 'rtcfile' directive. rtcsync # Step the system clock instead of slewing it if the adjustment is larger than # one second, but only in the first three clock updates. makestep 1 3 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943188 Title: Ensure chrony is configured (Automated) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1943188/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943188] [NEW] Ensure chrony is configured (Automated)
Public bug reported: Source: CIS_Ubuntu_Linux_20.04_LTS_Benchmark_v1.1.0.pdf Link: https://workbench.cisecurity.org/files/3228 (download PDF) cis-audit level2_server fails on rule_CIS-2.2.1.3 but passes all manual checks. === Title Ensure chrony is configured Rule xccdf_com.ubuntu.focal.cis_rule_CIS-2.2.1.3 Result fail === 2.1.1.3 Ensure chrony is configured (Automated) (xccdf_com.ubuntu.focal.cis_rule_CIS-2.2.1.3) Please note that with CIS_Ubuntu_Linux_20.04_LTS_Benchmark_v1.1.0 by CIS the numbering is no longer aligned to the xccdf file with xccdf_com.ubuntu.focal.cis_rule_CIS-2.2.1.3 === Procedure: Verify that only one time synchronization method is in use on the system: Run the following command to verify that ntp is not installed. # dpkg -s ntp | grep -E '(Status:|not installed)' Expected result: dpkg-query: package 'ntp' is not installed and no information is available Actual result: dpkg-query: package 'ntp' is not installed and no information is available === NEXT Run the following command to verify that systemd-timsyncd is masked: # systemctl is-enabled systemd-timesyncd Expected result: masked Actual result: masked === NEXT Verify that chrony is configured: Run the following command and verify remote server is configured properly: # grep -E "^(server|pool)" /etc/chrony/chrony.conf Expected result: server Actual result: server 0.pool.ntp.org minpoll 8 server 1.pool.ntp.org minpoll 8 server 2.pool.ntp.org minpoll 8 server 3.pool.ntp.org minpoll 8 === NEXT Run the following command and verify the first field for the chronyd process is _chrony: # ps -ef | grep chronyd Expected result: _chrony 491 1 0 20:32 ? 00:00:00 /usr/sbin/chronyd Actual result: _chrony 1092 1 0 17:35 ?00:00:00 /usr/sbin/chronyd -F -1 _chrony 10991092 0 17:35 ?00:00:00 /usr/sbin/chronyd -F -1 === === No errors or events within the logs. === OS Version (lsb_release) Description: Ubuntu 20.04.3 LTS Release: 20.04 Codename: focal US Version 27.2.2~20.04.1 ua status SERVICE ENTITLED STATUS DESCRIPTION cis yes enabled Center for Internet Security Audit Tools esm-infra yes enabled UA Infra: Extended Security Maintenance (ESM) fips yes disabled NIST-certified core packages fips-updates yes disabled NIST-certified core packages with priority security updates livepatch yes enabled Canonical Livepatch service === Expected result is that it should pass but process fails. ** Affects: ubuntu-advantage-tools (Ubuntu) Importance: Undecided Status: New ** Tags: cis-audit -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943188 Title: Ensure chrony is configured (Automated) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1943188/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1942010] Re: Ensure lockout for failed password attempts is configured
Hi, thanks for the suggestion. I can confirm that works (manual intervention). Files attached. The reason for the manual addition originally is that the hardening script failed to touch the files and add the lines as per the code snippet. I just used a fresh image as a test, same result from default build. The hardening script seems to fail to inject the code. Not sure why. Will keep testing. Scott ** Attachment added: "common-files" https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1942010/+attachment/5524209/+files/common-files.zip -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1942010 Title: Ensure lockout for failed password attempts is configured To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1942010/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1942010] Re: Ensure lockout for failed password attempts is configured
Please find attached. ** Attachment added: "common-account.txt" https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1942010/+attachment/5522351/+files/common-account.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1942010 Title: Ensure lockout for failed password attempts is configured To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1942010/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1942010] Re: Ensure lockout for failed password attempts is configured
Please find attached. ** Attachment added: "common-auth.txt" https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1942010/+attachment/5522352/+files/common-auth.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1942010 Title: Ensure lockout for failed password attempts is configured To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1942010/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1942010] Re: Ensure lockout for failed password attempts is configured
** Tags added: cis-audit -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1942010 Title: Ensure lockout for failed password attempts is configured To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1942010/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1942010] [NEW] Ensure lockout for failed password attempts is configured
Public bug reported: Source: CIS_Ubuntu_Linux_20.04_LTS_Benchmark_v1.1.0.pdf Link: https://workbench.cisecurity.org/files/3228 (download PDF) cis-audit level2_server fails on rule_CIS-5.3.2 but passes all manual checks. === Title Ensure lockout for failed password attempts is configured Rulexccdf_com.ubuntu.focal.cis_rule_CIS-5.3.2 Result fail === 5.4.2 Ensure lockout for failed password attempts is configured (xccdf_com.ubuntu.focal.cis_rule_CIS-5.3.2) Please note that with CIS_Ubuntu_Linux_20.04_LTS_Benchmark_v1.1.0 by CIS the numbering is no longer aligned to the xccdf file with xccdf_com.ubuntu.focal.cis_rule_CIS-5.3.2. === Procedure: Verify password lockouts are configured. These settings are commonly configured with the pam_tally2.so modules found in /etc/pam.d/common-auth: # grep "pam_tally2" /etc/pam.d/common-auth Expected result: auth required pam_tally2.so onerr=fail audit silent deny=5 unlock_time=900 Actual result: auth required pam_tally2.so onerr=fail audit silent deny=5 unlock_time=900 === NEXT Verify the pam_deny.so module and pam_tally2.so modules are included in /etc/pam.d/common-account: # grep -E "pam_(tally2|deny)\.so" /etc/pam.d/common-account Expected result: account requisite pam_deny.so account requiredpam_tally2.so 0 Actual result: account requisite pam_deny.so account requiredpam_tally2.so === No errors or events within the logs. === OS Version (lsb_release) Description:Ubuntu 20.04.3 LTS Release:20.04 Codename: focal US Version 27.2.2~20.04.1 ua status SERVICE ENTITLED STATUSDESCRIPTION cis yes enabled Center for Internet Security Audit Tools esm-infra yes enabled UA Infra: Extended Security Maintenance (ESM) fips yes disabled NIST-certified core packages fips-updates yes disabled NIST-certified core packages with priority security updates livepatch yes enabled Canonical Livepatch service === Expected result is that it should pass but process fails. ** Affects: ubuntu-advantage-tools (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/1942010 Title: Ensure lockout for failed password attempts is configured To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1942010/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1784713] Re: cloud-init profile.d files use bash-specific builtin "local"
@Eli,
I can recreate your problem, but it looks to me like a bug in ksh. ksh
complains that 'local can only be used in a function, when as shown
below it *is* being used in a function.'
My suggestion is to file a bug with ksh2020.
root@focal1:~# ksh -c 'foo() { local a=1; echo $?; }; foo'
ksh: local: local can only be used in a function
1
root@focal1:~# ksh2020 -c 'foo() { local a; echo $?; }; foo'
ksh2020: local: local can only be used in a function
1
also oddly, ksh seems to report itself in '$SHELL' as /bin/sh.
root@focal1:~# /usr/bin/ksh2020 -c 'foo() { local a=1; echo $?; }; echo
$SHELL; foo'
/bin/sh
/usr/bin/ksh2020: local: local can only be used in a function
1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1784713
Title:
cloud-init profile.d files use bash-specific builtin "local"
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1784713/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940711] [NEW] sign-efi-sig-list uses PKCS7 for variable updates
Public bug reported: When building some software (https://github.com/puzzleos/uefi-dev) I ran into a problem/bug in efitools 'sign-efi-sig-list'. The end result in my case was that an attempt to update the PK variable in uefi (ovmf files from 20.04 with qemu from 20.04) resulted in an exit code of 26 (EFI_SECURITY_VIOLATION). FS0:\> sb_setup.efi SB_SETUP: attempting to configure UEFI Secure Boot SB_SETUP: system is in Setup Mode SB_SETUP: KEK installed SB_SETUP: db installed SB_SETUP: unable to set the PK variable (26) sign-efi-sig-list was used to generate an update to PK in the build process. The fix upstream is https://git.kernel.org/pub/scm/linux/kernel/git/jejb/efitools.git/commit/?id=e57bafc268511ad54598627b663a7ae86bd856f5 Unfortunately it does not easily cherry-pick to 1.8.1 (20.04's version). There is only a small amount of changes from 1.8.1 to 21.04's version (1.9.2), so the easiest/safest fix may be to just update. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: efitools 1.8.1-0ubuntu2 ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-63-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Aug 20 14:55:19 2021 InstallationDate: Installed on 2020-01-15 (582 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: TERM=screen.xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: efitools UpgradeStatus: Upgraded to focal on 2020-04-17 (490 days ago) ** Affects: efitools (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: efitools (Ubuntu Focal) Importance: Medium Status: Confirmed ** Tags: amd64 apport-bug focal third-party-packages ** Description changed: When building some software (https://github.com/puzzleos/uefi-dev) I ran into a problem/bug in efitools 'sign-efi-sig-list'. The end result in my case was that an attempt to update the PK variable in uefi (ovmf files from 20.04 with qemu from 20.04) resulted in an exit code of 26 (EFI_SECURITY_VIOLATION). + FS0:\> sb_setup.efi + SB_SETUP: attempting to configure UEFI Secure Boot + SB_SETUP: system is in Setup Mode + SB_SETUP: KEK installed + SB_SETUP: db installed + SB_SETUP: unable to set the PK variable (26) - FS0:\> sb_setup.efi - SB_SETUP: attempting to configure UEFI Secure Boot - SB_SETUP: system is in Setup Mode - SB_SETUP: KEK installed - SB_SETUP: db installed - SB_SETUP: unable to set the PK variable (26) + sign-efi-sig-list was used to generate an update to PK in the build + process. - - The fix upstream is https://git.kernel.org/pub/scm/linux/kernel/git/jejb/efitools.git/commit/?id=e57bafc268511ad54598627b663a7ae86bd856f5 + The fix upstream is + https://git.kernel.org/pub/scm/linux/kernel/git/jejb/efitools.git/commit/?id=e57bafc268511ad54598627b663a7ae86bd856f5 Unfortunately it does not easily cherry-pick to 1.8.1 (20.04's version). - There is only a small amount of changes from 1.8.1 to 21.04's version (1.9.2), so - the easiest/safest fix may be to just update. + There is only a small amount of changes from 1.8.1 to 21.04's version + (1.9.2), so the easiest/safest fix may be to just update. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: efitools 1.8.1-0ubuntu2 ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-63-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Aug 20 14:55:19 2021 InstallationDate: Installed on 2020-01-15 (582 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: - TERM=screen.xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=screen.xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash SourcePackage: efitools UpgradeStatus: Upgraded to focal on 2020-04-17 (490 days ago) ** Also affects: efitools (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: efitools (Ubuntu) Status: New => Fix Released ** Changed in: efitools (Ubuntu Focal) Status: New => Confirmed ** Changed in: efitools (Ubuntu Focal) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940711 Title: sign-efi-sig-list uses PKCS7 for variable updates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/efitools/+bug/1940711/+subscriptions --
[Bug 1100758] Re: suds.sax.text.Text objects with unicode cannot be encoded when used in lists
I believe this is no longer an issue because it doesn't occur under Python 3 and Python 2 is EOL. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1100758 Title: suds.sax.text.Text objects with unicode cannot be encoded when used in lists To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/suds/+bug/1100758/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1932145] Re: rustc 1.51 and cargo 0.52 required by firefox 91
This released on Bionic and Hirsute a week ago, but Focal still has Rustc 1.47.0. Is there a reason for that? (1.51 also doesn't seem to be in any of the Focal branches on https://code.launchpad.net/ubuntu/+source/rustc, but I don't entirely know how the workflow for package releases works.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1932145 Title: rustc 1.51 and cargo 0.52 required by firefox 91 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cargo/+bug/1932145/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934761] Re: gnome keyboard settings panel enforces single iso-level3-shift key
This issue was fixed in https://gitlab.gnome.org/GNOME/gnome-control- center/-/merge_requests/994 which avoids changing `xkb-options` unless the Alternate Characters dialog is opened. (That was originally part of MR 910, but was split off so it could be merged without being blocked on design concerns.) I've just added an additional commit to https://gitlab.gnome.org/GNOME/gnome-control-center/-/merge_requests/910 to also not change `xkb-options` on opening the dialog unless the setting is actually changed, with is less necessary but probably an improvement. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934761 Title: gnome keyboard settings panel enforces single iso-level3-shift key To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1934761/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1939157] Re: HWE kernels: NFSv4.1 NULL pointer dereference
** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1939157 Title: HWE kernels: NFSv4.1 NULL pointer dereference To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939157/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1939157] [NEW] HWE kernels: NFSv4.1 NULL pointer dereference
Public bug reported: Ubuntu 20.04 systems running as NFSv4.1 clients are experiencing crashes (in this case with a NetApp filer mounted): [ 266.199481] BUG: kernel NULL pointer dereference, address: [ 266.199495] #PF: supervisor read access in kernel mode [ 266.199500] #PF: error_code(0x) - not-present page [ 266.199503] PGD 0 P4D 0 [ 266.199511] Oops: [#1] SMP PTI [ 266.199518] CPU: 15 PID: 2244 Comm: tracker-extract Not tainted 5.11.0-25-generic #27~20.04.1-Ubuntu [ 266.199525] Hardware name: Intel Corporation S2600GZ/S2600GZ, BIOS SE5C600.86B.02.06.0006.032420170950 03/24/2017 [ 266.199529] RIP: 0010:pnfs_mark_matching_lsegs_return+0xfe/0x140 [nfsv4] [ 266.199631] Code: f0 41 80 4d 50 08 49 8b 06 4d 89 f5 4c 39 75 d0 75 9b 8b 45 bc 85 c0 75 3b 48 8b 45 c8 48 8b 50 38 48 83 c0 38 48 39 c2 74 23 <41> 8b 34 24 48 8b 7d c8 44 89 fa e8 42 e0 ff ff 31 c0 48 83 c4 20 [ 266.199637] RSP: 0018:ae23a19a7c88 EFLAGS: 00010297 [ 266.199642] RAX: a048621ef238 RBX: a048621ef238 RCX: [ 266.199646] RDX: a04847636780 RSI: a04847636780 RDI: a048621ef200 [ 266.199650] RBP: ae23a19a7cd0 R08: 0001 R09: a086febdcc10 [ 266.199653] R10: a0677ffd6b80 R11: 0003 R12: [ 266.199657] R13: a048621ef228 R14: a048621ef228 R15: [ 266.199661] FS: 7f9de3440340() GS:a086febc() knlGS: [ 266.199665] CS: 0010 DS: ES: CR0: 80050033 [ 266.199669] CR2: CR3: 00012ed86006 CR4: 001706e0 [ 266.199674] Call Trace: [ 266.199682] _pnfs_return_layout+0x13d/0x2c0 [nfsv4] [ 266.199755] ? nfs_put_delegation+0x4c/0x70 [nfsv4] [ 266.199814] nfs4_evict_inode+0x78/0x80 [nfsv4] [ 266.199870] evict+0xd2/0x180 [ 266.199879] iput+0x18f/0x200 [ 266.199884] nfs_dentry_iput+0x33/0x60 [nfs] [ 266.199934] dentry_unlink_inode+0xb8/0x110 [ 266.199946] __dentry_kill+0xdf/0x180 [ 266.199953] dput+0x171/0x320 [ 266.199960] do_renameat2+0x387/0x500 [ 266.199968] __x64_sys_rename+0x45/0x50 [ 266.199974] do_syscall_64+0x38/0x90 [ 266.199987] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 266.16] RIP: 0033:0x7f9de644200b [ 266.23] Code: e8 aa ce 0a 00 85 c0 0f 95 c0 0f b6 c0 f7 d8 5d c3 66 0f 1f 44 00 00 b8 ff ff ff ff 5d c3 90 f3 0f 1e fa b8 52 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 05 c3 0f 1f 40 00 48 8b 15 51 4e 18 00 f7 d8 [ 266.28] RSP: 002b:7ffe70e5f008 EFLAGS: 0246 ORIG_RAX: 0052 [ 266.200014] RAX: ffda RBX: 55a5ed503070 RCX: 7f9de644200b [ 266.200018] RDX: 55a5ed37b940 RSI: 55a5ed1db250 RDI: 55a5ed4aea00 [ 266.200022] RBP: 55a5ed503060 R08: R09: [ 266.200025] R10: 000d R11: 0246 R12: 0001 [ 266.200029] R13: 55a5ed503078 R14: 55a5ed503040 R15: 55a5ed37b980 [ 266.200036] Modules linked in: nfs_layout_nfsv41_files rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace nfs_ssc fscache intel_rapl_msr intel_rapl_common sb_edac x86_pkg_temp_thermal intel_powerclamp coretemp crct10dif_ pclmul ghash_clmulni_intel aesni_intel crypto_simd cryptd glue_helper mgag200 rapl joydev input_leds intel_cstate drm_kms_helper ipmi_si ipmi_devintf cec rc_core fb_sys_fops syscopyarea sysfillrect mei_me ipmi_msghandler s ysimgblt mei ioatdma mac_hid ip6t_REJECT nf_reject_ipv6 nf_log_ipv6 xt_hl ip6t_rt ipt_REJECT nf_reject_ipv4 xt_comment nf_log_ipv4 nf_log_common xt_addrtype xt_limit xt_LOG xt_recent xt_tcpudp sch_fq_codel xt_state xt_conn This bug occurs in all recent 20.04 HWE kernels (both 5.8 and 5.11). I believe it is fixed by https://patchwork.kernel.org/project/linux- nfs/patch/20210519165451.412566-1-anna.schuma...@netapp.com/ -- please consider backporting this patch. (The bug was briefly also present in the 5.4 kernels, but was fixed in 5.4.0-79: see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1936673) ** Affects: linux (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/1939157 Title: HWE kernels: NFSv4.1 NULL pointer dereference To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939157/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928393] Re: linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0] retry page fault"
It happened to me too ** Attachment added: "Crash log of amdgpu driver" https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1928393/+attachment/5516220/+files/amdgu_crash.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928393 Title: linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0] retry page fault" To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1928393/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1939081] [NEW] package fonts-adf-gillius (not installed) failed to install/upgrade: trying to overwrite '/usr/share/fonts/truetype/adf/GilliusADF-Bold.otf', which is also in package ttf-adf-gilli
Public bug reported: GEneral install crap out, probably my fault, ignore ProblemType: Package DistroRelease: Ubuntu 20.04 Package: fonts-adf-gillius (not installed) ProcVersionSignature: Ubuntu 5.4.0-80.90-generic 5.4.124 Uname: Linux 5.4.0-80-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Aug 5 14:48:07 2021 DuplicateSignature: package:fonts-adf-gillius:(not installed) Unpacking fonts-adf-accanthis (0.20190904-1.1) ... dpkg: error processing archive /tmp/apt-dpkg-install-pm3Dvj/101-fonts-adf-accanthis_0.20190904-1.1_all.deb (--unpack): trying to overwrite '/usr/share/fonts/truetype/adf/AccanthisADFStd-Bold.otf', which is also in package ttf-adf-accanthis 0.20090423-2 ErrorMessage: trying to overwrite '/usr/share/fonts/truetype/adf/GilliusADF-Bold.otf', which is also in package ttf-adf-gillius 0.20090423-2 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: fonts-adf Title: package fonts-adf-gillius (not installed) failed to install/upgrade: trying to overwrite '/usr/share/fonts/truetype/adf/GilliusADF-Bold.otf', which is also in package ttf-adf-gillius 0.20090423-2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: fonts-adf (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal package-conflict -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1939081 Title: package fonts-adf-gillius (not installed) failed to install/upgrade: trying to overwrite '/usr/share/fonts/truetype/adf/GilliusADF- Bold.otf', which is also in package ttf-adf-gillius 0.20090423-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-adf/+bug/1939081/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918955] Re: SRU network: fix LXC_NET_NONE cleanup
Marking this fix-released in focal as bug 1923232 was released to focal. So this should be fixed in '1:4.0.6-0ubuntu1~20.04.1'. ** Changed in: lxc (Ubuntu Focal) 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/1918955 Title: SRU network: fix LXC_NET_NONE cleanup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1918955/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1707222] Re: usage of /tmp during boot is not safe due to systemd-tmpfiles-clean
Norman, Thanks for the comment. On first pass, it looks like you've diagnosed a failure correctly. Please open another bug and add output of 'cloud-init collect-logs'. thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1707222 Title: usage of /tmp during boot is not safe due to systemd-tmpfiles-clean To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1707222/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931509] Re: System hang with kernel general protection fault due to dell-wmi-sysman sysman_init failure
Can not reproduce on QA side with 1031 kernel over than 350 times SKU: ANDW-DVT2-C3 Image: canonical-oem-somerville-focal-amd64-20200502-85+fossa-mewtwo+X101 bios-version: 1.3.0 kernel:5.10.0-1031-oem -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931509 Title: System hang with kernel general protection fault due to dell-wmi- sysman sysman_init failure To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1931509/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1923232] Re: SRU of LXC 4.0.6 to focal (upstream bugfix release)
lxc auto package tests show green for 4.0.6-0ubuntu1 other than i386, which failed previously. * amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/l/lxc/20210525_040935_c4b64@/log.gz * arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/arm64/l/lxc/20210525_041453_b8cfc@/log.gz * armhf: (skipped) https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/armhf/l/lxc/20210525_035510_ea5c7@/log.gz * i386: (failed) https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/i386/l/lxc/20210525_035427_d5ede@/log.gz * ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/ppc64el/l/lxc/20210525_040452_d2faa@/log.gz * s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/s390x/l/lxc/20210525_040245_aea9b@/log.gz Given the comments above from bdmurray and stgraber, and also the '[Test Case]' section in the SRU template, I think that should qualify as 'verification-done'. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1923232 Title: SRU of LXC 4.0.6 to focal (upstream bugfix release) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1923232/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918955] Re: SRU network: fix LXC_NET_NONE cleanup
** Description changed: Hi. I'm using 20.04, and I need a fix for https://github.com/lxc/lxc/pull/3589 I think my only options to get that via packaging are a.) https://launchpad.net/~ubuntu-lxc/+archive/ubuntu/lxc-git-master b.) build my own. I don't love either of those options. Can we please get a SRU update to 20.04 of an lxc with that fix? The fix is not in 4.0.5, so I marked this as affecting Groovy (currently 1:4.0.4-0ubuntu3) without testing. + + + Related bugs: + * #1923232: SRU of LXC 4.0.6 to focal (upstream bugfix release) ** Description changed: Hi. I'm using 20.04, and I need a fix for https://github.com/lxc/lxc/pull/3589 I think my only options to get that via packaging are a.) https://launchpad.net/~ubuntu-lxc/+archive/ubuntu/lxc-git-master b.) build my own. I don't love either of those options. Can we please get a SRU update to 20.04 of an lxc with that fix? The fix is not in 4.0.5, so I marked this as affecting Groovy (currently 1:4.0.4-0ubuntu3) without testing. - Related bugs: - * #1923232: SRU of LXC 4.0.6 to focal (upstream bugfix release) + * bug 1923232: SRU of LXC 4.0.6 to focal (upstream bugfix release) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918955 Title: SRU network: fix LXC_NET_NONE cleanup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1918955/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918955] Re: SRU network: fix LXC_NET_NONE cleanup
Just fwi, this is in 4.0.6 which is up for SRU in LP: #1923232. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918955 Title: SRU network: fix LXC_NET_NONE cleanup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1918955/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
