Bug 288934

Summary:	kde-misc/yakuake-2.9.6 is moving x/y of window on each invokation on fluxbox
Product:	Gentoo Linux	Reporter:	simon <s7mon>
Component:	[OLD] Unspecified	Assignee:	Marcus D. Hanwell (RETIRED) <cryos>
Status:	RESOLVED UPSTREAM
Severity:	normal	CC:	kde
Priority:	High
Version:	unspecified
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---
Attachments:	yakuake when started fresh yakuake after several hide/show runs

Description simon 2009-10-13 20:18:45 UTC

Yakuake (terminal emulator which scrolls in from screen-top like in FPS quake) gets a different window position than 0/0 each time it's invoked to scroll down under fluxbox (1.1.1-r1)

so after several uses it's no longer from top to e.g. 50% of the screen but from the middle to the bottom.

Reproducible: Always

Steps to Reproduce:
1. Start yakuake-2.9.6 (2.8 old codebase is fine) within fluxbox.
2. use key to show and hide yakuake several times


Actual Results:  
window position is moved downwards.

Expected Results:  
window position stays starting from top of the screen.

yakuake-2.8 (old kde3 codebase) works fine.

changed return value of   QRect MainWindow::getDesktopGeometry()
from mainwindow.cpp of yakuake to return fixed screen size with 
return QRect(0,0,1280, 1024);
but this didn't change the behavior.

Comment 1 simon 2009-10-13 20:28:20 UTC

Created attachment 207013 [details]
yakuake when started fresh

this is the correct position after startup of yakuake and where it should be positioned always.

Comment 2 simon 2009-10-13 20:29:27 UTC

Created attachment 207014 [details]
yakuake after several hide/show runs

this is current position after yakuake was hidden and shown a few times (~10x)

Comment 3 Tomáš Chvátal (RETIRED) gentoo-dev

2009-11-10 12:12:47 UTC

Hello, this is not gentoo bug at all, but upstream issue.
Please open bug in upstream bugzilla on http://bugs.kde.org/
When you have the bugreport reported upstream add please another comment here with the link to upstream bug (or add the link to the URL field of bug).

Thanks