https://bugs.kde.org/show_bug.cgi?id=494927
Adam Fontenot <adam.m.fontenot+...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |adam.m.fontenot+kde@gmail.c
| |om
--- Comment #25 from Adam Fontenot <adam.m.fontenot+...@gmail.com> ---
I think this is probably the same bug as
https://bugs.kde.org/show_bug.cgi?id=493145?
They're both bugs that exclusively appear on Qt 6.8. They both reflect some
kind of pointer issue. People reporting the issue in this thread have mostly
seen the "Property 'respond' of object 1,0,0,0,0,1,0,0,0,0,1,0,0,0,0,1 is not a
function" type of error, which results in a freeze in the authentication
process and the password field gets stuck.
This doesn't sound like a programming bug in kscreenlocker to me, it looks like
in the line
authenticator.respond(password)
The Qt internal pointer to the authenticator object has gotten corrupted,
resulting in the nonsensical debugging statement seen here.
People over on the other bug are mostly seeing segfaults, which looks a little
different in the logs and sometimes seems to result in kscreenlocker being
restarted and it becoming possible to log in, but I think it's probably the
same issue?
--
You are receiving this mail because:
You are watching all bug changes.
