# Kscreenlocker\_greet missing osd directory

**URL:** <https://discuss.kde.org/t/kscreenlocker-greet-missing-osd-directory/36293>\
**Category:** Help\
**Tags:** plasma\
**Created:** [June 29, 2025, 7:29am UTC](https://discuss.kde.org/t/kscreenlocker-greet-missing-osd-directory/36293 "2025-06-29T07:29:44Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![pg-tips](https://discuss-cdn.kde.org/letter_avatar_proxy/v4/letter/p/9d8465/32.png) [@pg-tips](https://discuss.kde.org/u/pg-tips)\
**Post date:** [June 29, 2025, 12:37pm UTC](https://discuss.kde.org/t/kscreenlocker-greet-missing-osd-directory/36293/3 "2025-06-29T12:37:37Z")

</div>

I suspect this is the issue discussed here: [All KDE apps crash upon opening / interacting - #2 by pg-tips](https://discuss.kde.org/t/all-kde-apps-crash-upon-opening-interacting/36294/2)

It’s a problem with the latest version of `qt6-qtwayland` deployed in Fedora.

If you updated today, then you most likely have version 6.9.1-2 of that package installed, so you could try downgrading to 6.9.1-1 as per [2375356 – qt6-qtwayland 6.9.1-2 breaks KDE Plasma lockscreen, requiring user to drop to TTY to unlock session](https://bugzilla.redhat.com/show_bug.cgi?id=2375356#c4)

The “…/osd” error message is unrelated I think. I also see this message on a system which has never had the bad version of `qt6-qtwayland` installed, and never had the broken lockscreen.

The timing of the updates has meant that many users got their `qt6-qtwayland` upgraded at the same time as the Plasma 6.4.1 upgrade. So this issue is often being attributed to Plasma 6.4.1, when the cause is actually this Fedora-specific qtwayland package.

---

_[View the full topic](https://discuss.kde.org/t/kscreenlocker-greet-missing-osd-directory/36293)._