Bug 124849

Summary:	Kopete doesn´t remember docked position on right border
Product:	[Plasma] kwin	Reporter:	Michael Stather <kontakt>
Component:	general	Assignee:	KWin default assignee <kwin-bugs-null>
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 Michael Stather 2006-04-03 20:47:38 UTC

Version:           0.11.93 (0.12 Beta 2) (using KDE 3.5.0 Level "a" , SUSE 10.0 UNSUPPORTED)
Compiler:          Target: i586-suse-linux
OS:                Linux (i686) release 2.6.13-15.8-default

When I move kopete to the right border of the screen, so that it attaches (like a magnet) to the screen boarder, and restart it, its position isn´t at the border but some pixels left of it. There´s a small "gap" between  the kopete border and the screen one.

Comment 1 Chani 2006-04-03 20:53:34 UTC

> When I move kopete to the right border of the screen, so that it attaches (like a magnet) to the screen boarder, and restart it, its position isn

Comment 2 Michael Stather 2006-04-03 23:08:52 UTC

There´s no gap (even a little one) at your system? Then this is one of the thousands of KDE bugs which will never be fixed :(

Comment 3 Philip Rodrigues 2006-04-04 23:32:35 UTC

Works fine here too (3.5.2, compiled from source). If it is really a bug, it's almost certainly a problem with kwin and not kopete - reassigning.

Comment 4 Lubos Lunak 2006-04-09 22:52:26 UTC

Sorry, I can't reproduce the problem either, unless you provide some more info. I suggest you check geometry in Alt+F3/Advanced/Special window settings (which in fact you may also use to work around the problem).

Comment 5 Michael Stather 2006-04-11 09:12:39 UTC

Strange, it works now, too. If it happens again I´ll reopen.
And if you are the session manager guys please have a look at this bug. It is IMHO the most severe KDE bug right now. I can´t see why somebody is unable to reproduce it, it really happens on almost all machines :(

http://bugs.kde.org/show_bug.cgi?id=121736