Bug 61351

Summary:	kstart --fullscreen doesn't take kicker screen space into account
Product:	[Unmaintained] kstart	Reporter:	Jens <jens-bugs.kde.org>
Component:	general	Assignee:	Matthias Ettrich <ettrich>
Status:	RESOLVED WORKSFORME
Severity:	normal
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	unspecified
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Jens 2003-07-17 10:13:47 UTC

Version:            (using KDE 3.1.9)
Compiler:          gcc version 3.3.1 20030626 (Debian prerelease)
OS:          Linux (i686) release 2.2.20

I have kicker at the top of my desktop, non-hidden, non-overlappable. (the first option in the respective kicker menu)

I start 'kstart --fullscreen xterm -fn 10x20".

kstart loads up a fullscreen xterm of which the lowermost line is not visible (outside the visible screen space).

If I set kicker to auto-hide or overlap, the xterm window that is started has the same size but moves further to the top. It seems that kstart calculates the fullscreen window size without taking kicker into account.

The same thing happens when I start 'kstart --fullscreen konsole' - then I can't see the konsole terminal session buttons at the bottom of the konsole application window.

I am using an up-to-date Debian unstable setup with CVS packages that are a couple days old (from opendoorsoftware.com).


Please have a look into this :-)

Thank you!


-- Jens

Comment 1 Jens 2004-02-07 19:19:48 UTC

closing. works now. (3.2.0-final)