Bug 166815

Summary:	locking the main toolbar not sustained in kate
Product:	[Applications] kate	Reporter:	sigma <kde>
Component:	general	Assignee:	KWrite Developers <kwrite-bugs-null>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	andresbajotierra
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	unspecified
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description sigma 2008-07-17 10:17:09 UTC

Version:           3.0.98 (using 4.00.98 (KDE 4.0.98 (4.1 RC1)), Kubuntu packages)
Compiler:          gcc
OS:                Linux (i686) release 2.6.24-16-generic

if you right click the main toolbar and lock it, it locks. however when kate is restarted the settings are not saved and the toolbar becomes unlocked by itself, this occurs for all the options on the toolbar menu

Comment 1 Dario Andres 2008-07-31 00:17:31 UTC

Kate Version 3.1.0 Using KDE 4.1.00 (KDE 4.1.0) (KDEmod) in ArchLinux
I can confirm this bug. Also, I think this is related to a lot of toolbar positioning bugs (toolbar settings not saved/loaded) like:
bug 164555 , bug 166202 , bug 167659 , bug 166984 , bug 164500

Comment 2 Stas 2008-08-08 15:29:09 UTC

KDE Version 	3.1.0 (KDE 4.1.00 (KDE 4.1.0), MS Visual Studio 2005 SP1)
Application 	Advanced Text Editor
Operating System 	Microsoft Windows (i686) release 5.1 (XP Professional)
Compiler 	cl.exe

Same problem. Any settings on the toolbar (like setting icons only mode) are not saved for Kate.

Comment 3 Dario Andres 2008-12-18 23:51:28 UTC

Can anyone reproduce this bug using any KDE4.2 version? (beta1 / beta2 / svn) ?

Comment 4 Dario Andres 2009-01-02 14:20:13 UTC

Well..I can't reproduce this bug using:

Qt: 4.4.3 + qt-copy-patches-889120
KDE: 4.1.86 (KDE 4.1.86 (KDE 4.2 >= 20081221))
kdelibs svn rev. 904448 / kdebase svn rev. 904448
kdesdk svn rev. 899416
on ArchLinux x86_64 - Kernel 2.6.27.10

Also, a lot of toolbars bugs were fixed for KDE4.2
Closing :)

Reopen if anyone can still reproduce this in a KDE4.2 version. Thanks

Comment 5 Dario Andres 2009-01-02 14:24:42 UTC


*** This bug has been marked as a duplicate of bug 165205 ***