Bug 177707

Summary:	panel height destroys plasma desktop
Product:	[Plasma] plasma4	Reporter:	mootchie <fm2097ad+kde>
Component:	general	Assignee:	Plasma Bugs List <plasma-bugs>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	andresbajotierra, aseigo
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Compiled Sources
OS:	Linux
Latest Commit:		Version Fixed In:

Description mootchie 2008-12-13 20:25:59 UTC

Version:            (using Devel)
OS:                Linux
Installed from:    Compiled sources

If I increase the height of the panel to some extreme value (like almost half the screen) the plasma desktop is destroyed and replaced with an empty grey box. No widgets or any mouse action is possible inside this dead zone.

However, if I then reduce the height the dead zone shrinks a little (but not completely).

Work around: logout and then back in.

Screenshot: http://bayimg.com/JamchaABh

Comment 1 mootchie 2008-12-19 20:01:20 UTC

The bug remains there exactly as before.

Using KDE4daily revision: KDETRUNKr898979 at Fri Dec 19 17:52:19 UTC 2008
Composite disabled (obviously, using virtualbox)
All defaults ( did a rm -rf .kde/ after update, read somewhere it might help... but didn't change the behavior of the bug )

Later I'll see if it also appears with the Kubuntu beta 2 packages.

Comment 2 mootchie 2008-12-20 18:22:43 UTC

Yep, same problem with Kubuntu beta2 packages (nvidia card, composite enabled).
The bug remains there.

Also noticed that if the increase in height is done in small steps it takes a larger height for it to destroy the plasma background. So the best way to cause this is just to push the height quickly to almost half the screen...

Comment 3 mootchie 2008-12-20 20:53:50 UTC

I just noticed this bug doesn't happen if you have two panels (one in the bottom and the other on top).

Therefore, if you intend to reproduce it make sure you just have the one bottom panel (like in the default, after the first login).

Comment 4 Dario Andres 2009-01-01 14:11:44 UTC


*** This bug has been marked as a duplicate of bug 176280 ***