I'm using my existing 3.5.10 ~/.kde profile. I mentioned this quirk previously.
When I start KDE 3.5.10, my konsole has a black background with tabs on the top. That is what I want.
When I start Trinity KDE, my konsole has a white background with tabs on the bottom.
Pretty good way to irritate new users migrating to Trinity from 3.5.10. :)
I have seen this behavior before --- in Debian Lenny. I never traced the cause. I guess now I will.
As the Trinity KDE sources were started from Debian Lenny rather than from the stock 3.5.10, I suspect Trinity is carrying some weird baggage from Debian Lenny.
I do not believe any user configuration files are being changed. My reasoning is I can exit Trinity, log in two seconds later in 3.5.10, and konsole is black with tabs on top.
I presume some *.desktop file somewhere defines the default konsole in Debian/Trinity as white background and tabs on bottom. I don't care for that default selection, but my user configuration should prevail.
Why are the user configuration files being ignored for konsole?
If I understand correctly:
1. Color schemes are controlled by schema files in /usr/share/apps/konsole. 2. The preferred user scheme is defined in ~/.kde/share/apps/konsole/shell.desktop. 3. If ~/.kde/share/apps/konsole/shell.desktop does not exist then the system default Konsole is used. 4. The default Konsole schema is defined in /usr/share/apps/konsole/linux.desktop and shell.desktop. 5. In both 3.5.10 and Trinity, the default schema in linux.desktop is Linux.schema. 6. Linux.schema is the same in both 3.5.10 and Trinity. 7. shell.desktop is the same in both 3.5.10 and Trinity. 8. I'm unsure how to read the schema files, but I think the background color in Linux.schema is black.
At this point I'm lost as to why Trinity opens konsole with a white background and tabs on the bottom.
Darrell
More info:
In Trinity konsole is using the Black on Light Colors schema.
In 3.5.10 I am using the Linux Colors schema. that is my system default too.
I still don't know where the override is occuring.
Perchance is this only when you run as root?
Non-root too.
How are you setting the schema? On my systems I do this in Konsole: Settings->Schema->Transparent, Dark Background Settings->Save as Default
The next time Konsole is launched, it uses the saved schema.
Tim
this in Konsole: Settings->Schema->Transparent, Dark Background Settings->Save as Default
The next time Konsole is launched, it uses the saved schema.
That's my point. I'm not changing anything.
I start 3.5.10 with my existing profile. I get a black background and tabs on top. That is what I want.
I log out of 3.5.10. I log in with the same account in Trinity. White background and tabs on bottom.
I log out of Trinity and log in to 3.5.10. I have a black background and tabs on top.
I'm not changing anything. Yet Trinity does not honor my konsole configuration. Something is overriding.
As I saw this in Lenny I presume Trinity is carrying the same baggage. I haven't yet figured out what causes this quirk.
Yes, I can reset the schema, but my toggling between the two desktops shows that my configuration is not being changed --- just not honored. If the configuration changed, then when I returned to 3.5.10 I would see a white background and tabs on bottom. I don't. I see black and tabs on top.
this in Konsole: Settings->Schema->Transparent, Dark Background Settings->Save as Default
The next time Konsole is launched, it uses the saved schema.
That's my point. I'm not changing anything.
I start 3.5.10 with my existing profile. I get a black background and tabs on top. That is what I want.
I log out of 3.5.10. I log in with the same account in Trinity. White background and tabs on bottom.
I log out of Trinity and log in to 3.5.10. I have a black background and tabs on top.
I'm not changing anything. Yet Trinity does not honor my konsole configuration. Something is overriding.
As I saw this in Lenny I presume Trinity is carrying the same baggage. I haven't yet figured out what causes this quirk.
Yes, I can reset the schema, but my toggling between the two desktops shows that my configuration is not being changed --- just not honored. If the configuration changed, then when I returned to 3.5.10 I would see a white background and tabs on bottom. I don't. I see black and tabs on top.
OK, now I understand better. Sorry about that.
However, I am unable to find anything different between the stock 3.5.10 sources and the Trinity sources that would account for such behaviour. Is it possible Slackware changed the location of the Konsole configuration file?
Tim
Konsole white background, tabs on bottom.
Resolved.
The original 3.5.10 kdebase Slackware build script created a file in /usr/share/config named konsolerc. That file specified the default schema as Linux.schema. Adding that snippet to the Trinity build script seems have solved the problem.
My testing version of Debian Lenny does not have a /usr/share/config directory. I'm guessing then Lenny inherits the defaults of the upstream KDE. As Lenny exhibits this white background, tabs on bottom behavior, I'm guessing the original default 3.5.x konsole must use the BlackOnWhite schema. Trinity inherited these same defaults, hence the same behavior.
-
Darrell Anderson -
Timothy Pearson