A post was split to a new topic: Libcrypto.so.3 after stable update
Most of my OpenVPN connections stopped working in NetworkManager. There is no any information about the reasons in the log:
nmcli c up "Germany, Frankfurt S3"
Error: Connection activation failed: Unknown reason
Hint: For more information, use «journalctl -xe NM_CONNECTION=d290757d-a374-49a4-9c4e-48060f111cab + NM_DEVICE=wlp2s0»
And after the hint using:
bigpc NetworkManager[2737]: <warn> [1668938718.2041] vpn[0x5566810ec960,d290757d-a374-49a4-9c4e-48060f111cab,"Germany, Frankfurt S3"]: dbus: failure: connect-failed (1)
openssl-1.1 is installed. Do anybody know how to fix it?
Check the journal, there will be an error message.
journalctl -u NetworkManager -t nm-openvpn
You might want to add -b and --no-pager
Since it is probably because you use ancient, insecure chipers, update your config. You can find multiple topics in the forum about this.
–
Also do not downgrade, it will just delay the time until you will need to update your config anyway. And maybe leaves you with the next update without a networking at all.
Ok, thank you, it’s more comprehensible:
OpenSSL: error:0A00018E:SSL routines::ca md too weak
nm-openvpn[35695]: Cannot load certificate file
And then you copy paste that error into google and go to first superuser-com result.
A recent openssl update is enforcing higher cert signings. Check with your vpn provider to reissue any depreciated certs associated with your profile and then regenerate openvpn configs.
Do NOT follow any silly advice by disabling all security by adding something like “DEFAULT:@SECLEVEL=0” to your configs. 
I have a problem with wake up from suspend. Normally My Laptop Dell Inspiron 15 5505 ADM Ryzen 7 4700u has no S3 but I able to fix it by DSDT modification. Now after the update 3 times after suspend no display and I got this error message.
What went wrong I can’t figure it out.
Nov 20 10:36:48 PM kernel: [drm:process_one_work] *ERROR* ib ring test failed (-22).
Nov 20 10:36:48 PM kernel: amdgpu 0000:03:00.0: [drm:amdgpu_ib_ring_tests [amdgpu]] *ERROR* IB test failed on gfx (-22).
Nov 20 10:36:48 PM kernel: Non-boot CPUs are not disabled
Nov 20 10:36:20 PM nmbd: register_name: Failed to send packet trying to register name WORKGROUP<1d>
Nov 20 8:49:54 PM kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, but soft recovered
Nov 20 8:49:44 PM kernel: amdgpu 0000:03:00.0: amdgpu: RW: 0x0
Nov 20 8:49:35 PM nmbd: Packet send failed to 192.168.100.255(138) ERRNO=Network is unreachable
Nov 20 6:44:56 PM systemd-coredum: Process 1624 (goa-daemon) of user 1000 dumped core.
Had to refresh keys before being able to proceed with update.
I am also with night light broken after update (on intel though), did you managed to fix it?
Unable to switch to my Creative usb headset after the latest update. It is still detected by the kernel, but it does not show up as a device in volume control any more.
After the update and a reboot, Chrome started rendering “big”–the wrong display scaling was being used. I had spent many hours trying to get scaling to work properly in Manjaro when using Wayland. The SDDM logon screen scaling is a persistent issue. But I was surprised to see Chrome rendering all of a sudden “broken”. Knowing I had a similar issue with Firefox previously, I checked out Firefox. It too, was all of a sudden “broken”–rendering things way too large.
In the case of Firefox, previously, I set a configuration flag in the about:config page. I set layout.css.dpi to 256 (my monitor’s physical DPI) and layout.css.devPixelsPerPx to 2.
I had also tried setting various things in various configuration files. One thing I set was in /etc/environment: GDK_SCALE=2.66.
Ok, so back in Firefox, I reset layout.css.devPixelsPerPx to 1. And boom! Firefox was “fixed”. Ok, this is definitely a scaling issue that’s been “fixed” in one of the updates. Unfortunately, there’s no such flag like that in Chrome.
So, I backed out the GDK_SCALE variable I set in /etc/environment and rebooted. But, upon restart, typing the command echo $GDK_SCALE, I received back 2.00. Where was this being set??? Apparently, this was put in a configuration file in my local home directory–though, I did not set this, and this is why scaling probably never worked the way I thought it should–“my settings” were being overridden by the entry in a local configuration file in my Home directory which I never set! The file is ~/.config/plasma-workspaces/env/10-hidpi.sh, which had export GDK_SCALE='2.00' inside it. So I set that line to export GDK_SCALE='1.00', reboot, and now Chrome was fixed too.
1 Like
libcrypto.so.1.1 breaks grub generation with update-grub failing too…Installing the recommended package fixes it too…
Firefox with graphic card (hardware) acceleration fails to process clicks on some websites. If you run it from the command line you get a message 
:
GFX1-]: glxtest: VA-API test failed: process crashed. Please check your VA-API drivers.
Anyone knows how to solve this without disabling hardware acceleration?
1 Like
I have a reoccurring but kind of not properly reproducible issue:
When I use the three finger swipe gesture to switch Desktops on Gnome, sometimes the whole system freezes for a few seconds.
Though it’s not always the reproducible e.g. if I just rebooted my system it mostly works fine.
E.g. I have Xournal++ on desktop 1 and Firefox on desktop 2, after a clean restart the gesture works flawless, but most of the time when I already worked for a few hours or so(possibly switched to standby a couple times) my entire system freezes for at least 5 seconds or so, this is especially annoying when I accidentally trigger the gesture while navigating with my fingers.
The issue persists if I close Xournal++ or/and FF so I dont think it’s entirely their fault/if at all.
My system:
Model: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop TP420UA_TM420UA
CPU: AMD Ryzen™ 5 5500
GPU: AMD Radeon™ Graphics
RAM: 8,0 GiB
Note: This issue was deffenitly not present before though the Xournal++ Version updated two days prior.
Answering my own question, downgrading xlib seems to be a solution. Haven’t tested it long enough to corroborate but seems legit.
Downgrading to libx11 1.8.1-3 solves this issue
After the update, a monitor that was working before doesn’t get signal. I see it on system settings > display. But when making it active, it blinks looking for signal and gets nothing.
Nvidia Gforce 1060, manjaro KDE (with openboxwm). This is a major issue. The monitor works with another computer fine (so we can discard hardware error). Has anything major changed in how external monitors are being treated?
edited to link to corresponding thread
How you did this?
Firefox here is crashing a lot of times, I want to downgrade the libx11
yay -S downgrade
downgrade libx11
1 Like