https://bugs.kde.org/show_bug.cgi?id=494927
--- Comment #5 from Airbag ---
I had the bug reproduced without the 2nd screen, so I edit the title.
Like the previous comments, I have the repetition of "LockScreenUi.qml:280:
TypeError: Property 'respond' of object ".
It happen
https://bugs.kde.org/show_bug.cgi?id=494927
Airbag changed:
What|Removed |Added
Summary|kscreen_locker does not |kscreen_locker does not
|unlock
https://bugs.kde.org/show_bug.cgi?id=483094
Airbag changed:
What|Removed |Added
CC||saroum...@rbox.me
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=494927
--- Comment #8 from Airbag ---
This bug might be a duplicate of this 7 months old bug :
https://bugs.kde.org/show_bug.cgi?id=483094
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=483094
--- Comment #44 from Airbag ---
I think I might have opened a duplicate here :
https://bugs.kde.org/show_bug.cgi?id=494927
The difference is that I (and other people, apparently) have a specific line
repeated in logs, when trying (without success) to
https://bugs.kde.org/show_bug.cgi?id=494927
Bug ID: 494927
Summary: kscreeen_locker does not unlock screen if there is a
2nd display connected
Classification: Plasma
Product: kscreenlocker
Version: 6.2.1
Platform: Arch
https://bugs.kde.org/show_bug.cgi?id=494927
Airbag changed:
What|Removed |Added
Summary|kscreeen_locker does not|kscreen_locker does not
|unlock
https://bugs.kde.org/show_bug.cgi?id=494927
--- Comment #1 from Airbag ---
(In reply to Airbag from comment #0)
> OBSERVED RESULT
> The field for entering the password is blanked, nothing else is changed, no
> error message, the unlock screen stays on screen.
> You can try to type
https://bugs.kde.org/show_bug.cgi?id=494927
--- Comment #12 from Airbag ---
I wonder if there are some specific triggering conditions. That will explain
that a majority of people are not affected.
For me : my monitor is in 3840x2160 and I use 200% scaling, and an ICC profile.
Do you have any of
https://bugs.kde.org/show_bug.cgi?id=494927
--- Comment #23 from Airbag ---
(In reply to Nate Graham from comment #17)
> Interesting. In step 2, you say "wake up the screen", but screen locking
> doesn't automatically put screens to sleep. Is a step missing? Maybe
https://bugs.kde.org/show_bug.cgi?id=494927
--- Comment #24 from Airbag ---
(In reply to Nate Graham from comment #17)
> Interesting. In step 2, you say "wake up the screen", but screen locking
> doesn't automatically put screens to sleep. Is a step missing? Maybe
https://bugs.kde.org/show_bug.cgi?id=494927
--- Comment #16 from Airbag ---
Eureka ! On my setup, I found a way to reproduce the problem at will (and a
workaround to avoid it completely)
1. Lock the screen manually (or wait for the X min delay you have set up in the
settings), and wait for the
https://bugs.kde.org/show_bug.cgi?id=494927
--- Comment #49 from Airbag ---
(In reply to Airbag from comment #48)
> (In reply to Torabi from comment #46)
> > A report has been filed upstream
> > (https://bugreports.qt.io/browse/QTBUG-130767) for the Qt issue presumably
> >
https://bugs.kde.org/show_bug.cgi?id=494927
--- Comment #48 from Airbag ---
(In reply to Torabi from comment #46)
> A report has been filed upstream
> (https://bugreports.qt.io/browse/QTBUG-130767) for the Qt issue presumably
> causing this, but I have also seen comments suggesting tha
https://bugs.kde.org/show_bug.cgi?id=494804
Airbag changed:
What|Removed |Added
CC|saroum...@rbox.me |
See Also|https://bugreports.qt.io/br
https://bugs.kde.org/show_bug.cgi?id=494804
Airbag changed:
What|Removed |Added
CC||saroum...@rbox.me
--
You are receiving this mail
16 matches
Mail list logo
