You are not logged in.

#1 2021-06-08 16:27:14

frank1962
Member
Registered: 2021-05-10
Posts: 19

[SOLVED]update problems:libcanberra

During an update of Discover, I can't update from "0.30+2+gc0620e4-3" to "0.30+2+gc0620e4-4".

The error message is "Risoluzione della dipendenza non riuscita 0.30+2+gc0620e4-3"

Can anyone help me please ?

Last edited by frank1962 (2021-06-12 07:20:00)

Offline

#2 2021-06-08 16:45:05

Scimmia
Fellow
Registered: 2012-09-01
Posts: 11,599

Re: [SOLVED]update problems:libcanberra

Start by using pacman, not Discover. If you need to post error messages, prepend the command with LC_ALL=C

Offline

#3 2021-06-08 20:31:48

mpan
Member
Registered: 2012-08-01
Posts: 1,211
Website

Re: [SOLVED]update problems:libcanberra

After doing what Scimmia asked for, please also install community/pacman-contrib and provide the output of each of those commands:

$ pactree -r libcanberra-gstreamer
$ pactree -r libcanberra-pulse

Last edited by mpan (2021-06-08 20:32:50)


Sometimes I seem a bit harsh — don’t get offended too easily!

Offline

#4 2021-06-09 04:39:56

edacval
Member
From: .LT
Registered: 2008-10-23
Posts: 91

Re: [SOLVED]update problems:libcanberra

libcanberra-gstreamer does not exist anymore. It was removed in commit and leftover package prevents upgrades. You need to uninstall libcanberra-gstreamer before upgrading.

Offline

#5 2021-06-09 06:43:53

frank1962
Member
Registered: 2021-05-10
Posts: 19

Re: [SOLVED]update problems:libcanberra

pacman -Syu

:: Synchronizing package databases...
core                                                                        134.8 KiB   793 KiB/s 00:00 [##############################################################] 100%
extra                                                                      1562.6 KiB  9.78 MiB/s 00:00 [##############################################################] 100%
community                                                                     5.6 MiB  10.8 MiB/s 00:01 [##############################################################] 100%
multilib                                                                    150.1 KiB  5.64 MiB/s 00:00 [##############################################################] 100%
:: Starting full system upgrade...
:: Replace libcanberra-pulse with extra/libcanberra?Y/n

my answer must be Y, right?

Offline

#6 2021-06-09 06:46:01

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 21,790

Re: [SOLVED]update problems:libcanberra

Yes. General rule of thumb, if a change has happened deliberately and intentionally, pacman will preselect the Y option, if a replacement would happen due to packaging conflicts the preselected option would be N, if unsure pick whatever pacman preselects.

Offline

#7 2021-06-09 08:19:06

tcomarchetti
Member
Registered: 2021-04-21
Posts: 36

Re: [SOLVED]update problems:libcanberra

I had some issues with the last update of libcanberra, multimedia apps did not work properly after that update (like Spotify, I was unable to let songs start or I had sound issues with VLC); did someone have the same problems?

Offline

#8 2021-06-09 08:43:33

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 21,790

Re: [SOLVED]update problems:libcanberra

Very unlikely to impossible. libcanberra is for desktop/theme beeps and irrelevant for actual audio output (and the change in question here is purely cosmetic packaging simplification with no actual end user effect) and will definitely not be used for core playback features of these respective applications. The big ALSA bump to 1.2.5 is much more likely to have an effect here on specific setups, did you read pacman's warning to restart audio using applications after the alsa-lib update and did you do that? Does the  "had" imply you restarted in the meantime and the issue vanished?  If it did then, the conclusion would be that this was due to the alsa-lib breakage, which pacman will have told you about, take to heart to read pacman's output. It doesn't often show things you need to check, but if it does you need to make sure you've read that.

Offline

#9 2021-06-09 10:20:43

tcomarchetti
Member
Registered: 2021-04-21
Posts: 36

Re: [SOLVED]update problems:libcanberra

V1del wrote:

Very unlikely to impossible. libcanberra is for desktop/theme beeps and irrelevant for actual audio output (and the change in question here is purely cosmetic packaging simplification with no actual end user effect) and will definitely not be used for core playback features of these respective applications. The big ALSA bump to 1.2.5 is much more likely to have an effect here on specific setups, did you read pacman's warning to restart audio using applications after the alsa-lib update and did you do that? Does the  "had" imply you restarted in the meantime and the issue vanished?  If it did then, the conclusion would be that this was due to the alsa-lib breakage, which pacman will have told you about, take to heart to read pacman's output. It doesn't often show things you need to check, but if it does you need to make sure you've read that.


Yes, I did what pacman suggested about alsa-lib update and I restarted pipewire etc etc wink
I thought the problem was related to libcanberra because when I tried to reload my previous snapshoot in order to re-update the system, I tried to update everithing except libcanberra I and solved my problem.....a mystery!

Offline

#10 2021-06-09 11:58:04

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 21,790

Re: [SOLVED]update problems:libcanberra

I don't see an universe where there is a relation between that issue and libcanberra. Was your audio device occupied by something else during that? sudo fuser -v /dev/snd/* to check. But that is a bit off-topic. FWIW I don't use spotify but no issues with VLC (... and VLC doesn't even link to canberra) on an updated system *shrug*

@frank1964 If your question is answered and the issue solved, please mark it as such by editing and prepending [SOLVED] or so to the title.

Offline

#11 2021-06-09 14:19:03

frank1962
Member
Registered: 2021-05-10
Posts: 19

Re: [SOLVED]update problems:libcanberra

The update was successful

[sudo] password for @@@@:
:: Synchronizing package databases...
core is up to date
extra is up to date
community                                                                     5.6 MiB   168 KiB/s 00:34 [##############################################################] 100%
multilib                                                                    149.8 KiB   139 KiB/s 00:01 [##############################################################] 100%
:: Starting full system upgrade...
:: Replace libcanberra-pulse with extra/libcanberra? [Y/n] Y
:: Replace qca with extra/qca-qt5? [Y/n] Y
resolving dependencies...
looking for conflicting packages...

Packages (9) libcanberra-0.30+2+gc0620e4-4  libcanberra-pulse-0.30+2+gc0620e4-3 [removal]  libxcrypt-4.4.22-4  pambase-20210605-2  qca-2.3.2-2 [removal]  qca-qt5-2.3.3-1
             util-linux-2.37-3  util-linux-libs-2.37-3  vtk-8.2.0-19

Total Download Size:    38.84 MiB
Total Installed Size:  212.62 MiB
Net Upgrade Size:       -0.38 MiB

:: Proceed with installation? [Y/n] Y
:: Retrieving packages...
libxcrypt-4.4.22-4-x86_64                                                    88.5 KiB   242 KiB/s 00:00 [##############################################################] 100%
pambase-20210605-2-any                                                        3.0 KiB   152 KiB/s 00:00 [##############################################################] 100%
util-linux-libs-2.37-3-x86_64                                               411.3 KiB   168 KiB/s 00:02 [##############################################################] 100%
util-linux-2.37-3-x86_64                                                      2.5 MiB   171 KiB/s 00:15 [##############################################################] 100%
libcanberra-0.30+2+gc0620e4-4-x86_64                                         91.5 KiB   160 KiB/s 00:01 [##############################################################] 100%
qca-qt5-2.3.3-1-x86_64                                                      777.9 KiB   159 KiB/s 00:05 [##############################################################] 100%
vtk-8.2.0-19-x86_64                                                          35.0 MiB   163 KiB/s 03:40 [##############################################################] 100%
Total (7/7)                                                                  38.8 MiB   163 KiB/s 04:04 [##############################################################] 100%
(7/7) checking keys in keyring                                                                           [##############################################################] 100%
(7/7) checking package integrity                                                                         [##############################################################] 100%
(7/7) loading package files                                                                              [##############################################################] 100%
(7/7) checking for file conflicts                                                                        [##############################################################] 100%
(9/9) checking available disk space                                                                      [##############################################################] 100%
:: Processing package changes...
(1/2) removing qca                                                                                       [##############################################################] 100%
(2/2) removing libcanberra-pulse                                                                         [##############################################################] 100%
(1/7) upgrading libxcrypt                                                                                [##############################################################] 100%
> Starting with 'libxcrypt' 4.4.21, weak password hashes (such as MD5 and SHA1)
> are no longer accepted for new passwords. Users that still have their
> passwords stored with a weak hash will be asked to update their password on
> their next login.
> If the login just fails (for example from display manager) switch to a
> virtual terminal ('Ctrl-Alt-F2') and log in there once.
(2/7) upgrading pambase                                                                                  [##############################################################] 100%
(3/7) upgrading util-linux-libs                                                                          [##############################################################] 100%
(4/7) upgrading util-linux                                                                               [##############################################################] 100%
(5/7) upgrading libcanberra                                                                              [##############################################################] 100%
(6/7) installing qca-qt5                                                                                 [##############################################################] 100%
Optional dependencies for qca-qt5
    pkcs11-helper: PKCS-11 plugin [installed]
    botan: botan plugin
(7/7) upgrading vtk                                                                                      [##############################################################] 100%
:: Running post-transaction hooks...
(1/6) Creating system user accounts...
(2/6) Reloading system manager configuration...
(3/6) Reloading device manager configuration...
(4/6) Arming ConditionNeedsUpdate...
(5/6) Refreshing PackageKit...
(6/6) Checking which packages need to be rebuilt

while same programs like teams, openboard runs correctly, others like guvcview , records without audio.

Offline

#12 2021-06-09 14:46:17

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 21,790

Re: [SOLVED]update problems:libcanberra

And this has no relation to libcanberra. If you want help there I suggest you open a new thread and mark this as [SOLVED]

Offline

#13 2021-06-23 07:18:36

JailhouseJoe
Member
From: Germany
Registered: 2013-06-04
Posts: 21
Website

Re: [SOLVED]update problems:libcanberra

V1del wrote:

And this has no relation to libcanberra. If you want help there I suggest you open a new thread and mark this as [SOLVED]

I also observed issues with 'libcanberra-0.30+2+gc0620e4-4' which are cured by a downgrade to '-3'. Let's move this to this (already existing) thread.

@V1del, @Scimmia, @mpan: Would you also be so kind to have a look at that?

Offline

Board footer

Powered by FluxBB