Hi Andrew (and list),

On Wed, Jan 15, 2025, at 14:49, Andrew Greig via luv-main wrote:
> Hi All
>
> I am trying to remove all vestiges of Google Chrome because it will not 
> update, it calls for an uninstall re-install.
>
> Ubuntu 22.04 LTS Jammy I have come up against this:
>
>
> ~$ sudo apt-get purge google-chrome-stable
> Reading package lists... Done
> Building dependency tree... Done
> Reading state information... Done
> The following packages will be REMOVED:
>    google-chrome-stable*
> 0 to upgrade, 0 to newly install, 1 to remove and 324 not to upgrade.
> After this operation, 348 MB disk space will be freed.
> Do you want to continue? [Y/n] y
> dpkg: unrecoverable fatal error, aborting:
>   loading files list file for package 'mutter-common': cannot open 
> /var/lib/dpkg/info/mutter-common.list (Input/output error)
> libdvd-pkg: Checking orig.tar integrity...
> /usr/src/libdvd-pkg/libdvdcss_1.4.3.orig.tar.bz2: OK
> libdvd-pkg: `apt-get check` failed, you may have broken packages. 
> Aborting...
> E: Sub-process /usr/bin/dpkg returned an error
>
> How do I poceed, please?

What jumped out at me is the

    /var/lib/dpkg/info/mutter-common.list (Input/output error)

That suggest to me that you're getting some sort of disk error
in a file accessed by dpkg, not particularly related to Google
Chrome itself.

What happens if you try to read that mutter-common.list file (by
just catting it, or trying to open it in a file manager)?

https://packages.debian.org/sid/mutter-common says that this
package contains the shared files of mutter display server, etc.
(This link is for sid release, the first one I found on a web
search, but it should be much the same for other releases.)

I don't know enough about the internals of dkpg workings to
suggest how to replace that broken file with a good copy.
Probably you could extract it from a good copy of the .deb file.

But the "Input/output error" suggests that you might have a
bigger problem, a failing disk drive, which would need replacing
soon.  But then, it might have been just a sporadic error that
can be fixed by replacing the broken file.  So before you jump
to replacing the disk drive, just monitor what's happening and
make sure you have good backups of important files.

What filesystem are you using?  If it's btrfs, you could do a
btrfs-scrub.  Whatever filesystem, you could use smartctl from
package smartmontools to check on the health of your disk drive.

I hope some of this is useful.


— Smiles, Les.
_______________________________________________
luv-main mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to