Created attachment 59306 [details] Screenshot Version: unspecified (using KDE 4.6.2) OS: Linux Notification window slides out of screen when application updates existing notification instance instead of creating new one every time. Reproducible: Always
*** This bug has been confirmed by popular vote. ***
This seems to happen only when custom position is set in ~/.kde/share/config/plasma-desktop-appletsrc. I removed the lines customPosition=-10,18 customPositionAffinityHoriz=r customPositionAffinityVert=b from my plasma-desktop-appletsrc, restarted plasma-desktop and it is working normal now.
(In reply to comment #2) > This seems to happen only when custom position is set in > ~/.kde/share/config/plasma-desktop-appletsrc. I removed the lines > > customPosition=-10,18 > customPositionAffinityHoriz=r > customPositionAffinityVert=b > > from my plasma-desktop-appletsrc, restarted plasma-desktop and it is working > normal now. Yes, removing that lines helped. Thank You.
Git commit 0624d4f3d4ba82a04beea682f79982030e63259c by Lamarque V. Souza. Committed on 10/05/2011 at 02:22. Pushed by lvsouza into branch 'KDE/4.6'. Adjust StackDialog's custom position after a resize event. The position is not saved, so next time it will appear at the same position where it was before the resize event. BUG: 271703 FIXED-IN: 4.6.4 (cherry picked from commit 9d4f1f9d3271ab7a1e4238882c10c5ed9e669918) M +3 -1 plasma/generic/applets/notifications/ui/stackdialog.cpp http://commits.kde.org/kde-workspace/0624d4f3d4ba82a04beea682f79982030e63259c
Git commit 9d4f1f9d3271ab7a1e4238882c10c5ed9e669918 by Lamarque V. Souza. Committed on 10/05/2011 at 02:22. Pushed by lvsouza into branch 'master'. Adjust StackDialog's custom position after a resize event. The position is not saved, so next time it will appear at the same position where it was before the resize event. BUG: 271703 FIXED-IN: 4.6.4 M +3 -1 plasma/generic/applets/notifications/ui/stackdialog.cpp http://commits.kde.org/kde-workspace/9d4f1f9d3271ab7a1e4238882c10c5ed9e669918
*** Bug 273267 has been marked as a duplicate of this bug. ***