Bug 208390

Summary:	akregator doesn't honor "lock toolbar" settings
Product:	[Applications] kontact	Reporter:	Derek Broughton <auspex>
Component:	general	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED UNMAINTAINED
Severity:	normal	CC:	asturm
Priority:	NOR
Version:	4.9.1
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Derek Broughton 2009-09-24 14:55:48 UTC

Version:            (using KDE 4.3.1)
OS:                Linux
Installed from:    Ubuntu Packages

Routinely (but not always) when I open akregator inside kontact (I don't know if it happens if akregator is run standalone), the toolbars have moved.

I want the mail toolbar on the left, the browser toolbar to its immediate right, and the navigator toolbar on the extreme right.  This keeps the icons that are constant in all kontact components in the same places.  So I arrange the bars this way, click on "lock toolbars", and exit.  Next time in, the bars _may_ be this way, or the navigator bar may have moved between the others.

Comment 1 Andreas Sturmlechner 2012-09-10 05:26:43 UTC

This has also bugged me since the very beginning of KDE4 and isn't fixed in 4.9.1.

Navigator toolbar, which I always want to keep to the right, regularly creeps to the left side _between_ the two main toolbars when switching to akregator. It stays correct in all other parts of kontact. It is a bit, well, unnerving. :)

Comment 2 Myriam Schweingruber 2012-09-10 08:16:57 UTC

Setting status to confirmed.

Comment 3 Andreas Sturmlechner 2014-05-16 20:54:05 UTC

Still happening in 4.13.1

Comment 4 Denis Kurz 2016-09-24 19:27:38 UTC

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.

Comment 5 Denis Kurz 2017-01-07 22:33:39 UTC

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.