Bug 99152

Summary:	"set as default schema" doesn't affect "Konsole Default" schema
Product:	[Applications] konsole	Reporter:	Zack Cerza <zack>
Component:	general	Assignee:	Konsole Developer <konsole-devel>
Status:	RESOLVED DUPLICATE
Severity:	normal
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Debian testing
OS:	Linux
Latest Commit:		Version Fixed In:

Description Zack Cerza 2005-02-11 20:27:19 UTC

Version:            (using KDE KDE 3.3.2)
Installed from:    Debian testing/unstable Packages
OS:                Linux

When I use the "set as default schema" checkbox in konsole, then save the schema, konsole seems to start up using that schema as expected.

But if I load the "Konsole Default" schema - which doesn't exist in the editable schema list - it loads something that is clearly not the schema I just set as default. This makes konsolepart behave differently from konsole - and I can't imagine why anyone would think I'd want that by default.

Comment 1 Kurt Hindenburg 2005-02-12 06:35:13 UTC

As I mentioned in 99153, konsole_part and konsole use 2 different setting files.

There is no 'Konsole Default' schema file.  It is hardcoded into konsole.

Please clarify this bug as to what you want.

Comment 2 Zack Cerza 2005-02-14 00:01:48 UTC

Well, all I want is for konsole_part and konsole to use the same settings. I guess this is another duplicate of #94169 .

Comment 3 Kurt Hindenburg 2005-02-14 00:22:46 UTC

I guess it is not obvious that konsole and konsole_part would use 2 different setting files.  I would think/hope 94169 will be in KDE4.0.

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