https://bugs.kde.org/show_bug.cgi?id=374890
Fabian Beutel changed:
What|Removed |Added
Blocks|474811 |
Referenced Bugs:
https://bugs.kde.org/show_b
https://bugs.kde.org/show_bug.cgi?id=374890
Fabian Beutel changed:
What|Removed |Added
Blocks||474811
Referenced Bugs:
https://bugs.kde.org/
https://bugs.kde.org/show_bug.cgi?id=374890
--- Comment #54 from Nate Graham ---
These seem suspicious:
Sep 21 08:01:27 latitude kscreenlocker_greet[14825]: qt.qpa.wayland: Creating a
fake screen in order for Qt not to crash
Sep 21 08:01:27 latitude kscreenlocker_greet[14825]: The Wayland connec
https://bugs.kde.org/show_bug.cgi?id=374890
Fabian Beutel changed:
What|Removed |Added
CC||f...@hedgeware.net
--- Comment #53 from Fabian
https://bugs.kde.org/show_bug.cgi?id=374890
idoitprone changed:
What|Removed |Added
CC||monkeyboy...@yahoo.com
--- Comment #52 from idoitp
https://bugs.kde.org/show_bug.cgi?id=374890
--- Comment #51 from Hugh Phoenix-Hulme ---
Killing one is working for me, but it's not a great solution. To minimise
hassle one could write a script to kill the first process if there are multiple
and run it as a cron job every second, but that's obvio
https://bugs.kde.org/show_bug.cgi?id=374890
aux...@gmail.com changed:
What|Removed |Added
CC||aux...@gmail.com
--- Comment #50 from aux...@
https://bugs.kde.org/show_bug.cgi?id=374890
Hugh Phoenix-Hulme changed:
What|Removed |Added
CC||h...@webnet.org.uk
--- Comment #49 from Hu
https://bugs.kde.org/show_bug.cgi?id=374890
--- Comment #48 from Vitaliy Filippov ---
I don't think there are 2 of them... I always check processes with `ps ax|grep
kscr` when I'm killing a stuck kscreenlocker_greet and I always see 2
processes:
1) /usr/lib/x86_64-linux-gnu/libexec/kf5/kscreen_ba
https://bugs.kde.org/show_bug.cgi?id=374890
--- Comment #47 from Nate Graham ---
Thanks! Looks like two kscreenlocker_greet processes are running and one is
stuck in a futex while the other is in a pselect64 syscall. Maybe they're
blocking one another.
--
You are receiving this mail because:
Yo
https://bugs.kde.org/show_bug.cgi?id=374890
Vitaliy Filippov changed:
What|Removed |Added
Status|NEEDSINFO |REPORTED
Resolution|WAITINGFORINFO
https://bugs.kde.org/show_bug.cgi?id=374890
--- Comment #46 from Vitaliy Filippov ---
Created attachment 15
--> https://bugs.kde.org/attachment.cgi?id=15&action=edit
hung kscreenlocker stack traces with debug info
--
You are receiving this mail because:
You are watching all bug change
https://bugs.kde.org/show_bug.cgi?id=374890
--- Comment #45 from Bug Janitor Service ---
Dear Bug Submitter,
This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular
https://bugs.kde.org/show_bug.cgi?id=374890
--- Comment #44 from Vincent PINON ---
> The error occurred several times again, and actually "kscreenlocker" line
> doesn't appear every time in journalctl, whereas kwin_wayland failure is
> always here.
> It was still on 5.26.90 (latest available in D
https://bugs.kde.org/show_bug.cgi?id=374890
--- Comment #43 from Harald Sitter ---
Works fine for me :|
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=374890
--- Comment #42 from Vitaliy Filippov ---
Ok, I can do that, the bug still reproduces almost every time when compositing
is disabled
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=374890
Harald Sitter changed:
What|Removed |Added
CC||sit...@kde.org
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=374890
zellox changed:
What|Removed |Added
CC||zel...@fastmail.com
--
You are receiving this mail be
https://bugs.kde.org/show_bug.cgi?id=374890
Sam James changed:
What|Removed |Added
CC||s...@gentoo.org
--
You are receiving this mail bec
https://bugs.kde.org/show_bug.cgi?id=374890
--- Comment #40 from Vitaliy Filippov ---
Seems that it still hangs when compositing is disabled, yeah.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=374890
--- Comment #39 from Vitaliy Filippov ---
Created attachment 157143
--> https://bugs.kde.org/attachment.cgi?id=157143&action=edit
Stack traces of hung kscreenlocker_greet
Ok, finally I got another hang with 5.27.2. Attaching stack traces of all
threa
https://bugs.kde.org/show_bug.cgi?id=374890
--- Comment #38 from Vitaliy Filippov ---
In fact it hasn't reproduced for me more since that 1 time. So it seems that
it's almost fixed. Only 1 failure in 5 days with 5.27.2 by now :)
--
You are receiving this mail because:
You are watching all bug c
https://bugs.kde.org/show_bug.cgi?id=374890
--- Comment #37 from Vincent PINON ---
(In reply to Vincent PINON from comment #29)
> I have 2 laptops on Debian testing (plasma 5.26.90-1, qt 5.15.8+dfsg-2),
> that regularly fail to unlock after sleep (but not always, haven't
> identified the exact si
https://bugs.kde.org/show_bug.cgi?id=374890
Rick Scholten changed:
What|Removed |Added
CC|khr...@proton.me|
--
You are receiving this mail because:
You a
https://bugs.kde.org/show_bug.cgi?id=374890
--- Comment #36 from Vitaliy Filippov ---
I almost thought it was fixed :) but it reproduced with 5.27.2 again, after a
day of usage. :) I tend to think that it's still slightly better because today
I only had to kill -9 it one time instead of several t
https://bugs.kde.org/show_bug.cgi?id=374890
--- Comment #35 from Vitaliy Filippov ---
(In reply to Simon B from comment #34)
> Is it still occurring with plasma 5.27.x? Some similar bugs got resolved
> with this release
Thanks for the information, I just installed 5.27.2, will check if the bug
s
https://bugs.kde.org/show_bug.cgi?id=374890
Simon B changed:
What|Removed |Added
CC||sbutcher+b...@gmail.com
--- Comment #34 from Simon B
https://bugs.kde.org/show_bug.cgi?id=374890
--- Comment #33 from Vitaliy Filippov ---
By the way, I don't use a multiscreen setup - for me it reproduces on a laptop
without the external monitor, and with Intel integrated graphics (I also have
nvidia proprietary driver installed but I don't think
https://bugs.kde.org/show_bug.cgi?id=374890
Vitaliy Filippov changed:
What|Removed |Added
CC||vita...@yourcmc.ru
--- Comment #32 from Vita
https://bugs.kde.org/show_bug.cgi?id=374890
--- Comment #31 from Nate Graham ---
(In reply to d.brown from comment #30)
> Hello, I am coming from #456210.
>
> 1. Enter password at lock screen
> 2. The login UI closes
> 3. Instead of going to desktop as normal, a button that says "Unlock" appears
https://bugs.kde.org/show_bug.cgi?id=374890
d.br...@hackion.com changed:
What|Removed |Added
CC||d.br...@hackion.com
--- Comment #30 from d
https://bugs.kde.org/show_bug.cgi?id=374890
Vincent PINON changed:
What|Removed |Added
CC||vpi...@kde.org
--- Comment #29 from Vincent PIN
https://bugs.kde.org/show_bug.cgi?id=374890
--- Comment #28 from Nate Graham ---
It mostly shows that the NVIDIA driver is involved. Beyond that, I can't tell.
But the issue doesn't seem NVIDIA-specific, as people with Intel GPUs and
open-source Mesa drivers have reported experiencing it too.
--
https://bugs.kde.org/show_bug.cgi?id=374890
--- Comment #27 from jkallinge...@gmx.at ---
Created attachment 156229
--> https://bugs.kde.org/attachment.cgi?id=156229&action=edit
gdb backtrace
coming from Bug 465113, hopefully this is somewhat helpful
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=374890
Rick Scholten changed:
What|Removed |Added
CC||khr...@proton.me
--
You are receiving this mai
https://bugs.kde.org/show_bug.cgi?id=374890
Nate Graham changed:
What|Removed |Added
CC||jkallinge...@gmx.at
--- Comment #26 from Nate Gra
https://bugs.kde.org/show_bug.cgi?id=374890
soredake changed:
What|Removed |Added
CC|ndrzj1...@relay.firefox.com |
--
You are receiving this mail because:
You are wa
https://bugs.kde.org/show_bug.cgi?id=374890
Ferry changed:
What|Removed |Added
CC||ferry.t...@elsinga.info
--- Comment #25 from Ferry ---
https://bugs.kde.org/show_bug.cgi?id=374890
Alexander Kernozhitsky changed:
What|Removed |Added
CC||sh200...@mail.ru
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=374890
Nate Graham changed:
What|Removed |Added
CC||alexander.fieroch@mpi-dortm
|
https://bugs.kde.org/show_bug.cgi?id=374890
Nate Graham changed:
What|Removed |Added
Priority|NOR |VHI
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=374890
Nate Graham changed:
What|Removed |Added
CC||ke...@myplaceonline.com
--- Comment #23 from Nate
https://bugs.kde.org/show_bug.cgi?id=374890
Nate Graham changed:
What|Removed |Added
CC||php4...@gmail.com
--- Comment #22 from Nate Graha
https://bugs.kde.org/show_bug.cgi?id=374890
Nate Graham changed:
What|Removed |Added
Component|greeter |general
--
You are receiving this mail because:
https://bugs.kde.org/show_bug.cgi?id=374890
Nate Graham changed:
What|Removed |Added
CC||n...@kde.org
Severity|normal
https://bugs.kde.org/show_bug.cgi?id=374890
Aleix Pol changed:
What|Removed |Added
CC||david.cortes.rivera@gmail.c
|
https://bugs.kde.org/show_bug.cgi?id=374890
Nathaniel changed:
What|Removed |Added
CC||digitalpion...@gmail.com
--- Comment #19 from Natha
https://bugs.kde.org/show_bug.cgi?id=374890
j...@raby.sh changed:
What|Removed |Added
CC||j...@raby.sh
--- Comment #18 from j...@raby.sh --
https://bugs.kde.org/show_bug.cgi?id=374890
ruruoli changed:
What|Removed |Added
CC||maniikarab...@protonmail.ch
--
You are receiving thi
https://bugs.kde.org/show_bug.cgi?id=374890
Andy changed:
What|Removed |Added
CC||kde.20.andromodon@spamgourm
|
https://bugs.kde.org/show_bug.cgi?id=374890
--- Comment #16 from Eirik Schultz ---
Hi,
I also have the same issue on both my laptop and workstation running Arch
Linux. Currently I'm running plasma-desktop 5.19.4-1 from the standard
archlinux package repository. Please let me know if I can provid
https://bugs.kde.org/show_bug.cgi?id=374890
Eirik Schultz changed:
What|Removed |Added
CC||schultz...@gmail.com
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=374890
--- Comment #15 from Jan-Matthias Braun ---
On an interesting side note, I have observed that not all screens are frozen at
the same time, i.e., the laptop display stopped three minutes before the two
external ones.
--
You are receiving this mail beca
https://bugs.kde.org/show_bug.cgi?id=374890
--- Comment #14 from Jan-Matthias Braun ---
Some more testing … with probably unhelpful outcome.
On a machine with an old nvidia graphics card, I cannot observe any issue.
On the questionable machine with Intel graphics, I had a period last week where
https://bugs.kde.org/show_bug.cgi?id=374890
Christoph Feck changed:
What|Removed |Added
Status|NEEDSINFO |REPORTED
Resolution|WAITINGFORINFO
https://bugs.kde.org/show_bug.cgi?id=374890
--- Comment #12 from Bug Janitor Service ---
Dear Bug Submitter,
This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular
https://bugs.kde.org/show_bug.cgi?id=374890
--- Comment #11 from Jan-Matthias Braun ---
Is there any more information I could provide?
(I do think that there are general problems -- at least with the intel OpenGL
-- stack, as kwin_x11, plasmashell, and krunner also sometimes freeze).
But I don't
https://bugs.kde.org/show_bug.cgi?id=374890
--- Comment #10 from Jan-Matthias Braun ---
Hi! This backtrace is when directly calling with --testing . The hang occurred
after entering the password.
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.s
https://bugs.kde.org/show_bug.cgi?id=374890
David Edmundson changed:
What|Removed |Added
Status|REPORTED|NEEDSINFO
CC|
https://bugs.kde.org/show_bug.cgi?id=374890
--- Comment #8 from Jan-Matthias Braun ---
Just to make sure that the driver does not interfere I checked: the backtraces
after not setting MESA_LOADER_DRIVER_OVERRIDE=iris look the same as with the
iris driver.
--
You are receiving this mail because:
https://bugs.kde.org/show_bug.cgi?id=374890
--- Comment #7 from Jan-Matthias Braun ---
> I now collected backtraces in two conditions:
I forgot to explicitly mention that these backtraces were all collected when
using the iris driver. I will add backtraces for the standard intel i965
driver, but
https://bugs.kde.org/show_bug.cgi?id=374890
Jan-Matthias Braun changed:
What|Removed |Added
CC||jan_br...@gmx.net
--- Comment #6 from Jan-
https://bugs.kde.org/show_bug.cgi?id=374890
--- Comment #5 from Christian Muehlhaeuser ---
Certainly still "NotWorkingForMe". Happy to provide more info, but that's all I
got for now.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=374890
Bhushan Shah changed:
What|Removed |Added
Status|RESOLVED|REPORTED
Resolution|WORKSFORME
https://bugs.kde.org/show_bug.cgi?id=374890
fbampaloukas changed:
What|Removed |Added
Resolution|--- |WORKSFORME
CC|
https://bugs.kde.org/show_bug.cgi?id=374890
--- Comment #2 from Christian Muehlhaeuser ---
I see what's happening now: the screen-locker is active on multiple monitors
and only lets me enter the password on one of them. All the other monitors show
the locker, but don't react to input.
--
You ar
https://bugs.kde.org/show_bug.cgi?id=374890
--- Comment #1 from Martin Gräßlin ---
can you try to gdb into the frozen process and get a backtrace?
--
You are receiving this mail because:
You are watching all bug changes.
67 matches
Mail list logo