https://bugs.kde.org/show_bug.cgi?id=493145
Nate Graham changed:
What|Removed |Added
Status|CONFIRMED |RESOLVED
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=493145
--- Comment #45 from Iyán Méndez Veiga ---
(In reply to Nate Graham from comment #44)
> This one does appear to match the symptoms of Bug 494927, so marking as a
> duplicate of that.
>
> *** This bug has been marked as a duplicate of bug 494927 ***
Agr
https://bugs.kde.org/show_bug.cgi?id=493145
Nate Graham changed:
What|Removed |Added
See Also|https://bugs.kde.org/show_b |
|ug.cgi?id=494927|
https://bugs.kde.org/show_bug.cgi?id=493145
--- Comment #43 from Synthetic451 ---
The issue is still occuring for me even with the latest updates today. The
problem doesn't occur every time. There are moments where it works okay. For
example, it worked for 3 times today until it failed again on t
https://bugs.kde.org/show_bug.cgi?id=493145
Gurenko Alex changed:
What|Removed |Added
CC||agure...@protonmail.com
--
You are receiving th
https://bugs.kde.org/show_bug.cgi?id=493145
--- Comment #42 from steve ---
(In reply to steve from comment #40)
> I rolled back to kscreenlocker-6.1.4-1, my previous version, as a temporary
> work around.
Which seemed to work for a while but then it didn't:
10/25/24 7:39 AMkscreenlocker_
https://bugs.kde.org/show_bug.cgi?id=493145
--- Comment #41 from kde.tinker...@passinbox.com ---
Still also experiencing this after updating everything
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=493145
--- Comment #40 from steve ---
I rolled back to kscreenlocker-6.1.4-1, my previous version, as a temporary
work around.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=493145
Jakob Petsovits changed:
What|Removed |Added
CC||jpe...@petsovits.com
See Also|
https://bugs.kde.org/show_bug.cgi?id=493145
--- Comment #39 from Iyán Méndez Veiga ---
(In reply to Nate Graham from comment #37)
> Cool. I don't suppose that's the case for you as well, Iyán?
Nope. Latest version of kernel, mesa and Plasma. Same issue on my side.
--
You are receiving this mai
https://bugs.kde.org/show_bug.cgi?id=493145
--- Comment #38 from steve ---
Latest updates to Plasma 6.2.2 don't fix the regression for me"
10/23/24 9:15 PMkscreenlocker_greet
file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/lockscreen/LockScreenUi.qml:128:
TypeError: P
https://bugs.kde.org/show_bug.cgi?id=493145
--- Comment #37 from Nate Graham ---
Cool. I don't suppose that's the case for you as well, Iyán?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=493145
--- Comment #36 from Xavier Corredor Llano ---
I updated some packages in my system (mesa, vulkan, and others) and after a
reboot, this issue is no longer occurs, kscreenlocker is working fine, at least
in my case. It could be related to a problem with
https://bugs.kde.org/show_bug.cgi?id=493145
--- Comment #35 from Adam Fontenot ---
I don't think this issue is a duplicate of 483094. This issue appeared for
everyone here when kscreenlocker started to be built on some distros with Qt
6.8, and based on the logs and segfaults seen, there seems to
https://bugs.kde.org/show_bug.cgi?id=493145
Nate Graham changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
|
https://bugs.kde.org/show_bug.cgi?id=493145
Alex changed:
What|Removed |Added
CC||a...@polverini.org
--
You are receiving this mail becau
https://bugs.kde.org/show_bug.cgi?id=493145
--- Comment #34 from Synthetic451 ---
(In reply to Xavier Corredor Llano from comment #30)
> I found a trick to make this work: enter a wrong password and then the
> correct one.
> I think when the kscreenlocker reload (e.g. wrong passwork, or esc mult
https://bugs.kde.org/show_bug.cgi?id=493145
--- Comment #33 from steve ---
I've been getting screenlocker issues beginning with 6.2. After screen sleep
login goes to second login goes to desktop. If I use Enter, it won't work, have
to click on the enter arrow on the dialog. I can avoid all of thi
https://bugs.kde.org/show_bug.cgi?id=493145
--- Comment #32 from steve ---
This may be a duplicate of https://bugs.kde.org/show_bug.cgi?id=483094
On Fri, Oct 18, 2024 at 11:55 PM Iyán Méndez Veiga
wrote:
> https://bugs.kde.org/show_bug.cgi?id=493145
>
> Iyán Méndez Veiga changed:
>
>
https://bugs.kde.org/show_bug.cgi?id=493145
postix changed:
What|Removed |Added
CC||pos...@posteo.eu
--
You are receiving this mail becau
https://bugs.kde.org/show_bug.cgi?id=493145
Iyán Méndez Veiga changed:
What|Removed |Added
Status|REPORTED|CONFIRMED
Ever confirmed|0
https://bugs.kde.org/show_bug.cgi?id=493145
steve changed:
What|Removed |Added
CC||scal...@gmail.com
--
You are receiving this mail becau
https://bugs.kde.org/show_bug.cgi?id=493145
Xavier Corredor Llano changed:
What|Removed |Added
CC||xavier.corredor.llano@gmail
https://bugs.kde.org/show_bug.cgi?id=493145
Isaiah Rosinski changed:
What|Removed |Added
CC||irosin...@outlook.com
--
You are receiving t
https://bugs.kde.org/show_bug.cgi?id=493145
--- Comment #29 from Synthetic451 ---
A bit of a weird crappy workaround, but if you get into a state where you can't
log in, switch to another TTY and kill the kscreenlocker_greeter process. This
will cause another kscreenlocker_greeter process to spaw
https://bugs.kde.org/show_bug.cgi?id=493145
kde.tinker...@passinbox.com changed:
What|Removed |Added
CC||kde.tinker...@passinbox.com
--- Co
https://bugs.kde.org/show_bug.cgi?id=493145
a.samb...@gmail.com changed:
What|Removed |Added
CC||a.samb...@gmail.com
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=493145
--- Comment #27 from Synthetic451 ---
It seems like sleep is irrelevant here actually. I just encountered the bug
again while I stepped away from my computer. When I came back, my screen was
off (LG C2 powered down) but my system was still awake. I turn
https://bugs.kde.org/show_bug.cgi?id=493145
Synthetic451 changed:
What|Removed |Added
CC||bugs.kde.org.facelift226@pa
|
https://bugs.kde.org/show_bug.cgi?id=493145
--- Comment #25 from Adam Fontenot ---
(In reply to Iyán Méndez Veiga from comment #24)
> Are you building with Qt 6.7 or Qt 6.8? Are you using [kde-unstable].
>
> If I filter my logs with sudo journalctl | grep segfault, I have many
> entries, all cau
https://bugs.kde.org/show_bug.cgi?id=493145
--- Comment #24 from Iyán Méndez Veiga ---
Are you building with Qt 6.7 or Qt 6.8? Are you using [kde-unstable].
If I filter my logs with sudo journalctl | grep segfault, I have many entries,
all caused by kscreenlocker since September 14. That day is
https://bugs.kde.org/show_bug.cgi?id=493145
--- Comment #23 from Adam Fontenot ---
Sorry to spam the issue a little, but I just want to add that the code
mentioned elsewhere in my logs also seems relevant:
LockScreenUi.qml:280: TypeError: Property 'respond' of object
1.001511807998,-0.000408
https://bugs.kde.org/show_bug.cgi?id=493145
--- Comment #22 from Adam Fontenot ---
I tried rebuilding kscreenlocker 6.1.5 and installed it. After rebooting my
system, I was still able to reproduce the issue, so whatever caused it (in my
case) must be coming from some other part of the Plasma 6.2
https://bugs.kde.org/show_bug.cgi?id=493145
Adam Fontenot changed:
What|Removed |Added
CC||adam.m.fontenot+kde@gmail.c
|
https://bugs.kde.org/show_bug.cgi?id=493145
--- Comment #20 from Iyán Méndez Veiga ---
https://drive.switch.ch/index.php/s/brMKoQJ6QBHS8Hr
And here is a video of what I just explained in my previous comment. The cut in
~00:16 was just two or three more attempts, exactly the same as the last that
https://bugs.kde.org/show_bug.cgi?id=493145
--- Comment #19 from Iyán Méndez Veiga ---
After that Segmentation fault, which happens after trying a few times to
introduce the password (without any feedback if it's correct or not), a new
kscreenlocker process starts which works as expected to unloc
https://bugs.kde.org/show_bug.cgi?id=493145
Iyán Méndez Veiga changed:
What|Removed |Added
Resolution|WAITINGFORINFO |---
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=493145
--- Comment #17 from Iyán Méndez Veiga ---
After a ~week with Plasma 6.2 final with Qt 6.8.0 I never had this issue when
running on the laptop alone. That is, never connecting the laptop to an
external monitor, to a docking station, etc. The situation i
https://bugs.kde.org/show_bug.cgi?id=493145
--- Comment #16 from Iyán Méndez Veiga ---
I'm sorry I could not provide a useful backtrace for this issue. I had tried
several times, but whenever I attack gdb to the running process I don't manage
to reproduce the issue. Two notes about this: 1) On my
https://bugs.kde.org/show_bug.cgi?id=493145
Nate Graham changed:
What|Removed |Added
Resolution|BACKTRACE |WAITINGFORINFO
--- Comment #15 from Nate Graham
https://bugs.kde.org/show_bug.cgi?id=493145
--- Comment #14 from Iyán Méndez Veiga ---
Today I experienced yet a different variation of the same (?) issue, which is a
high security risk. After opening the laptop lid, kscreenlocker was not shown,
only the mouse, but after a few seconds (~10) the d
https://bugs.kde.org/show_bug.cgi?id=493145
--- Comment #13 from Iyán Méndez Veiga ---
There is no crash listed there. What I tried the other day was connecting via
ssh and attaching gdb to the running process. But when doing that I never
managed to replicate the issue.
--
You are receiving thi
https://bugs.kde.org/show_bug.cgi?id=493145
--- Comment #12 from Nate Graham ---
Can you use `coredumpctl` to get a backtrace of the existing crash? See
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl
--
You a
https://bugs.kde.org/show_bug.cgi?id=493145
--- Comment #11 from Iyán Méndez Veiga ---
Okay, that doesn't work because after I close the lid a second
kscreenlocker_greet is run by Plasma. That is the one that crashes, after I log
in into that one with the trick I mentioned above, then I see the o
https://bugs.kde.org/show_bug.cgi?id=493145
--- Comment #10 from Iyán Méndez Veiga ---
Perhaps I can run gbd /usr/lib/kscreenlocker_greet? I will try...
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=493145
--- Comment #9 from Iyán Méndez Veiga ---
I can reproduce the issue on my desktop as well.
Operating System: Arch Linux
KDE Plasma Version: 6.1.90
KDE Frameworks Version: 6.6.0
Qt Version: 6.8.0
Kernel Version: 6.11.0-arch1-1 (64-bit)
Graphics Platfor
https://bugs.kde.org/show_bug.cgi?id=493145
Nate Graham changed:
What|Removed |Added
Resolution|--- |BACKTRACE
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=493145
--- Comment #7 from Iyán Méndez Veiga ---
I tried now with an external screen and in the external one there is not even
the field to enter the password. Before, in Plasma 6.1 for example, all screens
would behave identically, now there seems to be a dif
https://bugs.kde.org/show_bug.cgi?id=493145
--- Comment #6 from Iyán Méndez Veiga ---
No external screens, just the laptop built-in screen. Tomorrow I'll be back in
the office so I can also check what happens with an external screen.
--
You are receiving this mail because:
You are watching all
https://bugs.kde.org/show_bug.cgi?id=493145
Nate Graham changed:
What|Removed |Added
Priority|NOR |VHI
Keywords|
https://bugs.kde.org/show_bug.cgi?id=493145
--- Comment #4 from Iyán Méndez Veiga ---
I discovered one method that seems to work most of the times. Instead of
changing to a different TTY, by clicking the arrow (or pressing enter) many
times, at some point the screenlocker seems to crash, I get a
https://bugs.kde.org/show_bug.cgi?id=493145
Iyán Méndez Veiga changed:
What|Removed |Added
Resolution|WAITINGFORINFO |---
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=493145
--- Comment #2 from Iyán Méndez Veiga ---
Created attachment 173995
--> https://bugs.kde.org/attachment.cgi?id=173995&action=edit
journalctl-logs
Sorry for the delay. Here are the logs.
--
You are receiving this mail because:
You are watching all b
https://bugs.kde.org/show_bug.cgi?id=493145
Nate Graham changed:
What|Removed |Added
CC||n...@kde.org
Severity|normal
54 matches
Mail list logo
