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

            Bug ID: 481681
           Summary: Application Launcher menu background does not remember
                    Opacity setting across sessions
    Classification: Plasma
           Product: plasmashell
           Version: 5.27.10
          Platform: Other
                OS: Linux
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: Application Menu (Kicker)
          Assignee: [email protected]
          Reporter: [email protected]
  Target Milestone: 1.0

SUMMARY
Application Launcher does not remember the Opacity setting beyond the current
session. Even if set to opaque, it returns to Translucent after logout/reboot.

STEPS TO REPRODUCE
1. Right-click on taskbar -> Enter Edit Mode
2. Click More Options -> Opacity -> Opaque

Click Application Launcher -> Note that launcher background is opaque
Click "Show Hidden Icons" in System Tray -> Note that "Status and
Notifications" popup is opaque

3. Log out and log back in

Click Application Launcher -> Note that launcher background is translucent.
Click "Show Hidden Icons" in System Tray -> Note that "Status and
Notifications" popup is translucent


OBSERVED RESULT
Application Launcher menu reverts to Translucent after every logout/reboot.

Edit Mode -> More Options still shows Opacity as Opaque. Setting it to Adaptive
or Translucent and then back to Opaque fixes it for the session, but it will
revert again at logout.

EXPECTED RESULT
Application Launcher menu should remember Opacity settings across sessions to
match the task bar.

SOFTWARE/OS VERSIONS
Operating System: Fedora Linux 39
KDE Plasma Version: 5.27.10
KDE Frameworks Version: 5.115.0
Qt Version: 5.15.12
Kernel Version: 6.7.4-200.fc39.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 12 × 12th Gen Intel® Core™ i5-12400
Memory: 31.1 GiB of RAM
Graphics Processor: AMD Radeon RX 6600
Manufacturer: Gigabyte Technology Co., Ltd.
Product Name: B660M DS3H DDR4

ADDITIONAL INFORMATION
Sounds similar to the title of bug 452796, but that one claims to have been
fixed in 5.25. I can repro in 5.27.10.

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

Reply via email to