Bug 341160 - Toolbar customizing not followed on start / switch
Summary: Toolbar customizing not followed on start / switch
Status: RESOLVED UNMAINTAINED
Alias: None
Product: korganizer
Classification: Applications
Component: general (show other bugs)
Version: 4.14.2
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-11-21 11:31 UTC by Giuseppe Vinci
Modified: 2018-01-31 17:14 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Giuseppe Vinci 2014-11-21 11:31:34 UTC
In the modules Kalender and Kmail I have set a customized toolbar, which should appear near the default one, just below the menu line. But it does not on starting, nor on first switching to the related module. 


Reproducible: Always

Steps to Reproduce:
1. Add a customized toolbar on Kalender und/or Kmail, if you have not any yet
2. Shut down Kontact
3. Restart Kontact and optionally switch to Kalender or Kmail

Actual Results:  
Customized additional toolbars do not appear on start or first switch. 

Expected Results:  
Personalized toolbars should appear on start and on first switching to modules too.

In order to see them, you have to follow some steps, as you would wont to set a new toolbar. 
I.e. in Kalender (steps to be followed):
a) click on menu point settings / configure toolbars
b) choose a personalized toolbar
c) change something on it
d) confirm with Apply and OK
Now the personalized toolbar appears
Comment 1 Giuseppe Vinci 2014-11-21 11:33:44 UTC
It happens also on KDE /Kontact version 4.14.3
Comment 2 Denis Kurz 2017-06-23 20:04:58 UTC
This bug has never been confirmed for a KDE PIM version that is based on KDE Frameworks (5.x). Those versions differ significantly from the old 4.x series. Therefore, I plan to close it in around two or three months. In the meantime, it is set to WAITINGFORINFO to give reporters the oportunity to check if it is still valid. As soon as someone confirms it for a recent version (at least 5.1, ideally even more recent), I'll gladly reopen it.

Please understand that we lack the manpower to triage bugs reported for versions almost two years beyond their end of life.
Comment 3 Denis Kurz 2018-01-31 17:14:55 UTC
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.1 aka 15.12; preferably much more recent), please open a new one unless it already exists. Thank you for all your input.