[Bug 2079785] Re: apt / apt-get install produce spurious Warning
Ah, spoke too soon. BEFORE apt-utils installed - ALL installs produce W mesasge AFTER apt-utils installed - NEW installs only produce W message; re- installing packages which have been been removed does NOT produce W message. Removing using 'apt purge' displays furterh warnings about pemrission failures when deleting. Test case apt install xkcdpass W message displayed apt remove xkcdpass no warnings apt install xkcdpass no message displayed apt purge xkcdpasswarnings displayed - Permission denied removing file from /var/cache/man apt install xkcdpass no message displayed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2079785 Title: apt / apt-get install produce spurious Warning To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2079785/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2079785] Re: apt / apt-get install produce spurious Warning
Update - solution of sorts? I noticed from the output of a batch update that immediately after all the GET lines, there was debconf: delaying package configuration, since apt-utils is not installed I must admit I've never heard of apt-utils, and it evidently isn't installed as a dependency in the base system. So, out of curiosity, I installed it (and of course got the W message). However, subsequent installs are now clean - no more warnings. So - either something in apt-utils is required (and so apt-utils should be included in the minimal install configuration out the box) or remediates the "problem" so may give you a clue as to its cause. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2079785 Title: apt / apt-get install produce spurious Warning To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2079785/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2079785] Re: apt / apt-get install produce spurious Warning
** Description changed: A new minimal install of Ubuntu Server 24.04 has started giving a W message on completion of all installs: W: Download is performed unsandboxed as root as file '/var/cache/apt/archives/partial/' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) This seems to be spurious, as on checking /var/cache/apt/archives/partial has correct _apt:root ownership, mode 700. I have set ownership on everything from /var/cache/apt down to _apt:root, but it makes no difference - the warning continues to be emitted on all installs, using both apt and apt-get. From widespread discussion I've found online, this seems to be a common issue with no obvious cause or solution other than to make root the sandbox user in /etc/apt/apt.conf.d, which seem to me to not be a solution at all! I agree that _apt should be used with reduced privileges for downloading, but it seems that something in the changes you made to implement this is broken. + The only non-standard thing about the install I can think of is that + /var is symlinked to /zen/var/ where /zen mounts another partition (we + prefer to keep data directories such as /var, /srv and /tmp off the + system volume). However, we have the same arrangement on other systems + and don't have this issue everywhere. + I'll attach my ubuntu-bug report here, as the machine which generated it is headless. Thanks C ** Description changed: A new minimal install of Ubuntu Server 24.04 has started giving a W - message on completion of all installs: + message on completion of all apt and apt-get installs: W: Download is performed unsandboxed as root as file '/var/cache/apt/archives/partial/' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) This seems to be spurious, as on checking /var/cache/apt/archives/partial has correct _apt:root ownership, mode 700. I have set ownership on everything from /var/cache/apt down to _apt:root, but it makes no difference - the warning continues to be emitted on all installs, using both apt and apt-get. From widespread discussion I've found online, this seems to be a common issue with no obvious cause or solution other than to make root the sandbox user in /etc/apt/apt.conf.d, which seem to me to not be a solution at all! I agree that _apt should be used with reduced privileges for downloading, but it seems that something in the changes you made to implement this is broken. The only non-standard thing about the install I can think of is that /var is symlinked to /zen/var/ where /zen mounts another partition (we prefer to keep data directories such as /var, /srv and /tmp off the system volume). However, we have the same arrangement on other systems and don't have this issue everywhere. I'll attach my ubuntu-bug report here, as the machine which generated it is headless. Thanks C -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2079785 Title: apt / apt-get install produce spurious Warning To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2079785/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2079785] Re: apt / apt-get install produce spurious Warning
** Description changed: A new minimal install of Ubuntu Server 24.04 has started giving a W message on completion of all installs: W: Download is performed unsandboxed as root as file '/var/cache/apt/archives/partial/' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) This seems to be spurious, as on checking /var/cache/apt/archives/partial has correct _apt:root ownership, mode 700. I have set ownership on everything from /var/cache/apt down to _apt:root, but it makes no difference - the warning continues to be emitted on all installs, using both apt and apt-get. From widespread discussion I've found online, this seems to be a common issue with no obvious cause or solution other than to make root the sandbox user in /etc/apt/apt.conf.d, which seem to me to not be a solution at all! I agree that _apt should be used with reduced - privileges for downlaoading, but it seems that something in the changes + privileges for downloading, but it seems that something in the changes you made to implement this is broken. I'll attach my ubuntu-bug report here, as the machine which generated it is headless. Thanks - Colin + C -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2079785 Title: apt / apt-get install produce spurious Warning To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2079785/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2079785] [NEW] apt / apt-get install produce spurious Warning
Public bug reported: A new minimal install of Ubuntu Server 24.04 has started giving a W message on completion of all installs: W: Download is performed unsandboxed as root as file '/var/cache/apt/archives/partial/' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) This seems to be spurious, as on checking /var/cache/apt/archives/partial has correct _apt:root ownership, mode 700. I have set ownership on everything from /var/cache/apt down to _apt:root, but it makes no difference - the warning continues to be emitted on all installs, using both apt and apt-get. From widespread discussion I've found online, this seems to be a common issue with no obvious cause or solution other than to make root the sandbox user in /etc/apt/apt.conf.d, which seem to me to not be a solution at all! I agree that _apt should be used with reduced privileges for downlaoading, but it seems that something in the changes you made to implement this is broken. I'll attach my ubuntu-bug report here, as the machine which generated it is headless. Thanks Colin ** Affects: apt (Ubuntu) Importance: Undecided Status: New ** Tags: apt download install permissions warning ** Attachment added: "ubuntu-bug report" https://bugs.launchpad.net/bugs/2079785/+attachment/5813842/+files/apport.apt.c0blqzu2.apport -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2079785 Title: apt / apt-get install produce spurious Warning To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2079785/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065174] [NEW] ser2net v4.6.0 has bugfix releases that haven't been applied
Public bug reported: The command `ser2net -v` returns an error code in 4.6.0 when it shouldn't. This was fixed in v4.6.2 The command also has an additional functional bug in 4.6.0 surrounding rfc2217 flushing which was fixed in 4.6.1. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: ser2net 4.6.0-1build2 ProcVersionSignature: Ubuntu 6.8.0-1004.4-raspi 6.8.1 Uname: Linux 6.8.0-1004-raspi aarch64 ApportVersion: 2.28.1-0ubuntu2 Architecture: arm64 CasperMD5CheckResult: unknown CloudArchitecture: aarch64 CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSubPlatform: config-disk (/dev/mmcblk0p1) Date: Wed May 8 07:16:04 2024 ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-color XDG_RUNTIME_DIR= SourcePackage: ser2net UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ser2net (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug arm64 noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065174 Title: ser2net v4.6.0 has bugfix releases that haven't been applied To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ser2net/+bug/2065174/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947618] Re: [i915] CPU locks up on Ubuntu 21.10 boot when 2 displays are connected
Confirmed, my system boots fine when that second monitor isn't plugged in. I removed the bluetooth driver as well, but that didn't fix it. This is the adapter I'm using (I believe): https://us.amazon.com/NiaoChao-Adapter-Charging-Compatible-MacBook/dp/B08CRXD22M I have a bunch of USBC / HDMI adapters around, so maybe other ones won't halt the boot. The kernel I'm running: 5.13.0-41-generic #46~20.04.1-Ubuntu SMP Wed Apr 20 13:16:21 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947618 Title: [i915] CPU locks up on Ubuntu 21.10 boot when 2 displays are connected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947618/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947618] Re: [i915] CPU locks up on Ubuntu 21.10 boot when 2 displays are connected
I'm seeing the same thing with 20.04 when running any of the 5.13 kernels. Last tested with 5.13.0-41. My setup is an ASUS Hero XIII motherboard. Monitor plugged in, with a second monitor plugged in via a USB / HDMI adapter (not sure if that is relevant) I had to remove iwlwifi-ty-a0-gf-a0.pnvm and iwlwifi- ty-a0-gf-a0-63.ucode to get wifi to work, but the boot hangs with any 5.13 kernels. Only 5.11 will work, unfortunately. Some of the bluetooth startup info when it fails (5.13): Bluetooth: Core ver 2.22 NET: Registered protocol family 31 Bluetooth: HCI device and connection manager initialized Bluetooth: HCI socket layer initialized Bluetooth: L2CAP socket layer initialized Bluetooth: SCO socket layer initialized Intel(R) Wireless WiFi driver for Linux iwlwifi :04:00.0: enabling device ( -> 0002) iwlwifi :04:00.0: Direct firmware load for iwlwifi-ty-a0-gf-a0-63.ucode failed with error -2 iwlwifi :04:00.0: Direct firmware load for iwlwifi-ty-a0-gf-a0-62.ucode failed with error -2 iwlwifi :04:00.0: Direct firmware load for iwlwifi-ty-a0-gf-a0-61.ucode failed with error -2 iwlwifi :04:00.0: Direct firmware load for iwlwifi-ty-a0-gf-a0-60.ucode failed with error -2 usbcore: registered new interface driver btusb iwlwifi :04:00.0: api flags index 2 larger than supported by driver iwlwifi :04:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version: 93.8.63.28 iwlwifi :04:00.0: loaded firmware version 59.601f3a66.0 ty-a0-gf-a0-59.ucode op_mode iwlmvm Bluetooth: hci0: Firmware timestamp 2022.9 buildtype 1 build 40196 Bluetooth: hci0: Found device firmware: intel/ibt-0041-0041.sfi Bluetooth: hci0: Boot Address: 0x100800 Bluetooth: hci0: Firmware Version: 175-42.20 The startup info when it succeeds (5.11): Bluetooth: Core ver 2.22 NET: Registered protocol family 31 Bluetooth: HCI device and connection manager initialized Bluetooth: HCI socket layer initialized Bluetooth: L2CAP socket layer initialized Bluetooth: SCO socket layer initialized usbcore: registered new interface driver btusb Reached target Bluetooth. Starting Bluetooth service... Bluetooth: hci0: Firmware timestamp 2020.42 buildtype 1 build 15791 I haven't upgraded yet, but I booted to the 2022.04 image and I was pleased to see everything booted up without any issues. I'll see if there's anything else to try - maybe around that ibt-0041-0041.sfi firmware -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947618 Title: [i915] CPU locks up on Ubuntu 21.10 boot when 2 displays are connected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947618/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
