Version: 4.3.0 rc2 (using KDE 4.2.96) Compiler: gcc (Gentoo 4.3.3-r2 p1.2, pie-10.1.5) 4.3.3 OS: Linux Installed from: Gentoo Packages I can't modify toolbars of KMail or Akregator (not tested with other components). I can modifiy toolbars with 'Configure toolbars'. My configuration is correctly stored as when I close/reopen Kontact, my configuration is still present in `Configure toolbars'. Unfortunately, my toolbar configuration is never taken in account. (My kontact configuration was upgraded from KDE 4.2.4.)
works for me KMail Version 1.12.0 Using KDE 4.2.96 (KDE 4.2.96 (KDE 4.3 RC2)) Akregator Version 1.4.50 Using KDE 4.2.96 (KDE 4.2.96 (KDE 4.3 RC2)) Kontact Version 4.3.0 rc2 I mean each individual application has it's own set of toolbars, kmail and akregator when run standalone keep their configuration and also when running kontact the view toolbars are remembered, it's just kontact doesn't import the toolbars from when running the applications standalone into it's view (I believe this is the expected behaviour, but I'm not sure) tried each multiple times and worked always however ocasionally these applications crash after clicking on quit from the system tray after doing these operations
Frédéric please can you try with a new account? If it's the same in a new account, can you try on KMail standalone?
With my current account, I can't reproduce the problem with the standalone KMail. For Kontact, I found a workaround : if I click on 'Defaults' button, I'm now able to customize the toolbar. (But 'Defaults' button has a strange effect on the dialog layou : screenshot in attachement)
Created attachment 35414 [details] 'Defaults' button modified the layout of the dialog box
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present? If noone confirms this bug for a Framework-based version of kontact (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months.
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.