<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!DOCTYPE bugzilla SYSTEM "https://bugs.kde.org/page.cgi?id=bugzilla.dtd">

<bugzilla version="5.0.6"
          urlbase="https://bugs.kde.org/"
          
          maintainer="sysadmin@kde.org"
>

    <bug>
          <bug_id>454706</bug_id>
          
          <creation_ts>2022-06-01 13:24:40 +0000</creation_ts>
          <short_desc>8dbec4a153be35bcab4a1877ee524a7cbcb72e84 inappropriately shows the user the &quot;no password unlock&quot; screen after they supply their fingerprint</short_desc>
          <delta_ts>2025-08-30 02:25:28 +0000</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>10</classification_id>
          <classification>Unmaintained</classification>
          <product>kscreenlocker</product>
          <component>general</component>
          <version>5.24.90</version>
          <rep_platform>Other</rep_platform>
          <op_sys>Linux</op_sys>
          <bug_status>RESOLVED</bug_status>
          <resolution>FIXED</resolution>
          
          
          <bug_file_loc></bug_file_loc>
          <status_whiteboard></status_whiteboard>
          <keywords>regression</keywords>
          <priority>NOR</priority>
          <bug_severity>normal</bug_severity>
          <target_milestone>---</target_milestone>
          
          
          <everconfirmed>1</everconfirmed>
          <reporter name="Nate Graham">nate</reporter>
          <assigned_to name="Plasma Bugs List">plasma-bugs-null</assigned_to>
          <cc>andrej</cc>
    
    <cc>Avamander</cc>
    
    <cc>beojan</cc>
    
    <cc>bshah</cc>
    
    <cc>darcagn</cc>
    
    <cc>fabian</cc>
    
    <cc>kde</cc>
    
    <cc>notsyncing</cc>
    
    <cc>postix</cc>
    
    <cc>rafaeln.dev</cc>
    
    <cc>thuryn1</cc>
    
    <cc>timeygaming69</cc>
          
          <cf_commitlink>https://invent.kde.org/plasma/plasma-workspace/commit/20c51d95798e953acd3299354a5b37a1216b6343</cf_commitlink>
          <cf_versionfixedin>5.26.4</cf_versionfixedin>
          <cf_sentryurl></cf_sentryurl>
          <votes>0</votes>

      

      

      

          <comment_sort_order>oldest_to_newest</comment_sort_order>  
          <long_desc isprivate="0" >
    <commentid>2128171</commentid>
    <comment_count>0</comment_count>
    <who name="Nate Graham">nate</who>
    <bug_when>2022-06-01 13:24:40 +0000</bug_when>
    <thetext>With fingerprint auth configured, 8dbec4a153be35bcab4a1877ee524a7cbcb72e84 regresses the UX:

Previously, placing my finger on the reader would immediately unlock the screen.

Now, placing my finger on the reader brings me to a new screen with an &quot;Unlock&quot; button on it. I have to manually click this button, and then the screen unlocks.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>2128176</commentid>
    <comment_count>1</comment_count>
    <who name="David Edmundson">kde</who>
    <bug_when>2022-06-01 13:39:42 +0000</bug_when>
    <thetext>That&apos;s still better than what we had in 5.24 though?</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>2128180</commentid>
    <comment_count>2</comment_count>
    <who name="Nate Graham">nate</who>
    <bug_when>2022-06-01 13:51:51 +0000</bug_when>
    <thetext>Indeed, it&apos;s better than what we had in 5.24, but it&apos;s worse than what we had in 5.25 prior to that commit. :)</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>2128185</commentid>
    <comment_count>3</comment_count>
    <who name="Nate Graham">nate</who>
    <bug_when>2022-06-01 13:56:44 +0000</bug_when>
    <thetext>I see you removed the regression keyword (I guess because the better state that it&apos;s a regression from was never released to users), but regardless, I would really appreciate a quick fix because the current state is super annoying. :) What we had before 8dbec4a153be35bcab4a1877ee524a7cbcb72e84 was a very pleasant UX.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>2131988</commentid>
    <comment_count>4</comment_count>
    <who name="Nate Graham">nate</who>
    <bug_when>2022-06-16 19:12:34 +0000</bug_when>
    <thetext>*** Bug 455380 has been marked as a duplicate of this bug. ***</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>2133536</commentid>
    <comment_count>5</comment_count>
    <who name="beojan">beojan</who>
    <bug_when>2022-06-21 20:35:08 +0000</bug_when>
    <thetext>For me the Unlock button then doesn&apos;t work, leaving me unable to unlock my session.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>2135447</commentid>
    <comment_count>6</comment_count>
    <who name="">timeygaming69</who>
    <bug_when>2022-06-28 11:31:55 +0000</bug_when>
    <thetext>(In reply to beojan from comment #5)
&gt; For me the Unlock button then doesn&apos;t work, leaving me unable to unlock my
&gt; session.

You&apos;ll have to scan your finger multiple times, at least that&apos;s what worked for me.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>2138543</commentid>
    <comment_count>7</comment_count>
    <who name="">darcagn</who>
    <bug_when>2022-07-12 16:55:06 +0000</bug_when>
    <thetext>(In reply to timeygaming69 from comment #6)
&gt; (In reply to beojan from comment #5)
&gt; &gt; For me the Unlock button then doesn&apos;t work, leaving me unable to unlock my
&gt; &gt; session.
&gt; 
&gt; You&apos;ll have to scan your finger multiple times, at least that&apos;s what worked
&gt; for me.

This bug doesn&apos;t seem to be exclusive to fingerprint reader users only, though. I successfully enter my password and am left with an &quot;unlock&quot; button that does not work at all when clicked, meaning I&apos;m completely unable to unlock my session. I have no fingerprint reader on this system.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>2138581</commentid>
    <comment_count>8</comment_count>
    <who name="Fabian Vogt">fabian</who>
    <bug_when>2022-07-12 18:20:35 +0000</bug_when>
    <thetext>(In reply to darcagn from comment #7)
&gt; (In reply to timeygaming69 from comment #6)
&gt; &gt; (In reply to beojan from comment #5)
&gt; &gt; &gt; For me the Unlock button then doesn&apos;t work, leaving me unable to unlock my
&gt; &gt; &gt; session.
&gt; &gt; 
&gt; &gt; You&apos;ll have to scan your finger multiple times, at least that&apos;s what worked
&gt; &gt; for me.
&gt; 
&gt; This bug doesn&apos;t seem to be exclusive to fingerprint reader users only,
&gt; though. I successfully enter my password and am left with an &quot;unlock&quot; button
&gt; that does not work at all when clicked, meaning I&apos;m completely unable to
&gt; unlock my session. I have no fingerprint reader on this system.

That sounds more like bug 456639.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>2155226</commentid>
    <comment_count>9</comment_count>
    <who name="notsyncing">notsyncing</who>
    <bug_when>2022-09-22 13:17:07 +0000</bug_when>
    <thetext>(In reply to darcagn from comment #7)
&gt; (In reply to timeygaming69 from comment #6)
&gt; &gt; (In reply to beojan from comment #5)
&gt; &gt; &gt; For me the Unlock button then doesn&apos;t work, leaving me unable to unlock my
&gt; &gt; &gt; session.
&gt; &gt; 
&gt; &gt; You&apos;ll have to scan your finger multiple times, at least that&apos;s what worked
&gt; &gt; for me.
&gt; 
&gt; This bug doesn&apos;t seem to be exclusive to fingerprint reader users only,
&gt; though. I successfully enter my password and am left with an &quot;unlock&quot; button
&gt; that does not work at all when clicked, meaning I&apos;m completely unable to
&gt; unlock my session. I have no fingerprint reader on this system.
(In reply to beojan from comment #5)
&gt; For me the Unlock button then doesn&apos;t work, leaving me unable to unlock my
&gt; session.


Same here on 5.25.0 with an unlock button which does nothing. And I found that when the unlock button appears, you can still scan a wrong finger for 3 times, then type your password(of course it won&apos;t show anything), then press enter, it will unlock.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>2176041</commentid>
    <comment_count>10</comment_count>
    <who name="Bug Janitor Service">bug-janitor</who>
    <bug_when>2022-11-21 15:34:26 +0000</bug_when>
    <thetext>A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/2348</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>2176066</commentid>
    <comment_count>11</comment_count>
    <who name="Nate Graham">nate</who>
    <bug_when>2022-11-21 17:56:11 +0000</bug_when>
    <thetext>Git commit bd0c85460225ac91c469030ba05cf172a578fb80 by Nate Graham, on behalf of Janet Blackquill.
Committed on 21/11/2022 at 15:49.
Pushed by ngraham into branch &apos;master&apos;.

lockscreen: Consider info messages to be prompts

The fingerprint message is delivered via this mechanism;
using info messages in our heuristic will allow us to skip
the Unlock button step for fingerprint users.

M  +1    -0    lookandfeel/org.kde.breeze/contents/lockscreen/LockScreenUi.qml

https://invent.kde.org/plasma/plasma-workspace/commit/bd0c85460225ac91c469030ba05cf172a578fb80</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>2176067</commentid>
    <comment_count>12</comment_count>
    <who name="Nate Graham">nate</who>
    <bug_when>2022-11-21 17:58:00 +0000</bug_when>
    <thetext>Git commit 20c51d95798e953acd3299354a5b37a1216b6343 by Nate Graham, on behalf of Janet Blackquill.
Committed on 21/11/2022 at 17:57.
Pushed by ngraham into branch &apos;cherry-pick-bd0c8546&apos;.

lockscreen: Consider info messages to be prompts

The fingerprint message is delivered via this mechanism;
using info messages in our heuristic will allow us to skip
the Unlock button step for fingerprint users.


(cherry picked from commit bd0c85460225ac91c469030ba05cf172a578fb80)

M  +1    -0    lookandfeel/org.kde.breeze/contents/lockscreen/LockScreenUi.qml

https://invent.kde.org/plasma/plasma-workspace/commit/20c51d95798e953acd3299354a5b37a1216b6343</thetext>
  </long_desc>
      
      

    </bug>

</bugzilla>