I activated the custom location and set it to the upper right corner after I saw notifications coming up randomly at the lower left or lower right corner after I upgraded from 5.4. After each restart I have to set this again. Reproducible: Always Using plasma 5.5.0, Frameworks 5.16 and Qt5.5.1
Same here, Opensuse 42.1, plasma 5.5.0, Frameworks 5.16
Git commit 5c5bbc3f8c4297cfd6862072aa33a45d947fa41b by Martin Klapetek. Committed on 09/12/2015 at 19:07. Pushed by mklapetek into branch 'Plasma/5.5'. [notifications] Move reading globalConfig() from ctor to init() The globalConfig() in ctor returns a non-(yet-)existing KConfigGroup which makes it always return the default value. So the config access must be delayed for init(). Custom notification position is now correctly remembered. FIXED-IN: 5.5.1 M +7 -3 applets/notifications/lib/notificationsapplet.cpp M +1 -0 applets/notifications/lib/notificationsapplet.h http://commits.kde.org/plasma-workspace/5c5bbc3f8c4297cfd6862072aa33a45d947fa41b
*** Bug 356613 has been marked as a duplicate of this bug. ***
(In reply to Martin Klapetek from comment #2) > Git commit 5c5bbc3f8c4297cfd6862072aa33a45d947fa41b by Martin Klapetek. > Committed on 09/12/2015 at 19:07. > Pushed by mklapetek into branch 'Plasma/5.5'. > > [notifications] Move reading globalConfig() from ctor to init() > > The globalConfig() in ctor returns a non-(yet-)existing KConfigGroup > which makes it always return the default value. So the config access > must be delayed for init(). > > Custom notification position is now correctly remembered. > FIXED-IN: 5.5.1 > > M +7 -3 applets/notifications/lib/notificationsapplet.cpp > M +1 -0 applets/notifications/lib/notificationsapplet.h > > http://commits.kde.org/plasma-workspace/ > 5c5bbc3f8c4297cfd6862072aa33a45d947fa41b There is a minor papercut currently with the saving. Say you have custom position already saved; (top-right for this purpose) open settings and unselect "Use custom position...." and then select it together with a postion and apply. If you select the same position it wont save.
Thanks, I'll investigate.
That config issue should be fixed now; 5.5.4 should have the fix.