[Stable Update] 2021-08-09 - Kernels, Xorg-Server, Systemd, Virtualbox, Mesa, Plasma, Pipewire

I caught a problem with sound in telegram (2.9.0-4) during calls. When companion says creacks are heard like the microphone is overloaded. It is like that with many contacts and isn’t a hardware problem. At the same time voice messages sound good.

Thats a known problem of telegram 2.9 and hopefully will be fixed for the new release


Have libimagic6 update for several days but can’t update to 6.9.19-2 it.

Warning: skypeforlinux-stable-bin: ignoring package upgrade ( =>
Checking libmagick6 dependencies...
Synchronizing package databases...
Warning: deepin-desktop-base: local (3:2019.07.10-1) is newer than community (2:2021.06.16-1)
Warning: deepin-wallpapers: local (2:1.7.7-1) is newer than community (1:1.7.7-2)
Warning: electron9: local (9.4.4-2) is newer than community (9.4.4-1)
Warning: manjaro-hello: local (0.6.7-2) is newer than extra (0.6.6-6)
Warning: libmagick6- is up to date -- reinstalling
Resolving dependencies...
Checking inter-conflicts...

Building imagemagick6...
==> ERROR: PKGBUILD does not exist.

❯ pamac upgrade
Synchronizing package databases...
Warning: manjaro-hello: local (0.6.7-2) is newer than extra (0.6.6-6)
Warning: perl: ignoring package upgrade (5.32.0-1 => 5.34.0-2)
Resolving dependencies...
Checking inter-conflicts...
Warning: removing 'pulseaudio' from target list because it conflicts with 'pipewire-pulse'
Error: Failed to prepare transaction:
could not satisfy dependencies:
- unable to satisfy dependency 'pulseaudio=15.0-1' required by pulseaudio-equalizer

On doing pamac update or pamac upgrade I get this pulseaudio error. Any idea how to resolve this?

Remove pulseaudio-equalizer package.


Don’t know. Was removed here: [pkg-upd] 5.13.6-1 (cbc57124) · Commits · Packages / Core / linux513 · GitLab Have to check if that got backported: usb: xhci: avoid renesas_usb_fw.mem when it's unusable · torvalds/linux@0665e38 · GitHub


The commit message should have contained the reasoning for the removal, but it’s lacking.

1 Like

Most likely it was removed due to updated files. I checked the 514er version, which got wrongly modified. I’ve updated the patch and will be re-added with the upcoming kernel updates.

1 Like

Only issue I had with this update was with Visual Studio Code (VSCode) from Snap.
Had to install the Flatpak version, which I don’t like to do…

This is because the Snap version was published using classic confinement.

The error message when installing is:

cannot install “code”: classic confinement requires snaps under /snap or symlink from /snap to /var/lib/snapd/snap


Do not like versions in our repo and AUR?

$ pacman -Si code
Repository      : community
Name            : code
Version         : 1.58.0-1
Description     : The Open Source build of Visual Studio Code (vscode) editor

Binary releases of VS Code without MS branding/telemetry/licensing: http://aur.archlinux.org/packages/vscodium-bin

1 Like

I removed the packages and other similar pulseaudio packages which were giving me trouble.
I removed pulseaudio-equaliser; pulseaudio-jack; pulseaudio-lirc; pulseaudio-rtp and pulseaudio-zeroconf only then was I able to update.
Now on doing so, my GNOME doesn’t have audio anymore. On battery connection, increasing volume and other GNOME sounds aren’t there.
How do I solve this? The above packages were required for GNOME for the audio.
(Audio from Spotify, Chrome etc works fine, only GNOME audio is gone)
I installed pipewire-pulse recently, could this have something to do with it?

Yes it does - it conflicted with your pulseaudio-* packages. Just look at the initial error message you posted.
I assumed your system used pipewire for audio and that pulseaudio-equalizer package was a leftover/oversight of a switch from pulseaudio to pipewire.
Try (completly) installing pipewire support:

$ sudo pacman -Syu manjaro-pipewire

If this doesn’t bring your audio back, please open a new thread for the problem.

1 Like

There was a mini update today, “manjaro-kde-settings” , version 20210812-1.
The color function got disabled after the update.


A post was split to a new topic: Gnome Development ISO installation problems

Moreover, Yakuake does not autostart for me after this update, and when it’s launched manually, its icon looks differently. All of these problems are fixed after downgrading to manjaro-kde-settings-20210806-1.

I know, that’s what I ended up doing. :wink:

I ended up switching to a different color theme, then switching back to my original color theme (Breath2 Dark) and this resolved the problem for me. I didn’t need to downgrade any packages.

After doing this, then logging out, then logging back in, my colors are back to how they originally were. :slight_smile:

It appears the update triggered a new naming schema for color themes, perhaps?

Looks like something changed under

  • $HOME/.kde4/share/apps/color-schemes/
  • $HOME/.kde4/share/config/
1 Like

I had some problems with the stability of digiKam + database compatibility when coning from digikam 7.2 and it looks that my database even was still in version 12 (I do use the integrated MySQL option (mariadb)).

That’s what happened:
When starting digiKam 7.3 the error came up that my DB is still on version 12 and it failed to be updated to version 13.
This is a known error which is fixed in digiKam 7.4! ([digikam] [Bug 440212] New: Digikam 7.3.0 fails to update the database schema from version 12 to version 13). Workaround by manually editing version information in DB and then executing a migration to SQLite und back to MySQL was not working because digiKam was crashing a few seconds when is started to working with the DB.

So I executed a downgrade back to digiKam 7.2.0-5… Starting digiKam was possible again, but when the database was utilized the whole programmed crashed again.

in user log I found something like this (partial copy& paste)

Aug 13 17:07:24 uranus systemd-coredump[35854]: [🡕] Process 35709 (digikam) of user 1000 dumped core.
                                                Stack trace of thread 35709:
                                                #0  0x00007f1920066953 n/a (libmariadb.so.3 + 0x1f953)
                                                #1  0x00007f192007479c n/a (libmariadb.so.3 + 0x2d79c)
                                                #2  0x00007f192006eca7 n/a (libmariadb.so.3 + 0x27ca7)
                                                #3  0x00007f1920070887 mysql_stmt_fetch (libmariadb.so.3 + 0x29887)
                                                #4  0x00007f19201882ed n/a (libqsqlmysql.so + 0x72ed)
                                                #5  0x00007f1948edfa79 _ZN7Digikam15BdEngineBackend10readToListERNS_16DbEngineSqlQueryE (libdigikamcore.so.7.2.0 + 0x928a79)
                                                #6  0x00007f1948edfba2 _ZN7Digikam15BdEngineBackend17handleQueryResultERNS_16DbEngineSqlQueryEP5QListI8QVariantEPS4_ (libdigikamcore.so.7.2.0 + 0x928ba2)
                                                #7  0x00007f1948ee132b _ZN7Digikam15BdEngineBackend7execSqlERK7QStringRK8QVariantP5QListIS4_EPS4_ (libdigikamcore.so.7.2.0 + 0x92a32b)
                                                #8  0x00007f194936f965 _ZNK7Digikam6CoreDB15getItemPositionEx6QFlagsINS_14DatabaseFields18ItemPositionsFieldEE (libdigikamdatabase.so.7.2.0 + 0xa0965)
                                                #9  0x00007f19493e5d32 n/a (libdigikamdatabase.so.7.2.0 + 0x116d32)
                                                #10 0x00007f19493e645c _ZN7Digikam12ItemPositionC2Ex (libdigikamdatabase.so.7.2.0 + 0x11745c)
                                                #11 0x00007f19493ceb8c _ZNK7Digikam8ItemInfo13imagePositionEv (libdigikamdatabase.so.7.2.0 + 0xffb8c)
                                                #12 0x00007f19493ceea2 _ZNK7Digikam8ItemInfo14hasCoordinatesEv (libdigikamdatabase.so.7.2.0 + 0xffea2)
                                                #13 0x00007f1949b425ab n/a (libdigikamgui.so.7.2.0 + 0x5c05ab)
                                                #14 0x00007f19474064ff _ZN7QObject5eventEP6QEvent (libQt5Core.so.5 + 0x2e64ff)
                                                #15 0x00007f1947eadd62 _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5 + 0x15ad62)
                                                #16 0x00007f19473d93aa _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5 + 0x2b93aa)
                                                #17 0x00007f19473dc4a9 _ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData (libQt5Core.so.5 + 0x2bc4a9)
                                                #18 0x00007f19474329a4 n/a (libQt5Core.so.5 + 0x3129a4)
                                                #19 0x00007f193632310c g_main_context_dispatch (libglib-2.0.so.0 + 0x5410c)
                                                #20 0x00007f1936376b99 n/a (libglib-2.0.so.0 + 0xa7b99)
                                                #21 0x00007f1936320871 g_main_context_iteration (libglib-2.0.so.0 + 0x51871)
                                                #22 0x00007f1947431fd6 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x311fd6)
                                                #23 0x00007f19473d7d1c _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2b7d1c)
                                                #24 0x00007f194983523a _ZN7Digikam14ScanController26completeCollectionScanCoreEbb (libdigikamgui.so.7.2.0 + 0x2b323a)
                                                #25 0x00007f19499c5659 _ZN7Digikam14NewItemsFinder9slotStartEv (libdigikamgui.so.7.2.0 + 0x443659)

cause and solution:
there is an incompatibility with the mariadb version 10.6. A downgrade to mariadb 10.5.11-1 resolved all the trouble. Now digiKam 7.2 works stable again.

I am now converting thew database to SQlite and then upgrade all packages back to current Manjaro stable branch release and wait for digiKam 7.4 for switching back to MySQL as DB system for digiKam.

So two issues:
I came from digiKam version 7.2 a

Since this latest update, libmagick6 keeps wanting to be reinstalled for some reason. I can go through the process below any number of times, but despite reinstalling a number of times it keeps coming up as something that needs to be installed yet again…even though pamac knows that it’s already up to date. This is true on two different systems – a desktop and a laptop.

What should I do to get out of this loop?

sudo pamac upgrade
[sudo] password for jwalsh: 
Warning: Building packages as root
Warning: Setting build directory to /var/cache/pamac
Checking libmagick6 dependencies...
Synchronizing package databases...
Warning: manjaro-hello: local (0.6.7-2) is newer than extra (0.6.6-6)
Warning: libmagick6- is up to date -- reinstalling
Resolving dependencies...
Checking inter-conflicts...

To build (1):
  libmagick6                 AUR

Edit build files : [e] 
Apply transaction ? [e/y/N]