package chromium-browser (not installed) failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 1

Bug #2038609 reported by David Lang
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Snap Store Server
New
Undecided
Unassigned
chromium-browser (Ubuntu)
Invalid
Undecided
Unassigned
snapd (Ubuntu)
New
Undecided
Unassigned

Bug Description

failed to install

ProblemType: Package
DistroRelease: Ubuntu 23.10
Package: chromium-browser (not installed)
ProcVersionSignature: Ubuntu 6.5.0-7.7-generic 6.5.3
Uname: Linux 6.5.0-7-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.27.0-0ubuntu4
AptOrdering:
 chromium-browser:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
CasperMD5CheckResult: pass
Date: Thu Oct 5 23:37:38 2023
ErrorMessage: new chromium-browser package pre-installation script subprocess returned error exit status 1
InstallationDate: Installed on 2023-10-06 (0 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230417)
Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.22.0ubuntu1
 apt 2.7.3
SourcePackage: chromium-browser
Title: package chromium-browser (not installed) failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 1
UpgradeStatus: Upgraded to mantic on 2023-10-06 (0 days ago)

Revision history for this message
David Lang (david-lang) wrote :
Revision history for this message
Nathan Teodosio (nteodosio) wrote :

> - Fetch and check assertions for snap "chromium" (2642) (cannot verify snap "chromium", no matching signatures found)

Looks like a transient failure, could you please try again?

Revision history for this message
David Lang (david-lang) wrote : Re: [Bug 2038609] Re: package chromium-browser (not installed) failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 1

On Fri, 6 Oct 2023, Nathan Teodosio wrote:

>> - Fetch and check assertions for snap "chromium" (2642) (cannot verify
> snap "chromium", no matching signatures found)
>
> Looks like a transient failure, could you please try again?

I tried at least four times, twice after a reboot, same error each time.

David Lang

Revision history for this message
David Lang (david-lang) wrote :

On Fri, 6 Oct 2023, David Lang wrote:

> On Fri, 6 Oct 2023, Nathan Teodosio wrote:
>
>>> - Fetch and check assertions for snap "chromium" (2642) (cannot verify
>> snap "chromium", no matching signatures found)
>>
>> Looks like a transient failure, could you please try again?
>
> I tried at least four times, twice after a reboot, same error each time.

still reporting unable to validate the snap, no matching signatures (and I did
do apt update to make sure I had the latest)

David Lang

Revision history for this message
Nathan Teodosio (nteodosio) wrote :

I cannot reproduce it.

Given the nature of the error this must be something in Snapd or in the Snapstore.

Are you able to install the snap from a different channel, say,

  snap install --candidate chromium

? Are you able to install different snaps?

Changed in chromium-browser (Ubuntu):
status: New → Invalid
Revision history for this message
Felix Exner (fexner) wrote :

Same here, also ubuntu 23.10, snapd version 2.60.4+23.10.1. Trying the candidate channel produces the same error.

I've successfully installed other snaps.

Revision history for this message
Nathan Teodosio (nteodosio) wrote :

> the same error.

Which one? If the one in DpkgHistoryLog.txt, it really looks like a store/snapd bug, maybe follow up in the forum. Found this: https://forum.snapcraft.io/t/cannot-performe-any-task-using-snap.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.