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.
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 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.
It appears the update triggered a new naming schema for color themes, perhaps?
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)
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.
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
Preparing...
Checking libmagick6 dependencies...
Synchronizing package databases...
Warning: manjaro-hello: local (0.6.7-2) is newer than extra (0.6.6-6)
Warning: libmagick6-6.9.12.15-1 is up to date -- reinstalling
Resolving dependencies...
Checking inter-conflicts...
To build (1):
libmagick6 6.9.12.15-1 AUR
Edit build files : [e]
Apply transaction ? [e/y/N]
It was a part of update to fix wrong plasma colors for new users. I’ve changed /etc/xdg/kdeglobals and added colors there hoping Plasma will just override settings from home folder (it was a case for me) for existing users but it looks like some colors don’t work this way. So I reverted this change and added kdeglobals to create per-user on a new user creation.
Hello.
I have no idea why, but I think grub was broked (maybe it’s only my problem).
Have this update log with yay and it hangs ~20 minutes: Warning: os-prober will be executed to detect other bootable partitions. Its output will be used to detect bootable binaries on them and create new boot entries.
Canceled w/ Ctrl+C the step, and the update finished w/o any problems.
After this, I tried to run manually update-grub and got same issue it’s hanged os-prob (also try to run this manually for checking output, but got a frozen process).
So I have not rebooted the system yet, but I feel that everything will break, and the grab will not be able to start.
Maybe can someone tell me what I can do before the reboot, so that everything I need is guaranteed to be “registered” in the grub?
My only problem with the OSS version are the extensions.
Some don’t exist for it and lately I’ve been having an error “We cannot connect to the Extensions Marketplace at this time, please try again later”.
pamac update in tty3 switched to the logged in graphical user interface after downloading and installing and a few scripts. Switching to tty3 was no longer possible using the keyboard. After a restart, the boot entry no longer worked.
Error: “File /boot/vmlinuz-5.10-x86_64 not found.”