Bug 488531 - Strange shadows in the desktop tray
Summary: Strange shadows in the desktop tray
Status: RESOLVED DUPLICATE of bug 488295
Alias: None
Product: plasmashell
Classification: Plasma
Component: System Tray (show other bugs)
Version: 6.0.5
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-06-15 12:27 UTC by Sobirjon Matnazarov
Modified: 2024-06-17 08:27 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
Screenshot (1.58 MB, image/png)
2024-06-15 12:28 UTC, Sobirjon Matnazarov
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Sobirjon Matnazarov 2024-06-15 12:27:04 UTC
***
If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org

If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***

SUMMARY
When maximizing the window, a shadow appeared in the desktop panel, which no longer disappears when the window is made smaller.

STEPS TO REPRODUCE
1. Open Steam
2. Expand the window
3. Make the window smaller

OBSERVED RESULT
With such an action, shadows appeared in the panel that do not disappear.

EXPECTED RESULT
When doing this, there should be no shadows in the panel.

SOFTWARE/OS VERSIONS
Operating System: Fedora Linux 40
KDE Plasma Version: 6.0.5
KDE Frameworks Version: 6.3.0
Qt Version: 6.7.1
Kernel Version: 6.8.11-300.fc40.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 12 × AMD Ryzen 5 5500U with Radeon Graphics
Memory: 7.1 GiB of RAM
Graphics Processor: AMD Radeon Graphics
Manufacturer: ASUSTeK COMPUTER INC.
Product Name: VivoBook_ASUSLaptop X513UA_M513UA
System Version: 1.0

ADDITIONAL INFORMATION
(no response)
Comment 1 Sobirjon Matnazarov 2024-06-15 12:28:25 UTC
Created attachment 170520 [details]
Screenshot
Comment 2 David Redondo 2024-06-17 08:27:48 UTC

*** This bug has been marked as a duplicate of bug 488295 ***