Bug 313352

Summary: new notifications show up starting under the panel
Product: [Unmaintained] plasma4 Reporter: m.wege
Component: notificationsAssignee: Marco Martin <notmart>
Status: RESOLVED UNMAINTAINED    
Severity: normal CC: dilfridge, johu, plasma-bugs-null, stupor_scurvy343
Priority: NOR    
Version First Reported In: 4.9.98 RC3   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: Attachment

Description m.wege 2013-01-16 09:18:18 UTC
Since I have installed KDE 4.10 RC new notifications do not start directly above the panel, but start below the panel, so that they can not be seen fully because the panel covers them.

Reproducible: Always
Comment 1 Marco Martin 2013-01-22 13:07:21 UTC
can you do a screenshot of this?
Comment 2 m.wege 2013-01-25 15:20:46 UTC
Is there away to provoke a kind of fake notification which stays a little longer than normal ones so that I can take a screenshot?
Comment 3 Jekyll Wu 2013-01-26 04:05:57 UTC
I think the normal notification already stays long enough for you to take a screenshot. Neverthelss, you can take a screencast, or simply use some stupid hack in two shells :

    $ sleep 3; notify-send "hello"
    $ sleep 4; ksnapshot
Comment 4 m.wege 2013-01-26 09:41:28 UTC
Created attachment 76730 [details]
Attachment
Comment 5 m.wege 2013-01-26 09:42:05 UTC
Done. I had to extend the text. Otherwise one could not see what I mean.
Comment 6 Christoph Feck 2013-02-02 00:35:46 UTC
From what I see, it is just sized too small.
Comment 7 Andreas K. Huettel 2013-09-01 01:28:11 UTC
Is this still visible with current KDE 4.11.0?
Comment 8 Nate Graham 2018-06-08 18:58:01 UTC
Hello!

This bug report was filed for KDE Plasma 4, which reached end-of-support status in August 2015. KDE Plasma 5's desktop shell has been almost completely rewritten for better performance and usability, so it is likely that this bug is already resolved in Plasma 5.

Accordingly, we hope you understand why we must close this bug report. If the issue described  here is still present in KDE Plasma 5.12 or later, please feel free to open a new ticket in the "plasmashell" product after reading https://community.kde.org/Get_Involved/Bug_Reporting

If you would like to get involved in KDE's bug triaging effort so that future mass bug closes like this are less likely, please read https://community.kde.org/Get_Involved#Bug_Triaging

Thanks for your understanding!

Nate Graham