SUMMARY Would be nice to see simple, short presentation showing (one time) after first login to freshly upgraded plasma (for example to 5.25). I think it would be helpful for those users who don't read "This week in KDE...." and are not aware new changes/function. For example recently was disabled (by default) function highlighting of screen corners when application is running in full screen. To be honest I was surprised that after update of plasma I could not / had problem to switch from working in full screen VMVare Horizon Client to Plasma desktop or Activity screen. I thought that happened regression and was going to raise request, but I found info about this in "This week in KDE....". I think many users will raise bug report, if will meet something not working what worked before update, I think If such presentation would appear after first login if plasma was updated then kde/plasma team would avoided raising many tickets by users who are not aware about changes. You usually do such presentation when new version of plasma is released, so maybe would be good idea just include it into every new Plasma. BTW. I think you observed that something like that is doing by couple web browsers and IMO this is helpful. STEPS TO REPRODUCE 1. very first login after update to new version of plasma 2. OBSERVED RESULT normal login EXPECTED RESULT simple, short presentation with the most important changes SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.25.2 KDE Frameworks Version: 5.95 Qt Version: 5.15.5 ADDITIONAL INFORMATION
This is a good idea, because I've had it myself! :) Someone needs to do it though. Felipe was working on a welcome wizard that could probably be repurposed to show this information. CCing him. > but I found info about this in "This week in KDE....". I think many users will raise bug report In fact, they have. See Bug 455490. So presenting information of this type more prominently would solve a real issue. Anyway, let's continue the discussion in Bug 441367. *** This bug has been marked as a duplicate of bug 441367 ***