Bug 509043 - Allow disabling "what's new"
Summary: Allow disabling "what's new"
Status: RESOLVED FIXED
Alias: None
Product: kmail2
Classification: Applications
Component: UI (other bugs)
Version First Reported In: 6.5.0
Platform: NixOS Linux
: NOR wishlist
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-09-02 21:46 UTC by Thomas Baag
Modified: 2025-09-08 16:08 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Thomas Baag 2025-09-02 21:46:53 UTC
Hi, 


I have an ephemeral home directory. Configuration files are generated by the means of Nix, HomeManager and Plasma-Manager. If they are only generated by the application itself they are created at runtime and discarded by a fresh boot.

Having an attention grabbing visual in Kmail2 every time a new feature hits Kmail2 (or a spelling error is fixed) is nothing I seek. I'm also wondering if this is aimed at users only having a single computer as they need to click it away for every computer they use Kmail2 on.

I don't want to change my Nix configuration for Kmail2 every time the "what's new" hash value changes.

Please add a new feature to allow me to disable the new features "what's new".

Thanks!


BR,
Thomas
Comment 1 Laurent Montel 2025-09-03 05:51:20 UTC
Hi,
no I will add a settings for that.
It's the idea to show new version.
If you use stable version you will show it one time . 

And for sure kmail there is not a lot of info.

Regards.
Comment 2 Thomas Baag 2025-09-03 13:37:17 UTC
One time per workstation. Which is 4 times for me. Also there is no stable version of anything KDE. Would be nice if Kmail2 (and Akonadi) would just work. But having a lot of new features and being informed about those is also nice or even important for some, I guess. Regards.
Comment 3 Thomas Baag 2025-09-03 17:09:13 UTC
Can't you just initialize the default hash value with the current hash when PreviousNewFeaturesMD5 is missing from the config? Currently it is assumed that new users want to be greeted with the what's new banner. So here, look at this program which is completely new to you and check out what's new. Probably everything. Doesn't make sense.
Comment 4 Laurent Montel 2025-09-04 04:59:57 UTC
As you wrote it's on each computer, if you have 1 PC you just need to click once.
for me it's the default.
I don't think it's critical :)

But for sure "what's new " is for informing user, otherwise I can remove all.
So no I will not add more settings for it.

For me user need/want to be informed.

Regards.
Comment 5 Thomas Baag 2025-09-04 19:58:39 UTC
> As you wrote it's on each computer, if you have 1 PC you just need to click once.
That's what I've guessed already. Again, I have four with KDE PIM stuff and six in total. All of them sport a rolling release distro. Meaning features hash could change more often than you'd expect. For the four PCs with KDE PIM on it Kmail CANNOT write to kmail2rc. I hope you start to see the problem.
> for me it's the default.
> I don't think it's critical :)
If I do nothing about it, this banner will be displayed all of the time for me. It will never go away because I have to actively do something to make it go away. I need to find out the current hash value and put it into my static kmail2rc, because, again, Kmail CANNOT write this file, it is static and on a read-only mount. The visual annoyance is not critical enough to do those extra steps every time. So it will be displayed all the time for me. You see?
> But for sure "what's new " is for informing user, otherwise I can remove all.
> So no I will not add more settings for it.
That's why I'd ask you to handle the case where it's missing from kmail2rc differently. Currently you assume that the banner should be shown in a first run scenario (or didn't think about this case at all). So it is shown not only if a new feature is added, but also on the very first run of Kmail. Why not change this behavior? Do you understand what I mean or should I attach a patch as an example? It's not a setting. It's a different default for a missing config value.
> For me user need/want to be informed.
I've no issue with that. My issue is with the banner being there all of the time for me informing me of nothing new. Changing the default would inform users about what's new while still allowing me to stay unbothered. No extra setting needed. Why not do that?

Regards.
Comment 6 Laurent Montel 2025-09-08 05:16:10 UTC
Git commit 6f410f542e3e1354f83bf17daf9d8b830737ad7b by Laurent Montel.
Committed on 08/09/2025 at 05:15.
Pushed by mlaurent into branch 'master'.

Don't show "what's new" in first step

M  +12   -7    src/kmmainwidget.cpp

https://invent.kde.org/pim/kmail/-/commit/6f410f542e3e1354f83bf17daf9d8b830737ad7b
Comment 7 Laurent Montel 2025-09-08 05:17:13 UTC
Git commit 60d683d4dbb23874508ffd06c08020c2976db680 by Laurent Montel.
Committed on 08/09/2025 at 05:17.
Pushed by mlaurent into branch 'release/25.08'.

Don't show "what's new" in first step
(cherry picked from commit 6f410f542e3e1354f83bf17daf9d8b830737ad7b)

M  +12   -7    src/kmmainwidget.cpp

https://invent.kde.org/pim/kmail/-/commit/60d683d4dbb23874508ffd06c08020c2976db680
Comment 8 Thomas Baag 2025-09-08 16:08:21 UTC
Thanks mate! You are my hero of the week. Best regards!