https://bugs.kde.org/show_bug.cgi?id=456210
stellarpo...@googlemail.com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |stellarpo...@googlemail.com
--- Comment #72 from stellarpo...@googlemail.com ---
I am also on Ubuntu 22.04 and Plasma 5.25.5 (wayland).
I have not had any lock-screen issues so far (I'm not using it at all) but when
I see Plasma crashes I have lines in the log in common with what is mentioned
here.
https://bugs.kde.org/show_bug.cgi?id=458469
I am seeing behaviour similar to in this bug and have added comments there; and
someone else who was able to get 5.26 also saw that fix it.
Am commenting in case there might be something in common between these issues,
and something that has been resolved as of 5.26, but not in the 5.25 branch
(which is the latest available for all Ubuntu LTS users, so a reasonably large
number may encounter further problems)
I see these lines in common (and searching for them has brought me here):
- Creating a fake screen in order for Qt not to crash
- requesting unexisting screen -1
- qt.qpa.wayland: Wayland does not support QWindow::requestActivate()
- QMetaProperty::read: Unable to handle unregistered datatype
'KWin::SessionState' for property 'KWin::EffectsHandlerImpl::sessionState'
- QML Connections: Detected function "onConfigurationChanged" in Connections
element. This is probably intended to be a signal handler but no signal of the
target matches the name.
This is unrelated to the screenlocking, and often occurs when I power my
display back on after being away form the PC for some time (fully on, not
suspended); but I also experience this at times when there is a change in my
desktop - e.g. opening a new application.
- Cannot read property 'wallpaper' of null
--
You are receiving this mail because:
You are watching all bug changes.
