https://bugs.kde.org/show_bug.cgi?id=525165

            Bug ID: 525165
           Summary: OSD can fail to show on lock screen
    Classification: Plasma
           Product: plasmashell
      Version First 6.7.80
       Reported In:
          Platform: Other
                OS: Linux
            Status: REPORTED
          Severity: minor
          Priority: NOR
         Component: Theme - Breeze
          Assignee: [email protected]
          Reporter: [email protected]
                CC: [email protected]
  Target Milestone: 1.0

DESCRIPTION

Using a rather convoluted set of steps, I can get the OSD to fail to show up on
the lock screen. I'm not 100% certain about the steps, but if I do these a
couple of times it happens consistently on two laptops and one desktop, using
master or Fedora's 6.7.

STEPS TO REPRODUCE
1. Lock screen
2. Volume Up key/binding, with the Volume OSD showing press Esc  
3. Wait a bit (few seconds), Volume Up, wait a bit, Esc
4. Repeat 2-3 a couple of times (usually 1-2 times is enough, I don't think
I've managed to make it happen the first time)

OBSERVED RESULT

At some point, pressing Volume Up again does not show the OSD anymore until you
unlock the screen. In the main session, and when locking it again, it's fixed

EXPECTED RESULT

Keeps showing the OSD whenever I press Volume Up

SOFTWARE/OS VERSIONS

Operating System: Fedora Linux 44
KDE Plasma Version: 6.7.80
KDE Frameworks Version: 6.30.0
Qt Version: 6.11.2
Kernel Version: 7.1.12-200.fc44.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 16 × 12th Gen Intel® Core™ i7-1270P
Memory: 32 GiB of RAM (30.9 GiB usable)
Graphics Processor: Intel® Iris® Xe Graphics

ADDITIONAL INFORMATION

I've found a second way to trigger it that doesn't involve Esc, but this is way
less reproducible. It involves pressing Volume Up relatively soon before the
password thing is timing out, then sometimes pressing Volume Down - sometimes
it will fail to show up, and from then on the OSD is dead.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to