Bug 415819

Summary: Notification entry in history too small in height resulting in an overlap
Product: [Plasma] plasmashell Reporter: postix <postix>
Component: NotificationsAssignee: Kai Uwe Broulik <kde>
Status: RESOLVED DUPLICATE    
Severity: normal CC: kdelibs-bugs, nate, niccolo.venerandi, nroycea+kde, plasma-bugs, postix, squeakypancakes, vopahi2164
Priority: HI Keywords: regression
Version: 5.19.3   
Target Milestone: 1.0   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed In:
Attachments: Screenshot of the issue.
Screenshot (Scaling: 2.0)
Notification Group Overlap
"show less" overlap, scale=100% (5.21.5)

Description postix 2020-01-02 19:51:53 UTC
Created attachment 124861 [details]
Screenshot of the issue.

SUMMARY

As you can see in the screenshot, one notification's height was too small, resulting in an overlap with the notification beneath. 
"Do not reply to this email. You can add" and "[my mail address] has 1 new" overlap.
This is the very first time I experienced it. After receiving a new notification and closing and opening the history, the issue was gone.

SOFTWARE/OS VERSIONS
Operating System: Manjaro Linux 
KDE Plasma Version: 5.17.4
KDE Frameworks Version: 5.66.0
Qt Version: 5.14.0

ADDITIONAL INFORMATION
Scaling: 1.5
Forced Font DPI: 144
Comment 1 postix 2020-01-02 19:53:58 UTC
You can also see that the title of the problematic notification elides instead of line breaks as the other notification with the same content.
Comment 2 Squeaky Pancakes 2020-06-26 23:19:28 UTC
I also see this issue on 5.19.2
Comment 3 postix 2020-07-23 20:28:08 UTC
Created attachment 130348 [details]
Screenshot (Scaling: 2.0)

Still happens and also happens for scaling 2.0
Comment 4 vindicator 2020-07-30 04:48:40 UTC
Created attachment 130500 [details]
Notification Group Overlap

I just encountered this issue as well with the the same version (5.19.3).
Comment 5 vopahi2164 2021-07-08 15:46:18 UTC
Created attachment 139954 [details]
"show less" overlap, scale=100%

(5.21.5)
Comment 6 postix 2021-10-16 10:54:50 UTC
Looks like it's a duplicate and that it has been resolved. :-)

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