hm, openshot does not use x264 or x265… so it has no hardware acceleration
I have now also thought about whether this is a good idea to remove the hardware acceleration from Mesa. Since many content creators require this, I think you should provide a way to enable this feature whether it is via x264 or x265.
I’m running Manjaro Plasma on an Intel / NVIDIA system.
After the updates and rebooting I noticed Flameshot wasn’t running in the background as it should. Clicking the shortcut in the application launcher did absolutely nothing, but running the Exec command from its .desktop file in a terminal gave the following error:
/usr/bin/flatpak run --branch=stable --arch=x86_64 --command=/app/bin/flameshot org.flameshot.Flameshot
This was fixed by manually running flatpak upgrade and waiting for it to remove, update, and install various packages - some of which I’m sure I saw included in the system updates, but I may be mistaken on this.
Updated & tested various of my RDP connections
It is as I expected.
Some RDP connections still work.
But those to my company (RDS Gateway, for which I had to install H264 package) doesn’t work any longer.
Since I have no access to their error logs & configs I’m stuck.
Edit/update: after reinstalling openh264 I succeded to connect again
After last update the interface start working with visible reduced performance (low fps, jerky windows drawings).
I use XFCE with picom compositor on an old AMD FX-8350 with integrated AMD ATI Radeon 3000., kernel: 6.0.11-1-MANJARO, and video-linux drivers
It does not work even after installing openssl-1.1 and lib32-openssl-1.1. It fails with an error SSL Provider [error:0A0C0103:SSL routines::internal error]
I don’t think this is really a Manjaro issue, more of a problem with Microsoft’s driver. Microsoft suggests to symlink the OpenSSL binary to the 1.1 version, which suggest that their driver is still “looking for that”. Just wanted to let the community know.
Latest update broke some chrome based applications that I use for work (StorageExplorer and AzureDataStudio).
To make them work, I had to disable GPU Acceleration using --disable-gpu from the cli.
I assume it has something to do with the new Nvidia driver and CEF versions that those apps use. Chrome based browsers work without problem.
Error log example:
(main:813200) <ERRO> UNHANDLED PROMISE REJECTION in main process:
Error: GPU access not allowed. Reason: GPU process crashed too many times with SwiftShader.
(node:807364) UnhandledPromiseRejectionWarning: Error: GPU access not allowed. Reason: GPU process crashed too many times with SwiftShader.
at App.gpuProcessCrashHandler (/opt/StorageExplorer/resources/app/out/app/index.js:173:38)
at App.emit (node:events:527:28)
at App.<anonymous> (node:electron/js2c/browser_init:229:1206)
at App.emit (node:events:527:28)
(Use `StorageExplorerExe --trace-warnings ...` to show where the warning was created)
(node:807364) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 9)
You can build your own mesa package, it takes less than 5 min when using a good CPU, done.
If you switched to Arch, but you would build and compile many other AUR source packages (e.g: zfs-utils), their build-processes take longer. But they are already in Manjaro repos, no need to build them.