WetGeek Flawless here as well. Updated three Plasma laptops, one Xkde laptop, and one VM for each of the five Solus editions. Not a single error so far. Two desktops to update later, but I don't anticipate any issues with those, either.
brent EbonJaeger We have two deprecations this week: evopop-gtk-theme users tearfully pleading with you to keep evopop: (crickets) /s that and mokat are probably the only two that have not graced my Budgie. I like the idea of phasing out some of the 2017-era icon packages.
RegularJogger Everything went well for my Budgie except for integrity of glibc being reported as Broken by eopkg check after this update. Tried reinstalling and rebooting but the issue persists. Maybe just one of those false positives we get from time to time? Checking integrity of glibc Broken Corrupted file: /usr/bin/ld.so Corrupted file: /usr/lib64/libthread_db.so
JTCPingas RegularJogger gnome-shell-extension-appindicator and packagekit show up as broken on my GNOME install. Everything does appear to work perfectly fine. Though now that you mentioned glibc showing broken, it shows that for me too.
penny-farthing After this update (135 packages, 1,37 GiB), the terminal command sudo eopkg check give me also the same error: What can we do to solve it ? (I precise that I am a Budgie desktop user) Otherwise, nothing else to report at this time.
mouse_AUS Lazarus wont build it has linking issues, is there a way I can roll back? Kodi wont open at all missing x11 libs I thought v21 should now be running under Wayland? edit - after installing qt6pas-dev i could build but would be good if qt5pas-dev was still available so I can build for older qt5 systems. Also there seems to be a permissions issue. I need to change the permissions on /usr/share/lazarus otherwise builds fail
Solarmass I can confirm that eopkg check reports glibc is Broken on Solus Budgie mouse_AUS Kodi wont open at all missing x11 libs I thought v21 should now be running under Wayland? Kodi doesn't start here on Solus Budgie too: /usr/lib64/kodi/kodi-x11: error while loading shared libraries: libxg.so: cannot open shared object file: No such file or directory
Mascaret same here. No reproduction steps, alas : just eopk -up then : Vérification de l'intégrité de glibc Cassé Fichier corrompu : usr/bin/ld.so Fichier corrompu : usr/lib64/libthread_db.so meaning glibc broken corrupted file : usr/bin/ld.so corrupted file : : usr/lib64/libthread_db.so This is solus with kde. Btw : solus is the 1st to incorporate kde framework 6.1. Congrats!!
ender Same here: ❯ _ eopkg check glibc Checking integrity of glibc Broken Corrupted file: /usr/bin/ld.so Corrupted file: /usr/lib64/libthread_db.so
mbevks The update made the "icons" setting on Budgie Desktop blank, giving me an initial shock when I looked at my icons. I manually went in to change it back to what it was previously set as.
synth-ruiner phew, IntelliJ IDEA is working again! I think it was this one: xorg-xwayland was updated to 23.2.6-25 (joebonrichie). I looked into it last week and considered filing a bug report, but I was lazy and had faith that it would somehow get updated anyway, and lo and behold 😂 thanks for saving me from having to use vscode!
[deleted] This sync also introduces fan2goto the repos, which is a simple daemon for fan speed control written in Go. In comparison to fancontrol it provides multi-point fan curves, should work after resume from suspend and is more hassle-free as it doesn't rely on absolute hwmon paths unlike fancontrol.
EbonJaeger Cherry-picked putty to fix CVE-2024-31497. If you have used a 521-bit ECDSA private key with any previous version of PuTTY, consider the private key compromised: remove the public key from authorized_keys files, and generate a new key pair. However, this only affects that one algorithm and key size. No other size of ECDSA key is affected, and no other key type is affected.
