Bug 73820

Summary: wrong font when starting new session
Product: [Applications] konsole Reporter: Wilbert Berendsen <wbsoft>
Component: generalAssignee: Konsole Developer <konsole-devel>
Status: RESOLVED FIXED    
Severity: normal    
Priority: NOR    
Version: 1.3   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Wilbert Berendsen 2004-01-30 14:13:40 UTC 
Version:           1.3 (using KDE 3.2.0 RC1, Gentoo)
Compiler:          gcc version 3.2.1
OS:          Linux (i686) release 2.4.23-ck1

I have different sessiontypes configured with different fonts.

When I start a session from the Konsole menu on the panel, it starts a Konsole window with the correct session and the correct font.

However, when I start a new, other, session from within that window, it will inherit the font from the running session, instead of getting its own, configured font.
Comment 1 Stephan Binner 2004-02-15 18:13:26 UTC 
What font is defined for the session type which the "new, other" session uses? Is it "<Default>"?
Comment 2 Wilbert Berendsen 2004-02-15 18:45:59 UTC 
No, the new session started from within the first session has "Small" preconfigured, but it uses the font from the old session, which is configured as "<Default>".

But it works either way. When I start Konsole from the kicker konsole menu with the other preconfigured session (which runs the "top" program btw), and then start a default shell session in that konsole instance, that session inherits the "Small" font setting from the "top" session.
Comment 3 Hans Dembinski 2004-07-02 13:23:41 UTC 
It's the same here. I defined a "logging session" with the font size "tiny", but when I start it tabbed in the same konsole window with other shell sessions, the font setting of the last opened session is used. All my other sessions are customized with the font size "huge". Funnily, if I look in the font settings of that newly opened logging session, the font size "tiny" is marked, but not used!
Comment 4 Wilbert Berendsen 2004-07-11 18:41:33 UTC 
This seems fixed in CVS as of now.
Comment 5 Kurt Hindenburg 2004-07-18 09:45:33 UTC 
Everything I tried works on the current CVS.