package firefox 97.0+build2-0ubuntu0.20.04.1 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 1
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
firefox (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
failed to install while doing an upgrade on a fresh install.
ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: firefox 97.0+build2-
ProcVersionSign
Uname: Linux 5.13.0-30-generic x86_64
AddonCompatChec
ApportVersion: 2.20.11-0ubuntu82.4
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
BuildID: 20220202182137
CasperMD5CheckR
Channel: Unavailable
Date: Sun Apr 30 12:22:58 2023
ErrorMessage: new firefox package pre-installation script subprocess returned error exit status 1
ForcedLayersAccel: False
InstallationDate: Installed on 2023-04-30 (0 days ago)
InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
IpRoute:
default via 10.0.0.1 dev enp3s0 proto dhcp metric 100
default via 10.0.0.1 dev enp3s0 proto dhcp metric 20100
10.0.0.0/24 dev enp3s0 proto kernel scope link src 10.0.0.11 metric 100
169.254.0.0/16 dev enp3s0 scope link metric 1000
NoProfiles: True
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
Python3Details: /usr/bin/
PythonDetails: N/A
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageV
dpkg 1.21.1ubuntu2.1
apt 2.4.9
RunningIncompat
SourcePackage: firefox
Title: package firefox 97.0+build2-
UpgradeStatus: Upgraded to jammy on 2023-04-30 (0 days ago)
dmi.bios.date: 09/07/2012
dmi.bios.release: 8.6
dmi.bios.vendor: AMI
dmi.bios.version: 8.06
dmi.board.
dmi.board.name: 2AF0
dmi.board.vendor: PEGATRON CORPORATION
dmi.board.version: 1.02
dmi.chassis.
dmi.chassis.type: 3
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnAMI:
dmi.product.family: 103C_53316J G=D
dmi.product.name: 20-b014
dmi.product.sku: H3Z01AA#ABA
dmi.sys.vendor: Hewlett-Packard
tags: | removed: need-duplicate-check |
Hello, and sorry for the slow reply here.
Based on the attached dpkg terminal logs, it appears that the snapd version available on your system at the time was rather old and didn't support the 'mount' command. If you still have access to that system, you may want to try upgrading snapd to the latest version using 'sudo apt-get upgrade snapd' and/or 'sudo snap refresh snapd'. Could you by any chance still reproduce this bug today?