Maybe GNOME sent a spy to infiltrate Manjaro and give users a nudge into switching DEs…
We’ve got ourselves a Hollywood thriller movie script on our hands.
Maybe GNOME sent a spy to infiltrate Manjaro and give users a nudge into switching DEs…
We’ve got ourselves a Hollywood thriller movie script on our hands.
A good plus for this update: I am seeing ~25% reduction in CPU/GPU usage for hardware video decoding (VAAPI).
hi, War Thunder now crashes of couple of seconds after start-up : screen freezes up and is then filled with weird colored pixels. When game finally crash, we get back to desktop and all works normally.
System: Host: antares Kernel: 5.10.56-1-MANJARO x86_64 bits: 64 Desktop: KDE Plasma 5.22.4 Distro: Manjaro Linux
Machine: Type: Desktop System: ASUS product: N/A v: N/A serial: <superuser required>
Mobo: ASUSTeK model: TUF GAMING Z490-PLUS v: Rev 1.xx serial: <superuser required> UEFI: American Megatrends
v: 1208 date: 07/21/2020
CPU: Info: 8-Core model: Intel Core i7-10700F bits: 64 type: MT MCP cache: L2: 16 MiB
Speed: 800 MHz min/max: 800/4800 MHz Core speeds (MHz): 1: 800 2: 800 3: 801 4: 800 5: 800 6: 800 7: 800 8: 800
9: 800 10: 800 11: 800 12: 800 13: 800 14: 800 15: 800 16: 800
Graphics: Device-1: Advanced Micro Devices [AMD/ATI] Navi 14 [Radeon RX 5500/5500M / Pro 5500M] driver: amdgpu v: kernel
Display: x11 server: X.Org 1.20.13 driver: loaded: amdgpu,ati unloaded: modesetting,radeon
resolution: 3840x2160~60Hz
OpenGL: renderer: Radeon RX 5500 XT (NAVI14 DRM 3.40.0 5.10.56-1-MANJARO LLVM 12.0.1) v: 4.6 Mesa 21.1.6
Audio: Device-1: Intel Comet Lake PCH cAVS driver: snd_hda_intel
Device-2: Advanced Micro Devices [AMD/ATI] Navi 10 HDMI Audio driver: snd_hda_intel
Sound Server-1: ALSA v: k5.10.56-1-MANJARO running: yes
Sound Server-2: PulseAudio v: 15.0 running: yes
Sound Server-3: PipeWire v: 0.3.33 running: yes
Info: Processes: 362 Uptime: 6h 34m Memory: 31.25 GiB used: 3.09 GiB (9.9%) Shell: Bash inxi: 3.3.06
Not really an issue, but a behaviour change that I don’t like: The system volume is now controlled by my Bluetooth headphones. I have my own volume setup (custom keys run custom scripts), completely separate from anything the system does, so I didn’t want that. If anyone else wants to restore the old behaviour, here’s the “solution”:
Edit /etc/pulse/default.pa
and append “ avrcp_absolute_volume=false
” to the line that says “load-module module-bluetooth-discover
” (66 in my case), then restart PulseAudio with for example a reboot or “systemctl --user restart pulseaudio.service
” and also close and reopen all programs that play audio.
bluetoothd[814]: src/service.c:btd_service_connect() a2dp-sink profile connect failed for 84:17:15:11:3E:27: Protocol not available
Help
Solution : deinstall pulseaudio-modules-bt
install: pulseaudio-bluetooth 15.0-1
Unfortunately, GNOME is what is holding back the next ISO release.
I’ll stick with KDE, LXQt, and Openbox versions of Manjaro
Another minor issue I’ve noticed is that the system icons like time, networks, volume have become dimmer than before the update (faded out). Hope it gets fixed in the next update!
System:
Kernel: 5.10.56-1-MANJARO x86_64 bits: 64 compiler: gcc v: 11.1.0
Desktop: KDE Plasma 5.22.4 Distro: Manjaro Linux base: Arch Linux
It’s under New Issues.
Symptoms:
Solution:
Thank you so much man, thank you so very much… My speaker for some reason whenever connected with absolute volume maxes out at 25 while it goes max upto 40 so I have to disable it on Android and now on Linux too I guess
Seems that the Pulseaudio 15 killed my Bluetooth Headset : with the new HFP / HSP dissociation, the HSP one wasn’t available, and no audio was played this way. This trick solved the problem : in /etc/pulse/default.pa, add “enable_native_hfp_hf=false” after “load-module module-bluetooth-discover”, then you’re good with pulseaudio -k
. Now only A2DP and HSP are available. See there for source, seems that there’s maybe a Kernel fix in the oven : bluetooth issue after upgrading to pulseaudio-15.0 (#1247) · Issues · PulseAudio / pulseaudio · GitLab
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 6.9.12.17-1 to 6.9.19-2 it.
Preparing...
Warning: skypeforlinux-stable-bin: ignoring package upgrade (8.74.0.152-1 => 8.75.0.140-1)
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-6.9.12.17-1 is up to date -- reinstalling
Resolving dependencies...
Checking inter-conflicts...
Building imagemagick6...
==> ERROR: PKGBUILD does not exist.
❯ pamac upgrade
Preparing...
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.
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.
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