To remove dbus-python 1.3.2-3, to install python-dbus 1.3.2-4

Support Software & Applications
1

Hi,
I tried applying a big update today (I just mean there were tons of packages to be updated), it downloaded everything and then “failed to commit”

I tried just doing one package at a time and it seems there is an issue with dbus-python 1.3.2-3 as mentioned in my topic. It wants to remove it and add python-dbus 1.3.2-4.

But, it just keeps saying “failed to commit transaction”.

So, I can’t update or install or re-install any package at the moment.

Any help to get these updates installed? Thanks!

2

Yes, that is how it should be. If you cannot update it for whatever reason, try removing the package first and then reinstalling python-dbus.

3

You must rebuild or remove this 3rd party package.

4

And when I try to remove dbus-python 1.3.2-3, I get this error:

Warning: installing icu (75.1-1) breaks dependency 'libicui18n.so=74-64' required by electron25
Add electron25 to remove
Warning: installing icu (75.1-1) breaks dependency 'libicuuc.so=74-64' required by electron25
Add electron25 to remove
5

Ok, I’ll try that. Thanks.

6

when a package is created to replace another it is explicitly defined in the package.

thus the maintainer has very good reason and you should accept to replace any package suggested by the package manager.

you may run into other issues along those lines - handle them when they appear.

when it comes to electron - it is sensitive - in any case the package managers recommendattion should be followed

third party packages depending in specific versions of electron should be removed in order to proceed with the sync

7

When I try to remove electron25, I get this message:

Warning: installing icu (75.1-1) breaks dependency 'libicui18n.so=74-64' required by electron25
Add electron25 to remove
Warning: installing icu (75.1-1) breaks dependency 'libicuuc.so=74-64' required by electron25
Add electron25 to remove

It says add electron25 to remove, but, I already have electron25 installed. v 25.9.8-5

8

yes - and it is “in the way”
remove it
you can reinstall it later should you really need it

9 
sudo pacman -R electron25
sudo pacman -Syu

and agree to replace dbus-python when you get to that.

10

Ok, I got it removed somehow.

So, then I went back to trying to remove dbus-python and I get this message:

could not satisfy dependencies:
- removing dbus-python breaks dependency 'python-dbus' required by deluge

And I just keep removing one package at a time, but, I feel like this isn’t going well or properly.

11

Ok, I’ll try that. Thanks.

12

Wait

sudo pacman -R deluge

as well.

Are you seeing a pattern here?

Look to the package name aftter “required by” and remove it in the same way for any other similar dependency warnings.

13

Ok, I followed through with all the package removals. I had to remove hplip, pulseaudio-equalizer, system-config-printer.

Then I was able to remove dbus-python, command line worked.

Then I tried applying the all the updates again and everything seemed good, it all downloaded, integrity checks all good, and then…:

invalid or corrupted package (PGP signature):

Forgot to mention, when I issued the command from earlier (before removing hplip, pulseaudio-equalizer, system-config-printer):
sudo pacman -Syu

It asked to proceed with installation and I said yes.

Then it said:

(323/323) checking keys in keyring                                       [########################################] 100%
warning: Public keyring not found; have you run 'pacman-key --init'?
downloading required keys...
error: keyring is not writable
error: keyring is not writable
error: keyring is not writable
error: keyring is not writable
error: keyring is not writable
error: keyring is not writable
error: keyring is not writable
error: keyring is not writable
error: keyring is not writable
error: keyring is not writable
error: keyring is not writable
error: keyring is not writable
error: keyring is not writable
error: keyring is not writable
error: keyring is not writable
error: keyring is not writable
error: required key missing from keyring
error: failed to commit transaction (unexpected error)
Errors occurred, no packages were upgraded.

So, then I issued the command:
sudo pacman-key --init

(323/323) checking keys in keyring                                       [########################################] 100%
warning: Public keyring not found; have you run 'pacman-key --init'?
downloading required keys...
error: keyring is not writable
error: keyring is not writable
error: keyring is not writable
error: keyring is not writable
error: keyring is not writable
error: keyring is not writable
error: keyring is not writable
error: keyring is not writable
error: keyring is not writable
error: keyring is not writable
error: keyring is not writable
error: keyring is not writable
error: keyring is not writable
error: keyring is not writable
error: keyring is not writable
error: keyring is not writable
error: required key missing from keyring
error: failed to commit transaction (unexpected error)
Errors occurred, no packages were upgraded.

gpg: Generating pacman keyring master key...
gpg: revocation certificate stored as '/etc/pacman.d/gnupg/openpgp-revocs.[d/fksdfjsklfslkjf-I replaced this just in case].rev'
gpg: Done
==> Updating trust database...
gpg: public key of ultimately trusted key [sdlkjada08-I replaced this just in case] not found
gpg: marginals needed: 3  completes needed: 1  trust model: pgp
gpg: depth: 0  valid:   2  signed:   0  trust: 0-, 0q, 0n, 0m, 0f, 2u
==> ERROR: Trust database could not be updated.

I realized, I should have dealt with this first. Doing too many other things at once :slight_smile:

Any idea how to fix this?

14

I’ve rarely used it.
@linux-aarhus might be better versed in handling this in Manjaro.
(if he’s still online)

15

Ok, appreciate your help so far. Thanks.

16

I tried searching for this issue and came across another forum topic:

Can’t import keys (Stable Update 2023-07-10)

I tried issuing the command:
sudo pacman -S manjaro-keyring archlinux-keyring

And I got this message:

:: Proceed with installation? [Y/n] Y
(2/2) checking keys in keyring                                           [########################################] 100%
(2/2) checking package integrity                                         [########################################] 100%
error: manjaro-keyring: signature from "Philip Müller (Called Little) <philm@manjaro.org>" is unknown trust
:: File /var/cache/pacman/pkg/manjaro-keyring-20230719-2-any.pkg.tar.xz is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n] 
error: archlinux-keyring: signature from "Christian Hesse <eworm@archlinux.org>" is unknown trust
:: File /var/cache/pacman/pkg/archlinux-keyring-20240520-1-any.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n] n
error: failed to commit transaction (invalid or corrupted package (PGP signature))
Errors occurred, no packages were upgraded.

I answered no because I felt it might cause more problems, but, not really sure.

Any ideas at this point?

17

archlinux-keyring is just a package like any other. You should be able to just Y to delete the damaged ones and allow them to be replaced/upgraded.

sudo pacman-mirrors --continent && sudo pacman -Syu archlinux-keyring

should likely do it. At least, I don’t see why not.

18

Ok, I’m going to try it. after I create Manjaro install CD or something.

19

I couldn’t even delete it :slight_smile:

sudo pacman -S manjaro-keyring archlinux-keyring
warning: manjaro-keyring-20230719-2 is up to date -- reinstalling
warning: archlinux-keyring-20240520-1 is up to date -- reinstalling
resolving dependencies...
looking for conflicting packages...

Packages (2) archlinux-keyring-20240520-1  manjaro-keyring-20230719-2

Total Download Size:   1.17 MiB
Total Installed Size:  1.75 MiB
Net Upgrade Size:      0.00 MiB

:: Proceed with installation? [Y/n] Y
:: Retrieving packages...
 archlinux-keyring-20240520-1-any           1193.9 KiB  3.40 MiB/s 00:00 [########################################] 100%
(2/2) checking keys in keyring                                           [########################################] 100%
(2/2) checking package integrity                                         [########################################] 100%
error: archlinux-keyring: signature from "Christian Hesse <eworm@archlinux.org>" is unknown trust
:: File /var/cache/pacman/pkg/archlinux-keyring-20240520-1-any.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n] Y
error: failed to commit transaction (invalid or corrupted package (PGP signature))
Errors occurred, no packages were upgraded.
20

I found this post (from myself) from some time ago.
It was marked by others as the correct solution - or leading to it.
so:
have a look

Getting invalid or corrupted package (PGP signature) error when updating - #4 by Nachlese