Bug 500468 - Regression: notification sometimes pops up in the top left instead of the defined location
Summary: Regression: notification sometimes pops up in the top left instead of the def...
Status: RESOLVED DUPLICATE of bug 499970
Alias: None
Product: plasmashell
Classification: Plasma
Component: Notifications (other bugs)
Version First Reported In: 6.3.0
Platform: Other Linux
: NOR normal
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-02-20 15:42 UTC by Christian (Fuchs)
Modified: 2025-02-20 16:47 UTC (History)
2 users (show)

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

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Christian (Fuchs) 2025-02-20 15:42:55 UTC 
SUMMARY
The notification popup in Plasma 6.3 occasionally pops up in the top left corner of the screen instead of where it should (in my case: bottom right)

Unfortunately it's very finnicky and I haven't found a 100% way to reproduce it yet

STEPS TO REPRODUCE
1. Apparently random
2. Receive a notification (I've seen it with Signal chat messages and korganizer event reminders, but probably it's "any")

OBSERVED RESULT
Notification is placed in the top left corner

EXPECTED RESULT
Notification is placed according to config  (next to the systray)

Operating System: Fedora Linux 41
KDE Plasma Version: 6.3.0
KDE Frameworks Version: 6.11.0
Qt Version: 6.8.2
Kernel Version: 6.12.13-200.fc41.x86_64 (64-bit)
Graphics Platform: X11
Processors: 8 × Intel® Core™ i5-8265U CPU @ 1.60GHz
Memory: 15.4 GiB of RAM
Graphics Processor: Intel® UHD Graphics 620
Manufacturer: LENOVO
Product Name: 20NQS30W00

Also reproducible on my desktop system, same software, but nvidia and a dual screen setup


ADDITIONAL INFORMATION
Bug only started occuring after the update to plasma 6.3
Comment 1 cwo 2025-02-20 16:47:12 UTC 
Thank you for the bug report! This issue is already being tracked; marking as a duplicate.

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