Comments

14 Comments

To add some potentially important information for debugging: the issue appears to be independent from the graphics server, as it happens both with Wayland and X11. I have the following apps in my autostart section:

  • yakuake
  • telegram-desktop

I don't think it did. There is a slightly different behaviour, though for the app launch issue. Using systemdBoot=false, KDE apps can be launched as soon as the session starts, without delay. However, the session loading takes much longer (the additional loading time of the splash screen seems to correspond to the app launch delay with systemdBoot=true).

The icons from autostart apps are still missing in the tray with systemdBoot=false.

Note that this update brings a tiny regression that in the first 5-10 seconds after boot, QT-based apps cannot be launched / there is a considerable delay, and system tray icons of autostart apps don't appear until killed+relaunched manually. However, this is likely an upstream issue, since it happens on my Ubuntu system too after the update to the latest Gear.

karma

This is a very important update, possibly for many users having updated to kernel 6.2.

With the previous kernel version (v6.2.7), I couldn't use my machine, because my mouse and keyboard were not working. This version fixes it, and everything runs smoothly as with 6.1.18.

If you are reading this and affected by USB issues, this update may fix it for you :)

I don't know if it matters, but the following KWin rules are in effect for the applications:

No border and titleframe: Apply initially Opacity: 0.67 Force

Here is the link: https://imgur.com/a/VjGDqcx

As it turns out, the issue is not specific to yakuake, but affects all KDE-based terminal emulators, including konsole and the one integrated into dolphin. It happens in both X11 and Wayland.

Depending on the terminal output, it disappears for a short while, but reappears once the output changes again, or a new session is started.

This is hardly worth mentioning (it is a literally minuscule, non-breaking issue), but since this update, the most top left corner of yakuake is white, despite using a dark theme. Aside from this, everything works as expected. I also didn't encounter issues with copying files in dolphin, but maybe I misunderstood the way of triggering the bug :)

karma

Everything working on my end. (except the exploit, hopefully) Will run a PoC tomorrow if I find one.

@ozeszty it's caused by the kf5 update from some weeks ago, and the issue has been fixed by the KDE devs, so it will be gone with the next KDE Frameworks update :) (also getting this issue, and I haven't installed this testing update. Here is the fix commit: https://invent.kde.org/frameworks/plasma-framework/-/merge_requests/509)

karma

Yes, with the new iaito, the update installs successfully. Thank you!

With this update, the new radare2 version installs correctly. No regressions spotted after a (very quick) DLL analysis.

BZ#2024387 iaito-5.5.0-beta is available
BZ#2055092 F34FailsToInstall: iaito
karma

Cannot be installed when using the GUI frontend iaito:

┌─[vainlystrain@vainlystrain]─[~] └──╼ $sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-6aba96e1b8 Fedora 34 - x86_64 - Test Updates 8.0 kB/s | 18 kB 00:02
Fedora 34 - x86_64 - Test Updates 1.3 MB/s | 10 MB 00:07
Last metadata expiration check: 0:00:09 ago on Sun 06 Mar 2022 03:39:17 CET. Dependencies resolved.

Problem: problem with installed package iaito-5.3.1-4.fc34.x86_64 - package iaito-5.3.1-4.fc34.x86_64 requires libr_anal.so.5.4.2()(64bit), but none of the providers can be installed - package iaito-5.3.1-4.fc34.x86_64 requires libr_asm.so.5.4.2()(64bit), but none of the providers can be installed - package iaito-5.3.1-4.fc34.x86_64 requires libr_bin.so.5.4.2()(64bit), but none of the providers can be installed - package iaito-5.3.1-4.fc34.x86_64 requires libr_bp.so.5.4.2()(64bit), but none of the providers can be installed - package iaito-5.3.1-4.fc34.x86_64 requires libr_config.so.5.4.2()(64bit), but none of the providers can be installed - package iaito-5.3.1-4.fc34.x86_64 requires libr_cons.so.5.4.2()(64bit), but none of the providers can be installed - package iaito-5.3.1-4.fc34.x86_64 requires libr_core.so.5.4.2()(64bit), but none of the providers can be installed - package iaito-5.3.1-4.fc34.x86_64 requires libr_crypto.so.5.4.2()(64bit), but none of the providers can be installed - package iaito-5.3.1-4.fc34.x86_64 requires libr_debug.so.5.4.2()(64bit), but none of the providers can be installed - package iaito-5.3.1-4.fc34.x86_64 requires libr_egg.so.5.4.2()(64bit), but none of the providers can be installed - package iaito-5.3.1-4.fc34.x86_64 requires libr_flag.so.5.4.2()(64bit), but none of the providers can be installed - package iaito-5.3.1-4.fc34.x86_64 requires libr_fs.so.5.4.2()(64bit), but none of the providers can be installed - package iaito-5.3.1-4.fc34.x86_64 requires libr_hash.so.5.4.2()(64bit), but none of the providers can be installed - package iaito-5.3.1-4.fc34.x86_64 requires libr_io.so.5.4.2()(64bit), but none of the providers can be installed - package iaito-5.3.1-4.fc34.x86_64 requires libr_parse.so.5.4.2()(64bit), but none of the providers can be installed - package iaito-5.3.1-4.fc34.x86_64 requires libr_reg.so.5.4.2()(64bit), but none of the providers can be installed - package iaito-5.3.1-4.fc34.x86_64 requires libr_search.so.5.4.2()(64bit), but none of the providers can be installed - package iaito-5.3.1-4.fc34.x86_64 requires libr_syscall.so.5.4.2()(64bit), but none of the providers can be installed - package iaito-5.3.1-4.fc34.x86_64 requires libr_util.so.5.4.2()(64bit), but none of the providers can be installed - cannot install both radare2-5.6.4-1.fc34.x86_64 and radare2-5.4.2-1.fc34.x86_64 - cannot install the best update candidate for package radare2-5.4.2-1.fc34.x86_64

This also affects the last pushed update, I was a bit late reporting it, sorry.

Tested dolphin, kate, konsole and yakuake. No regressions noted on X. (both regular and touchscreen usage) The bug that caused yakuake to crash on tab close is fixed.

I'm sorry if this comment is inappropriate (as I don't know if this is the right place to ask), but would it be possible to build this update for Fedora 34? The Yakuake tab-close crash also affects its version of the terminal emulator. Thanks!